http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60275
--- Comment #6 from Jakub Jelinek jakub at gcc dot gnu.org ---
Author: jakub
Date: Wed Apr 23 08:20:12 2014
New Revision: 209672
URL: http://gcc.gnu.org/viewcvs?rev=209672root=gccview=rev
Log:
PR sanitizer/60275
* common.opt
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60275
Jakub Jelinek jakub at gcc dot gnu.org changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60275
--- Comment #5 from Jakub Jelinek jakub at gcc dot gnu.org ---
Created attachment 32597
-- http://gcc.gnu.org/bugzilla/attachment.cgi?id=32597action=edit
gcc410-pr60275.patch
Untested fix. Marek, sorry for hacking this up, but I'd like to
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60275
--- Comment #4 from Tobias Burnus burnus at gcc dot gnu.org ---
(In reply to Jakub Jelinek from comment #3)
I guess we shouldn't copy the design mistakes clang makes. What action to
take on detected undefined behavior should be orthogonal to
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60275
--- Comment #3 from Jakub Jelinek jakub at gcc dot gnu.org ---
I guess we shouldn't copy the design mistakes clang makes. What action to take
on detected undefined behavior should be orthogonal to how to report it
(runtime error message with
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60275
--- Comment #2 from Tobias Burnus burnus at gcc dot gnu.org ---
Post script: CLANG has:
'-fsanitize=undefined' not allowed with '-fsanitize-undefined-trap-on-error'
And regarding the function call: With -fno-sanitize-recover one simply appends
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60275
Marek Polacek mpolacek at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
