Closed
Bug 788246
Opened 13 years ago
Closed 10 months ago
IonMonkey: Regression in 3d-raytrace from Aug 29 merge
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: dvander, Unassigned)
References
Details
(Whiteboard: [ion:t])
This was about a 2ms (10%) regression.
|
||
Comment 1•13 years ago
|
||
Note that bug 778724 was a 2.2 ms regression when it landed on inbound so this is likely the same issue and not IonMonkey-specific. We should at least compare the number of recompiles and type information to see if anything regressed there.
|
Reporter | |
Updated•13 years ago
|
Whiteboard: [ion:p1] → [ion:p1:fx18]
|
|
Reporter | |
Updated•13 years ago
|
Whiteboard: [ion:p1:fx18] → [ion:t]
|
Assignee | |
Updated•11 years ago
|
Assignee: general → nobody
|
||
Updated•3 years ago
|
Severity: normal → S3
|
||
Comment 2•10 months ago
|
||
v8/octane is not a priority. And things have moved a lot in the last 12 years or so.
Closing this.
You need to log in
before you can comment on or make changes to this bug.
Description
•