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/99396] std::rotl and std::rotr Does not convert into ROTATE on the gimple level Date: Fri, 05 Mar 2021 09:50:29 +0000 [thread overview] Message-ID: <bug-99396-4-kgYpw27s7K@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99396-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99396 --- Comment #8 from Jakub Jelinek <jakub at gcc dot gnu.org> --- so using __unsigned_type = __make_unsigned<_Tp>::__type; constexpr auto _Nd = __gnu_cxx::__int_traits<__unsigned_type>::__digits; const auto __r = static_cast<unsigned int>(__s); const auto __y = static_cast<__unsigned_type>(__x; const auto __z = (__y << (__r % _Nd)) | (__y >> ((-__r) % _Nd)); return static_cast<_Tp>(__z); ? Of course, if _Tp can be anything other than integral types, it would need to be a specialization for integral types (though it will work for __int128 fine if that doesn't count as integral).
next prev parent reply other threads:[~2021-03-05 9:50 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-04 23:09 [Bug libstdc++/99396] New: std::rotl and std::rotr do not invoke intrinsics, leading to serious performance issues unlvsur at live dot com 2021-03-05 0:05 ` [Bug tree-optimization/99396] " pinskia at gcc dot gnu.org 2021-03-05 0:06 ` [Bug tree-optimization/99396] std::rotl and std::rotr Does not convert into ROTATE on the gimple level pinskia at gcc dot gnu.org 2021-03-05 2:08 ` unlvsur at live dot com 2021-03-05 3:12 ` pinskia at gcc dot gnu.org 2021-03-05 3:18 ` unlvsur at live dot com 2021-03-05 8:25 ` redi at gcc dot gnu.org 2021-03-05 9:36 ` jakub at gcc dot gnu.org 2021-03-05 9:44 ` jakub at gcc dot gnu.org 2021-03-05 9:50 ` jakub at gcc dot gnu.org [this message] 2021-03-05 10:38 ` jakub at gcc dot gnu.org 2021-03-05 10:47 ` redi at gcc dot gnu.org 2021-03-05 10:52 ` jakub at gcc dot gnu.org 2021-03-05 11:02 ` jakub at gcc dot gnu.org 2021-03-05 11:59 ` unlvsur at live dot com 2021-03-05 12:03 ` jakub at gcc dot gnu.org 2021-03-05 12:04 ` jakub at gcc dot gnu.org 2021-03-05 12:08 ` unlvsur at live dot com 2021-03-05 12:09 ` unlvsur at live dot com 2021-03-05 12:12 ` unlvsur at live dot com 2021-03-06 10:12 ` cvs-commit at gcc dot gnu.org 2021-03-06 10:13 ` jakub 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-99396-4-kgYpw27s7K@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).