http://llvm.org/bugs/show_bug.cgi?id=18095
Mathieu Desnoyers <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID |--- --- Comment #3 from Mathieu Desnoyers <[email protected]> --- Have you guys considered perhaps emitting a warning when clang finds such an undefined behavior ? This would have the advantage of both carrying the optimization when undefined behaviors are detected (performance) and making sure existing code that worked fine on gcc and previous llvm versions don't end up crashing in front of application end-users without warning to the developer (robustness). Thanks for the pointers, Mathieu -- You are receiving this mail because: You are on the CC list for the bug.
_______________________________________________ LLVMbugs mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/llvmbugs
