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 vladris
Recipients amaury.forgeotdarc, meador.inge, santoso.wijaya, terry.reedy, vladris
Date 2011-09-01.18:30:33
SpamBayes Score 9.651628e-10
Marked as misclassified No
Message-id <1314901834.84.0.11701101769.issue12528@psf.upfronthosting.co.za>
In-reply-to
Content
Well currently we pack bitfields with an algorithm that uses #ifdefs for GCC and MSVC builds. This feature tries to remove the hardcoded behavior and implement it as a runtime option. This should improve interop with other compilers. Currently I provided these for MSVC-style and GCC-style bitfield allocations. These, of course, can be extended with other strategies.

I am not sure that the fact that GCC has different types of bitfield allocations in different versions is a point against this feature. Consider that in our current code we don't use compiler bitfield allocation, we create the structure layout using our own algorithm, interop might be broken even if Python gets built with same version of GCC as the binary we want to interop with as long as algorithm is out of date. This patch should provide some flexibility in this matter.

Wouldn't a GCC44 constant provided at API level be better than saying "you can't interop with anything build with GCC 4.4 and up"? Or vice-versa, anything built with GCC < 4.4.
History
Date User Action Args
2011-09-01 18:30:34vladrissetrecipients: + vladris, terry.reedy, amaury.forgeotdarc, meador.inge, santoso.wijaya
2011-09-01 18:30:34vladrissetmessageid: <1314901834.84.0.11701101769.issue12528@psf.upfronthosting.co.za>
2011-09-01 18:30:34vladrislinkissue12528 messages
2011-09-01 18:30:33vladriscreate