Closed
Bug 851053
Opened 11 years ago
Closed 11 years ago
IonMonkey: Remove MRecompileCheck
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
mozilla22
People
(Reporter: jandem, Assigned: jandem)
Details
Attachments
(1 file)
29.13 KB,
patch
|
bhackett1024
:
review+
|
Details | Diff | Splinter Review |
It's from the time we thought we would use Ion itself as baseline compiler. With JM or baseline, it doesn't add much other than extra code/complexity.
Assignee | ||
Comment 1•11 years ago
|
||
Attachment #724872 -
Flags: review?(bhackett1024)
Updated•11 years ago
|
Attachment #724872 -
Flags: review?(bhackett1024) → review+
Comment 2•11 years ago
|
||
Can you provide sunspider / octane results when running with --no-jm before and after the patch? Just to check if there is not a corner case here.
Assignee | ||
Comment 3•11 years ago
|
||
(In reply to Nicolas B. Pierron [:nbp] from comment #2) > Can you provide sunspider / octane results when running with --no-jm before > and after the patch? Just to check if there is not a corner case here. I can measure, but question is if we care about --no-jm. Like --ion-eager, it's not the default configuration on any platform and only there for testing purposes I think...
Comment 4•11 years ago
|
||
(In reply to Jan de Mooij [:jandem] from comment #3) > (In reply to Nicolas B. Pierron [:nbp] from comment #2) > > Can you provide sunspider / octane results when running with --no-jm before > > and after the patch? Just to check if there is not a corner case here. > > I can measure, but question is if we care about --no-jm. Like --ion-eager, > it's not the default configuration on any platform and only there for > testing purposes I think... The answer is no, we don't care, but it would be informative to know if this had any effect or not.
Assignee | ||
Comment 5•11 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/6fdbfac4b51c (In reply to Nicolas B. Pierron [:nbp] from comment #2) > Can you provide sunspider / octane results when running with --no-jm before > and after the patch? Just to check if there is not a corner case here. SS seems to be about 5% faster with the patch, other than that I don't see much of a difference.
Comment 6•11 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/6fdbfac4b51c
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla22
You need to log in
before you can comment on or make changes to this bug.
Description
•