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)] Update ChangeLog.meissner.
Date: Wed,  3 Aug 2022 15:36:45 +0000 (GMT)	[thread overview]
Message-ID: <20220803153645.9403338A90B2@sourceware.org> (raw)

https://gcc.gnu.org/g:4c54bfeab72d7a56678ea421cd3a7d1a3002d44d

commit 4c54bfeab72d7a56678ea421cd3a7d1a3002d44d
Author: Michael Meissner <meissner@linux.ibm.com>
Date:   Wed Aug 3 11:36:25 2022 -0400

    Update ChangeLog.meissner.
    
    2022-08-03   Michael Meissner  <meissner@linux.ibm.com>
    
    gcc/
    
            * ChangeLog.meissner: Update.

Diff:
---
 gcc/ChangeLog.meissner | 15 +++++++++++++++
 1 file changed, 15 insertions(+)

diff --git a/gcc/ChangeLog.meissner b/gcc/ChangeLog.meissner
index 78ff9a7dbd5..5cdeae3a44b 100644
--- a/gcc/ChangeLog.meissner
+++ b/gcc/ChangeLog.meissner
@@ -1,3 +1,18 @@
+==================== work096, patch 11.
+
+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.
+
 ==================== work096, patch 10.
 
 Make __ibm128 have a distinct type and always use IFmode.


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

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-03 15:36 Michael Meissner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-08-04 22:50 Michael Meissner
2022-08-03 15:14 Michael Meissner
2022-08-02 21:34 Michael Meissner
2022-08-02 19:35 Michael Meissner
2022-08-02 18:50 Michael Meissner
2022-08-02 18:00 Michael Meissner
2022-08-02  4:26 Michael Meissner
2022-08-02  0:38 Michael Meissner
2022-08-01 22:12 Michael Meissner

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=20220803153645.9403338A90B2@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).