public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/101226] Suboptimal codegen for >>/>>> Date: Fri, 16 Jul 2021 22:51:19 +0000 [thread overview] Message-ID: <bug-101226-4-yAaT66iYCV@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101226-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101226 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|normal |enhancement Component|d |tree-optimization Status|UNCONFIRMED |NEW Ever confirmed|0 |1 Last reconfirmed| |2021-07-16 Keywords| |missed-optimization CC| |pinskia at gcc dot gnu.org Assignee|ibuclaw at gdcproject dot org |unassigned at gcc dot gnu.org --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- _2 = (uint) value.1_1; _3 = _2 >> 5; _4 = (ubyte) _3; Right this could be optimized at the tree level to be : _4 = value.1_1 >> 5; Something like this for match.pd (note this is not fully correct just close enough for someone else to start): (simplify (convert (shift (convert@0 @1) INTEGER_CST@2)) (if (type == TREE_TYPE (@0) && TYPE_SIGN (TREE_TYPE(@0) == TYPE_SIGN (type)) (if (@2 >= bitsintype(type)) ({build_zero_cst (type);}) (shift @1 @2))))
next prev parent reply other threads:[~2021-07-16 22:51 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-26 16:14 [Bug d/101226] New: " maxsamukha at gmail dot com 2021-07-16 22:51 ` pinskia at gcc dot gnu.org [this message] 2023-05-02 4:06 ` [Bug tree-optimization/101226] " pinskia 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-101226-4-yAaT66iYCV@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).