Do not use Xcode 11. https://gist.github.com/jedisct1/6787e095ade93703a7f2fde112586102 …https://gist.github.com/jedisct1/8188b1c4aeddd1f5cde84245ddb83c8a …
-
-
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.
-
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.
End of conversation
New conversation -
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.