Displaying 3 results from an estimated 3 matches for "e66152ec".
2013 Nov 11
2
[LLVMdev] loop vectorizer: JIT + AVX segfaults
...at cs.uiuc.edu>
> http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>
>
>
>
> --
> ~Craig
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20131110/e66152ec/attachment.html>
2013 Nov 11
0
[LLVMdev] loop vectorizer: JIT + AVX segfaults
Do you have a stack trace of the segfault?
We have two different code emitters for X86 in LLVM. The one used by the
normal compiler and MCJIT and the other used by the legacy JIT. All of the
test cases for AVX support go through the first one so it gets the most
attention. We try to keep the legacy JIT in sync with it, but have a
history of failing at that. The stack trace of the segfault may
2013 Nov 10
2
[LLVMdev] loop vectorizer: JIT + AVX segfaults
Is it possible that the AVX support in the JIT engine or x86-64 backend
is not mature? I am getting segfaults when switching from a vector
length 4 to 8 in my application. I isolated the barfing function and it
still segfaults in the minimal setup:
The IR attached implements the following simple function:
void bar(int start, int end, int ignore , bool add , bool addme , float*
out, float* in)
{