public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "unlvsur at live dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/111353] New: bits/new_allocator.h: No such file or directory in freestanding C++ toolchain Date: Sat, 09 Sep 2023 02:08:19 +0000 [thread overview] Message-ID: <bug-111353-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111353 Bug ID: 111353 Summary: bits/new_allocator.h: No such file or directory in freestanding C++ toolchain Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: unlvsur at live dot com Target Milestone: --- D:/toolchains/gnu/x86_64-w64-mingw32/x86_64-elf/x86_64-elf/include/c++/14.0.0/x86_64-elf/bits/c++allocator.h:33:10: fatal error: bits/new_allocator.h: No such file or directory 33 | #include <bits/new_allocator.h> | ^~~~~~~~~~~~~~~~~~~~~~ As I reported to wg21 before, there is no way to allocate memory in constexpr context for freestanding. clang provides __builtin_operator_new and __builtin_operator_delete. Maybe gcc needs that too?
next reply other threads:[~2023-09-09 2:08 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-09 2:08 unlvsur at live dot com [this message] 2023-09-09 12:26 ` [Bug libstdc++/111353] " redi at gcc dot gnu.org 2023-09-09 13:08 ` redi at gcc dot gnu.org 2023-09-09 13:26 ` unlvsur at live dot com 2023-09-09 13:35 ` redi at gcc dot gnu.org 2023-09-09 19:19 ` unlvsur at live dot com 2023-09-09 19:59 ` redi at gcc dot gnu.org 2023-09-09 20:03 ` 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-111353-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).