This is the mail archive of the
binutils@sourceware.org
mailing list for the binutils project.
Re: on mapping between assembly codes and objdump files
- From: Ian Lance Taylor <ian at airs dot com>
- To: Liu Haibin <liu dot haibin at gmail dot com>
- Cc: binutils at sourceware dot org
- Date: 07 Nov 2005 11:19:23 -0800
- Subject: Re: on mapping between assembly codes and objdump files
- References: <e538aa3e0511070318x77a2a958u833a8398d8da9a1e@mail.gmail.com>
Liu Haibin <liu.haibin@gmail.com> writes:
> I have a question on the mapping between assembly codes and objdump
> files. I understand that some codes in assembly codes are INSN_MACRO.
> For example, addu in assembly codes can become addiu in objdump files,
> li to addiu, move to addu, and so on. My question is if there's an
> easy way to show the mapping between the above two, like an option in
> gas. Or I have to go through the gas source codes for every
> INSN_MACRO.
You are presumably talking about MIPS. It helps if you explain that.
I'm not sure what kind of a mapping you are looking for. All the
INSN_MACRO instructions are listed in opcodes/mips-opc.c, along with
all the other MIPS instructions. If that is not what you want, can
you give an example of what you are looking for?
Ian