Closed Bug 979859 Opened 11 years ago Closed 10 years ago

Math.max not supported in parallel sections

Categories

(Core :: JavaScript Engine, defect)

x86_64
Linux
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: lth, Unassigned)

References

Details

(Whiteboard: [PJS])

Attachments

(2 files)

Calling Math.max() from a parallel section causes many bailouts with both 2 and 4 arguments.  Using a custom max() function gets rid of the bailouts.

What concerns me, in a run on the attached program, is that there are many fewer bailouts than calls to mapPar, but (unsubstantiated speculation) perhaps the code gets marked as parallel-unfriendly at some point and execution falls back to sequential.  Also, there are fewer bailouts when running in a debug shell than in a release shell.

AMD FX-4100, Ubuntu 13.10 64-bit, mozilla-central 171972:714c8927d6af.
Attached image Input file
There were some fixes to Math.max previously, I forget the bug number, perhaps those were enough: with current code and Math.max I see no bailouts, and there's plenty of parallel work.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: