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++/113970] [14 Regression] pch/system-{1,2}.C fails on darwin after r14-8987-gdd9d14f7d53
Date: Sat, 17 Feb 2024 20:12:47 +0000 [thread overview]
Message-ID: <bug-113970-4-DjRjDHZWn7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113970-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113970
Iain Sandoe <iains at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|pch |c++
CC| |nshead at gcc dot gnu.org
Summary|[14 Regression] |[14 Regression]
|pch/system-{1,2}.C fails on |pch/system-{1,2}.C fails on
|darwin |darwin after
| |r14-8987-gdd9d14f7d53
Keywords|needs-bisection |
Target Milestone|--- |14.0
--- Comment #1 from Iain Sandoe <iains at gcc dot gnu.org> ---
Bisected to r14-8987-gdd9d14f7d53; reverting that commit on current trunk
(r14-9043) also clears the issue.
next prev parent reply other threads:[~2024-02-17 20:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-17 13:40 [Bug pch/113970] New: [14 Regression] pch/system-{1,2}.C fails on darwin iains at gcc dot gnu.org
2024-02-17 13:40 ` [Bug pch/113970] " iains at gcc dot gnu.org
2024-02-17 20:12 ` iains at gcc dot gnu.org [this message]
2024-02-17 22:16 ` [Bug c++/113970] [14 Regression] pch/system-{1,2}.C fails on darwin after r14-8987-gdd9d14f7d53 pinskia at gcc dot gnu.org
2024-02-22 16:12 ` iains at gcc dot gnu.org
2024-02-22 16:14 ` iains at gcc dot gnu.org
2024-02-28 0:26 ` cvs-commit at gcc dot gnu.org
2024-03-06 20:23 ` mpolacek at gcc dot gnu.org
2024-03-06 20:25 ` iains 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-113970-4-DjRjDHZWn7@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).