Open Bug 934418 Opened 11 years ago Updated 2 years ago

Split RuntimeOptions off from ContextOptions

Categories

(Core :: JavaScript Engine, defect)

defect

Tracking

()

People

(Reporter: ejpbruel, Unassigned)

References

Details

No description provided.
Blocks: 885526
OS: Mac OS X → All
Hardware: x86 → All
Whiteboard: [Shumway:m2]
Depends on: 939562
Depends on: 938907
Moving all the flags from the context to the runtime in one go turned out to be a bit too much to chew, so I've opened up two sub-bugs: bug 938907 removes the compile and go flag from ContextOptions completelty, and bug 939562 moves the JIT flags from the ContextOptions to RuntimeOptions.
Depends on: 940305
Depends on: 940316
Depends on: 940317
Depends on: 940318
Depends on: 940321
Depends on: 940323
I've opened separate bugs for each of the remaining flags, as we agreed on irc.
Assignee: ejpbruel → nobody
Depends on: 1037756
8/9 blockers are done for this now!! Would be so so awesome to get that last one!
Whiteboard: [Shumway:m2]
Woohoo! 9/9 blockers are done for this now. Eddy, Bobby, is there any chance either of you guys would have a chance to look at this now with all the blocking work completed?
You guys think you'll be able to look at this one?
(In reply to Ben McCann from comment #5) > You guys think you'll be able to look at this one? I see you filed bug 885786 but note that the issue there should have been fixed a while ago, by bug 939562 and others. Fixing *this* bug is unlikely to help add-on performance. If you still see cases where add-on JS is much slower than website JS I'd love to know about it!
Ahh, thanks! So do you think it's wrong that bug 885786 is marked as depending on this bug?
No longer blocks: 885786
(In reply to Ben McCann from comment #7) > Ahh, thanks! So do you think it's wrong that bug 885786 is marked as > depending on this bug? I changed it so bug 885786 depends on bug 939562 (fixed about a year ago) instead of this one. The remaining ContextOptions are not performance-sensitive. Let me know if bug 885786 is still a problem for you, if it is please also try with a recent Nightly build and file a new bug. Thanks!
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.