On Wed, Feb 13, 2013 at 12:49 PM, Nick Foster n...@ettus.com wrote:
The segfault is a different story. Like Josh suggests a backtrace would be
helpful to see exactly what went wrong.
The generic implementation of the rotator function normally takes 5-6
seconds on a typical machine, so the
Thank you. I think this may be the problem:
# grep Available architectures cmake.out
-- Available architectures:
generic;32;3dnow;abm;popcount;mmx;sse;sse2;orc;norc;sse3;ssse3;sse4_a;sse4_1;sse4_2;avx
# grep Available machines cmake.out
-- Available machines:
On Wed, Feb 13, 2013 at 8:25 AM, Tommy Tracy II tj...@virginia.edu wrote:
# grep Available architectures cmake.out
-- Available architectures:
generic;32;3dnow;abm;popcount;mmx;sse;sse2;orc;norc;sse3;ssse3;sse4_a;sse4_1;sse4_2;avx
# grep Available machines cmake.out
-- Available machines:
On 02/13/2013 01:44 PM, Johnathan Corgan wrote:
On Wed, Feb 13, 2013 at 8:25 AM, Tommy Tracy II tj...@virginia.edu wrote:
# grep Available architectures cmake.out
-- Available architectures:
generic;32;3dnow;abm;popcount;mmx;sse;sse2;orc;norc;sse3;ssse3;sse4_a;sse4_1;sse4_2;avx
# grep
The problem is that during the build, AVX support was enabled, even though my
processor doesn't support it.
-- Python checking for Cheetah = 2.0.0
-- Python checking for Cheetah = 2.0.0 - found
-- Compiler name: GNU
-- x86* CPU detected
-- CPU width is 32 bits, Overruled arch 64
-- Available
Nick, thank you. I was wondering why AVX showed up in the list if the processor
didn't support it.
Does anyone have any ideas why rotatorpupper would take so long?
Sincerely,
Tommy James Tracy II
PhD Student
High Performance Low Power Lab
On 02/13/2013 01:59 PM, Tommy Tracy II wrote:
The problem is that during the build, AVX support was enabled, even though my
processor doesn't support it.
Thats intended because AVX is supported by the compiler. You should
notice however, that VOLK detected at runtime that AVX was not
What I got from GDB:
Is there any way to get more information using backtrace?
Program received signal SIGSEGV, Segmentation fault.
0xf7f77098 in volk_32fc_32f_multiply_32fc_a_generic () from
/usr/lib/libvolk.so.0.0.0
…
Program terminated with signal SIGSEGV, Segmentation fault.
The program no
On 02/13/2013 12:17 PM, Tommy Tracy II wrote:
Nick, thank you. I was wondering why AVX showed up in the list if the
processor didn't support it.
Does anyone have any ideas why rotatorpupper would take so long?
I don't, but I'm not that worried about it as the generic implementation
is only
On Mon, Feb 11, 2013 at 1:19 PM, Tommy Tracy II tj...@virginia.edu wrote:
I tried running volk_profile in Gentoo and got the following:
# volk_profile
Using Volk machine: sse4_2_32_orc
RUN_VOLK_TESTS: volk_32fc_s32fc_rotatorpuppet_32fc_a
*generic completed in 361.04s*
sse4_1 completed in
I tried running volk_profile in Gentoo and got the following:
# volk_profile
Using Volk machine: sse4_2_32_orc
RUN_VOLK_TESTS: volk_32fc_s32fc_rotatorpuppet_32fc_a
generic completed in 361.04s
sse4_1 completed in 0.49s
Best arch: sse4_1
RUN_VOLK_TESTS: volk_16ic_s32f_deinterleave_real_32f_a
11 matches
Mail list logo
