diff options
| author | Martin Storsjö <martin@martin.st> | 2025-09-30 18:21:25 +0300 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-09-30 11:21:25 -0400 |
| commit | 870e4f9a525d07d39b1e43db6c872d6c34c1bcd8 (patch) | |
| tree | 39f30d8ae3037b3d8f3b274282ddef2b3230b4d9 /clang/test/CodeGenCXX/c99-variable-length-array.cpp | |
| parent | 981122696701d3c3897af267afd73bbefa61c3d4 (diff) | |
| download | llvm-870e4f9a525d07d39b1e43db6c872d6c34c1bcd8.zip llvm-870e4f9a525d07d39b1e43db6c872d6c34c1bcd8.tar.gz llvm-870e4f9a525d07d39b1e43db6c872d6c34c1bcd8.tar.bz2 | |
[libc++][test] Use ASSERT_WITH_LIBRARY_INTERNAL_ALLOCATIONS in more places (#144339)
ASSERT_WITH_LIBRARY_INTERNAL_ALLOCATIONS allows waiving asserts, for
cases when we can't count allocations that happen within the libc++
shared library.
When compiling with optimization, it is possible that some calls end up
generated inline, where the overridden operator new/delete do get called
(counting those calls), whereas the compiler may decide to leave some
calls to the external definition (inside the shared library, where we
can't count the calls).
In particular, in one case, a non-optimized build calls
_ZNSt3__112basic_stringIcNS_11char_traitsIcEENS_9allocatorIcEEED1Ev from
the DLL, while it gets inlined (including direct calls to operator
delete) when built with optimization.
Therefore; for the cases where we can't count allocations internally
within the library, waive these asserts.
This fixes all testcases in mingw mode, when built with optimization
enabled.
Diffstat (limited to 'clang/test/CodeGenCXX/c99-variable-length-array.cpp')
0 files changed, 0 insertions, 0 deletions