Filters

Article

Being Successful with the Intel® Compilers -- You Need to Know

Tips and techniques on using the Intel® Compilers to maximize your application performance.
Authored by Last updated on 03/05/2019 - 22:07
Article

Intel® C++ Compiler - ANSI C/C++ and OpenMP* compliance

C Standard Conformance

Authored by Jennifer J. (Blackbelt) Last updated on 08/01/2019 - 19:50
Article

Intel® Compiler - How can I generate optimized code to run on any IA-32 or Intel®64 architecture processor?

Some frequently used optimization switches of the Intel Compiler are described
Authored by admin Last updated on 05/25/2018 - 15:30
Article

Performance Tools for Software Developers - SSE generation and processor-specific optimizations continued

Can I combine the processor values and target more than one processor? How to generate optimized code for both Intel and AMD* architecture? Where can I find more information on processor-specific optimizations?
Authored by admin Last updated on 05/25/2018 - 15:30
Article

Performance Tools for Software Developers - Loop blocking

Loop blocking is a combination of strip mining and loop interchange to enhance reuse of local data. It helps the nested loops that manipulate arrays and are too large to fit into the cache. The loop blocking allows reuse of the arrays by transforming the
Authored by admin Last updated on 05/25/2018 - 15:30
Article

Performance Tools for Software Developers - Auto-parallelization and /Qpar-threshold

The article describes effect of /Qpar-threshold option when doing auto parallelization with Intel C++ compiler.
Authored by admin Last updated on 12/31/2018 - 15:00
Article

Size of 'long integer' data type (C++) on various architectures and OS

The Intel® Compiler treats the size of a "long" integer as 4 bytes or 8 bytes depending on the architecture and operating system, affecting portability. The size of a "long long" integer is always 8 bytes. The size of a "long double" may also vary.
Authored by admin Last updated on 12/26/2018 - 17:39
Article

internal threshold was exceeded

In very large, complex functions, loops preceded by OpenMP directives may not be threaded. Compiler may emit the warning remark: "An internal threshold was exceeded: loops may not be vectorized or parallelized. Try to reduce routine size."
Authored by Martyn Corden (Intel) Last updated on 12/26/2018 - 13:11
Article

White space requirement between macro name and replacement text

In the definition of an object-like macro, C99 and C++0x require that the replacement text be separated from the macro name by white space. The Intel® Compiler will check this requirement and will issue appropriate warning accordingly.
Authored by admin Last updated on 05/25/2018 - 15:30
Article

Diagnostic 29: expected an expression

Cause:
Authored by admin Last updated on 05/25/2018 - 15:30