Skip to content

[Support] Use malloc instead of non-throwing new #92157

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
May 15, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 9 additions & 2 deletions llvm/lib/Support/MemoryBuffer.cpp
Original file line number Diff line number Diff line change
Expand Up @@ -98,7 +98,7 @@ class MemoryBufferMem : public MB {

/// Disable sized deallocation for MemoryBufferMem, because it has
/// tail-allocated data.
void operator delete(void *p) { ::operator delete(p); }
void operator delete(void *p) { std::free(p); }

StringRef getBufferIdentifier() const override {
// The name is stored after the class itself.
Expand Down Expand Up @@ -315,7 +315,14 @@ WritableMemoryBuffer::getNewUninitMemBuffer(size_t Size,
size_t RealLen = StringLen + Size + 1 + BufAlign.value();
if (RealLen <= Size) // Check for rollover.
return nullptr;
char *Mem = static_cast<char*>(operator new(RealLen, std::nothrow));
// We use a call to malloc() rather than a call to a non-throwing operator
// new() because LLVM unconditionally installs an out of memory new handler
// when exceptions are disabled. This new handler intentionally crashes to
// aid with debugging, but that makes non-throwing new calls unhelpful.
// See MemoryBufferMem::operator delete() for the paired call to free(), and
// llvm::install_out_of_memory_new_handler() for the installation of the
// custom new handler.
char *Mem = static_cast<char *>(std::malloc(RealLen));
if (!Mem)
return nullptr;

Expand Down
Loading