public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/90693] Missing popcount simplifications
Date: Fri, 05 Jan 2024 10:17:46 +0000	[thread overview]
Message-ID: <bug-90693-4-2LNtPxrrmy@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-90693-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90693

--- Comment #10 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:

https://gcc.gnu.org/g:0152637c74c9eab7658483b1cca4e3d584dd4262

commit r14-6940-g0152637c74c9eab7658483b1cca4e3d584dd4262
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Fri Jan 5 11:16:58 2024 +0100

    Improve __builtin_popcount* (x) == 1 generation if x is known != 0
[PR90693]

    We expand __builtin_popcount* (x) == 1 as
    x ^ (x - 1) > x - 1, either unconditionally in tree-ssa-math-opts.cc
    if we don't have a direct optab support for popcount, or during
    expansion where we compare the costs of comparison of the popcount
    against one vs. the above expression.
    As mentioned in the PR, if we know from ranger that the argument is
    not zero, we can emit x & (x - 1) == 0 test which is same number of
    GIMPLE statements, but on many targets cheaper (e.g. whenever an AND
    instruction can also set flags on whether result was zero or not).

    The following patch does that.

    2024-01-05  Jakub Jelinek  <jakub@redhat.com>

            PR tree-optimization/90693
            * tree-ssa-math-opts.cc (match_single_bit_test): If
            tree_expr_nonzero_p (arg), remember it in the second argument to
            IFN_POPCOUNT or lower it as arg & (arg - 1) == 0 rather than
            arg ^ (arg - 1) > arg - 1.
            * internal-fn.cc (expand_POPCOUNT): If second argument to
            IFN_POPCOUNT suggests arg is non-zero, try to expand it as
            arg & (arg - 1) == 0 rather than arg ^ (arg - 1) > arg - 1.

            * gcc.target/i386/pr90693-2.c: New test.

  parent reply	other threads:[~2024-01-05 10:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-90693-4@http.gcc.gnu.org/bugzilla/>
2021-08-10 23:15 ` pinskia at gcc dot gnu.org
2023-11-20  9:04 ` cvs-commit at gcc dot gnu.org
2023-11-20  9:04 ` cvs-commit at gcc dot gnu.org
2023-11-20 14:10 ` wilco at gcc dot gnu.org
2023-11-20 17:01 ` jakub at gcc dot gnu.org
2024-01-01 12:41 ` piotrsiupa at gmail dot com
2024-01-03 15:34 ` jakub at gcc dot gnu.org
2024-01-05 10:17 ` cvs-commit at gcc dot gnu.org [this message]
2024-01-07 12:56 ` piotrsiupa at gmail dot com
2024-03-04  7:42 ` pinskia at gcc dot gnu.org
2024-03-04 16:41 ` pinskia at gcc dot gnu.org
2024-03-04 22:55 ` 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-90693-4-2LNtPxrrmy@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: link
Be 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).