0aef747b84
The motivation is that the update script has at least two deviations (`<...>@GOT`/`<...>@PLT`/ and not hiding pointer arithmetics) from what pretty much all the checklines were generated with, and most of the tests are still not updated, so each time one of the non-up-to-date tests is updated to see the effect of the code change, there is a lot of noise. Instead of having to deal with that each time, let's just deal with everything at once. This has been done via: ``` cd llvm-project/llvm/test/CodeGen/X86 grep -rl "; NOTE: Assertions have been autogenerated by utils/update_llc_test_checks.py" | xargs -L1 <...>/llvm-project/llvm/utils/update_llc_test_checks.py --llc-binary <...>/llvm-project/build/bin/llc ``` Not all tests were regenerated, however.
25 lines
930 B
LLVM
25 lines
930 B
LLVM
; NOTE: Assertions have been autogenerated by utils/update_llc_test_checks.py
|
|
; RUN: llc < %s -mtriple=i686-apple-darwin9 -mattr=+mmx,+sse4.2 | FileCheck %s --check-prefix=X32
|
|
; RUN: llc < %s -mtriple=x86_64-apple-darwin9 -mattr=+mmx,+sse4.2 | FileCheck %s --check-prefix=X64
|
|
|
|
; MMX insertelement is not available; these are promoted to xmm.
|
|
; (Without SSE they are split to two ints, and the code is much better.)
|
|
|
|
define x86_mmx @mmx_movzl(x86_mmx %x) nounwind {
|
|
; X32-LABEL: mmx_movzl:
|
|
; X32: ## %bb.0:
|
|
; X32-NEXT: movq {{\.?LCPI[0-9]+_[0-9]+}}, %mm0
|
|
; X32-NEXT: retl
|
|
;
|
|
; X64-LABEL: mmx_movzl:
|
|
; X64: ## %bb.0:
|
|
; X64-NEXT: movl $32, %eax
|
|
; X64-NEXT: movq %rax, %xmm0
|
|
; X64-NEXT: retq
|
|
%tmp = bitcast x86_mmx %x to <2 x i32>
|
|
%tmp3 = insertelement <2 x i32> %tmp, i32 32, i32 0
|
|
%tmp8 = insertelement <2 x i32> %tmp3, i32 0, i32 1
|
|
%tmp9 = bitcast <2 x i32> %tmp8 to x86_mmx
|
|
ret x86_mmx %tmp9
|
|
}
|