summaryrefslogtreecommitdiffstats
path: root/llvm/test
diff options
context:
space:
mode:
authorDan Gohman <gohman@apple.com>2009-06-19 23:23:27 +0000
committerDan Gohman <gohman@apple.com>2009-06-19 23:23:27 +0000
commitcc31110b95befccaa410c33febaf53ac0e2e82f0 (patch)
treefb84ec91e8daa669313b1e23d3ef721e5bd97744 /llvm/test
parent88be5cf01fef41ba45a5483032e493e7c507f85f (diff)
downloadbcm5719-llvm-cc31110b95befccaa410c33febaf53ac0e2e82f0.tar.gz
bcm5719-llvm-cc31110b95befccaa410c33febaf53ac0e2e82f0.zip
Re-apply r73718, now that the fix in r73787 is in, and add a
hand-crafted testcase which demonstrates the bug that was exposed in 254.gap. llvm-svn: 73793
Diffstat (limited to 'llvm/test')
-rw-r--r--llvm/test/CodeGen/X86/optimize-max-0.ll1
-rw-r--r--llvm/test/CodeGen/X86/optimize-max-1.ll1
-rw-r--r--llvm/test/CodeGen/X86/optimize-max-2.ll30
3 files changed, 30 insertions, 2 deletions
diff --git a/llvm/test/CodeGen/X86/optimize-max-0.ll b/llvm/test/CodeGen/X86/optimize-max-0.ll
index 78bb669e331..90c14565e9a 100644
--- a/llvm/test/CodeGen/X86/optimize-max-0.ll
+++ b/llvm/test/CodeGen/X86/optimize-max-0.ll
@@ -1,5 +1,4 @@
; RUN: llvm-as < %s | llc -march=x86 | not grep cmov
-; XFAIL: *
; LSR should be able to eliminate the max computations by
; making the loops use slt/ult comparisons instead of ne comparisons.
diff --git a/llvm/test/CodeGen/X86/optimize-max-1.ll b/llvm/test/CodeGen/X86/optimize-max-1.ll
index b9e6688837a..084e1818f5d 100644
--- a/llvm/test/CodeGen/X86/optimize-max-1.ll
+++ b/llvm/test/CodeGen/X86/optimize-max-1.ll
@@ -1,5 +1,4 @@
; RUN: llvm-as < %s | llc -march=x86-64 | not grep cmov
-; XFAIL: *
; LSR should be able to eliminate both smax and umax expressions
; in loop trip counts.
diff --git a/llvm/test/CodeGen/X86/optimize-max-2.ll b/llvm/test/CodeGen/X86/optimize-max-2.ll
new file mode 100644
index 00000000000..effc3fc737d
--- /dev/null
+++ b/llvm/test/CodeGen/X86/optimize-max-2.ll
@@ -0,0 +1,30 @@
+; RUN: llvm-as < %s | llc -march=x86-64 > %t
+; RUN: grep cmov %t | count 2
+; RUN: grep jne %t | count 1
+
+; LSR's OptimizeMax function shouldn't try to eliminate this max, because
+; it has three operands.
+
+target datalayout = "e-p:64:64:64-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64:64:64-f32:32:32-f64:64:64-v64:64:64-v128:128:128-a0:0:64-s0:64:64-f80:128:128"
+
+define void @foo(double* nocapture %p, i64 %x, i64 %y) nounwind {
+entry:
+ %tmp = icmp eq i64 %y, 0 ; <i1> [#uses=1]
+ %umax = select i1 %tmp, i64 1, i64 %y ; <i64> [#uses=2]
+ %tmp8 = icmp ugt i64 %umax, %x ; <i1> [#uses=1]
+ %umax9 = select i1 %tmp8, i64 %umax, i64 %x ; <i64> [#uses=1]
+ br label %bb4
+
+bb4: ; preds = %bb4, %entry
+ %i.07 = phi i64 [ 0, %entry ], [ %2, %bb4 ] ; <i64> [#uses=2]
+ %scevgep = getelementptr double* %p, i64 %i.07 ; <double*> [#uses=2]
+ %0 = load double* %scevgep, align 8 ; <double> [#uses=1]
+ %1 = fmul double %0, 2.000000e+00 ; <double> [#uses=1]
+ store double %1, double* %scevgep, align 8
+ %2 = add i64 %i.07, 1 ; <i64> [#uses=2]
+ %exitcond = icmp eq i64 %2, %umax9 ; <i1> [#uses=1]
+ br i1 %exitcond, label %return, label %bb4
+
+return: ; preds = %bb4
+ ret void
+}
OpenPOWER on IntegriCloud