Linked by Thom Holwerda on Fri 10th Sep 2010 15:06 UTC, submitted by lemur2
Permalink for comment 440602
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 05/20/13 11:29 UTC
Linked by Thom Holwerda on 05/18/13 21:33 UTC
Linked by David Adams on 05/16/13 4:23 UTC
Linked by Thom Holwerda on 05/11/13 21:41 UTC
Linked by Thom Holwerda on 05/08/13 14:22 UTC
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Linked by Thom Holwerda on 04/24/13 22:24 UTC
Linked by Thom Holwerda on 04/18/13 11:21 UTC
Linked by Thom Holwerda on 04/16/13 9:29 UTC
More Features »
Sponsored Links



Member since:
2010-07-16
You've got your terminology confused. The "new JIT eingine" *is* JaegerMonkey. And just btw, TraceMonkey uses JIT too. It's just that TM is tracing JIT, while JM is method JIT.
JaegerMonkey has been in development for at least three months, possibly more. It's just that it was developed in a branch. Then, on August 31st, it has been merged from it's own branch into the TraceMonkey branch. And yesterday, the now combined JM+TM have been merged into mozilla-central, which is the "trunk".
Oh, and let's throw another word into the mix: SpiderMonkey. What is SM? Well, it's Mozilla's JS engine as a whole. In the beginning, there was SM, an interpreter JS engine. Then, TM was added to it. And now JM too. So SpiderMonkey now consists of an interpreter, a tracing JIT engine and a method JIT engine.