Guided Auto Parallelism Overview

The Guided Auto Parallelism (GAP) feature of the Intel® Fortran Compiler is a tool that offers selective advice to improve the performance of serially-coded applications by suggesting changes that will take advantage of the compiler’s ability to automatically vectorize and parallelize your code as well as improve the efficiency of data operations. Despite having the words “auto parallelism” in the name, this tool does not require you to implement threaded code in order to improve the execution performance of your code nor does it require that your code is already threaded or parallel code.

You do not need to use any advanced optimization techniques such as inter-procedural analysis or profile-guided feedback to use this feature. Using the [Q]guide set of options in addition to the compiler options you normally use is sufficient to enable the GAP feature, with the requirement that you must compile with O2 or higher optimization levels. The compiler does not generate any object files or executables during the GAP run.

In debug mode (/Zi on Windows* OS, -g on Linux* OS), the compiler's optimization level defaults to /Od (on Windows* OS) or -O0 (on Linux* OS and OS X*); thus O2 (or a higher level optimization) must be specified explicitly on the command-line.

//  (Windows* OS)
/Qguide, /Qdiag-disable:30534

//  (Linux* OS and OS X*)
-guide, -diag-disable:30534

If you decide to follow the advice offered by the GAP tool by making the suggested code changes and/or using the suggested compiler options, you must then recompile the program without the [Q]guide option.

Any advice generated by the compiler when using the GAP tool is optional; you can either implement it or reject it. The advice typically falls under three broad categories:

• Advice for source modifications: The compiler advises you to make source changes that are localized to a loop-nest or a routine. For example, the tool may recommend that you use a local-variable for the upper-bound of a loop or that you should initialize a local variable unconditionally at the top of the loop-body.
• Advice to apply directives: The compiler advises you to apply a new directive on a certain loop-level if the directive semantics can be satisfied (you must verify this). In many cases, you may be able to apply the directive (thus implicitly asserting new program/loop properties) that the compiler can then take advantage of to perform enhanced optimizations.
• Advice to add compiler options: The compiler advises you to add command-line options that assert new properties.

  Note

  These suggested compiler options apply to the entire file. It is your responsibility to check that the properties asserted by these options are valid for the entire file, and not just the loop in question.

If you use GAP options along with option [Q]parallel , the compiler may suggest options to further parallelize your application. The compiler may also offer advice on enabling other optimizations of your application, including vectorization.

If you use the GAP options without enabling auto parallelism (without using the [Q]parallel option), the compiler may only suggest enabling optimizations such as vectorization for your application. This approach is recommended when you wish to improve the performance of a single-threaded code without the use of parallelization or when you want to improve the performance of threaded applications that do not rely on the compiler for auto parallelism.