From: Ramana Radhakrishnan <ramana.gcc@googlemail.com>
To: Alan Lawrence <alan.lawrence@arm.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Jakub Jelinek <jakub@redhat.com>
Subject: Re: [PATCH 4.9 ARM] Backport r210219: "Neon Intrinsics TLC - remove ML"
Date: Tue, 08 Jul 2014 11:35:00 -0000 [thread overview]
Message-ID: <CAJA7tRaDsuZX1Q3cgUFeF1hr=1-E-x_JtgkBXffb1Z1zxk-Psg@mail.gmail.com> (raw)
In-Reply-To: <53A7FC05.4060601@arm.com>
On Mon, Jun 23, 2014 at 11:05 AM, Alan Lawrence <alan.lawrence@arm.com> wrote:
> As for 4.8, I'm intending to backport the ZIP/UZP/TRN fix for ARM big-endian
> in r211369 of mainline. That patches arm_neon.h, so again we need to remove
> the OCAML code by which that file is autogenerated...ok?
Ok Makes life with backports for any fixes to neon intrinsics easier,
therefore OK unless an RM objects in 24 hours.
Ramana
>
> --Alan
prev parent reply other threads:[~2014-07-08 11:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-23 10:06 Alan Lawrence
2014-07-08 11:35 ` Ramana Radhakrishnan [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='CAJA7tRaDsuZX1Q3cgUFeF1hr=1-E-x_JtgkBXffb1Z1zxk-Psg@mail.gmail.com' \
--to=ramana.gcc@googlemail.com \
--cc=alan.lawrence@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=ramrad01@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).