3 ms·
> That is the official LLVM bitcode, which doesn't mean Apple is using their own internal architecture neutral fork. Where would it live? The bitcode uploaded
by masklinn 10y ago
> That is the official LLVM bitcode, which doesn't mean Apple is using their own internal architecture neutral fork.
Where would it live? The bitcode uploaded to the AppStore is the one produced by the local toolchain, AFAIK there's no evidence that it's a fork with its own custom platform-independent bitcode.
The point of bitcode is that Apple can the compile separate packages for ARM32 and ARM64 devices, can easily drop ARM32, and can eventually migrate Watch software to ARM64 without involving developers (hence bitcode being required for WatchOS and tvOS, but optional for iOS). It also lets them perform higher-level static validation of software, or add new transformation/optimisation passes.
Incidentally, the whole thing is irrelevant because bitcode is an appstore feature, I've found no reference to it being used for MAS.
- pjmlp 10y agoApple toolchain is not the same you download from llvm.org.
- masklinn 10y agoWhich completely misses the point, Apple's toolchain is machine-local, it can be inspected, so can the compiled bitcode package, and in the year since bitcode was released (and mandated for watchOS and tvOS) nobody has reported anything which would distinguish it from LLVM's bitcode. And again the whole discussion is nonsensical considering bitcode is an appstore thing, MAS doesn't use it, it's not a thing on macOS at all.
- pjmlp 10y agoSo you know more than anyone else what is going on Apple walls? I don't, so it makes sense to speculate. Nothing prevents Apple to make the MAS a requirement for thr desktop as well.
- madeofpalk 10y ago> Nothing prevents Apple to make the MAS a requirement for thr desktop as well. Except they haven't because the market and plenty of other realities prevent them from doing this.
- pjmlp 10y agoKeep hoping.
- coldtea 10y ago>So you know more than anyone else what is going on Apple walls? Strawman. He didn't claim that, just that the bitcode out of XCode is the same as that out of LLVM directly. No need for access behind "Apple walls".
- pjmlp 10y agoSo you do have access to whatever might be XCode vNext?
- coldtea 10y agoNot sure what you keep talking about or deflecting. Parents didn't mention some "future" or "behind the walls" Apple technology. They said the current bitcode as produced by the current version of XCode on people's laptops now, is the same as LLVM bitcode. Not sure if that's the case myself (haven't checked) but if so, it has nothing to do with secret access to Apple's future technologies and is easily proven or disproven.
- pjmlp 10y agoParents appear to believe just because it isn't available in XCode installed on their Macs today, Apple will never change it tomorrow. Given that in the past there were features coming to Xcode compilers that only several months later appeared on the open source ones, I don't see why one believes that Apple isn't already preparing something into this direction. Whatever, I don't care about the downvotes, lets see who is right in a couple of months.