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: Mon, 20 Nov 2023 09:04:19 +0000 [thread overview]
Message-ID: <bug-90693-4-LhPfefxsvR@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 #5 from CVS 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:103a3966bc7b68f91b6cd3c5beb330c4b8570c90
commit r14-5613-g103a3966bc7b68f91b6cd3c5beb330c4b8570c90
Author: Jakub Jelinek <jakub@redhat.com>
Date: Mon Nov 20 10:03:20 2023 +0100
tree-ssa-math-opts: popcount (X) == 1 to (X ^ (X - 1)) > (X - 1)
optimization for direct optab [PR90693]
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.
2023-11-20 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 (DEF_INTERNAL_INT_EXT_FN): New macro, document
it,
undefine at the end.
(POPCOUNT): Use it instead of DEF_INTERNAL_INT_FN.
* internal-fn.cc (DEF_INTERNAL_INT_EXT_FN): Define to nothing
before
inclusion to define expanders.
(expand_POPCOUNT): New function.
next prev parent reply other threads:[~2023-11-20 9:04 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 [this message]
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
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-LhPfefxsvR@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).