Intel Developer Zone Articles

25-Feb-2014
11:10 AM PST
Diagnostic 15134: vectorization support: reference xxxx has unaligned access (Fortran)
By Martyn Corden (Intel)Posted 02/25/20140
Cause: The vectorizer cannot safely use aligned loads or stores for this data access, either because the data are not aligned to an n-byte boundary in memory, or because the compiler does not know the alignment. The compiler must use unaligned memory accesses, which may be less efficient. The val...
11-Feb-2014
10:16 AM PST
Intel® Visual Fortran Composer XE 2013 SP1 for Windows*, Update 2
By Roland Wiele (Intel)Posted 02/11/20140
Intel® Visual Fortran Composer XE 2013 SP1 Update 2 includes the latest Intel Fortran compilers and performance libraries for IA-32 and Intel® 64 architecture systems. This new product release now includes: Intel® Visual Fortran Compiler XE Version 14.0.2, Intel® Math Kernel Library (Intel® MKL) ...
11-Feb-2014
9:48 AM PST
Intel® Visual Fortran Composer XE 2013 SP1 for Windows* with IMSL*, Update 2
By Roland Wiele (Intel)Posted 02/11/20140
Intel® Visual Fortran Composer XE 2013 SP1 Update 2 includes the latest Intel Fortran compilers and performance libraries for IA-32 and Intel® 64 architecture systems. This new product release now includes: Intel® Visual Fortran Compiler XE Version 14.0.2, Intel® Math Kernel Library (Intel® MKL) ...
17-Jan-2014
2:54 PM PST
New Fortran switch allows use of abbreviated syntax to examine parent fields of an extended derived type when debugging
By Roland Wiele (Intel)Posted 01/17/20140
Examining the parent fields of an extended derived type in the gdb* or Microsoft Visual Studio* debugger currently requires that you also list the parent name.  A new internal command line switch for the Intel(R) Fortran Compiler, /switch:fe_debug_use_inherit (for Windows*) or –switch fe_debug_us...
02-Jan-2014
4:31 PM PST
Diagnostic 15015: loop was not vectorized: unsupported data type (Fortran)
By Martyn Corden (Intel)Posted 01/02/20140
Cause: The vectorizer does not support certain data types because there is no corresponding SIMD instruction. For example, the compiler supports REAL(16) arithmetic (quad precision) through a software implementation, but is unable to vectorize it: subroutine d_15015_1(a,b,n) implicit none ...
02-Jan-2014
4:29 PM PST
Diagnostic 15033: loop was not vectorized: modifying order of operation not allowed under given switches (Fortran)
By Martyn Corden (Intel)Posted 01/02/20140
Cause: A summation operation or reduction can be vectorized by breaking it up into a separate partial sum for each vector lane, and then adding together the partial sums at the end. Because this changes the order in which the individual contributions to the sum are added together, and hence the ...
24-Dec-2013
11:05 AM PST
Diagnostic 15011: loop was not vectorized: statement cannot be vectorized (Fortran)
By Martyn Corden (Intel)Posted 12/24/20130
  Cause: The loop contains a statement that cannot be mapped to SIMD instructions by the vectorizer. In the example below, the loop contains an assignment to a derived data type which is not directly vectorizable. Example: module my_mod integer, parameter :: N=1000 type :: my_type ...
19-Dec-2013
5:50 PM PST
Diagnostic 15032: loop was not vectorized: unsupported reduction (Fortran)
By Martyn Corden (Intel)Posted 12/19/20130
Cause: Reduction idioms can be recognized by the compiler and vectorized in simple cases.The compiler is unable to vectorize more complex constructs and emits a warning message: Example: integer function minIndex(x,n) implicit none real, intent(in), dimension(n) :: x real ...
16-Dec-2013
5:20 PM PST
Diagnostic 15037: loop was not vectorized: vectorization possible but seems inefficient (Fortran)
By Martyn Corden (Intel)Posted 12/16/20130
This diagnostic can also occur in the form:     remainder loop was not vectorized: vectorization possible but seems inefficient Cause: The compiler only auto-vectorizes a loop if its internal heuristics indicate that a speed-up is likely. If a speed-up seems unlikely or is too uncertain, the c...
13-Dec-2013
9:57 AM PST
Diagnostic 15046: loop was not vectorized: existence of vector dependence (Fortran)
By Martyn Corden (Intel)Posted 12/13/20130
Cause: The compiler has detected a potential backward dependency between loop iterations that could make vectorization unsafe. The compiler will not auto-vectorize a loop if there are any data values for which vectorization could lead to an incorrect result. Two common examples are:  1. reading...
Subscribe to Intel Developer Zone Articles