public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "de34 at live dot cn" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/104542] New: make_obj_using_allocator and uninitialized_construct_using_allocator lack constexpr Date: Tue, 15 Feb 2022 06:36:08 +0000 [thread overview] Message-ID: <bug-104542-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104542 Bug ID: 104542 Summary: make_obj_using_allocator and uninitialized_construct_using_allocator lack constexpr Product: gcc Version: 12.0 Status: UNCONFIRMED Keywords: rejects-valid Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: de34 at live dot cn Target Milestone: --- std::make_obj_using_allocator and std::uninitialized_construct_using_allocator are constexpr in C++20 (LWG3185, LWG3321), but currently they are not constexpr in libstdc++. I think the related compiler support for std::construct_at is available since gcc11 (partially available in gcc10), so these functions are reasonably constexpr in libstdc++ now, and this fix should be backported to gcc 10/11. wandbox links: gcc10 with manual constexpr (lacks support for CZ044): https://wandbox.org/permlink/CvSEindXZa3MMRT5 gcc11&12 with manual constexpr: https://wandbox.org/permlink/8i7oM16jGxlmz3FC https://wandbox.org/permlink/VHQJhGINcdpNC0Eh gcc11&12 with std versions, currently doesn't compile: https://wandbox.org/permlink/ZUx1xZIOphwxcJhS https://wandbox.org/permlink/f8uujdEoMUPbsUIq
next reply other threads:[~2022-02-15 6:36 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-15 6:36 de34 at live dot cn [this message] 2022-02-15 9:52 ` [Bug libstdc++/104542] " redi at gcc dot gnu.org 2022-02-15 14:28 ` cvs-commit at gcc dot gnu.org 2022-04-04 11:46 ` cvs-commit at gcc dot gnu.org 2022-04-04 21:22 ` redi at gcc dot gnu.org
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-104542-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).