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/work082)] Update ChangeLog.meissner. Date: Thu, 24 Mar 2022 16:53:25 +0000 (GMT) [thread overview] Message-ID: <20220324165325.04EC53858D3C@sourceware.org> (raw) https://gcc.gnu.org/g:3b1cf8a2aae57953c1a6e6371f598747a4d71dd2 commit 3b1cf8a2aae57953c1a6e6371f598747a4d71dd2 Author: Michael Meissner <meissner@linux.ibm.com> Date: Thu Mar 24 12:53:02 2022 -0400 Update ChangeLog.meissner. 2022-03-23 Michael Meissner <meissner@linux.ibm.com> gcc/ * ChangeLog.meissner: Update. Diff: --- gcc/ChangeLog.meissner | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/gcc/ChangeLog.meissner b/gcc/ChangeLog.meissner index 8cf11cf85b4..9db64884a54 100644 --- a/gcc/ChangeLog.meissner +++ b/gcc/ChangeLog.meissner @@ -1,3 +1,16 @@ +==================== Work082, patch #10: +Improve vsx_extract_<mode> + +In looking at PR target/99293, I noticed that the insn "type" attribute is +incorrect. This patch fixes those attributes. + +2022-03-23 Michael Meissner <meissner@linux.ibm.com> + +gcc/ + PR target/99392 + * config/rs6000/rs6000.md (vsx_extract_<mode>): Use the correct + insn type for the alternatives. + ==================== Work082, patch #9 (reverted): ==================== Work082, patch #8:
next reply other threads:[~2022-03-24 16:53 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-24 16:53 Michael Meissner [this message] -- strict thread matches above, loose matches on Subject: below -- 2022-03-24 18:24 Michael Meissner 2022-03-24 16:55 Michael Meissner 2022-03-24 1:35 Michael Meissner 2022-03-23 23:33 Michael Meissner 2022-03-23 16:56 Michael Meissner 2022-03-23 5:21 Michael Meissner 2022-03-23 1:29 Michael Meissner 2022-03-22 20:10 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=20220324165325.04EC53858D3C@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).