Closed
Bug 1652549
Opened 4 years ago
Closed 4 years ago
Optimize BindGName in Warp
Categories
(Core :: JavaScript Engine: JIT, task, P1)
Core
JavaScript Engine: JIT
Tracking
()
RESOLVED
FIXED
mozilla80
| Tracking | Status | |
|---|---|---|
| firefox80 | --- | fixed |
People
(Reporter: iain, Assigned: iain)
Details
Attachments
(1 file)
JSOp::BindGName has an optimization in baseline to bake in the correct global env where possible, allowing us to avoid the IC. We should extend the same optimization to Warp. Otherwise, BindGName ops that are not executed in the baseline interpreter will have empty IC chains and generate a bailout snapshot.
|
||
Updated•4 years ago
|
Severity: -- → N/A
|
Assignee | |
Comment 1•4 years ago
|
||
|
||
Updated•4 years ago
|
Assignee: nobody → iireland
Status: NEW → ASSIGNED
Pushed by iireland@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/1106a2c9c199 Optimize BindGName in Warp r=jandem
|
||
Comment 3•4 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
status-firefox80:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla80
You need to log in
before you can comment on or make changes to this bug.
Description
•