https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91859
Jason Merrill changed:
What|Removed |Added
Target Milestone|--- |11.2
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91859
--- Comment #8 from CVS Commits ---
The releases/gcc-11 branch has been updated by Jason Merrill
:
https://gcc.gnu.org/g:ee3edeb01eca1cc8d7ebe777b4adb333f0c1118a
commit r11-8495-gee3edeb01eca1cc8d7ebe777b4adb333f0c1118a
Author: Jason Merrill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91859
--- Comment #7 from CVS Commits ---
The master branch has been updated by Jason Merrill :
https://gcc.gnu.org/g:cf2b7020ee8e9745ede527b0a3b2e0ffbafd492b
commit r12-1145-gcf2b7020ee8e9745ede527b0a3b2e0ffbafd492b
Author: Jason Merrill
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91859
--- Comment #6 from Jonathan Wakely ---
Yes, but those optimizations are just doing what they are designed to do. I
suspect that the bug is due to the front end inserting a CLOBBER that says it's
ok for those optimizations to do that.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91859
--- Comment #5 from Joseph C. Sible ---
The real problem mentioned in comment 2 still happens as of GCC 11.1. I've
narrowed it down somewhat to the optimization flags "-Og -ftree-dse
-ftree-pta". Removing any one of those will make it behave
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91859
Jonathan Wakely changed:
What|Removed |Added
CC||jason at gcc dot gnu.org
