3 ms·
This is not true. It would not allow them to transpile between architectures. This myth was dispelled by no less than Chris Lattner on ATP. Even though he did
by scarface74 7y ago
This is not true. It would not allow them to transpile between architectures.
This myth was dispelled by no less than Chris Lattner on ATP.
Even though he did later admit that he wasn’t completely being honest. Part of the purpose of the bitcode requirement for the Watch was that Apple knew that they would be shipping a 64 bit chip for the Watch two years later.
https://atp.fm/205-chris-lattner-interview-transcript https://atp.fm/205-chris-lattner-interview-transcript
Bitcode is not [12:30] a magic solution, though. You can't take a 32-bit app, for example, and run it on a 64-bit device. That kind of portability isn’t something that Bitcode can give you, notably because that is something that's visible in C. As you're writing C code, you can write #ifdef pointer size equals 32, and that’s something that Bitcode can't abstract over. It's useful for very specific, low-level kinds of enhancements, but it isn't a panacea that makes everything [13:00] magically portable.
John Siracusa: The same thing I would assume for architecture changes, especially if there was an endian difference, because endianness is visible from the C world, so you can't target different endianness?
Chris Lattner: Yep. It's not something that magically solves all portability problems, but it is very useful for specific problems that Apple's faced in the past.
- Rolcol 7y agoIn the case of a Mac transition, applications would go from little-endian 64bit x86_64 to little-endian 64bit AArch64.
- threeseed 7y agoAll of the OSX apps are 64-bit. And ARM I believe has runtime-selectable endianness.
- scarface74 7y agoHe wasn’t saying that the only difficulty in using bitcode was translating from 32 bit to 64 bit and endianness but just thst was one of the issues.