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++/113398] New: <string> no longer usable with -ffreestanding Date: Mon, 15 Jan 2024 13:10:20 +0000 [thread overview] Message-ID: <bug-113398-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113398 Bug ID: 113398 Summary: <string> no longer usable with -ffreestanding Product: gcc Version: unknown Status: UNCONFIRMED Severity: enhancement Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: redi at gcc dot gnu.org Target Milestone: --- This used to work with GCC 12 when compiled with -ffreestanding #include <string> // Defined by the user. void* operator new(std::size_t n); void operator delete(void*, std::size_t n); int main() { std::string s = "a string that needs to allocate from the heap"; return s.size(); } Since GCC 13 the -ffreestanding option also selects a freestanding libstdc++, which doesn't allow std::string to be used. The change was done intentionally, to provide a more clearly defined and documented freestanding library, but it removes functionality that was being used.
next reply other threads:[~2024-01-15 13:10 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-15 13:10 redi at gcc dot gnu.org [this message] 2024-01-15 13:12 ` [Bug libstdc++/113398] " redi at gcc dot gnu.org 2024-01-15 14:06 ` redi at gcc dot gnu.org 2024-01-24 3:42 ` hp 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-113398-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).