Mail Archives: djgpp/2000/02/29/16:22:16
Eric Rudd <rudd AT cyberoptics DOT com> wrote:
> gcc -g -Wa,-adhl foo.c >foo.lst
That's a largely correct set of options, indeed. For details, look up
info as invoking
and the menu entry 'a' in that info node to see what the single option
letters behind the '-a' do. You may want to add '-fverbose-asm' to
that set of flags.
> The -g option seems to be necessary,
That's true. Without the '-g', gcc doesn't generate linenumber
information, and without that, as cannot find the source line an
assembly operation came from. It's clearly documented to behave like
that.
> the two times that -Wa,-a,-ad worked, I got the C source in between
> assembly directives like this:
> /APP
> C statement
> /NO_APP
That's a different piece of cake, I think. This bracing in pairs of
/APP and /NO_APP macros is a typical sign of inline assembly being
passed to as. You'll find it around every block of assembly not
generated by gcc. Other options on the gcc command line may influence
wether inline functions are used or not, so maybe that's what made
this miraculously work, from time to time. It's hard to say without
concrete example cases.
--
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.
- Raw text -