diff options
| author | Louis Dionne <ldionne.2@gmail.com> | 2023-06-19 14:44:21 -0400 |
|---|---|---|
| committer | Louis Dionne <ldionne.2@gmail.com> | 2023-06-21 08:34:51 -0400 |
| commit | 9ff36c24a04d9aae61ae09f460c3344f16bb40dc (patch) | |
| tree | 1cd1e7c1ec698dd4a6f7ed52718fe64f0bee880f /llvm/lib/Target/RISCV/Disassembler/RISCVDisassembler.cpp | |
| parent | 699e64c0d96f9d899cbe868f4e7818c8c3b90ff4 (diff) | |
| download | llvm-9ff36c24a04d9aae61ae09f460c3344f16bb40dc.zip llvm-9ff36c24a04d9aae61ae09f460c3344f16bb40dc.tar.gz llvm-9ff36c24a04d9aae61ae09f460c3344f16bb40dc.tar.bz2 | |
[libc++] Guard terminate_successful with TEST_HAS_NO_EXCEPTIONS
This one is a bit twisted. Some platforms don't have support for
exiting in a clean manner, so they don't provide std::exit(). As
a result, defining `terminate_successful()` on those platforms won't
work, and the PSTL tests that rely on `terminate_successful()` also
won't work.
However, we don't have a notion of "no clean termination" in libc++,
so we can't properly guard this. Since embedded platforms that don't
support clean termination usually also don't enable exceptions, we
don't need to be able to run those `terminate_successful` PSTL tests,
and guarding the definition of `terminate_successful` with
TEST_HAS_NO_EXCEPTIONS works pretty well.
This is kind of a hack for the lack of having a concept of "no clean
termination" in the library and in the test suite.
Differential Revision: https://reviews.llvm.org/D153302
Diffstat (limited to 'llvm/lib/Target/RISCV/Disassembler/RISCVDisassembler.cpp')
0 files changed, 0 insertions, 0 deletions