From: "Jan Beulich" <jbeulich@suse.com>
To: <amodra@gmail.com>
Cc: <binutils@sourceware.org>
Subject: Re: [PATCH 1/5] PowerPC add initial -mfuture instruction support
Date: Thu, 20 Jun 2019 12:09:00 -0000 [thread overview]
Message-ID: <5D0B7763020000780015CF3E@prv1-mh.provo.novell.com> (raw)
In-Reply-To: <20190524013332.GD6820@bubble.grove.modra.org>
>>> Alan Modra <amodra@gmail.com> 05/24/19 3:33 AM >>>
>--- a/opcodes/ppc-opc.c
>+++ b/opcodes/ppc-opc.c
>@@ -2721,6 +2721,18 @@ const unsigned int num_powerpc_operands = (sizeof (powerpc_operands)
>#define OP(x) ((((uint64_t)(x)) & 0x3f) << 26)
>#define OP_MASK OP (0x3f)
>
>+/* The prefix opcode. */
>+#define PREFIX_OP (1ULL << 58)
>+
>+/* The 2-bit prefix form. */
>+#define PREFIX_FORM(x) ((x & 3ULL) << 56)
>+
>+#define SUFFIX_MASK ((1ULL << 32) - 1)
>+#define PREFIX_MASK (SUFFIX_MASK << 32)
With these, am I right in understanding that ...
>@@ -7796,6 +7809,17 @@ const struct powerpc_opcode powerpc_opcodes[] = {
>const unsigned int powerpc_num_opcodes =
>sizeof (powerpc_opcodes) / sizeof (powerpc_opcodes[0]);
>
>+/* The opcode table for 8-byte prefix instructions.
>+
>+ The format of this opcode table is the same as the main opcode table. */
>+
>+const struct powerpc_opcode prefix_opcodes[] = {
>+{"pnop", PMRR, PREFIX_MASK, POWERXX, 0, {0}},
... everything with the 32 prefix bits matching the pattern decodes to PNOP, regardless of
any of the 32 suffix bits? The testcase added covers only the case of the suffix bits all being
zero.
Jan
next prev parent reply other threads:[~2019-06-20 12:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-24 1:31 [PATCH 0/5] PowerPC -mfuture support Alan Modra
2019-05-24 1:33 ` [PATCH 1/5] PowerPC add initial -mfuture instruction support Alan Modra
2019-06-02 6:33 ` Jan Beulich
2019-06-03 2:26 ` Alan Modra
2019-06-20 12:09 ` Jan Beulich [this message]
2019-06-20 13:31 ` Alan Modra
2019-06-20 13:40 ` Alan Modra
2019-05-24 1:34 ` [PATCH 2/5] PowerPC D-form prefixed loads and stores Alan Modra
2019-06-20 12:04 ` Jan Beulich
2019-06-20 13:17 ` Alan Modra
2019-05-24 1:35 ` [PATCH 3/5] PowerPC relocations for prefix insns Alan Modra
2019-05-24 1:36 ` [PATCH 4/5] PowerPC GOT_PCREL34 optimisation Alan Modra
2019-05-24 1:37 ` [PATCH 5/5] PowerPC notoc linkage stubs Alan Modra
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=5D0B7763020000780015CF3E@prv1-mh.provo.novell.com \
--to=jbeulich@suse.com \
--cc=amodra@gmail.com \
--cc=binutils@sourceware.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).