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

ICE with ifx 2022.1.0: segmentation violation signal raised

Jorn
Novice
1,009 Views

With a production code (https://fabm.net) that is regularly tested with many compilers including ifort, I get the following error with the latest ifx:

/home/jbr/intel/compiler/2022.1.0/linux/bin-llvm/xfortcom[0x146f4ea]
/home/jbr/intel/compiler/2022.1.0/linux/bin-llvm/xfortcom[0x10f84dd]
/home/jbr/intel/compiler/2022.1.0/linux/bin-llvm/xfortcom[0x1156992]
/home/jbr/intel/compiler/2022.1.0/linux/bin-llvm/xfortcom[0x1156ac0]
/lib/x86_64-linux-gnu/libc.so.6(+0x43090)[0x7f5d75b20090]
/home/jbr/intel/compiler/2022.1.0/linux/bin-llvm/xfortcom[0x10c370b]
/home/jbr/intel/compiler/2022.1.0/linux/bin-llvm/xfortcom[0x10c37e2]
/home/jbr/intel/compiler/2022.1.0/linux/bin-llvm/xfortcom[0x10c37e2]
/home/jbr/intel/compiler/2022.1.0/linux/bin-llvm/xfortcom[0x10c37e2]
/home/jbr/intel/compiler/2022.1.0/linux/bin-llvm/xfortcom[0x10c37e2]
/home/jbr/intel/compiler/2022.1.0/linux/bin-llvm/xfortcom[0x10c354a]
/home/jbr/intel/compiler/2022.1.0/linux/bin-llvm/xfortcom[0x10a9fe8]
/home/jbr/intel/compiler/2022.1.0/linux/bin-llvm/xfortcom[0x10552ec]
/home/jbr/intel/compiler/2022.1.0/linux/bin-llvm/xfortcom[0x11fb612]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf3)[0x7f5d75b01083]
/home/jbr/intel/compiler/2022.1.0/linux/bin-llvm/xfortcom[0xe701e9]

/tmp/ifxBWcBH5.i90: error #5633: **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 /home/jbr/Temp/fabm/src/fabm.F90 (code 3)

To reproduce this:

git clone https://github.com/fabm-model/fabm.git
mkdir build
cd build
cmake ../fabm -DCMAKE_Fortran_COMPILER=ifx
make

Is there anything further I can do to identify the line or lines causing the issue?

Jorn

 

 

 

 

0 Kudos
7 Replies
Barbara_P_Intel
Moderator
975 Views

I will be happy to file a bug report. Can you attach just the file(s) required to produce the ICE (internal compiler error)? If fabfm.F90 uses modules or any include files, attach the source for those, too.

Thank you!

 

0 Kudos
Barbara_P_Intel
Moderator
943 Views

I downloaded the app and am working on isolating the ICE, Internal Compiler Error. I thought I would let you know, so we're both not working on it.


0 Kudos
Barbara_P_Intel
Moderator
912 Views

I filed a bug, CMPLRLLVM-39826.

You can use ifort as the workaround. No ICE there.



0 Kudos
Jorn
Novice
894 Views

Thanks! We ourselves and many of our users do use ifort regularly; it is included in our automated testing too (https://github.com/fabm-model/fabm/actions/runs/2904973615) It has always worked fine (versions dating back to at least since 2012). However, since ifx is presumably meant to replace ifort in some point in the the future (?), it would be great if we could get it to work with our code too. Hopefully the bug report will lead to that.

0 Kudos
Barbara_P_Intel
Moderator
848 Views

Do you know that you can mix and match .o files and .mod files between ifort and ifx? That will allow you to continue testing ifx.

There is also this Porting Guide.

 

0 Kudos
Barbara_P_Intel
Moderator
615 Views

Please check out the latest release of ifx. The compiler no longer ICEs.

It's part of the oneAPI HPC Toolkit 2023.2 that was released last week.


0 Kudos
Jorn
Novice
586 Views

Thanks very much! I can confirm that this code compiles fine with the latest ifx.

0 Kudos
Reply