➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ericvw
Recipients Michael.Felt, aixtools@gmail.com, ericvw, martin.panter
Date 2016-08-23.20:24:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1471983873.69.0.758159948906.issue27643@psf.upfronthosting.co.za>
In-reply-to
Content 
I am able to replicate what Michael has provided (i.e., xlc does not support signed short).  Sorry for the confusion: I overlooked that the compiler is emitting the error with may patch and assuming 'unsigned'.

So it seems like there are two things to address: (1) The bit fields should be explicitly marked as 'signed', since that appears to be the desired intent.  (2) What to do about the test case.

It seems like we all agree on (1).  For (2), is this something that should be stubbed out on AIX/xlc, resolved by xlc for supporting implementation-defined (short) bit-fields, or remove the short members in the struct since C99 (6.7.2.1) allows "a qualified or unqualified version of _Bool, signed int, unsigned int, or some other implementation-defined type"; thus removing the ambiguity for implementation-defined behavior?
History
Date User Action Args
2016-08-23 20:24:33ericvwsetrecipients: + ericvw, martin.panter, Michael.Felt, aixtools@gmail.com
2016-08-23 20:24:33ericvwsetmessageid: <1471983873.69.0.758159948906.issue27643@psf.upfronthosting.co.za>
2016-08-23 20:24:33ericvwlinkissue27643 messages
2016-08-23 20:24:33ericvwcreate