@DrPizza you've invented -fno-strict-aliasing
-
-
Replying to @whitequark
@whitequark at least, I don't think? But still, even if -fno-strict-aliasing were mandated in the standard, would that be bad?1 reply 0 retweets 0 likes -
Replying to @DrPizza
@DrPizza@whitequark Yes. GCC should rename -fno-strict-aliasing to -fno-vectorization so people stop repeating this mistake.3 replies 0 retweets 0 likes -
Replying to @RichFelker
@RichFelker@whitequark if I want vectorization I have SIMD intrinsics.1 reply 0 retweets 0 likes -
Replying to @DrPizza
@DrPizza@whitequark Uhg. The whole purpose of optimizing compilers is to keep people from writing asm or equivalent monstrosities.2 replies 0 retweets 0 likes -
Replying to @RichFelker
@RichFelker@whitequark I think "not creating bugs induced by weird and unexpected standard behaviour" is a bigger priority.1 reply 0 retweets 0 likes -
Replying to @DrPizza
@DrPizza@RichFelker C is not a language made for you. The goals of WG14 do not align with your goals. What's left to discuss?3 replies 0 retweets 0 likes -
Replying to @whitequark
@whitequark@RichFelker We all have to live on an Internet written with C programs.1 reply 0 retweets 0 likes -
Replying to @DrPizza
@DrPizza@RichFelker no. we don't. and you know what? even if gcc reverts to 2.95, this will not appreciably...2 replies 0 retweets 0 likes -
Replying to @whitequark
@whitequark@RichFelker we don't? How do I avoid crap C bugs in code that I didn't write?2 replies 0 retweets 0 likes
@DrPizza @whitequark Take advantage of all the great tools like UBSan, tis-interpreter, etc. that depend on UB being UB to do their thing.
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.