public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "patrick at rivosinc dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/113206] [14] RISC-V rv64gcv vector: Runtime mismatch with rv64gc
Date: Thu, 04 Jan 2024 16:44:43 +0000 [thread overview]
Message-ID: <bug-113206-4-6tMDtLXGDV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113206-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113206
--- Comment #9 from Patrick O'Neill <patrick at rivosinc dot com> ---
(In reply to JuzheZhong from comment #8)
> It seems that we still didn't locate the real problem of failed SPEC you ran.
> Do you have any other ideas to locale the real problem ?
>
> Li Pan didn't locate the problem neither.
Using 4a0a8dc1b88408222b88e10278017189f6144602, the spec run failed on:
zvl128b (All runtime fails):
527.cam4 (Runtime)
531.deepsjeng (Runtime)
521.wrf (Runtime)
523.xalancbmk (Runtime)
zvl256b:
507.cactuBSSN (Runtime)
521.wrf (Build)
527.cam4 (Runtime)
531.deepsjeng (Runtime)
549.fotonik3d (Runtime)
With that info I think the next steps are:
1. Triage the zvl256b 521.wrf build failure
2. Bisect the newly-failing testcases
3. Finish triaging the remaining testcases the fuzzer found
4. Attempt to manually reduce cam4 for zvl128b (since it seems to have the
fastest build+runtime)
5. Attempt to manually reduce other fails.
prev parent reply other threads:[~2024-01-04 16:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-02 19:08 [Bug target/113206] New: " patrick at rivosinc dot com
2024-01-02 23:20 ` [Bug target/113206] " juzhe.zhong at rivai dot ai
2024-01-02 23:26 ` patrick at rivosinc dot com
2024-01-03 1:15 ` juzhe.zhong at rivai dot ai
2024-01-04 0:33 ` cvs-commit at gcc dot gnu.org
2024-01-04 0:47 ` juzhe.zhong at rivai dot ai
2024-01-04 1:36 ` patrick at rivosinc dot com
2024-01-04 2:32 ` patrick at rivosinc dot com
2024-01-04 3:46 ` juzhe.zhong at rivai dot ai
2024-01-04 16:44 ` patrick at rivosinc dot com [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=bug-113206-4-6tMDtLXGDV@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).