[Bug middle-end/108298] Wrong optimization of volatile access from gcc 11 and beyond

2023-01-09 Thread rguenther at suse dot de via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108298

--- Comment #10 from rguenther at suse dot de  ---
On Mon, 9 Jan 2023, segher at gcc dot gnu.org wrote:

> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108298
> 
> --- Comment #9 from Segher Boessenkool  ---
> It cannot be a duplicate: this bug was introduced much later than when
> PR69482 was filed!

It wasn't introduced - the present issue was exposed for this case ;-)

[Bug middle-end/108298] Wrong optimization of volatile access from gcc 11 and beyond

2023-01-09 Thread segher at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108298

--- Comment #9 from Segher Boessenkool  ---
It cannot be a duplicate: this bug was introduced much later than when
PR69482 was filed!

But glad the same patch seems to have fixed both, sure :-)

[Bug middle-end/108298] Wrong optimization of volatile access from gcc 11 and beyond

2023-01-09 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108298

Richard Biener  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #8 from Richard Biener  ---
Yes, and I think it's a duplicate in the end.

*** This bug has been marked as a duplicate of bug 69482 ***

[Bug middle-end/108298] Wrong optimization of volatile access from gcc 11 and beyond

2023-01-06 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108298

--- Comment #7 from Andrew Pinski  ---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69482#c7 addresses the big issue
here I think.

[Bug middle-end/108298] Wrong optimization of volatile access from gcc 11 and beyond

2023-01-06 Thread marxin at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108298

Martin Liška  changed:

   What|Removed |Added

 CC||marxin at gcc dot gnu.org,
   ||rguenth at gcc dot gnu.org

--- Comment #6 from Martin Liška  ---
I think it started with r11-165-geb72dc663e9070b2.