public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/115167] [15 Regression] CFG edge visualization to path-printing bootstrap failure
Date: Tue, 21 May 2024 13:38:08 +0000 [thread overview]
Message-ID: <bug-115167-4-h7Nrfd64AN@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-115167-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115167
David Malcolm <dmalcolm at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
--- Comment #4 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
> Also, gcc119 would be a much better choice than gcc111.
Thanks; am trying on that.
FWIW r15-636-g770657d02c986c added a new vfunc to libcpp:
range_label::get_effects
and it's *defined* in the header, so my immediately suspicion is that's the
issue. Investigating...
next prev parent reply other threads:[~2024-05-21 13:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-20 18:37 [Bug bootstrap/115167] New: " dje at gcc dot gnu.org
2024-05-20 20:57 ` [Bug bootstrap/115167] [15 Regression] " dmalcolm at gcc dot gnu.org
2024-05-20 22:03 ` dje at gcc dot gnu.org
2024-05-21 0:46 ` dje at gcc dot gnu.org
2024-05-21 6:42 ` rguenth at gcc dot gnu.org
2024-05-21 13:38 ` dmalcolm at gcc dot gnu.org [this message]
2024-05-24 1:42 ` dmalcolm at gcc dot gnu.org
2024-05-24 12:09 ` dje at gcc dot gnu.org
2024-05-28 17:08 ` cvs-commit at gcc dot gnu.org
2024-05-28 17:16 ` dmalcolm 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-115167-4-h7Nrfd64AN@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).