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 rtl-optimization/109476] Missing optimization for 8bit/8bit multiplication / regression Date: Fri, 28 Apr 2023 13:22:40 +0000 [thread overview] Message-ID: <bug-109476-4-3Vlb1Eks4u@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109476-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109476 --- Comment #18 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Roger Sayle <sayle@gcc.gnu.org>: https://gcc.gnu.org/g:650c36ec461a722d9c65e82512b4c3aeec2ffee1 commit r14-335-g650c36ec461a722d9c65e82512b4c3aeec2ffee1 Author: Roger Sayle <roger@nextmovesoftware.com> Date: Fri Apr 28 14:21:53 2023 +0100 PR rtl-optimization/109476: Use ZERO_EXTEND instead of zeroing a SUBREG. This patch fixes PR rtl-optimization/109476, which is a code quality regression affecting AVR. The cause is that the lower-subreg pass is sometimes overly aggressive, lowering the LSHIFTRT below: (insn 7 4 8 2 (set (reg:HI 51) (lshiftrt:HI (reg/v:HI 49 [ b ]) (const_int 8 [0x8]))) "t.ii":4:36 557 {lshrhi3} (nil)) into a pair of QImode SUBREG assignments: (insn 19 4 20 2 (set (subreg:QI (reg:HI 51) 0) (reg:QI 54 [ b+1 ])) "t.ii":4:36 86 {movqi_insn_split} (nil)) (insn 20 19 8 2 (set (subreg:QI (reg:HI 51) 1) (const_int 0 [0])) "t.ii":4:36 86 {movqi_insn_split} (nil)) but this idiom, SETs of SUBREGs, interferes with combine's ability to associate/fuse instructions. The solution, on targets that have a suitable ZERO_EXTEND (i.e. where the lower-subreg pass wouldn't itself split a ZERO_EXTEND, so "splitting_zext" is false), is to split/lower LSHIFTRT to a ZERO_EXTEND. To answer Richard's question in comment #10 of the bugzilla PR, the function resolve_shift_zext is called with one of four RTX codes, ASHIFTRT, LSHIFTRT, ZERO_EXTEND and ASHIFT, but only with LSHIFTRT can the setting of low_part and high_part SUBREGs be replaced by a ZERO_EXTEND. For ASHIFTRT, we require a sign extension, so don't set the high_part to zero; if we're splitting a ZERO_EXTEND then it doesn't make sense to replace it with a ZERO_EXTEND, and for ASHIFT we've played games to swap the high_part and low_part SUBREGs, so that we assign the low_part to zero (for double word shifts by greater than word size bits). 2023-04-28 Roger Sayle <roger@nextmovesoftware.com> gcc/ChangeLog PR rtl-optimization/109476 * lower-subreg.cc: Include explow.h for force_reg. (find_decomposable_shift_zext): Pass an additional SPEED_P argument. If decomposing a suitable LSHIFTRT and we're not splitting ZERO_EXTEND (based on the current SPEED_P), then use a ZERO_EXTEND instead of setting a high part SUBREG to zero, which helps combine. (decompose_multiword_subregs): Update call to resolve_shift_zext. gcc/testsuite/ChangeLog PR rtl-optimization/109476 * gcc.target/avr/mmcu/pr109476.c: New test case.
next prev parent reply other threads:[~2023-04-28 13:22 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-11 19:19 [Bug c++/109476] New: " klaus.doldinger64 at googlemail dot com 2023-04-11 19:27 ` [Bug target/109476] " klaus.doldinger64 at googlemail dot com 2023-04-12 11:14 ` rguenth at gcc dot gnu.org 2023-04-12 11:33 ` klaus.doldinger64 at googlemail dot com 2023-04-12 12:21 ` [Bug rtl-optimization/109476] " rguenth at gcc dot gnu.org 2023-04-12 15:43 ` segher at gcc dot gnu.org 2023-04-12 16:48 ` klaus.doldinger64 at googlemail dot com 2023-04-12 18:43 ` roger at nextmovesoftware dot com 2023-04-12 20:20 ` klaus.doldinger64 at googlemail dot com 2023-04-12 20:56 ` segher at gcc dot gnu.org 2023-04-13 7:01 ` rguenth at gcc dot gnu.org 2023-04-13 12:55 ` klaus.doldinger64 at googlemail dot com 2023-04-13 15:19 ` segher at gcc dot gnu.org 2023-04-13 17:57 ` klaus.doldinger64 at googlemail dot com 2023-04-13 21:49 ` roger at nextmovesoftware dot com 2023-04-14 7:42 ` klaus.doldinger64 at googlemail dot com 2023-04-14 7:46 ` klaus.doldinger64 at googlemail dot com 2023-04-23 20:22 ` roger at nextmovesoftware dot com 2023-04-28 13:22 ` cvs-commit at gcc dot gnu.org [this message] 2023-05-07 8:30 ` roger at nextmovesoftware dot com
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-109476-4-3Vlb1Eks4u@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).