public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/112789] Missing clang __builtin_ctzs for short Date: Thu, 30 Nov 2023 21:20:17 +0000 [thread overview] Message-ID: <bug-112789-4-bUAqud1Cpy@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112789-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112789 --- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> --- So just for future reference __builtin_c[lt]zs is for short. But with GCC 14 (trunk) added __builtin_ct[lt]g, there is no need to add __builtin_c[lt]zs to GCC. You could just do: #if __has_builtin(__builtin_ctzg) && !__has_builtin(__builtin_ctzs) #define ctzs(a) __builtin_ctzg((short)a) #elif __has_builtin(__builtin_ctzs) #define ctzs(a) __builtin_ctzs((short)a) #else #error implement fall back for not both cases #endif
next prev parent reply other threads:[~2023-11-30 21:20 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-30 20:59 [Bug c++/112789] New: " gonzalo.gadeschi at gmail dot com 2023-11-30 21:03 ` [Bug c++/112789] " pinskia at gcc dot gnu.org 2023-11-30 21:05 ` pinskia at gcc dot gnu.org 2023-11-30 21:08 ` pinskia at gcc dot gnu.org 2023-11-30 21:20 ` pinskia at gcc dot gnu.org [this message] 2023-12-01 7:07 ` jakub at gcc dot gnu.org 2023-12-02 23:32 ` gonzalo.gadeschi at gmail dot com 2023-12-02 23:36 ` pinskia at gcc dot gnu.org 2023-12-02 23:37 ` gonzalo.gadeschi at gmail dot com 2023-12-02 23:41 ` gonzalo.gadeschi at gmail dot com 2023-12-02 23:44 ` pinskia at gcc dot gnu.org 2023-12-02 23:44 ` sjames at gcc dot gnu.org 2023-12-03 0:20 ` pinskia at gcc dot gnu.org 2023-12-03 4:17 ` xry111 at gcc dot gnu.org 2023-12-03 12:14 ` 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-112789-4-bUAqud1Cpy@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).