🚀 go-pugleaf

I'm using the iris5 port on my box, so I don't have the benefits
of debugging info with gcc-2.5.7 ( -g not supportet in this version).
Now I looked how the native cc does it. It creates a .s file
with the source lines in the form of
#  <line>  <C-statement>
In fact, it does it allways, regardeless of -g switch. The only 
difference I could examine is , that when -g is specified an 
aditional step after assembling is done - elf2elf -q file.o -.
elf2elf is the dwarf debugging info pass.
Is it possible for gcc to print the source lines in the form above
into the .s file and then run elf2elf after assembling ?
I'm not sure that the "# line statement" is the only thing cc does
to create debugging info, but if so, it would be a cheap way for gcc
to produce it too.

Sebastian