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 c/111309] va_arg alternative for _BitInt Date: Wed, 06 Sep 2023 17:29:50 +0000 [thread overview] Message-ID: <bug-111309-4-s2z07ulgtO@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111309-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111309 --- Comment #1 from joseph at codesourcery dot com <joseph at codesourcery dot com> --- Yes, we should have APIs for building type-generic _BitInt interfaces (also a width-of operation to give the width in bits of an integer type; also type-generic versions of operations such as clz, ctz, parity, popcount that work to the width in bits of any unsigned operand). Though I suspect any library implementations of printf _BitInt support would end up needing architecture-specific workarounds for a while to avoid depending on having GCC new enough to support _BitInt in order to build a library with that support.
next prev parent reply other threads:[~2023-09-06 17:29 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-06 17:05 [Bug c/111309] New: " jakub at gcc dot gnu.org 2023-09-06 17:29 ` joseph at codesourcery dot com [this message] 2023-09-06 17:40 ` [Bug c/111309] " jakub at gcc dot gnu.org 2023-09-06 17:47 ` joseph at codesourcery dot com 2023-11-14 9:52 ` cvs-commit at gcc dot gnu.org 2023-11-20 10:31 ` clyon at gcc dot gnu.org 2023-11-20 16:55 ` jakub at gcc dot gnu.org 2023-11-21 9:04 ` 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-111309-4-s2z07ulgtO@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).