Closed
Bug 1917766
Opened 1 year ago
Closed 1 year ago
Don't iterate over all ranges in HasFollowingRangeSharingVreg
Categories
(Core :: JavaScript Engine: JIT, task, P1)
Core
JavaScript Engine: JIT
Tracking
()
RESOLVED
FIXED
132 Branch
| Tracking | Status | |
|---|---|---|
| firefox132 | --- | fixed |
People
(Reporter: jandem, Assigned: jandem)
References
Details
Attachments
(1 file)
This is one of the simpler fixes for bug 1916442. The function should start iterating at range instead of going through all ranges that precede it first. This cuts off ~16 seconds (about 7%) for me locally for that Wasm module.
|
Assignee | |
Comment 1•1 year ago
|
||
This also renames prevRange to nextRange. The prevRange name was likely
copy/pasted from HasPrecedingRangeSharingVreg.
|
||
Updated•1 year ago
|
Severity: -- → N/A
Priority: -- → P1
Pushed by jdemooij@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/6c377a20623a
Fix HasFollowingRangeSharingVreg to start iterating at |range|. r=jseward
|
||
Comment 3•1 year ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
status-firefox132:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 132 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•