Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ifort segfaults when compiling 1.5.1's libxsmm.f #104

Closed
alheinecke opened this issue Oct 30, 2016 · 2 comments
Closed

ifort segfaults when compiling 1.5.1's libxsmm.f #104

alheinecke opened this issue Oct 30, 2016 · 2 comments
Assignees
Labels

Comments

@alheinecke
Copy link
Collaborator

With:
[localhost libxsmm]$ ifort -V
Intel(R) Fortran Intel(R) 64 Compiler XE for applications running on Intel(R) 64, Version 15.0.3.187 Build 20150407
Copyright (C) 1985-2015 Intel Corporation. All rights reserved.

Then:

[localhost libxsmm]$ make realclean && make

LIBXSMM master-1.5.1-78

Intel Compiler: icc 15.0.3, icpc 15.0.3, and ifort 15.0.3
C / C++: -msse3

Fortran: -msse3

[...]
results into:
ifort -threads -qno-offload -fpic -diag-disable 10006,10010,10411,13003 -free -O2 -fp-model fast=2 -align array64byte -DLIBXSMM_BUILD -DNDEBUG -D__STATIC=1 -D_REENTRANT -Iinclude -Ibuild -I/home/aheineck/Projects/LIBXSMM_workspace/libxsmm_internal_merge/src -msse3 -c include/libxsmm.f -o build/intel64/libxsmm-mod.o -module include
include/libxsmm.f: catastrophic error: Internal compiler error: segmentation violation signal raised Please report this error along with the circumstances in which it occurred in a Software Problem Report. Note: File and line given may not be explicit cause of this error.
compilation aborted for include/libxsmm.f (code 1)

When the Fortran interface is not needed:
[localhost libxsmm]$ make realclean && make FC=
can be used to work-around the problem

@hfp hfp self-assigned this Oct 31, 2016
hfp added a commit that referenced this issue Oct 31, 2016
…t to workaround the problem. This fix is validated against latest PGI Fortran, which was the deviating from what's accepted when compared to any other Fortran compiler (however, it's not the PGI version previously used to check with since the CSCS' Dora environment is not available at the moment).
@hfp
Copy link
Collaborator

hfp commented Oct 31, 2016

Checked with IFORT 15.0.3 and it appears to be worked around. Also checked with PGI (make CXX=pgc++ CC=pgcc FC=pgfortran COMPATIBLE=1 interface), and it appears to work as well. Let's wait for Travis...

hfp added a commit that referenced this issue Oct 31, 2016
…t to workaround the problem. This fix is validated against latest PGI Fortran, which was the deviating from what's accepted when compared to any other Fortran compiler (however, it's not the PGI version previously used to check with since the CSCS' Dora environment is not available at the moment).
@hfp hfp added the bug label Oct 31, 2016
@hfp
Copy link
Collaborator

hfp commented Oct 31, 2016

I've also setup another test pipeline with Buildkite, which builds/runs the Travis testset using the aforementioned compiler.

@hfp hfp closed this as completed Oct 31, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants