[Bug target/110011] -mfull-toc (-mfp-in-toc) yields incorrect _Float128 constants on power9

["cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>]

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

--- Comment #11 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-11 branch has been updated by Kewen Lin <linkw@gcc.gnu.org>:

https://gcc.gnu.org/g:bccc9960eb728bfd890c9388593bd166efcd0591

commit r11-10865-gbccc9960eb728bfd890c9388593bd166efcd0591
Author: Kewen Lin <linkw@linux.ibm.com>
Date:   Mon Jun 12 01:07:52 2023 -0500

    rs6000: Don't use TFmode for 128 bits fp constant in toc [PR110011]

    As PR110011 shows, when encoding 128 bits fp constant into
    toc, we adopts REAL_VALUE_TO_TARGET_LONG_DOUBLE which is
    to find the first float mode with LONG_DOUBLE_TYPE_SIZE
    bits of precision, it would be TFmode here.  But the 128
    bits fp constant can be with mode IFmode or KFmode, which
    doesn't necessarily have the same underlying float format
    as the one of TFmode, like this PR exposes, with option
    -mabi=ibmlongdouble TFmode has ibm_extended_format while
    KFmode has ieee_quad_format, mixing up the formats (the
    encoding/decoding ways) would cause unexpected results.

    This patch is to make it use constant's own mode instead
    of TFmode for real_to_target call.

            PR target/110011

    gcc/ChangeLog:

            * config/rs6000/rs6000.c (output_toc): Use the mode of the 128-bit
            floating constant itself for real_to_target call.

    gcc/testsuite/ChangeLog:

            * gcc.target/powerpc/pr110011.c: New test.

    (cherry picked from commit 388809f2afde874180da0669c669e241037eeba0)