[Bug target/99921] PowerPC xxeval has the wrong predicates

[meissner at gcc dot gnu.org via Gcc-bugs]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99921

Michael Meissner  changed:

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
 Resolution|--- |FIXED

--- Comment #3 from Michael Meissner  ---
Fixed on August 13th on the trunk.

[Bug target/99921] PowerPC xxeval has the wrong predicates

[cvs-commit at gcc dot gnu.org via Gcc-bugs]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99921

--- Comment #2 from CVS Commits  ---
The master branch has been updated by Michael Meissner :

https://gcc.gnu.org/g:58eec9908c01e2f5a6eb9cd76bbf037bbe2cf5e6

commit r12-2905-g58eec9908c01e2f5a6eb9cd76bbf037bbe2cf5e6
Author: Michael Meissner 
Date:   Fri Aug 13 19:43:27 2021 -0400

Fix xxeval predicates (PR 99921).

I noticed that the xxeval built-in function used the
altivec_register_operand
predicate.  Since it takes vsx registers, this might force the register
allocate to issue a move when it could use a traditional floating point
register.  This patch fixes that.

2021-08-13  Michael Meissner  

gcc/
PR target/99921
* config/rs6000/altivec.md (xxeval): Use register_predicate
instead of altivec_register_predicate.

[Bug target/99921] PowerPC xxeval has the wrong predicates

[meissner at gcc dot gnu.org via Gcc-bugs]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99921

Michael Meissner  changed:

   What|Removed |Added

   Last reconfirmed||2021-05-04
   Assignee|unassigned at gcc dot gnu.org  |meissner at gcc dot 
gnu.org
 Ever confirmed|0   |1
 Status|UNCONFIRMED |ASSIGNED

--- Comment #1 from Michael Meissner  ---
I have patches for this and I will submit it when I get back from surgery.  If
somebody else wants to fix it earlier, go ahead.