https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107497
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2022-11-01
Host|powerpc64-linux-gnu, |powerpc64-linux-gnu,
|powerpc64le-linux-gnu |powerpc64le-linux-gnu
| |x86_64-linux-gnu
Target|powerpc64-linux-gnu, |powerpc64-linux-gnu,
|powerpc64le-linux-gnu |powerpc64le-linux-gnu
| |x86_64-linux-gnu
Ever confirmed|0 |1
Build|powerpc64-linux-gnu, |powerpc64-linux-gnu,
|powerpc64le-linux-gnu |powerpc64le-linux-gnu
| |x86_64-linux-gnu
Status|UNCONFIRMED |NEW
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Looks like it also fails on x86_64:
https://gcc.gnu.org/pipermail/gcc-testresults/2022-November/771026.html
https://gcc.gnu.org/pipermail/gcc-testresults/2022-November/771027.html
I suspect building with mpfr/mpc/gmp in the source tree is definitely a good
test of the compiler, especially with floating point too :).