discuss-gnuradio
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Discuss-gnuradio] Volk library invalid opcode exception


From: Tom Rondeau
Subject: Re: [Discuss-gnuradio] Volk library invalid opcode exception
Date: Sun, 15 Apr 2012 11:45:17 -0400

On Sun, Apr 15, 2012 at 11:04 AM, Joanna Rutkowska
<address@hidden> wrote:
> On 04/15/12 16:59, Joanna Rutkowska wrote:
>> With dbg symbols:
>>
>> Starting program:
>> /rw/home/user/gnuradio/gnuradio/volk/build/apps/volk_profile
>> [Thread debugging using libthread_db enabled]
>> Using Volk machine: avx_64
>> RUN_VOLK_TESTS: volk_16ic_s32f_deinterleave_real_32f_a
>>
>> Program received signal SIGILL, Illegal instruction.
>> 0x00007ffff7b289bd in volk_16ic_s32f_deinterleave_real_32f_a_sse4_1
>> (iBuffer=0x7053a0, complexVector=0x7ffff7e47020, scalar=4.59163468e-41,
>>     num_points=4160742024) at
>> /rw/home/user/gnuradio/gnuradio/volk/include/volk/volk_16ic_s32f_deinterleave_real_32f_a.h:17
>> 17    static inline void
>> volk_16ic_s32f_deinterleave_real_32f_a_sse4_1(float* iBuffer, const
>> lv_16sc_t* complexVector, const float scalar, unsigned int num_points){
>>
>
> Sorry, this didn't paste in into the last message:
>
> Dump of assembler code for function
> volk_16ic_s32f_deinterleave_real_32f_a_sse4_1:
>   0x00007ffff7b289a4 <+0>:     push   %rbp
>   0x00007ffff7b289a5 <+1>:     mov    %rsp,%rbp
>   0x00007ffff7b289a8 <+4>:     sub    $0x108,%rsp
>   0x00007ffff7b289af <+11>:    mov    %rdi,-0x158(%rbp)
>   0x00007ffff7b289b6 <+18>:    mov    %rsi,-0x160(%rbp)
> => 0x00007ffff7b289bd <+25>:    vmovss %xmm0,-0x164(%rbp)
>
>
> j.

Yes, so the vmovss is an AVX instruction (the AVX version of movss),
but your processor doesn't have AVX according to your flags above.
Except that it does. According to Intel, the i5-2540M processor
supports AVX, but your OS isn't recognizing the avx flag in
/proc/cpuinfo. The Volk build process asks the processor directly for
the flags that it can use.

I really think this is a problem with Xen (or at least something in the setup).

Tom



reply via email to

[Prev in Thread] Current Thread [Next in Thread]