public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zaikin.icc at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/98226] Slow std::countr_one
Date: Fri, 11 Dec 2020 12:16:46 +0000	[thread overview]
Message-ID: <bug-98226-4-pJIsVWMH4n@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98226-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #11 from Oleg Zaikin <zaikin.icc at gmail dot com> ---
(In reply to Jonathan Wakely from comment #8)
> That needs to be investigated, but it's a problem with the compiler. It has
> nothing to do with countr_one being implemented using countr_zero (as shown
> by the same problem being present when calling __builtin_ctz directly).

Thank you for the detailed clarification!

  parent reply	other threads:[~2020-12-11 12:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-10 16:51 [Bug libstdc++/98226] New: " zaikin.icc at gmail dot com
2020-12-10 17:31 ` [Bug libstdc++/98226] " redi at gcc dot gnu.org
2020-12-10 17:33 ` redi at gcc dot gnu.org
2020-12-10 18:08 ` pinskia at gcc dot gnu.org
2020-12-10 22:00 ` cvs-commit at gcc dot gnu.org
2020-12-10 22:08 ` redi at gcc dot gnu.org
2020-12-11  9:17 ` zaikin.icc at gmail dot com
2020-12-11  9:18 ` zaikin.icc at gmail dot com
2020-12-11 10:59 ` redi at gcc dot gnu.org
2020-12-11 11:08 ` redi at gcc dot gnu.org
2020-12-11 11:28 ` amonakov at gcc dot gnu.org
2020-12-11 12:16 ` zaikin.icc at gmail dot com [this message]
2020-12-11 12:21 ` zaikin.icc at gmail dot com
2020-12-11 12:33 ` zaikin.icc at gmail dot com
2021-03-29 20:01 ` 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-98226-4-pJIsVWMH4n@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).