* [PATCH AARCH64]XFAIL gcc.target/aarch64/ldp_vec_64_1.c
@ 2017-01-25 17:02 Bin Cheng
2017-01-25 18:11 ` Richard Earnshaw (lists)
0 siblings, 1 reply; 2+ messages in thread
From: Bin Cheng @ 2017-01-25 17:02 UTC (permalink / raw)
To: gcc-patches; +Cc: nd
[-- Attachment #1: Type: text/plain, Size: 540 bytes --]
Hi,
Test gcc.target/aarch64/ldp_vec_64_1.c because we don't choose [base+offset] addressing mode in IVOPT
on AArch64. Given auto-increment addressing mode is disabled in IVOPT on AArch64, we can't really test
the addressing mode. I may try to enable it only for small loops in GCC8, so this patch xfail the case at the
moment. Also I filed PR79213 for tracking.
Test result checked. Is it OK?
Thanks,
bin
gcc/testsuite/ChangeLog
2017-01-23 Bin Cheng <bin.cheng@arm.com>
* gcc.target/aarch64/ldp_vec_64_1.c: Xfail.
[-- Attachment #2: xfail-1.txt --]
[-- Type: text/plain, Size: 589 bytes --]
diff --git a/gcc/testsuite/gcc.target/aarch64/ldp_vec_64_1.c b/gcc/testsuite/gcc.target/aarch64/ldp_vec_64_1.c
index 62213f3..59cf914 100644
--- a/gcc/testsuite/gcc.target/aarch64/ldp_vec_64_1.c
+++ b/gcc/testsuite/gcc.target/aarch64/ldp_vec_64_1.c
@@ -13,4 +13,6 @@ foo (int32x2_t *foo, int32x2_t *bar)
foo[i] = bar[i] + bar[i + 1];
}
-/* { dg-final { scan-assembler "ldp\td\[0-9\]+, d\[0-9\]" } } */
+/* Xfail for now since IVOPT doesn't choose [base+offset] addressing mode.
+ See PR79213. */
+/* { dg-final { scan-assembler "ldp\td\[0-9\]+, d\[0-9\]" { xfail *-*-* } } } */
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [PATCH AARCH64]XFAIL gcc.target/aarch64/ldp_vec_64_1.c
2017-01-25 17:02 [PATCH AARCH64]XFAIL gcc.target/aarch64/ldp_vec_64_1.c Bin Cheng
@ 2017-01-25 18:11 ` Richard Earnshaw (lists)
0 siblings, 0 replies; 2+ messages in thread
From: Richard Earnshaw (lists) @ 2017-01-25 18:11 UTC (permalink / raw)
To: Bin Cheng, gcc-patches; +Cc: nd
On 25/01/17 16:49, Bin Cheng wrote:
> Hi,
> Test gcc.target/aarch64/ldp_vec_64_1.c because we don't choose [base+offset] addressing mode in IVOPT
> on AArch64. Given auto-increment addressing mode is disabled in IVOPT on AArch64, we can't really test
> the addressing mode. I may try to enable it only for small loops in GCC8, so this patch xfail the case at the
> moment. Also I filed PR79213 for tracking.
>
> Test result checked. Is it OK?
>
> Thanks,
> bin
>
> gcc/testsuite/ChangeLog
> 2017-01-23 Bin Cheng <bin.cheng@arm.com>
>
> * gcc.target/aarch64/ldp_vec_64_1.c: Xfail.
>
>
> xfail-1.txt
>
>
> diff --git a/gcc/testsuite/gcc.target/aarch64/ldp_vec_64_1.c b/gcc/testsuite/gcc.target/aarch64/ldp_vec_64_1.c
> index 62213f3..59cf914 100644
> --- a/gcc/testsuite/gcc.target/aarch64/ldp_vec_64_1.c
> +++ b/gcc/testsuite/gcc.target/aarch64/ldp_vec_64_1.c
> @@ -13,4 +13,6 @@ foo (int32x2_t *foo, int32x2_t *bar)
> foo[i] = bar[i] + bar[i + 1];
> }
>
> -/* { dg-final { scan-assembler "ldp\td\[0-9\]+, d\[0-9\]" } } */
> +/* Xfail for now since IVOPT doesn't choose [base+offset] addressing mode.
> + See PR79213. */
> +/* { dg-final { scan-assembler "ldp\td\[0-9\]+, d\[0-9\]" { xfail *-*-* } } } */
>
OK.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2017-01-25 17:50 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-01-25 17:02 [PATCH AARCH64]XFAIL gcc.target/aarch64/ldp_vec_64_1.c Bin Cheng
2017-01-25 18:11 ` Richard Earnshaw (lists)
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).