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/work121)] Update ChangeLog.meissner Date: Sat, 3 Jun 2023 04:07:31 +0000 (GMT) [thread overview] Message-ID: <20230603040731.1A1983858D38@sourceware.org> (raw) https://gcc.gnu.org/g:9ad58bc668ccff75ffc89cf6a18aabeadced6dbe commit 9ad58bc668ccff75ffc89cf6a18aabeadced6dbe Author: Michael Meissner <meissner@linux.ibm.com> Date: Sat Jun 3 00:07:28 2023 -0400 Update ChangeLog.meissner Diff: --- gcc/ChangeLog.meissner | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/gcc/ChangeLog.meissner b/gcc/ChangeLog.meissner index fe59d9cd0a9..b047e0712b2 100644 --- a/gcc/ChangeLog.meissner +++ b/gcc/ChangeLog.meissner @@ -17,7 +17,7 @@ Given the vector shift instructions only look at the bottom 5 or 6 bits of the shift value, we can load the constant via VSPLTISW or XXSPLTIB instructions and eliminate the sign extend instructions (VEXTSW2D, VEXTSB2D, and VEXTSB2W). -2023-06-02 Michael Meissner <meissner@linux.ibm.com> +2023-06-03 Michael Meissner <meissner@linux.ibm.com> gcc/ @@ -34,6 +34,7 @@ gcc/testsuite/ PR target/89213 * gcc.target/powerpc/pr89213.c: New test. + * gcc.target/powerpc/vec-rlmi-rlnm.c: Update insn count. ==================== Branch work121, patch #37 ====================
next reply other threads:[~2023-06-03 4:07 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-03 4:07 Michael Meissner [this message] -- strict thread matches above, loose matches on Subject: below -- 2023-06-02 19:14 Michael Meissner 2023-06-02 4:15 Michael Meissner 2023-05-18 5:13 Michael Meissner 2023-05-17 21:26 Michael Meissner 2023-05-15 23:31 Michael Meissner 2023-05-12 16:56 Michael Meissner 2023-05-12 16:51 Michael Meissner 2023-05-12 16:51 Michael Meissner 2023-05-12 16:50 Michael Meissner 2023-05-09 20:45 Michael Meissner 2023-05-08 23:55 Michael Meissner 2023-05-08 23:46 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=20230603040731.1A1983858D38@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: linkBe 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).