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/work134-vsubreg)] Update ChangeLog.vsubreg
Date: Fri, 22 Sep 2023 03:23:28 +0000 (GMT)	[thread overview]
Message-ID: <20230922032328.3D7A93858409@sourceware.org> (raw)

https://gcc.gnu.org/g:393e903139ee1f2377b1bc10564e2961152e715f

commit 393e903139ee1f2377b1bc10564e2961152e715f
Author: Michael Meissner <meissner@linux.ibm.com>
Date:   Thu Sep 21 23:23:25 2023 -0400

    Update ChangeLog.vsubreg

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

diff --git a/gcc/ChangeLog.vsubreg b/gcc/ChangeLog.vsubreg
index d54bfa75550..ffa2c0882c5 100644
--- a/gcc/ChangeLog.vsubreg
+++ b/gcc/ChangeLog.vsubreg
@@ -1,3 +1,19 @@
+==================== Branch work134-vsubreg, patch #204 ====================
+
+Use simplify_gen_subreg instead of generating direct register number.
+
+2023-09-15  Michael Meissner  <meissner@linux.ibm.com>
+
+gcc/
+
+	* config/rs6000/rs6000.cc (split_unary_vector_pair): Use
+	simplify_gen_subreg instead of generating hard registers.
+	(split_binary_vector_pair): Likewise.
+	(split_fma_vector_pair): Likewise.
+	* config/rs6000/vector-pair.md (vpair_zero): Use simplify_gen_subreg
+	instead of generating hard registers.
+	(vpair_get_vector_<vp_pmode>): Likewise.
+
 ==================== Branch work134-vsubreg, patch #203 ====================
 
 Peter's patch for updating tieable support.

             reply	other threads:[~2023-09-22  3:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-22  3:23 Michael Meissner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-09-25 16:45 Michael Meissner
2023-09-22 19:50 Michael Meissner
2023-09-21 20:15 Michael Meissner
2023-09-21 20:02 Michael Meissner
2023-09-21 19:11 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=20230922032328.3D7A93858409@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).