https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108085
--- Comment #5 from Andrew Pinski ---
The difference between the two front-ends is at the original.
The C++ front-end adds a BLOCK around the loop while the C front-end does not.
This difference changes where the ASAN_MARK is placed with respec
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108085
--- Comment #4 from Andrew Pinski ---
Hmm, using the C++ front-end, the use-after-scope still happens at -O3 but not
with the C front-end.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108085
Martin Liška changed:
What|Removed |Added
Assignee|marxin at gcc dot gnu.org |unassigned at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108085
--- Comment #3 from Martin Liška ---
Created attachment 54153
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54153&action=edit
pr108085.c.216t.uncprop1.dot.svg
So no, it's a real issue where we optimize out .ASAN_CHECK (6, &f, 4, 8); in
t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108085
--- Comment #2 from Richard Biener ---
I bet we unroll the loop and then elide f[] at -O3.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108085
Martin Liška changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |marxin at gcc dot
gnu.org
Last
