Closed
Bug 683039
Opened 12 years ago
Closed 12 years ago
IonMonkey: delayed compilation
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: bhackett1024, Assigned: dvander)
References
Details
Attachments
(1 file)
3.49 KB,
patch
|
bhackett1024
:
review+
|
Details | Diff | Splinter Review |
Code needs to warm up a little before TI can provide good information for property accesses etc. in a script. IonMonkey should support delayed compilation in a similar manner to JM, though for now will only enter scripts at function entry rather than at loop heads.
![]() |
Assignee | |
Comment 1•12 years ago
|
||
Introduces delayed compilation and --ion-eager to get around it.
![]() |
Assignee | |
Comment 2•12 years ago
|
||
This potentially makes testing more annoying right now, since we'll have to type --ion-eager all the time, so if anyone would rather see --ion-lazy instead, let me know and I'll change it. (Though, in theory, we'd like to be testing with type inference which will need lazy compilation.)
Reporter | ||
Updated•12 years ago
|
Attachment #556722 -
Flags: review?(bhackett1024) → review+
![]() |
Assignee | |
Comment 3•12 years ago
|
||
http://hg.mozilla.org/projects/ionmonkey/rev/4ceb3e9961e4
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
![]() |
||
Comment 4•12 years ago
|
||
This made a huge difference for JM's memory consumption, so it's good to see IonMonkey getting the same treatment.
You need to log in
before you can comment on or make changes to this bug.
Description
•