From: Marcus Shawcroft <marcus.shawcroft@gmail.com>
To: Alex Velenko <Alex.Velenko@arm.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Marcus Shawcroft <Marcus.Shawcroft@arm.com>
Subject: Re: [PATCH AArch64_BE 2/4] Big-Endian lane numbering fix
Date: Tue, 21 Jan 2014 13:31:00 -0000 [thread overview]
Message-ID: <CAFqB+PykrKAnBwhcRTat5Q_yt5SjfXy_w1LaP1vG8ssyRCBmCQ@mail.gmail.com> (raw)
In-Reply-To: <52D7C761.6090605@arm.com>
On 16 January 2014 11:49, Alex Velenko <Alex.Velenko@arm.com> wrote:
> Hi,
> This patch changes get_lane intrinsics to provide a correct big-endian
> indexing. This fixes numerous BE load and store issues based on getting
> correct lane.
>
> Is this good for trunk?
OK
/Marcus
next prev parent reply other threads:[~2014-01-21 13:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-16 11:49 Alex Velenko
2014-01-21 13:31 ` Marcus Shawcroft [this message]
2014-01-21 19:00 ` Alex Velenko
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=CAFqB+PykrKAnBwhcRTat5Q_yt5SjfXy_w1LaP1vG8ssyRCBmCQ@mail.gmail.com \
--to=marcus.shawcroft@gmail.com \
--cc=Alex.Velenko@arm.com \
--cc=Marcus.Shawcroft@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).