maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/llvm/test/CodeGen/X86/2008-09-05-sinttofp-2xi32.ll

43 lines
1.0 KiB
LLVM
Raw Normal View History

X86: Do not use llc -march in tests. `llc -march` is problematic because it only switches the target architecture, but leaves the operating system unchanged. This occasionally leads to indeterministic tests because the OS from LLVM_DEFAULT_TARGET_TRIPLE is used. However we can simply always use `llc -mtriple` instead. This changes all the tests to do this to avoid people using -march when they copy and paste parts of tests. See also the discussion in https://reviews.llvm.org/D35287 llvm-svn: 309774
2017-08-02 08:28:10 +08:00
; RUN: llc < %s -mtriple=i686-- -mattr=+sse2,+mmx | FileCheck %s
Massive rewrite of MMX: The x86_mmx type is used for MMX intrinsics, parameters and return values where these use MMX registers, and is also supported in load, store, and bitcast. Only the above operations generate MMX instructions, and optimizations do not operate on or produce MMX intrinsics. MMX-sized vectors <2 x i32> etc. are lowered to XMM or split into smaller pieces. Optimizations may occur on these forms and the result casted back to x86_mmx, provided the result feeds into a previous existing x86_mmx operation. The point of all this is prevent optimizations from introducing MMX operations, which is unsafe due to the EMMS problem. llvm-svn: 115243
2010-10-01 07:57:10 +08:00
; originally from PR2687, but things don't work that way any more.
; there are no MMX instructions here; we use XMM.
Fix for PR2687: Add patterns to match sint_to_fp and fp_to_sint for <2 x i32>. This is a little messy, but it works. We should really get rid of the intrinsics, though, since they map perfectly well to standard LLVM instructions. llvm-svn: 55864
2008-09-06 07:07:03 +08:00
define <2 x double> @a(<2 x i32> %x) nounwind {
entry:
Update test to use FileCheck and clean up run lines to match the expected behavior. llvm-svn: 249498
2015-10-07 09:21:49 +08:00
; CHECK-LABEL: a
; CHECK-NOT: unpcklpd
Fix for PR2687: Add patterns to match sint_to_fp and fp_to_sint for <2 x i32>. This is a little messy, but it works. We should really get rid of the intrinsics, though, since they map perfectly well to standard LLVM instructions. llvm-svn: 55864
2008-09-06 07:07:03 +08:00
%y = sitofp <2 x i32> %x to <2 x double>
ret <2 x double> %y
}
define <2 x i32> @b(<2 x double> %x) nounwind {
entry:
Update test to use FileCheck and clean up run lines to match the expected behavior. llvm-svn: 249498
2015-10-07 09:21:49 +08:00
; CHECK-LABEL: b
; CHECK-NOT: unpckhpd
Fix for PR2687: Add patterns to match sint_to_fp and fp_to_sint for <2 x i32>. This is a little messy, but it works. We should really get rid of the intrinsics, though, since they map perfectly well to standard LLVM instructions. llvm-svn: 55864
2008-09-06 07:07:03 +08:00
%y = fptosi <2 x double> %x to <2 x i32>
ret <2 x i32> %y
}
Massive rewrite of MMX: The x86_mmx type is used for MMX intrinsics, parameters and return values where these use MMX registers, and is also supported in load, store, and bitcast. Only the above operations generate MMX instructions, and optimizations do not operate on or produce MMX intrinsics. MMX-sized vectors <2 x i32> etc. are lowered to XMM or split into smaller pieces. Optimizations may occur on these forms and the result casted back to x86_mmx, provided the result feeds into a previous existing x86_mmx operation. The point of all this is prevent optimizations from introducing MMX operations, which is unsafe due to the EMMS problem. llvm-svn: 115243
2010-10-01 07:57:10 +08:00
; This is how to get MMX instructions.
define <2 x double> @a2(x86_mmx %x) nounwind {
entry:
Update test to use FileCheck and clean up run lines to match the expected behavior. llvm-svn: 249498
2015-10-07 09:21:49 +08:00
; CHECK-LABEL: a2
; CHECK: cvtpi2pd
; CHECK-NOT: cvtpi2pd
Massive rewrite of MMX: The x86_mmx type is used for MMX intrinsics, parameters and return values where these use MMX registers, and is also supported in load, store, and bitcast. Only the above operations generate MMX instructions, and optimizations do not operate on or produce MMX intrinsics. MMX-sized vectors <2 x i32> etc. are lowered to XMM or split into smaller pieces. Optimizations may occur on these forms and the result casted back to x86_mmx, provided the result feeds into a previous existing x86_mmx operation. The point of all this is prevent optimizations from introducing MMX operations, which is unsafe due to the EMMS problem. llvm-svn: 115243
2010-10-01 07:57:10 +08:00
%y = tail call <2 x double> @llvm.x86.sse.cvtpi2pd(x86_mmx %x)
ret <2 x double> %y
}
define x86_mmx @b2(<2 x double> %x) nounwind {
entry:
Update test to use FileCheck and clean up run lines to match the expected behavior. llvm-svn: 249498
2015-10-07 09:21:49 +08:00
; CHECK-LABEL: b2
; CHECK: cvttpd2pi
; CHECK-NOT: cvttpd2pi
Massive rewrite of MMX: The x86_mmx type is used for MMX intrinsics, parameters and return values where these use MMX registers, and is also supported in load, store, and bitcast. Only the above operations generate MMX instructions, and optimizations do not operate on or produce MMX intrinsics. MMX-sized vectors <2 x i32> etc. are lowered to XMM or split into smaller pieces. Optimizations may occur on these forms and the result casted back to x86_mmx, provided the result feeds into a previous existing x86_mmx operation. The point of all this is prevent optimizations from introducing MMX operations, which is unsafe due to the EMMS problem. llvm-svn: 115243
2010-10-01 07:57:10 +08:00
%y = tail call x86_mmx @llvm.x86.sse.cvttpd2pi (<2 x double> %x)
ret x86_mmx %y
}
declare <2 x double> @llvm.x86.sse.cvtpi2pd(x86_mmx)
declare x86_mmx @llvm.x86.sse.cvttpd2pi(<2 x double>)