bug-binutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: gprof 2.14 glitches w/ powerpc elf binaries


From: Njuguna Njoroge
Subject: Re: gprof 2.14 glitches w/ powerpc elf binaries
Date: Mon, 30 Aug 2004 16:15:44 -0700

Hi Nick,

Nick Clifton wrote:

> Have you tried running gprof with the -D command line switch ?  I think
> that this will get fix the spurious references to Letext for you.

This helps and it does take off Letext.

>
> As for the references to memcpy - I think that these really do happen.
> It appears to be called from the code inside xil_printf.c.  It may be
> that the code there uses the "=" operator to perform a structure
> assignment.  The compiler will sometimes translate this into a call to
> memcpy.  eg:
>
>     typedef struct { int a; int b; int c; } s;
>     s * ptr1, * ptr2;
>
>     * ptr1 = * ptr2;
>

Good point. While this may be true about memcpy, there are some other functions 
that
are still listed (even after -D) and we are certain that were never executed. I
inserted print statements in my Perl scripts to dump out the address histogram 
bins as
it is about to write them into the gmon.out file and compared them with the 
address
specified in the ELF binary. For instance, in the simple_test.elf that I have 
attached,
the functions _boot0 and _boot were never captured in the trace (they were run, 
but the
trace capture triggered after these functions exited). However, they appear in 
the
profile (simple_test_x86.pro). Even more strange, when we run native gpprof 
(version
2.10) on the ppc405 processor, these functions are excluded (simple_test.pro). 
What
could be causing this discrepancy?

Thanks,

Nju

Attachment: simple_test_sol.out
Description: application/unknown-content-type-out_auto_file

Attachment: simple_test.elf
Description: Binary data

Attachment: simple_test_x86.pro
Description: application/unknown-content-type-pro_auto_file

Attachment: simple_test.pro
Description: application/unknown-content-type-pro_auto_file

Attachment: simple_test.c
Description: application/unknown-content-type-c_auto_file


reply via email to

[Prev in Thread] Current Thread [Next in Thread]