It seems to be a bug in ld tool while checking at assembly object files. It is treating ARM assembly .o files included in static libs as external files. If you create a zero byte file with the file name "libcrypto.a(aes-x86_64.o)" in the same folder of your .a file, it will work.

Can someone from the compiler team comment on the safety of this? I personally have no other choice for now than disabling OpenSSL in my entire project because I can't trust Bitcode to not optimize away time-safety operations in cryptographic libraries.

It would be really insightful to get ANY information about the types of optimizations that will be performed between the code I upload and the one that is distributed. Keep in mind that due to the FairPlay DRM, as a developer, we can't easily read the assembly code of our applications without jailbreaking. That's really a bummer.

More Like This

Retrieving data ...

This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Developer Forums Participation Agreement.