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/116592] illegal operands th.vsetvli zero,0,e32,m8 with -O2 -O3 when compiling for risc-v xtheadvector Date: Sat, 07 Sep 2024 16:30:35 +0000 [thread overview] Message-ID: <bug-116592-4-gaIMRxk8sn@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-116592-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116592 --- Comment #6 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jeff Law <law@gcc.gnu.org>: https://gcc.gnu.org/g:d620499b3a24f14cfb98529640584e63d7eca149 commit r15-3527-gd620499b3a24f14cfb98529640584e63d7eca149 Author: Jin Ma <jinma@linux.alibaba.com> Date: Sat Sep 7 10:29:02 2024 -0600 [PATCH v4] [target/116592] RISC-V: Fix illegal operands "th.vsetvli zero,0,e32,m8" for XTheadVector Since the THeadVector vsetvli does not support vl as an immediate, we need to convert 0 to zero when outputting asm. PR target/116592 gcc/ChangeLog: * config/riscv/thead.cc (th_asm_output_opcode): Change '0' to "zero" gcc/testsuite/ChangeLog: * gcc.target/riscv/rvv/xtheadvector/pr116592.c: New test.
next prev parent reply other threads:[~2024-09-07 16:30 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-09-04 5:16 [Bug target/116592] New: " shuizhuyuanluo at gmail dot com 2024-09-04 5:20 ` [Bug target/116592] " pinskia at gcc dot gnu.org 2024-09-04 6:02 ` kito at gcc dot gnu.org 2024-09-04 11:14 ` cooper.qu at linux dot alibaba.com 2024-09-04 11:16 ` jinma at linux dot alibaba.com 2024-09-06 7:16 ` jinma at linux dot alibaba.com 2024-09-07 16:30 ` cvs-commit at gcc dot gnu.org [this message] 2024-09-22 21:25 ` law at gcc dot gnu.org
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-116592-4-gaIMRxk8sn@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).