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: Fri, 1 Apr 2022 22:19:24 +0000 (GMT) [thread overview] Message-ID: <20220401221924.46B6A3858418@sourceware.org> (raw) https://gcc.gnu.org/g:982211f6a06ff1050f05394f8d5ace85f0b15fa8 commit 982211f6a06ff1050f05394f8d5ace85f0b15fa8 Author: Michael Meissner <meissner@linux.ibm.com> Date: Fri Apr 1 18:18:54 2022 -0400 Update ChangeLog.meissner. 2022-04-01 Michael Meissner <meissner@linux.ibm.com> gcc/ * ChangeLog.meissner: Update. Diff: --- gcc/ChangeLog.meissner | 24 ++++++++++++++++++++++++ 1 file changed, 24 insertions(+) diff --git a/gcc/ChangeLog.meissner b/gcc/ChangeLog.meissner index c7e98861615..e6ad03fd49c 100644 --- a/gcc/ChangeLog.meissner +++ b/gcc/ChangeLog.meissner @@ -1,3 +1,27 @@ +==================== Work084, patch #5: + +Add zero_extendditi2. Improve lxvr*x code generation. + +This pattern adds zero_extendditi2 so that if we are extending DImode to +TImode, and we want the result in a vector register, the compiler can +generate MTVSRDDD. + +In addition the patterns for generating lxvr{b,h,w,d}x and stxvr{b,h,w,d}x +were tuned to allow loading to gpr registers and storing from gpr +registers. This prevents needlessly doing direct moves to get the value +into the vector registers if the gpr register was already selected. + +2022-04-01 Michael Meissner <meissner@linux.ibm.com> + +gcc/ + * config/rs6000/vsx.md (vsx_lxvr<wd>x): Add support for loading to + GPR registers. + (vsx_stxvr<wd>x): Add support for storing from GPR registers. + (zero_extendditi2): New insn. + +gcc/testsuite/ + * gcc.target/powerpc/zero-extend-di-ti.c: New test. + ==================== Work084, patch #4: Add zero_extendditi2.
next reply other threads:[~2022-04-01 22:19 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-01 22:19 Michael Meissner [this message] -- strict thread matches above, loose matches on Subject: below -- 2022-04-05 18:46 Michael Meissner 2022-04-02 0:50 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=20220401221924.46B6A3858418@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).