Re: [ft-devel] Undefined behavior

[Alexei Podtelezhnikov]

>> Ok. I still do not think that we should fix the macro, because there
>> is no good value to return. Returning zero for zero is bad too. One
>> should not call MSB or the builtins with zero argument, just like one
>> should not divide by zero. So I'll try to apply fix the callers.
>
> It's sometimes more convenient to have such defined behaviors as returning 0
> for 0 in MSB as it makes caller code both cleaner and safer, like what was
> there before.

I pushed all the necessary changes. I do not see *any* possibility now
to encounter undefined FT_MSB. Please review.