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 martin.panter
Recipients Michael.Felt, aixtools@gmail.com, ericvw, martin.panter
Date 2016-08-24.01:01:50
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1472000511.79.0.355107600735.issue27643@psf.upfronthosting.co.za>
In-reply-to
Content
Michael: When posting to the bug tracker, please trim irrelevant parts of old messages. It makes it hard to see if you actually added anything new.

> [Me] If your compiler does not support “signed short” bitfields, maybe we just have to accept that ctypes supports it even though the compiler doesn’t, and skip the test.

Proper support for “signed short” according to standard C I guess would mean if you define

struct BITS {
    signed short M: 1;
} b;
b.M = -1;

then reading back b.M gives -1. However I realized test_bitfields tests overflowing values rather than negative values. In any case, I think we have established that neither of these cases work with XLC.

I haven’t changed the signed int A–I fields yet. That was part of my patch. I was waiting for confirmation about the __xlC__ check, before committing the whole thing.

Eric: I proposed to conditionally skip the test; see disable-signed-short.patch. Since many other compilers apparently pass the test and support signed short, we should probably keep the test.
History
Date User Action Args
2016-08-24 01:01:51martin.pantersetrecipients: + martin.panter, ericvw, Michael.Felt, aixtools@gmail.com
2016-08-24 01:01:51martin.pantersetmessageid: <1472000511.79.0.355107600735.issue27643@psf.upfronthosting.co.za>
2016-08-24 01:01:51martin.panterlinkissue27643 messages
2016-08-24 01:01:50martin.pantercreate