llvm-mirror/test/CodeGen/X86/2007-06-15-IntToMMX.ll

; RUN: llc < %s -march=x86-64 -mattr=+mmx | grep paddusw
@R = external global x86_mmx          ; <x86_mmx*> [#uses=1]

define void @foo(<1 x i64> %A, <1 x i64> %B) {
entry:
        %tmp2 = bitcast <1 x i64> %A to x86_mmx
        %tmp3 = bitcast <1 x i64> %B to x86_mmx
        %tmp7 = tail call x86_mmx @llvm.x86.mmx.paddus.w( x86_mmx %tmp2, x86_mmx %tmp3 )   ; <x86_mmx> [#uses=1]
        store x86_mmx %tmp7, x86_mmx* @R
        tail call void @llvm.x86.mmx.emms( )
        ret void
}

declare x86_mmx @llvm.x86.mmx.paddus.w(x86_mmx, x86_mmx)

declare void @llvm.x86.mmx.emms()
Eliminate more uses of llvm-as and llvm-dis. llvm-svn: 81290 2009-09-09 01:54:48 +02:00			`; RUN: llc < %s -march=x86-64 -mattr=+mmx \| grep paddusw`
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 01:57:10 +02:00			`@R = external global x86_mmx ; <x86_mmx*> [#uses=1]`
Testcase for MMX int to MMX register failure. llvm-svn: 37612 2007-06-16 08:31:47 +02:00
			`define void @foo(<1 x i64> %A, <1 x i64> %B) {`
			`entry:`
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 01:57:10 +02:00			`%tmp2 = bitcast <1 x i64> %A to x86_mmx`
			`%tmp3 = bitcast <1 x i64> %B to x86_mmx`
			`%tmp7 = tail call x86_mmx @llvm.x86.mmx.paddus.w( x86_mmx %tmp2, x86_mmx %tmp3 ) ; <x86_mmx> [#uses=1]`
			`store x86_mmx %tmp7, x86_mmx* @R`
Testcase for MMX int to MMX register failure. llvm-svn: 37612 2007-06-16 08:31:47 +02:00			`tail call void @llvm.x86.mmx.emms( )`
			`ret void`
			`}`

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 01:57:10 +02:00			`declare x86_mmx @llvm.x86.mmx.paddus.w(x86_mmx, x86_mmx)`
Testcase for MMX int to MMX register failure. llvm-svn: 37612 2007-06-16 08:31:47 +02:00
			`declare void @llvm.x86.mmx.emms()`