Another attempt to fix the build bot breaks after r360426

The test case checks were produced by the update_test_checks.py
scripts and I assumed that is sufficient. However, the behaviour
is different with different default target triples. Specify the
triple explicitly in the test case.

If this doesn't clean up the build bot breaks, I'll remove the test
case until I can get to the bottom of why the behaviour on build bots
is different from my machine.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@360434 91177308-0d34-0410-b5e6-96231b3b80d8

diff --git a/test/Transforms/PhaseOrdering/reassociate-after-unroll.ll b/test/Transforms/PhaseOrdering/reassociate-after-unroll.ll
index 0cb7b558a78311c4ca24ae46cee6f6316b1350c1..89d6af1d2e9bff5c2a119e628ce2101b06748b31 100644 (file)
--- a/test/Transforms/PhaseOrdering/reassociate-after-unroll.ll
+++ b/test/Transforms/PhaseOrdering/reassociate-after-unroll.ll
@@ -1,7 +1,6 @@
 ; NOTE: Assertions have been autogenerated by utils/update_test_checks.py
-; REQUIRES: asserts
-; RUN: opt -O2 -S < %s | FileCheck %s
-; RUN: opt -passes='default<O2>' -S < %s | FileCheck %s --check-prefix=NPM
+; RUN: opt -mtriple=powerpc64le-unknown-unknown -O2 -S < %s | FileCheck %s
+; RUN: opt -mtriple=powerpc64le-unknown-unknown -passes='default<O2>' -S < %s | FileCheck %s --check-prefix=NPM
 
 target datalayout = "e-m:e-i64:64-n32:64"
 target triple = "powerpc64le-unknown-linux-gnu"