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/115465] [15 Regression] aarch64-early-ra.cc:3449:23: error: ‘class pretty_printer’ has no member named ‘buffer’
Date: Wed, 12 Jun 2024 19:01:38 +0000 [thread overview]
Message-ID: <bug-115465-4-PtHBmhfhLM@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-115465-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115465
--- Comment #4 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
(In reply to David Malcolm from comment #3)
> Build breakage should be fixed by the above patch.
Indeed, https://builder.sourceware.org/buildbot/#/builders/266/builds/3620
succeeded.
prev parent reply other threads:[~2024-06-12 19:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-12 16:48 [Bug bootstrap/115465] New: " dmalcolm at gcc dot gnu.org
2024-06-12 16:48 ` [Bug bootstrap/115465] " dmalcolm at gcc dot gnu.org
2024-06-12 16:49 ` pinskia at gcc dot gnu.org
2024-06-12 16:54 ` pinskia at gcc dot gnu.org
2024-06-12 18:25 ` cvs-commit at gcc dot gnu.org
2024-06-12 18:30 ` dmalcolm at gcc dot gnu.org
2024-06-12 19:01 ` dmalcolm at gcc dot gnu.org [this message]
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-115465-4-PtHBmhfhLM@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).