Intel® Fortran Compiler

Equality comparison for unlimited polymorphic variables

Fortran Gurus: say I have two unlimited polymorphic variables (CLASS(*)), and I want to check if they are equal. Does anyone know if there is a better way than having to write nested SELECT TYPE statements for all possible variable types? Basic example below. Assuming I only cared about built-in variables types (integers, etc.) I'd have to write cases for INT8, INT16, INT32, INT64, REAL32, REAL64, REAL128, and CHARACTERS kinds. This seems unsatisfactory to me, but I can't think of any other way to do it.


Linking Error


I am trying to compile UMAT Subroutine for ABAQUS.  I use Microsoft Visual Studio 10 and Evaluation version of Intel Parallel Studio XE 2016.  I tried to Run ABAQUS with my subroutine file:










cannot open file 'kernel32.lib

LINK : fatal error LNK1104: cannot open file 'kernel32.lib'

I continue to have this problem with the VS2015 integration since updating VS2015 to the current version.  I have spent about 20 hours on it, removing VS2015 entirely and re-installing, and removing all Parallel Studio 2016 components and re-installing.

VS2012 and VS2013 integrations continue to work fine, even when setting -Qlocation,link to point to the VS2015 bin\amd64 folder.


We are using Windows 7, Visual Studio 10, and Intel Parallel Studio XE 2015 Composer Edition for Fortran Windows.  I cannot debug my Fortran project, it never gets to the first breakpoint, no error messages, it just doesn't run the program in Debug configuration.  The program runs in Release configuration, but I need to find a problem and cannot debug.  Any thoughts?


possible bug with !DIR$ directive and option /stand:f08

Take the following code:

subroutine test

    print *,"if this line exceeds 132 characters, the directive makes the compilation fail if using /stand:f08                                 1"
end subroutine

if I compile it with

ifort sub.f90 /c

I get no warnings or errors.

If however I compile it with 

ifort sub.f90 /c /stand:f08

I get:

non-allocated array for optional argument with cheks turned on

Dear all,

I think, the ifort compiler 16.0.0 and also previous ones behave strange, when turning on pointer checking ("-check pointers") and passing an unallocated array as actual argument to an optional array dummy argument in a subroutine. The code below compiles and runs fine without the "-check pointers" option, but triggers a false error during run-time when the option is turned on during the compilation.


Compability issues with F66

Hello, I'm trying to compile some sources coded that come from Unisys basic mode with F66 compatibility. I have create the makefile with the flags -f66 -nowarn, but I got a lot of syntax issues related to types, initialization, use of pseudo-functions,...etc. Maybe the reason of that is because I'm not using the right flags, so please could anyone give me any advise or help me with it?

Thanks in advance!



Crash after using derived type with allocatable component in DLL

I have a derived type that contains an allocatable array. A bound procedure exists that allows adding elements to that array. The adding involves a call to move_alloc. I call a procedure in a DLL with an argument of that derived type. The DLL procedure adds an element to the array. If after the return from the DLL procedure I add another element to the array -> crash.

Suscribirse a Intel® Fortran Compiler