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/work119)] Update ChangeLog.meissner
Date: Wed, 26 Apr 2023 15:47:17 +0000 (GMT)	[thread overview]
Message-ID: <20230426154717.16E003858D1E@sourceware.org> (raw)

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

commit f64caf896d2a371ef77510d4837e3be99925b76a
Author: Michael Meissner <meissner@linux.ibm.com>
Date:   Wed Apr 26 11:47:13 2023 -0400

    Update ChangeLog.meissner

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

diff --git a/gcc/ChangeLog.meissner b/gcc/ChangeLog.meissner
index 8254b9027f2..16c9a116edc 100644
--- a/gcc/ChangeLog.meissner
+++ b/gcc/ChangeLog.meissner
@@ -6,7 +6,7 @@ This patch allows vec_extract of V4SI, V8HI, and V16QI vector types with a
 variable element number to be loaded with sign or zero extension, and GCC will
 not generate a separate zero/sign extension instruction.
 
-2023-04-25   Michael Meissner  <meissner@linux.ibm.com>
+2023-04-26   Michael Meissner  <meissner@linux.ibm.com>
 
 gcc/
 
@@ -28,7 +28,7 @@ This patch allows vec_extract of V4SI, V8HI, and V16QI vector types with a
 variable element number to be loaded into vector registers directly.  It also
 will be split before register allocation.
 
-2023-04-25   Michael Meissner  <meissner@linux.ibm.com>
+2023-04-26   Michael Meissner  <meissner@linux.ibm.com>
 
 gcc/
 
@@ -43,7 +43,7 @@ This patch allows vec_extract of V4SI, V8HI, and V16QI vector types with a
 constant element number to be zero extended.  It also allows vec_extract of V4SI
 and V8HI vector types with constant element number to be sign extended.
 
-2023-04-25   Michael Meissner  <meissner@linux.ibm.com>
+2023-04-26   Michael Meissner  <meissner@linux.ibm.com>
 
 gcc/

             reply	other threads:[~2023-04-26 15:47 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-26 15:47 Michael Meissner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-05-01 17:24 Michael Meissner
2023-04-29  4:10 Michael Meissner
2023-04-28 19:48 Michael Meissner
2023-04-28  6:37 Michael Meissner
2023-04-28  3:44 Michael Meissner
2023-04-28  3:37 Michael Meissner
2023-04-26 23:55 Michael Meissner
2023-04-26 23:44 Michael Meissner
2023-04-26 16:21 Michael Meissner
2023-04-26  5:14 Michael Meissner
2023-04-25 15:56 Michael Meissner
2023-04-25  2:55 Michael Meissner
2023-04-25  2:04 Michael Meissner
2023-04-25  2:03 Michael Meissner
2023-04-21 19:01 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=20230426154717.16E003858D1E@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).