Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.

catastrophic error: **Internal compiler error: segmentation violation signal raised**

Irena_J_
Principiante
2.126 Visualizações

I am using Intel Compiler 2015.u1, saxonHE/9.6.0.7, java/jdk1.8.0_45, python-2.7.10. The compilation fails with the error "catastrophic error: **Internal compiler error: segmentation violation signal raised**" -- see below. 

Please advise. Thank you, 
Irena 

 

mkdir -p ifort 
ifort -c -r8 -O0 -assume no2underscore -fPIC -module ifort -g -shared-intel -Iifort ids_schemas.f90 -o ids_schemas_ifort.o 
ifort -c -r8 -O0 -assume no2underscore -fPIC -module ifort -g -shared-intel -Iifort utilities_copy_struct.f90 -o utilities_copy_struct_ifort.o 
utilities_copy_struct.f90: 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 utilities_copy_struct.f90 (code 1) 
make[2]: *** [utilities_copy_struct_ifort.o] Error 1 
make[2]: Leaving directory `/u/ijohnson/IMAS/imas-installer/src/develop/3/ual/develop/fortraninterface' 
make[1]: *** [all] Error 2 
make[1]: Leaving directory `/u/ijohnson/IMAS/imas-installer/src/develop/3/ual/develop/fortraninterface' 
make: *** [fortraninterface] Error 2

0 Kudos
8 Respostas
KitturGanesh
Funcionário
2.126 Visualizações

Hi Irena,  I'll move this thread to the Intel Fortran Compiler forum so this issue can be looked into by the Fortran support group, appreciate much.

 

_Kittur

Kevin_D_Intel
Funcionário
2.126 Visualizações

If you can attach your utilities_copy_struct.f90 source file in a reply (note: that will be accessible to all forum users) I can investigate further. I may find the underlying issues is fixed in a newer Composer 2015 Update, or our latest PSXE 2016 release, or perhaps there is a palatable source code change to work around the issue with the compiler you currently are using.

If you cannot share the source file publicly in a reply, you can attach it in a private reply to me (use the Send Author A Message).

If you are able upgrade your compiler now, you could consider upgrading to the Composer XE 2015 Update 5 release to remain at the 2015 release, or if you prefer the bigger step up to the PSXE 2016 release. Those are available from the Intel® Software Development Products Registration Center (IRC).

Irena_J_
Principiante
2.126 Visualizações

Hi Kevin,

Thanks for pointing it out. I was able to remove the file. 

 

Irena

Irena_J_
Principiante
2.126 Visualizações

Thank you!

Laurent_T_
Principiante
2.126 Visualizações

Hello

I have the same problem when I want to install imas3.2.1

My compiler is Intel(R) Fortran Intel(R) 64 Compiler XE for applications running on Intel(R) 64, Version 15.0.3.187 Build 20150407

Did you solve the problem by installing the Composer XE 2015 Update 5 ?

 

Thank you

Kevin_D_Intel
Funcionário
2.126 Visualizações

The reproducer I have also fails with PSXE 2015 Update 5 and the latest PSXE 2016 (initial release and Update 1). I also have not found a work around at this time.

I escalated the issue to our Development team for further investigation and repair (see internal tracking id below). I will let you know whether they find a work around.

(Internal tracking id: DPD200381838)

Laurent_T_
Principiante
2.126 Visualizações

Too bad 

thank you

If it can help, there is no problem when compiling with Intel(R) Fortran Intel(R) 64 Compiler XE for applications running on Intel(R) 64, Version 12.0.2.137 Build 20110112

 

Best regards,

 

Laurent

 

Kevin_D_Intel
Funcionário
2.126 Visualizações

Our Developers found a work around. In file utilities_copy_struct.f90, place a ‘use ids_schemas’ at the top of the module and then comment out the 100+ 'use ids_schemas' statements in the module procedures within the file. I confirmed this avoids the internal error.

I will continue to update this thread as I learn more.

Responder