https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93206
--- Comment #11 from Carl Love ---
Created attachment 47626
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47626&action=edit
311r.dwarf2 file for v4si and the v2di test case
The attached file was generated with the #if in the test program
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93206
--- Comment #10 from Carl Love ---
Created attachment 47625
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47625&action=edit
310r.nothrow for both tests v4si and v2di
The attached file was generated with the #if in the test program set to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93206
--- Comment #9 from Carl Love ---
Created attachment 47624
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47624&action=edit
311r.dwarf2 file for just the v2di test case
The attached file was generated with the #if in the test program set t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93206
--- Comment #8 from Carl Love ---
Created attachment 47623
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47623&action=edit
310r.nothrow for just the __builtin_vec_foo_v2di test case
The attached file was generated with the #if in the test
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93206
--- Comment #7 from Jakub Jelinek ---
Please attach RTL dumps then, at least the one from right before var-tracking
and the var-tracking one.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93206
--- Comment #6 from Bill Schmidt ---
(In reply to Jakub Jelinek from comment #4)
> There is no error, it is a note and if some variable at some point, even
> short one, can't be described using just registers or memory, but needs the
> value of t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93206
--- Comment #5 from Carl Love ---
I am puzzled. When we have both test cases included which are identical other
then the data size, the notes are correct for second test case but not the
first test case. When we remove the first test case, then
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93206
--- Comment #4 from Jakub Jelinek ---
There is no error, it is a note and if some variable at some point, even short
one, can't be described using just registers or memory, but needs the value of
the UNSPEC to describe it, there is no var-trackin
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93206
--- Comment #3 from Carl Love ---
The initial bug report states that the bug moves around depending on the test
case. If the test case only consists of the test for the V2DI case, you get
the error that Bill was specifically stating, i.e. UNSPEC
