Re: Mapping C code to generated asm code

2006-01-11 Thread Andi Kleen
Ron McCall <[EMAIL PROTECTED]> writes: > On Wed, Jan 11, 2006 at 12:03:42PM -0600, Perry Smith wrote: > > Is there a way to get some type of debugging output that tells me > > what line of C code produced what lines of asm code? > > How about $TARGET-objdump --disassemble --source? That's tota

Re: Mapping C code to generated asm code

2006-01-11 Thread Jim Blandy
On 1/11/06, Perry Smith <[EMAIL PROTECTED]> wrote: > Is there a way to get some type of debugging output that tells me > what line of C code produced what lines of asm code? Do the .loc directives in the .s files produced by gcc -S work for you? The arguments to .loc are the file number, line num

Re: Mapping C code to generated asm code

2006-01-11 Thread Ron McCall
On Wed, Jan 11, 2006 at 12:03:42PM -0600, Perry Smith wrote: > Is there a way to get some type of debugging output that tells me > what line of C code produced what lines of asm code? How about $TARGET-objdump --disassemble --source? Ron

Re: Mapping C code to generated asm code

2006-01-11 Thread Diego Novillo
On Wednesday 11 January 2006 13:03, Perry Smith wrote: > Is there a way to get some type of debugging output that tells me > what line of C code produced what lines of asm code? > $ gcc -Wa,-ahlsdn -gstabs

Mapping C code to generated asm code

2006-01-11 Thread Perry Smith
Is there a way to get some type of debugging output that tells me what line of C code produced what lines of asm code? Thank you, Perry