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 libstdc++/98226] Slow std::countr_one Date: Thu, 10 Dec 2020 22:00:09 +0000 [thread overview] Message-ID: <bug-98226-4-fPwaLcbikM@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 #4 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>: https://gcc.gnu.org/g:2ea62857a3fbdf091ba38cbb62e98dc76b198e2e commit r11-5922-g2ea62857a3fbdf091ba38cbb62e98dc76b198e2e Author: Jonathan Wakely <jwakely@redhat.com> Date: Thu Dec 10 21:57:42 2020 +0000 libstdc++: Remove redundant branches in countl_one and countr_one [PR 98226] There's no need to explicitly check for the maximum value, because the function we call handles it correctly anyway. libstdc++-v3/ChangeLog: PR libstdc++/98226 * include/std/bit (__countl_one, __countr_one): Remove redundant branches.
next prev parent reply other threads:[~2020-12-10 22:00 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 [this message] 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 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-fPwaLcbikM@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: linkBe 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).