https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94655
Martin Sebor changed:
What|Removed |Added
Status|RESOLVED|NEW
Resolution|DUPLICATE
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94655
Jeffrey A. Law changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94655
--- Comment #5 from Martin Sebor ---
We want stores by user code to be diagnosed based on strict language rules
(e.g., accessing a member via a reference to another member). To do that we
either have to teach the middle end to avoid taking
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94655
--- Comment #4 from Jakub Jelinek ---
I don't see how it makes a difference between whether it is a store created by
the vectorizer or some original user store.
What matters is what ADDR_EXPR picks up SCCVN for the base, and it will pick up
the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94655
--- Comment #3 from Martin Sebor ---
Using the base object in the MEM_REF instead of the member when accessing
another member should certainly fix it.
Another option might be to somehow mark up these synthesized stores (e.g., by
setting some
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94655
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94655
Martin Liška changed:
What|Removed |Added
Known to work||9.3.0
Last reconfirmed|
