summaryrefslogtreecommitdiffstats
path: root/llvm/test
diff options
context:
space:
mode:
authorArnaud A. de Grandmaison <arnaud.degrandmaison@arm.com>2014-09-11 10:39:52 +0000
committerArnaud A. de Grandmaison <arnaud.degrandmaison@arm.com>2014-09-11 10:39:52 +0000
commit36902667398162c1795c6aae2931d9cab91e429d (patch)
treea3e383de7a4d2ea29612b5358df1a7642892d562 /llvm/test
parent0c1249ac6087afc4e1cbbfefecad78647de8d5e9 (diff)
downloadbcm5719-llvm-36902667398162c1795c6aae2931d9cab91e429d.tar.gz
bcm5719-llvm-36902667398162c1795c6aae2931d9cab91e429d.zip
[AArch64] Reenable the PBQP test now that the leak issue has been fixed.
David Blaikie's commits r217563 & r217564, which added shared_ptr to the CostPool have fixed some memory leak issues exposed by the PBQP with coalescing constraints. The sanitizer bot was failing because of those leaks. Now that the leaks are gone, we can reenable the aarch64/pbqp test. llvm-svn: 217580
Diffstat (limited to 'llvm/test')
-rw-r--r--llvm/test/CodeGen/AArch64/PBQP.ll14
1 files changed, 14 insertions, 0 deletions
diff --git a/llvm/test/CodeGen/AArch64/PBQP.ll b/llvm/test/CodeGen/AArch64/PBQP.ll
new file mode 100644
index 00000000000..491998e1e30
--- /dev/null
+++ b/llvm/test/CodeGen/AArch64/PBQP.ll
@@ -0,0 +1,14 @@
+; RUN: llc -mtriple=aarch64-linux-gnu -mcpu=cortex-a57 -aarch64-pbqp -o - %s | FileCheck %s
+
+define i32 @foo(i32 %a) {
+; CHECK-LABEL: foo:
+; CHECK: bl bar
+; CHECK-NEXT: bl baz
+ %call = call i32 @bar(i32 %a)
+ %call1 = call i32 @baz(i32 %call)
+ ret i32 %call1
+}
+
+declare i32 @bar(i32)
+declare i32 @baz(i32)
+
OpenPOWER on IntegriCloud