[issue37415] Error build Python with Intel compiler: doesn't provide atomic_uintptr_t

STINNER Victor added the comment: According to Adam J. Stewart, my PR 16717 fix the Python build on ICC: https://github.com/python/cpython/pull/16717#issuecomment-544812182 So I merged it in 3.7, 3.8 and master branches. Adam saw other failures, but it's unrelated issues which should be

[issue37415] Error build Python with Intel compiler: doesn't provide atomic_uintptr_t

miss-islington added the comment: New changeset dbcea39ba713cc5b31fa1a243b16a0128c231c98 by Miss Skeleton (bot) in branch '3.8': bpo-37415: Fix stdatomic.h header check for ICC compiler (GH-16717) https://github.com/python/cpython/commit/dbcea39ba713cc5b31fa1a243b16a0128c231c98 --

[issue37415] Error build Python with Intel compiler: doesn't provide atomic_uintptr_t

miss-islington added the comment: New changeset b102e4f05278c1b06130885eba961bd0193733b4 by Miss Skeleton (bot) in branch '3.7': bpo-37415: Fix stdatomic.h header check for ICC compiler (GH-16717) https://github.com/python/cpython/commit/b102e4f05278c1b06130885eba961bd0193733b4 --

[issue37415] Error build Python with Intel compiler: doesn't provide atomic_uintptr_t

Change by miss-islington : -- pull_requests: +16432 pull_request: https://github.com/python/cpython/pull/16893 ___ Python tracker ___

[issue37415] Error build Python with Intel compiler: doesn't provide atomic_uintptr_t

STINNER Victor added the comment: New changeset 028f7349a0f6eaea0fec31becb587fcdf6e3cb28 by Victor Stinner in branch 'master': bpo-37415: Fix stdatomic.h header check for ICC compiler (GH-16717) https://github.com/python/cpython/commit/028f7349a0f6eaea0fec31becb587fcdf6e3cb28 --

[issue37415] Error build Python with Intel compiler: doesn't provide atomic_uintptr_t

Change by miss-islington : -- pull_requests: +16431 pull_request: https://github.com/python/cpython/pull/16892 ___ Python tracker ___

[issue37415] Error build Python with Intel compiler: doesn't provide atomic_uintptr_t

STINNER Victor added the comment: I marked bpo-35473 as duplicate of this issue. -- ___ Python tracker ___ ___ Python-bugs-list

[issue37415] Error build Python with Intel compiler: doesn't provide atomic_uintptr_t

STINNER Victor added the comment: Can someone please test PR 16717 with ICC? -- ___ Python tracker ___ ___ Python-bugs-list

[issue37415] Error build Python with Intel compiler: doesn't provide atomic_uintptr_t

STINNER Victor added the comment: I wrote PR 16717 which uses a similar approach than python.patch. -- components: +Build versions: +Python 3.7, Python 3.8, Python 3.9 ___ Python tracker

[issue37415] Error build Python with Intel compiler: doesn't provide atomic_uintptr_t

Change by STINNER Victor : -- pull_requests: +16294 stage: -> patch review pull_request: https://github.com/python/cpython/pull/16717 ___ Python tracker ___

[issue37415] Error build Python with Intel compiler: doesn't provide atomic_uintptr_t

Rainer Keller added the comment: We have been experiencing the same problem with compiling Python-3.7.4 on a system with CentOS 7.6 (aka glib-2.17): Intel Compiler 2019.6 implements stdatomic.h. but lacks the definition of atomic_uintptr_t. >From a configure-point of view just failing to

[issue37415] Error build Python with Intel compiler: doesn't provide atomic_uintptr_t

STINNER Victor added the comment: > Changing Include/pyatomic.h to use _Atomic as suggested by Victor in > msg346785 leads to the error that _Atomic was undefined. No idea how to define a "_Py_atomic_address" type with icc 2019.4 in this case. If someone has a working patch, I can review it

[issue37415] Error build Python with Intel compiler: doesn't provide atomic_uintptr_t

Christian Berger added the comment: I have the same problem on RH6 with icc 2019.4 and Python 3.6.9. Do you want a new bug for that? Changing Include/pyatomic.h to use _Atomic as suggested by Victor in msg346785 leads to the error that _Atomic was undefined. -- nosy: +cberger

[issue37415] Error build Python with Intel compiler: doesn't provide atomic_uintptr_t

Stefan Krah added the comment: Is it available with -std=c11? It is a bit strange that we use -std=c99. I thought that header is C11: https://en.cppreference.com/w/c/atomic -- nosy: +skrah ___ Python tracker

[issue37415] Error build Python with Intel compiler: doesn't provide atomic_uintptr_t

Change by Glenn Johnson : -- nosy: +Glenn Johnson ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue37415] Error build Python with Intel compiler: doesn't provide atomic_uintptr_t

STINNER Victor added the comment: I suggested you to test the following change on the master branch of Python: diff --git a/Include/internal/pycore_atomic.h b/Include/internal/pycore_atomic.h index 336bc3fec2..c624a0cf1c 100644 --- a/Include/internal/pycore_atomic.h +++

[issue37415] Error build Python with Intel compiler: doesn't provide atomic_uintptr_t

Borja added the comment: Two things. I searched a bit more and found "atomic_uint" inside , but it's not exactly the same as what you wrote. What you have put me to try, where do I put it? I attached in case it helps. -- Added file: https://bugs.python.org/file48443/stdatomic.h

[issue37415] Error build Python with Intel compiler: doesn't provide atomic_uintptr_t

STINNER Victor added the comment: > I searched at atomic_uintptr_t and found nothing. That's not good. I expectd std to stand for standard. I expected that atomic_uintptr_t would always be available on . GCC defines the type as: typedef _Atomic __UINTPTR_TYPE__ atomic_uintptr_t; Maybe