aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/Support/CommandLine.cpp
diff options
context:
space:
mode:
authorMartin Storsjö <martin@martin.st>2022-01-09 22:32:47 +0000
committerMartin Storsjö <martin@martin.st>2022-01-26 11:52:32 +0200
commita2aea7199a5c99260d27ee37f3cda8f752478c02 (patch)
treedfde076c8d75a927a428af133ed5921e9269e423 /llvm/lib/Support/CommandLine.cpp
parentbec4e865dedfa36fc9c03139268f405e32e9be1d (diff)
downloadllvm-a2aea7199a5c99260d27ee37f3cda8f752478c02.zip
llvm-a2aea7199a5c99260d27ee37f3cda8f752478c02.tar.gz
llvm-a2aea7199a5c99260d27ee37f3cda8f752478c02.tar.bz2
[libcxx] [test] Fix mismatches between _aligned_malloc and free() on Windows
This allows getting rid of one case of LIBCXX-WINDOWS-FIXME. The fixme comment was inaccurate; aligned allocation functions are provided these days, but the test kept failing as it was using mismatched allocation and free functions. A similar issue was fixed earlier, in 6596778b46ba69517191e7397289228168064ff4. That test was fixed by overriding the aligned `operator new` too, and returning a dummy fixed allocation instead. As this test is libcxx specific, it can use the internal `std::__libcpp_aligned_free()` instead, to match libcxx's internal aligned `operator new`. Differential Revision: https://reviews.llvm.org/D118190
Diffstat (limited to 'llvm/lib/Support/CommandLine.cpp')
0 files changed, 0 insertions, 0 deletions