topic Regression in 2025.2 in Intel® Fortran Compiler

Regression in 2025.2

NCarlson — Wed, 09 Jul 2025 19:35:32 GMT

The following example reproduces a regression in the oneAPI 2025.2 Fortran compiler that I encountered in our production code.

module m1 character(:), pointer, private :: string => null() contains function get() class(*), pointer :: get if (.not.associated(string)) allocate(string, source='foo') get => string end function subroutine set(arg) class(*), intent(in) :: arg select type (arg) type is (character(*)) print *, 'set received string "', arg, '"' if (arg /= 'foo') stop 'ERROR!' end select end subroutine end module use m1 select type (s => get()) type is (character(*)) print *, 'passing string "', s, '" to set' call set(s) end select end

It produces the incorrect result

$ ifx intel-20250709.f90 $ ./a.out passing string "foo" to set set received string "" ERROR!

The expected output (from 2025.1, for instance) is of course

passing string "foo" to set set received string "foo"

Re: Regression in 2025.2

NCarlson — Wed, 09 Jul 2025 19:41:18 GMT

A workaround in the main program is to assign S to a local allocatable character variable and pass it instead:

use m1 character(:), allocatable :: ss select type (s => get()) type is (character(*)) print *, 'passing string "', s, '" to set' ss = s call set(ss) end select end

Re: Regression in 2025.2

NCarlson — Thu, 02 Apr 2026 13:44:32 GMT

Ping to someone on the Intel team. This regression still exists in 2025.3.

Re: Regression in 2025.2

Igor_V_Intel — Tue, 14 Apr 2026 14:01:19 GMT

Unfortunately, it is still in the latest engineering build. I am escalating to fix it (CMPLRLLVM-74899).