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++/103626] _GLIBCXX_HOSTED should respect -ffreestanding Date: Sat, 17 Sep 2022 22:19:14 +0000 [thread overview] Message-ID: <bug-103626-4-iI6Dg0zGsH@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103626-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103626 --- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> --- I don't think we need to add the #error to every header. For a start, users never include the bits/* headers directly, and if they do, it's their problem. So we only need to mark the standard headers as hosted-only. And if we add it to <iosfwd>, that already covers a large number of them, because they include that.
next prev parent reply other threads:[~2022-09-17 22:19 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-09 11:05 [Bug libstdc++/103626] New: " redi at gcc dot gnu.org 2022-09-16 20:06 ` [Bug libstdc++/103626] " redi at gcc dot gnu.org 2022-09-17 19:37 ` arsen at aarsen dot me 2022-09-17 22:19 ` redi at gcc dot gnu.org [this message] 2022-09-18 1:40 ` arsen at aarsen dot me 2022-09-18 6:41 ` redi at gcc dot gnu.org 2022-09-18 12:36 ` arsen at aarsen dot me 2022-10-03 14:45 ` cvs-commit at gcc dot gnu.org 2022-10-03 14:45 ` cvs-commit at gcc dot gnu.org 2022-10-03 14:45 ` cvs-commit at gcc dot gnu.org 2022-10-03 14:46 ` cvs-commit at gcc dot gnu.org 2022-10-03 14:46 ` cvs-commit at gcc dot gnu.org 2022-10-03 14:46 ` cvs-commit at gcc dot gnu.org 2022-10-03 14:50 ` 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-103626-4-iI6Dg0zGsH@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).