https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108177
--- Comment #6 from CVS Commits ---
The releases/gcc-12 branch has been updated by Stam Markianos-Wright
:
https://gcc.gnu.org/g:bb113a56e31159f4fbe26cc06ee25e4972ce74b5
commit r12-9610-gbb113a56e31159f4fbe26cc06ee25e4972ce74b5
Author: Andre V
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108177
--- Comment #5 from Stam Markianos-Wright ---
With the fix to MVE auto_inc having gone in as
ddc9b5ee13cd686c8674f92d46045563c06a23ea I have found that this fix keeps the
auto-inc on these predicated stores broken.
It seems to fail in auto_inc_
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108177
--- Comment #4 from CVS Commits ---
The master branch has been updated by Andre Simoes Dias Vieira
:
https://gcc.gnu.org/g:c1093923733a1072a237f112e3239b5ebd88eadd
commit r13-5327-gc1093923733a1072a237f112e3239b5ebd88eadd
Author: Andre Vieira
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108177
--- Comment #3 from avieira at gcc dot gnu.org ---
The architecture describes it as only writing the true-predicated bytes and
leaving the others untouched. I guess reading and writting to the same memory
is the best we can do to 'mimic' that in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108177
--- Comment #2 from Richard Biener ---
I suspect
(insn 10 9 11 2 (set (mem:V16QI (reg/v/f:SI 117 [ pa ]) [0 MEM[(signed char[16]
*)pa_2(D)]+0 S16 A8])
(unspec:V16QI [
(reg/v:V16QI 116 [ a ])
(reg:V16BI 1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108177
--- Comment #1 from avieira at gcc dot gnu.org ---
I noticed that for SVE stores seem to be marked as volatile memory accesses, I
suspect it's because they are represented using masked stores which probably
are by definition volatile (for this re
