Toolkit/crashreporter/client/crashreporter_osx.mm - add CPU_TYPE_X86 Xpcom/string/public/nsUTF8Utils.h - remove two add'l MOZILLA_MAY_SUPPORT_SSE2 ifdefs vs. Nsprpub/pr/src/md/unix/pratom.h - remove references to stuff we took out of os_Darwin.s Nsprpub/pr/src/md/unix/os_Darwin.s - remove ppc asm stuff With the hard work already done it took less than half an hour if you exclude the time spent compiling it. There's probably other stuff I missed (OpenGL stuff, maybe?) but it worked and was quite stable. Sorry, no patch-it was my first time using Mercurial. In case anyone's interested, here are the notes I kept. For example, Sunspider ran in 343ms on 10.8 and 383ms on TFF/10.4 on my late '07 MBP. It's slightly slower than mainline FF on newer OS X. It runs very well, with the Intel-specific optimizations from the main tree intact. It seems Cameron did quite a good job of keeping PPC-specific things #ifdef'd out, so the changes required were very small for the most part. Out of curiosity I decided to try compiling TFF 17.0.2 on Intel Tiger. But I have too much on my plate to support it myself, especially since I have no way of really testing it. Interested? Grab it, give it a spin, let me know how it goes. Then you can use the 10.4-widget, graphics and font support, which should work with no changes.
Tenfourfox or aurorafox code#
This is non-trivial, but the x86 code obviously is already in the code base you just have to get everything pointing back to it, since I didn't really design the source for cross-compilation.
It would not be difficult to do: you'd have to undo the current JS compiler and point it to the built-in x86 one instead, change the AltiVec code to point to the built-in SSE2 equivalents, and make sure we haven't made any big-endian assumptions (usually we're dealing with code that makes little-endian assumptions). However, I would be happy to point people towards such a build and maybe even host it.
Tenfourfox or aurorafox software#
I get periodic questions about an Intel TenFourFox, but I don't use Intel 10.4, and I have a standing rule I don't support software I don't use (which is sort of a question about TTYtter since I don't use Twitter much if ever anymore - moved to App.net). And, like theos911 said, use the G3 version. If the browser starts okay in safe mode, that's the problem (hold down Option as you start it). It's probably the JavaScript compiler - it plays fast and loose with stack frames to get everything to fit in the limited OS X PPC stack range.
0 kommentar(er)
