From: Andrew Pinski <pinskia@gmail.com>
To: "juzhe.zhong@rivai.ai" <juzhe.zhong@rivai.ai>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>,
palmer <palmer@rivosinc.com>,
"Kito.cheng" <Kito.cheng@sifive.com>
Subject: Re: RISC-V Test Errors and Failures
Date: Tue, 16 May 2023 19:02:49 -0700 [thread overview]
Message-ID: <CA+=Sn1nsYXH6+JnfwEeVLzf-Rmw5YRyV4OZUGmA1T9oRq1PecA@mail.gmail.com> (raw)
In-Reply-To: <839CD64995EA7D11+2023051709574114343673@rivai.ai>
On Tue, May 16, 2023 at 6:58 PM juzhe.zhong@rivai.ai
<juzhe.zhong@rivai.ai> wrote:
>
> Hi, Palmer.
> I saw your patch showed there are a lot of run time fail (execution fail) of C++.
> bug-*.C
>
> These tests are RVV api intrinsics tests coming from Kito's that I have already fixed all of them.
> I just double checked again they all passed.
> I think it may be your regression environment does not set up simulator (QEMU or SPIKE or GEM5) correctly.
> For example, did not enable vector extension in simulator, I don't you may try.
So on x86_64, we test to see if you have the right vector unit before
running those tests? The same thing was true on powerpc (and I think
aarch64 does the same for SVE now too). The reason why I am asking is
that I would need to run the testsuite using the simulator as setup
for the RISCV ISA I am using rather than the one with everything on.
So does the RVV runtime testsuite tests to see if you can run RVV
before running them (or running them and return they passed)?
Thanks,
Andrew Pinski
>
> Thanks.
>
>
> juzhe.zhong@rivai.ai
next prev parent reply other threads:[~2023-05-17 2:03 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 1:57 juzhe.zhong
2023-05-17 2:02 ` Andrew Pinski [this message]
2023-05-17 2:07 ` juzhe.zhong
2023-05-17 2:13 ` Palmer Dabbelt
2023-05-17 2:20 ` Kito Cheng
2023-05-17 2:21 ` Kito Cheng
2023-05-17 2:46 ` Vineet Gupta
2023-05-17 2:47 ` Palmer Dabbelt
2023-05-17 2:51 ` Patrick O'Neill
2023-05-17 2:53 ` Palmer Dabbelt
2023-05-17 3:08 ` Vineet Gupta
2023-05-17 3:11 ` Palmer Dabbelt
2023-05-17 3:33 ` Kito Cheng
2023-05-17 4:04 ` Jeff Law
-- strict thread matches above, loose matches on Subject: below --
2023-05-16 23:06 Palmer Dabbelt
2023-05-17 0:16 ` Vineet Gupta
2023-05-17 0:20 ` Palmer Dabbelt
2023-05-17 1:04 ` Vineet Gupta
2023-05-17 1:29 ` Palmer Dabbelt
2023-05-17 2:00 ` Jeff Law
2023-05-17 2:05 ` Palmer Dabbelt
2023-05-17 2:32 ` Jeff Law
2023-05-17 2:39 ` Palmer Dabbelt
2023-05-17 4:08 ` Jeff Law
2023-05-17 2:08 ` Vineet Gupta
2023-05-17 2:12 ` Jeff Law
2023-05-17 7:52 ` Andreas Schwab
2023-05-19 0:13 ` Vineet Gupta
2023-05-25 20:29 ` Thomas Schwinge
2023-05-26 0:04 ` Vineet Gupta
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='CA+=Sn1nsYXH6+JnfwEeVLzf-Rmw5YRyV4OZUGmA1T9oRq1PecA@mail.gmail.com' \
--to=pinskia@gmail.com \
--cc=Kito.cheng@sifive.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=juzhe.zhong@rivai.ai \
--cc=palmer@rivosinc.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).