From: Richard Biener <rguenther@suse.de>
To: Kyrylo Tkachov <Kyrylo.Tkachov@arm.com>
Cc: Andre Simoes Dias Vieira <Andre.SimoesDiasVieira@arm.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Richard Sandiford <Richard.Sandiford@arm.com>
Subject: RE: [PATCH][AArch64] Implement ACLE Data Intrinsics
Date: Thu, 6 Oct 2022 07:23:34 +0000 (UTC) [thread overview]
Message-ID: <nycvar.YFH.7.77.849.2210060722430.18337@jbgna.fhfr.qr> (raw)
In-Reply-To: <PAXPR08MB6926BD6A76C38A2630138835935D9@PAXPR08MB6926.eurprd08.prod.outlook.com>
On Wed, 5 Oct 2022, Kyrylo Tkachov wrote:
>
>
> > -----Original Message-----
> > From: Andre Vieira (lists) <andre.simoesdiasvieira@arm.com>
> > Sent: Tuesday, October 4, 2022 11:34 AM
> > To: Kyrylo Tkachov <Kyrylo.Tkachov@arm.com>; gcc-patches@gcc.gnu.org;
> > Richard Sandiford <Richard.Sandiford@arm.com>; Richard Biener
> > <rguenther@suse.de>
> > Subject: Re: [PATCH][AArch64] Implement ACLE Data Intrinsics
> >
> > Hi all,
> >
> > Can I backport this to gcc-11 branch? Also applies cleanly (with the
> > exception of the file extensions being different: 'aarch64-builtins.cc
> > vs aarch64-builtins.c').
> >
>
> Ok by me if testing is clean.
Target patches like this are really up to the maintainers to decide
for backporting.
Richard.
prev parent reply other threads:[~2022-10-06 7:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-10 13:37 Andre Vieira (lists)
2022-06-17 10:54 ` Richard Sandiford
2022-06-28 14:04 ` Andre Vieira (lists)
2022-06-29 7:18 ` Richard Sandiford
2022-07-01 10:25 ` Andre Vieira (lists)
2022-07-01 11:26 ` Richard Sandiford
2022-08-11 15:11 ` Andre Vieira (lists)
2022-08-11 15:21 ` Kyrylo Tkachov
2022-10-04 10:33 ` Andre Vieira (lists)
2022-10-05 8:47 ` Kyrylo Tkachov
2022-10-06 7:23 ` Richard Biener [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=nycvar.YFH.7.77.849.2210060722430.18337@jbgna.fhfr.qr \
--to=rguenther@suse.de \
--cc=Andre.SimoesDiasVieira@arm.com \
--cc=Kyrylo.Tkachov@arm.com \
--cc=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).