-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Enigmail
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFEAyO5MPiy0tCWlz4RAoLWAJ4iWjiTKTYPH0EJmjXyot68+4ee1QCgw/H8
XngfDRCbqpwesc2NT9hZO94=
=tnLf
-----END PGP SIGNATURE-----
--- Begin Message ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> Dave> On 27 February 2006 14:48, Nikolaos Kavvadias wrote: Dave>
> Well, yes, it /could/ be done. It would be pretty trivial Dave>
> really; you'd just need to go through the insn patterns in the
> Dave> .md file, find the ones that have output templates that
> mention Dave> any of the macros, and replace them with templates
> that Dave> generate the expanded version directly. You might also
> need to Dave> check the md .c and .h files as well, because they
> often Dave> contain assembler fragments, but they would be just as
> easy to Dave> convert.
Thanks DaveK and paul for your to-the-point responses. The reason
behind my question is that I want to use an closed-source
infrastructure for software toolchain generation which does not allow
macros that expand to more than one machine instructions (that's the
reason for the "li"). [The "li" example was taken from another
(open-source) infrastructure that I use for such stuff
(http://www.archc.org).]
I understand that binutils are not responsible for generating these
macros, they only have to interpret them; the compiler (e.g.
mips-elf-gcc) is. But your response is insightful. However, binutils
could produce a "real" assembly listing without the macro-instructions
(is that one taken by "-l"?).
I'll cross-post to gcc too since this is gcc-specific. I'm not sure if
the latest gcc (4.0.2?) avoids macros. I'll have a look at gcc ml too.
kind regards
Nikolaos Kavvadias
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFEAyObMPiy0tCWlz4RAkGTAJ0fzplFyFSwgVVigzAxnAPPgeOfCACgqx6G
Ci8QR2N0Vf6v/vtmFo0Yc3A=
=/shs
-----END PGP SIGNATURE-----
--- End Message ---
