[Webkit-unassigned] [Bug 177925] New: Evaluate the benefit of skipping dead code in the DFGByteCodeParser when a function returns in its first block

[bugzilla-daemon at webkit.org]

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

            Bug ID: 177925
           Summary: Evaluate the benefit of skipping dead code in the
                    DFGByteCodeParser when a function returns in its first
                    block
           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

There is code in the treatment of op_ret in DFGByteCodeParser.cpp::parseBlock() that checks if an early return is from the first block.
In that case, it skips the rest of the function, knowing that all other blocks are dead code.
I would like to measure whether this is something that ever happens in actual code, because I do not see why it would happen, and if it does not, we could get rid of this code, and of everything that touches the shouldContinueParsing variable.


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/ae819ec1/attachment.html>