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/112743] RISC-V: building FAIL with -march=rv64(or rv32)gc_zve32f_zvfh_zfh Date: Wed, 29 Nov 2023 06:51:00 +0000 [thread overview] Message-ID: <bug-112743-4-FHZfdkYylV@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112743-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112743 --- Comment #3 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Pan Li <panli@gcc.gnu.org>: https://gcc.gnu.org/g:25a51e98fdd504826a40775a5e5b9ffb336b5aa1 commit r14-5945-g25a51e98fdd504826a40775a5e5b9ffb336b5aa1 Author: Pan Li <pan2.li@intel.com> Date: Wed Nov 29 14:31:30 2023 +0800 RISC-V: Bugfix for ICE in block move when zve32f The exact_div requires the exactly multiple of the divider. Unfortunately, the condition will be broken when zve32f in some cases. For example, potential_ew is 8 BYTES_PER_RISCV_VECTOR * lmul1 is [4, 4] This patch would like to ensure the precondition of exact_div when get_vec_mode. PR target/112743 gcc/ChangeLog: * config/riscv/riscv-string.cc (expand_block_move): Add precondition check for exact_div. gcc/testsuite/ChangeLog: * gcc.target/riscv/rvv/base/pr112743-1.c: New test. Signed-off-by: Pan Li <pan2.li@intel.com>
next prev parent reply other threads:[~2023-11-29 6:51 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-28 8:16 [Bug c/112743] New: " juzhe.zhong at rivai dot ai 2023-11-28 8:19 ` [Bug c/112743] " pan2.li at intel dot com 2023-11-28 12:03 ` [Bug target/112743] " rguenth at gcc dot gnu.org 2023-11-29 6:51 ` cvs-commit at gcc dot gnu.org [this message] 2023-11-29 6:52 ` pan2.li at intel dot com 2023-12-02 3:18 ` cvs-commit at gcc dot gnu.org 2023-12-02 11:11 ` pan2.li at intel dot com 2023-12-02 13:59 ` 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-112743-4-FHZfdkYylV@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).