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/work137-vsubreg)] Update ChangeLog.vsubreg
Date: Fri, 29 Sep 2023 05:48:08 +0000 (GMT)	[thread overview]
Message-ID: <20230929054808.50C6C3858C78@sourceware.org> (raw)

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

commit c28af3d68256a3cd87dfb99f40af6a5d7819ef56
Author: Michael Meissner <meissner@linux.ibm.com>
Date:   Fri Sep 29 01:48:05 2023 -0400

    Update ChangeLog.vsubreg

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

diff --git a/gcc/ChangeLog.vsubreg b/gcc/ChangeLog.vsubreg
index 91e23f4125a..290012e9990 100644
--- a/gcc/ChangeLog.vsubreg
+++ b/gcc/ChangeLog.vsubreg
@@ -1,5 +1,35 @@
+==================== Branch work137-vsubreg, patch #400 ====================
+
+Peter's patches for subreg support.
+
+2023-09-21  Peter Bergner  <bergner@linux.ibm.com>
+
+gcc/
+
+	PR target/109116
+	* gcc/config/rs6000/rs6000.cc (rs6000_modes_tieable_p): Make OOmdoe
+	tieable with 128-bit vector modes.
+
+2023-09-15  Peter Bergner  <bergner@linux.ibm.com>
+
+gcc/
+
+	PR target/109116
+	* gcc/config/rs6000/mma.md (vsx_disassemble_pair): Use SUBREG's instead
+	of UNSPEC's.
+	(mma_disassemble_acc): Likewise.
+
 ==================== Branch work137-vsubreg, baseline ====================
 
+Add ChangeLog.vsubreg and update REVISION.
+
+2023-09-29  Michael Meissner  <meissner@linux.ibm.com>
+
+gcc/
+
+	* ChangeLog.vsubreg: New file for branch.
+	* REVISION: Update.
+
 2023-09-29   Michael Meissner  <meissner@linux.ibm.com>
 
 	Clone branch

             reply	other threads:[~2023-09-29  5:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-29  5:48 Michael Meissner [this message]
2023-09-29  6:20 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=20230929054808.50C6C3858C78@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).