This is the mail archive of the
mailing list for the binutils project.
Re: About opcode!
- From: Ian Lance Taylor <ian at wasabisystems dot com>
- To: libra <mr924352 at cs dot nthu dot edu dot tw>
- Cc: binutils at sources dot redhat dot com
- Date: 02 Jul 2004 13:19:26 -0400
- Subject: Re: About opcode!
- References: <firstname.lastname@example.org>
libra <email@example.com> writes:
> I have one question about opcode in binutils source directory.
> Why have two opcode information(file) in two different location,one is in
> "binutils-2.14/opcodes/xxx-opc.h", the other is in "binutils-
> For example:
> "binutils-2.14/opcodes/arm-opc.h" and "binutils-2.14/include/opcode/arm.h"
> Why can not just use one opcode table file? For example, just use "binutils-
> 2.14/include/opcode/arm.h". What's different purpose between arm-opc.h and
There is no good reason for this. It is just the ways the ARM tools
were historically developed. You didn't even mention that there is
yet another version of the ARM opcode table in gas/config/tc-arm.c. I
think it would be great if somebody cleaned it up.
Fortunately most processors do not have this type of duplicated
information. For most processors, all opcode information can be found
in one place: opcodes/CPU-opc.c.