[issue25589] test_ascii_formatd fails on Mac when built with Intel compiler

Serhiy Storchaka added the comment: Python 2.7 is no longer supported. -- nosy: +serhiy.storchaka resolution: -> out of date stage: -> resolved status: open -> closed ___ Python tracker

[issue25589] test_ascii_formatd fails on Mac when built with Intel compiler

Chris Hogan added the comment: The Intel compiler team is looking into this issue. I'll keep everyone updated here. -- ___ Python tracker ___

[issue25589] test_ascii_formatd fails on Mac when built with Intel compiler

Zachary Ware added the comment: This one is officially weird. I can reliably reproduce the segfault in test_ascii_formatd on OSX with ICC 15 or 16, using the included libffi in Modules/_ctypes/libffi_osx. There are also segfaults in test_ctypes, test_multiprocessing, and test_threading (all

[issue25589] test_ascii_formatd fails on Mac when built with Intel compiler

Changes by Chris Hogan : -- resolution: not a bug -> status: closed -> open ___ Python tracker ___

[issue25589] test_ascii_formatd fails on Mac when built with Intel compiler

R. David Murray added the comment: We've figured out that the difference is the optimization level. Without --with-pydebug, I can reproduce the failure. -- ___ Python tracker

[issue25589] test_ascii_formatd fails on Mac when built with Intel compiler

R. David Murray added the comment: Someone can correct me if I'm wrong, but my expectation would be that since we use ICC for the main compile on the ICC buildbots, we also compile the bundled ctypes using it. It is hard to see how any of the other modules would affect this. --

[issue25589] test_ascii_formatd fails on Mac when built with Intel compiler

Chris Hogan added the comment: I guess since no one can reproduce the error, it must be a problem with how I'm building it. We build our own dependencies (zlib, bzip, sqlite3, openssl, etc.) with the Intel compiler, so it could be any number of things causing the issue. Closing as not a bug.

[issue25589] test_ascii_formatd fails on Mac when built with Intel compiler

STINNER Victor added the comment: See also issue #24999 about ICC compiler. -- nosy: +haypo ___ Python tracker ___

[issue25589] test_ascii_formatd fails on Mac when built with Intel compiler

New submission from Chris Hogan: I successfully built Python on OS X 10.10 with the Intel compiler v15. However, running the regression tests gives me a "segmentation fault: 11" on test_ascii_formated. I think this has to do with libffi, because when I build with the --use-system-ffi flag

[issue25589] test_ascii_formatd fails on Mac when built with Intel compiler

Zachary Ware added the comment: Also, I haven't had an issue with this on my own machine. -- ___ Python tracker ___

[issue25589] test_ascii_formatd fails on Mac when built with Intel compiler

Zachary Ware added the comment: This doesn't seem to be a problem on the ICC buildbot; David, did you do anything special for libffi/ctypes? -- nosy: +r.david.murray, zach.ware ___ Python tracker

[issue25589] test_ascii_formatd fails on Mac when built with Intel compiler

Ned Deily added the comment: Chris, how exactly are you running this test that fails and where does the test come from? I may be overlooking something but I do not see any spelling of a test_ascii_formatted in the Python 3.5 source including its embedded ctypes. The ctypes shipped with

[issue25589] test_ascii_formatd fails on Mac when built with Intel compiler

Chris Hogan added the comment: Ned, the test is in Lib/test/test_ascii_formatd.py. Sorry, I spelled it wrong originally. Also, I guess it's only in 2.7. My mistake. -- versions: -Python 3.5 ___ Python tracker