From: Gerald Pfeifer <gerald@pfeifer.com>
To: Maxim Blinov <maxim.blinov@embecosm.com>
Cc: gcc-patches@gcc.gnu.org, David Malcolm <dmalcolm@redhat.com>
Subject: Re: [PATCH v2] analyzer: Define INCLUDE_UNIQUE_PTR
Date: Fri, 17 Sep 2021 00:38:30 +0200 (CEST) [thread overview]
Message-ID: <1256870-baaa-b1b8-a488-4a52dc461512@pfeifer.com> (raw)
In-Reply-To: <20210914083557.15566-1-maxim.blinov@embecosm.com>
On Tue, 14 Sep 2021, Maxim Blinov wrote:
> Un-break the build for AArch64 Darwin, see PR bootstrap/102242. Build
> fails with log below:
David already acked this with
"Does the patch fix the build for you?
If so, looks good for trunk. Please reference PR bootstrap/102242
in the ChangeLog entry."
Can you please go ahead and commit this to fix the regression and
bootstrap failure (and add PR bootstrap/102242 to the ChangeLog)?
Oh, I don't see your name in the MAINTAINERS file, so I went ahead
and committed this in your behalf.
(One out of four bootstrap failures gone, hopefully.)
Gerald
PS: It might have made sense to Cc: David on your updated patch and
note that you do not have commit access.
prev parent reply other threads:[~2021-09-16 22:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-14 8:35 Maxim Blinov
2021-09-16 22:38 ` Gerald Pfeifer [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=1256870-baaa-b1b8-a488-4a52dc461512@pfeifer.com \
--to=gerald@pfeifer.com \
--cc=dmalcolm@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=maxim.blinov@embecosm.com \
/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).