Den 01. sep. 2011 15:09, skrev Knoll Lars (Nokia-MP-Qt/Oslo): > On 9/1/11 2:58 PM, "ext Thiago Macieira"<[email protected]> wrote: > >> >> If the ARM simulator works, that's a start. Full MIPS functionality would >> be >> preferred, considering how important Qt is on MIPS. > I agree. There's work ongoing to fully support V8 on MIPS. I'm not 100% > sure what the status is right now, but I heard it's working. That would be > the best solution to support MIPS.
https://groups.google.com/forum/#!topic/fameisfame/YR6f8pA7jYc has a recent status. "The team doing the MIPS port] are not part of V8 team but they are contributing their code back to main V8 repo. [...] Our main repo AFAIK is still behind theirs in terms of MIPS support (e.g. optimizing compiler is not yet merged)." On a related note, I tested a trunk build of the MIPS simulator on ia32, and it seems to be working: scons mode=debug simulator=mips -j0 sample=shell then run "./shell_g --print_code" and enter some JavaScript... But like the ARM simulator, this also only works for 32-bit builds. >> V8 was announced. V8 blocking the build of Qt Base and/or QtCore wasn't. >> QtCore doesn't depend on V8 yet. Sure, that might be the direction we want to go, but it doesn't do it _yet_. I'm sorry about the (unannounced) breakage of Qt Base. I'll be doing what I can to ensure that V8 stays "out of the way" for those who don't need it / can't build it. Step one should be working now (when -no-v8 is given, don't build it!); step two would be configure-time detection, as you suggested. > >>> The simulator should work on all platforms, and it's a way to get the >>> full >> It doesn't and that's the problem. The ARM simulator is supported right >> now on >> i386 only. Not even x86-64 is supported. See above. > Hmmm... I didn't know that. I thought it was generic C++ code interpreting > ARM instructions. Kent, can you have a look? Confirmed, see Thiago's later mail. Some pointers (e.g. callbacks) that you pass through the public API are written straight to fields of JS heap objects, and there's no provision for host pointer size being different from target pointer size, it seems. Regarding performance of the ARM simulator: Compared to a native build, the slowdown on ia32 is about 150x on average for the V8 benchmarks (as much as 250x for one, down to 15x for another). Kent _______________________________________________ Qt5-feedback mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback
