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: Wed, 23 Mar 2022 01:29:13 +0000 (GMT) [thread overview] Message-ID: <20220323012913.64F8E3858401@sourceware.org> (raw) https://gcc.gnu.org/g:107cdf9c04e9b81539aa7661bcdae63afa671c1d commit 107cdf9c04e9b81539aa7661bcdae63afa671c1d Author: Michael Meissner <meissner@linux.ibm.com> Date: Tue Mar 22 21:28:53 2022 -0400 Update ChangeLog.meissner. 2022-03-22 Michael Meissner <meissner@linux.ibm.com> gcc/ * ChangeLog.meissner: Update. Diff: --- gcc/ChangeLog.meissner | 21 +++++++++++++++++++-- 1 file changed, 19 insertions(+), 2 deletions(-) diff --git a/gcc/ChangeLog.meissner b/gcc/ChangeLog.meissner index c79a5a5e387..53691a0dc53 100644 --- a/gcc/ChangeLog.meissner +++ b/gcc/ChangeLog.meissner @@ -1,3 +1,20 @@ +==================== Work082, patch #5: +Generate vadduqm and vsubuqm for TImode add/subtract + +If the TImode variable is in an Altivec register instead of a GPR +register, then generate vadduqm and vsubuqm instead of having to move the +value to the GPR registers and doing the add and subtract with carry +instructions. To do this, we have to delay the splitting of the addition +and subtraction until after register allocation. + +2022-03-22 Michael Meissner <meissner@linux.ibm.com> + +gcc/ + * config/rs6000/rs6000.md (addti3): Generate vadduqm if we are + using the Altivec registers. + (subti3): Generate vsubuqm if we using the Altivec registers. + (negti3): New insn. + ==================== Work082, patch #4: Optimize multiply/add of DImode extended to TImode. @@ -47,10 +64,10 @@ instructions. In order to support recognizing the multiply and add combination, we need to keep the addti3 and subti3 as complete insns through the combiner phase. -2022-03-18 Michael Meissner <meissner@linux.ibm.com> +2022-03-22 Michael Meissner <meissner@linux.ibm.com> gcc/ - * config/rs6000/rs6000.md (addti3): Don't immediate expand the + * config/rs6000/rs6000.md (addti3): Don't immediately expand the insn, delay expansion until the split passes. (subti3): Likewise.
next reply other threads:[~2022-03-23 1:29 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-23 1:29 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 16:53 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-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=20220323012913.64F8E3858401@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).