2 ms·
I would expect that Apple would bring back the Rosetta component for such cases (i.e. the same interface to the OS, but now a component doing Intel->ARM dynamic
by derefr 8y ago
I would expect that Apple would bring back the Rosetta component for such cases (i.e. the same interface to the OS, but now a component doing Intel->ARM dynamic binary translation rather than PWR->Intel dynamic binary translation.)
Actually, maybe dymamic binary translation wouldn't be needed all that often. A new Rosetta would likely also be helped out quite a bit by the fact that modern macOS binaries contain embedded copies of their their LLVM intermediate representation; you could transpile that IR (by patching Intel-targeted intrinsics with ARM polyfills) and then run it through the LLVM optimizer again, and then cache the result. That's a fully static binary translation, and the resulting binaries would probably be pretty fast.
(You'd still need dynamic binary translation for anything with its own JIT, but maybe there are few enough programs with their own JITs—and all such programs are "big" enough in terms of development resources—that Apple can require these to ship an ARM target. In which case, maybe they don't need to build a new dynamic binary translation component at all!)
- jmount 8y agoThe translation stuff may be okay for user code (and I know Apple has done it before). But for scientific code it is just too much cost and too many things to break. I know scientists are not Apple's target market, but this just makes getting a Linux laptop a much better proposition.