Closed Bug 500304 Opened 11 years ago Closed 11 years ago

turn on chrome jit by default

Categories

(Core :: JavaScript Engine, defect)

x86
All
defect
Not set

Tracking

()

VERIFIED FIXED
Tracking Status
status1.9.2 --- beta1-fixed

People

(Reporter: sayrer, Assigned: sayrer)

References

Details

(Keywords: verified1.9.2, Whiteboard: fixed-in-tracemonkey)

Attachments

(1 file)

No description provided.
Attached patch flip the prefSplinter Review
I'll run this through the tryserver
Flags: blocking1.9.2+
OS: Mac OS X → All
Version: unspecified → Trunk
At least bug 499610 has to be fixed, adding dependency.
Depends on: 499610
Attachment #384984 - Flags: review?(brendan)
Comment on attachment 384984 [details] [diff] [review]
flip the pref

I think this is ready.
Attachment #384984 - Flags: review?(brendan) → review+
http://hg.mozilla.org/tracemonkey/rev/3ee14f5164bc
Whiteboard: fixed-in-tracemonkey
hey rob, other than testing popular websites, what are suggested testcases you think we should run and focus on, once you land this on trunk?
(In reply to comment #5)
> hey rob, other than testing popular websites, what are suggested testcases you
> think we should run and focus on, once you land this on trunk?

Bug 453668 -  TM: Regressions with JIT enabled for Chrome

There's only bug 481804 left there.
http://hg.mozilla.org/mozilla-central/rev/3ee14f5164bc
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Mass change: adding fixed1.9.2 keyword

(This bug was identified as a mozilla1.9.2 blocker which was fixed before the mozilla-1.9.2 repository was branched (August 13th, 2009) as per this query: http://is.gd/2ydcb - if this bug is not actually fixed on mozilla1.9.2, please remove the keyword. Apologies for the bugspam)
Keywords: fixed1.9.2
Verified fix in Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2a2pre) Gecko/20090825 Namoroka/3.6a2pre
and Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.3a1pre) Gecko/20090825 Minefield/3.7a1pre
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.