public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "nathan at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/99413] internal library headers are not header-unit ready
Date: Fri, 05 Mar 2021 16:00:08 +0000	[thread overview]
Message-ID: <bug-99413-4-54ogKakOnh@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99413-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99413

--- Comment #2 from Nathan Sidwell <nathan at gcc dot gnu.org> ---
Correct.  We're only picking headers that are either (a) user-facing or (b)
included from more than one place.

Specifically we're partitioning the include graph into a set of multi-reached
sub-graphs.

And we're maintaining a bad-list, which are the case reported here.

Hope that helps.

  parent reply	other threads:[~2021-03-05 16:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-05 15:13 [Bug libstdc++/99413] New: " nathan at gcc dot gnu.org
2021-03-05 15:48 ` [Bug libstdc++/99413] " redi at gcc dot gnu.org
2021-03-05 16:00 ` nathan at gcc dot gnu.org [this message]
2021-03-10 15:28 ` cvs-commit at gcc dot gnu.org
2021-03-11 13:15 ` 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-99413-4-54ogKakOnh@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).