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

; RUN: opt < %s -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
}
Change tests from "opt %s" to "opt < %s" so that opt doesn't see the input filename so that opt doesn't print the input filename in the output so that grep lines in the tests don't unintentionally match strings in the input filename. llvm-svn: 81537 2009-09-11 20:01:28 +02:00			`; RUN: opt < %s -indvars`
convertToSignExtendedInteger should return opInvalidOp instead of asserting if sematics of float does not allow arithmetics. llvm-svn: 60042 2008-11-25 20:00:29 +01:00
			`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 llvm-svn: 72897 2009-06-05 00:49:04 +02: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. llvm-svn: 60042 2008-11-25 20:00:29 +01:00			`br label %bb23.i91`
			`}`