From: Lehua Ding <lehua.ding@rivai.ai>
To: Robin Dapp <rdapp.gcc@gmail.com>,
"juzhe.zhong@rivai.ai" <juzhe.zhong@rivai.ai>,
gcc-patches <gcc-patches@gcc.gnu.org>,
palmer <palmer@dabbelt.com>, "kito.cheng" <kito.cheng@gmail.com>,
jeffreyalaw <jeffreyalaw@gmail.com>
Subject: Re: [PATCH] RISC-V: testsuite: Fix 32-bit FAILs.
Date: Mon, 13 Nov 2023 17:49:17 +0800 [thread overview]
Message-ID: <2D241ED7BCDC3AB9+bae67ce6-4f85-41d6-a910-d8758e4c4b12@rivai.ai> (raw)
In-Reply-To: <79df9cdb-2e5b-4e65-9c91-aae20f5c0fde@gmail.com>
Hi Robin,
Can you show me the compile command in gcc.log for the
slp-mask-run-1.exe like bellow? I'd like to see the -march option on
your side.
Executing on host:
/work/home/lding/open-source/riscv-gnu-toolchain-push/build/dev-rv64gcv_zvfh_zfh-lp64d-medany-newlib-spike-debug/build-gcc-newlib-stage2/gcc/xgcc
-B/work/home/lding/open-source/riscv-gnu-toolchain-push/build/dev-rv64gcv_zvfh_zfh-lp64d-medany-newlib-spike-debug/build-gcc-newlib-stage2/gcc/
/work/home/lding/open-source/riscv-gnu-toolchain-push/gcc/gcc/testsuite/gcc.target/riscv/rvv/autovec/slp-mask-run-1.c
-march=rv64gcv_zvfh_zfh -mabi=lp64d -mcmodel=medany
-fdiagnostics-plain-output -O3 -ftree-vectorize -ansi -pedantic-errors
-march=rv64gcv_zfh -mabi=lp64d -O3 -std=gnu99 -O3
--param=riscv-autovec-preference=scalable -lm -o
./slp-mask-run-1.exe (timeout = 6000)
spawn -ignore SIGHUP
/work/home/lding/open-source/riscv-gnu-toolchain-push/build/dev-rv64gcv_zvfh_zfh-lp64d-medany-newlib-spike-debug/build-gcc-newlib-stage2/gcc/xgcc
-B/work/home/lding/open-source/riscv-gnu-toolchain-push/build/dev-rv64gcv_zvfh_zfh-lp64d-medany-newlib-spike-debug/build-gcc-newlib-stage2/gcc/
/work/home/lding/open-source/riscv-gnu-toolchain-push/gcc/gcc/testsuite/gcc.target/riscv/rvv/autovec/slp-mask-run-1.c
-march=rv64gcv_zvfh_zfh -mabi=lp64d -mcmodel=medany
-fdiagnostics-plain-output -O3 -ftree-vectorize -ansi -pedantic-errors
-march=rv64gcv_zfh -mabi=lp64d -O3 -std=gnu99 -O3
--param=riscv-autovec-preference=scalable -lm -o ./slp-mask-run-1.exe
On 2023/11/13 17:31, Robin Dapp wrote:
>> I'm going to configure with --with-arch=rv32gcv_zfh_zvfh --with-abi=ilp32d
>> to see if there is any difference.
>
> No change for me, how do you invoke the testsuite? I.e. Which target board?
>
> Regards
> Robin
--
Best,
Lehua (RiVAI)
lehua.ding@rivai.ai
next prev parent reply other threads:[~2023-11-13 9:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-10 12:51 Robin Dapp
2023-11-10 13:26 ` 钟居哲
2023-11-10 23:00 ` 钟居哲
2023-11-13 8:52 ` Robin Dapp
2023-11-13 8:55 ` juzhe.zhong
2023-11-13 9:10 ` Robin Dapp
2023-11-13 9:31 ` Robin Dapp
2023-11-13 9:34 ` juzhe.zhong
2023-11-13 9:49 ` Lehua Ding [this message]
2023-11-13 9:59 ` Robin Dapp
2023-11-13 10:14 ` Lehua Ding
2023-11-13 10:17 ` Robin Dapp
2023-11-13 10:22 ` juzhe.zhong
2023-11-13 10:32 ` Lehua Ding
2023-11-13 10:33 ` Robin Dapp
2023-11-13 10:35 ` Lehua Ding
2023-11-13 11:13 ` Lehua Ding
2023-11-13 11:27 ` Lehua Ding
2023-11-15 10:47 ` 钟居哲
2023-11-17 8:29 ` Kito Cheng
2023-11-17 8:54 ` Lehua Ding
2023-11-17 8:56 ` Robin Dapp
2023-11-13 8:58 ` juzhe.zhong
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=2D241ED7BCDC3AB9+bae67ce6-4f85-41d6-a910-d8758e4c4b12@rivai.ai \
--to=lehua.ding@rivai.ai \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=juzhe.zhong@rivai.ai \
--cc=kito.cheng@gmail.com \
--cc=palmer@dabbelt.com \
--cc=rdapp.gcc@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).