public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Christophe Lyon <christophe.lyon@linaro.org>
To: David Sherwood <david.sherwood@arm.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
	Alan Hayward <Alan.Hayward@arm.com>
Subject: Re: New patch: [AArch64] [BE] [1/2] Make large opaque integer modes endianness-safe.
Date: Mon, 17 Nov 2014 21:18:00 -0000	[thread overview]
Message-ID: <CAKdteOY9E1N1oYP5YFkhDWt_GgJW8cEx9Vw5KPC=kfuokCAapg@mail.gmail.com> (raw)
In-Reply-To: <000b01cfff4e$aa668090$ff3381b0$@arm.com>

On 13 November 2014 15:32, David Sherwood <david.sherwood@arm.com> wrote:
> Hi,
>
> I think that's because Alan Hayward's original patch had a bug in it, which he
> has fixed and should be submitting to gcc patches fairly soon. So it's probably
> best waiting until he gets a new patch up I think.
>

I've applied both Alan's patches and the advsimd-intrinsics tests now
all pass on aarch64_be, but this doesn't need your patch.

Which testcase does your patch actually fix?


> Regards,
> David.
>
> -----Original Message-----
> From: Christophe Lyon [mailto:christophe.lyon@linaro.org]
> Sent: 13 November 2014 14:22
> To: David Sherwood
> Cc: gcc-patches@gcc.gnu.org
> Subject: Re: New patch: [AArch64] [BE] [1/2] Make large opaque integer modes endianness-safe.
>
> On 13 November 2014 11:09, David Sherwood <david.sherwood@arm.com> wrote:
>> Hi All,
>>
>> I have successfully rebased this and tested in conjunction with a patch from
>> Alan Hayward ([AArch64] [BE] Fix vector load/stores to not use ld1/st1), who
>> should be submitting a new version shortly. Built and tested on:
>>
>> aarch64-none-elf
>> aarch64_be-none-elf
>> x86_64-linux-gnu
>
> I've applied both patches to recent trunk (r217483), and I still see
> ICEs on aarch64_be, when running the advsimd-intrinsics/vldX.c tests.
>
> I have them with Alan Hayward's patch alone, too. BTW, I thought that
> patch had been approved by Marcus, but it's not in trunk yet. Maybe I
> missed something.
>
> Christophe.
>
>>
>> Regards,
>> David Sherwood.
>>
>> -----Original Message-----
>> From: David Sherwood [mailto:david.sherwood@arm.com]
>> Sent: 28 October 2014 08:55
>> To: 'gcc-patches@gcc.gnu.org'
>> Subject: RE: [AArch64] [BE] [1/2] Make large opaque integer modes endianness-safe.
>>
>> Hi,
>>
>> Sorry to bother you again. Could someone take a look at this change
>> please if they have time?
>>
>> Thanks!
>> David.
>>
>> -----Original Message-----
>> From: David Sherwood [mailto:david.sherwood@arm.com]
>> Sent: 10 October 2014 15:48
>> To: gcc-patches@gcc.gnu.org
>> Subject: [AArch64] [BE] [1/2] Make large opaque integer modes endianness-safe.
>>
>> Hi,
>>
>> I have a fix (originally written by Tejas Belagod) for the following bug:
>>
>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59810
>>
>> Could someone take a look please?
>>
>> Thanks!
>> David Sherwood.
>>
>> ChangeLog:
>>
>>     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.
>>         * config/aarch64/aarch64-simd.md (aarch64_rev_reglist,
>>         aarch64_simd_(ld/st)(2/3/4)): Added.
>>         * config/aarch64/aarch64.c (aarch64_simd_attr_length_rglist,
>>         aarch64_reverse_mask): Added.
>
>
>
>

  reply	other threads:[~2014-11-17 21:09 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 [this message]
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
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='CAKdteOY9E1N1oYP5YFkhDWt_GgJW8cEx9Vw5KPC=kfuokCAapg@mail.gmail.com' \
    --to=christophe.lyon@linaro.org \
    --cc=Alan.Hayward@arm.com \
    --cc=david.sherwood@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).