Do not use Xcode 11. https://gist.github.com/jedisct1/6787e095ade93703a7f2fde112586102 …https://gist.github.com/jedisct1/8188b1c4aeddd1f5cde84245ddb83c8a …
-
-
Replying to @jedisct1
What is the implication? Is Xcode insecure, the apps compiled with the bundled compiler or does it make behaviour silently undefined with AVX enabled?
1 reply 0 retweets 0 likes -
Replying to @sehetw
Undefined behavior, leading to crashes for code expecting a properly aligned stack. Maybe related, the AES implementation was reported to produce incorrect output on 32-bit targets. This shows that Xcode 11 didn’t receive much testing before being tagged. Don’t trust it.
1 reply 2 retweets 2 likes -
Replying to @jedisct1
Ooh. Bad codegen on regular AES implementation, that's bad. The sample appeared rather contrived and I wasn't sure any "real code" would trigger it. Thanks for explaining.
1 reply 0 retweets 0 likes
Samples are reduced test cases. Charm and libsodium don’t work any more. Disabling stack checking (enabled by default in Xcode 11) seems to work around it, but still doesn’t give me much confidence in the compiler.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.