public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/113429] RISC-V: SPEC2017 527 cam4 miscompilation in autovec VLA build Date: Wed, 24 Jan 2024 01:19:29 +0000 [thread overview] Message-ID: <bug-113429-4-Rfy1cVWEDs@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113429-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113429 --- Comment #12 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Patrick O'Neill <poneill@gcc.gnu.org>: https://gcc.gnu.org/g:7f7d9c525c694e36ae525ed93ccd5b6ffad0f1d8 commit r14-8379-g7f7d9c525c694e36ae525ed93ccd5b6ffad0f1d8 Author: Patrick O'Neill <patrick@rivosinc.com> Date: Tue Jan 23 16:36:53 2024 -0800 RISC-V: Add regression test for vsetvl bug pr113429 The reduced testcase for pr113429 (cam4 failure) needed additional modules so it wasn't committed. The fuzzer found a c testcase that was also fixed with pr113429's fix. Adding it as a regression test. PR target/113429 gcc/testsuite/ChangeLog: * gcc.target/riscv/rvv/vsetvl/pr113429.c: New test. Signed-off-by: Patrick O'Neill <patrick@rivosinc.com>
prev parent reply other threads:[~2024-01-24 1:19 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-16 20:37 [Bug target/113429] New: " vineetg at gcc dot gnu.org 2024-01-16 20:39 ` [Bug target/113429] " vineetg at gcc dot gnu.org 2024-01-16 20:42 ` vineetg at gcc dot gnu.org 2024-01-16 20:58 ` vineetg at gcc dot gnu.org 2024-01-16 22:29 ` juzhe.zhong at rivai dot ai 2024-01-17 2:02 ` juzhe.zhong at rivai dot ai 2024-01-17 2:40 ` vineetg at gcc dot gnu.org 2024-01-17 22:24 ` juzhe.zhong at rivai dot ai 2024-01-17 22:45 ` vineetg at gcc dot gnu.org 2024-01-18 1:31 ` cvs-commit at gcc dot gnu.org 2024-01-18 1:33 ` juzhe.zhong at rivai dot ai 2024-01-19 3:23 ` vineetg at gcc dot gnu.org 2024-01-24 1:19 ` cvs-commit at gcc dot gnu.org [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-113429-4-Rfy1cVWEDs@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).