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/112773] [14 Regression] RISC-V ICE: in force_align_down_and_div, at poly-int.h:1828 on rv32gcv_zvl256b Date: Thu, 14 Dec 2023 20:13:07 +0000 [thread overview] Message-ID: <bug-112773-4-Pkee9U04eg@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112773-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112773 --- Comment #16 from Robin Dapp <rdapp at gcc dot gnu.org> --- I'd hope it was not fixed by this but just latent because we chose a VLS-mode vectorization instead. Hopefully we're better off with the fix than without :)
next prev parent reply other threads:[~2023-12-14 20:13 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-30 3:10 [Bug target/112773] New: " patrick at rivosinc dot com 2023-11-30 8:46 ` [Bug target/112773] " rguenth at gcc dot gnu.org 2023-11-30 9:06 ` juzhe.zhong at rivai dot ai 2023-11-30 17:10 ` patrick at rivosinc dot com 2023-12-01 1:57 ` juzhe.zhong at rivai dot ai 2023-12-01 2:01 ` juzhe.zhong at rivai dot ai 2023-12-01 2:02 ` juzhe.zhong at rivai dot ai 2023-12-01 2:05 ` patrick at rivosinc dot com 2023-12-01 2:05 ` juzhe.zhong at rivai dot ai 2023-12-01 10:27 ` rdapp at gcc dot gnu.org 2023-12-01 11:54 ` rdapp at gcc dot gnu.org 2023-12-01 12:07 ` rguenth at gcc dot gnu.org 2023-12-01 12:44 ` rdapp at gcc dot gnu.org 2023-12-01 13:20 ` rguenther at suse dot de 2023-12-01 21:16 ` rdapp at gcc dot gnu.org 2023-12-14 16:54 ` cvs-commit at gcc dot gnu.org 2023-12-14 19:51 ` patrick at rivosinc dot com 2023-12-14 20:13 ` rdapp at gcc dot gnu.org [this message] 2023-12-14 21:09 ` 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-112773-4-Pkee9U04eg@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).