Bit twiddling builtins

[Richard Henderson]

On Wed, Jan 29, 2003 at 12:43:25PM +0100, Falk Hueffner wrote:
> Well, the comment above that seemed to imply that some makes or shells
> have probems with variables longer than 256 characters, and when I add
> them to LIB2FUNCS_2, it does get longer than that. If this is no
> longer relevant, we might as well merge LIB2FUNCS_1 and LIB2FUNCS_2...

Ug.  No, I hadn't noticed that.  How gross.

Of course, there's no particular reason why they need to be
passed from the Makefile to mklibgcc either.  Targets don't
modify these variables.  Then change LIB2FUNCS_EXTRA.

So we could merge them and move them to mklibgcc.in.

> BTW, I'm wondering about these statements in optabs.c when looking for
> wider modes:
> 
> if (class == MODE_INT || class == MODE_FLOAT || class == MODE_COMPLEX_FLOAT)
> 
> Why not MODE_COMPLEX_INT?

I'm not sure why MODE_COMPLEX_FLOAT.  I thought for a moment that
there was a target that actually implemented some complex float
operations in the md file, but I can't find one now.


r~