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/work077)] Update ChangeLog.meissner.
Date: Wed,  2 Feb 2022 05:05:10 +0000 (GMT)	[thread overview]
Message-ID: <20220202050510.1D17B3858437@sourceware.org> (raw)

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

commit d43e4059888a4065039f1c76aed07a14b46fd752
Author: Michael Meissner <meissner@linux.ibm.com>
Date:   Wed Feb 2 00:04:45 2022 -0500

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

Diff:
---
 gcc/ChangeLog.meissner | 20 ++++++++++++++------
 1 file changed, 14 insertions(+), 6 deletions(-)

diff --git a/gcc/ChangeLog.meissner b/gcc/ChangeLog.meissner
index 220c077f2af..a6fe73d6f9a 100644
--- a/gcc/ChangeLog.meissner
+++ b/gcc/ChangeLog.meissner
@@ -1,3 +1,16 @@
+work077, patch #3:
+2022-02-01  Michael Meissner  <meissner@the-meissners.org>
+
+	* config.in (TARGET_POWERPC_IEEE_128BIT_LONG_DOUBLE): New
+	configure option.
+	* config/rs6000/rs6000.cc (TARGET_IEEEQUAD_DEFAULT): If the host
+	compiler used IEEE 128-bit long doubles and the long double format
+	was not specified with configuration switches, set the long double
+	format to IEEE 128-bit.
+	* configure.ac (TARGET_POWERPC_IEEE_128BIT_LONG_DOUBLE): Set as 1
+	if the host compiler used IEEE 128-bit long doubles.
+	* configure: Regenerate.
+
 work077, patch #2:
 2022-01-28  Michael Meissner  <meissner@the-meissners.org>
 	PR target/104253
@@ -5,12 +18,7 @@ work077, patch #2:
 	compiler used to build the current compiler defaults to IEEE
 	128-bit long double,  make that the default for this build.
 
-work077, patch #1:
-2022-01-26  Michael Meissner  <meissner@the-meissners.org>
-
-	* config/rs6000/rs6000.cc (TARGET_IEEEQUAD_DEFAULT): If the
-	compiler used to build the current compiler defaults to IEEE
-	128-bit long double,  make that the default for this build.
+work077, patch #1 was reverted:
 
 2022-01-26   Michael Meissner  <meissner@linux.ibm.com>


             reply	other threads:[~2022-02-02  5:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-02  5:05 Michael Meissner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-02-02 18:33 Michael Meissner
2022-01-28 17:39 Michael Meissner
2022-01-27 18:40 Michael Meissner
2022-01-27  4:00 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=20220202050510.1D17B3858437@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).