Intel® Fortran Compiler

Coarray type with an allocatable component of length zero

I get a SIGSEGV when running the following code

 type t

	  real, allocatable :: a(:)

	 end type t

	 type(t) :: data[*]


	 print*, size(data[1]%a)

	end program

If, instead of the last line I put

print*, size(data%a)

it runs successfully by printing 0 for each image. In principle I could work out the problem by using 'allocated' statements, but



interdependence of indices in DO CONCURRENT

The following DO statement compiles on IFORT [IA-32]:

DO CONCURRENT (i = 1:SIZE(arr1d), j = 1:i-1)

According to the F08 draft (N1830), C739 it is not permitted to

reference to any index-name in the forall-triplet-spec-list in which it appears

, and if I use the same forall-header in a FORALL statement the error is catched.

Is this allowed or not?

Support for Intrinsic EXECUTE_COMMAND_LINE

Dear Intel team,

Is there a roadmap for supporting further Fortran 03/08 intrinsics such as EXECUTE_COMMAND_LINE? I am working on a project right now that is supposed to be 100% standard compliant (up to F2008) and I am looking for a way to replace my ifort-only SYSTEM call.

I guess implementing this specific functionality is not a very big deal, particularly compared to other new features that obviously need some more time to make it into all compilers.

Really appreciate your thoughts on this..

Visual Studio 2012: Global Variables Not Displayed in Watch Window

Hi all,

I am using the Intel Visual Fortran Compiler as a 64bit version. On my PC, I am using Visual Studio Version 2010 w/o any problems.

On my Laptop I have the Visual Studio 2012 version and the problem is that gloabal variables are not displayed in the watch window (as they are on my PC version using Visual Studio 2010). I checked the settings in Project -> Properties -> Fortran -> Debugging and have the options set correctly, hence

Debug Information Format: Full

Infromation for PARAMETER Constant: All

Intel(R) C++ Compiler and Intel(R) Fortran Compiler Do not Work with XCode 5.1*

Reference Number : DPD200254375

  • Intel(R) C++ Composer XE 2013 for OS X* (including update 2)
  • Intel(R) Fortran Composer XE 2013 for OS X* (including update 2)

Problem Description:

If you have recently upgraded to the latest XCode 5.1*, the Intel C++ compiler or the Intel Fortran compiler is not integrated into XCode any more. So the existing projects that are built with Intel C++ compiler or Intel Fortran compiler will fail when building.

Solution Status:

  • Desarrolladores
  • Apple OS X*
  • C/C++
  • Fortran
  • Intel® C++ Compiler
  • Intel® Fortran Compiler
  • XCode
  • Compiler not detecting missing OMP4 declare target variable

    Most of the time, the compiler will complain if a global variable used in an OMP4 target region is not declared for the target (!$omp declare targt(foo))

    But now I had a (very big) program that compiled without errors (finally after fixing all the missing declares) but failed at runtime with the message:

    Functions returning arrays, derived types and the creation of temporaries.

    Dear all,

    Consider the following situation followed up by a working test case.

    Let there be a derived type wrapping a multidimensional array. Let there further be a function "sum" which adds array components of the objects of a derived type and returns the resulting array. Furthermore, there is a "from_array" assignment subroutine which takes an object and an array, then fills the array component of the object with its array argument.

    Override default component initialization


    I understand the following is not legal:

    module foo
    type :: bar
        integer :: a=53
    end type
    type, extends(bar) :: rab
        integer :: a=-33333 !!! Redefine default initialization
    end type
    end module

    I think this would be quite practical. The only workaround is implementing clumsy constructor wrappers...

    Any thoughts?

    Suscribirse a Intel® Fortran Compiler