Closed
Bug 469351
Opened 16 years ago
Closed 14 years ago
TM: loop with i<hColl.length slower with jit enabled
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: Dpeelen, Unassigned)
References
()
Details
Attachments
(1 file)
3.74 KB,
text/html
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; nl; rv:1.9.0.4) Gecko/2008102920 Firefox/3.0.4
Build Identifier: Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2a1pre) Gecko/20081212 Minefield/3.2a1pre
As a follow up of bug 451974, here some more for loop problems.
Both
for (var i=0; i<hColl.length; i++) { }
And
var i = 0; while (i < hColl.length) { i++; }
are 1.3x to 1.4x slower with JIT enabled then with JIT disabled. As i got the
idea these 2 problems are related, i put them in one bug for now.
Reproducible: Always
Reporter | ||
Updated•16 years ago
|
Version: unspecified → Trunk
Reporter | ||
Comment 1•16 years ago
|
||
Comment 2•16 years ago
|
||
We're aborting because of the DOM access here, but I'd still expect us to blacklist this....
Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: blocking1.9.1?
Comment 4•14 years ago
|
||
This is about as fast as Chrome now. It's even faster with JM or JIT profiling disabled, I will file a follow up bug for that.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Comment 6•14 years ago
|
||
Ah, bug 606494.
Comment 7•14 years ago
|
||
(In reply to comment #5)
> Please post that followup bug number here?
Sorry, will post it next time and block 467263 for perf bugs :)
You need to log in
before you can comment on or make changes to this bug.
Description
•