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

Possible compiler bug?

OP1
New Contributor III
403 Views
The following behavior illustrates a really weird behavior of IVF 10.1. As is, the subroutine compiles. If I comment out lines 2 and 15 of the subroutine, and uncomment lines 1 and 14, ifort spawns fortcom and then hangs. The only difference is the length of the variable name.

It took me quite a while to reduce the issue to this size.

Thanks for any help on this.

Olivier



Module:

[fortran]MODULE TYPES
IMPLICIT NONE
TYPE T_T1
    INTEGER :: N1
    INTEGER :: N2
    INTEGER :: N3
    INTEGER :: N4
    INTEGER :: N5
END TYPE T_T1
END MODULE TYPES[/fortran]


Subroutine:

[fortran]!SUBROUTINE SUB(T1,A,B,C,D,E,F,G,H,I,THIS_ONE_WILL_NOT_WORK)
SUBROUTINE SUB(T1,A,B,C,D,E,F,G,H,I,THIS_ONE_WILL_WORK)
    USE TYPES
    IMPLICIT NONE
    INTEGER,PARAMETER :: DP = SELECTED_REAL_KIND(14)
    TYPE(T_T1),INTENT(IN) :: T1
    REAL(KIND=DP),DIMENSION(T1%N1),INTENT(IN)  :: A
    REAL(KIND=DP),DIMENSION(T1%N2,T1%N5),INTENT(OUT) :: B,C
    REAL(KIND=DP),DIMENSION(T1%N4,T1%N2),INTENT(OUT) :: D
    REAL(KIND=DP),DIMENSION(T1%N2),INTENT(OUT) :: E
    REAL(KIND=DP),DIMENSION(T1%N3),INTENT(OUT) :: F
    REAL(KIND=DP),DIMENSION(T1%N1),INTENT(OUT) :: G
    REAL(KIND=DP),DIMENSION(T1%N2,T1%N5),INTENT(OUT) :: H,I
    !REAL(KIND=DP),DIMENSION(T1%N4,T1%N2),INTENT(OUT) :: THIS_ONE_WILL_NOT_WORK
    REAL(KIND=DP),DIMENSION(T1%N4,T1%N2),INTENT(OUT) :: THIS_ONE_WILL_WORK
END SUBROUTINE SUB


[/fortran]
0 Kudos
3 Replies
Steven_L_Intel1
Employee
403 Views
Works fine in the current version (12.1) of the compiler. I don't have 10.1 installed so can't readily check it. I suggest you move to a current, supported version.
0 Kudos
mecej4
Honored Contributor III
403 Views
Are you able to try this with a newer release of the compiler? There are no problems compiling it with 11.1.073 or 12.1.
0 Kudos
OP1
New Contributor III
403 Views
Yes - problem solved with IVF 11.1.070 That was an odd bug though.

Thanks,
Olivier
0 Kudos
Reply