[Python-Dev] Bugs in thread_nt.h
"Martin v. Löwis"
martin at v.loewis.de
Thu Mar 10 05:42:24 CET 2011
More information about the Python-Dev mailing list
Thu Mar 10 05:42:24 CET 2011
- Previous message: [Python-Dev] Bugs in thread_nt.h
- Next message: [Python-Dev] Bugs in thread_nt.h
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Am 09.03.11 20:25, schrieb Sturla Molden: > These methods require the memory to be aligned > on 32-byte boundaries. You misread the documentation - it's a 32-*bit* boundary that the LONG variable must be on. The malloc() call that is currently used trivially meets this requirement. As for the volatile marker - I believe the code is also correct without it, since the owned field is only accessed through initialization and Interlocked operations. Regards, Martin
- Previous message: [Python-Dev] Bugs in thread_nt.h
- Next message: [Python-Dev] Bugs in thread_nt.h
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list