From: C.W. B. <com...@ho...> - 2012-06-28 01:04:38
|
If you are planning on using TCG from Qemu, you will have to use the TCG interpreter because otherwise clang will fail due to a global register variable. At least on the i386 code. ... On further testing, it works fine on the PowerPC code; you don't need to use the TCG interpreter, just the regular TCG will work fine. On Jun 18, 2012, at 10:18 PM, Gwenole Beauchesne wrote: > Hi, > > Le 19 juin 2012 à 02:27, Frank Trampe a écrit : > >> Given the high level of interest in improving SheepShaver, it seems like it might be good to get it to the point at which it compiles on newer versions of Mac O.S., which probably means getting the code to compile in clang-llvm. > > The JIT based on dyngen needs to be built with GCC. You can select the GCC compiler to be used, see DYNGEN_CC variable. > > Here are the solutions for the PPC emulator, in increasing order of complexity to implement: > > 1. Always use GCC as it is intended, and set DYNGEN_CC accordingly. > 2. Ship with pre-compiled ELF binaries and regenerate synthetic opcodes from that, or ship with pre-generated .{h,cpp} files that implement the opcodes for the supported target architectures (x86, x86_64, etc.) > 3. Rework the JIT: migrate to TCG but VMX emulation performance will suffer, migrate to a full-blown DBT engine > > I'd like to keep the dyngen-based generator for now as it would allow for easy update for AVX1/AVX2 support. At some point, I was also working on a mix of dyngen + something similar to what was implemented for QEMU (TCG). > > Regards, > Gwenole. > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > basilisk-devel mailing list > bas...@li... > https://lists.sourceforge.net/lists/listinfo/basilisk-devel > |