From: Joseph Myers <joseph@codesourcery.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Richard Biener <rguenther@suse.de>,
Jason Merrill <jason@redhat.com>, <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Add type-generic clz/ctz/clrsb/ffs/parity/popcount builtins [PR111309]
Date: Thu, 9 Nov 2023 21:43:41 +0000 [thread overview]
Message-ID: <88c58cc-df3-f755-55f3-c7f483dee465@codesourcery.com> (raw)
In-Reply-To: <ZUz0fdighFsO3Na6@tucnak>
On Thu, 9 Nov 2023, Jakub Jelinek wrote:
> The main reason to add these is to support arbitrary unsigned (for
> clrsb/ffs signed) bit-precise integer types and also __int128 which
> wasn't supported by the existing builtins, so that e.g. <stdbit.h>
> type-generic functions could then support not just bit-precise unsigned
> integer type whose width matches a standard or extended integer type,
> but others too.
Thanks for working on this. My plan for the <stdbit.h> implementation I'm
working on for glibc is to start with implementations using existing
built-in functions (and only handling types whose width matches standard
types), then supporting _BitInt with these new built-in functions will be
suitable for a followup.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2023-11-09 21:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-09 15:02 Jakub Jelinek
2023-11-09 21:43 ` Joseph Myers [this message]
2023-11-10 8:09 ` Richard Biener
2023-11-10 9:10 ` Jakub Jelinek
2023-11-10 9:19 ` Richard Biener
2023-11-10 9:44 ` Jakub Jelinek
2023-11-11 8:18 ` Jakub Jelinek
2023-11-13 23:45 ` Joseph Myers
2023-12-16 5:51 ` Andrew Pinski
2023-12-16 8:36 ` Jakub Jelinek
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=88c58cc-df3-f755-55f3-c7f483dee465@codesourcery.com \
--to=joseph@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=jason@redhat.com \
--cc=rguenther@suse.de \
/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: link
Be 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).