[Bug c/108298] Wrong optimization of volatile access from gcc 11 and beyond

2023-01-05 Thread segher at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108298 --- Comment #5 from Segher Boessenkool --- This is not x86-specific. Like on powerpc64 we get addi 3,3,3 # 11 [c=4 l=4] *addsi3/1 extsw 3,3# 17 [c=4 l=4] extendsidi2/1 blr # 25 [c=4 l=

[Bug c/108298] Wrong optimization of volatile access from gcc 11 and beyond

2023-01-05 Thread segher at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108298 --- Comment #4 from Segher Boessenkool --- But please use PR33053 for that, or open a new PR? Let's keep this one for just this actual bug :-)

[Bug c/108298] Wrong optimization of volatile access from gcc 11 and beyond

2023-01-05 Thread daniel.lundin.mail at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108298 --- Comment #3 from Daniel Lundin --- (In reply to Segher Boessenkool from comment #2) > This is not a dup of 33053 (see PR33053#c5 and PR33053#c6). Reopening, and > confirmed. There should be a read from memory: that is a side effect, it has

[Bug c/108298] Wrong optimization of volatile access from gcc 11 and beyond

2023-01-05 Thread segher at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108298 Segher Boessenkool changed: What|Removed |Added Resolution|DUPLICATE |--- Last reconfirmed|

[Bug c/108298] Wrong optimization of volatile access from gcc 11 and beyond

2023-01-05 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108298 Andrew Pinski changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRME