Closed
Bug 1144361
Opened 9 years ago
Closed 9 years ago
Enable jit code randomization on windows x64
Categories
(Core :: JavaScript Engine: JIT, defect)
Tracking
()
RESOLVED
FIXED
mozilla41
Tracking | Status | |
---|---|---|
firefox41 | --- | fixed |
People
(Reporter: evilpie, Unassigned)
References
Details
(Keywords: sec-want, Whiteboard: [adv-main41-])
Attachments
(1 file)
1.23 KB,
patch
|
jandem
:
review+
|
Details | Diff | Splinter Review |
Sad story, this was apparently disabled for a sunspider regression in bug 728623! http://mxr.mozilla.org/mozilla-central/source/js/src/jit/ExecutableAllocatorWin.cpp#232
Reporter | ||
Updated•9 years ago
|
Blocks: support-win64
Linking the bugs to create a path from that code comment to here.
Depends on: 728623
In quick testing I don't see the regression anymore. Definitely not the 2x slowdown seen in bug 728623. I tried both the current sunspider 1.0.2 and the 0.9.1 as originally filed. I guess 3 years can do a lot to the code! I'm going to put up a patch and let the experts tell me what to scrutinize more closely.
I just did a few local tests on the sunspider website. The overall score goes slightly down with this patch, but I think it's noise. In any case it's certainly not regressing. What further testing should I do on this patch? Do you guys have local command line perf tests or things like that?
Attachment #8604904 -
Flags: review?(jdemooij)
Comment 4•9 years ago
|
||
Comment on attachment 8604904 [details] [diff] [review] Re-enable JIT code randomization on Win64 Review of attachment 8604904 [details] [diff] [review]: ----------------------------------------------------------------- Thanks! The original sunspider regression is gone so we should just land this IMO.
Attachment #8604904 -
Flags: review?(jdemooij) → review+
https://hg.mozilla.org/mozilla-central/rev/6d24046cb041
Status: NEW → RESOLVED
Closed: 9 years ago
status-firefox41:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla41
Updated•9 years ago
|
Whiteboard: [adv-main41-]
You need to log in
before you can comment on or make changes to this bug.
Description
•