Intel® Fortran Compiler

Preprocessor directives not defined?

I am working on an Intel Visual Fortran solution provided to me by a third party. I am trying to gain a deeper understanding of how this solution is built. The .FOR files included within this solution, for several of them contain preprocessor directives such as #ifdef and #else. I understand vaguely what these preprocessors do (test for definition of a macro). I also understand that the tokens used must refer to a pre-existing macro generated using the directive #define. I cannot find this macro defined anywhere in my solution.

Confusion about file formats for Intel Fortran files

I am working on a project that was given to me by someone else. This project contains a ton of .FOR files written in seemingly free- format. Recently I have been studying fortran code formats in a little more detail and came accross this article ( which states:

".f90 specifies Fortran free-form source and .f, .ftn, or .for specify fixed-form souce"

Do DLL's created still require valid license?

Hi, sorry if this is a dumb question. I have a broken version of Python 2.7 with a horrible mix of VS libraries that I cant debug. I figure what the hey, I'll just rebuild everything from source, including SCIPY, etc, using Visual Studio FORTRAN, C++, MKL, etc. What could go wrong :-)

I have VS 2017 for C++, but and have now just downloaded an evaluation copy of FORTRAN compiler. My assumption is that any Fortran-related DLL's, etc, that get built will all survive the loss of the FORTRAN compiler license (after 30days) , but I wanted to check first.


ifort GLIBC dependencies

When compiling with ifort 17 on Linux, I notice very different GLIBC dependencies than when compiling with icc.  In particular, the following code

      program main
      write(*,*) 'Hello world!'
      end program main

when compiled on my RHEL 6 system (GLIBC2.11) produces an executable that when examined with objdump -x shows dependencies on 

Missing files during code coverage

I have a project that I compile with the intel toolchain. All the .f90 files are compiled to corresponding .o files in the bin directory. When I use the codecov utility I get an HTML with the list of covered files. However that list is missing a bunch of files which should be eligible for coverage. Some of the modules contained in those files are even used during the runs.

What could be a reason why these these files are missing from the coverage report?


IFORT.EXE not found when using USEENV flag

I am attempting to compile a .VFPROJ file inside of Visual Studio Ultimate 2013 Update 4. When I run VS2013 by typing DEVENV and then build the project, it builds without issue. However, when I run VS2013 by typing DEVENV /USEENV and then build the project, it errors out and says, "The Fortran compiler (ifort.exe) cannot be found." That doesn't make much sense. USEENV brings in the PATH, LIB, and INCLUDE environment variables to use in that session of VS2013.

Fortran 11 and probable 2003 compatibility issue


I'm using Intel Fortran 11 to create a Fortran-Call-C piece of code

I have problem when passing arguments by value from Fortran to C, and I was wondering if this may come from 2003 support issues in ifort 11

The fortran sends a single argument by value

ival=1 in CALL  p_f_i_AMETest(ival)  

but the C function get the adress instead of the value, and print

ival =1703488 in void AMETest(int ival) 


many thanks for any tips !!




This is my code


Problem compiling using a batch file (to create user subroutine for modelling software)


In a university project I need to compile fortran codes to create user subroutines which are then used by a modelling software, called Cycle-tempo. Cycle-tempo provides a compile.bat file which can be used for compiling fortran codes and create a UserSub.exe, but certain modifications have to be made in it to set up the actual user environment (see my version attached). Two other files, WinTempo.lib and WinTempo.res, are also provided to be used for the compiling.

订阅 Intel® Fortran Compiler