/Qinit:arrays and parameter arrays

[Nicholas_B_]

There are a couple of iminor ssues when compiling the following with /Qinit:snan /Qinit:arrays:

program overlap

  use iso_fortran_env, only : dp => real64
  implicit none

  real(dp), dimension(4,4,3), parameter :: half_turn = reshape ( &
    [ &
     ! half turn about y axis
    -1,  0,  0,  0, &
     0,  1,  0,  0, &
     0,  0, -1,  0, &
     0,  0,  0,  1, &
     ! half turn about z axis
    -1,  0,  0,  0, &
     0, -1,  0,  0, &
     0,  0,  1,  0, &
     0,  0,  0,  1,  &
     ! half turn about x axis
     1,  0,  0,  0, &
     0, -1,  0,  0, &
     0,  0, -1,  0, &
     0,  0,  0,  1  &
     ], shape=[ 4, 4, 3 ], order=[ 2, 1, 3 ] )

  integer :: i, k

  do k = 1, 3
    write(*,'(4(4I3/)/)') ( int(half_turn(i,1:4,k)), i=1,4 )
  end do

end program overlap

Compiling with Intel(R) Visual Fortran Compiler XE 15.0.2.179 [Intel(R) 64]...
ifort /nologo /debug:full /Od /standard-semantics /stand:f08 /warn:all /debug-parameters:all /Qinit:snan /Qinit:arrays /module:"x64\Debug\\" /object:"x64\Debug\\" /Fd"x64\Debug\vc120.pdb" /traceback /check:bounds /check:stack /libs:dll /threads /dbglibs /c /Qvc12 /Qlocation,link,"C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\\bin\amd64" "C:\Users\Nicholas\Documents\mesh_store\mesh_store_2015\overlap\overlap.f90"
C:\Users\Nicholas\Documents\mesh_store\mesh_store_2015\overlap\overlap.f90(9): warning #5436: Overlapping storage initializations encountered with HALF_TURN
    -1,  0,  0,  0, &
----^

I think this warning is completely spurious.

Also when debugging Visual 2013 the half_trun array and dp parameter are listed multiple times in the Locals window.

Nick

[mecej4]

I do not get the warning when I use the same compiler version but without /stand:f08, so this is a glitch that should be fixed.

I reported the debugger problem earlier in this forum, and the post was moved to the debugger forum, please see https://software.intel.com/en-us/forums/topic/540783 . The problem is in the debug information placed in the .OBJ file by the compiler (this information is present in duplicate), so I do not know which Intel group is responsible for fixing the problem.

[Steven_L_Intel1]

I can reproduce the warning with 15.0.2 but not with the 16.0 beta, so it seems that this problem has been fixed. I could not find a report of it in our system, but sometimes things get fixed as side-effects of other fixes.

The double debug problem has been escalated to the proper team.

[Steven_L_Intel1]

The double debug problem will be fixed in the 16.0 release.