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/work104)] Update ChangeLog.meissner
Date: Tue, 10 Jan 2023 04:20:01 +0000 (GMT)	[thread overview]
Message-ID: <20230110042001.47EAC3858CDA@sourceware.org> (raw)

https://gcc.gnu.org/g:8b0d5796b5d2a13db67f948510fd0cfd2ec0b5a5

commit 8b0d5796b5d2a13db67f948510fd0cfd2ec0b5a5
Author: Michael Meissner <meissner@linux.ibm.com>
Date:   Mon Jan 9 23:19:58 2023 -0500

    Update ChangeLog.meissner

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

diff --git a/gcc/ChangeLog.meissner b/gcc/ChangeLog.meissner
index 74bfbe3c8b6..525dd331b52 100644
--- a/gcc/ChangeLog.meissner
+++ b/gcc/ChangeLog.meissner
@@ -1,3 +1,15 @@
+==================== Patch #25, work104 branch ====================
+
+Tweak setting precision.
+
+2022-01-09   Michael Meissner  <meissner@linux.ibm.com>
+
+	* config/rs6000/rs6000.cc (rs6000_option_override_internal): Make unqiue
+	float128 precision a user switch.
+	* config/rs6000/rs6000.opt (-munique-float128-precision): Likewise.
+	* genmodes.cc (emit_mode_adjustments): Set mode_precision as well as
+	mode_unit_precision.
+
 ==================== Patch #24, work104 branch ====================
 
 Use unique precisions for 128-bit floating point on Fortran.

             reply	other threads:[~2023-01-10  4:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-10  4:20 Michael Meissner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-01-10 20:05 Michael Meissner
2023-01-10  6:02 Michael Meissner
2023-01-09 20:42 Michael Meissner
2023-01-09 19:47 Michael Meissner
2023-01-07  1:35 Michael Meissner
2023-01-07  1:17 Michael Meissner
2023-01-06 23:14 Michael Meissner
2023-01-06 20:10 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=20230110042001.47EAC3858CDA@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).