ICE with IFX 2025.2.0 for combination of move_alloc with /check:bounds

[Johannes_Rieke]

Dear Intel team, dear community,

it's been I while since my last post and I'm happy to see this very active discussion and "known" writers.

Currently, I move to a new machine and by that opportunity I updated to latest OneAPI compilers. In 2022 I tried IFX on my code and I got a lot of ICE and errors, so I skipped my tries. Now with IFX 2025.2.0 almost all of my code compiled with IFX (Windows 10/11 OS, VS2022). Only on one routine I got an ICE.

Compiling with Intel® Fortran Compiler 2025.2.0 [Intel(R) 64]...
ifx /nologo /MP /O2 /QaxAVX /Qipo /Qopt-matmul /fpp /Qopenmp /warn:all /real-size:64 /Qinit:snan /Qinit:arrays /fp:source /Qfp-speculation=safe /module:"x64\Release\\" /object:"x64\Release\\" /check:bounds /libs:static /threads /c /Qimf-precision:high /nostandard-realloc-lhs /Qlocation,link,"C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.44.35207\bin\HostX64\x64" /Qm64 "D:\02_Fortran\ifx_2025.2.0_bug\ifx_fatal_move_alloc\sub.f90"
xfortcom: Fatal: There has been an internal compiler error (C0000005).
ifx: error #10298: problem during post processing of parallel object compilation
compilation aborted for D:\02_Fortran\ifx_2025.2.0_bug\ifx_fatal_move_alloc\sub.f90 (code 1)

The minimum example is attached. The ICE might be related to ICE with ifx -assume norealloc_lhs -check all - Intel Community but also might not be the same.

If I remove /check:bounds the same code compiles and yes I use also /nostandard-realloc-lhs. However, if I comment out line 102 to 149 in my sub.f90, which belongs to a if construct with many branches and thus reduces it to only 4, the is disappearing.

Also, the way I copy the derived type array, which I "re-size", seems to have an effect on the ICE. So, it might be not only the combination of bounds checking and no automatic LHS reallocation?

I'm fine to deactivate bounds checking to get my code running for now. Hope this example helps the developers to improve IFX.

Any other recommendations are welcome.

Best regards, Johannes