[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Discuss-gnuradio] Oprofile from a flow graph running on an OMAP3
From: |
Philip Balister |
Subject: |
Re: [Discuss-gnuradio] Oprofile from a flow graph running on an OMAP3 |
Date: |
Mon, 13 Oct 2008 21:50:42 -0400 |
On Sat, Oct 11, 2008 at 11:22 PM, Eric Blossom <address@hidden> wrote:
> On Sat, Oct 11, 2008 at 02:38:28PM -0400, Philip Balister wrote:
>> From gnuradio running on the Beagle. The flow graph is the one I
>> posted earlier, except fed real data.
>>
>> Anyone know what the std::vector<float, std::allocator<float>
>> >::operator[](unsigned int) call does? I guess it is time to hack
>> some NEON into the generic FIR fiilter code.
>
> I think that's just a sampling artifact of the inlined foo[x].
> I'm pretty sure it's spending time 55% of the time in
> gr_fir_fff_generic::filter.
>
> You may want to try gr.fft_filter_fff instead.
Sort of related, I have GNU radio detecting it is being built for NEON
capable ARM and building the generic and NEON filters. (oddly enough
the cheesy no-unrolling c I use for NEON beats the code in generic by
a factor of 3 or so) Is there a clever way to get the gcc .s files
built?
Philip