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: Sat, 15 Oct 2022 00:12:44 +0000 (GMT)	[thread overview]
Message-ID: <20221015001244.B0D683858C52@sourceware.org> (raw)

https://gcc.gnu.org/g:9b86371808ffbc38273c36c8fc99419ef3a14089

commit 9b86371808ffbc38273c36c8fc99419ef3a14089
Author: Michael Meissner <meissner@linux.ibm.com>
Date:   Fri Oct 14 20:12:29 2022 -0400

    Update ChangeLog.meissner.
    
    2022-10-14   Michael Meissner  <meissner@linux.ibm.com>
    
    gcc/
    
            * ChangeLog.meissner: Update.

Diff:
---
 gcc/ChangeLog.meissner | 34 ++++++++++++++++++++++++++++++++++
 1 file changed, 34 insertions(+)

diff --git a/gcc/ChangeLog.meissner b/gcc/ChangeLog.meissner
index 65b9f7e5652..cd0de0e4348 100644
--- a/gcc/ChangeLog.meissner
+++ b/gcc/ChangeLog.meissner
@@ -1,3 +1,37 @@
+==================== dmf001, patch #13
+
+Use DMF names instead of MMF for instructions.
+
+2022-10-14   Michael Meissner  <meissner@linux.ibm.com>
+
+gcc/
+
+	* config/rs6000/mma.md (vvi4i4i8_insn): New int attribute.
+	(avvi4i4i8_insn): Likewise.
+	(vvi4i4i2_insn): Likewise.
+	(avvi4i4i2_insn): Likewise.
+	(vvi4i4_insn): Likewise.
+	(avvi4i4_insn): Likewise.
+	(pvi4i2_insn): Likewise.
+	(apvi4i2_insn): Likewise.
+	(vvi4i4i4_insn): Likewise.
+	(avvi4i4i4_insn): Likewise.
+	(mma_<vv>): On DMF systems, emit the DMF instruction name instead of the
+	MMF instruction name.
+	(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.
+
 ==================== dmf001, patch #12
 
 Document wD constraint.

             reply	other threads:[~2022-10-15  0:12 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-15  0:12 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:06 Michael Meissner
2022-10-14 17:36 Michael Meissner
2022-10-13 17:59 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=20221015001244.B0D683858C52@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: link
Be 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).