Generating assembly code without macro-instructions

Nikolaos Kavvadias nkavv@physics.auth.gr
Mon Feb 27 23:09:00 GMT 2006


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
 
Dave Korn wrote:

> <boggle> To my way of thinking, that just says that it doesn't
> allow macros full stop!
>
> The output you see from "objdump -d" will always have the real
> instructions and not show the macros. I don't know what the
> assembler does, but I think the listing files are very closely tied
> to the input sources you find it, so it's likely to output the
> "lhi" instruction with 8 bytes (2 words) of instruction data next
> to it instead of just 4, but still likely to show the original
> input form of the macro. You can of course modify the assembler to
> behave differently but I haven't ever looked at listing-generation
> so I can't offer advice, except that it should be possible if it
> doesn't already do so.

Dave

although their tool (commercial but we are academic buyers) is nice
(Win IDE, concise language, real-life designs -- mostly DSPs -- have
been employed with the tools) it suffers from some ommisions.

1. Macro-operations are not ***really*** supported (as you said).
2. Alternate register names not supported.
3. Common gas directives not supported.

Overall, their lack of "synchronization" to binutils conventions is
the cause of most issues.

regards
Nikolaos Kavvadias

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
 
iD8DBQFEAzfLMPiy0tCWlz4RAn9TAJ0fq+AcDr1OnWPhnCfckf0b4SvgJwCfQY0L
jvsEV0olKYhiB06/8oyz3I4=
=CACJ
-----END PGP SIGNATURE-----



More information about the Binutils mailing list