From: "Maciej W. Rozycki" <macro@orcam.me.uk>
To: binutils@sourceware.org
Subject: [committed 1/2] MIPS/opcodes: Update INSN_CHIP_MASK for INSN_ALLEGREX
Date: Thu, 13 Jun 2024 14:03:50 +0100 (BST) [thread overview]
Message-ID: <alpine.DEB.2.21.2406131313390.9248@angie.orcam.me.uk> (raw)
In-Reply-To: <alpine.DEB.2.21.2406131309130.9248@angie.orcam.me.uk>
From: Maciej W. Rozycki <macro@redhat.com>
An update has been missed with commit df18f71b565c ("Add MIPS Allegrex
CPU as a MIPS2-based CPU") for INSN_CHIP_MASK to include INSN_ALLEGREX.
Fix it.
---
include/opcode/mips.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
binutils-mips-opcodes-chip-mask-allegrex.diff
Index: binutils-gdb/include/opcode/mips.h
===================================================================
--- binutils-gdb.orig/include/opcode/mips.h
+++ binutils-gdb/include/opcode/mips.h
@@ -1225,7 +1225,7 @@ static const unsigned int mips_isa_table
#undef ISAF
/* Masks used for Chip specific instructions. */
-#define INSN_CHIP_MASK 0xc7ff4f60
+#define INSN_CHIP_MASK 0xcfff4f60
/* Cavium Networks Octeon instructions. */
#define INSN_OCTEON 0x00000800
next prev parent reply other threads:[~2024-06-13 13:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-13 13:03 [committed 0/2] MIPS/opcodes: INSN_* flag clean-ups Maciej W. Rozycki
2024-06-13 13:03 ` Maciej W. Rozycki [this message]
2024-06-13 13:03 ` [committed 2/2] MIPS/opcodes: Rework INSN_* flags into a consistent block Maciej W. Rozycki
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=alpine.DEB.2.21.2406131313390.9248@angie.orcam.me.uk \
--to=macro@orcam.me.uk \
--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).