Closed
Bug 1073587
Opened 10 years ago
Closed 3 years ago
Eliminate redundant MaybeCopyElementsForWrite instructions
Categories
(Core :: JavaScript Engine: JIT, defect, P5)
Core
JavaScript Engine: JIT
Tracking
()
RESOLVED
INVALID
People
(Reporter: jandem, Unassigned)
References
Details
See the script below. For each of the 3 SETELEM's we add MMaybeCopyElementsForWrite, MElements, MInitializedLength, MBoundsCheck. function f() { var x = [1, 2, 3]; var t = new Date; for (var i=0; i<10000000; i++) { x[0] = i; x[1] = i; x[2] = i; } print(new Date - t); } f(); I noticed this on the "Test 0" test in bug 679710 where this is measurably slowing us down.
Comment 1•9 years ago
|
||
I get 40 for Nightly and 60 for Chrome 43. Is this still a problem?
Reporter | ||
Comment 2•8 years ago
|
||
Yeah we still have multiple MaybeCopyElementsForWrite instructions.
Priority: -- → P5
Comment 3•3 years ago
|
||
No longer valid, MaybeCopyElementsForWrite
was removed in Warp.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•