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/dmf007)] Update ChangeLog.meissner
Date: Thu,  2 Feb 2023 02:59:26 +0000 (GMT)	[thread overview]
Message-ID: <20230202025926.7C20F3858D3C@sourceware.org> (raw)

https://gcc.gnu.org/g:5c95330904db0dd2808c3717d1b4394c06fe7332

commit 5c95330904db0dd2808c3717d1b4394c06fe7332
Author: Michael Meissner <meissner@linux.ibm.com>
Date:   Wed Feb 1 21:59:23 2023 -0500

    Update ChangeLog.meissner

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

diff --git a/gcc/ChangeLog.meissner b/gcc/ChangeLog.meissner
index be0f215b9a5..a62040e495d 100644
--- a/gcc/ChangeLog.meissner
+++ b/gcc/ChangeLog.meissner
@@ -1,5 +1,20 @@
 ==================== dmf007, patch #40 ====================
 
+Update lxvrl test for 32-bit.
+
+2023-02-01   Michael Meissner  <meissner@linux.ibm.com>
+
+gcc/
+
+	* config/rs6000/rs6000-string.c (expand_block_move): Only generate LXVL
+	and STXVL moves on 64-bit, since the pattern is not enabled on 32-bit.
+
+gcc/testsuite/
+
+	* gcc.target/powerpc/lxvrl.c: Restrict test to 64-bit.
+
+==================== dmf007, patch #40 ====================
+
 Bump up precision size to 16 bits.
 
 The new __dmr type that is being added as a possible future PowerPC instruction

             reply	other threads:[~2023-02-02  2:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-02  2:59 Michael Meissner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-02-01 17:35 Michael Meissner
2023-02-01  6:28 Michael Meissner
2023-02-01  3:10 Michael Meissner
2023-01-28  7:14 Michael Meissner
2023-01-28  3:21 Michael Meissner
2023-01-23 21:19 Michael Meissner
2023-01-23 21:19 Michael Meissner
2023-01-23 21:18 Michael Meissner
2023-01-21  3:27 Michael Meissner
2023-01-20 22: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=20230202025926.7C20F3858D3C@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).