[Bug target/104253] libgcc missing __floatdiif
cvs-commit at gcc dot gnu.org
gcc-bugzilla@gcc.gnu.org
Sun Mar 6 01:16:28 GMT 2022
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104253
--- Comment #15 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by Michael Meissner
<meissner@gcc.gnu.org>:
https://gcc.gnu.org/g:b3531eb23a23be0219c6ab0ff85110c2648086e6
commit r10-10487-gb3531eb23a23be0219c6ab0ff85110c2648086e6
Author: Michael Meissner <meissner@linux.ibm.com>
Date: Sat Mar 5 20:14:44 2022 -0500
Use correct names for __ibm128 if long double is IEEE 128-bit.
If you are on a PowerPC system where the default long double is IEEE
128-bit (either through the compiler option -mabi=ieeelongdouble or via
the configure option --with-long-double-format=ieee), GCC used the wrong
names for some of the conversion functions for the __ibm128 type.
Internally, GCC uses IFmode for __ibm128 if long double is IEEE 128-bit,
instead of TFmode when long double is IBM 128-bit. This patch adds the
missing conversions to prevent the 'if' name from being used.
In particular, before the patch, the conversions used were:
IFmode to DImode signed: __fixifdi instead of __fixtfdi
IFmode to DImode unsigned __fixunsifti instead of __fixunstfti
DImode to IFmode signed: __floatdiif instead of __floatditf
DImode to IFmode unsigned: __floatundiif instead of __floatunditf
2022-03-05 Michael Meissner <meissner@the-meissners.org>
gcc/
PR target/104253
* config/rs6000/rs6000.c (init_float128_ibm): Update the
conversion functions used to convert IFmode types. Backport
change made to the master branch on 2022-02-14.
gcc/testsuite/
PR target/104253
* gcc.target/powerpc/pr104253.c: New test. Backport change made
to the master branch on 2022-02-14.
More information about the Gcc-bugs
mailing list