04-abr-2014
2:49 AM PDT
Open Source Downloads
By Georg Zitzlsberger (Intel)Posted 04/04/20146
This article makes available third-party libraries, executables and sources that were used in the creation of Intel® Software Development Products or are required for operation of those. Intel provides this software pursuant to their applicable licenses. [Intel® Graphics Technology, Intel® Compos...
03-abr-2014
9:07 AM PDT
Environment not set correctly for non-Intel(R) Composer XE products in compiler command prompts
By Brandon Hewitt (Intel)Posted 04/03/20140
Reference Number: DPD200519258  Version: 2015 (Compiler 15.0) Product: Intel® Composer XE (affects Intel® VTune™ Amplifier XE, Intel® Inspector XE, and Intel® Advisor XE) Operating System: Windows* Problem Description: When using the 15.0 compiler command prompts from the Start Menu (under St...
31-mar-2014
1:28 PM PDT
Intel MPI Library and Composer XE Compatibility
By Gergana Slavova (Intel)Posted 03/31/20140
The following table lists all supported versions of the Intel® MPI Library and the Intel® Composer XE.  Use this as a reference on the cross-compatibility between the library and associated compiler. Compatibility Matrix Intel® MPI Library Version Intel® Compiler XE 8.1 Intel® Compiler XE...
31-mar-2014
1:28 PM PDT
Intel MPI Library and Composer XE Compatibility
By Gergana Slavova (Intel)Posted 03/31/20140
The following table lists all supported versions of the Intel® MPI Library and the Intel® Composer XE.  Use this as a reference on the cross-compatibility between the library and associated compiler. Compatibility Matrix Intel® MPI Library Version Intel® Compiler XE 8.1 Intel® Compiler XE...
27-mar-2014
5:29 PM PDT
Diagnostic 15003: PARTIAL LOOP WAS VECTORIZED (Fortran)
By Martyn Corden (Intel)Posted 03/27/20140
Cause: This message is emitted when only part of the loop body is vectorized. The loop is distributed (divided) into two loops, one of which is vectorized and one of which is not. Example: subroutine d_15003(a,b,n) implicit none integer, intent(out), dimension(n) :: a,b integer, intent(i...
27-mar-2014
3:13 PM PDT
Intel® Software Development Tools 2015 Beta
By Gergana Slavova (Intel)Posted 03/27/20140
Contents What's New Details Frequently Asked Questions Beta duration Support How to enroll in the Beta program Beta Webinars Known Issues and Special Features Next Steps   What's New in the 2015 Beta This suite of products brings together exciting new technologies along...
07-mar-2014
4:25 PM PST
Diagnostic 15002: loop was vectorized (Fortran)
By Martyn Corden (Intel)Posted 03/07/20140
  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 ...
25-fev-2014
12:15 PM PST
Diagnostic 15133: vectorization support: reference xxxx has aligned access (Fortran)
By Martyn Corden (Intel)Posted 02/25/20140
Cause: The vectorizer was able to generate code for this memory access assuming the data to be aligned to an n-byte boundary in memory. The value of n depends on the targeted instruction set and corresponds to the width of the vector instructions: 16 for Intel® SSE, 32 for Intel® AVX and 64 for ...
25-fev-2014
11:37 AM PST
Diagnostic 15126: vectorization support: unaligned access used inside loop body
By Martyn Corden (Intel)Posted 02/25/20140
Cause: The loop contains one or more memory accesses for which the vectorizer could not safely use aligned load or store instructions, either because the data are not aligned to an n-byte boundary in memory, or because the compiler does not know the alignment. The value of n depends on the targe...
25-fev-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...

Páginas

Assine o