public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "aldyh at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/107342] Optimization opportunity where integer '/' corresponds to '>>' Date: Fri, 21 Oct 2022 19:10:37 +0000 [thread overview] Message-ID: <bug-107342-4-Yez2CbzFbc@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107342-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107342 --- Comment #2 from Aldy Hernandez <aldyh at gcc dot gnu.org> --- Created attachment 53749 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53749&action=edit untested patch I'm sure somebody smarter could handle other shift amounts that are not powers of 2, but this seems to do the trick for the test case. DOM2 does the threading and DOM3 will remove the second call to foo4b.
next prev parent reply other threads:[~2022-10-21 19:10 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-21 8:36 [Bug tree-optimization/107342] New: " tschwinge at gcc dot gnu.org 2022-10-21 19:04 ` [Bug tree-optimization/107342] " aldyh at gcc dot gnu.org 2022-10-21 19:10 ` aldyh at gcc dot gnu.org [this message] 2022-10-22 18:01 ` aldyh at gcc dot gnu.org 2022-11-04 14:18 ` cvs-commit at gcc dot gnu.org 2022-11-04 14:20 ` aldyh at gcc dot gnu.org 2022-11-28 22:13 ` 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-107342-4-Yez2CbzFbc@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).