[compiler-rt] c875567 - [asan,test] Disable alloca_loop_unpoisoning.cpp on s390{{.*}}

[Fangrui Song via llvm-commits]

Author: Fangrui Song
Date: 2024-01-19T00:39:23-08:00
New Revision: c875567af352716e703a49c9445f5dc1d3cf0063

URL: https://github.com/llvm/llvm-project/commit/c875567af352716e703a49c9445f5dc1d3cf0063
DIFF: https://github.com/llvm/llvm-project/commit/c875567af352716e703a49c9445f5dc1d3cf0063.diff

LOG: [asan,test] Disable alloca_loop_unpoisoning.cpp on s390{{.*}}

The test (from https://reviews.llvm.org/D7098) is about the interaction
of VLA and alloca where the VLA causes alloca to have the same address.
This is mostly about behavior checking and less about instrumentation
correctness, so I think it is fair to disable it for a platform that
does not work after StackSafetyAnalysis is enabled by default (#77210).

Added: 
    

Modified: 
    compiler-rt/test/asan/TestCases/alloca_loop_unpoisoning.cpp

Removed: 
    


################################################################################
diff  --git a/compiler-rt/test/asan/TestCases/alloca_loop_unpoisoning.cpp b/compiler-rt/test/asan/TestCases/alloca_loop_unpoisoning.cpp
index af6ca2163195a0..ac25a4faa2dc1b 100644
--- a/compiler-rt/test/asan/TestCases/alloca_loop_unpoisoning.cpp
+++ b/compiler-rt/test/asan/TestCases/alloca_loop_unpoisoning.cpp
@@ -2,6 +2,7 @@
 // RUN: %env_asan_opts=detect_stack_use_after_return=0 %run %t 2>&1
 //
 // REQUIRES: stable-runtime
+// UNSUPPORTED: target=s390{{.*}}
 
 // This testcase checks that allocas and VLAs inside loop are correctly unpoisoned.