WG14: C pointer values are explicitly *not* simple bit patterns; they can well be path-dependent http://www.open-std.org/JTC1/SC22/WG14/www/docs/n2012.htm#clarifying-the-c-memory-object-model-pointer-provenance …
@DrPizza @whitequark Uhg. The whole purpose of optimizing compilers is to keep people from writing asm or equivalent monstrosities.
-
-
@RichFelker@whitequark I think "not creating bugs induced by weird and unexpected standard behaviour" is a bigger priority. -
@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? -
@whitequark@RichFelker We all have to live on an Internet written with C programs. -
@DrPizza@RichFelker no. we don't. and you know what? even if gcc reverts to 2.95, this will not appreciably... -
@DrPizza@RichFelker increase the correctness of Internet-of-crappy-C. The only solution is to kill C. -
@whitequark@RichFelker that seems even less likely than reforming C to me. -
@DrPizza@RichFelker nah. not really. the Internet is in protocols, not endpoint implementations. we've changed those before. -
@DrPizza@RichFelker we have a memory-safe browser layout engine now, I don't see any reason that can't work for everything else. - 1 more reply
New conversation -
-
-
@RichFelker@whitequark it's (demonstrably) hard enough to write bug-free code without the compiler subverting our intentions. -
@DrPizza@whitequark It's pretty easy to write code that doesn't access memory using the wrong types. Just don't write bogus casts.
End of conversation
New conversation -
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.