Closed
Bug 551087
Opened 16 years ago
Closed 16 years ago
JM: Enable JaegerMonkey in the browser
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
People
(Reporter: dmandelin, Assigned: dmandelin)
References
Details
Basically, make it handled the same way the trace jit is now. I think at first, in the JM repo, we want the method jit enabled by default for content only, and the trace jit disabled. We'll re-enable once they are integrated.
| Assignee | ||
Updated•16 years ago
|
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Comment 1•16 years ago
|
||
I'm assuming this was the relevant changeset:
http://hg.mozilla.org/users/danderson_mozilla.com/jaegermonkey/rev/f2c8a8d35d6f
1.2 +++ b/build/automation.py.in
1.8 +user_pref("javascript.options.jit.content", false);
That should probably be .tracejit.content?
| Assignee | ||
Comment 2•16 years ago
|
||
(In reply to comment #1)
> I'm assuming this was the relevant changeset:
> http://hg.mozilla.org/users/danderson_mozilla.com/jaegermonkey/rev/f2c8a8d35d6f
>
> 1.2 +++ b/build/automation.py.in
> 1.8 +user_pref("javascript.options.jit.content", false);
>
> That should probably be .tracejit.content?
Good catch. Thanks!
You need to log in
before you can comment on or make changes to this bug.
Description
•