public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/109011] missed optimization in presence of __builtin_ctz
Date: Mon, 06 Mar 2023 08:32:23 +0000	[thread overview]
Message-ID: <bug-109011-4-yneurxf3tN@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109011-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #16 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 54590
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54590&action=edit
gcc13-pr109011-2.patch

Here is what I have right now, totally untested and will need further work
so that the two pattern recognizers work together nicely (I think the one
modified by the earlier patch will for ctz/ffs need to trigger first and allow
ctz/ffs and be done even if for these they don't have direct optab but have
ctz (for ffs), clz or popcount.  And then let the new one rewrite it.

  parent reply	other threads:[~2023-03-06  8:32 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-03 14:56 [Bug tree-optimization/109011] New: " vincenzo.innocente at cern dot ch
2023-03-03 19:45 ` [Bug tree-optimization/109011] " pinskia at gcc dot gnu.org
2023-03-03 19:48 ` pinskia at gcc dot gnu.org
2023-03-03 20:21 ` jakub at gcc dot gnu.org
2023-03-03 20:39 ` jakub at gcc dot gnu.org
2023-03-03 20:46 ` jakub at gcc dot gnu.org
2023-03-04  0:18 ` jakub at gcc dot gnu.org
2023-03-04 11:14 ` jakub at gcc dot gnu.org
2023-03-04 12:22 ` jakub at gcc dot gnu.org
2023-03-04 14:01 ` jakub at gcc dot gnu.org
2023-03-04 15:08 ` jakub at gcc dot gnu.org
2023-03-06  5:26 ` crazylht at gmail dot com
2023-03-06  7:01 ` jakub at gcc dot gnu.org
2023-03-06  7:59 ` crazylht at gmail dot com
2023-03-06  8:11 ` jakub at gcc dot gnu.org
2023-03-06  8:23 ` crazylht at gmail dot com
2023-03-06  8:32 ` jakub at gcc dot gnu.org [this message]
2023-03-06  9:22 ` jakub at gcc dot gnu.org
2023-03-14  9:24 ` crazylht at gmail dot com
2023-03-16  6:32 ` crazylht at gmail dot com
2023-04-19  9:15 ` cvs-commit at gcc dot gnu.org
2023-04-20  9:56 ` cvs-commit at gcc dot gnu.org
2023-04-20 17:45 ` cvs-commit at gcc dot gnu.org
2023-04-24  1:35 ` cvs-commit 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-109011-4-yneurxf3tN@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).