[issue14993] GCC error when using unicodeobject.h

STINNER Victor added the comment: > I don't think the change had any effect on memory consumption: because of > alignment, padding is inserted either way to fill the flags to four (32-bit) > or eight bytes. So with the bit field, there were 7 bytes of padding on > 64-bit systems, and now ther

[issue14993] GCC error when using unicodeobject.h

Martin v. Löwis added the comment: I don't think the change had any effect on memory consumption: because of alignment, padding is inserted either way to fill the flags to four (32-bit) or eight bytes. So with the bit field, there were 7 bytes of padding on 64-bit systems, and now there are o

[issue14993] GCC error when using unicodeobject.h

Changes by STINNER Victor : -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list U

[issue14993] GCC error when using unicodeobject.h

STINNER Victor added the comment: > OTOH, I fail to see why they need to be bitfields: a plain > unsigned char field should work as well (as would an int bitfield). Victor? I chose a bitfield to have a more compact structure. I didn't know that a bitfield using unsigned char is a GCC extension

[issue14993] GCC error when using unicodeobject.h

Roundup Robot added the comment: New changeset 09736ae1c314 by Victor Stinner in branch 'default': Issue #14993: Use standard "unsigned char" instead of a unsigned char bitfield http://hg.python.org/cpython/rev/09736ae1c314 -- nosy: +python-dev ___ P

[issue14993] GCC error when using unicodeobject.h

André Malo added the comment: I'm not talking about compiling python but my extension module. I *do* try supporting c89. Also relying on implementation extensions is bad style. I think, there's a huge difference between public header files (standards are good) and linked C code (do whatever y

[issue14993] GCC error when using unicodeobject.h

Martin v. Löwis added the comment: Compilation with gcc -std=c89 is not supported. Just drop this option. While Python strives to use C89, we will not distort to meet some abstract language compliance goal. OTOH, I fail to see why they need to be bitfields: a plain unsigned char field shoul

[issue14993] GCC error when using unicodeobject.h

Changes by Serhiy Storchaka : -- nosy: +storchaka ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.p

[issue14993] GCC error when using unicodeobject.h

Benjamin Peterson added the comment: It might not matter if it's an extension that everyone implements. -- nosy: +benjamin.peterson, loewis ___ Python tracker ___ __

[issue14993] GCC error when using unicodeobject.h

New submission from André Malo : GCC error when using unicodeobject.h This ist my first attempt to test an extension with python 3.3. I've been using the 3.3.0a4 tarball. I'm using very strict compiler settings when compiling my extension modules, especially -Wall -Werror (along with a lot mo