Disclosure: In October 2021 after 10 years working at Apple I left to join Microsoft, so I’m not totally unbiased. I love the sentiment this article is expressing, and anecdotally the thesis holds in my experience:…
Interesting that the two highest functions in that trace relate to Bitcode serialization and GlobalISel. Why is Swift serializing Bitcode if it is also running ISEL in the same compile?
The bitcode used for watchOS is not stable. There’s a special ABI for watchOS that uses 32-bit pointers on 64-bit hardware to make the IR representation stable, but the bitcode itself is still version locked to the…
Disclosure: In October 2021 after 10 years working at Apple I left to join Microsoft, so I’m not totally unbiased. I love the sentiment this article is expressing, and anecdotally the thesis holds in my experience:…
Interesting that the two highest functions in that trace relate to Bitcode serialization and GlobalISel. Why is Swift serializing Bitcode if it is also running ISEL in the same compile?
The bitcode used for watchOS is not stable. There’s a special ABI for watchOS that uses 32-bit pointers on 64-bit hardware to make the IR representation stable, but the bitcode itself is still version locked to the…