From: Andrea Corallo <andrea.corallo@arm.com>
To: Kyrylo Tkachov <Kyrylo.Tkachov@arm.com>
Cc: nd <nd@arm.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Richard Earnshaw <Richard.Earnshaw@arm.com>
Subject: Re: [PATCH] aarch64: Do not alter value on a force_reg returned rtx expanding __jcvt
Date: Thu, 24 Sep 2020 11:50:49 +0200 [thread overview]
Message-ID: <gkr7dsjcxl2.fsf@arm.com> (raw)
In-Reply-To: <gkrv9g772fk.fsf@arm.com> (Andrea Corallo's message of "Mon, 21 Sep 2020 14:13:35 +0200")
Andrea Corallo <andrea.corallo@arm.com> writes:
> Kyrylo Tkachov <Kyrylo.Tkachov@arm.com> writes:
[...]
>>
>> Can you please also backport it to the appropriate branches as well after some time on trunk.
>> Thanks,
>> Kyrill
>
> Ciao Kyrill,
>
> Sure happy to do that. For now into trunk as 2c62952f816.
Backported into gcc-10 as aa47c987340.
Thanks
Andrea
prev parent reply other threads:[~2020-09-24 9:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-21 10:31 Andrea Corallo
2020-09-21 10:58 ` Richard Sandiford
2020-09-21 11:00 ` Kyrylo Tkachov
2020-09-21 12:13 ` Andrea Corallo
2020-09-24 9:50 ` Andrea Corallo [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=gkr7dsjcxl2.fsf@arm.com \
--to=andrea.corallo@arm.com \
--cc=Kyrylo.Tkachov@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=nd@arm.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).