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/112755] New: RISC-V regression testsuite errors with rv32gcv_zvl256b Date: Tue, 28 Nov 2023 23:43:10 +0000 [thread overview] Message-ID: <bug-112755-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112755 Bug ID: 112755 Summary: RISC-V regression testsuite errors with rv32gcv_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 56711 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56711&action=edit rv32gcv_zvl256b testsuite failures 2023-11-27 Current testsuite status of rv32gcv_zvl256b on GCC ad3e759c172272f6f2ba66631e7e7bd03fb2b436 I've started running rv32 zvl variants 128-1024b weekly on the postcommit CI. Artifacts for this run can be downloaded here: https://github.com/patrick-rivos/gcc-postcommit-ci/actions/runs/7012181120 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 rv32gcv_zvl256b with glibc v2.37 on QEMU v8.1.2
next reply other threads:[~2023-11-28 23:43 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-28 23:43 patrick at rivosinc dot com [this message] 2023-11-28 23:51 ` [Bug target/112755] " patrick at rivosinc dot com 2023-12-04 22:17 ` patrick at rivosinc dot com 2024-01-24 23:54 ` 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-112755-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).