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/work097)] Update ChangeLog.meissner.
Date: Fri, 12 Aug 2022 21:19:08 +0000 (GMT)	[thread overview]
Message-ID: <20220812211908.43AFA3858D28@sourceware.org> (raw)

https://gcc.gnu.org/g:37084294aa28e52ee615e2e50ffa441bf45d1b74

commit 37084294aa28e52ee615e2e50ffa441bf45d1b74
Author: Michael Meissner <meissner@linux.ibm.com>
Date:   Fri Aug 12 17:18:50 2022 -0400

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

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

diff --git a/gcc/ChangeLog.meissner b/gcc/ChangeLog.meissner
index 4065a6f3848..83ffc0af1f9 100644
--- a/gcc/ChangeLog.meissner
+++ b/gcc/ChangeLog.meissner
@@ -1,3 +1,77 @@
+==================== work097, patch014
+
+Add 'w' suffix for __ibm128 constants.
+
+In the documentation, we mention that 'w' or 'W' can be used as a suffix for
+__ibm128 constants.  We never implemented this.  This patch fixes that.
+
+2022-08-12   Michael Meissner  <meissner@linux.ibm.com>
+
+gcc/
+
+	* config/rs6000/rs6000.cc (rs6000_c_mode_for_suffix): Allow 'w' or 'W'
+	for __ibm128 constants.
+
+gcc/testsuite/
+
+	* gcc.target/powerpc/ibm128-suffix.c: New test.
+
+==================== work097, patch013
+
+Make __float128 use the _Float128 type.
+
+2022-08-12   Michael Meissner  <meissner@linux.ibm.com>
+
+gcc/
+
+	* config/rs6000/rs6000-builtin.cc (rs6000_init_builtins): Always use the
+	_Float128 type for __float128.  Don't use the long double type.
+	* config/rs6000/rs6000.cc (rs6000_libgcc_floating_mode_supported_p):
+	Always use KFmode for Float128 mode.
+	(rs6000_floatn_mode): Likewise.
+	(rs6000_c_mode_for_suffix): Likewise.
+
+==================== work097, patch012
+
+Update switching between KFmode to TFmode and IFmode to TFmode builtins
+
+This patch looks to see if the caller function wants TFmode (when long double is
+IEEE 128-bit) to switch the KFmode built-in functions to TFmode.
+
+It will look to see if the caller functions wants IFmode (when long double is
+IBM 128-bit) to switch the unpackif built-in function to unpacktf.
+
+It will look to see if a TFmode argument is passed (when long double is IBM
+128-bit) to switch the packif built-in function to packtf.
+
+2022-08-12   Michael Meissner  <meissner@linux.ibm.com>
+
+gcc/
+
+	* config/rs6000/rs6000-builtin.cc (rs6000_expand_builtin): Update
+	switching from KFmode/IFmode built-in functions to TFmode built-in
+	functions.
+
+==================== work097, patch011
+
+Add ibm128_operand.
+
+Since we have 2 modes for IBM 128-bit (IFmode and TFmode if long double is IBM
+128-bit), this patch provides a new predicate (ibm128_operand) that allows
+combining a conversion from one mode to another.
+
+2022-08-12   Michael Meissner  <meissner@linux.ibm.com>
+
+gcc/
+
+	* config/rs6000/predicates.md (ibm128_operand): New predicate.
+	* config/rs6000/rs6000.md (extendiftf2_internal): Add GPR registers in
+	case -msoft-float is used.
+	(extendtfif2_internal): Likewise.
+	(unpack<mode>): Use ibm128_operand.
+	(unpack<mode>_dm): Likewise.
+	(unpack<mode>_nodm): Likewise.
+
 ==================== work097, patch010
 
 Update switching between KFmode to TFmode and IFmode to TFmode builtins


             reply	other threads:[~2022-08-12 21:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-12 21:19 Michael Meissner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-08-13  2:16 Michael Meissner
2022-08-12 19:59 Michael Meissner
2022-08-12  4:19 Michael Meissner
2022-08-12  1:12 Michael Meissner
2022-08-11 21:16 Michael Meissner
2022-08-10  7:04 Michael Meissner
2022-08-09 22:32 Michael Meissner
2022-08-09 21:06 Michael Meissner
2022-08-09 20:53 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=20220812211908.43AFA3858D28@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).