[PATCH] Make BITMAP_WORD more easily configurable

[Martin Sebor]

On 7/30/19 9:19 AM, Jakub Jelinek wrote:
> On Tue, Jul 30, 2019 at 09:16:45AM -0600, Martin Sebor wrote:
>> Say something like this POC:
> 
> We have those already, see ctz_hwi, clz_hwi etc.
> The thing is that BITMAP_WORD isn't always the same type as unsigned
> HOST_WIDE_INT, and so we need ones with the BITMAP_WORD type.

That sounds like a problem overloading would solve to the benefit
of all clients.  I.e., overload count_trailing_zeros (or whatever
other name) to take integer arguments of all widths (signed and
unsigned) and call the appropriate built-in from each.  That way
we just have to remember one function name and know that it will
be the right choice regardless of the type of the argument.

Martin