Closed Bug 606483 Opened 12 years ago Closed 12 years ago
Pixastic desaturate test no longer traces with jit profiling
I really wish we had actual performance regression tests for this stuff... This benchmark has a single loop, the loop iterates for a bajillion (4096000) iterations, and the loop body is: data[pix-=4] = data[pix1=pix+1] = data[pix2=pix+2] = (data[pix]+data[pix1]+data[pix2])/3 This seems like the canonical tracing use-case to me...
Comment on attachment 485347 [details] [diff] [review] patch This seems to fix the problem by giving the tracer priority for typed arrays.
Attachment #485347 - Flags: review?(bzbarsky)
Comment on attachment 485347 [details] [diff] [review] patch r=me. Looks great.
Attachment #485347 - Flags: review?(bzbarsky) → review+
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.