llvm-6502/test/ExecutionEngine/2003-01-10-FUCOM.ll

; RUN: lli %s > /dev/null

define i32 @main() {
	%X = fadd double 0.000000e+00, 1.000000e+00		; <double> [#uses=1]
	%Y = fsub double 0.000000e+00, 1.000000e+00		; <double> [#uses=2]
	%Z = fcmp oeq double %X, %Y		; <i1> [#uses=0]
	fadd double %Y, 0.000000e+00		; <double>:1 [#uses=0]
	ret i32 0
}
lli: Switch to using ParseIRFile, for consistency with other LLVM tools. - Also, switch tests to not using llvm-as. They run 20% faster now, not that it matters. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@118952 91177308-0d34-0410-b5e6-96231b3b80d8 2010-11-13 00:28:01 +00:00			`; RUN: lli %s > /dev/null`
Adding RUN lines. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@17536 91177308-0d34-0410-b5e6-96231b3b80d8 2004-11-06 23:32:43 +00:00
Remove llvm-upgrade and update tests. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@48137 91177308-0d34-0410-b5e6-96231b3b80d8 2008-03-10 07:21:50 +00:00			`define i32 @main() {`
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 git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@72897 91177308-0d34-0410-b5e6-96231b3b80d8 2009-06-04 22:49:04 +00:00			`%X = fadd double 0.000000e+00, 1.000000e+00 ; <double> [#uses=1]`
			`%Y = fsub double 0.000000e+00, 1.000000e+00 ; <double> [#uses=2]`
Remove llvm-upgrade and update tests. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@48137 91177308-0d34-0410-b5e6-96231b3b80d8 2008-03-10 07:21:50 +00:00			`%Z = fcmp oeq double %X, %Y ; <i1> [#uses=0]`
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 git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@72897 91177308-0d34-0410-b5e6-96231b3b80d8 2009-06-04 22:49:04 +00:00			`fadd double %Y, 0.000000e+00 ; <double>:1 [#uses=0]`
Remove llvm-upgrade and update tests. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@48137 91177308-0d34-0410-b5e6-96231b3b80d8 2008-03-10 07:21:50 +00:00			`ret i32 0`
New testcases git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@5261 91177308-0d34-0410-b5e6-96231b3b80d8 2003-01-13 01:03:16 +00:00			`}`
Remove llvm-upgrade and update tests. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@48137 91177308-0d34-0410-b5e6-96231b3b80d8 2008-03-10 07:21:50 +00:00