ifort 16 ICE: -debug full -O2

[AShte]

newblue4> ifort -coarray ca_check1.f90
newblue4> ifort -coarray -debug full -O2 ca_check1.f90
010101_0

catastrophic error: **Internal compiler error: internal abort** 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 ca_check1.f90 (code 1)
newblue4>

newblue4> cat ca_check1.f90
program z
use iso_fortran_env
implicit none
integer, parameter :: dp = real64
real( kind=dp)     :: time1, time2

integer :: x(10)

, img, nimgs, i
  img = this_image()
nimgs = num_images()
    x = img

sync all

if ( img .eq. 1 ) then
  do i = 2, nimgs
!    time1 = mytime()
!    x = x(:)
!    time2 = mytime()
!    write (*,"(a,g)") "Remote read took, s : ", time2-time1
    time1 = mytime()
    x(:) = x
    time2 = mytime()
    write( *,*) "Remote write took, s : ", time2-time1
    write( *, "(a,i0,a,10(i0))" ) "img: ", i, "x:", x(:)
  end do
end if

sync all

write (*,"(a,i0,a,i0,a)") "Image: ", img, " out of ", nimgs, &
 " completed ok"

contains

function mytime() result (tseconds)
        real( dp ) :: tseconds
  integer( INT64 ) :: tsec, trate
  CALL SYSTEM_CLOCK( count=tsec, count_rate=trate )
  tseconds = real(tsec,kind=dp) / real(trate,kind=dp)
end function mytime

end program z
newblue4>

Thanks

Anton

[Steven_L_Intel1]

Please show the output of:

ifort -V

[Steven_L_Intel1]

Never mind - I can reproduce this now. Taking off -debug is a workaround.

[AShte]

Steve, thank you for looking into this.

In case you still want it:

 ifort -V
Intel(R) Fortran Intel(R) 64 Compiler for applications running on Intel(R) 64, Version 16.0.0.109 Build 20150815

[Steven_L_Intel1]

Escalated as issue DPD200382002. I find that if I try our latest internal sources, for the next major release later this year, I don't get the error. I have asked the developers to take a closer look to see if they can identify the problem.

I would recommend updating to 16.0.2, available now.

[Steven_L_Intel1]

The fix was identified, it will be in the next major release but not a 16.0 update.