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 05:58:44 +0000 (GMT)	[thread overview]
Message-ID: <20220729055844.62BDD385840A@sourceware.org> (raw)

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

commit c5e2fff182fe86c0fa19985e1b1998b3447b988c
Author: Michael Meissner <meissner@linux.ibm.com>
Date:   Fri Jul 29 01:57:43 2022 -0400

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

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

diff --git a/gcc/ChangeLog.meissner b/gcc/ChangeLog.meissner
index 6a6baccb60f..70efe3d3163 100644
--- a/gcc/ChangeLog.meissner
+++ b/gcc/ChangeLog.meissner
@@ -1,5 +1,60 @@
 ==================== work095, patch #14.
 
+Make __float128 and __ibm128 use different types from long double.
+
+2022-07-29   Michael Meissner  <meissner@linux.ibm.com>
+
+gcc/
+
+	* config/rs6000/rs6000-builtin.cc (rs6000_init_builtins): Always
+	create a new tree node for __ibm128, even if long double uses the IBM
+	128-bit format.  Always create a new tree node for __float128, even if
+	long double uses the IEEE 128-bit format.
+	* config/rs6000/rs600.cc (rs6000_expand_builtin): Remove code that
+	converted the KFmode and IFmode built-in functions to TFmode depending
+	on what the long double format is, and use built-in overloading
+	instead.
+	(init_float128_ieee): Remove setting up KFmode complex multiply and
+	divide here.
+	(rs6000_init_libfuncs): Rewrite the setup for complex multiply and
+	divide for long double if long double uses the IEEE 128-bit encoding.
+	(rs6000_scalar_mode_supported_p): Allow __ibm128 even if we don't
+	support _Float128.
+	(rs6000_libgcc_floating_mode_supported_p): Allow KFmode if IEEE
+	128-bit floating point is supported.  Allow IFmode if either IEEE
+	128-bit floating point is supported or long double is IBM 128-bit.
+	(rs6000_floatn_mode): Always return KFmode for IEEE 128-bit.  Do not
+	return TFmode, even if long double uses the IEEE 128-bit format.
+	(rs6000_c_mode_for_suffix): The 'q' suffix always uses KFmode, even if
+	long double uses the IEEE 128-bit encoding.
+	* config/rs6000/rs6000.md (IFKF): Delete.
+	(IFKF_reg): Delete.
+	(trunckfif2): New insn.
+	(trunctfif2): Likewise.
+	(extendkftf2_internal): Split extend<mode>tf2_internal and
+	extendtf<mode>2_internal into separate insns that handle either
+	conversions between IEEE 128-bit types or between IBM 128-bit types.
+	Set the type and insn length correctly.
+	(extendtfkf2_internal): Likewise.
+	(extendiftf2_internal): Likewise.
+	(extendtfif2_internal): Likewise.
+
+gcc/testsuite/
+
+	* gcc.target/powerpc/mulkc3-2.c: Update test.
+	* gcc.target/powerpc/divkc3-2.c: Likewise.
+
+libgcc/
+
+	* config/rs6000/float128-ifunc.c (__multc3_ieee128): Add ifunc
+	support.
+	(__divtc3_ieee128): Likewise.
+	* config/rs6000/quad-float128.h (__multc3_ieee128): Add
+        declaration.
+        (__divtc3_ieee128): Likewise.
+
+==================== work095, patch #14.
+
 Allow __ibm128 even if IEEE 128-bit floating point is not supported.
 
 This set of patches fixes places in the compiler where it was assumed to use


             reply	other threads:[~2022-07-29  5:58 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-29  5:58 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  1:57 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=20220729055844.62BDD385840A@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).