public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/99936] [modules] FAIL: g++.dg/modules/xtreme-header* on Darwin Date: Mon, 19 Apr 2021 12:56:48 +0000 [thread overview] Message-ID: <bug-99936-4-llDdpplpMk@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99936-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99936 Dominique d'Humieres <dominiq at lps dot ens.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nathan at gcc dot gnu.org Blocks| |99227 Ever confirmed|0 |1 Summary|FAIL: |[modules] FAIL: |g++.dg/modules/xtreme-heade |g++.dg/modules/xtreme-heade |r* on Darwin |r* on Darwin Last reconfirmed| |2021-04-19 Status|UNCONFIRMED |NEW --- Comment #1 from Dominique d'Humieres <dominiq at lps dot ens.fr> --- See also https://gcc.gnu.org/pipermail/gcc-testresults/2021-April/682945.html and friends. It would be nice to have this PR fixed for GCC 11.1! Referenced Bugs: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99227 [Bug 99227] [meta] [modules] Bugs relating to header-units of STL header files
next prev parent reply other threads:[~2021-04-19 12:56 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-06 13:20 [Bug c++/99936] New: " dominiq at lps dot ens.fr 2021-04-19 12:56 ` dominiq at lps dot ens.fr [this message] 2021-10-02 11:38 ` [Bug c++/99936] [modules] " dominiq at lps dot ens.fr 2021-10-02 14:18 ` redi at gcc dot gnu.org 2021-12-24 13:58 ` fxcoudert at gcc dot gnu.org 2021-12-24 14:03 ` pinskia at gcc dot gnu.org 2021-12-24 14:11 ` fxcoudert at gcc dot gnu.org 2021-12-24 14:14 ` pinskia at gcc dot gnu.org 2022-02-16 13:52 ` dominiq at lps dot ens.fr 2022-02-16 13:58 ` fxcoudert at gcc dot gnu.org 2022-02-17 15:08 ` dominiq at lps dot ens.fr
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-99936-4-llDdpplpMk@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).