llvm-project/llvm/test/CodeGen/PowerPC/unsafe-math.ll

; RUN: llc < %s -mattr=-vsx -march=ppc32 | grep fmul | count 2
; RUN: llc < %s -mattr=-vsx -march=ppc32 -enable-unsafe-fp-math | \
; RUN:   grep fmul | count 1

define double @foo(double %X) nounwind {
        %tmp1 = fmul double %X, 1.23
        %tmp2 = fmul double %tmp1, 4.124
        ret double %tmp2
}
[PPC] Adjust some PowerPC tests to account for presence/absence of VSX Patch by Bill Seurer; committed on his behalf. These test cases generate slightly different code sequences when VSX is activated and thus fail. The update turns off VSX explicitly for the existing checks and then adds a second set of checks for most of them that test the VSX instruction output. llvm-svn: 220019 2014-10-17 09:41:22 +08:00			`; RUN: llc < %s -mattr=-vsx -march=ppc32 \| grep fmul \| count 2`
			`; RUN: llc < %s -mattr=-vsx -march=ppc32 -enable-unsafe-fp-math \| \`
Convert tests using "\| wc -l \| grep ..." to use the count script. llvm-svn: 41097 2007-08-15 21:36:28 +08:00			`; RUN: grep fmul \| count 1`
new testcase llvm-svn: 33023 2007-01-09 07:03:19 +08:00
add some nounwind's. llvm-svn: 119086 2010-11-15 06:22:14 +08:00			`define double @foo(double %X) nounwind {`
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			`%tmp1 = fmul double %X, 1.23`
			`%tmp2 = fmul double %tmp1, 4.124`
new testcase llvm-svn: 33023 2007-01-09 07:03:19 +08:00			`ret double %tmp2`
			`}`