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: Mon, 29 May 2023 16:35:33 +0000 [thread overview] Message-ID: <bug-109592-4-elRaTSjZgS@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 #7 from Jeffrey A. Law <law at gcc dot gnu.org> --- Attached is what I cobbled together. It doesn't use magic numbers. But it doesn't yet handle zero extensions in the simplify-rtx code. But I think it shows the overall direction fairly well.
next prev parent reply other threads:[~2023-05-29 16:35 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 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 [this message] 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-elRaTSjZgS@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).