https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101520
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2021-07-19
Component|other |testsuite
Status|UNCONFIRMED |NEW
Ever confirmed|0 |1
--- Comment #1 from Martin Sebor <msebor at gcc dot gnu.org> ---
The test uses a loop to write into consecutive bytes of a char variable. The
loop vectorizer turns it into a series of assignments of vector(16) char each,
which the warning then points out. A simple fix for the test is
straightforward: suppress the warning.
A better solution to this class of problems is to constrain the loop unroller
and/or vectorizer to prevent emitting more stores than fit in the destination.
