[Webkit-unassigned] [Bug 177926] New: Avoid allocating useless landingBlocks in DFGByteCodeParser::handleInlining()

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=177926

            Bug ID: 177926
           Summary: Avoid allocating useless landingBlocks in
                    DFGByteCodeParser::handleInlining()
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: JavaScriptCore
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: rmorisset at apple.com
        Depends on: 177922

In the polyvariant case, handleInlining allocates a separate landingBlock for each inlined callee, and then links them to a continuationBlock.
https://bugs.webkit.org/show_bug.cgi?id=177922 use of m_continuationBlock in the inlineStackEntry give us a way to avoid this, and have all the returns from the callees go directly to the continuationBlock.
One slight difficulty is that we will have to special case inlined intrinsics to keep their landingBlock, so that they still have somewhere to call processSetLocalQueue.


Referenced Bugs:

https://bugs.webkit.org/show_bug.cgi?id=177922
[Bug 177922] Refactor the inliner to simplify block linking
-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20171005/a211b474/attachment-0001.html>