Re: Preprocessor for assembler macros?

[Ian Lance Taylor <iant at google dot com>]

Dave Korn <dave.korn.cygwin@googlemail.com> writes:

> Daniel Jacobowitz wrote:
>> On Mon, Mar 09, 2009 at 09:20:42AM +0000, Andrew Haley wrote:
>>> Ian Lance Taylor wrote:
>>>>> I'm looking for a way to get inbetween the assembler macro processor
>>>>> and the assembler. I'd like to get the assembler sources mostly
>>>>> as-is, but with the macros used therein already expanded.
>>>> As far as I know there is no straightforward way to do this.  (There 
>>>> certainly was no way to do it back when I implemented macros in gas.)
>>> OK, I have to ask.  If you can't see the effect of macro expansion, how
>>> on Earth did you test the macro processor.  I even imagine how you'd
>>> develop a macro processor whose output you couldn't see.  :-)
>> 
>> Objdump? :-)  It's a lot closer to assembly source than to C source.
>
>   -Wa,am?
>
>   Both these let you see and debug the macro expansion, but Ian's point is
> that what you get isn't anything you can just feed straight back into gas.
> There's no direct equivalent of -E.

Dave and Daniel are both right.  I examined the -am output, and I wrote
a set of test cases, in gas/testsuite/gas/macros, which use objdump to
verify that the output matches an expected pattern.

Ian