This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Two suggestions for gcc C compiler to extend C language (by WD Smith)
- From: Joseph Myers <joseph at codesourcery dot com>
- To: Warren D Smith <warren dot wds at gmail dot com>
- Cc: <gcc at gcc dot gnu dot org>
- Date: Tue, 26 Jul 2016 16:07:26 +0000
- Subject: Re: Two suggestions for gcc C compiler to extend C language (by WD Smith)
- Authentication-results: sourceware.org; auth=none
- References: <CAAJP7Y3cHYEOpdhZUXF1PZAJ=vkKoozRiPgwm2V_jH_T63XTKw@mail.gmail.com> <CAH6eHdRrmRWARhbcqWbqV07Y=SZp+Hsiv5-42y2k28CHqP4+UQ@mail.gmail.com> <CAAJP7Y0oRZmE4qS=shs4m7EWjWK2RfZdK2NSe1Kx1ZUT6W=QZw@mail.gmail.com> <alpine.DEB.2.20.1607261441290.2852@digraph.polyomino.org.uk> <CAAJP7Y13cQ6WkxL_dPpBbk7rkCvAVwqEZ6HJzYuZ4nNkpfpu9w@mail.gmail.com>
On Tue, 26 Jul 2016, Warren D Smith wrote:
> > Only sizes which are an integer number of bytes with no padding bits.
>
> wikipedia:
Wikipedia is not the standard (and, to be clear, C99 before TC3 had
various defects in the <stdint.h> specification as well, so you should not
refer to pre-TC3 versions for understanding <stdint.h> requirements).
C11 6.2.6.1#2 and #4 require that non-bit-fields have an integer number of
bytes and consist of n*CHAR_BIT bits, and 7.20.1.1#1 and #2 require the
absence of padding bits in intN_t and uintN_t.
--
Joseph S. Myers
joseph@codesourcery.com