llvm-project.git/llvm/lib/Support/MemAlloc.cpp, branch users/nico/python-1 Unnamed repository; edit this file 'description' to name the repository. [Support] Report OOM from `allocate_buffer` (#85449) 2025-01-27T17:04:43+00:00 Josh Stone jistone@redhat.com 2025-01-27T17:04:43+00:00 b80965efc1ea3f30cbdac090d869b1000fca5d2b Previously, it called `::operator new` which may throw `std::bad_alloc`, regardless of whether LLVM itself was built with exception handling, and this can cause safety issues if outside code has destructors that will call back into LLVM. Now we use `::operator new(..., nothrow)` and call `llvm::report_bad_alloc_error` when allocation fails, which will abort when LLVM is built without exceptions. Ref: https://github.com/llvm/llvm-project/issues/85281 
Previously, it called `::operator new` which may throw `std::bad_alloc`,
regardless of whether LLVM itself was built with exception handling, and
this can cause safety issues if outside code has destructors that will
call back into LLVM. Now we use `::operator new(..., nothrow)` and call
`llvm::report_bad_alloc_error` when allocation fails, which will abort
when LLVM is built without exceptions.

Ref: https://github.com/llvm/llvm-project/issues/85281
 [Support] #include <new> for std::align_val_t 2022-01-25T18:40:00+00:00 Benjamin Kramer benny.kra@googlemail.com 2022-01-25T18:36:52+00:00 ce5b04cc048aa9b82355bbea21a062462553eb47 This is only used when aligned new is enabled. 
This is only used when aligned new is enabled.
Replicate attributes on definition to make MSVC less noisy 2020-04-25T00:02:00+00:00 Benjamin Kramer benny.kra@googlemail.com 2020-04-25T00:00:54+00:00 bc1ea2a2c5e177ad0034e445cd32b62d3b22ac90 warning C4565: 'llvm::allocate_buffer': redefinition; the symbol was previously declared with __declspec(restrict) 
warning C4565: 'llvm::allocate_buffer': redefinition; the symbol was previously declared with __declspec(restrict)
[ADT] Move allocate_buffer to MemAlloc.h and out of line 2020-04-24T11:32:50+00:00 Benjamin Kramer benny.kra@googlemail.com 2020-04-24T11:22:40+00:00 7aaff8fd2da2812a2b3cbc8a41af29774b10a7d6 There's an ABI breakage here if LLVM is compiled in C++14 without aligned allocation and a user tries to use the result with aligned allocation. If DenseMap or unique_function is used across that ABI boundary it will break (PR45413). Moving it out of line is a bit of a band-aid and LLVM doesn't really give ABI guarantees at this level, but given the number of complaints I've received over this it still seems worth fixing. 
There's an ABI breakage here if LLVM is compiled in C++14 without
aligned allocation and a user tries to use the result with aligned
allocation. If DenseMap or unique_function is used across that ABI
boundary it will break (PR45413). Moving it out of line is a bit of
a band-aid and LLVM doesn't really give ABI guarantees at this level,
but given the number of complaints I've received over this it still
seems worth fixing.