@pcwalton That's a thing now?
-
-
-
@scottmichaud@pcwalton I think the issue is more with compilers doing optimizations which violate common assumptions about C's semantics. - 21 more replies
New conversation -
-
-
@pcwalton The backlash isn't about optimizing compilers per se, but about creeping semantic shifts to enable new opts that break old code. -
@pcwalton The biggest offender for sure is overzealous UB exploitation (primarily a C/C++ issue), but there are other issues like that. - 12 more replies
New conversation -
-
-
@jamiiecb
@davecheney Sure, but that doesn't mean we don't need optimizations. :)Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@pcwalton it's very much a case of throwing the baby out with the bath water, the problem is not -O, but undefined behaviour. -
@davecheney@pcwalton undefined behaviour which compilers interpret as a licence to kill. They need to pick safety/correctness over speed. - 5 more replies
New conversation -
-
-
@johnregehr have you tried reading unoptimized Rust assembly :) -
@comex@johnregehr Can't be any worse than unoptimized Haskell assembly.
End of conversation
New conversation -
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.