Closed
Bug 1440648
Opened 7 years ago
Closed 7 years ago
Need to handle JSTRY_FOR_OF in JSScript::hasLoops()?
Categories
(Core :: JavaScript Engine: JIT, enhancement, P3)
Core
JavaScript Engine: JIT
Tracking
()
RESOLVED
FIXED
mozilla63
People
(Reporter: anba, Assigned: khyperia)
Details
Attachments
(1 file)
1.19 KB,
patch
|
jandem
:
review+
|
Details | Diff | Splinter Review |
JSScript::hasLoops() is currently only used for IonBuilder::makeInliningDecision(...) and makeInliningDecision(...) was modified in bug 1142669 to use different inlining heuristics when loops are present. At about the same time bug 1143194 added JSTRY_FOR_OF. And now I'm wondering if the modified heuristics should also apply to for-of loops?
Comment 1•7 years ago
|
||
Yeah we probably should add it. Also there should probably be some kind of switch-statement or MOZ_ASSERT so if we add a new try note we will update that code.
Updated•7 years ago
|
Priority: -- → P3
Assignee | ||
Comment 2•7 years ago
|
||
Assignee | ||
Updated•7 years ago
|
Assignee: nobody → khyperia
Status: NEW → ASSIGNED
Assignee | ||
Updated•7 years ago
|
Attachment #9002541 -
Flags: review?(jdemooij)
Comment 3•7 years ago
|
||
Comment on attachment 9002541 [details] [diff] [review]
Add JSTRY_FOR_OF to JSScript::hasLoops, and guard against new JSTRY values.
Review of attachment 9002541 [details] [diff] [review]:
-----------------------------------------------------------------
LGTM.
Attachment #9002541 -
Flags: review?(jdemooij) → review+
Assignee | ||
Updated•7 years ago
|
Keywords: checkin-needed
Pushed by dluca@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/03537843fab2
Add JSTRY_FOR_OF to JSScript::hasLoops, and guard against new JSTRY values. r=jandem
Keywords: checkin-needed
Comment 5•7 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
status-firefox63:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla63
Updated•7 years ago
|
status-firefox61:
--- → wontfix
status-firefox62:
--- → wontfix
You need to log in
before you can comment on or make changes to this bug.
Description
•