public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rdapp at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/113087] [14] RISC-V rv64gcv vector: Runtime mismatch with rv64gc
Date: Mon, 22 Jan 2024 13:42:41 +0000 [thread overview]
Message-ID: <bug-113087-4-4wYuBcrICz@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113087-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113087
--- Comment #37 from Robin Dapp <rdapp at gcc dot gnu.org> ---
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113206#c9
> Using 4a0a8dc1b88408222b88e10278017189f6144602, the spec run failed on:
> zvl128b (All runtime fails):
> 527.cam4 (Runtime)
> 531.deepsjeng (Runtime)
> 521.wrf (Runtime)
> 523.xalancbmk (Runtime)
I tried reproducing the xalanc fail first but with the current trunk I don't
see a runtime fail. Going to try deepsjeng next.
next prev parent reply other threads:[~2024-01-22 13:42 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-19 22:20 [Bug target/113087] New: " patrick at rivosinc dot com
2023-12-19 22:28 ` [Bug target/113087] " juzhe.zhong at rivai dot ai
2023-12-19 22:45 ` patrick at rivosinc dot com
2023-12-19 22:51 ` juzhe.zhong at rivai dot ai
2023-12-19 23:42 ` patrick at rivosinc dot com
2023-12-20 2:12 ` juzhe.zhong at rivai dot ai
2023-12-20 2:21 ` patrick at rivosinc dot com
2023-12-20 23:06 ` cvs-commit at gcc dot gnu.org
2023-12-20 23:06 ` cvs-commit at gcc dot gnu.org
2023-12-20 23:25 ` juzhe.zhong at rivai dot ai
2023-12-21 2:55 ` patrick at rivosinc dot com
2023-12-21 19:22 ` patrick at rivosinc dot com
2023-12-21 22:43 ` juzhe.zhong at rivai dot ai
2023-12-22 19:59 ` vineetg at gcc dot gnu.org
2023-12-22 21:04 ` vineetg at gcc dot gnu.org
2023-12-22 22:21 ` juzhe.zhong at rivai dot ai
2023-12-22 23:07 ` vineetg at gcc dot gnu.org
2023-12-22 23:10 ` juzhe.zhong at rivai dot ai
2023-12-22 23:12 ` vineetg at gcc dot gnu.org
2023-12-22 23:14 ` juzhe.zhong at rivai dot ai
2023-12-22 23:20 ` juzhe.zhong at rivai dot ai
2023-12-22 23:21 ` juzhe.zhong at rivai dot ai
2023-12-22 23:33 ` palmer at gcc dot gnu.org
2023-12-22 23:36 ` juzhe.zhong at rivai dot ai
2023-12-22 23:37 ` juzhe.zhong at rivai dot ai
2023-12-23 2:21 ` jiawei at iscas dot ac.cn
2023-12-25 2:39 ` juzhe.zhong at rivai dot ai
2024-01-04 17:12 ` patrick at rivosinc dot com
2024-01-04 22:31 ` juzhe.zhong at rivai dot ai
2024-01-09 1:34 ` pan2.li at intel dot com
2024-01-10 22:16 ` patrick at rivosinc dot com
2024-01-10 23:09 ` juzhe.zhong at rivai dot ai
2024-01-11 0:33 ` patrick at rivosinc dot com
2024-01-11 0:37 ` vineetg at gcc dot gnu.org
2024-01-11 1:13 ` juzhe.zhong at rivai dot ai
2024-01-11 1:14 ` juzhe.zhong at rivai dot ai
2024-01-15 11:11 ` juzhe.zhong at rivai dot ai
2024-01-22 13:42 ` rdapp at gcc dot gnu.org [this message]
2024-01-22 14:39 ` rdapp at gcc dot gnu.org
2024-01-24 1:07 ` patrick at rivosinc dot com
2024-01-24 1:08 ` patrick at rivosinc dot com
2024-01-24 7:24 ` juzhe.zhong at rivai dot ai
2024-01-24 7:48 ` patrick at rivosinc dot com
2024-01-24 21:41 ` patrick at rivosinc dot com
2024-01-24 22:29 ` juzhe.zhong at rivai dot ai
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-113087-4-4wYuBcrICz@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).