diff options
| author | Jonas Devlieghere <jonas@devlieghere.com> | 2023-05-15 22:47:12 -0700 |
|---|---|---|
| committer | Jonas Devlieghere <jonas@devlieghere.com> | 2023-05-16 09:27:09 -0700 |
| commit | 10a50762caa6ac17dd063b28863a2ec60576c6f7 (patch) | |
| tree | 83099cec25705788995dc9974fc8c2fcad22044e /llvm/lib/Target/RISCV/Disassembler/RISCVDisassembler.cpp | |
| parent | 9e37a7bd1f38fed4e00704d561b3897fe8915c4c (diff) | |
| download | llvm-10a50762caa6ac17dd063b28863a2ec60576c6f7.zip llvm-10a50762caa6ac17dd063b28863a2ec60576c6f7.tar.gz llvm-10a50762caa6ac17dd063b28863a2ec60576c6f7.tar.bz2 | |
[lldb] Define lldbassert based on NDEBUG instead of LLDB_CONFIGURATION_DEBUG
Whether assertions are enabled or not is orthogonal to the build type
which could lead to surprising behavior for lldbassert. Previously, when
doing a debug build with assertions disabled, lldbassert would become a
NOOP, rather than printing an error like it does in a release build. By
definining lldbassert in terms of NDEBUG, it behaves like a regular
assert when assertions are enabled, and like a soft assert.
Differential revision: https://reviews.llvm.org/D150639
Diffstat (limited to 'llvm/lib/Target/RISCV/Disassembler/RISCVDisassembler.cpp')
0 files changed, 0 insertions, 0 deletions