Apple OS X*

Inquire statement with -openmp option

Dear forum,

I actually use Intel composer_xe_2013_sp1.2.144 with openMP.

I separated the following issue from my software project. The program fails to execute in case of using

INQUIRE (FILE= ... , OPENED= ...) together with the -openmp option, see example.

Otherwiese, without -openmp option or without the statement every things works fine.

Intel® GPA: Which Tools Are Available on My Platform?

Intel® GPA is the premier tool for optimizing games on Microsoft Windows*. Intel GPA also supports the analysis of games on Intel phones and tablets running the Google* Android* OS. This article describes the different platforms for the product, and how to download the product.
  • Developers
  • Android*
  • Apple OS X*
  • Linux*
  • Microsoft Windows* (XP, Vista, 7)
  • Microsoft Windows* 8
  • Android*
  • Windows*
  • Intel® Graphics Performance Analyzers
  • vcsource_type_techarticle
  • vcsource_product_gpa
  • vcsource_index
  • Microsoft DirectX*
  • OpenGL*
  • Game Development
  • Graphics
  • Xcode 5.1 unsupported?

    Tried updating Xcode to 5.1, but it seems to have dropped my FORTRAN 14.0 compiler after multiple attempts to re-install the compiler after the upgrade.  Downgraded Xcode to 5.0.2 and everything works fine again.  Not sure what Apple changed, but it looks like Xcode 5.1 doesn't support the Intel FORTRAN compiler once again.

    Mysterious ifort compilation failure when -fpp is used with input file is on a NFS volume

    This is a bit hard to describe, and unbelievable, too!

    All of a sudden, one of our files can not be compiled by ifort anymore, and as I look into the cause of the failure, it looks like -fpp really mess up the compilation - this particular file has a lot of #ifndef, #ifdef blocks.

    here is the findings:

    1) by using -save-temps, I was able to get the .i file, and with that file, I can compile it successfully with either -fpp or without -fpp option.

    Compiler bug with associate construct

    I was playing around with a way to record log messages in an internal "file" (character variable) when I came upon a strange compiler notice. The following module does not compile, producing the error

    error #7146: This object must not be used as an allocate-object in an allocate-stmt or deallocate-stmt in a PURE procedure or an internal procedure contained in a PURE procedure.   [TEMP]
          allocate(temp(2*size(this%buffer)), mold = this%buffer)

    **Internal compiler error: segmentation violation signal raised** with -O3

    Dear Intel developers,

    Compilation of this subroutine optrms.F (See attachment) leads to an  **Internal compiler error: segmentation violation signal raised** with -O3 options. This error disappears with -O2

    The compilation instructions is /share/apps/intel/composer_xe_2013_sp1.2.144/bin/intel64/ifort -i8 -r8 -pc64 -auto -vec-report0 -warn nousage -cxxlib

    fort version: Intel(R) Fortran Intel(R) 64 Compiler XE for applications running on Intel(R) 64, Version 14.0.2.144 Build 20140120

    Linux kernel: 2.6.32-279.14.1.el6.x86_64

    Diagnostic 15002: loop was vectorized (Fortran)

     

    Cause:

    For the Intel® Compiler, vectorization is the unrolling of a loop combined with the generation of packed SIMD instructions. Because the packed instructions operate on more than one data element at a time, the loop can execute more efficiently. The above message indicates that the loop was successfully vectorized using packed SIMD instructions. 

    Example:

  • Apple OS X*
  • Linux*
  • Microsoft Windows* (XP, Vista, 7)
  • Microsoft Windows* 8
  • Fortran
  • Intel® Composer XE
  • Intel® Fortran Compiler
  • Intel® Fortran Composer XE
  • Intel® Visual Fortran Composer XE
  • Intel® Fortran Studio XE
  • Intel® Parallel Studio XE
  • vectorization
  • Diagnostics
  • Optimization
  • Vectorization
  • some compiler options relevant to compilation cascades

    I've seen that NAG provides some options to control the output and behavior surrounding .mod files. I've poured through the documentation, and I can't find Intel's direct equivalents to these options, however I think I have an idea of some work arounds. Can someone please let me know if I have overlooked anything?

    The NAG options in question are:

    Subscribe to Apple OS X*