➜

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 Daniel Colascione
Recipients Daniel Colascione, amaury.forgeotdarc, belopolsky, davin, meador.inge, pitrou, rhettinger
Date 2017-10-01.19:42:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAKOZuetTrjwW8iBuBu_c3ipH_7+oqL=HwAcgLHGLTkOjVA0E1w@mail.gmail.com>
In-reply-to <1506881676.53.0.213398074469.issue31654@psf.upfronthosting.co.za>
Content 
On Sun, Oct 1, 2017 at 11:14 AM, Antoine Pitrou <report@bugs.python.org>
wrote:

>
> Antoine Pitrou <pitrou@free.fr> added the comment:
>
> Note that if there is already a C API to perform atomic ops, you can
> simply use ctypes to invoke that API.  Unfortunately, the aforementioned
> GCC builtins seem to be only available as intrinsics (at least I couldn't
> find a shared library that exposes the __atomic_* functions on my system).
>

Right. I performed the same search. On Windows, at least
InterlockedCompareExchange is exported from kernel32.
History
Date User Action Args
2017-10-01 19:42:26Daniel Colascionesetrecipients: + Daniel Colascione, rhettinger, amaury.forgeotdarc, belopolsky, pitrou, meador.inge, davin
2017-10-01 19:42:26Daniel Colascionelinkissue31654 messages
2017-10-01 19:42:26Daniel Colascionecreate