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/work085)] Update ChangeLog.meissner. Date: Thu, 14 Apr 2022 20:19:21 +0000 (GMT) [thread overview] Message-ID: <20220414201921.EC9623858C2C@sourceware.org> (raw) https://gcc.gnu.org/g:053c68d9cb8422460874ab6daaf110c4b42e1126 commit 053c68d9cb8422460874ab6daaf110c4b42e1126 Author: Michael Meissner <meissner@linux.ibm.com> Date: Thu Apr 14 16:19:03 2022 -0400 Update ChangeLog.meissner. 2022-04-14 Michael Meissner <meissner@linux.ibm.com> gcc/ * ChangeLog.meissner: Update. Diff: --- gcc/ChangeLog.meissner | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/gcc/ChangeLog.meissner b/gcc/ChangeLog.meissner index c4fec7b0639..459e8e4e9d1 100644 --- a/gcc/ChangeLog.meissner +++ b/gcc/ChangeLog.meissner @@ -1,3 +1,21 @@ +==================== Work086, patch #9: + +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. + ==================== Work086, patch #8: Eliminate power8 fusion options, use power8 tuning, PR target/102059
next reply other threads:[~2022-04-14 20:19 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-14 20:19 Michael Meissner [this message] -- strict thread matches above, loose matches on Subject: below -- 2022-04-12 18:47 Michael Meissner 2022-04-11 18:14 Michael Meissner 2022-04-11 18:04 Michael Meissner 2022-04-07 22:24 Michael Meissner 2022-04-07 20:24 Michael Meissner 2022-04-06 22:54 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=20220414201921.EC9623858C2C@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).