I agree with this. C and C++ would be better without UB. http://www.yodaiken.com/wp-content/uploads/2018/05/ub-1.pdf …
-
-
Replying to @filpizlo
I was thinking about this yesterday, but the hard question is what should out of bounds writes be specified to do? What about UAF? I don't see how to specify this without ruling out genuine optimizations (which is not to say that many of the dumb UB shouldn't be eliminated).
3 replies 0 retweets 3 likes -
yeah, there are several UBs that are hard to eliminate without changing these languages beyond recognition. this ship sailed long ago. we should focus on new languages but also on C/C++ dialects that don't aim for full back compatibility.
3 replies 2 retweets 8 likes -
Replying to @johnregehr @samth
I don’t think that’s right. The signed math UBs and strict aliasing are just dumb. You don’t need to replace the language to fix those.
3 replies 0 retweets 1 like
You kinda do. Aliasing is not possible to detect locally. Anything using "context pointer" becomes horribly pessimized if the compiler must assume any write through any pointer could modify the context.
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.