https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69278
Martin Liška changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69278
--- Comment #11 from Jakub Jelinek ---
Author: jakub
Date: Wed Nov 23 19:51:27 2016
New Revision: 242795
URL: https://gcc.gnu.org/viewcvs?rev=242795&root=gcc&view=rev
Log:
PR sanitizer/69278
* opts.c (parse_sanitizer_options): Fo
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69278
--- Comment #10 from Jakub Jelinek ---
Created attachment 40134
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=40134&action=edit
gcc7-pr69278.patch
Untested fix for that.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69278
--- Comment #9 from Jakub Jelinek ---
You've already changed that behavior in r240491 (but also broke
-fsanitize=undefined at the same time, will fix momentarily).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69278
--- Comment #8 from Martin Liška ---
(In reply to Martin Liška from comment #7)
> Well, the actual difference is that they enabled by default
> -fsanitize-recover=address:
>
> ~/bin/llvm/bin/clang -fsanitize=address /tmp/leak.c ; grep store leak
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69278
--- Comment #7 from Martin Liška ---
Well, the actual difference is that they enabled by default
-fsanitize-recover=address:
~/bin/llvm/bin/clang -fsanitize=address /tmp/leak.c ; grep store leak.s
callq __asan_report_store4_noabort
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69278
--- Comment #6 from Martin Liška ---
Behavior was changed in between clang 3.7.1 and 3.8.1:
https://godbolt.org/g/poL2cY.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69278
--- Comment #5 from Martin Liška ---
(In reply to Jakub Jelinek from comment #4)
> Maybe llvm doesn't care about backwards compatibility, but we do.
Sure, are we going to make a behavior change (and document it) in upcoming
release? If so, I can
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69278
--- Comment #4 from Jakub Jelinek ---
Maybe llvm doesn't care about backwards compatibility, but we do.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69278
--- Comment #3 from Martin Liška ---
I've just verified that clang 3.8.1 emits *_noabort calls with
-fsanitize-recover=all:
$ clang++ -fsanitize=address -fsanitize-recover=all /tmp/leak.c -S ; grep store
leak.s
callq __asan_report_stor
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69278
Andrew Pinski changed:
What|Removed |Added
Target Milestone|7.0 |---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69278
Martin Liška changed:
What|Removed |Added
Target Milestone|--- |7.0
--- Comment #2 from Martin Liška ---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69278
--- Comment #1 from Jakub Jelinek ---
This has been the intentional behavior before when -fsanitize-recover=address
has not been supported. Now it is just a backwards compatibility thing, unless
clang went away and redefined -fsanitize=recover=a
13 matches
Mail list logo
