From: Richard Biener <richard.guenther@gmail.com>
To: Yixuan Chen <chenyixuan@iscas.ac.cn>
Cc: gcc-patches@gcc.gnu.org, kito.cheng@gmail.com, andrew@sifive.com,
oriachiuan@gmail.com, jiawei@iscas.ac.cn
Subject: Re: [PATCH] Riscv don't support "-fprefetch-loop-arrays", skip.
Date: Tue, 22 Nov 2022 09:54:19 +0100 [thread overview]
Message-ID: <CAFiYyc3nWfyf_ADHFoWDeBtDGqYM5Jnh-8qorDVHwMmVxFUpow@mail.gmail.com> (raw)
In-Reply-To: <20221122084235.1216435-1-chenyixuan@iscas.ac.cn>
On Tue, Nov 22, 2022 at 9:43 AM Yixuan Chen <chenyixuan@iscas.ac.cn> wrote:
>
> gcc/testsuite/ChangeLog:
>
> Riscv don't support "-fprefetch-loop-arrays" option, skip.
Looking around other testcases simply add -w to the set of command-line options,
can you do that instead?
OK with that change,
Richard.
> 2022-11-22 Yixuan Chen <chenyixuan@iscas.ac.cn>
>
> * gcc.dg/pr106397.c: Riscv don't support "-fprefetch-loop-arrays" option, skip.
> ---
> gcc/testsuite/gcc.dg/pr106397.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/gcc/testsuite/gcc.dg/pr106397.c b/gcc/testsuite/gcc.dg/pr106397.c
> index 2bc17f8cf80..7b507125575 100644
> --- a/gcc/testsuite/gcc.dg/pr106397.c
> +++ b/gcc/testsuite/gcc.dg/pr106397.c
> @@ -1,7 +1,7 @@
> /* { dg-do compile } */
> /* { dg-options "-O3 -fprefetch-loop-arrays --param l2-cache-size=0 --param prefetch-latency=3 -fprefetch-loop-arrays" } */
> /* { dg-additional-options "-march=i686 -msse" { target { { i?86-*-* x86_64-*-* } && ia32 } } } */
> -
> +/* { dg-skip-if "" { riscv*-*-* } } */
> int
> bar (void)
> {
> --
> 2.37.2
>
prev parent reply other threads:[~2022-11-22 8:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 8:42 Yixuan Chen
2022-11-22 8:54 ` Richard Biener [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=CAFiYyc3nWfyf_ADHFoWDeBtDGqYM5Jnh-8qorDVHwMmVxFUpow@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=andrew@sifive.com \
--cc=chenyixuan@iscas.ac.cn \
--cc=gcc-patches@gcc.gnu.org \
--cc=jiawei@iscas.ac.cn \
--cc=kito.cheng@gmail.com \
--cc=oriachiuan@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).