From: Tejas Belagod <tejas.belagod@arm.com>
To: Marcus Shawcroft <marcus.shawcroft@gmail.com>,
David Sherwood <David.Sherwood@arm.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: New patch: [AArch64] [BE] [1/2] Make large opaque integer modes endianness-safe.
Date: Wed, 17 Dec 2014 15:23:00 -0000 [thread overview]
Message-ID: <54919DF7.4090407@arm.com> (raw)
In-Reply-To: <CAFqB+PxhNGS6KTz+Yw-SiOCbGGuO+_35ftuq1D309YH38TfZ9A@mail.gmail.com>
On 20/11/14 18:19, Marcus Shawcroft wrote:
> On 13 November 2014 10:09, David Sherwood <david.sherwood@arm.com> wrote:
>
>> gcc/:
>> 2014-11-13 David Sherwood <david.sherwood@arm.com>
>>
>> * config/aarch64/aarch64-protos.h (aarch64_simd_attr_length_rglist,
>> aarch64_reverse_mask): New decls.
>> * config/aarch64/iterators.md (UNSPEC_REV_REGLIST): New enum.
>> * config/aarch64/iterators.md (insn_count): New mode_attr.
>> * config/aarch64/aarch64-simd.md (vec_store_lanes(o/c/x)i,
>> vec_load_lanes(o/c/x)i): Fixed to work for Big Endian.
>
> Spell these out in full please, some folks like to be able to grep for
> function names in these logs.
>
>> * config/aarch64/aarch64-simd.md (aarch64_rev_reglist,
>> aarch64_simd_(ld/st)(2/3/4)): Added.
>
> Likewise.
>
>> * config/aarch64/aarch64.c (aarch64_simd_attr_length_rglist,
>> aarch64_reverse_mask): Added.
>
> It isn;t clear to me how far through the various BE patches we need to
> get before 59810 is actually resolved?
David's 2 patches
https://gcc.gnu.org/ml/gcc-patches/2014-11/msg01431.html
https://gcc.gnu.org/ml/gcc-patches/2014-10/msg01099.html
and Alan's 2 patches:
https://gcc.gnu.org/ml/gcc-patches/2014-11/msg02797.html
https://gcc.gnu.org/ml/gcc-patches/2014-12/msg01087.html
should fix 59810.
Thanks,
Tejas.
next prev parent reply other threads:[~2014-12-17 15:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-13 10:11 David Sherwood
2014-11-13 14:23 ` Christophe Lyon
2014-11-13 14:33 ` David Sherwood
2014-11-17 21:18 ` Christophe Lyon
2014-11-18 9:17 ` David Sherwood
2014-11-18 10:33 ` Christophe Lyon
2014-11-27 15:03 ` David Sherwood
2014-12-11 10:16 ` David Sherwood
2014-12-11 13:46 ` Christophe Lyon
2014-12-15 9:58 ` David Sherwood
2014-12-15 13:48 ` Christophe Lyon
2014-11-20 18:41 ` Marcus Shawcroft
2014-12-17 15:23 ` Tejas Belagod [this message]
2014-12-17 16:54 ` Marcus Shawcroft
2014-12-17 17:05 ` Tejas Belagod
2015-01-25 23:07 ` Christophe Lyon
2015-08-14 15:06 ` Christophe Lyon
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=54919DF7.4090407@arm.com \
--to=tejas.belagod@arm.com \
--cc=David.Sherwood@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=marcus.shawcroft@gmail.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).