https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104698
Michael Meissner changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104698
--- Comment #5 from Peter Bergner ---
Mike, are we doing backports of this? ...or can we marked this as FIXED?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104698
--- Comment #4 from CVS Commits ---
The master branch has been updated by Michael Meissner :
https://gcc.gnu.org/g:1301d7f647c7ac40da7f910aa6e790205e34bb8b
commit r12-7501-g1301d7f647c7ac40da7f910aa6e790205e34bb8b
Author: Michael Meissner
Dat
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104698
--- Comment #3 from Michael Meissner ---
It goes beyond 'just use RTL'.
The problem is the code only generates an altivec instruction. So if the
__int128_t value is in a GPR, the compiler will need to do a move to the vector
registers (1 insn)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104698
Segher Boessenkool changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104698
--- Comment #1 from Segher Boessenkool ---
GCC should not use unspecs for any basic operations like this. *That* is
the problem.
