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/112597] New: RISC-V regression testsuite errors with rv64gcv_zvl256b Date: Fri, 17 Nov 2023 21:15:44 +0000 [thread overview] Message-ID: <bug-112597-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112597 Bug ID: 112597 Summary: RISC-V regression testsuite errors with rv64gcv_zvl256b Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: patrick at rivosinc dot com Target Milestone: --- Created attachment 56624 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56624&action=edit rv64gcv_zvl256b testsuite failures 2023-11-17 Current testsuite status of rv64gcv_zvl256b on GCC 5cb13173e85537a8a423b7b22b60ca3b6505f91e I've started running zvl variants 128-1024b weekly on the postcommit CI. This is my first time running these so if any of the failures look odd poke me here or via email and I can dig into/share the logs. Artifacts for this run can be downloaded here: https://github.com/patrick-rivos/gcc-postcommit-ci/actions/runs/6898356494 Likely artifacts of interest: gcc-linux-rv64gcv_zvl-lp64d-5cb13173e85537a8a423b7b22b60ca3b6505f91e-multilib-debug-output.log gcc-linux-rv64gcv_zvl-lp64d-5cb13173e85537a8a423b7b22b60ca3b6505f91e-multilib-report.log gcc-linux-rv64gcv_zvl-lp64d-5cb13173e85537a8a423b7b22b60ca3b6505f91e-multilib-sum-files This is just a tracking issue, similar to https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111311 I've attached the current results for rv64gcv_zvl256b with glibc v2.37 on QEMU v8.1.2
next reply other threads:[~2023-11-17 21:15 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-17 21:15 patrick at rivosinc dot com [this message] 2023-11-17 21:21 ` [Bug target/112597] " patrick at rivosinc dot com 2023-11-20 10:16 ` juzhe.zhong at rivai dot ai 2023-11-20 13:54 ` cvs-commit at gcc dot gnu.org 2023-11-21 2:41 ` juzhe.zhong at rivai dot ai 2023-11-21 17:36 ` patrick at rivosinc dot com 2023-11-21 17:39 ` patrick at rivosinc dot com 2023-11-21 22:10 ` juzhe.zhong at rivai dot ai 2023-11-21 22:38 ` patrick at rivosinc dot com 2023-11-27 17:34 ` patrick at rivosinc dot com 2023-11-27 17:39 ` patrick at rivosinc dot com 2023-12-04 21:30 ` patrick at rivosinc dot com 2023-12-11 22:04 ` patrick at rivosinc dot com 2024-01-24 23:53 ` patrick at rivosinc dot com
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-112597-4@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: linkBe 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).