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/work093)] Update ChangeLog.meissner.
Date: Wed,  6 Jul 2022 21:15:26 +0000 (GMT)	[thread overview]
Message-ID: <20220706211526.10E893858C39@sourceware.org> (raw)

https://gcc.gnu.org/g:7dc7cf283eff4692e395df5773cafbd25fe9cac6

commit 7dc7cf283eff4692e395df5773cafbd25fe9cac6
Author: Michael Meissner <meissner@linux.ibm.com>
Date:   Wed Jul 6 17:15:07 2022 -0400

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

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

diff --git a/gcc/ChangeLog.meissner b/gcc/ChangeLog.meissner
index a093e556f47..0a81518ea91 100644
--- a/gcc/ChangeLog.meissner
+++ b/gcc/ChangeLog.meissner
@@ -1,3 +1,45 @@
+==================== work093, patch #7
+
+__float128 and __ibm128 always gets different internal types.
+
+2022-07-06   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.
+	(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/rs600.cc (reg_offset_addressing_ok_p): Allow
+	IFmode to use offset addresses.
+	(init_float128_ibm): Remove checks for hardware floating point for
+	the IBM 128-bit comparisons.
+	(init_float128_ieee): Do not create __mulkc3 and __divkc3 since
+	__float128 always creates these functions.
+	(rs6000_init_libfuncs): Create complex multiply and divide for
+	long double if long double uses the IEEE 128-bit encoding.
+	(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.
+
+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.
+
 ==================== work093, patch #6
 
 Overload IEEE 128-bit test data built-in functions.


             reply	other threads:[~2022-07-06 21:15 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-06 21:15 Michael Meissner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-07-12  2:52 Michael Meissner
2022-07-12  1:37 Michael Meissner
2022-07-08 20:02 Michael Meissner
2022-07-08  2:27 Michael Meissner
2022-07-07 23:39 Michael Meissner
2022-07-07 21:08 Michael Meissner
2022-07-07 20:22 Michael Meissner
2022-07-07 16:32 Michael Meissner
2022-07-07  4:40 Michael Meissner
2022-07-06 22:15 Michael Meissner
2022-07-01  7:26 Michael Meissner
2022-07-01  6:48 Michael Meissner
2022-06-30 20:28 Michael Meissner
2022-06-30 19:22 Michael Meissner
2022-06-30 19:18 Michael Meissner
2022-06-30 17:43 Michael Meissner
2022-06-30 15:22 Michael Meissner
2022-06-30  6:01 Michael Meissner
2022-06-30  4:30 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=20220706211526.10E893858C39@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).