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] New: Slow std::countr_one Date: Thu, 10 Dec 2020 16:51:20 +0000 [thread overview] Message-ID: <bug-98226-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98226 Bug ID: 98226 Summary: Slow std::countr_one Product: gcc Version: 10.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: zaikin.icc at gmail dot com Target Milestone: --- The function std::countr_one() from C++20 is slow. For a given x (say, unsigned int) it in fact calls std::countr_zero(~x) which in turn calls __builtin_ctz(~x). Calling __builtin_ctz(~x) directly from std::countr_one() would increase the performance. The test case contains three sources, each of which finally does the same but with different performance. Test case: --- test1.cpp: #include <bit> int main() { unsigned j; for (unsigned i=0; i<(1 << 30); i++) { j = std::countr_one(i); } } --- g++ -std=c++20 ./test1.cpp -o test1 test2.cpp: #include <bit> int main() { unsigned j; for (unsigned i=0; i<(1 << 30); i++) { j = std::countr_zero(~i); } } --- g++ -std=c++20 ./test2.cpp -o test2 test3.cpp: #include <bit> int main() { unsigned j; for (unsigned i=0; i<(1 << 30); i++) { j = __builtin_ctz(~i); } } --- g++ -std=c++20 ./test3.cpp -o test3 The user time is reported below: time ./test1 5.266s time ./test2 3.028s time ./test3 0.741s $ g++ -v Using built-in specs. COLLECT_GCC=g++ COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/10/lto-wrapper OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa:hsa OFFLOAD_TARGET_DEFAULT=1 Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu 10.2.0-5ubuntu1~20.04' --with-bugurl=file:///usr/share/doc/gcc-10/README.Bugs --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,m2 --prefix=/usr --with-gcc-major-version-only --program-suffix=-10 --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-plugin --enable-default-pie --with-system-zlib --enable-libphobos-checking=release --with-target-system-zlib=auto --enable-objc-gc=auto --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none=/build/gcc-10-WJNXnb/gcc-10-10.2.0/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/gcc-10-WJNXnb/gcc-10-10.2.0/debian/tmp-gcn/usr,hsa --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu Thread model: posix Supported LTO compression algorithms: zlib zstd gcc version 10.2.0 (Ubuntu 10.2.0-5ubuntu1~20.04)
next reply other threads:[~2020-12-10 16:51 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-10 16:51 zaikin.icc at gmail dot com [this message] 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 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@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).