public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/98531] [11 Regression] g++.dg/modules/xtreme-header-2_a.H etc. FAIL Date: Tue, 16 Feb 2021 08:41:33 +0000 [thread overview] Message-ID: <bug-98531-4-RAcJZmvoGm@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98531-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98531 --- Comment #13 from Iain Sandoe <iains at gcc dot gnu.org> --- fixed for Darwin.
next prev parent reply other threads:[~2021-02-16 8:41 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-05 13:00 [Bug c++/98531] New: " ro at gcc dot gnu.org 2021-01-05 13:00 ` [Bug c++/98531] " ro at gcc dot gnu.org 2021-01-05 13:57 ` nathan at gcc dot gnu.org 2021-01-05 14:00 ` ro at CeBiTec dot Uni-Bielefeld.DE 2021-01-05 14:08 ` nathan at gcc dot gnu.org 2021-01-19 15:13 ` [Bug c++/98531] [11 Regression] " iains at gcc dot gnu.org 2021-01-21 16:52 ` nathan at gcc dot gnu.org 2021-01-22 13:22 ` nathan at gcc dot gnu.org 2021-01-27 13:30 ` ro at CeBiTec dot Uni-Bielefeld.DE 2021-01-27 13:36 ` nathan at acm dot org 2021-02-01 12:36 ` ro at gcc dot gnu.org 2021-02-02 20:55 ` nathan at gcc dot gnu.org 2021-02-08 17:24 ` cvs-commit at gcc dot gnu.org 2021-02-08 17:36 ` nathan at gcc dot gnu.org 2021-02-16 8:41 ` iains at gcc dot gnu.org [this message] 2021-04-27 11:40 ` [Bug c++/98531] [modules] " jakub at gcc dot gnu.org 2021-07-28 7:05 ` rguenth at gcc dot gnu.org 2022-04-21 7:48 ` rguenth at gcc dot gnu.org 2023-04-02 15:01 ` danglin at gcc dot gnu.org 2023-04-02 15:23 ` danglin at gcc dot gnu.org 2023-05-29 10:03 ` jakub at gcc dot gnu.org 2023-12-06 16:09 ` danglin at gcc dot gnu.org 2024-02-11 18:27 ` danglin at gcc dot gnu.org 2024-02-11 18:34 ` pinskia at gcc dot gnu.org 2024-02-11 18:35 ` pinskia at gcc dot gnu.org 2024-02-11 18:51 ` danglin 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-98531-4-RAcJZmvoGm@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).