llvm-project/llvm/test/Transforms/Reassociate/2006-04-27-ReassociateVecto...

; RUN: opt < %s -reassociate -disable-output

define void @foo() {
	%tmp162 = fsub <4 x float> zeroinitializer, zeroinitializer		; <<4 x float>> [#uses=1]
	%tmp164 = fmul <4 x float> zeroinitializer, %tmp162		; <<4 x float>> [#uses=0]
	ret void
}
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-12 02:01:28 +08:00			`; RUN: opt < %s -reassociate -disable-output`
new testcase llvm-svn: 28006 2006-04-28 12:14:29 +08:00
Upgrade tests to not use llvm-upgrade. llvm-svn: 48530 2008-03-19 12:36:04 +08:00			`define void @foo() {`
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			`%tmp162 = fsub <4 x float> zeroinitializer, zeroinitializer ; <<4 x float>> [#uses=1]`
			`%tmp164 = fmul <4 x float> zeroinitializer, %tmp162 ; <<4 x float>> [#uses=0]`
new testcase llvm-svn: 28006 2006-04-28 12:14:29 +08:00			`ret void`
			`}`
Upgrade tests to not use llvm-upgrade. llvm-svn: 48530 2008-03-19 12:36:04 +08:00