llvm-mirror/test/CodeGen/PowerPC/vec_zero.ll

; RUN: llc -verify-machineinstrs < %s -march=ppc32 -mcpu=g5 | grep vxor

define void @foo(<4 x float>* %P) {
        %T = load <4 x float>, <4 x float>* %P               ; <<4 x float>> [#uses=1]
        %S = fadd <4 x float> zeroinitializer, %T                ; <<4 x float>> [#uses=1]
        store <4 x float> %S, <4 x float>* %P
        ret void
}
Adding -verify-machineinstrs option to PowerPC tests Currently we have a number of tests that fail with -verify-machineinstrs. To detect this cases earlier we add the option to the testcases with the exception of tests that will currently fail with this option. PR 27456 keeps track of this failures. No code review, as discussed with Hal Finkel. llvm-svn: 277624 2016-08-03 20:17:35 +02:00			`; RUN: llc -verify-machineinstrs < %s -march=ppc32 -mcpu=g5 \| grep vxor`
new testcase llvm-svn: 27058 2006-03-24 08:47:53 +01:00
Remove llvm-upgrade and update tests. llvm-svn: 47325 2008-02-19 09:07:33 +01:00			`define void @foo(<4 x float>* %P) {`
[opaque pointer type] Add textual IR support for explicit type parameter to load instruction Essentially the same as the GEP change in r230786. A similar migration script can be used to update test cases, though a few more test case improvements/changes were required this time around: (r229269-r229278) import fileinput import sys import re pat = re.compile(r"((?:=\|:\|^)\sload (?:atomic )?(?:volatile )?(.?))(\| addrspace\(\d+\) )\($\| (?:%\|@\|null\|undef\|blockaddress\|getelementptr\|addrspacecast\|bitcast\|inttoptr\|\[\[[a-zA-Z]\|\{\{).$)") for line in sys.stdin: sys.stdout.write(re.sub(pat, r"\1, \2\3*\4", line)) Reviewers: rafael, dexonsmith, grosser Differential Revision: http://reviews.llvm.org/D7649 llvm-svn: 230794 2015-02-27 22:17:42 +01:00			`%T = load <4 x float>, <4 x float>* %P ; <<4 x float>> [#uses=1]`
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			`%S = fadd <4 x float> zeroinitializer, %T ; <<4 x float>> [#uses=1]`
Remove llvm-upgrade and update tests. llvm-svn: 47325 2008-02-19 09:07:33 +01:00			`store <4 x float> %S, <4 x float>* %P`
			`ret void`
new testcase llvm-svn: 27058 2006-03-24 08:47:53 +01:00			`}`
Remove llvm-upgrade and update tests. llvm-svn: 47325 2008-02-19 09:07:33 +01:00