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 rtl-optimization/109592] Failure to recognize shifts as sign/zero extension Date: Fri, 28 Apr 2023 20:26:17 +0000 [thread overview] Message-ID: <bug-109592-4-FhycJF6zk1@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109592-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109592 --- Comment #4 from Jeffrey A. Law <law at gcc dot gnu.org> --- If we need to handle subregs here, I would suggest something like this if (SUBREG_P (XEXP (op0, 0)) && subreg_lowpart_p (op0) ... other tests ... That way we know we're extracting the low word of the subreg. But I'm not sure at all why we need to handle them in this code. I would expect generic optimizers to strip away the subregs in the result if they are extraneous. It's not clear why you check the size of the subreg modes. It seems like this optimization should work even for a paradoxical subreg (bitsize of inner will be smaller than bitsize of outer). In general if you only have one statement in an arm of an IF-THEN-ELSE, then it need not be inside a { } block. Rather than using magic numbers like INTVAL (op1) + 8 == 32 Instead use mode information. INTVAL (op) + GET_MODE_BITSIZE (QImode) == GET_MODE_BITSIZE (SImode) // code for QI->SI expansion Then repeat for the other mode combinations. Note that we probably should go ahead and support QI->HI. While it doesn't happen for RISC-V, it could likely happen on other architectures. So you end up wanting to supprot QI->HI, QI->SI QI->DI HI->SI, HI->DI SI->DI I don't know if it happens in practice, so check first to see what we do for a zero extension variant of your original test. If we need to handle that too, it can be easily done by changing the shifts we recognize. Anyway, it looks like you're on the right track. I would suggest further discussions happen on gcc-patches. Anyway, it definitely looks like you're on the right track.
next prev parent reply other threads:[~2023-04-28 20:26 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-22 0:12 [Bug rtl-optimization/109592] New: " law at gcc dot gnu.org 2023-04-24 2:46 ` [Bug rtl-optimization/109592] " wangfeng at eswincomputing dot com 2023-04-24 3:52 ` wangfeng at eswincomputing dot com 2023-04-24 7:02 ` rguenth at gcc dot gnu.org 2023-04-28 20:26 ` law at gcc dot gnu.org [this message] 2023-05-11 7:56 ` wangfeng at eswincomputing dot com 2023-05-11 14:33 ` law at gcc dot gnu.org 2023-05-29 16:35 ` law at gcc dot gnu.org 2023-05-30 6:17 ` wangfeng at eswincomputing dot com 2023-05-30 20:40 ` law at gcc dot gnu.org 2023-05-30 20:41 ` 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-109592-4-FhycJF6zk1@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).