public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Michael Meissner <meissner@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc(refs/users/meissner/heads/work096)] Mangle __ibm128 to u8__ibm128.
Date: Wed,  3 Aug 2022 15:35:27 +0000 (GMT)	[thread overview]
Message-ID: <20220803153527.132E43858413@sourceware.org> (raw)

https://gcc.gnu.org/g:15da4be5576ba170253355cd59c7be9b15862ae3

commit 15da4be5576ba170253355cd59c7be9b15862ae3
Author: Michael Meissner <meissner@linux.ibm.com>
Date:   Wed Aug 3 11:35:05 2022 -0400

    Mangle __ibm128 to u8__ibm128.
    
    With the change to __ibm128 having a distinct type within GCC, we need to adjust
    the mangling for __ibm128 to distinguish it from long double, when long double
    uses the IBM 128-bit encoding.
    
    2022-08-03   Michael Meissner  <meissner@linux.ibm.com>
    
    gcc/
    
            * config/rs6000/rs6000.cc (rs6000_mangle_type): Mangle __ibm128 to
            u8__ibm128 if long double uses the IBM 128-bit encoding.

Diff:
---
 gcc/config/rs6000/rs6000.cc | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/gcc/config/rs6000/rs6000.cc b/gcc/config/rs6000/rs6000.cc
index 9066bbe8850..9d79fc0bb69 100644
--- a/gcc/config/rs6000/rs6000.cc
+++ b/gcc/config/rs6000/rs6000.cc
@@ -20068,6 +20068,11 @@ rs6000_mangle_type (const_tree type)
   if (type == bool_int_type_node) return "U6__booli";
   if (type == bool_long_long_type_node) return "U6__boolx";
 
+  /* If long double uses the IBM 128-bit extended format, we need to
+     distinguish between __ibm128 and long double.  */
+  if (type == ibm128_float_type_node && FLOAT128_IBM_P (TFmode))
+    return "u8__ibm128";
+
   if (SCALAR_FLOAT_TYPE_P (type) && FLOAT128_IBM_P (TYPE_MODE (type)))
     return "g";
   if (SCALAR_FLOAT_TYPE_P (type) && FLOAT128_IEEE_P (TYPE_MODE (type)))


                 reply	other threads:[~2022-08-03 15:35 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20220803153527.132E43858413@sourceware.org \
    --to=meissner@gcc.gnu.org \
    --cc=gcc-cvs@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: link
Be 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).