@ch3root @RichFelker It is arbitrary! This is like GCC backtracking on UB from using uninitialized memory between 4.4.3 and 4.4.7, or…
-
-
Replying to @volatile_void
@ch3root@RichFelker backtracking from pointer comparison optimizations since https://lwn.net/Articles/278137/ … . They have no idea what they're doing1 reply 0 retweets 0 likes -
Replying to @volatile_void
@ch3root@RichFelker To them it's a game and benchmarks are the scoring system.1 reply 0 retweets 1 like -
Replying to @volatile_void
@spun_off
@RichFelker Are you saying that aliasing analysis is not needed at all? Go tell it@bmastenbrook.1 reply 0 retweets 1 like -
Replying to @ch3root
@spun_off
@RichFelker Or you have better solution than DR 260? Or what? I'm not sure which direction you are aiming at.1 reply 0 retweets 0 likes -
Replying to @RichFelker
@RichFelker @spun_off There are several issues in DR 260. And I think it was wrong to mix them.1 reply 0 retweets 0 likes -
Replying to @ch3root
@RichFelker @spun_off The part of DR 260 regarding instability of indet values seems to be more or less overrridden by DR 451.1 reply 0 retweets 1 like -
Replying to @ch3root
@RichFelker @spun_off But for the part about pointer provenance DR 260 still seems to be the authoritative source.1 reply 0 retweets 0 likes -
Replying to @ch3root
@RichFelker @spun_off "They may also treat pointers based on different origins as distinct even though they are bitwise identical."2 replies 0 retweets 0 likes
-
-
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.