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/work089)] Update ChangeLog.meissner. Date: Thu, 12 May 2022 22:31:18 +0000 (GMT) [thread overview] Message-ID: <20220512223118.82A663858427@sourceware.org> (raw) https://gcc.gnu.org/g:27908e2efc13f7b8e47c02f0413d57d167c98d2f commit 27908e2efc13f7b8e47c02f0413d57d167c98d2f Author: Michael Meissner <meissner@linux.ibm.com> Date: Thu May 12 18:30:59 2022 -0400 Update ChangeLog.meissner. 2022-05-12 Michael Meissner <meissner@linux.ibm.com> gcc/ * ChangeLog.meissner: Update. Diff: --- gcc/ChangeLog.meissner | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) diff --git a/gcc/ChangeLog.meissner b/gcc/ChangeLog.meissner index f4f767e8e14..0e1adbcaee4 100644 --- a/gcc/ChangeLog.meissner +++ b/gcc/ChangeLog.meissner @@ -1,3 +1,22 @@ +==================== work089 patch #4 + +Delay splitting addti3/subti3 until first split pass. + +This patch makes addti3 and subti3 be define_insn_and_split instead of +define_expand. This patch will be a building block to support in a future +patch PR target/103109 which wants to optimize 128-bit some integer +multiply-add combinations to use the power9 maddld, maddhd, maddhdu +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-05-12 Michael Meissner <meissner@linux.ibm.com> + +gcc/ + * config/rs6000/rs6000.md (addti3): Don't immediately expand the + insn. Delay expansion until the split passes. + (subti3): Likewise. + ==================== work089 patch #3 Replace UNSPEC with RTL code for extendditi2.
next reply other threads:[~2022-05-12 22:31 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-12 22:31 Michael Meissner [this message] -- strict thread matches above, loose matches on Subject: below -- 2022-05-12 22:56 Michael Meissner 2022-05-12 22:47 Michael Meissner 2022-05-12 22:22 Michael Meissner 2022-05-12 20:53 Michael Meissner 2022-05-11 17:19 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=20220512223118.82A663858427@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).