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.* Date: Fri, 21 Apr 2023 02:57:53 +0000 (GMT) [thread overview] Message-ID: <20230421025753.2826F3858D37@sourceware.org> (raw) https://gcc.gnu.org/g:29b454a5acd53d82628cbcc42dd5fba0b2c22cf6 commit 29b454a5acd53d82628cbcc42dd5fba0b2c22cf6 Author: Michael Meissner <meissner@linux.ibm.com> Date: Thu Apr 20 22:57:49 2023 -0400 Update ChangeLog.* Diff: --- gcc/ChangeLog.meissner | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/gcc/ChangeLog.meissner b/gcc/ChangeLog.meissner index 925b88c03e2..29c73d701dd 100644 --- a/gcc/ChangeLog.meissner +++ b/gcc/ChangeLog.meissner @@ -1,3 +1,15 @@ +==================== Branch work119, patch #47 ==================== + +Allow vec_extract with variable element number to load vector registers. + +2023-04-20 Michael Meissner <meissner@linux.ibm.com> + +gcc/ + + * config/rs6000/vsx.md (vsx_extract_<mode>_var_load): Allow vec_extract + of integer types with a variable element number to load into vector + registers. Allow splitting before register allocation. + ==================== Branch work119, patch #46 ==================== Combine variable element vec_extract of V4SF with DF convert.
next reply other threads:[~2023-04-21 2:57 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-21 2:57 Michael Meissner [this message] -- strict thread matches above, loose matches on Subject: below -- 2023-04-24 23:01 Michael Meissner 2023-04-22 0:58 Michael Meissner 2023-04-21 23:33 Michael Meissner 2023-04-21 23:08 Michael Meissner 2023-04-21 23:06 Michael Meissner 2023-04-21 22:02 Michael Meissner 2023-04-21 15:23 Michael Meissner 2023-04-21 4:23 Michael Meissner 2023-04-20 20:48 Michael Meissner 2023-04-20 19:42 Michael Meissner 2023-04-19 22:09 Michael Meissner 2023-04-18 22:16 Michael Meissner 2023-04-18 5:45 Michael Meissner 2023-04-17 20:02 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=20230421025753.2826F3858D37@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).