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/work150-vpair)] Update ChangeLog.*
Date: Thu, 14 Dec 2023 22:01:33 +0000 (GMT)	[thread overview]
Message-ID: <20231214220133.474B73858D20@sourceware.org> (raw)

https://gcc.gnu.org/g:6b21ec9de226a21d08ed7856d2ef38c1b584942e

commit 6b21ec9de226a21d08ed7856d2ef38c1b584942e
Author: Michael Meissner <meissner@linux.ibm.com>
Date:   Thu Dec 14 17:01:29 2023 -0500

    Update ChangeLog.*

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

diff --git a/gcc/ChangeLog.vpair b/gcc/ChangeLog.vpair
index 2760a03687f..356c415c631 100644
--- a/gcc/ChangeLog.vpair
+++ b/gcc/ChangeLog.vpair
@@ -1,3 +1,16 @@
+==================== Branch work150-vpair, patch #208 ====================
+
+Check vector pair mode sizes before splitting.
+
+2023-12-14  Michael Meissner  <meissner@linux.ibm.com>
+
+gcc/
+
+	* config/rs6000/rs6000.cc (vpair_split_unary): Make sure vector pair
+	operands are 32 bytes before splitting.
+	(vpair_split_binary): Likewise.
+	(vpair_split_fma): Likewise.
+
 ==================== Branch work150-vpair, patch #207 ====================
 
 Move vpair splits to rs6000.cc; Allow vpair assemble to load constants.

             reply	other threads:[~2023-12-14 22:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-14 22:01 Michael Meissner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-12-21 17:47 Michael Meissner
2023-12-21  7:15 Michael Meissner
2023-12-21  6:19 Michael Meissner
2023-12-15  6:43 Michael Meissner
2023-12-14 19:22 Michael Meissner
2023-12-14 17:44 Michael Meissner
2023-12-14  5:23 Michael Meissner
2023-12-13 20:33 Michael Meissner
2023-12-13 20:05 Michael Meissner
2023-12-13 19:56 Michael Meissner
2023-12-13  7:22 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=20231214220133.474B73858D20@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).