Kenneth Hoste added the comment:
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
Ned Deily added the comment:
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
