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: Tue, 12 Jul 2022 01:37:23 +0000 (GMT)	[thread overview]
Message-ID: <20220712013723.EE683382FDD2@sourceware.org> (raw)

https://gcc.gnu.org/g:40652cac7e725c3dfdb54ca871ac4043d125e470

commit 40652cac7e725c3dfdb54ca871ac4043d125e470
Author: Michael Meissner <meissner@linux.ibm.com>
Date:   Mon Jul 11 21:36:57 2022 -0400

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

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

diff --git a/gcc/ChangeLog.meissner b/gcc/ChangeLog.meissner
index 7eb6a381596..20e65871084 100644
--- a/gcc/ChangeLog.meissner
+++ b/gcc/ChangeLog.meissner
@@ -1,3 +1,25 @@
+==================== work093, patch #16
+
+Make __ibm128 support work on older machines.
+
+2022-07-08   Michael Meissner  <meissner@linux.ibm.com>
+
+gcc/
+
+	* config/rs6000/rs600.md (IFKF): Delete.
+	(IFKF_reg): Delete.
+	(extendiftf2): Allow __ibm128 on older systems.
+	(extendtfif2): Likewise.
+	(trunciftf2): Likewise.
+	(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.
+
 ==================== work093, patch #15 (reverted)
 
 ==================== work093, patch #14


             reply	other threads:[~2022-07-12  1:37 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-12  1:37 Michael Meissner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-07-12  2:52 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-06 21: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=20220712013723.EE683382FDD2@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).