public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/55899] GCC should provide built-ins in <stdint.h> data types flavor/version/variation Date: Tue, 29 Nov 2022 18:59:26 +0000 [thread overview] Message-ID: <bug-55899-4-rwmHC8K8zp@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-55899-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55899 --- Comment #3 from joseph at codesourcery dot com <joseph at codesourcery dot com> --- C2x <stdbit.h> provides type-generic versions of various such operations, in addition to type-specific versions (but the type-specific versions are for unsigned char through unsigned long long, so don't themselves address the issue from this PR, and my view is that type-generic functions are error-prone in cases, such as clz, where the result depends on the type and not just the integer value of the argument). Since <stdbit.h> is a library facility (with functions thus expected to be available with external linkage to link against whether or not the header is included) I expect to implement it in due course in glibc, not GCC, though as usual built-in functions with the standard names would be appropriate in GCC.
prev parent reply other threads:[~2022-11-29 18:59 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-01-07 15:15 [Bug other/55899] New: " yann at droneaud dot fr 2013-01-10 17:30 ` [Bug other/55899] " hp at gcc dot gnu.org 2022-11-29 11:45 ` yann at droneaud dot fr 2022-11-29 18:59 ` joseph at codesourcery dot com [this message]
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-55899-4-rwmHC8K8zp@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).