Closed Bug 470738 Opened 17 years ago Closed 16 years ago

TM: 6X slower with Math.max, loop

Categories

(Core :: JavaScript Engine, defect)

x86
macOS
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 470779

People

(Reporter: jruderman, Unassigned)

Details

(Keywords: perf, testcase)

for (var a = 0; a < 100000; ++a) { Math.max(1); for (var b = 0; b < 4; ++b) { } } 6X slower when JIT is enabled. Keeps hitting a side exit?
Might be related to bug 470737 (there's an implicit -Infinity when you use Math.max) or bug 470779 (because of the inner loop).
Not bug 470737 -- that's fixed and this bug remains. Now that I understand bug 470779, I can see that this is a result of that bug along with Math.max with exactly one argument not being traced: abort: 6165: unknown native Abort recording (line 2, pc 21): call.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.