search

andreww / fox

A Fortran XML library
https://andreww.github.io/fox/
Other
58 stars 50 forks source link

Intel Compilation Error #32

Open bhermanmit opened 10 years ago

bhermanmit commented 10 years ago

fox_m_fsys_format.F90 fails to compile with -check all flag

Error: /tmp/ifortWO02kC.i90: 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: ifort -c -check all -DFC_HAVE_FLUSH -DFC_HAVE_ABORT -DFC_ABORT_ARG -DFC_EOR_LF fox_m_fsys_format.F90

Version: Intel(R) Fortran Intel(R) 64 Compiler XE for applications running on Intel(R) 64, Version 13.0.1.117 Build 20121010

andreww commented 10 years ago

Thanks for the report.

An internal compiler error is by definition a compiler bug and it is probably worth reporting this to Intel. From memory I think ifort has fallen over on this file before (but this was 10 or 11 point something and I thought it had all been fixed) so it's probably worth reviewing the FoX-discuss archives. I think the most recent post is this one: https://groups.google.com/forum/?hl=en#!topic/fox-discuss/FTUc5Ro9nxI but also see this one: https://groups.google.com/forum/?hl=en#!topic/fox-discuss/aWegvAKe4vo and links from there. It may be worth raising this on that list too as others may have found a work around.

dev-zero commented 5 years ago

I'm seeing the same ICE with gfortran-7.3.1 (and FoX 4.0.3):

gfortran -c fox_m_fsys_format.F90
fox_m_fsys_format.F90:1289:0:

     if (.not.checkFmt(fmt)) then

internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://bugs.opensuse.org/> for instructions.
andreww commented 5 years ago

This is a compiler bug, not a problem with FoX, but I've not seen this with gfortran before. For what it's worth, the tests on travis are passing, but they use gfortran-4.9. It's probably worth configuring something newer too.

andreww commented 5 years ago

Also - see #57 for a possible work around