3 ms·
It's not every app as far as I know because I believe you can opt out of BitCode, but this would be widely the case with exceptions: https://thenextweb.com/app
by awinder 6y ago
It's not every app as far as I know because I believe you can opt out of BitCode, but this would be widely the case with exceptions:
https://thenextweb.com/apple/2015/06/17/apples-biggest-developer-news-at-wwdc-that-nobodys-talking-about-bitcode/ https://thenextweb.com/apple/2015/06/17/apples-biggest-devel...
https://www.highcaffeinecontent.com/blog/20190518-Translating-an-ARM-iOS-App-to-Intel-macOS-Using-Bitcode https://www.highcaffeinecontent.com/blog/20190518-Translatin... (other direction but clearly demonstrative of what apple can do here)
- saagarjha 6y agoYes, Bitcode is not a requirement for the Mac App Store. Furthermore, Steven’s blog post is misleading: it implies that Apple can just seamlessly translate IR into a different architecture, and shows it kind of working for the simple example he has there. The problem is that this falls apart for anything that is more than mildly complicated (which, of course, is not mentioned in he blog post) because of ABI differences. Apple did this once before with Apple Watch and there they had full control of both the chipset and the ABI on both sides of the transition, plus they had the forsight to mandate Bitcode submissions for the platform. And watchOS itself precludes doing certain fancy things anyways. So this isn’t really a proven way forwards in this case.
- kevin_thibedeau 6y agoAnything that uses a 32-bit uintptr_t will blow up.