diff options
| author | Duo Wang <duow1@uci.edu> | 2024-01-05 01:59:26 -0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-01-05 09:59:26 +0000 |
| commit | c458f928fad7bbcf08ab1da9949eb2969fc9f89c (patch) | |
| tree | 1f8f1f0fb708ec1bc1f574e5f03e4c4c8c0569b5 /llvm/lib/CodeGen | |
| parent | 0eefcaf96d2900a4f3009026a3673ed3b7793fcc (diff) | |
| download | llvm-c458f928fad7bbcf08ab1da9949eb2969fc9f89c.zip llvm-c458f928fad7bbcf08ab1da9949eb2969fc9f89c.tar.gz llvm-c458f928fad7bbcf08ab1da9949eb2969fc9f89c.tar.bz2 | |
[NFC][clang][test][asan] Make `instantiation-depth-default.cpp` a valid test case under `asan` and `ubsan` configs (#75254)
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.
Diffstat (limited to 'llvm/lib/CodeGen')
0 files changed, 0 insertions, 0 deletions