llvm-6502/test/Transforms/IndVarSimplify/2008-11-25-APFloatAssert.ll

; RUN: llvm-as < %s | opt -indvars

define void @t() nounwind {
entry:
	br label %bb23.i91

bb23.i91:		; preds = %bb23.i91, %entry
	%result.0.i89 = phi ppc_fp128 [ 0xM00000000000000000000000000000000, %entry ], [ %0, %bb23.i91 ]		; <ppc_fp128> [#uses=2]
	%0 = fmul ppc_fp128 %result.0.i89, %result.0.i89		; <ppc_fp128> [#uses=1]
	br label %bb23.i91
}
convertToSignExtendedInteger should return opInvalidOp instead of asserting if sematics of float does not allow arithmetics. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@60042 91177308-0d34-0410-b5e6-96231b3b80d8 2008-11-25 19:00:29 +00:00			`; RUN: llvm-as < %s \| opt -indvars`

			`define void @t() nounwind {`
			`entry:`
			`br label %bb23.i91`

			`bb23.i91: ; preds = %bb23.i91, %entry`
			`%result.0.i89 = phi ppc_fp128 [ 0xM00000000000000000000000000000000, %entry ], [ %0, %bb23.i91 ] ; <ppc_fp128> [#uses=2]`
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			`%0 = fmul ppc_fp128 %result.0.i89, %result.0.i89 ; <ppc_fp128> [#uses=1]`
convertToSignExtendedInteger should return opInvalidOp instead of asserting if sematics of float does not allow arithmetics. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@60042 91177308-0d34-0410-b5e6-96231b3b80d8 2008-11-25 19:00:29 +00:00			`br label %bb23.i91`
			`}`