public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/110011] -mfull-toc (-mfp-in-toc) yields incorrect _Float128 constants on power9 Date: Mon, 12 Jun 2023 06:10:45 +0000 [thread overview] Message-ID: <bug-110011-4-laoONHVk4q@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110011-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110011 --- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Kewen Lin <linkw@gcc.gnu.org>: https://gcc.gnu.org/g:388809f2afde874180da0669c669e241037eeba0 commit r14-1703-g388809f2afde874180da0669c669e241037eeba0 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.cc (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.
next prev parent reply other threads:[~2023-06-12 6:10 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-28 0:32 [Bug target/110011] New: -mfull-toc " vincent-gcc at vinc17 dot net 2023-05-28 3:41 ` [Bug target/110011] -mfull-toc (-mfp-in-toc) " pinskia at gcc dot gnu.org 2023-05-28 3:54 ` pinskia at gcc dot gnu.org 2023-05-30 6:47 ` linkw at gcc dot gnu.org 2023-05-30 7:51 ` vincent-gcc at vinc17 dot net 2023-05-30 8:09 ` linkw at gcc dot gnu.org 2023-05-30 8:11 ` linkw at gcc dot gnu.org 2023-06-12 6:10 ` cvs-commit at gcc dot gnu.org [this message] 2023-06-19 9:29 ` cvs-commit at gcc dot gnu.org 2023-06-20 3:20 ` cvs-commit at gcc dot gnu.org 2023-06-20 3:21 ` cvs-commit at gcc dot gnu.org 2023-06-20 8:24 ` cvs-commit at gcc dot gnu.org 2023-06-20 8:27 ` LpSolit at gmail dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-110011-4-laoONHVk4q@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).