summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBenjamin Kramer <benny.kra@googlemail.com>2013-05-30 15:22:28 +0000
committerBenjamin Kramer <benny.kra@googlemail.com>2013-05-30 15:22:28 +0000
commit051ed0ae2dc9e20f01a9a459708728ec90805d92 (patch)
tree168b9623ab481503d99ed51c5553234b945266db
parent71f2df0e2800c8141d5926f1e37d68bf814ec1d6 (diff)
downloadllvm-051ed0ae2dc9e20f01a9a459708728ec90805d92.tar.gz
llvm-051ed0ae2dc9e20f01a9a459708728ec90805d92.tar.bz2
llvm-051ed0ae2dc9e20f01a9a459708728ec90805d92.tar.xz
Force fragile test to the atom scheduler model.
The pattern the test originally checked for doesn't occur on other -mcpu settings. On atom it's still there though slightly differently scheduled. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@182933 91177308-0d34-0410-b5e6-96231b3b80d8
-rw-r--r--test/CodeGen/X86/zext-sext.ll6
1 files changed, 4 insertions, 2 deletions
diff --git a/test/CodeGen/X86/zext-sext.ll b/test/CodeGen/X86/zext-sext.ll
index 2459f1fa25..87a6099c0c 100644
--- a/test/CodeGen/X86/zext-sext.ll
+++ b/test/CodeGen/X86/zext-sext.ll
@@ -1,4 +1,4 @@
-; RUN: llc < %s -march=x86-64 | FileCheck %s
+; RUN: llc < %s -march=x86-64 -mcpu=atom | FileCheck %s
; <rdar://problem/8006248>
; This randomly started passing after an unrelated change, if it fails again it
@@ -34,9 +34,11 @@ entry:
%tmp12 = add i64 %tmp11, 5089792279245435153
; CHECK: addl $2138875574, %e[[REGISTER_zext:[a-z0-9]+]]
+; CHECK-NEXT: cmpl $-8608074, %e[[REGISTER_zext]]
; CHECK-NEXT: movslq %e[[REGISTER_zext]], [[REGISTER_tmp:%r[a-z0-9]+]]
; CHECK: movq [[REGISTER_tmp]], [[REGISTER_sext:%r[a-z0-9]+]]
-; CHECK-NEXT: subq %r[[REGISTER_zext]], [[REGISTER_sext]]
+; CHECK-NOT: [[REGISTER_zext]]
+; CHECK: subq %r[[REGISTER_zext]], [[REGISTER_sext]]
%tmp13 = sub i64 %tmp12, 2138875574
%tmp14 = zext i32 %tmp4 to i64