public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/109040] [13 Regression] wrong code with v16hi compare & mask on riscv64 at -O2 since r13-4907-g2e886eef7f2b5a Date: Tue, 04 Apr 2023 12:54:20 +0000 [thread overview] Message-ID: <bug-109040-4-usLHK1uItb@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109040-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109040 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Created attachment 54808 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54808&action=edit gcc13-riscv-mvconst.patch I think it is weird to have multiple mov like patterns. I've tried to get rid of this by adding a new predicate for *movsi_internal/*movdi_64bit, which after expansion and until end of split1 accepts the splittable constants and turn the current *mvconst_internal into a pure splitter. This doesn't fix the PR though, but I think it would be a good idea anyway.
next prev parent reply other threads:[~2023-04-04 12:54 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-06 11:14 [Bug target/109040] New: [13 Regression] wrong code with v16hi compare & mask on riscv64 at -O2 zsojka at seznam dot cz 2023-03-07 9:01 ` [Bug target/109040] " rguenth at gcc dot gnu.org 2023-03-27 8:29 ` marxin at gcc dot gnu.org 2023-03-27 8:45 ` [Bug target/109040] [13 Regression] wrong code with v16hi compare & mask on riscv64 at -O2 since r13-4907-g2e886eef7f2b5a marxin at gcc dot gnu.org 2023-04-04 12:54 ` jakub at gcc dot gnu.org [this message] 2023-04-04 13:41 ` jakub at gcc dot gnu.org 2023-04-04 13:46 ` jakub at gcc dot gnu.org 2023-04-04 15:02 ` jakub at gcc dot gnu.org 2023-04-04 20:08 ` ebotcazou at gcc dot gnu.org 2023-04-05 14:17 ` law at gcc dot gnu.org 2023-04-14 7:32 ` cvs-commit at gcc dot gnu.org 2023-04-19 9:13 ` cvs-commit 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-109040-4-usLHK1uItb@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).