From: Jeff Law <jeffreyalaw@gmail.com>
To: Jakub Jelinek <jakub@redhat.com>, Richard Biener <rguenther@suse.de>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] tree-ssa-math-opts: popcount (X) == 1 to (X ^ (X - 1)) > (X - 1) optimization for direct optab [PR90693]
Date: Sat, 18 Nov 2023 21:03:19 -0700 [thread overview]
Message-ID: <8c954624-1f07-456e-9a1d-7302e82375ab@gmail.com> (raw)
In-Reply-To: <ZViRqiN7i3waSY2v@tucnak>
On 11/18/23 03:27, Jakub Jelinek wrote:
> Hi!
>
> On Fri, Nov 17, 2023 at 03:01:04PM +0100, Jakub Jelinek wrote:
>> As a follow-up, I'm considering changing in this routine the popcount
>> call to IFN_POPCOUNT with 2 arguments and during expansion test costs.
>
> Here is the follow-up which does the rtx costs testing.
> While having to tweak internal-fn.def so that POPCOUNT can have a custom
> expand_POPCOUNT, I have noticed we are inconsistent, some DEF_INTERNAL*
> macros (most of them) were undefined at the end of internal-fn.def (but in
> some cases uselessly undefined again after inclusion), while others were not
> (and sometimes undefined after the inclusion). I've changed it to always
> undefine at the end of internal-fn.def.
>
> Ok for trunk if it passes bootstrap/regtest?
>
> 2023-11-18 Jakub Jelinek <jakub@redhat.com>
>
> PR tree-optimization/90693
> * tree-ssa-math-opts.cc (match_single_bit_test): Mark POPCOUNT with
> result only used in equality comparison against 1 with direct optab
> support as .POPCOUNT call with 2 arguments.
> * internal-fn.h (expand_POPCOUNT): Declare.
> * internal-fn.def: Document missing DEF_INTERNAL* macros and make sure
> they are all undefined at the end.
> (DEF_INTERNAL_INT_EXT_FN): New macro.
> (POPCOUNT): Use it instead of DEF_INTERNAL_INT_FN.
> * internal-fn.cc (lookup_hilo_internal_fn, lookup_evenodd_internal_fn,
> widening_fn_p, get_len_internal_fn): Don't undef DEF_INTERNAL_*FN
> macros after inclusion of internal-fn.def.
> (DEF_INTERNAL_INT_EXT_FN): Define to nothing before inclusion to
> define expanders.
> (expand_POPCOUNT): New function.
>
> + unsigned cmp_cost = seq_cost (cmp_insns, speed_p);
> + if (popcount_cost < cmp_cost)
> + emit_insn (popcount_insns);
> + else
> + {
> + emit_insn (cmp_insns);
> + plhs = expand_normal (lhs);
> + if (GET_MODE (cmp) != GET_MODE (plhs))
> + cmp = convert_to_mode (GET_MODE (plhs), cmp, 1);
> + emit_move_insn (plhs, cmp);
> + }
Did you want <= for the test to use popcount? That seems like a better
choice in that scenario to me as the popcount is likely smaller.
OK for the trunk as-is or using a <= test.
jeff
next prev parent reply other threads:[~2023-11-19 4:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-17 14:01 [PATCH] tree-ssa-math-opts: popcount (X) == 1 to (X ^ (X - 1)) > (X - 1) optimization [PR90693] Jakub Jelinek
2023-11-18 10:27 ` [PATCH] tree-ssa-math-opts: popcount (X) == 1 to (X ^ (X - 1)) > (X - 1) optimization for direct optab [PR90693] Jakub Jelinek
2023-11-19 4:03 ` Jeff Law [this message]
2023-11-20 8:01 ` Richard Biener
2023-11-20 9:05 ` Jakub Jelinek
2023-11-19 3:59 ` [PATCH] tree-ssa-math-opts: popcount (X) == 1 to (X ^ (X - 1)) > (X - 1) optimization [PR90693] Jeff Law
2023-11-20 7:54 ` Richard Biener
2023-11-20 8:37 ` Jakub Jelinek
2023-11-20 8:39 ` Richard Biener
2023-11-20 8:41 ` Jakub Jelinek
2023-11-20 13:03 ` Jeff Law
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=8c954624-1f07-456e-9a1d-7302e82375ab@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=rguenther@suse.de \
/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).