Reference Number : DPD200151036 Version : 11.1.084 Product : Intel(R) Compiler for Mac OS* X Operating System : Mac OS X 10.5.x, 10.6.x Problem Description : $ cat t.cpp #include void foo (void) { std::cout
More here:
Can not build static library with 11.1.084
Reference Number : DPD200141726 Version : 11.1 and earlier Product : Intel(R) Visual Fortran Compiler Professional Edition for Windows* Operating System : Microsoft Windows XP*, Microsoft Windows Vista* Problem Description : Intermitent Errors were observed when building multi-project solutions under Visual Studio* on multi-core systems. Examples of errors reported: catastrophic error: Unable to read ‘filename’ error #5102: Cannot open include file ‘filename’ Microsoft Visual Studio has encountered a problem and needs to close All files flagged by the errors were present and accessible. Errors occurred on both Windows XP* and Vista* and on Visual Studio 2005* and 2008*. Errors were not observed on single core systems. Given the above information it was concluded that this was a parallel build issue. Visual Studio* will by default set the maximum number project builds to be performed in parallel to the number of cores on the system on which it was installed. Setting tools> Options…> Project and Solutions> Build and Run> maximum number of project builds to 1 eliminates the build errors. It should also be noted that the errors only occur when devenv is invoked from the command line. Build errors do not occur when building under the IDE. Resolution Status : This issue has been fixed in Intel(R) Visual Fortran Compiler Professional Edition for Windows* version 11.1 Update 5 (w_cprof_p_11.1.060)
Here is the original:
Intermitent Errors Occurring When Building under Visual Studio*
Version : Intel® MKL 10.* Product : Intel® Math Kernel Library Operating System : All supported OS’s – Microsoft Windows*, Linux* and Mac OS X Problem Description : When iparm[59] is set 1 and – memory required for the task solution is less then MKL_PARDISO_OOC_MAX_CORE_SIZE and – RAM available in the system > = MKL_PARDISO_OOC_MAX_CORE_SIZE PARDISO reports the following message: “=== PARDISO is running in Out-Of-Core mode, because iparam(60)=1 and there is not enough RAM for In-Core ===”.
More:
PARDISO: incorrect behavior in deciding whether to use in-Core or out-of-core (OOC)
Reference Number : DPD200087222 Version : Intel® MKL 10.2 Product : Intel(R) Math Kernel Library (Intel MKL) Operating System : Red Hat Enterprise Linux* 5 Microsoft Windows Problem Description : PARDISO returns the erroneous result or throws an exceptions in the following cases: 1) input matrix type == 11: real and unsymmetric, with multiple right-hand sides ( nhrs > 1 ) and when CGS iteration replaces the computation of LU ( iparm(4) == 31,61) or 2) input matrix’s type == 13: complex and unsymmetric matrix, with one right-hand side (nhrs ==1) and iparm(4) == 31,61 Resolution Status : The problem has been already fixed in the version Intel(R) MKL 10.2 Update 4. [DISCLAIMER: The information on this web site is intended for hardware system manufacturers and software developers. Intel does not warrant the accuracy, completeness or utility of any information on this site
Here is the original:
PARDISO returns the erroneous results or throws an exception.
Reference Number : dpd200150830 Version : 11.0 and 11.1 Product : Intel C++ and Fortran Compilers Problem Description : Variables within the lexical extent of an OpenMP task are treated as private by default, whereas the default should be shared (except for loop indices). For example, in the following Fortran code snippet: !$OMP PARALLEL !$OMP SINGLE ……
View original here:
OpenMP TASK directive incorrectly defaults to PRIVATE
Reference Number : DPD200148269 Version : 11.1 Product : Intel Fortran Compiler Operating System : All Problem Description : A valid pointer assignment to type-bound procedure returning a pointer may fail to compile.
Original post:
error #6678: compiler defect with pointer assignment to a type-bound procedure returning a pointer
Reference Number : DPD200148269 Version : 11.1 Product : Intel Fortran Compiler Operating System : All Problem Description : A valid pointer assignment to type-bound procedure returning a pointer may fail to compile. The compiler will incorrectly diagnose this as “error #6678: When the target is an expression it must deliver a pointer result.” The error only occurs if the procedure is invoked through a type-compatible object using component selector syntax (the % sign). An example of such a code: MODULE ArrayModule IMPLICIT NONE TYPE ArrayOps INTEGER, DIMENSION(:), POINTER :: iArray CONTAINS PROCEDURE :: allocArray PROCEDURE :: getSubArray END TYPE ArrayOps CONTAINS SUBROUTINE allocArray(self, aSize) CLASS(ArrayOps) :: self INTEGER, INTENT(IN) :: aSize ALLOCATE(self%iArray(aSize)) END SUBROUTINE allocArray FUNCTION getSubArray(self, LB, UB) CLASS(ArrayOps) :: self INTEGER, INTENT(IN) :: LB, UB INTEGER, DIMENSION(:), POINTER :: getSubArray getSubArray => self%iArray(LB:UB) END FUNCTION END MODULE ArrayModule PROGRAM getTypeBoundPtKB USE ArrayModule IMPLICIT NONE TYPE(ArrayOps) :: aVar INTEGER, DIMENSION(:), POINTER :: subArray CALL aVar%allocArray(10) #ifdef SHOW_BUG subArray => aVar%getSubArray(2,5) #else subArray => getSubArray(aVar,2,5) #endif END PROGRAM getTypeBoundPtKB The compiler will incorrect diagnose this as error #6678: > ifort -V Intel(R) Fortran Intel(R) 64 Compiler Professional for applications running on Intel(R) 64, Version 11.1 > ifort -fpp -DSHOW_BUG getTypeBoundPtKB.f90 getTypeBoundPtKB.f90(31): error #6678: When the target is an expression it must deliver a pointer result. subArray => aVar%getSubArray(2,5) —————^ compilation aborted for getTypeBoundPtKB.f90 (code 1) > As a workaround, avoid using component selector syntax, and explicitly pass the invoking object to the procedure. The workaround is illustrated in the example: subArray => getSubArray(aVar,2,5) The example can be successfully compiled by not defining SHOW_BUG: ifort -fpp getTypeBoundPtKB.f90 Resolution Status : The issue is planned to be fixed in an update to the 11.1 compiler [DISCLAIMER: The information on this web site is intended for hardware system manufacturers and software developers
Read the original:
error #6678: compiler defect with pointer assignment to a type-bound procedure returning a pointer
The user may run sampling data collection with BIG application, but only have interest of limited code area, so collecting data for whole run is unnecessary.
Excerpt from:
Using ActivityController to selectively profile your big program
Reference Number : DPD200149092 Version : v11.1 Product : Intel Fortran Compiler Operating System : All Problem Description : Inheritance in Intel Fortran has the following defect. An extended public type with PRIVATE components cannot be accessed if the parent component is referenced
Read more:
error #6292: compiler defect accessing extended type if parent component is referenced
Reference Number : DPD200148444 Version : v11.1 Product : Intel Fortran Compiler Operating System : All Problem Description : A legal polymorphic (class) pointer assignment to a type-compatible target may cause an internal compiler error with Intel Fortran v11.1. An example of such a code is: module class_link private public :: lnode public :: get_elem type lnode integer :: node end type type link_ptr class(lnode), pointer :: elem => null() end type type(link_ptr) :: lnk_ptr contains function get_elem() result(rtnlnk) class(lnode), pointer :: rtnlnk rtnlnk => lnk_ptr%elem end function end module program class_link_ptr use class_link class(lnode), pointer :: lptr lptr => get_elem() end program class_link_ptr The internal compiler error error produced when this code is compiled: > ifort class_link_ptr.f90 Intel(R) Visual Fortran Compiler Professional for applications running on IA-32, Version 11.1 Build 20091130 Package ID: w_cprof_p_11.1.054 Copyright (C) 1985-2009 Intel Corporation. All rights reserved
See original here:
Internal compiler error with polymorphic pointer assignment