Bug 175842 - If a catch OSR exit becomes hot but we didn't compile the catch in DFG IR, we should consider reoptimizing the codeblock
Summary: If a catch OSR exit becomes hot but we didn't compile the catch in DFG IR, we...
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: JavaScriptCore (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Saam Barati
URL:
Keywords:
Depends on: 174590
Blocks:
  Show dependency tree / graph
 
Reported: 2017-08-22 12:49 PDT by Saam Barati
Modified: 2017-08-22 12:50 PDT (History)
11 users (show)

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 Saam Barati 2017-08-22 12:49:50 PDT 
What could happen is:
- We notice an op_catch never executes, so we don't compile it
- Then we start exiting to that op_catch
- We never jettison

In such situations, it could be useful to jettison and reoptimize so the catch is optimized