Closed
Bug 579400
Opened 14 years ago
Closed 12 years ago
JM: Investigate BINDNAME degradation
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: dmandelin, Unassigned)
References
Details
Attachments
(1 file)
|
726 bytes,
text/html
|
Details |
Spun off from bug 494268 comment 13. This bug should add a PIC or the like for setting variables that are closed over, as in the test case for bug 494268.
We already do this - morphing bug to reflect the problem in the test case: [jaeger] PICs bind disabled: max stubs reached (k.js: 15)
Summary: JM: Make setting free variables fast → JM: Investigate BINDNAME degradation
|
Reporter | |
Comment 2•13 years ago
|
||
We are still 1.33x slower than Chrome on the original test case, linked here with loop sizes big enough so that we can measure time taken.
|
||
Comment 3•12 years ago
|
||
A recent Ion nightly is now about as fast as Chrome (and with ALIASEDVAR it should no longer use BINDNAME).
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•