This is the mail archive of the
mailing list for the binutils project.
RE: I've broken my binutils version 2.28
> -----Original Message-----
> From: ANDY KENNEDY
> Sent: Thursday, September 14, 2017 5:18 PM
> To: 'email@example.com'
> Subject: RE: I've broken my binutils version 2.28
> > -----Original Message-----
> > From: firstname.lastname@example.org [mailto:email@example.com] On Behalf Of Matthew
> > Sent: Wednesday, September 13, 2017 5:09 PM
> > To: ANDY KENNEDY; 'firstname.lastname@example.org'
> > Subject: RE: I've broken my binutils version 2.28
> Again, thanks to Matthew for helping me fix that last problem.
> The new problem (as described briefly last night) has multiple variants.
A specific question: In the file include/opcode/mips.h, I see lines
#define INSN_OCTEON3 0x00000040
#define INSN_XLR 0x00000020
In the patch I stole from the web years ago, I found this:
#define INSN_XLP 0x00000040
0x00000040 is now Octeon3's spot. What values are acceptable for this
match? I see where it XLR and OCTEON3 are used below in
cpu_is_member(), but I also see there are no more unique values. I
attempted to try 0x00000080 as a value, but that seems to be defined as:
#define ASE_MT 0x00000080
which I would expect would collide with that target.
Am I allowed to use something like:
#define INSN_XLP 0xdeadbee40
to make it unique enough?