Intel® Visual Fortran Compiler for Windows*

Module variable not recognised in debugger

I want to look at a module variable, so following the documented technique for doing this, in the Watch window I type


The debugger replies that the variable is not recognised, even though the variable is defined as a PARAMETER in the module and calculations up to that point use its value.
The module is in a separate Fortran file. Is that the problem?

I am using VS 2012 Pro.

LNK1207 error with /debug switch on IVF v15.0 & 16.0

Hello all,

Compilation with IVF v15.0 & v16.0 (ia32) using the following command fails.

ifort /debug testprog.f90

The following error message is produced:

LINK : fatal error LNK1207: incompatible PDB format in 'c:\David\test\testprog.pdb'; delete and rebuild.

It would appear that with debug enabled the following intermediate files are produced: testprog.pdb, testprog.ilk. Furthermore a file vc140.pdb is created. These are not produced when when debug is disabled.

(1) What is the purpose of these files?

Compiling with DLL switches


I have a combination of C/C++ and Fortran libraries in a Nuclear Simulator exe.  The previous Visual Studio configuration had all sorts of "Ignore Specific Default Libraries" to prevent conflicting libraries between Single-Threaded, Multi-Threaded Release, Multi-Threaded DLL, etc, etc, etc.  This has been a CONSTANT battle for me, and the battle apparently ain't over.

Missing compiler check for procedure pointer reference to an elemental procedure

It appears current Fortran standard (c.f. 2008 C1218) doesn't allow the code shown below, but Intel Fortran compiler raises no errors or warnings:

module m

   implicit none

   abstract interface
      elemental subroutine Ifoo()
      end subroutine Ifoo
   end interface

   procedure(Ifoo), pointer :: foo_ptr

end module m


Mysterious crash

My Fortran code calls some subroutines that call others, and the chain ends up in some C++ code that draws lines on the screen.  Occasionally it crashes.  In debug mode I see the message Run-Time Check Failure #0 -- The value of ESP was not properly saved across a function call ....

Could this be causing the crash in release mode?  I use the same subroutines, called from elsewhere, with no problems.




ONLY : MYSELF to blame

This isn't a bug as such, but perhaps a feature request.

I have some code that I am maintaining and enhancing, and in this instance I am annotating it for offload programming on the Xeon Phi. Wishing to keep as much of the annotations out of the source code as possible, I place the !DIR$ ATTRIBUTES OFFLOAD : mic :: foobar into an interface module. This works quite well provided you do not do something like the following:

License problem - could not checkout FLEXlm license

We have a license for Intel® Parallel Studio XE Composer Edition for Fortran Windows valid until version 2011 update 11.

We performed a new installation on another computer. The installation was successful but when we try to compile a Fortran file we get the following error messages:

detect bad array shape

The following program has a bug.  Do you know if it is possible to have the compiler detect it?  I have tried the following options without success:

/Qtrapuv /Qinit:snan /Qinit:arrays /fpe:0   /check:all

program test_shape
implicit none

real,allocatable,dimension(:):: a, b 
real c

allocate( a(5), b(2) )

b = 0.0
a = b   !!!

c = a(3)
print*, c  ! output: -4.3160208E+08  ???
end program test_shape


Bad optimized assembly code generated for Fortran

When we compile the Fortran code below, we get this error in Visual Studio:

Exception thrown at 0x4B426F3 (kbcunitop.dll) in Petro-SIM.exe: 0xC000005: Access violation reading location 0xFFFFFFFF

I apologize for not being able to include a full project and all the files, but the error is very reproducible using only a small snippet of code, and centers around this snippet of code:

      integer, parameter :: UNINT     = -32767

   DO 20 I = 1 , LMIDEX
      MINDEX (I) = UNINT

The rest is not really relevant.

Intel® Visual Fortran Compiler for Windows* abonnieren