Re: MI: performance of getting stack arguments

Daniel Jacobowitz
2006-04-26T14:59:44Z

On Wed, Apr 26, 2006 at 06:53:43PM +0400, Vladimir Prus wrote:
> Here's the results I get for multiple -stack-list-frames commands:
>
> % cumulative self self total
> time seconds seconds calls Ts/call Ts/call name
> 24.18 2.50 2.50 find_pc_sect_psymbol
> 18.28 4.39 1.89
> lookup_minimal_symbol_by_pc_section
> 8.03 5.22 0.83 find_pc_sect_psymtab
> 6.48 5.89 0.67 find_pc_sect_section
> 4.06 6.31 0.42 dwarf2_frame_find_fde
> 3.09 6.63 0.32 find_pc_sect_line
> 2.03 6.84 0.21 mem_file_write
> 1.84 7.03 0.19 printchar
>
> I'm not sure how to interpret this data, though.

I'd definitely try to get a callgraph - either from --enable-profiling
or callgrind, whatever. It looks like we're doing a _lot_ of
unwinding; otherwise dwarf2_frame_find_fde shouldn't be showing up.

--
Daniel Jacobowitz
CodeSourcery