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/work144-vsize)] Update ChangeLog.*
Date: Wed, 15 Nov 2023 19:58:39 +0000 (GMT)	[thread overview]
Message-ID: <20231115195839.0C9603858D32@sourceware.org> (raw)

https://gcc.gnu.org/g:4cc4fbec994dcfb54a85f99a528a867ac9c35d0e

commit 4cc4fbec994dcfb54a85f99a528a867ac9c35d0e
Author: Michael Meissner <meissner@linux.ibm.com>
Date:   Wed Nov 15 14:58:35 2023 -0500

    Update ChangeLog.*

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

diff --git a/gcc/ChangeLog.vsize b/gcc/ChangeLog.vsize
index 11c1ad52ade..0950f577225 100644
--- a/gcc/ChangeLog.vsize
+++ b/gcc/ChangeLog.vsize
@@ -1,3 +1,13 @@
+==================== Branch work144-vsize, patch #403 ====================
+
+Add -mvector-size-32 requirement to vector pair move insns
+
+2023-11-15  Michael Meissner  <meissner@linux.ibm.com>
+
+gcc/
+
+	* config/rs6000/vector-pair.md (mov<mode>): Add -mvector-size-32 check.
+
 ==================== Branch work144-vsize, patch #402 ====================
 
 Require -mvector-size-32 for vector pair init, extract, and set.

             reply	other threads:[~2023-11-15 19:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-15 19:58 Michael Meissner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-11-17 16:23 Michael Meissner
2023-11-17  3:46 Michael Meissner
2023-11-17  2:55 Michael Meissner
2023-11-16 22:38 Michael Meissner
2023-11-16 22:23 Michael Meissner
2023-11-16 22:02 Michael Meissner
2023-11-16 20:16 Michael Meissner
2023-11-16 17:47 Michael Meissner
2023-11-16  7:17 Michael Meissner
2023-11-16  3:15 Michael Meissner
2023-11-16  0:43 Michael Meissner
2023-11-15 19:35 Michael Meissner
2023-11-15 18:35 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=20231115195839.0C9603858D32@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).