public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug libstdc++/105262] New: Consider adding std::__new_allocator::allocate(size_type, nothrow_t)
@ 2022-04-13 11:40 redi at gcc dot gnu.org
  0 siblings, 0 replies; only message in thread
From: redi at gcc dot gnu.org @ 2022-04-13 11:40 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105262

            Bug ID: 105262
           Summary: Consider adding
                    std::__new_allocator::allocate(size_type, nothrow_t)
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: P3
         Component: libstdc++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: redi at gcc dot gnu.org
  Target Milestone: ---

It would be useful to be able to use std::__new_allocator as an abstraction for
the nothrow versions of operator new. That way all the logic for choosing
whether to use aligned new/delete and whether __builtin_operator_new is
available would only be in one place.

It could be used in std::basic_stacktrace::_Impl::_M_allocate and in
std::get_temporary_buffer.

N.B. I proposed this in
http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2016/p0401r0.html#Nothrow.overload.of.allocate..

^ permalink raw reply	[flat|nested] only message in thread
only message in thread, other threads:[~2022-04-13 11:40 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-04-13 11:40 [Bug libstdc++/105262] New: Consider adding std::__new_allocator::allocate(size_type, nothrow_t) redi at gcc dot gnu.org

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).