public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "linkw 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: Tue, 30 May 2023 08:11:47 +0000 [thread overview] Message-ID: <bug-110011-4-W365fiElR5@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 #6 from Kewen Lin <linkw at gcc dot gnu.org> --- btw, one simple fix is under testing: diff --git a/gcc/config/rs6000/rs6000.cc b/gcc/config/rs6000/rs6000.cc index 3f129ea37d2..330c6a6fa5f 100644 --- a/gcc/config/rs6000/rs6000.cc +++ b/gcc/config/rs6000/rs6000.cc @@ -17314,7 +17314,7 @@ output_toc (FILE *file, rtx x, int labelno, machine_mode mode) if (DECIMAL_FLOAT_MODE_P (GET_MODE (x))) REAL_VALUE_TO_TARGET_DECIMAL128 (*CONST_DOUBLE_REAL_VALUE (x), k); else - REAL_VALUE_TO_TARGET_LONG_DOUBLE (*CONST_DOUBLE_REAL_VALUE (x), k); + real_to_target (k, CONST_DOUBLE_REAL_VALUE (x), GET_MODE (x)); if (TARGET_64BIT) {
next prev parent reply other threads:[~2023-05-30 8:11 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 [this message] 2023-06-12 6:10 ` cvs-commit at gcc dot gnu.org 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-W365fiElR5@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).