From: Carl Love <cel@us.ibm.com>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Cc: cel@us.ibm.com, Will Schmidt <will_schmidt@vnet.ibm.com>,
Ulrich Weigand <Ulrich.Weigand@de.ibm.com>,
Peter Bergner <bergner@linux.ibm.com>
Subject: [PATCH 0//2] PowerPC: MMA+ Outer-Product Instruction name change
Date: Thu, 03 Nov 2022 10:30:20 -0700 [thread overview]
Message-ID: <8cc2a8243ea9515069c067b5d3e40a1335e460f0.camel@us.ibm.com> (raw)
In-Reply-To: <20111d66a467599d893bf85bbdf2e82b76377127.camel@us.ibm.com>
GDB maintainers:
The following patch set updates the mnemonics for the pmxvf16ger*,
pmxvf32ger*,pmxvf64ger*, pmxvi4ger8*, pmxvi8ger4*, pmxvi16ger2*
instructions.
The names were officially changed to: pmdmxvf16ger*, pmdmxvf32ger*,
pmdmxvf64ger*, pmdmxvi4ger8*, pmdmxvi8ger4*,
pmdmxvi16ger* respectively in commit:
commit bb98553cad4e017f1851153fa5de91f2cee98fb2
Author: Peter Bergner <bergner@linux.ibm.com>
Date: Sat Oct 8 16:19:51 2022 -0500
PowerPC: Add support for RFC02658 - MMA+ Outer-Product Instructions
gas/
* config/tc-ppc.c (md_assemble): Only check for prefix opcodes.
* testsuite/gas/ppc/rfc02658.s: New test.
* testsuite/gas/ppc/rfc02658.d: Likewise.
* testsuite/gas/ppc/ppc.exp: Run it.
opcodes/
* ppc-opc.c (XMSK8, P_GERX4_MASK, P_GERX2_MASK, XX3GERX_MASK): New.
(powerpc_opcodes): Add dmxvi8gerx4pp, dmxvi8gerx4, dmxvf16gerx2pp,
dmxvf16gerx2, dmxvbf16gerx2pp, dmxvf16gerx2np, dmxvbf16gerx2,
dmxvi8gerx4spp, dmxvbf16gerx2np, dmxvf16gerx2pn, dmxvbf16gerx2pn,
dmxvf16gerx2nn, dmxvbf16gerx2nn, pmdmxvi8gerx4pp, pmdmxvi8gerx4,
pmdmxvf16gerx2pp, pmdmxvf16gerx2, pmdmxvbf16gerx2pp, pmdmxvf16gerx2np,
pmdmxvbf16gerx2, pmdmxvi8gerx4spp, pmdmxvbf16gerx2np, pmdmxvf16gerx2pn,
pmdmxvbf16gerx2pn, pmdmxvf16gerx2nn, pmdmxvbf16gerx2nn.
The old names are still accepted as extended mnemonics by the
assembler. The disassembler outputs the new mnemonics. The change in
the above commit resulted in about 224 test errors in test
gdb.arch/powerpc-power10.exp as the disassembled instruction names no
longer matched the expected names.
This patch set consists of two patches. The first patch fixes the
expected instruction names in the gdb.arch/powerpc-power10.exp test as
well as the instruction names in the comments of the source file
gdb.arch/powerpc-power10.s. The second patch updates the names of the
instructions contained in the comments of several gdb source files.
There are no functional changes in the second patch.
The patch set has been tested on Power 10 with no regressions.
Please let me know if the various patches are acceptable. Thanks.
Carl Love
next parent reply other threads:[~2022-11-03 17:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20111d66a467599d893bf85bbdf2e82b76377127.camel@us.ibm.com>
2022-11-03 17:30 ` Carl Love [this message]
2022-11-03 17:30 ` [PATCH 1/2] PowerPC: fix for the gdb.arch/powerpc-power10.exp test Carl Love
2022-11-04 13:02 ` Ulrich Weigand
2022-11-03 17:30 ` [PATCH 2/2] PowerPC: update comments for the MMA instruction name changes Carl Love
2022-11-04 13:04 ` Ulrich Weigand
2022-11-04 15:25 ` Carl Love
2022-11-04 15:49 ` [PATCH 2/2 version 2] " Carl Love
2022-11-04 16:02 ` Ulrich Weigand
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=8cc2a8243ea9515069c067b5d3e40a1335e460f0.camel@us.ibm.com \
--to=cel@us.ibm.com \
--cc=Ulrich.Weigand@de.ibm.com \
--cc=bergner@linux.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=will_schmidt@vnet.ibm.com \
/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).