public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "drepper.fsp+rhbz at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/107043] range information not used in popcount Date: Tue, 27 Sep 2022 10:19:10 +0000 [thread overview] Message-ID: <bug-107043-4-o9CCRhIUDJ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107043-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107043 --- Comment #2 from Ulrich Drepper <drepper.fsp+rhbz at gmail dot com> --- My original example and Andrew's g0 are handled by Aldy's patches 2022-09-26 Aldy Hernandez <aldyh@redhat.com> PR tree-optimization/107009 * range-op.cc (operator_bitwise_and::op1_range): Optimize 0 = x & MASK. (range_op_bitwise_and_tests): New test. 2022-09-26 Aldy Hernandez <aldyh@redhat.com> PR tree-optimization/107009 * tree-ssa-dom.cc (dom_opt_dom_walker::set_global_ranges_from_unreachable_edges): Iterate over exports. The g1 test case isn't handled, yet.
next prev parent reply other threads:[~2022-09-27 10:19 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-26 20:10 [Bug tree-optimization/107043] New: " drepper.fsp+rhbz at gmail dot com 2022-09-26 20:27 ` [Bug tree-optimization/107043] " pinskia at gcc dot gnu.org 2022-09-27 10:19 ` drepper.fsp+rhbz at gmail dot com [this message] 2022-09-27 14:29 ` aldyh at gcc dot gnu.org 2022-09-27 15:22 ` jakub at gcc dot gnu.org 2023-07-12 21:16 ` cvs-commit at gcc dot gnu.org 2023-07-12 21:19 ` aldyh 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-107043-4-o9CCRhIUDJ@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).