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.

Title: compiler error building the _sha3 module with Intel 2018 compilers
Type: compile error Stage: resolved
Components: Installation Versions: Python 3.6
Status: closed Resolution: third party
Dependencies: Superseder:
Assigned To: Nosy List: boegel, christian.heimes, edmondac, ned.deily, wscullin
Priority: normal Keywords:

Created on 2018-03-28 20:01 by wscullin, last changed 2022-04-11 14:58 by admin. This issue is now closed.

Messages (10)
msg314619 - (view) Author: William Scullin (wscullin) Date: 2018-03-28 20:01
When building Python 3.6.X and later with icc ( or, there's an error building the _sha3 module with any
optimization level other than -O0:

building '_sha3' extension
icc -pthread -fPIC -Wsign-compare -Wunreachable-code -DNDEBUG -g -O3
-Wall -Wstrict-prototypes -std=c99 -Wextra -Wno-unused-parameter
-Wno-missing-field-initializers -fp-model strict -I./Include -I.
-I/derp/Python-3.6.4 -c
sha3module.c -o
": internal error: ** The compiler has encountered an unexpected problem.
** Segmentation violation signal raised. **
Access violation or stack overflow. Please contact Intel Support for assistance.

compilation aborted for
(code 4)
[ jlselogin2: Python-3.6.4 ]$

if I drop to -O0, compilation works every time. I haven't found
disabling any particular set of optimizations to be useful in
obtaining a successful build.
[ jlselogin2: Python-3.6.4 ]$

dropping to -O0, compilation works every time. I haven't found
disabling any particular set of optimizations to be useful in
obtaining a successful build with icc.

 Intel has been notified and a bug filed as this is really a compiler bug. On the Python side, it does not appear possible to use Modules/Setup to drop the optimization level for just _sha3 and I'm hunting for a workaround.
msg315884 - (view) Author: Kenneth Hoste (boegel) Date: 2018-04-29 08:10
Willian: on which OS and (Intel?) processor generation are you seeing this?

We're not seeing this on CentOS 7.4.1708 with Python 3.6.4 and icc on Intel Haswell or Intel Skylake.
We have seen this with other software on Intel Skylake though...

Have you tried with icc 18.0.2 (which was released March 21st 2018)?
msg317591 - (view) Author: William Scullin (wscullin) Date: 2018-05-24 17:30
Hi Kenneth:

I can recreate this issue on Haswell, Skylake-X, and KNL running SLES 12, Clear Linux, and Centos 7.5. I've tried 18.1 and 18.2. It's still present across the board with Intel C/C++ On the Centos 7.5.1804 image, the build will seemingly complete, but since _sha3 didn't actually compile, the regression tests will fail with errors of the form:

$ /dev/shm/testinstall/icc/python/3.6.5/bin/python3 -m test
ERROR:root:code for hash sha3_224 was not found.
Traceback (most recent call last):
  File "/dev/shm/testinstall/icc/python/3.6.5/lib/python3.6/", line 121, in __get_openssl_constructor
    f = getattr(_hashlib, 'openssl_' + name)
AttributeError: module '_hashlib' has no attribute 'openssl_sha3_224'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/dev/shm/testinstall/icc/python/3.6.5/lib/python3.6/", line 243, in <module>
    globals()[__func_name] = __get_hash(__func_name)
  File "/dev/shm/testinstall/icc/python/3.6.5/lib/python3.6/", line 128, in __get_openssl_constructor
    return __get_builtin_constructor(name)
  File "/dev/shm/testinstall/icc/python/3.6.5/lib/python3.6/", line 113, in __get_builtin_constructor
    raise ValueError('unsupported hash type ' + name)
ValueError: unsupported hash type sha3_224
ERROR:root:code for hash sha3_256 was not found.
Traceback (most recent call last):
  File "/dev/shm/testinstall/icc/python/3.6.5/lib/python3.6/", line 121, in __get_openssl_constructor
    f = getattr(_hashlib, 'openssl_' + name)
AttributeError: module '_hashlib' has no attribute 'openssl_sha3_256'


Searching about, it looks like you may have seen something similar in EasyBuild:

but it doesn't look like the root cause was sussed out.

- William
msg319941 - (view) Author: Kenneth Hoste (boegel) Date: 2018-06-19 08:46
@William: someone in the EasyBuild community seems to have figured out the culprit, and came up with a patch to work around the problem, see .

Any feedback on that?
msg319943 - (view) Author: Christian Heimes (christian.heimes) * (Python committer) Date: 2018-06-19 08:58
I read the patch. The manual loop unrolling is ugly but mostly ok. But 
I'm -1 on the "-O0" option and won't accept the patch unless it works with standard optimization. sha3 is already slow. Without optimization, the algorithm grinds to a halt.

Did anybody contact Intel and reported the bug? It's clearly a bug in ICC. GCC, clang and MSVC compile the code just fine.
msg319945 - (view) Author: Andrew Edmondson (edmondac) Date: 2018-06-19 09:09
I made the patch. I'm not sure it's suitable to commit back as it is, as it unrolls a macro but there seems to be a choice of macro in the code (depending on certain conditions).

The problem is that icc can't handle a line that is so long.

I didn't log the bug with Intel - but I agree that it's a compiler bug and not a Python bug. I'll log it now...

msg319948 - (view) Author: Andrew Edmondson (edmondac) Date: 2018-06-19 09:24
msg320100 - (view) Author: Kenneth Hoste (boegel) Date: 2018-06-20 17:47
After a bit of back and forth, we have figured out the underlying cause for the problem with the Intel compiler: if the stack limit is not set to a specific value (see output of "ulimit -s"), the Intel compilers fail with a segfault or Interal Compiler Error (ICE).

But if the stack limit is set to 'unlimited' (e.g. via "ulimit -s unlimited"), then the compilation works fine...

See also and our (optional) workaround in
msg320104 - (view) Author: Ned Deily (ned.deily) * (Python committer) Date: 2018-06-20 18:52
Thanks for all the investigate work and thanks for the finding what appears to be an easy workaround, @boegel.  Clearly, though, this is not a Python problem and, with an external workaround (e.g. increasing the process stack size via ulimit), there is no need for a workaround in Python itself so I'm closing this issue.  Suggest making sure that the workaround is brought to the Intel compiler team's attention.
msg320106 - (view) Author: Kenneth Hoste (boegel) Date: 2018-06-20 19:01
Fully agreed that this is not something that should be fixed in the Python code base.

Moreover, the problem has been fixed in Intel compilers 2018 update 3 as far as I can tell (tested with both Python 3.6.4 and 3.7.0rc1).

I can't reproduce the problem anymore with that version of the Intel compilers, even after setting a hard stack limit (e.g. "ulimit -s 10240"), while it was easy to reproduce with the 2018 update 1 version.
Date User Action Args
2022-04-11 14:58:59adminsetgithub: 77355
2018-06-20 19:01:43boegelsetmessages: + msg320106
2018-06-20 18:52:42ned.deilysetstatus: open -> closed

title: error building the _sha3 module with Intel 2018 compilers -> compiler error building the _sha3 module with Intel 2018 compilers
nosy: + ned.deily

messages: + msg320104
resolution: third party
stage: resolved
2018-06-20 17:47:48boegelsetmessages: + msg320100
2018-06-19 09:24:37edmondacsetmessages: + msg319948
2018-06-19 09:09:37edmondacsetnosy: + edmondac
messages: + msg319945
2018-06-19 08:58:45christian.heimessetmessages: + msg319943
2018-06-19 08:46:57boegelsetmessages: + msg319941
2018-05-24 17:30:27wscullinsetmessages: + msg317591
2018-04-29 08:10:08boegelsetnosy: + boegel
messages: + msg315884
2018-03-28 20:13:38christian.heimessetnosy: + christian.heimes
2018-03-28 20:01:02wscullincreate