It looks like a couple of functions are failing from the stdout:
volk_32fc_s32f_magnitude_16i_a: fail on arch orc
volk_32fc_x2_multiply_32fc_a: fail on arch orc
These are both the Orc implementations of the functions, which seem to work fine on my Intel processors. I don't have access to an OSX box or an E100, so I can't really test this out. The files you sent me don't (appear to) tell me what the real problem is.
We'll need some other brave soul out there who can dig into these issues on the platforms for us.
Those are functions I wrote, so they're my problem. =) I'll hack on it this week. What's strange is I absolutely validated them on Orc before committing them... Sean, what version of Orc are you running on your E100?
Subject: Re: [Discuss-gnuradio] Using volk in Mac: test report
On Fri, Feb 17, 2012 at 5:11 PM, Nowlan, Sean <Sean.Nowlan@gtri...<mailto:Sean.Nowlan@gtri...>> wrote:
I built Tom's safe_align branch on E100 and ran volk_profile. It segfaulted on "RUN_VOLK_TESTS:volk_32fc_s32fc_multiply_32fc_a. I'll get a stack trace for you.
Really interesting that it's the same block. Hopefully, it's a single, simple fix. I'll look into it when you can get me the stack trace.
We are interested in determining the best architecture at instantation
time. What would be the best strategy? We though about running the
same operations several times for each architecture, measure the
results and use the fastest one for the processing blocks. Would this
be the right approach?
Run volk_profile. It does exactly what you said, and writes the results to ~/.volk/volk_config. Volk reads this file when it is involked (sorry) to determine which particular function to execute. So all you do is run volk_profile once on any given machine, and it's optimized.