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/work084)] Update ChangeLog.meissner.
Date: Sat,  2 Apr 2022 00:50:58 +0000 (GMT)	[thread overview]
Message-ID: <20220402005058.1110A3858D1E@sourceware.org> (raw)

https://gcc.gnu.org/g:2aea504015b39db038d72e8f6c13842ff6598c44

commit 2aea504015b39db038d72e8f6c13842ff6598c44
Author: Michael Meissner <meissner@linux.ibm.com>
Date:   Fri Apr 1 20:50:41 2022 -0400

    Update ChangeLog.meissner.
    
    2022-04-01   Michael Meissner  <meissner@linux.ibm.com>
    
    gcc/
            * ChangeLog.meissner: Update.

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

diff --git a/gcc/ChangeLog.meissner b/gcc/ChangeLog.meissner
index e6ad03fd49c..452690fe771 100644
--- a/gcc/ChangeLog.meissner
+++ b/gcc/ChangeLog.meissner
@@ -20,6 +20,9 @@ gcc/
 	(zero_extendditi2): New insn.
 
 gcc/testsuite/
+	* gcc.target/powerpc/vsx-load-element-extend-int.c: Use -O2
+	instead of -O0 and update insn counts.
+	* gcc.target/powerpc/vsx-load-element-extend-short.c: Likewise.
 	* gcc.target/powerpc/zero-extend-di-ti.c: New test.
 
 ==================== Work084, patch #4:


             reply	other threads:[~2022-04-02  0:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-02  0:50 Michael Meissner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-04-05 18:46 Michael Meissner
2022-04-01 22:19 Michael Meissner
2022-03-31 19:55 Michael Meissner
2022-03-31 16:34 Michael Meissner
2022-03-31 14:01 Michael Meissner
2022-03-31 14:00 Michael Meissner
2022-03-31 14:00 Michael Meissner
2022-03-31 14:00 Michael Meissner
2022-03-30 18:01 Michael Meissner
2022-03-29 23:57 Michael Meissner
2022-03-29  3:06 Michael Meissner
2022-03-29  0:12 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=20220402005058.1110A3858D1E@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).