on mapping between assembly codes and objdump files

[Liu Haibin]

Actually I'm talking about simplescalar, but it's just a close
derivative of MIPS architecture.

I know that I can get all INSN_MACRO from
opcodes/ss-opc.c(mips-opcs.c) and go through macro() in
gas/config/tc-ss.c to know all the corresponding actual instruction.
But the whole process is a lot of work.

What I want is an easy way to find the mapping between the macro to
actual instruction. Is there any option to gas so that it'll output
all the mapping. Or any other ways?


haibin




On 07 Nov 2005 11:19:23 -0800, Ian Lance Taylor <ian@airs.com> wrote:
> 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
>