ASSIGNED 161329
Move bytecode for finally block after the try block.
https://bugs.webkit.org/show_bug.cgi?id=161329
Summary Move bytecode for finally block after the try block.
Mark Lam
Reported 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.
Attachments
Note You need to log in before you can comment on or make changes to this bug.