2 ms·
Oh well, I guess the rumor is junk then. I will say, however, that executing LLVM bitcode on different targets than the compilation machine is a subject of act
by woodruffw 7y ago
Oh well, I guess the rumor is junk then.
I will say, however, that executing LLVM bitcode on different targets than the compilation machine is a subject of active research. It's one of the things that I work on in my day job.
- scarface74 7y agoRelevant quote: 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. What’s funny, is later on after Apple shipped a 64 bit chip for the Apple Watch. He admitted that forcing developers to ship watch apps as bitcode allowed Apple to recompile all of the third party Watch apps on the fly to support it, he knew that was coming, but couldn’t say anything at the time. https://twitter.com/clattner_llvm/status/1046960724646465541 https://twitter.com/clattner_llvm/status/1046960724646465541