3 ms·
So this is a purely software solution? I wonder if we could see ARM SoCs with some hardware for decoding x86 instructions and have them executed by the ARM core
by simias 14y ago
So this is a purely software solution? I wonder if we could see ARM SoCs with some hardware for decoding x86 instructions and have them executed by the ARM core.
After all since ARM7 most ARM cores support both ARM and THUMB instruction sets.
I'm not sure you could do that without permission from Intel though.
- rthomas6 14y agoAccording to Wikipedia, the instruction set is open, but for "some advanced features," they may need a license from Intel. I'm not sure what advanced features that would be.
- lucian1900 14y agoProbably things like SSE.
- mtgx 14y agoIndeed, AMD licenses the SSE from Intel, and Intel licenses x64 from AMD.
- lucian1900 14y agoAt that point, it'd basically become an x86 core, with all the space and complexity that requires. It's easier to translate in software.
- simias 14y agoI was not thinking about full blown x86 support, but partial support where it matters. A bit like the Jazelle Java bytecode support, it wouldn't really run x86 code in native but would support extensions that would make it easier and faster. I'm not familiar enough with the x86 instruction set to guess where this would really improve performances though.
- lucian1900 14y agoEven Jazelle is being dumped, since it was too complex in hardware. And x86 is much more complicated than JVM bytecode. Modern "Jazelle" is basically just Thumb (I think it's even called Thumb EE), and it requires software to translate to it (JIT to Thumb instead of to ARM).
- sneak 14y ago> I'm not sure you could do that without permission from Intel though. Then how does AMD do it?
- allenp 14y agoAMD licenses the right to produce x86 compatible chips from Intel.
- vetinari 14y agoThat's because AMD cores were not independently developed from scratch. Cyrix core, on the other hand, was. They never oficially licensed x86 and the problems between Intel and Cyrix ended as out of court settlement to save Intel's face.
- pm215 14y agoI don't think decode is really the hard part; if you're JITting at all it's pretty easy. The difficulties arise where the semantics of the target and the host don't match up. For instance, emulating a strong-memory-model architecture like x86 on a weak-memory-model architecture like ARM requires a pile of explicit memory barriers if you're going to handle multi-threaded binaries. Emulating atomic memory accesses might also be tricky. Differences in floating point semantics (like x86's 80-bit format or just different choices of IEEE implementation specifics) are also painful: QEMU takes the slow-but-safe option of doing all the floating point emulation in software (ie using integer arithmetic) to ensure bit-for-bit accuracy. None of these pain points is really related to the instruction decoding.
- koenigdavidmj 14y agoAccording to Herb Sutter at [1], ARMv8 will support a couple new ops to support sequentially consistent memory access. 1: http://herbsutter.com/2012/08/02/strong-and-weak-hardware-memory-models/ http://herbsutter.com/2012/08/02/strong-and-weak-hardware-me...