-fjunk-in-trunc is the best flag I've seen proposed in a while.
-
Show this thread
-
1 reply 0 retweets 5 likesShow this thread
-
Also, I totally called it. My review 3/26: "This is the class of optimizations that I would call "formally allowed by the standard, but extremely likely to break things and surprise people." Which isn't to say that we shouldn't do it, just ... be prepared."
3 replies 1 retweet 12 likesShow this thread -
Replying to @stephentyrone
I'm surprised anyone relied on the behavior of this overflow even before there were more optimizations. Also surprised that someone who “never actually used the sanitizers […]” is allowed to suggest new UB-exploiting optimizations.
2 replies 0 retweets 2 likes -
Replying to @volatile_void @stephentyrone
“For any UB that LLVM exploits for optimization, an LLVM sanitizer detects it” was never really true (strict aliasing), but it would be nice if it was a conscious near-invariant of the platform instead of an afterthought.
2 replies 0 retweets 3 likes
Obviously the ones covered by ASan and TSan too... They're all near impossible to trap on any efficient implementation.
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.