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/work095)] Update ChangeLog.meissner.
Date: Fri, 29 Jul 2022 01:57:21 +0000 (GMT)	[thread overview]
Message-ID: <20220729015721.18567385840A@sourceware.org> (raw)

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

commit f515799a03ac3a93e8a8a8b2b5e9f896c9b22378
Author: Michael Meissner <meissner@linux.ibm.com>
Date:   Thu Jul 28 21:57:02 2022 -0400

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

Diff:
---
 gcc/ChangeLog.meissner | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/gcc/ChangeLog.meissner b/gcc/ChangeLog.meissner
index 25213466458..6a6baccb60f 100644
--- a/gcc/ChangeLog.meissner
+++ b/gcc/ChangeLog.meissner
@@ -1,9 +1,11 @@
 ==================== work095, patch #14.
 
-Make __float128 and __ibm128 use different types from long double.
+Allow __ibm128 even if IEEE 128-bit floating point is not supported.
 
-This set of patches goes through to allow the use of __ibm128 if we don't have
-IEEE 128-bit support enabled, but long double uses the IBM 128-bit support.
+This set of patches fixes places in the compiler where it was assumed to use
+__ibm128 we needed to have IEEE 128-bit support enabled.  A future patch will
+implement the change to create the __ibm128 type if either we have IEEE 128-bit
+floating point enabled, or the long double type is IBM 128-bit floating point.
 
 2022-07-28   Michael Meissner  <meissner@linux.ibm.com>


             reply	other threads:[~2022-07-29  1:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-29  1:57 Michael Meissner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-07-30  2:18 Michael Meissner
2022-07-30  1:34 Michael Meissner
2022-07-30  1:30 Michael Meissner
2022-07-29 19:30 Michael Meissner
2022-07-29 17:57 Michael Meissner
2022-07-29  5:58 Michael Meissner
2022-07-29  1:47 Michael Meissner
2022-07-28 22:58 Michael Meissner
2022-07-28 22:31 Michael Meissner
2022-07-28 20:59 Michael Meissner
2022-07-23  0:12 Michael Meissner
2022-07-22 18:57 Michael Meissner
2022-07-21 21:50 Michael Meissner
2022-07-18 19:41 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=20220729015721.18567385840A@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).