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: Sat, 17 Sep 2022 19:37:56 +0000 [thread overview] Message-ID: <bug-103626-4-aSfdJ6NwzF@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 #2 from Arsen Arsenović <arsen at aarsen dot me> --- I started work on marking headers, and I already marked 162 headers (all of include/{std,bits,backward}, where appropriate) as part of my work on P1642. This set also lines up with the set of all installed installed headers for P1642. I already have a list of remaining headers that need to be marked, I'll be handling these, and maybe reverting the change on <expected> (to make it freestanding). The progress can be tracked here: https://github.com/ArsenArsen/gcc/tree/p16412 This branch includes the titular changes, in order to support switching between freestanding and hosted, a rework of how freestanding headers are handled and installed (though, I would like to exclude even more targets and files, so that stuff doesn't get stamped needlessly, probably by constraining allstamped, unsure so far), <bits/requires_hosted.h>, and the aforementioned marking. Next on my agenda is checking whether this version still produces equivalent results in hosting to the unpatched version of GCC, and updating the testsuite after that, then I can resume marking headers if this approach is deemed acceptable (which I'd like to get a greenlight on before editing 400-some headers by hand)
next prev parent reply other threads:[~2022-09-17 19:37 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 [this message] 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 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-aSfdJ6NwzF@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).