Title: Implement atomic operations on non-x86 platforms
Type: enhancement Stage:
Components: Interpreter Core Versions: Python 3.5, Python 3.4
Status: open Resolution:
Dependencies: Superseder:
Assigned To: Nosy List: Arfrever, John.Malmberg,, gustavotemple, koobs, lbianc, neologix, python-dev, vstinner
Priority: normal Keywords: patch

Created on 2014-07-22 17:24 by, last changed 2015-03-17 21:59 by vstinner.

File name Uploaded Description Edit
atomic.patch, 2014-07-22 17:24 A patch implemeting atomic operating using the GCC builtins review
atomicv2.patch, 2014-07-29 16:46 A patch implemeting atomic operating using the GCC builtins and the stdatomic.h header review
atomicv3.patch gustavotemple, 2014-12-18 20:14 review
atomicv4.patch gustavotemple, 2015-01-13 18:51 review
atomicv5.patch gustavotemple, 2015-01-14 11:27 review
atomic_pointer.patch vstinner, 2015-01-14 15:06
Messages (25)
msg223676 - (view) Author: Vitor de Lima ( Date: 2014-07-22 17:24
The atomic operations listed in the pyatomic.h header file were implemented only for the x86 architecture, this patch uses the atomic bultins available in GCC >= 4.7 to implement such operations, allowing it to work properly in other platforms.
msg223740 - (view) Author: STINNER Victor (vstinner) * (Python committer) Date: 2014-07-23 13:56
+ #define __ATOMIC_RELAXED 0

You should use the "_Py_" prefix for these constants, to avoid conflicts in applications.

(You may also replace tabs with spaces, the PEP 7 says "Use 4-space indents and no tabs at all." but I also prefer to avoid tabs in other places.)

I tested your patch on Fedora 20 (Linux kernel 3.14.8, GCC 4.8.2, glibc 2.18) on x86_64 ("Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz") and the whole Python test suite pass.

GCC 4.9 (released a few month ago) provides the <stdatomic.h> header:

pyatomic.h contains this comment:

/* XXX: When compilers start offering a stdatomic.h with lock-free
   atomic_int and atomic_address types, include that here and rewrite
   the atomic operations in terms of it. */

But using <stdatomic.h> header can be done in a separated issue.
msg224235 - (view) Author: Vitor de Lima ( Date: 2014-07-29 16:46
Implemented a new version of the patch using either gcc builtins or the stdatomic.h header (this is detected by the configure script).
msg232813 - (view) Author: Gustavo Frederico Temple Pedrosa (gustavotemple) * Date: 2014-12-17 12:22
msg232836 - (view) Author: STINNER Victor (vstinner) * (Python committer) Date: 2014-12-17 23:32
Fedora 20 provides GCC 4.7 but no stdatomic.c: HAVE_BUILTIN_ATOMIC set (HAVE_STD_ATOMIC unset).

Fedora 21 provides GCC 4.9 with stdatomic.c: HAVE_BUILTIN_ATOMIC and HAVE_STD_ATOMIC are set.

I tested atomicv2.patch on Fedora 20 (x86_64) and Fedora 21 (x86_64): the whole test suite pass.
msg232839 - (view) Author: STINNER Victor (vstinner) * (Python committer) Date: 2014-12-17 23:53
> _Atomic int _value;

Why not using the atomic_int type from stdatomic.h here?


"__atomic_store_n(): The valid memory model variants are __ATOMIC_RELAXED, __ATOMIC_SEQ_CST, and __ATOMIC_RELEASE."

I understand that _Py_atomic_store_explicit() only accept some values for order. An assertion should be added here, maybe for any implementation. Something like:

#define _Py_atomic_store_explicit(ATOMIC_VAL, NEW_VAL, ORDER) \
    (assert((ORDER) == __ATOMIC_RELAXED                       \
            || (ORDER) == __ATOMIC_SEQ_CST                    \
            || (ORDER) == __ATOMIC_RELEASE),                  \
     __atomic_store_n(&(ATOMIC_VAL)->_value, NEW_VAL, ORDER))

Same remark for _Py_atomic_load_explicit():

"__atomic_load_n(): The valid memory model variants are __ATOMIC_RELAXED, __ATOMIC_SEQ_CST, __ATOMIC_ACQUIRE, and __ATOMIC_CONSUME."
msg232901 - (view) Author: Gustavo Frederico Temple Pedrosa (gustavotemple) * Date: 2014-12-18 19:47
@haypo, done: atomicv3.patch
msg233706 - (view) Author: Roundup Robot (python-dev) Date: 2015-01-09 01:14
New changeset fbe87fb071a6 by Victor Stinner in branch 'default':
Issue #22038: pyatomic.h now uses stdatomic.h or GCC built-in functions for
msg233707 - (view) Author: STINNER Victor (vstinner) * (Python committer) Date: 2015-01-09 01:16
atomicv3.patch is wrong for GCC builtin atomic operations: the parenthesis is not closed. I fixed this typo in the commit.

Vitor & Gustavo: Thanks for the patch, it's now applied to Python 3.5.

I tested it on Fedora 21 (x86_64). I disabled manually HAVE_STD_ATOMIC in pyconfig.h to test the two new options (stdatomic header & GCC builtins).
msg233745 - (view) Author: Gustavo Frederico Temple Pedrosa (gustavotemple) * Date: 2015-01-09 11:44
Thank you, Victor!
msg233942 - (view) Author: STINNER Victor (vstinner) * (Python committer) Date: 2015-01-13 15:19
I reopen the issue because Python cannot be compiled anymore on the Builder AMD64 FreeBSD 10.0 3.x:

checking for stdatomic.h... yes
checking for GCC >= 4.7 __atomic builtins... yes

--- Parser/tokenizer_pgen.o ---
In file included from Parser/tokenizer_pgen.c:2:
In file included from Parser/tokenizer.c:4:
In file included from Include/Python.h:53:
Include/pyatomic.h:37:5: error: _Atomic cannot be applied to incomplete type 'void' 
    _Atomic void *_value;
msg233944 - (view) Author: Gustavo Frederico Temple Pedrosa (gustavotemple) * Date: 2015-01-13 15:27
@haypo, OK, I will investigate the problem.
msg233955 - (view) Author: Gustavo Frederico Temple Pedrosa (gustavotemple) * Date: 2015-01-13 18:53
@haypo, done: atomicv4.patch
msg233958 - (view) Author: STINNER Victor (vstinner) * (Python committer) Date: 2015-01-13 19:27
Can you please generate a patch for the default branch of Python?
msg233959 - (view) Author: Arfrever Frehtes Taifersar Arahesis (Arfrever) * Date: 2015-01-13 19:28
Gustavo Temple: A patch against newest revision of default branch would be more useful.
msg233960 - (view) Author: Gustavo Frederico Temple Pedrosa (gustavotemple) * Date: 2015-01-13 19:30
OK, I will do.
msg233991 - (view) Author: Kubilay Kocak (koobs) Date: 2015-01-14 01:29
FreeBSD buildbots broken since fbe87fb071a67cb5e638b3496362b5aedc0fc9a7
msg233993 - (view) Author: Kubilay Kocak (koobs) Date: 2015-01-14 01:30
Oops, incomplete comment, apologies. Just noticed haypo has reported the issue here already
msg234023 - (view) Author: Gustavo Frederico Temple Pedrosa (gustavotemple) * Date: 2015-01-14 12:28
@haypo, @Arfrever, done: atomicv5.patch
msg234029 - (view) Author: Roundup Robot (python-dev) Date: 2015-01-14 15:03
New changeset dacc944641b1 by Victor Stinner in branch 'default':
Issue #22038, configure: HAVE_STD_ATOMIC now also check that "atomic_int" and
msg234030 - (view) Author: STINNER Victor (vstinner) * (Python committer) Date: 2015-01-14 15:06
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.
msg234031 - (view) Author: STINNER Victor (vstinner) * (Python committer) Date: 2015-01-14 15:14
At least, the latest change repaired FreeBSD 10 compilation.
msg234037 - (view) Author: Gustavo Frederico Temple Pedrosa (gustavotemple) * Date: 2015-01-14 16:43
@haypo, I checked and your idea and implementation are very good, thank you very much.

Yes, there is a Clang-specific implementation of the stdatomic.h header [1].

The Musl libc for example created a stdatomic.h header with full compatibility [2].


msg237945 - (view) Author: Roundup Robot (python-dev) Date: 2015-03-12 15:05
New changeset eb48295e1f8b by Victor Stinner in branch 'default':
Issue #23644, #22038: Move #include <stdatomic.c> inside the extern "C" { ... }
msg238348 - (view) Author: STINNER Victor (vstinner) * (Python committer) Date: 2015-03-17 21:59
<stdatomic.h> is not compatible with C++: I disabled completly pyatomic.h on C++. pyatomic.h is only needed by Python core, not to compile Python extensions, so it's not an issue.
Date User Action Args
2015-03-17 21:59:03vstinnersetmessages: + msg238348
2015-03-12 16:00:02lbiancsetnosy: + lbianc
2015-03-12 15:05:34python-devsetmessages: + msg237945
2015-01-14 16:43:46gustavotemplesetmessages: + msg234037
2015-01-14 15:14:48vstinnersetmessages: + msg234031
2015-01-14 15:06:22vstinnersetfiles: + atomic_pointer.patch

messages: + msg234030
2015-01-14 15:03:15python-devsetmessages: + msg234029
2015-01-14 12:28:53gustavotemplesetmessages: + msg234023
2015-01-14 11:27:00gustavotemplesetfiles: + atomicv5.patch
2015-01-14 01:34:26jyasskinsetnosy: - jyasskin
2015-01-14 01:30:44koobssetmessages: + msg233993
2015-01-14 01:29:45koobssetnosy: + koobs
messages: + msg233991
2015-01-13 19:30:53gustavotemplesetmessages: + msg233960
2015-01-13 19:28:00Arfreversetmessages: + msg233959
2015-01-13 19:27:42vstinnersetmessages: + msg233958
2015-01-13 18:53:21gustavotemplesetmessages: + msg233955
2015-01-13 18:51:09gustavotemplesetfiles: + atomicv4.patch
2015-01-13 18:37:25gustavotemplesetfiles: - atomicv4.patch
2015-01-13 18:33:52gustavotemplesetfiles: + atomicv4.patch
2015-01-13 15:27:48gustavotemplesetmessages: + msg233944
2015-01-13 15:19:51vstinnersetstatus: closed -> open
resolution: fixed ->
messages: + msg233942
2015-01-09 11:44:11gustavotemplesetmessages: + msg233745
2015-01-09 01:16:08vstinnersetstatus: open -> closed
resolution: fixed
messages: + msg233707
2015-01-09 01:14:32python-devsetnosy: + python-dev
messages: + msg233706
2014-12-19 00:04:55Arfreversetnosy: + Arfrever
2014-12-18 20:14:03gustavotemplesetfiles: + atomicv3.patch
2014-12-18 20:13:53gustavotemplesetfiles: - atomicv3.patch
2014-12-18 20:05:46gustavotemplesetfiles: + atomicv3.patch
2014-12-18 20:05:07gustavotemplesetfiles: - atomicv3.patch
2014-12-18 20:00:46gustavotemplesetfiles: + atomicv3.patch
2014-12-18 20:00:14gustavotemplesetfiles: - atomicv3.patch
2014-12-18 19:47:58gustavotemplesetmessages: + msg232901
2014-12-18 19:47:16gustavotemplesetfiles: + atomicv3.patch
2014-12-17 23:53:27vstinnersetmessages: + msg232839
2014-12-17 23:32:15vstinnersetmessages: + msg232836
2014-12-17 12:22:53gustavotemplesetnosy: + gustavotemple
messages: + msg232813
2014-09-02 04:09:32John.Malmbergsetnosy: + John.Malmberg
2014-07-29 + atomicv2.patch

messages: + msg224235
2014-07-23 13:56:07vstinnersetnosy: + vstinner
messages: + msg223740
2014-07-22 17:32:38pitrousetnosy: + jyasskin, neologix