@cmuratori @nothings @LiaSae Clang is usually even more aggressive than GCC about this kind of stuff. http://people.csail.mit.edu/akcheung/papers/apsys12.html …
-
-
-
@cmuratori@nothings@LiaSae check section 2.1, passage starting with "When compiling with Clang, the result is even more surprising". - Show replies
New conversation -
-
-
@cmuratori@LiaSae More accurately it would appear that relying on undefined behavior is what's causing the serious problems. -
@olson_dan@cmuratori The optimizer is still doing some pretty shady stuff. See what@rygorous linked later: http://people.csail.mit.edu/akcheung/papers/apsys12.html … (2.1) - Show replies
New conversation -
-
-
@cmuratori@nothings@LiaSae you speak veeeeery fast. At best this is "bullshit c undefined behaviors", not really gcc faultThanks. 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.