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/94793] Failure to optimize clz idiom
Date: Mon, 16 Jan 2023 10:48:04 +0000	[thread overview]
Message-ID: <bug-94793-4-LeuAMGGE7f@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94793-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Andrew Carlotti <acarlotti@gcc.gnu.org>:

https://gcc.gnu.org/g:d347fbf774dc50bf7511f4dc6bc74547ed364995

commit r13-5193-gd347fbf774dc50bf7511f4dc6bc74547ed364995
Author: Andrew Carlotti <andrew.carlotti@arm.com>
Date:   Thu Nov 10 15:56:51 2022 +0000

    Add cltz_complement idiom recognition

    This recognises patterns of the form:
    while (n) { n >>= 1 }

    This patch results in improved (but still suboptimal) codegen:

    foo (unsigned int b) {
        int c = 0;

        while (b) {
            b >>= 1;
            c++;
        }

        return c;
    }

    foo:
    .LFB11:
            .cfi_startproc
            cbz     w0, .L3
            clz     w1, w0
            tst     x0, 1
            mov     w0, 32
            sub     w0, w0, w1
            csel    w0, w0, wzr, ne
            ret

    The conditional is unnecessary. phiopt could recognise a redundant csel
    (using cond_removal_in_builtin_zero_pattern) when one of the inputs is a
    clz call, but it cannot recognise the redunancy when the input is (e.g.)
    (32 - clz).

    I could perhaps extend this function to recognise this pattern in a later
    patch, if this is a good place to recognise more patterns.

    gcc/ChangeLog:

            PR tree-optimization/94793
            * tree-scalar-evolution.cc (expression_expensive_p): Add checks
            for c[lt]z optabs.
            * tree-ssa-loop-niter.cc (build_cltz_expr): New.
            (number_of_iterations_cltz_complement): New.
            (number_of_iterations_bitcount): Add call to the above.

    gcc/testsuite/ChangeLog:

            * lib/target-supports.exp (check_effective_target_clz)
            (check_effective_target_clzl, check_effective_target_clzll)
            (check_effective_target_ctz, check_effective_target_clzl)
            (check_effective_target_ctzll): New.
            * gcc.dg/tree-ssa/cltz-complement-max.c: New test.
            * gcc.dg/tree-ssa/clz-complement-char.c: New test.
            * gcc.dg/tree-ssa/clz-complement-int.c: New test.
            * gcc.dg/tree-ssa/clz-complement-long-long.c: New test.
            * gcc.dg/tree-ssa/clz-complement-long.c: New test.
            * gcc.dg/tree-ssa/ctz-complement-char.c: New test.
            * gcc.dg/tree-ssa/ctz-complement-int.c: New test.
            * gcc.dg/tree-ssa/ctz-complement-long-long.c: New test.
            * gcc.dg/tree-ssa/ctz-complement-long.c: New test.

      parent reply	other threads:[~2023-01-16 10:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-27 10:00 [Bug tree-optimization/94793] New: " gabravier at gmail dot com
2020-04-27 10:12 ` [Bug tree-optimization/94793] " rguenth at gcc dot gnu.org
2020-05-07 17:06 ` jakub at gcc dot gnu.org
2021-08-03 23:20 ` pinskia at gcc dot gnu.org
2022-05-25 13:37 ` tnfchris at gcc dot gnu.org
2023-01-16 10:48 ` cvs-commit at gcc dot gnu.org [this message]

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-94793-4-LeuAMGGE7f@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).