Bug 161329 - Move bytecode for finally block after the try block.
Summary: Move bytecode for finally block after the try block.
Status: ASSIGNED
Alias: None
Product: WebKit
Classification: Unclassified
Component: JavaScriptCore (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Mark Lam
URL:
Keywords:
Depends on: 160168
Blocks:
  Show dependency tree / graph
 
Reported: 2016-08-29 13:51 PDT by Mark Lam
Modified: 2016-08-29 13:51 PDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Mark Lam 2016-08-29 13:51:10 PDT 
Once we de-dupe finally blocks, it makes more sense for the finally block to follow the try block instead of the catch block following the try block.  This is because in the course of normal execution, the try block will fall thru to the finally block.  We should minimize the jumps in the normal case.