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 jos...@codesourcery.com
