Bug#491654: gcc-4.3: _Bool isn't wide enough.

2008-07-21 Thread Nick Lewycky
close 491654 thanks dude Hi Bastian, The paragraph talks about how signed types need to map to unsigned types, and then goes on to talk about _Bool and unsigned types. I completely misread it as meaning that _Bool had to map to an unsigned type. You're entirely correct here, sorry for the tro

Processed (with 5 errors): Re: Bug#491654: gcc-4.3: _Bool isn't wide enough.

2008-07-21 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > close 491654 Bug#491654: gcc-4.3: _Bool isn't wide enough. 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Nick Lewycky <[EMAIL PROTECTED]> > tha

Bug#491654: gcc-4.3: _Bool isn't wide enough.

2008-07-21 Thread Bastian Blank
On Sun, Jul 20, 2008 at 11:32:28PM -0700, Nick Lewycky wrote: > In C99, _Bool is required to map to one of the unsigned types (6.2.5/6). Please quote the standard. I read something different there. > However, GCC rejects the following (admittedly unethical) snippet: > struct S7 { > _Bool D

Bug#491654: gcc-4.3: _Bool isn't wide enough.

2008-07-20 Thread Nick Lewycky
Package: gcc-4.3 Version: 4.3.1-6 Severity: normal In C99, _Bool is required to map to one of the unsigned types (6.2.5/6). On i586, this is 'unsigned char', by ABI. That means that you get eight bits to the _Bool. However, GCC rejects the following (admittedly unethical) snippet: struct S7 {