https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102989
--- Comment #54 from rguenther at suse dot de <rguenther at suse dot de> --- On Fri, 2 Jun 2023, jakub at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102989 > > Jakub Jelinek <jakub at gcc dot gnu.org> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Attachment #55169|0 |1 > is obsolete| | > > --- Comment #53 from Jakub Jelinek <jakub at gcc dot gnu.org> --- > Created attachment 55240 > --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55240&action=edit > gcc14-bitint-wip.patch > > Further updates. This introduces a new bitintlower (and bitintlower0) pass, > categorizes > _BitInt types into 4 categories (small, which are kept as is as they work out > of the box, middle, which have already more than one limb, but there exists > DImode or TImode > type which is supported and covers the precision, here lowering is done by > casting to > INTEGER_TYPE and back, large which is up to double that size (so it will be > lowered to straight line code) and huge, which will use loops. The lowering > is > so far implemented for the middle _BitInts. > Added some runtime testsuite coverage for the small and middle _BitInts (so on > x86-64 up to 128 bits). At least for -Os we probably want to consider moving everything but small and maybe middle to out of line library functions?
