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/work146-vsubreg)] Update ChangeLog.*
Date: Sun, 19 Nov 2023 05:47:36 +0000 (GMT)	[thread overview]
Message-ID: <20231119054736.3870B3858D32@sourceware.org> (raw)

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

commit be7a2f0432425f5ed9b17d07216dc4f4a6951c02
Author: Michael Meissner <meissner@linux.ibm.com>
Date:   Sun Nov 19 00:47:32 2023 -0500

    Update ChangeLog.*

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

diff --git a/gcc/ChangeLog.vsubreg b/gcc/ChangeLog.vsubreg
index a4c9e1cc749..70e5079a969 100644
--- a/gcc/ChangeLog.vsubreg
+++ b/gcc/ChangeLog.vsubreg
@@ -1,3 +1,17 @@
+==================== Branch work146-vsubreg, patch #405 (vsize patches #304) ====================
+
+Work on vector pair extracts.
+
+2023-11-19  Michael Meissner  <meissner@linux.ibm.com>
+
+gcc/
+
+	* config/rs6000/vector-pair.md (vec_extract<mode><vpair_element_l>):
+	Rewrite.
+	(vec_extractv8sf): New insn.
+	* config/rs6000/vsx.md (vsx_extract_v4df): Delete.
+	(vsx_extract_v8sf): Delete.
+
 ==================== Branch work146-vsubreg, patch #404 (vsize patches #303) ====================
 
 Add set/extract support on vector pairs with double word elements.

             reply	other threads:[~2023-11-19  5:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-19  5:47 Michael Meissner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-11-19 17:26 Michael Meissner
2023-11-18 23:00 Michael Meissner
2023-11-18 18:26 Michael Meissner
2023-11-18  3:06 Michael Meissner
2023-11-18  2:51 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=20231119054736.3870B3858D32@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).