From: Richard Sandiford <richard.sandiford@arm.com>
To: Jonathan Wright <Jonathan.Wright@arm.com>
Cc: "gcc-patches\@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] testsuite: aarch64: Fix failing vector structure tests on big-endian
Date: Mon, 09 Aug 2021 09:43:58 +0100 [thread overview]
Message-ID: <mptr1f3xb1t.fsf@arm.com> (raw)
In-Reply-To: <DB9PR08MB695951E588485535D4E74788EBF69@DB9PR08MB6959.eurprd08.prod.outlook.com> (Jonathan Wright's message of "Mon, 9 Aug 2021 09:41:57 +0100")
Jonathan Wright <Jonathan.Wright@arm.com> writes:
> Hi,
>
> I've corrected the quoting and moved everything on to one line.
>
> Ok for master?
>
> Thanks,
> Jonathan
>
> ---
>
> gcc/testsuite/ChangeLog:
>
> 2021-08-04 Jonathan Wright <jonathan.wright@arm.com>
>
> * gcc.target/aarch64/vector_structure_intrinsics.c: Restrict
> tests to little-endian targets.
OK, thanks.
Richard
> From: Richard Sandiford <richard.sandiford@arm.com>
> Sent: 06 August 2021 13:24
> To: Jonathan Wright <Jonathan.Wright@arm.com>
> Cc: gcc-patches@gcc.gnu.org <gcc-patches@gcc.gnu.org>; Christophe Lyon <christophe.lyon.oss@gmail.com>
> Subject: Re: [PATCH] testsuite: aarch64: Fix failing vector structure tests on big-endian
>
> Jonathan Wright <Jonathan.Wright@arm.com> writes:
>> diff --git a/gcc/testsuite/gcc.target/aarch64/vector_structure_intrinsics.c b/gcc/testsuite/gcc.target/aarch64/vector_structure_intrinsics.c
>> index 60c53bc27f8378c78b119576ed19fde0e5743894..a8e31ab85d6fd2a045c8efaf2cbc42b5f40d2411 100644
>> --- a/gcc/testsuite/gcc.target/aarch64/vector_structure_intrinsics.c
>> +++ b/gcc/testsuite/gcc.target/aarch64/vector_structure_intrinsics.c
>> @@ -197,7 +197,8 @@ TEST_ST1x3 (vst1q, uint64x2x3_t, uint64_t*, u64, x3);
>> TEST_ST1x3 (vst1q, poly64x2x3_t, poly64_t*, p64, x3);
>> TEST_ST1x3 (vst1q, float64x2x3_t, float64_t*, f64, x3);
>>
>> -/* { dg-final { scan-assembler-not "mov\\t" } } */
>> +/* { dg-final { scan-assembler-not {"mov\\t"} {
>> + target { aarch64_little_endian } } ) } */
>
> I think this needs to stay on line. We should also either keep the
> original quoting on the regexp or use {mov\t}. Having both forms
> of quote would turn it into a test for the characters:
>
> "mov\t"
>
> (including quotes and backslash).
>
> Thanks,
> Richard
>
>
>>
>> /* { dg-final { scan-assembler-times "tbl\\t" 18} } */
>> /* { dg-final { scan-assembler-times "tbx\\t" 18} } */
>
> diff --git a/gcc/testsuite/gcc.target/aarch64/vector_structure_intrinsics.c b/gcc/testsuite/gcc.target/aarch64/vector_structure_intrinsics.c
> index 3e7e572bf39659ecf2f17751d92a4a99a4f2bf8b..89e9de18a92dbc00e58261e4558b3cff38c7ca75 100644
> --- a/gcc/testsuite/gcc.target/aarch64/vector_structure_intrinsics.c
> +++ b/gcc/testsuite/gcc.target/aarch64/vector_structure_intrinsics.c
> @@ -263,7 +263,7 @@ TEST_ST1x3 (vst1q, uint64x2x3_t, uint64_t*, u64, x3);
> TEST_ST1x3 (vst1q, poly64x2x3_t, poly64_t*, p64, x3);
> TEST_ST1x3 (vst1q, float64x2x3_t, float64_t*, f64, x3);
>
> -/* { dg-final { scan-assembler-not "mov\\t" } } */
> +/* { dg-final { scan-assembler-not "mov\\t" { target aarch64_little_endian } } } */
>
> /* { dg-final { scan-assembler-times "tbl\\t" 18} } */
> /* { dg-final { scan-assembler-times "tbx\\t" 18} } */
prev parent reply other threads:[~2021-08-09 8:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-23 8:21 [PATCH 1/8] aarch64: Use memcpy to copy vector tables in vqtbl[234] intrinsics Jonathan Wright
2021-07-23 9:15 ` Kyrylo Tkachov
2021-08-03 9:42 ` Christophe Lyon
2021-08-04 10:05 ` [PATCH] testsuite: aarch64: Fix failing vector structure tests on big-endian Jonathan Wright
2021-08-06 12:24 ` Richard Sandiford
2021-08-09 8:41 ` Jonathan Wright
2021-08-09 8:43 ` Richard Sandiford [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=mptr1f3xb1t.fsf@arm.com \
--to=richard.sandiford@arm.com \
--cc=Jonathan.Wright@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).