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: Thu, 28 Jul 2022 22:31:43 +0000 (GMT)	[thread overview]
Message-ID: <20220728223143.621D938582A4@sourceware.org> (raw)

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

commit 0b82940fb9e538c650d7905562637a42b6688743
Author: Michael Meissner <meissner@linux.ibm.com>
Date:   Thu Jul 28 18:31:22 2022 -0400

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

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

diff --git a/gcc/ChangeLog.meissner b/gcc/ChangeLog.meissner
index 4983749b0a5..e559837a29f 100644
--- a/gcc/ChangeLog.meissner
+++ b/gcc/ChangeLog.meissner
@@ -1,3 +1,37 @@
+==================== work095, patch #12.
+
+Enable using overload built-ins for 128-bit floating point.
+
+2022-07-28   Michael Meissner  <meissner@linux.ibm.com>
+
+gcc/
+
+	* config/rs6000/rs6000-builtin.cc (rs6000_expand_builtin): Remove all
+	of the code that changed KFmode built-in functions into TFmode, since
+	these functions now support overloading between KFmode and TFmode.
+	* config/rs6000/rs6000-c.cc (rs6000_builtin_type_compatible):
+	Don't consider _Float128 and long double under
+	-mabi=ieeelongdouble to be compatible for built-in functions.  Use
+	overloading instead.
+	* config/rs6000/rs6000.md (IFKF): Delete.
+	(IFKF_reg): Delete.
+	(@extenddf<mode>2_fprs): Remove extra test for
+	TARGET_LONG_DOUBLE_128.
+	(@extenddf<mode2>_vsx): Likewise.
+	(extendiftf2): Allow __ibm128 even if _Float128 is not supported.
+	(extendkfif2): New insn.
+	(extendtfkf2): Allow __ibm128 even if _Float128 is not supported.
+	(extendtfif2): Likewise.
+	(trunckfif2): New insn.
+	(trunctfif2): Allow __ibm128 even if _Float128 is not supported.
+	(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.
+
 ==================== work095, patch #11.
 
 Make __float128 and __ibm128 use different types from long double.


             reply	other threads:[~2022-07-28 22:31 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-28 22:31 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  5:58 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 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=20220728223143.621D938582A4@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).