Displaying 2 results from an estimated 2 matches for "elem_0_of_sourc".
Did you mean:
elem_0_of_source
2013 Feb 19
2
[LLVMdev] Is it a bug or am I missing something ?
...x float> %3, float %2, i32 1
%5 = getelementptr <8 x float>* %dest, i32 19
store <8 x float> %4, <8 x float>* %5, align 4
ret void
}
I'm expecting LLVM to generate code so that at vecor is stored at dest[19] with following value:
<float 0.000000e+00, float 'elem_0_of_source' , float 'elem_0_of_source', float 0.000000e+00, float 0.000000e+00, float 0.000000e+00, float 0.000000e+00, float 0.000000e+00>
When I use llc trunk as follows on a Corei7 machine I've got following assembly code:
llc shufxbug.ll -march=x86 -relocation-model=pic -o shufxbug.s...
2013 Feb 19
0
[LLVMdev] Is it a bug or am I missing something ?
...x float> %3, float %2, i32 1
%5 = getelementptr <8 x float>* %dest, i32 19
store <8 x float> %4, <8 x float>* %5, align 4
ret void
}
I'm expecting LLVM to generate code so that at vecor is stored at dest[19]
with following value:
<float 0.000000e+00, float 'elem_0_of_source' , float 'elem_0_of_source',
float 0.000000e+00, float 0.000000e+00, float 0.000000e+00, float
0.000000e+00, float 0.000000e+00>
When I use llc trunk as follows on a Corei7 machine I've got following
assembly code:
llc shufxbug.ll -march=x86 -relocation-model=pic -o shufxbug.s...