mirror of
https://github.com/capstone-engine/llvm-capstone.git
synced 2025-05-13 17:37:00 +00:00
c458f928fa
Clang test `instantiation-depth-default.cpp` fails on Windows when built with `ubsan` due to extra warnings printed by the compiler: ```console File instantiation-depth-default.cpp Line 11: stack nearly exhausted; compilation time may suffer, and crashes due to stack overflow are likely ``` The test case was disabled for `asan` in 571a647 because of the extra stack usage. Since `ubsan` also increases stack usage, seems like the two configs should be treated uniformly. On the other hand, we might be able to re-enable this test case for `asan`. During some preliminary testing on Windows, Linux, and macOS with the host compiler being as old as clang-10, the test case exited successfully if the `stack-exhausted` warnings are suppressed, though I haven't done exhaustive testing across platforms and clang versions. Any insights into whether this change will introduce any risks to existing buildbots is appreciated. Enabling this test case for `asan` helps to improve our test coverage, but if it causes problems on any buildbot, marking it as unsupported for `ubsan` is also a viable solution.
15 lines
710 B
C++
15 lines
710 B
C++
// RUN: %clang_cc1 -fsyntax-only -verify -ftemplate-backtrace-limit=2 %if {{asan|ubsan}} %{ -Wno-stack-exhausted %} %s
|
|
// The default stack size on NetBSD is too small for this test.
|
|
// UNSUPPORTED: system-netbsd
|
|
|
|
template<int N, typename T> struct X : X<N+1, T*> {};
|
|
// expected-error-re@5 {{recursive template instantiation exceeded maximum depth of 1024{{$}}}}
|
|
// expected-note@5 {{instantiation of template class}}
|
|
// expected-note@5 {{skipping 1023 contexts in backtrace}}
|
|
// expected-note@5 {{use -ftemplate-depth=N to increase recursive template instantiation depth}}
|
|
|
|
X<0, int> x; // expected-note {{in instantiation of}}
|
|
|
|
// FIXME: It crashes. Investigating.
|
|
// UNSUPPORTED: target={{.*-windows-gnu}}
|