matthiasgoergens commented on PR #95: URL: https://github.com/apache/incubator-milagro-crypto-c/pull/95#issuecomment-1451787720
Alas, that doesn't work. You can't work around undefined behaviour like that. There's not guarantee that the compiler treats undefined constructs deterministically. Eg the same construct can give you different results in different parts of your code, or even just when called twice etc. There's also no guarantee the compiler won't eg just remove and ignore your undefined behaviour test. That's totally within what the C spec allows. (Undefined behaviour can even travel backwards in time, so to speak. Undefined behaviour anywhere during the execution of your program releases the compiler from any requirements on any part of your execution.) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
