@whitequark @bmastenbrook LLVM or C--
@whitequark @oshepherd @bmastenbrook @johnregehr No, UB wins you the ability to make debug implementations that trap the nonportable usage.
-
-
@RichFelker@whitequark@oshepherd@bmastenbrook@johnregehr I will -O0 a function. The optimizer breaking obvious code is a COMPILER BUG.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@RichFelker@whitequark@oshepherd@bmastenbrook@johnregehr I will happily typecast (volatile) to shut the compiler up, with comment. -
@landley@RichFelker@oshepherd@bmastenbrook@johnregehr volatile NULL dereference is still UB and legal to optimize out -
@whitequark@RichFelker@oshepherd@bmastenbrook@johnregehr Null dereference is segfault at runtime, that's not new breakage. -
@landley@RichFelker@oshepherd@bmastenbrook@johnregehr I mean, volatile accesses will still be optimized, just somewhat less
End of conversation
New conversation -
-
-
@RichFelker@oshepherd@bmastenbrook@johnregehr pretty sure IDB still allows you to do that; an implementation that defines... -
@RichFelker@oshepherd@bmastenbrook@johnregehr all ambiguous behavior as traps is valid & equivalent to -fsanitize
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.