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/dmf001)] Update ChangeLog.meissner. Date: Thu, 13 Oct 2022 17:59:49 +0000 (GMT) [thread overview] Message-ID: <20221013175949.14C083858C55@sourceware.org> (raw) https://gcc.gnu.org/g:a9c17cd40b87e8d69d20d998353af861a781a1d9 commit a9c17cd40b87e8d69d20d998353af861a781a1d9 Author: Michael Meissner <meissner@linux.ibm.com> Date: Thu Oct 13 13:59:34 2022 -0400 Update ChangeLog.meissner. 2022-10-13 Michael Meissner <meissner@linux.ibm.com> gcc/ * ChangeLog.meissner: Update. Diff: --- gcc/ChangeLog.meissner | 35 +++++++++++++++++++++++++++++++++++ 1 file changed, 35 insertions(+) diff --git a/gcc/ChangeLog.meissner b/gcc/ChangeLog.meissner index 3157bf1aedd..eb51fd476f3 100644 --- a/gcc/ChangeLog.meissner +++ b/gcc/ChangeLog.meissner @@ -1,3 +1,38 @@ +==================== dmf001, patch #9 + +Use MMA instruction instead of the renamed DMF instruction. + +2022-10-13 Michael Meissner <meissner@linux.ibm.com> + +gcc/ + + * config/rs6000/mma.md (vvi4i4i8_dmf): Delete. + (avvi4i4i8_dmf): Likewise. + (vvi4i4i2_dmf): Likewise. + (avvi4i4i2_dmf): Likewise. + (vvi4i4_dmf): Likewise. + (avvi4i4_dmf): Likewise. + (pvi4i2_dmf): Likewise. + (apvi4i2_dmf): Likewise. + (vvi4i4i4_dmf): Likewise. + (avvi4i4i4_dmf): Likewise. + (mma_<vv>): Use MMA instruction instead of the renamed DMF + instruction. + (mma_<avv>): Likewise. + (mma_<pv>): Likewise. + (mma_<apv>): Likewise. + (mma_<vvi4i4i8>): Likewise. + (mma_<avvi4i4i8>): Likewise. + (mma_<vvi4i4i2>): Likewise. + (mma_<avvi4i4i2>): Likewise. + (mma_<vvi4i4>): Likewise. + (mma_<avvi4i4>): Likewise. + (mma_<pvi4i2>): Likewise. + (mma_<apvi4i2>): Likewise. + (mma_<vvi4i4i4>): Likewise. + (mma_<avvi4i4i4>): Likewise. + * config/rs6000/rs6000.cc (print_operand): Rework %A error message. + ==================== dmf001, patch #8 Switch to DMF syntax and DMR for all MMA operations.
next reply other threads:[~2022-10-13 17:59 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-13 17:59 Michael Meissner [this message] -- strict thread matches above, loose matches on Subject: below -- 2022-10-27 5:17 Michael Meissner 2022-10-27 3:37 Michael Meissner 2022-10-20 6:06 Michael Meissner 2022-10-20 4:11 Michael Meissner 2022-10-19 4:16 Michael Meissner 2022-10-19 3:53 Michael Meissner 2022-10-19 3:46 Michael Meissner 2022-10-18 22:36 Michael Meissner 2022-10-18 22:26 Michael Meissner 2022-10-17 23:18 Michael Meissner 2022-10-15 0:12 Michael Meissner 2022-10-15 0:06 Michael Meissner 2022-10-14 17:36 Michael Meissner 2022-10-12 2:33 Michael Meissner 2022-10-11 23:19 Michael Meissner 2022-10-11 16:02 Michael Meissner 2022-10-10 21:52 Michael Meissner 2022-10-10 21:52 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=20221013175949.14C083858C55@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).