https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93206
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
note: non-delegitimized UNSPEC
is just a debugging note solely in non-release checking builds. Not all
UNSPECs need to be delegitimized, it is just a hint that it is something that
could be inspected, whether it can be easily delegitimized or not (see
rs6000_delegitimize_address).
As UNSPEC_FOO is not in upstream GCC, I fail to see the need for upstream PR.
Anyway, I have to wonder why vsx.md uses so many UNSPECs, can't e.g.
UNSPEC_VSX_SET be just using vec_merge of vec_duplicate of the scalar operand
(what is inserted) and the vector operand, with the position as last operand?
Is the reason the endian correction?
