llvm-6502/test/CodeGen/Generic/storetrunc-fp.ll

; RUN: llvm-as < %s | llc

define void @foo(double %a, double %b, float* %fp) {
	%c = fadd double %a, %b
	%d = fptrunc double %c to float
	store float %d, float* %fp
	ret void
}
new testcase. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@46139 91177308-0d34-0410-b5e6-96231b3b80d8 2008-01-17 19:47:23 +00:00			`; RUN: llvm-as < %s \| llc`

			`define void @foo(double %a, double %b, float* %fp) {`
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			`%c = fadd double %a, %b`
new testcase. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@46139 91177308-0d34-0410-b5e6-96231b3b80d8 2008-01-17 19:47:23 +00:00			`%d = fptrunc double %c to float`
			`store float %d, float* %fp`
			`ret void`
			`}`