I'll take "sloppy" over "unstable, lacking direction, and full of feature creep" any day.https://twitter.com/hashbreaker/status/667845317325361152 …
-
-
Replying to @RichFelker
@RichFelker Lots of the flaws are just inherent in the niche. Optimizing compilers combined with a pervasively unsafe low-level language.2 replies 1 retweet 1 like -
Replying to @CopperheadOS
@RichFelker There's the option of using -fwrapv, -fno-strict-aliasing and various subsets of UBSan to get a saner version of the language.2 replies 0 retweets 0 likes -
Replying to @CopperheadOS
@CopperheadSec There is nothing "sane" about writing code that contains aliasing. It DOES NOT HAPPEN unless you do utterly idiotic things.1 reply 0 retweets 0 likes -
Replying to @RichFelker
@RichFelker It's easy to fall into the trap of doing something like using uint8_t instead of char and breaking the aliasing rules.2 replies 0 retweets 0 likes -
Replying to @CopperheadOS
@CopperheadSec The vast majority of programs should not even access reprs at all, except implicitly via memcpy. Neither uint8_t nor uchar.1 reply 0 retweets 0 likes -
Replying to @RichFelker
@RichFelker That's probably true, but it's really done everywhere. It's not sane to compile real world code without -fno-strict-aliasing.2 replies 0 retweets 0 likes
@CopperheadSec You must be using some utterly awful code. My take: it's not sane to be compiling that code to begin with.
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.