From: Richard Sandiford <richard.sandiford@arm.com>
To: gcc-patches@gcc.gnu.org
Subject: Re: [Ping] ifcvt: Fix regression in aarch64/fcsel_1.c
Date: Mon, 13 Feb 2023 10:46:40 +0000 [thread overview]
Message-ID: <mptttzpyh9r.fsf@arm.com> (raw)
In-Reply-To: <mpta61hzw2t.fsf@arm.com> (Richard Sandiford via Gcc-patches's message of "Mon, 13 Feb 2023 10:41:30 +0000")
Richard Sandiford via Gcc-patches <gcc-patches@gcc.gnu.org> writes:
> Ping for the patch below
Ugh, somehow missed Jeff's OK over the weekend. Sorry for the noise!
Richard
prev parent reply other threads:[~2023-02-13 10:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 9:15 [PATCH] " Richard Sandiford
2023-02-13 6:46 ` Jeff Law
2023-02-13 10:41 ` [Ping] " Richard Sandiford
2023-02-13 10:46 ` Richard Sandiford [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=mptttzpyh9r.fsf@arm.com \
--to=richard.sandiford@arm.com \
--cc=gcc-patches@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).