public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "arsen at aarsen dot me" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/103626] _GLIBCXX_HOSTED should respect -ffreestanding
Date: Sun, 18 Sep 2022 12:36:49 +0000	[thread overview]
Message-ID: <bug-103626-4-sGFJ1JKz8R@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 #6 from Arsen Arsenović <arsen at aarsen dot me> ---
Agreed. Now that I think about it, it'd be just as easy to spot errors if
something in freestanding is relying on a hosted feature by just trying to
#include those headers on a freestanding install, so more explicitly handling
internal headers that aren't installed in freestanding would be redundant. I'll
clean that up.

  parent reply	other threads:[~2022-09-18 12:36 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
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 [this message]
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-sGFJ1JKz8R@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: link
Be 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).