summaryrefslogtreecommitdiff
path: root/test/asan/TestCases/deep_stack_uaf.cc
diff options
context:
space:
mode:
authorRenato Golin <renato.golin@linaro.org>2016-11-19 21:19:19 +0000
committerRenato Golin <renato.golin@linaro.org>2016-11-19 21:19:19 +0000
commited845eb8a5232110728ef99f51958b759d7e0f1c (patch)
tree189556d0de6f21082f06f6dc67fd28c0926f7479 /test/asan/TestCases/deep_stack_uaf.cc
parent4eb08d1dbd9bdfe505c146fcfbcdf94e9d26a173 (diff)
[ARM|ASAN] Disabling more unstable ASAN tests
We're seeying these errors with GCC and Clang on different systems, while some other identical OSs on different boards fail. Like many other ASAN tests, there seem to be no easy way to investigate this other than someone familiar with the sanitizer code and the ARM libraries. At least, for now, we'll silence the bots. I'll create a bugzilla entry. git-svn-id: https://llvm.org/svn/llvm-project/compiler-rt/trunk@287464 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'test/asan/TestCases/deep_stack_uaf.cc')
-rw-r--r--test/asan/TestCases/deep_stack_uaf.cc3
1 files changed, 1 insertions, 2 deletions
diff --git a/test/asan/TestCases/deep_stack_uaf.cc b/test/asan/TestCases/deep_stack_uaf.cc
index 95032f2bd..bdf0dbdb4 100644
--- a/test/asan/TestCases/deep_stack_uaf.cc
+++ b/test/asan/TestCases/deep_stack_uaf.cc
@@ -2,8 +2,7 @@
// RUN: %clangxx_asan -O0 %s -o %t 2>&1
// RUN: %env_asan_opts=malloc_context_size=120:redzone=512 not %run %t 2>&1 | FileCheck %s
-// XFAIL: arm-linux-gnueabi
-// XFAIL: armv7l-unknown-linux-gnueabihf
+// REQUIRES: stable-runtime
#include <stdlib.h>
#include <stdio.h>