Google Code Exporter

``` This at least gets us to the default SpiderMonkey implementation without TraceMonkey. It might be worth doing that first to find any glitches there, make a save point, and...

``` ... and make sure we obey https://developer.mozilla.org/En/SpiderMonkey/JSAPI_User_Guide ``` Original comment by `[email protected]` on 22 Apr 2010 at 1:31

``` Flipped the switch on SpiderMonkey tonight. Still have a lot of problems with jQuery sites, including jquery.org itself (need to get the uncompressed version and do some testing in...

``` The key problems to overcome will be namespaces, which it appears CW 7.1 *does* support, and code generation, which is currently written only for GCC in the PPC nanojit....

``` TraceMonkey is already a failure. The rdtsc emulation code uses mftb/mftbu, and I don't think mfrtcl/mfrtcu is going to be an adequate substitute for 601. More to the point,...

``` Comparison with MXR shows that we are now running the same engine as Firefox 3.0.19. This is a huge leap forward. ``` Original comment by `[email protected]` on 17 May...

``` No new problems have been found; they are all DOM. I am holding this bug over for the TraceMonkey conversion which I want to do around 9.4. ``` Original...

``` https://bugzilla.mozilla.org/show_bug.cgi?id=300030 This would be nice to do, since a lot of subsequent bugs depend on it. Somewhat intimidated by its size, however. Have not yet evaluated feasibility. ``` Original...

``` https://bugzilla.mozilla.org/show_bug.cgi?id=209694 I suspect www.theregister.co.uk is the test case. Notice the overlaps. ``` Original comment by `[email protected]` on 31 May 2009 at 10:45

``` Layout 300030 will be targetted to "9.0.5"; see the new Roadmap entry. ``` Original comment by `[email protected]` on 1 Jun 2009 at 4:45