Re: [Discuss-gnuradio] oprofile callgraph question

[Eric Blossom]

On Mon, Jun 23, 2008 at 05:42:16PM -0400, Mikyung Han wrote:
> BTW, any suggestion for finding out who caused calling the symbols such as
> __ieee754_atan2
> and __kernel_cosf, __kernel_sinf, __ieee754_rem_pio2f from libm-2.5.so?

What kind of a machine are you running on?

The first is of course the guts of atan2.  I'm surprised to see it.
I think the only place it could be getting called is by way of the
complex arg(z) function.   We're replace all the others with calls to 
gr_fast_atan2


address@hidden trunk]$ dgs . '\barg[ \t]*('
./gnuradio-core/src/lib/general/gr_remez.cc: *      Change: ColumnVector 
x=arg(i).vector_value();
./gnuradio-core/src/lib/general/gr_remez.cc: *      to: ColumnVector 
x(arg(i).vector_value());
./gnuradio-core/src/lib/general/gr_mpsk_receiver_cc.cc:  return 
-arg(sample*conj(d_constellation[d_current_const_point]));
./gnuradio-core/src/lib/general/gr_ofdm_frame_sink.cc:  float angle = 
arg(accum_error);
./gnuradio-core/src/lib/general/gr_complex_to_xxx.cc:    //    out[i] = 
std::arg (in[i]);
./gnuradio-core/src/lib/general/gr_quadrature_demod_cf.cc:    // out[i] = 
d_gain * arg (product);


The last 3 are from the guts of cosf and sinf.

What's your test case?


> Also .cleanup?

.cleanup is a just a label toward the bottom of the SIMD code.  
It's unlikely you're getting any serious amount of hits there, it's
not in a loop.


Eric