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, christian.heimes, martin.panter
Date 2016-10-15.03:18:48
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
For the blake problem, I guess the structures may either get laid out incorrectly, or you might be lucky and they will get the desired packing by default. You might have to find if XLC has another way to enable struct packing. Or in the worst case, rewrite the code to pack data in a portable manner without using a struct.

The feature test macros like _POSIX_C_SOURCE are also discussed in various bug reports, including Issue 17120. How are you invoking /usr/include/standards.h? Perhaps there is a compiler mode or buggy header file that is getting in the way?

Regarding the data and function pointer confusion, this is a tricky case. I understand standard C (C99 etc) does not require function pointers to be compatible with void pointers. However, POSIX might require partial compatibility, at least for casting the void pointer from dlsym() to a function pointer: <>.

Does AIX actually have incompatible (e.g. different size) function and void pointers, or can we safely ignore those warnings? I think it may be annoying to change Python’s PyType_Slot and PyModuleDef_Slot structures to be compatible with function pointers, though perhaps it could be done with anonymous unions or something.
Date User Action Args
2016-10-15 03:18:49martin.pantersetrecipients: + martin.panter, christian.heimes, Michael.Felt
2016-10-15 03:18:49martin.pantersetmessageid: <>
2016-10-15 03:18:49martin.panterlinkissue28290 messages
2016-10-15 03:18:48martin.pantercreate