Message143330
Meador, I believe this was the first issue on the tracker that got me looking into bitfield allocation. I agree that big-endian on MSVC doesn't make too much sense but you can disregard that - using default endianess will still yield different sizes of bitfields when compiled with GCC and MSVC.
Basically bitfield allocation is compiler specific and patch in issue12528 implements a way to select which allocation strategy to be used at runtime instead of hardcoding the one with which Python is compiled. This should improve cross-compiler interop. I wanted to hyperlink that patch to all other bitfield bugs, that's why I followed up with link to the patch.
Feel free to close this, either as not an issue or as a duplicate of issue12528.
And yes, this bit about bitfield allocation should be documented and I was planning to look into it at some point after 12528 gets committed. |
|
Date |
User |
Action |
Args |
2011-09-01 14:45:28 | vladris | set | recipients:
+ vladris, terry.reedy, higstar, meador.inge |
2011-09-01 14:45:28 | vladris | set | messageid: <1314888328.47.0.0138570653786.issue6069@psf.upfronthosting.co.za> |
2011-09-01 14:45:27 | vladris | link | issue6069 messages |
2011-09-01 14:45:27 | vladris | create | |
|