llvm-project/llvm/test/CodeGen/SPARC/2006-01-22-BitConvertLegali...

; RUN: llc < %s -march=sparc

define void @execute_list() {
        %tmp.33.i = fdiv float 0.000000e+00, 0.000000e+00               ; <float> [#uses=1]
        %tmp.37.i = fmul float 0.000000e+00, %tmp.33.i           ; <float> [#uses=1]
        %tmp.42.i = fadd float %tmp.37.i, 0.000000e+00           ; <float> [#uses=1]
        call void @gl_EvalCoord1f( float %tmp.42.i )
        ret void
}

declare void @gl_EvalCoord1f(float)
Eliminate more uses of llvm-as and llvm-dis. llvm-svn: 81293 2009-09-09 08:09:15 +08:00			`; RUN: llc < %s -march=sparc`
move V8 testcases here llvm-svn: 25986 2006-02-05 13:52:55 +08:00
Remove llvm-upgrade and update tests. llvm-svn: 47296 2008-02-19 09:41:04 +08:00			`define void @execute_list() {`
			`%tmp.33.i = fdiv float 0.000000e+00, 0.000000e+00 ; <float> [#uses=1]`
Split the Add, Sub, and Mul instruction opcodes into separate integer and floating-point opcodes, introducing FAdd, FSub, and FMul. For now, the AsmParser, BitcodeReader, and IRBuilder all preserve backwards compatability, and the Core LLVM APIs preserve backwards compatibility for IR producers. Most front-ends won't need to change immediately. This implements the first step of the plan outlined here: http://nondot.org/sabre/LLVMNotes/IntegerOverflow.txt llvm-svn: 72897 2009-06-05 06:49:04 +08:00			`%tmp.37.i = fmul float 0.000000e+00, %tmp.33.i ; <float> [#uses=1]`
			`%tmp.42.i = fadd float %tmp.37.i, 0.000000e+00 ; <float> [#uses=1]`
Remove llvm-upgrade and update tests. llvm-svn: 47296 2008-02-19 09:41:04 +08:00			`call void @gl_EvalCoord1f( float %tmp.42.i )`
			`ret void`
move V8 testcases here llvm-svn: 25986 2006-02-05 13:52:55 +08:00			`}`

Remove llvm-upgrade and update tests. llvm-svn: 47296 2008-02-19 09:41:04 +08:00			`declare void @gl_EvalCoord1f(float)`
move V8 testcases here llvm-svn: 25986 2006-02-05 13:52:55 +08:00