-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Albert Chin on 2/4/2007 7:47 AM:
> The IBM C compiler on AIX 4.3.3 (v6) doesn't like signed bit types:
> gmake[1]: Entering directory `/opt/build/m4-1.4.8/src'
> xlc-I../lib -I../lib -O2 -qro -qroconst -qmaxmem=-1 -qarch=com -c
Eric Blake <[EMAIL PROTECTED]> writes:
> bool foo BOOL_BITFIELD;
I'd suggest rather something like this:
typedef unsigned int bool_bitfield;
so that your structure members can look like this:
bool_bitfield foo : 1;
This doesn't rely on any autoconf or cpp magic, which is a win.
__
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Paul Eggert on 2/4/2007 10:59 AM:
> I don't know any way to do this. 'bool' must promote to int, so
> the only plausible candidates that can be used for bit-fields are
> int and signed int. But bool bitfields have a value 0 or 1, whereas
Paul Eggert wrote:
> a signed bitfield has the value 0 or -1 (on two's complement hosts).
Some compilers also give warnings if you use 'int foo : 1;'. We don't want
these warnings to occur in code of gnulib users.
> Admittedly this problem should be documented. Here's a proposed patch.
Thanks.
Eric Blake <[EMAIL PROTECTED]> writes:
> If it is getting the gnulib bool, then we should figure out how to
> make the gnulib bool pick a type that will work for this usage
> pattern.
I don't know any way to do this. 'bool' must promote to int, so
the only plausible candidates that can be used f
On Sun, Feb 04, 2007 at 07:52:08AM -0700, Eric Blake wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> According to Albert Chin on 2/4/2007 7:47 AM:
> > The IBM C compiler on AIX 4.3.3 (v6) doesn't like signed bit types:
> > gmake[1]: Entering directory `/opt/build/m4-1.4.8/src'
> >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Albert Chin on 2/4/2007 7:47 AM:
> The IBM C compiler on AIX 4.3.3 (v6) doesn't like signed bit types:
> gmake[1]: Entering directory `/opt/build/m4-1.4.8/src'
> xlc-I../lib -I../lib -O2 -qro -qroconst -qmaxmem=-1 -qarch=com -c
