public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/105262] New: Consider adding std::__new_allocator::allocate(size_type, nothrow_t) Date: Wed, 13 Apr 2022 11:40:27 +0000 [thread overview] Message-ID: <bug-105262-4@http.gcc.gnu.org/bugzilla/> (raw) 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..
reply other threads:[~2022-04-13 11:40 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-105262-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
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).