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/106543] [11/12/13/14 Regression] *sge<u>_<X:mode><GPR:mode> uses operand 2 but there is no operand 2 Date: Fri, 16 Feb 2024 10:10:24 +0000 [thread overview] Message-ID: <bug-106543-4-H9ONjbjci3@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106543-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106543 --- Comment #3 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Kito Cheng <kito@gcc.gnu.org>: https://gcc.gnu.org/g:325d5dd53270fe8fd62b36c92c8f8b87c2938bf1 commit r14-9025-g325d5dd53270fe8fd62b36c92c8f8b87c2938bf1 Author: Kito Cheng <kito.cheng@sifive.com> Date: Fri Feb 16 17:27:24 2024 +0800 RISC-V: Fix *sge<u>_<X:mode><GPR:mode> pattern *sge<u>_<X:mode><GPR:mode> pattern has referenced operand[2] which is invalid...it should just use `slti<u>` rather than `slti%i2<u>`. gcc/ChangeLog: PR target/106543 * config/riscv/riscv.md (*sge<u>_<X:mode><GPR:mode>): Fix asm pattern.
prev parent reply other threads:[~2024-02-16 10:10 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-08-06 4:47 [Bug target/106543] New: " pinskia at gcc dot gnu.org 2023-03-22 6:17 ` [Bug target/106543] [10/11/12 Regression] " pinskia at gcc dot gnu.org 2023-03-27 14:12 ` [Bug target/106543] [10/11/12/13 " rguenth at gcc dot gnu.org 2023-07-07 10:43 ` [Bug target/106543] [11/12/13/14 " rguenth at gcc dot gnu.org 2024-02-16 10:10 ` 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-106543-4-H9ONjbjci3@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).