public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "law at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/106602] riscv: suboptimal codegen for zero_extendsidi2_shifted w/o bitmanip Date: Wed, 02 Nov 2022 00:46:16 +0000 [thread overview] Message-ID: <bug-106602-4-uhdrNvbNa1@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106602-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106602 --- Comment #12 from Jeffrey A. Law <law at gcc dot gnu.org> --- But insns 6, 7 and 8 aren't important here. We have a REG_EQUAL on insn 9 which indicates that (reg:DI 77) has the value 0xffffffffffffffc0. So I would have expected combine to substitute that into the use of (reg:DI 77) in insn 10 which would give you a shot a recognizing the result is just a pair of shifts. But the REG_EQUAL doesn't seem to be used in that case. My insn #s are different, but here's the relevant part of the dump: Trying 9 -> 15: 9: r139:DI=r141:DI-0x40 REG_DEAD r141:DI REG_EQUAL 0x3fffffffc0 15: a0:DI=r138:DI&r139:DI REG_DEAD r138:DI REG_DEAD r139:DI Failed to match this instruction: (set (reg/i:DI 10 a0) (and:DI (plus:DI (reg:DI 141) (const_int -64 [0xffffffffffffffc0])) (reg:DI 138))) BUt we know the (and (plus ...))) is just 0x3fffffffc0, what's not clear is why we don't use that information and try to recognize (set (reg:DI 10) (and (reg:DI 138) (const_int 0x3fffffffc0)) Which is just a pair of shifts.
next prev parent reply other threads:[~2022-11-02 0:46 UTC|newest] Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-08-12 20:34 [Bug target/106602] New: riscv: suboptimal codegen for shift left, right, left vineetg at rivosinc dot com 2022-08-12 20:39 ` [Bug target/106602] " pinskia at gcc dot gnu.org 2022-08-12 20:40 ` vineetg at rivosinc dot com 2022-11-01 0:12 ` [Bug target/106602] riscv: suboptimal codegen for zero_extendsidi2_shifted w/o bitmanip vineetg at rivosinc dot com 2022-11-01 0:18 ` pinskia at gcc dot gnu.org 2022-11-01 0:29 ` vineetg at rivosinc dot com 2022-11-01 0:32 ` vineetg at rivosinc dot com 2022-11-01 19:56 ` law at gcc dot gnu.org 2022-11-01 19:58 ` law at gcc dot gnu.org 2022-11-01 20:15 ` palmer at gcc dot gnu.org 2022-11-01 20:31 ` vineetg at rivosinc dot com 2022-11-01 23:39 ` vineetg at rivosinc dot com 2022-11-02 0:38 ` vineetg at rivosinc dot com 2022-11-02 0:46 ` law at gcc dot gnu.org [this message] 2022-11-02 1:03 ` law at gcc dot gnu.org 2022-11-02 1:24 ` vineetg at rivosinc dot com 2022-11-02 1:31 ` law at gcc dot gnu.org 2022-11-02 1:35 ` pinskia at gcc dot gnu.org 2022-11-02 1:35 ` pinskia at gcc dot gnu.org 2022-11-02 15:11 ` law at gcc dot gnu.org 2022-11-02 17:02 ` vineetg at rivosinc dot com 2022-11-02 17:05 ` vineetg at rivosinc dot com 2022-11-02 17:16 ` law at gcc dot gnu.org 2022-11-03 4:15 ` vineetg at rivosinc dot com 2022-11-03 20:41 ` vineetg at rivosinc dot com 2022-11-03 21:21 ` vineetg at rivosinc dot com 2022-11-16 17:55 ` law at gcc dot gnu.org 2022-11-16 18:47 ` law at gcc dot gnu.org 2022-12-27 23:31 ` cvs-commit at gcc dot gnu.org 2022-12-27 23:33 ` law at gcc dot gnu.org 2023-04-17 18:14 ` cvs-commit at gcc dot gnu.org 2023-04-19 2:41 ` 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-106602-4-uhdrNvbNa1@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).