➜

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 vstinner
Recipients Arfrever, John.Malmberg, Vitor.de.Lima, gustavotemple, koobs, neologix, python-dev, vstinner
Date 2015-01-14.15:06:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1421247982.26.0.357122886149.issue22038@psf.upfronthosting.co.za>
In-reply-to
Content 
I commited atomicv5.patch because it's simple, but I'm not sure that we are using stdatomic.h "correctly". The current code looks to be written for GCC, Clang fails to compile it (FreeBSD 10 now uses Clang instead of GCC).

Maybe the "_Atomic void*" type is wrong, and we should use the "atomic_uintptr_t" type instead and cast to the expected type? Attached atomic_pointer.patch implements this idea. It works on FreeBSD 10 with Clang and on Fedora 21 with GCC 4.9, both have stdatomic.h.
History
Date User Action Args
2015-01-14 15:06:22vstinnersetrecipients: + vstinner, Arfrever, neologix, python-dev, koobs, John.Malmberg, Vitor.de.Lima, gustavotemple
2015-01-14 15:06:22vstinnersetmessageid: <1421247982.26.0.357122886149.issue22038@psf.upfronthosting.co.za>
2015-01-14 15:06:22vstinnerlinkissue22038 messages
2015-01-14 15:06:22vstinnercreate