public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hp at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/108672] [13 Regression] g++.dg/modules/xtreme-header-2_a.H, _b.C, _c.C
Date: Fri, 30 Jun 2023 03:09:52 +0000 [thread overview]
Message-ID: <bug-108672-4-G2wKtoE1ZQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108672-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108672
Hans-Peter Nilsson <hp at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|FIXED |---
Ever confirmed|0 |1
Last reconfirmed| |2023-06-30
Status|RESOLVED |REOPENED
--- Comment #3 from Hans-Peter Nilsson <hp at gcc dot gnu.org> ---
I'm briefly reopening this PR so my next commit makes sense, as
r14-2109-g3162ca09dbdc2e overwrote the fix from February, making the fails
re-appear. I'll re-commit the fix shortly.
next prev parent reply other threads:[~2023-06-30 3:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-04 3:04 [Bug libstdc++/108672] New: " hp at gcc dot gnu.org
2023-02-04 17:39 ` [Bug libstdc++/108672] " cvs-commit at gcc dot gnu.org
2023-02-05 22:33 ` hp at gcc dot gnu.org
2023-06-30 3:09 ` hp at gcc dot gnu.org [this message]
2023-06-30 3:27 ` cvs-commit at gcc dot gnu.org
2023-06-30 3:58 ` hp 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-108672-4-G2wKtoE1ZQ@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).