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: Tue,  2 Aug 2022 21:34:01 +0000 (GMT)	[thread overview]
Message-ID: <20220802213401.42D523858031@sourceware.org> (raw)

https://gcc.gnu.org/g:0fcc54d9ac7f9d532dcda14b1319e2380b780859

commit 0fcc54d9ac7f9d532dcda14b1319e2380b780859
Author: Michael Meissner <meissner@linux.ibm.com>
Date:   Tue Aug 2 17:33:38 2022 -0400

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

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

diff --git a/gcc/ChangeLog.meissner b/gcc/ChangeLog.meissner
index cdbcb06498b..0ff42d6d4d4 100644
--- a/gcc/ChangeLog.meissner
+++ b/gcc/ChangeLog.meissner
@@ -1,3 +1,59 @@
+==================== work096, patch 9.
+
+Use _Float128 type for __float128.
+
+In the past if the long double type was IEEE 128-bit, the __float128 type would
+use the long double type, and TFmode would be used for the mode for both
+_Float128 and long double types.
+
+This patch always uses the _Float128 type for __float128, and it always uses
+KFmode for the mode.  Right now, a similar change for __ibm128 has not been
+made.
+
+In making these changes, I noticed that there was an internal tree for holding
+the __float128 type.  This code removes that internal tree variable.
+
+2022-08-02   Michael Meissner  <meissner@linux.ibm.com>
+
+gcc/
+
+	* config/rs6000/rs6000-builtin.cc (rs6000_type_string): Use
+	float128_type_node, not ieee128_float_type_mode.
+	(rs6000_init_builtins): Always use the _Float128 type for the __float128
+	keyword.
+	(rs6000_expand_builtin): Remove code that mapped the KFmode built-in
+	functions to TFmode functions if long double was IEEE 128-bit, and use
+	built-in function overloading instead.  Also remove the conversion of
+	IBM 128-bit built-in functions from IFmode to TFmode if long double is
+	IBM 128-bit.
+	* config/rs6000/rs6000-c.cc (rs6000_target_modify_macros): Use
+	float128_type_node, not ieee128_float_type_mode.
+	(rs6000_cpu_cpp_builtins): Delete ieee128_float_type_mode.
+	(is_float128_p): Delete.
+	(rs6000_builtin_type_compatible): Don't consider 128-bit floating point
+	types to be compatible if they use the same encoding.  Use built-in
+	function overloading instead.
+	(rs6000_libgcc_floating_mode_supported_p): Use KFmode for _Float128 and
+	__float128, not TFmode.
+	(rs6000_floatn_mode): Likewise.
+	(rs6000_c_mode_for_suffix): Likewise.
+	* config/rs6000/rs6000.h (RS6000_BTI_ieee128_float): Delete.
+	(ieee128_float_type_node): Likewise.
+	* config/rs6000/rs6000.md (IFKF): Delete.
+	(IFKF_reg): Delete.
+	(extendkfif2): New define_expand.
+	(trunckfif2): New define_expand.
+	(extend<mode>tf2_internal): Split into extendiftf2_internal and
+	extendkftf2_internal.  Update the insns to use the correct insn type and
+	length attributes based on whether KFmode or IFmode is used.
+	(extendiftf2_internal): Likewise.
+	(extendkftf2_internal): Likewise.
+	(extendtf<mode>2_internal): Split into extendtfif2_internal and
+	extendtfkf2_internal.  Update the insns to use the correct insn type and
+	length attributes based on whether KFmode or IFmode is used.
+	(extendtfif2_internal): Likewise.
+	(extendtfkf2_internal): Likewise.
+
 ==================== work096, patch 8.
 
 Rework 128-bit complex multiply and divide.


             reply	other threads:[~2022-08-02 21:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-02 21:34 Michael Meissner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-08-04 22:50 Michael Meissner
2022-08-03 15:36 Michael Meissner
2022-08-03 15:14 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=20220802213401.42D523858031@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).