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

Intermixing powerpc-eabi and powerpc-linux C code

2006-06-01 Thread Ron McCall
of code. None of the powerpc-eabi code will depend on any libraries or other external code, it will all be completely self-contained. Thanks! Ron McCall

Re: Intermixing powerpc-eabi and powerpc-linux C code

2006-06-01 Thread Ron McCall
I guess I should have also mentioned that the resultant program will be run under gdb, with a script setting breakpoints, running, examining variables, etc. --- Paul Brook <[EMAIL PROTECTED]> wrote: > > The call from Linux-land to eabi-land would not > need > > to pass arguments nor return anythi

Re: Intermixing powerpc-eabi and powerpc-linux C code

2006-06-06 Thread Ron McCall
You make a good point about the linker aspect but I was first most concerned about the code generation differences, if any. However, you are absolutely correct! A test is in order. I whipped up a quick test program and was able to successfully compile, link and run it, so it does indeed work!

DWARF2 DW_TAG_base_type for void?

2006-09-06 Thread Ron McCall
a void * pointer type). Is that not the case? I am using gcc 4.0.3 and binutils 2.16.1 in case that matters. Just curious. Ron McCall

Re: DWARF2 DW_TAG_base_type for void?

2006-09-06 Thread Ron McCall
On Wed, Sep 06, 2006 at 07:39:04PM -0400, Daniel Jacobowitz wrote: > Yes, this is the convention we use. > > Void isn't a base type. The DWARF 3 standard way to represent this is > DW_TAG_unspecified_type. OK, thanks! Ron