Displaying 6 results from an estimated 6 matches for "vec_spat".
Did you mean:
vec_splat
2008 Oct 26
6
[LLVMdev] Turning on LegalizeTypes by default
...are as follows:
(a) "make check" has two failures:
ARM/cse-libcalls.ll - this is because of a bug in UpdateNodeOperands
which does not do CSE on calls correctly. The question here is how best
to fix this while minimizing code duplication. This will doubtless be
fixed soon.
PowerPC/vec_spat.ll (@splat_h) - here code got slightly worse. The
problem here is that LegalizeDAG "cheats": it constructs a BUILD_VECTOR
where the type of the operands doesn't match the vector element type (this
is supposed to be illegal), while LegalizeTypes correctly constructs a
BUILD_VECTOR whe...
2008 Oct 26
0
[LLVMdev] Turning on LegalizeTypes by default
...ck" has two failures:
> ARM/cse-libcalls.ll - this is because of a bug in UpdateNodeOperands
> which does not do CSE on calls correctly. The question here is how
> best
> to fix this while minimizing code duplication. This will doubtless be
> fixed soon.
Ok.
> PowerPC/vec_spat.ll (@splat_h) - here code got slightly worse. The
> problem here is that LegalizeDAG "cheats": it constructs a
> BUILD_VECTOR
> where the type of the operands doesn't match the vector element type
> (this
> is supposed to be illegal), while LegalizeTypes correctly...
2006 Nov 16
2
[LLVMdev] 1.9 Prerelease Available for Testing
...I don't think thats a good solution. There are many other tests that
> should be run. I just need to fix that bug so we only run tests for the
> specific target we are on.
The issue is that we have many tests that work in cross compile mode. For
example, test/Regression/CodeGen/PowerPC/vec_spat.ll contains:
; RUN: llvm-as < %s | llc -march=ppc32 -mcpu=g5 | grep vspltw | wc -l | grep 2 &&
; RUN: llvm-as < %s | llc -march=ppc32 -mcpu=g3 | grep stfs | wc -l | grep 4 &&
; RUN: llvm-as < %s | llc -march=ppc32 -mcpu=g5 | grep vsplti | wc -l | grep 3 &&
; RUN: l...
2006 Nov 16
0
[LLVMdev] 1.9 Prerelease Available for Testing
>>> No ppc, but x86 (Slackware 10.2) with LLVM 1.9 and its associated
>>> GCC4-based frontend (recompiled for my machine). I put the log file in
>>> attachment. A lot of failures arose from the fact that the ppc, alpha, ...
>>> backends were not built and hence not found.
>>
>> Ah yes I see. The test framework needs to be modified to handle this but
2006 Nov 16
0
[LLVMdev] 1.9 Prerelease Available for Testing
...ts a good solution. There are many other tests that
>> should be run. I just need to fix that bug so we only run tests for the
>> specific target we are on.
>
> The issue is that we have many tests that work in cross compile mode. For
> example, test/Regression/CodeGen/PowerPC/vec_spat.ll contains:
>
> ; RUN: llvm-as < %s | llc -march=ppc32 -mcpu=g5 | grep vspltw | wc -l | grep 2 &&
> ; RUN: llvm-as < %s | llc -march=ppc32 -mcpu=g3 | grep stfs | wc -l | grep 4 &&
> ; RUN: llvm-as < %s | llc -march=ppc32 -mcpu=g5 | grep vsplti | wc -l | grep 3...
2006 Nov 16
2
[LLVMdev] 1.9 Prerelease Available for Testing
On Thu, 16 Nov 2006, Tanya M. Lattner wrote:
>> No ppc, but x86 (Slackware 10.2) with LLVM 1.9 and its associated
>> GCC4-based frontend (recompiled for my machine). I put the log file in
>> attachment. A lot of failures arose from the fact that the ppc, alpha, ...
>> backends were not built and hence not found.
>
> Ah yes I see. The test framework needs to be