A scalar data type holds a single value, such as the integer value 42 or the real value 112.6. The next table lists scalar data types, their size, format and range. Table 3 shows the range and approximate precision for Fortran real data types. Table 4 shows the alignment for different scalar data types. The alignments apply to all scalars, whether they are independent or contained in an array, a structure or a union.

⁽¹⁾ Approximate value

The logical constants .TRUE. and .FALSE. are all ones and all zeroes, respectively. Internally, the value of a logical variable is true if the least significant bit is one and false otherwise. When the option -⁠Munixlogical is set, a logical variable with a non-zero value is true and with a zero value is false.

The PGFORTRAN compiler supports de facto standard extensions to FORTRAN 77 that allow for aggregate data types. An aggregate data type consists of one or more scalar data type objects. You can declare the following aggregate data types:

• An array consists of one or more elements of a single data type placed in contiguous locations from first to last.
• A structure can contain different data types. The members are allocated in the order they appear in the definition but may not occupy contiguous locations.
• A union is a single location that can contain any of a specified set of scalar or aggregate data types. A union can have only one value at a time. The data type of the union member to which data is assigned determines the data type of the union after that assignment.

The alignment of an array, a structure or union (an aggregate) affects how much space the object occupies and how efficiently the processor can address members. Arrays use the alignment of their members.

Array types

align according to the alignment of the array elements. For example, an array of INTEGER*2 data aligns on a 2-byte boundary.

Structures and Unions

align according to the alignment of the most restricted data type of the structure or union. In the next example, the union aligns on a 4-byte boundary since the alignment of c, the most restrictive element, is four.

STRUCTURE /astr/
UNION
 MAP
 INTEGER*2 a ! 2 bytes
 END MAP
 MAP
 BYTE b ! 1 byte
 END MAP
 MAP
 INTEGER*4 c ! 4 bytes
 END MAP
END UNION
END STRUCTURE

Structure alignment can result in unused space called padding. Padding between members of the structure is called internal padding. Padding between the last member and the end of the space is called tail padding.

The offset of a structure member from the beginning of the structure is a multiple of the member's alignment. For example, since an INTEGER*2 aligns on a 2-byte boundary, the offset of an INTEGER*2 member from the beginning of a structure is a multiple of two bytes.

The Fortran 90 standard added formal support for aggregate data types. The TYPE statement begins a derived type data specification or declares variables of a specified user-defined type. For example, the following would define a derived type ATTENDEE:

TYPE ATTENDEE
 CHARACTER(LEN=30) NAME
 CHARACTER(LEN=30) ORGANIZATION
 CHARACTER (LEN=30) EMAIL
END TYPE ATTENDEE

In order to declare a variable of type ATTENDEE and access the contents of such a variable, code such as the following would be used:

TYPE (ATTENDEE) ATTLIST(100)
. . .
ATTLIST(1)%NAME = ‘JOHN DOE’

The options included in the following table pertain to the initial building of your program or application.

The options included in the following table pertain to debugging your program or application.

The options included in the following table pertain to optimizing your program or application code.

The options included in the following table pertain to defining parameters related to linking and running your program or application.

This section describes the -⁠M<pgflag> options that control code generation.

Default: For arguments that you do not specify, the default code generation controls are these:

Related options:-⁠D, -⁠I, -⁠L, -⁠l, -⁠U.

The following list provides the syntax for each -⁠M<pgflag> option that controls code generation. Each option has a description and, if appropriate, any related options.

-Mdaz

Set IEEE denormalized input values to zero; there is a performance benefit but misleading results can occur, such as when dividing a small normalized number by a denormalized number.
To take effect, this option must be set for the main program. To set this option in PVF, use the Fortran |
Floating Point Options | Treat Denormalized Values as Zero property, described in ‘Treat Denormalized Values as Zero’

-Mnodaz

Do not treat denormalized numbers as zero.
To take effect, this option must be set for the main program.

-Mnodwarf

Specifies not to add DWARF debug information.
To take effect, this option must be used in combination with -⁠g.

-Mdwarf1

Generate DWARF1 format debug information.
To take effect, this option must be used in combination with -⁠g.

-Mdwarf2

Generate DWARF2 format debug information.
To take effect, this option must be used in combination with -⁠g.

-Mdwarf3

Generate DWARF3 format debug information.
To take effect, this option must be used in combination with -⁠g.

-Mflushz

Set SSE flush-to-zero mode; if a floating-point underflow occurs, the value is set to zero.
To take effect, this option must be set for the main program.
To set this option in PVF, use the Fortran | Floating Point Options | Flush Denormalized Results to Zero property, described in ‘Flush Denormalized Results to Zero’ on page 391.

-Mnoflushz

Do not set SSE flush-to-zero mode; generate underflows.
To take effect, this option must be set for the main program.

-Mfunc32

Align functions on 32-byte boundaries.

-Minstrument[=functions] (linux86-64 only)

Generate additional code to enable instrumentation of functions. The option -⁠Minstrument=functions is the same as -⁠Minstrument.
Implies -⁠Minfo=ccff and -⁠Mframe.

-Mlargeaddressaware=[no]

[Win64 only] Generates code that allows for addresses greater than 2 GB, using RIP-relative addressing.
Use-⁠Mlargeaddressaware=no for a direct addressing mechanism that restricts the total addressable memory.

Note: Do not use -⁠Mlargeaddressaware=no if the object file will be placed in a DLL.

If -⁠Mlargeaddressaware=no is used to compile any object file, it must also be used when linking.

-Mlarge_arrays

Enable support for 64-bit indexing and single static data objects larger than 2 GB in size. This option is the default in the presence of -⁠mcmodel=medium. It can be used separately together with the default small memory model for certain 64-bit applications that manage their own memory space.
For more information, refer to the ‘Programming Considerations for 64-Bit Environments’ section of the PGI Visual Fortran Compiler User's Guide.

-Mnolarge_arrays

Disable support for 64-bit indexing and single static data objects larger than 2 GB in size. When this option is placed after -⁠mcmodel=medium on the command line, it disables use of 64-bit indexing for applications that have no single data object larger than 2 GB.
For more information, refer to the ‘Programming Considerations for 64-Bit Environments’ section of the PGI Visual Fortran Compiler User's Guide.

-Mnomain

Instructs the compiler not to include the object file that calls the Fortran main program as part of the link step. This option is useful for linking programs in which the main program is written in C/C++ and one or more subroutines are written in Fortran.

-Mmpi=option

-⁠Mmpi adds the include and library options to the compile and link commands necessary to build an MPI application using MPI header files and libraries.
To use -⁠Mmpi, you must have a version of MPI installed on your system.
This option tells the compiler to use the headers and libraries for the specified version of MPI.
-Mmpi=msmpi – Select the default Microsoft MPI libraries on Windows.
For more information, refer to the ‘Programming Considerations for 64-Bit Environments’ section of the PGI Visual Fortran Compiler User's Guide.

-M[no]movnt

Instructs the compiler to generate nontemporal move and prefetch instructions even in cases where the compiler cannot determine statically at compile-time that these instructions will be beneficial.

-M[no]pre

enables [disables] partial redundancy elimination.

-Mprof[=option[,option,...]]

Set performance profiling options. Use of these options changes which sections are included in the binary. These sections can be read by the PGI profiler.
The option argument can be any of the following:

[no]ccff

Enable [disable] common compiler feedback format, CCFF, information.

dwarf

Add limited DWARF symbol information sufficient for most performance profilers.

-Mrecursive

instructs the compiler to allow Fortran subprograms to be called recursively.

-Mnorecursive

Fortran subprograms may not be called recursively.

-Mref_externals

force references to names appearing in EXTERNAL statements.

-Mnoref_externals

do not force references to names appearing in EXTERNAL statements.

-Mreentrant

instructs the compiler to avoid optimizations that can prevent code from being reentrant.

-Mnoreentrant

instructs the compiler not to avoid optimizations that can prevent code from being reentrant.

-Msecond_underscore

instructs the compiler to add a second underscore to the name of a Fortran global symbol if its name already contains an underscore. This option is useful for maintaining compatibility with object code compiled using g77, which uses this convention by default.

-Mnosecond_underscore

instructs the compiler not to add a second underscore to the name of a Fortran global symbol if its name already contains an underscore.

-Msafe_lastval

When a scalar is used after a loop, but is not defined on every iteration of the loop, the compiler does not by default parallelize the loop. However, this option tells the compiler it’s safe to parallelize the loop. For a given loop, the last value computed for all scalars makes it safe to parallelize the loop.

-Msignextend

instructs the compiler to extend the sign bit that is set as a result of converting an object of one data type to an object of a larger signed data type.

-Mnosignextend

instructs the compiler not to extend the sign bit that is set as the result of converting an object of one data type to an object of a larger data type.

-Mstack_arrays

places automatic arrays on the stack.

-Mnostack_arrays

allocates automatic arrays on the heap. -Mnostack_arrays is the default and what traditionally has been the approach used.

-Mstride0

instructs the compiler to inhibit certain optimizations and to allow for stride 0 array references. This option may degrade performance and should only be used if zero-stride induction variables are possible.

-Mnostride0

instructs the compiler to perform certain optimizations and to disallow for stride 0 array references.

-Mvarargs

force Fortran program units to assume procedure calls are to C functions with a varargs-type interface.

This section describes the -⁠M<pgflag> options that control environments.

Default: For arguments that you do not specify, the default environment option depends on your configuration.

The following list provides the syntax for each -⁠M<pgflag> option that controls environments. Each option has a description and, if appropriate, a list of any related options.

-Mnostartup

instructs the linker not to link in the standard startup routine that contains the entry point (_start) for the program.

Note: If you use the -⁠Mnostartup option and do not supply an entry point, the linker issues the following error message: Warning: cannot find entry symbol _start

-M[no]smartalloc[=huge|huge:<n>|hugebss|nohuge]

adds a call to the routine mallopt in the main routine. This option supports large TLBs on Linux and Windows. This option must be used to compile the main routine to enable optimized malloc routines.
The option arguments can be any of the following:

huge

Link in the huge page runtime library.
Enables large 2-megabyte pages to be allocated. The effect is to reduce the number of TLB entries required to execute a program. This option is most effective on newer architectures; older architectures do not have enough TLB entries for this option to be beneficial. By itself, the huge suboption tries to allocate as many huge pages as required.

huge:<n>

Link the huge page runtime library and allocate n huge pages. Use this suboption to limit the number of huge pages allocated to n.
You can also limit the pages allocated by using the environment variable PGI_HUGE_PAGES.

hugebss

(64-bit only) Puts the BSS section in huge pages; attempts to put a program's uninitialized data section into huge pages.

Note: This flag dynamically links the library libhugetlbfs_pgi even if -⁠Bstatic is used.

nohuge

Overrides a previous -⁠Msmartalloc=huge setting.

Tip: To be effective, this switch must be specified when compiling the file containing the Fortran, C, or C++ main program.

-Mnostdinc

instructs the compiler to not search the standard location for include files. To set this option in PVF, use the Fortran | Preprocessor | Ignore Standard Include Path property, described in ‘Ignore Standard Include Path’ on page 381.

-Mnostdlib

instructs the linker not to link in the standard libraries in the library directory lib within the standard directory. You can link in your own library with the -⁠l option or specify a library directory with the -⁠L option.

This section describes the -⁠M<pgflag> options that affect Fortran language interpretations by the PGI Fortran compilers. These options are valid only for the Fortran compiler drivers.

Default: Before looking at all the options, let's look at the defaults. For arguments that you do not specify, the defaults are as follows:

The following list provides the syntax for each -⁠M<pgflag> option that affect Fortran language interpretations. Each option has a description and, if appropriate, a list of any related options.

-Mallocatable=95|03

controls whether Fortran 95 or Fortran 2003 semantics are used in allocatable array assignments. The default behavior is to use Fortran 95 semantics; the 03 option instructs the compiler to use Fortran 2003 semantics.

-Mbackslash

instructs the compiler to treat the backslash as a normal character, and not as an escape character in quoted strings.

-Mnobackslash

instructs the compiler to recognize a backslash as an escape character in quoted strings (in accordance with standard C usage).

-Mcuda

instructs the compiler to enable CUDA Fortran. If more than one option is on the command line, all the specified options occur.

The following suboptions exist:

ccXY

Generate code for a device with compute capability X.Y. Multiple compute capabilities can be specified, and one version will be generated for each. By default, the compiler will detect the compute capability for each installed GPU. Use -help -Mcuda to see the valid compute capabilities for your installation.

ccall

Generate code for all compute capabilities supported by this platform and by the selected or default CUDA Toolkit.

cudaX.Y

Use CUDA X.Y Toolkit compatibility, where installed.

7.5, 8.0, 9.0, 9.1

Support for the X.Y suboption has been removed. Use the cudaX.Y suboption instead.

fastmath

Use routines from the fast math library.

[no]flushz

Enable[disable] flush-to-zero mode for floating point computations in the GPU code generated for CUDA Fortran kernels.

generate rdc

Generate relocatable device code

keepbin

Keep the generated binary (.bin) file for CUDA Fortran.

keepgpu

Keep the generated GPU code for CUDA Fortran.

keepptx

Keep the portable assembly (.ptx) file for the GPU code.

kepler

is equivalent to -Mcuda,cc3x

llvm

Generate code using the llvm-based back-end.

[no]debug

Enable[disable] GPU debug information generation.

[no]lineinfo

Enable[disable] GPU line information generation.

maxregcount:n

Specify the maximum number of registers to use on the GPU. Leaving this blank indicates no limit.

nofma

Do not generate fused multiply-add instructions.

noL1

Prevent the use of L1 hardware data cache to cache global variables.

ptxinfo

Show PTXAS informational messages during compilation.

rdc

Enable CUDA Fortran separate compilation and linking of device routines, including device routines in Fortran modules.
To enable separate compilation and linking, include the command line option -Mcuda=rdc on both the compile and the link steps.

-Mdclchk

instructs the compiler to require that all program variables be declared.

-Mnodclchk

instructs the compiler not to require that all program variables be declared.

-Mdefaultunit

instructs the compiler to treat "*" as a synonym for standard input for reading and standard output for writing.

-Mnodefaultunit

instructs the compiler to treat "*" as a synonym for unit 5 on input and unit 6 on output.

-Mdlines

instructs the compiler to treat lines containing "D" in column 1 as executable statements (ignoring the "D").

-Mnodlines

instructs the compiler not to treat lines containing "D" in column 1 as executable statements. The compiler does not ignore the "D".

-Mdollar,char

char specifies the character to which the compiler maps the dollar sign. The compiler allows the dollar sign in names.

-Mextend

instructs the compiler to accept 132-column source code; otherwise it accepts 72-column code.

-Mfixed

instructs the compiler to assume input source files are in FORTRAN 77-style fixed form format.

-Mfree

instructs the compiler to assume input source files are in Fortran 90/95 freeform format.

-Miomutex

instructs the compiler to generate critical section calls around Fortran I/O statements.

-Mnoiomutex

instructs the compiler not to generate critical section calls around Fortran I/O statements.

-Monetrip

instructs the compiler to force each DO loop to execute at least once. This option is useful for programs written for earlier versions of Fortran.

-Mnoonetrip

instructs the compiler not to force each DO loop to execute at least once.

-Msave

instructs the compiler to assume that all local variables are subject to the SAVE statement.
This may allow older Fortran programs to run, but it can greatly reduce performance.

-Mnosave

instructs the compiler not to assume that all local variables are subject to the SAVE statement.

-Mstandard

instructs the compiler to flag non-ANSI-conforming source code.

-Munixlogical

directs the compiler to treat logical values as true if the value is non-zero and false if the value is zero (UNIX F77 convention). When -⁠Munixlogical is enabled, a logical value or test that is non-zero is .TRUE., and a value or test that is zero is .FALSE.. In addition, the value of a logical expression is guaranteed to be one (1) when the result is .TRUE..

-Mnounixlogical

directs the compiler to use the VMS convention for logical values for true and false. Even values are true and odd values are false.

-Mupcase

instructs the compiler to preserve uppercase letters in identifiers.
With -⁠Mupcase, the identifiers "X" and "x" are different. Keywords must be in lower case.
This selection affects the linking process. If you compile and link the same source code using -⁠Mupcase on one occasion and -⁠Mnoupcase on another, you may get two different executables – depending on whether the source contains uppercase letters. The standard libraries are compiled using the default -⁠Mnoupcase .

-Mnoupcase

instructs the compiler to convert all identifiers to lower case.
This selection affects the linking process. If you compile and link the same source code using -⁠Mupcase on one occasion and -⁠Mnoupcase on another, you may get two different executables, depending on whether the source contains uppercase letters. The standard libraries are compiled using -⁠Mnoupcase.

This section describes the -⁠M<pgflag> options that control function inlining.

Usage:Before looking at all the options, let’s look at a couple examples. In the following example, the compiler extracts functions that have 500 or fewer statements from the source file myprog.f and saves them in the file extract.il.

$ pgfortran -Mextract=500 -o extract.il myprog.f

In the following example, the compiler inlines functions with fewer than approximately 100 statements in the source file myprog.f.

$ pgfortran -Minline=maxsize:100 myprog.f

Related options: -⁠o, -⁠Mextract

The following list provides the syntax for each -⁠M<pgflag> option that controls function inlining. Each option has a description and, if appropriate, a list of any related options.

- M[no]autoinline[=option[,option,...]]

instructs the compiler to inline [not to inline] a C/C++ function at -⁠O2, where the option can be any of these:

maxsize:n

instructs the compiler not to inline functions of size > n. The default size is 100.

totalsize:n

instructs the compiler to stop inlining when the size equals n. The default size is 800.

-Mextract[=option[,option,...]]

Extracts functions from the file indicated on the command line and creates or appends to the specified extract directory where option can be any of the following:

name:func

instructs the extractor to extract function func from the file.

size:number

instructs the extractor to extract functions with number or fewer statements from the file.

lib:filename.ext

instructs the extractor to use directory filename.ext as the extract directory, which is required to save and re-use inline libraries.

If you specify both name and size, the compiler extracts functions that match func, or that have number or fewer statements. For examples of extracting functions, refer to the ‘Using Function Inlining’ section of the PGI Visual Fortran Compiler User's Guide.

-Minline[=option[,option,...]]

instructs the compiler to pass options to the function inliner, where the option can be any of the following:

except:func

Inlines all eligible functions except func, a function in the source text. You can use a comma-separated list to specify multiple functions.

[name:]func

Inlines all functions in the source text whose name matches func. You can use a comma-separated list to specify multiple functions.

The function name should be a non-numeric string that does not contain a period. You can also use a name: prefix followed by the function name. If name: is specified, what follows is always the name of a function.

[maxsize:]number

A numeric option is assumed to be a size. Functions of size number or less are inlined. If both number and function are specified, then functions matching the given name(s) or meeting the size requirements are inlined.

The size number need not exactly equal the number of statements in a selected function; the size parameter is merely a rough guage.

[no]reshape

instructs the inliner to allow [disallow] inlining in Fortran even when array shapes do not match. The default is -⁠Minline=noreshape, except with -⁠Mconcur or -⁠mp, where the default is -⁠Minline=reshape,=reshape.

smallsize:number

Always inline functions of size smaller than number regardless of other size limits.

totalsize:number

Stop inlining in a function when the function's total inlined size reaches the number specified.

[lib:]filename.ext

instructs the inliner to inline the functions within the library file filename.ext. The compiler assumes that a filename.ext option containing a period is a library file.

Tip: Create the library file using the -⁠Mextract option. You can also use a lib: prefix followed by the library name.

• If lib: is specified, no period is necessary in the library name. Functions from the specified library are inlined.
• If no library is specified, functions are extracted from a temporary library created during an extract prepass.

If you specify both func and number, the compiler inlines functions that match the function name or have number or fewer statements.

Inlining can be disabled with -⁠Mnoinline.

To set this option in PVF, use the Fortran | Optimization | Inlining property, described in ‘Inlining’

For examples of inlining functions, refer to ‘Using Function Inlining’ in the PGI Compiler User’s Guide.

This section describes the -⁠M<pgflag> options that control optimization.

Default: Before looking at all the options, let's look at the defaults. For arguments that you do not specify, the default optimization control options are as follows:

Usage: In this example, the compiler invokes the vectorizer with use of packed SSE instructions enabled.

>$ pgfortran -Mvect=sse -Mcache_align myprog.f

Related options:-⁠g, -⁠O

The following list provides the syntax for each -⁠M<pgflag> option that controls optimization. Each option has a description and, if appropriate, a list of any related options.

-Mcache_align

Align unconstrained objects of length greater than or equal to 16 bytes on cache-line boundaries. An unconstrained object is a data object that is not a member of an aggregate structure or common block. This option does not affect the alignment of allocatable or automatic arrays.
To effect cache-line alignment of stack-based local variables, the main program or function must be compiled with -⁠Mcache_align.

-Mconcur[=option [,option,...]]

Instructs the compiler to enable auto-concurrentization of loops. If -⁠Mconcur is specified, multiple processors will be used to execute loops that the compiler determines to be parallelizable.
option is one of the following:

allcores

Instructs the compiler to use all available cores. Use this option at link time.

[no]altcode:n

Instructs the parallelizer to generate alternate serial code for parallelized loops.

• If altcode is specified without arguments, the parallelizer determines an appropriate cutoff length and generates serial code to be executed whenever the loop count is less than or equal to that length.
• If altcode:n is specified, the serial altcode is executed whenever the loop count is less than or equal to n.
• If noaltcode is specified, the parallelized version of the loop is always executed regardless of the loop count.

cncall

Indicates that calls in parallel loops are safe to parallelize.
Loops containing calls are candidates for parallelization. Also, no minimum loop count threshold must be satisfied before parallelization will occur, and last values of scalars are assumed to be safe.

[no]innermost

Instructs the parallelizer to enable parallelization of innermost loops. The default is to not parallelize innermost loops, since it is usually not profitable on dual-core processors.

noassoc

Instructs the parallelizer to disable parallelization of loops with reductions.

When linking, the -⁠Mconcur switch must be specified or unresolved references result. The NCPUS environment variable controls how many processors or cores are used to execute parallelized loops.
To set this option in PVF, use the Fortran | Optimization | Auto-Parallelization property, described in ‘Auto-Parallelization’.

Note: This option applies only on shared-memory multi-processor (SMP) or multicore processor-based systems.

-Mcray[=option[,option,...]]

Force Cray Fortran (CF77) compatibility with respect to the listed options. Possible values of option include:

pointer

for purposes of optimization, it is assumed that pointer-based variables do not overlay the storage of any other variable.

-Mdepchk

instructs the compiler to assume unresolved data dependencies actually conflict.

-Mnodepchk

Instructs the compiler to assume potential data dependencies do not conflict. However, if data dependencies exist, this option can produce incorrect code.

-Mdse

Enables a dead store elimination phase that is useful for programs that rely on extensive use of inline function calls for performance. This is disabled by default.

-Mnodse

Disables the dead store elimination phase. This is the default.

-M[no]fpapprox[=option]

Perform certain floating point operations using low-precision approximation.
-⁠Mnofpapprox specifies not to use low-precision fp approximation operations.
By default -⁠Mfpapprox is not used.
If -⁠Mfpapprox is used without suboptions, it defaults to use approximate div, sqrt, and rsqrt. The available suboptions are these:

div

Approximate floating point division

sqrt

Approximate floating point square root

rsqrt

Approximate floating point reciprocal square root

-M[no]fpmisalign

Instructs the compiler to allow (not allow) vector arithmetic instructions with memory operands that are not aligned on 16-byte boundaries. The default is -⁠Mnofpmisalign on all processors.

-M[no]fprelaxed[=option]

Instructs the compiler to use [not use] relaxed precision in the calculation of some intrinsic functions. Can result in improved performance at the expense of numerical accuracy.
To set this option in PVF, use the Fortran | Floating Point Options | Floating Point Consistency property. For more information on this property, refer to ‘Floating Point Consistency’.
The possible values for option are:

div

Perform divide using relaxed precision.

intrinsic

Enables use of relaxed precision intrinsics.

noorder

Do not allow expression reordering or factoring.

order

Allow expression reordering, including factoring.

recip

Perform reciprocal using relaxed precision.

rsqrt

Perform reciprocal square root (1/sqrt) using relaxed precision.

sqrt

Perform square root with relaxed precision.

With no options, -⁠Mfprelaxed generates relaxed precision code for those operations that generate a significant performance improvement, depending on the target processor.
The default is -⁠Mnofprelaxed which instructs the compiler to not use relaxed precision in the calculation of intrinsic functions.

-Mi4

instructs the compiler to treat INTEGER variables as INTEGER*4.

-Mlre[=array | assoc | noassoc]

Enables loop-carried redundancy elimination, an optimization that can reduce the number of arithmetic operations and memory references in loops. The available suboptions are:

array

treat individual array element references as candidates for possible loop-carried redundancy elimination. The default is to eliminate only redundant expressions involving two or more operands.

assoc

allow expression re-association. Specifying this suboption can increase opportunities for loop-carried redundancy elimination but may alter numerical results.

noassoc

disallow expression re-association.

-Mnolre

Disable loop-carried redundancy elimination.

-Mnoframe

Eliminate operations that set up a true stack frame pointer for every function. With this option enabled, you cannot perform a traceback on the generated code and you cannot access local variables.
To set this option in PVF, use the Fortran | Optimization | Use Frame Pointer property, described in ‘Use Frame Pointer’

-Mnoi4

instructs the compiler to treat INTEGER variables as INTEGER*2.

-Mpre

Enables partial redundancy elimination.

-Mprefetch[=option [,option...]]

enables generation of prefetch instructions on processors where they are supported. Possible values for option include:

d:m

set the fetch-ahead distance for prefetch instructions to m cache lines.

n:p

set the maximum number of prefetch instructions to generate for a given loop to p.

nta

use the prefetch instruction.

plain

use the prefetch instruction (default).

t0

use the prefetcht0 instruction.

w

use the AMD-specific prefetchw instruction.

-Mnoprefetch

Disables generation of prefetch instructions.

-M[no]propcond

Enables or disables constant propagation from assertions derived from equality conditionals.
The default is enabled.

-Mr8

The compiler promotes REAL variables and constants to DOUBLE PRECISION variables and constants, respectively. DOUBLE PRECISION elements are 8 bytes in length.

-Mnor8

The compiler does not promote REAL variables and constants to DOUBLE PRECISION. REAL variables will be single precision (4 bytes in length).

-Mr8intrinsics

The compiler treats the intrinsics CMPLX and REAL as DCMPLX and DBLE, respectively.

-Mnor8intrinsics

The compiler does not promote the intrinsics CMPLX and REAL to DCMPLX and DBLE, respectively.

-Mscalarsse

Use SSE/SSE2 instructions to perform scalar floating-point arithmetic.

-Mnoscalarsse

Do not use SSE/SSE2 instructions to perform scalar floating-point arithmetic; use x87 instructions instead (on applicable platforms only).

-Msmart

instructs the compiler driver to invoke a post-pass assembly optimization utility.

-Mnosmart

instructs the compiler not to invoke an AMD64-specific post-pass assembly optimization utility.

-Munroll[=option [,option...]]

invokes the loop unroller to execute multiple instances of the loop during each iteration. This also sets the optimization level to 2 if the level is set to less than 2, or if no -⁠O or -⁠g options are supplied. The option is one of the following:

c:m

instructs the compiler to completely unroll loops with a constant loop count less than or equal to m, a supplied constant. If this value is not supplied, the m count is set to 1.

m:<n>

instructs the compiler to unroll multi-block loops n times. This option is useful for loops that have conditional statements. If n is not supplied, then the default value is 1. The default setting is not to enable -⁠Munroll=m.

n:<n>

instructs the compiler to unroll single-block loops n times, a loop that is not completely unrolled, or has a non-constant loop count. If n is not supplied, the unroller computes the number of times a candidate loop is unrolled.

To set this option in PVF, use the Fortran | Optimization | Loop Unroll Count property, described in ‘Loop Unroll Count’

-Mnounroll

instructs the compiler not to unroll loops.

-M[no]vect[=option [,option,...]]

enable [disable] the code vectorizer, where option is one of the following:

altcode

Instructs the vectorizer to generate alternate code (altcode) for vectorized loops when appropriate. For each vectorized loop the compiler decides whether to generate altcode and what type or types to generate, which may be any or all of: altcode without iteration peeling, altcode with non-temporal stores and other data cache optimizations, and altcode based on array alignments calculated dynamically at runtime. The compiler also determines suitable loop count and array alignment conditionals for executing the altcode. This option is enabled by default.

noaltcode

Instructs the vectorizer to disable alternate code generation for vectorized loops.

assoc

Instructs the vectorizer to enable certain associativity conversions that can change the results of a computation due to roundoff error. A typical optimization is to change an arithmetic operation to an arithmetic operation that is mathematically correct, but can be computationally different, due to round-off error.

noassoc

Instructs the vectorizer to disable associativity conversions.

cachesize:n

Instructs the vectorizer, when performing cache tiling optimizations, to assume a cache size of n. The default is set per processor type, either using the -⁠tp switch or auto-detected from the host computer.

[no]gather

Instructs the vectorizer to vectorize loops containing indirect array references, such as this one:

sum = 0.d0
do k=d(j),d(j+1)-1
     sum = sum + a(k)*b(c(k))
enddo

The default is gather.

partial

Instructs the vectorizer to enable partial loop vectorization through innermost loop distribution.

prefetch

Instructs the vectorizer to search for vectorizable loops and, wherever possible, make use of prefetch instructions.

[no]short

Instructs the vectorizer to enable [disable] short vector operations. -Mvect=short enables generation of packed SIMD instructions for short vector operations that arise from scalar code outside of loops or within the body of a loop iteration.

[no]sizelimit

Instructs the vectorizer to generate vector code for all loops where possible regardless of the number of statements in the loop. This overrides a heuristic in the vectorizer that ordinarily prevents vectorization of loops with a number of statements that exceeds a certain threshold. The default is nosizelimit.

smallvect[:n]

Instructs the vectorizer to assume that the maximum vector length is less than or equal to n. The vectorizer uses this information to eliminate generation of the stripmine loop for vectorized loops wherever possible. If the size n is omitted, the default is 100.

Note: No space is allowed on either side of the colon (:).

[no]sse

Instructs the vectorizer to search for vectorizable loops and, wherever possible, make use of SSE, SSE2, and prefetch instructions. The default is nosse.

[no]uniform

Instructs the vectorizer to perform the same optimizations in the vectorized and residual loops.

Note: This option may affect the performance of the residual loop.

To set this option in PVF, use the Fortran | Optimization Vectorization property, described in ‘Vectorization’

-Mnovect

instructs the compiler not to perform vectorization. You can use this option to override a previous instance of -⁠Mvect on the command-line, in particular for cases in which -⁠Mvect is included in an aggregate option such as -⁠fastsse.

-Mvect=[option]

instructs the compiler to enable loop vectorization, where option is one of the following:

partial

Enable partial loop vectorization through innermost loop distribution.

[no]short

Enable [disable] short vector operations. Enables [disables] generation of packed SIMD instructions for short vector operations that arise from scalar code outside of loops or within the body of a loop iteration.

simd[:{128|256}]

Specifies to vectorize using SIMD instructions and data, either 128 bits or 256 bits wide, on processors where there is a choice.

tile

Enable tiling/blocking over multiple nested loops for more efficient cache utilization.

-Mnovintr

instructs the compiler not to perform idiom recognition or introduce calls to hand-optimized vector functions.

This section describes the -⁠M<pgflag> options that do not easily fit into one of the other categories of -⁠M<pgflag> options.

Default: Before looking at all the options, let’s look at the defaults. For arguments that you do not specify, the default miscellaneous options are as follows:

Related options: -⁠m, -⁠S, -⁠V, -⁠v

Usage: In the following example, the compiler includes Fortran source code with the assembly code.

 $ pgfortran -Manno -S myprog.f

In the following example, the assembler does not delete the assembly file myprog.s after the assembly pass.

 $ pgfortran -Mkeepasm myprog.f

In the following example, the compiler displays information about inlined functions with fewer than approximately 20 source lines in the source file myprog.f.

 $ pgfortran -Minfo=inline -Minline=20 myprog.f

In the following example, the compiler creates the listing file myprog.lst.

 $ pgfortran -Mlist myprog.f

In the following example, array bounds checking is enabled.

 $ pgfortran -Mbounds myprog.f

The following list provides the syntax for each miscellaneous -⁠M<pgflag> option. Each option has a description and, if appropriate, a list of any related options.

-Manno

annotate the generated assembly code with source code. Implies -⁠Mkeepasm.
To set this option in PVF, use the Fortran | Output | Annotated ASM Listing property, described in ‘Annotate Assembly’.

-Mbounds

enables array bounds checking.

• If an array is an assumed size array, the bounds checking only applies to the lower bound.
• If an array bounds violation occurs during execution, an error message describing the error is printed and the program terminates. The text of the error message includes the name of the array, the location where the error occurred (the source file and the line number in the source), and information about the out of bounds subscript (its value, its lower and upper bounds, and its dimension).

The following is a sample error message:

PGFTN-F-Subscript out of range for array a (a.f: 2) 
subscript=3, lower bound=1, upper bound=2, dimension=2

-Mnobounds

disables array bounds checking.

-Mbyteswapio

swap byte-order from big-endian to little-endian or vice versa upon input/output of Fortran unformatted data files.

-Mchkptr

instructs the compiler to check for pointers that are dereferenced while initialized to NULL.

-Mchkstk

instructs the compiler to check the stack for available space in the prologue of a function and before the start of a parallel region. Prints a warning message and aborts the program gracefully if stack space is insufficient.
This option is useful when many local and private variables are declared in an OpenMP program.
If the user also sets the PGI_STACK_USAGE environment variable to any value, then the program displays the stack space allocated and used after the program exits. For example, you might see something similar to the following message:

thread 0 stack: max 8180KB, used 48KB

This message indicates that the program used 48KB of a 8180KB allocated stack. This information is useful when you want to explicitly set a reserved and committed stack size for your programs, such as using the -⁠stack option on Windows.
For more information on the PGI_STACK_USAGE, refer to ‘PGI_STACK_USAGE’ in the PGI Compiler User’s Guide.

-Mcpp[=option [,option,...]]

run the PGI cpp-like preprocessor without execution of any subsequent compilation steps. This option is useful for generating dependence information to be included in makefiles.

Note: Only one of the m, md, mm or mmd options can be present; if multiple of these options are listed, the last one listed is accepted and the others are ignored.

The option is one or more of the following:

m

print makefile dependencies to stdout.

md

print makefile dependencies to filename.d, where filename is the root name of the input file being processed, ignoring system include files.

mm

print makefile dependencies to stdout, ignoring system include files.

mmd

print makefile dependencies to filename.d, where filename is the root name of the input file being processed, ignoring system include files.

[no]comment

do [do not] retain comments in output.

[suffix:]<suff>

use <suff> as the suffix of the output file containing makefile dependencies.

-Mdll

This Windows-only flag has been deprecated. Refer to -⁠Bdynamic. This flag was used to link with the DLL versions of the runtime libraries, and it was required when linking with any DLL built by any PGI compilers. This option implied -⁠D_DLL, which defines the preprocessor symbol _DLL.

-Mgccbug[s]

instructs the compiler to match the behavior of certain gcc bugs.

-Miface[=option]

adjusts the calling conventions for Fortran, where option is one of the following:

cref

uses CREF calling conventions, no trailing underscores.

mixed_str_len_arg

places the lengths of character arguments immediately after their corresponding argument. Has affect only with the CREF calling convention.

nomixed_str_len_arg

places the lengths of character arguments at the end of the argument list. Has affect only with the CREF calling convention.

-Minfo[=option [,option,...]]

instructs the compiler to produce information on standard error, where option is one of the following:

all

instructs the compiler to produce all available -⁠Minfo information. Implies a number of suboptions:

-Mneginfo=accel,inline,ipa,loop,lre,mp,opt,par,vect 

accel

instructs the compiler to enable accelerator information.

ccff

instructs the compiler to append common compiler feedback format information, such as optimization information, to the object file.

ftn

instructs the compiler to enable Fortran-specific information.

inline

instructs the compiler to display information about extracted or inlined functions. This option is not useful without either the -⁠Mextract or -⁠Minline option.

intensity

instructs the compiler to provide informational messages about the intensity of the loop. Specify <n> to get messages on nested loops.

• For floating point loops, intensity is defined as the number of floating point operations divided by the number of floating point loads and stores.
• For integer loops, the loop intensity is defined as the total number of integer arithmetic operations, which may include updates of loop counts and addresses, divided by the total number of integer loads and stores.
• By default, the messages just apply to innermost loops.

ipa

instructs the compiler to display information about interprocedural optimizations.

loop

instructs the compiler to display information about loops, such as information on vectorization.

lre

instructs the compiler to enable LRE, loop-carried redundancy elimination, information.

mp

instructs the compiler to display information about parallelization.

opt

instructs the compiler to display information about optimization.

par

instructs the compiler to enable parallelizer information.

pfo

instructs the compiler to enable profile feedback information.

time

instructs the compiler to display compilation statistics.

unroll

instructs the compiler to display information about loop unrolling.

vect

instructs the compiler to enable vectorizer information.

-Minform=level

instructs the compiler to display error messages at the specified and higher levels, where level is one of the following:

fatal

instructs the compiler to display fatal error messages.

[no]file

instructs the compiler to print or not print source file names as they are compiled. The default is to print the names: -⁠Minform=file.

inform

instructs the compiler to display all error messages (inform, warn, severe and fatal).

severe

instructs the compiler to display severe and fatal error messages.

warn

instructs the compiler to display warning, severe and fatal error messages.

To set this option in PVF, use the Fortran | Diagnostics | Warning Level property, described in ‘Warning Level’.

-Minstrumentation=option

specifies the level of instrumentation calls generated. This option implies -Minfo=ccff, -Mframe.
option is one of the following:

level

specifies the level of instrumentation calls generated.

function (default)

generates instrumentation calls for entry and exit to functions.
Just after function entry and just before function exit, the following profiling functions are called with the address of the current function and its call site. (linux86-64 only).

void __cyg_profile_func_enter (void *this_fn, void *call_site);
void __cyg_profile_func_exit (void *this_fn, void *call_site);

In these calls, the first argument is the address of the start of the current function.

To set this option in PVF, use the Fortran | Diagnostics | Warning Level property, described in ‘Warning Level’.

-Mkeepasm

instructs the compiler to keep the assembly file as compilation continues. Normally, the assembler deletes this file when it is finished. The assembly file has the same filename as the source file, but with a .s extension.
To set this option in PVF, use the Fortran | Output | Assembler Output property, described in ‘Generate Assembly’.

-M list

instructs the compiler to create a listing file. The listing file is filename.lst, where the name of the source file is filename.f.

-Mmakedll

generate a dynamic link library (DLL).

-Mmakeimplib

generate an import library for a DLL without creating the DLL. When used without -def:deffile, passes the switch -def to the librarian without a deffile.

-Mnames=lowercase|uppercase

specifies the case for the names of Fortran externals.

• lowercase - Use lowercase for Fortran externals.
• uppercase - Use uppercase for Fortran externals.

-Mneginfo[=option [,option,...]]

instructs the compiler to produce information on standard error, where option is one of the following:

all

instructs the compiler to produce all available information on why various optimizations are not performed.

accel

instructs the compiler to enable accelerator information.

ccff

instructs the compiler to append information, such as optimization information, to the object file.

concur

instructs the compiler to produce all available information on why loops are not automatically parallelized. In particular, if a loop is not parallelized due to potential data dependence, the variable(s) that cause the potential dependence are listed in the messages that you see when using the option -⁠Mneginfo.

ftn

instructs the compiler to enable Fortran-specific information.

inline

instructs the compiler to display information about extracted or inlined functions. This option is not useful without either the -⁠Mextract or -⁠Minline option.

ipa

instructs the compiler to display information about interprocedural optimizations.

loop

instructs the compiler to display information about loops, such as information on vectorization.

lre

instructs the compiler to enable LRE, loop-carried redundancy elimination, information.

mp

instructs the compiler to display information about parallelization.

opt

instructs the compiler to display information about optimization.

par

instructs the compiler to enable parallelizer information.

pfo

instructs the compiler to enable profile feedback information.

vect

instructs the compiler to enable vectorizer information.

-Mnolist

the compiler does not create a listing file. This is the default.

-Mnoopenmp

when used in combination with the -⁠mp option, the compiler ignores OpenMP parallelization directives or pragmas, but still processes SGI-style parallelization directives or pragmas.

-Mnosgimp

when used in combination with the -⁠mp option, the compiler ignores SGI-style parallelization directives, but still processes OpenMP parallelization directives or pragmas.

-Mnopgdllmain

(Windows only) do not link the module containing the default DllMain() into the DLL. This flag applies to building DLLs with the PGFORTRAN compilers. If you want to replace the default DllMain() routine with a custom DllMain(), use this flag and add the object containing the custom DllMain() to the link line. The latest version of the default DllMain() used by PGFORTRAN is included in the Release Notes for each release. The PGFORTRAN-specific code in this routine must be incorporated into the custom version of DllMain() to ensure the appropriate function of your DLL.

-Mpreprocess

instruct the compiler to perform cpp-like preprocessing on assembly and Fortran input source files.
To set this option in PVF, use the Fortran | Preprocessor | Preprocess Source File property, described in ‘Preprocessor Definitions’.

-Mwritable_strings

stores string constants in the writable data segment.

Note: Options -⁠Xs and -⁠Xst include -⁠Mwritable_strings.

This directive has no corresponding command-line option. The compiler determines whether the last values for loop iteration control variables and promoted scalars need to be computed. In certain cases, the compiler must assume that the last values of these variables are needed and therefore computes their last values. The directive nolstval directs the compiler not to compute the last values for those cases.

The syntax for the IGNORE_TKR directive is this:

!DIR$ IGNORE_TKR [ [(<letter>) <dummy_arg>] ... ]

<letter>

is one or any combination of the following:

T – type

K – kind

R – rank

For example, KR indicates to ignore both kind and rank rules and TKR indicates to ignore the type, kind, and rank arguments.

<dummy_arg>

if specified, indicates the dummy argument for which TKR rules should be ignored. If not specified, TKR rules are ignored for all dummy arguments in the procedure that contains the directive.

The following rules apply to this directive:

• IGNORE_TKR must not specify dummy arguments that are allocatable, Fortran 90 pointers, or assumed-shape arrays.
• IGNORE_TKR may appear in the body of an interface block or in the body of a module procedure, and may specify dummy argument names only.
• IGNORE_TKR may appear before or after the declarations of the dummy arguments it specifies.
• If dummy argument names are specified, IGNORE_TKR applies only to those particular dummy arguments.
• If no dummy argument names are specified, IGNORE_TKR applies to all dummy arguments except those that are allocatable objects, Fortran 90 pointers, or assumed-shape arrays.

Consider this subroutine fragment:

subroutine example(A,B,C,D)
!DIR$ IGNORE_TKR A, (R) B, (TK) C, (K) D

Table 12 indicates which rules are ignored for which dummy arguments in the preceding sample subroutine fragment:

Notice that no letters were specified for A, so all type, kind, and rank rules are ignored.

This directive specifies an alternative name with which to resolve a routine.

The syntax for the ALIAS directive is either of the following:

!DEC$ ALIAS routine_name , external_name
!DEC$ ALIAS routine_name : external_name

In this syntax, external_name is used as the external name for the specified routine_name.

If external_name is an identifier name, the name (in uppercase) is used as the external name for the specified routine_name. If external_name is a character constant, it is used as-is; the string is not changed to uppercase, nor are blanks removed.

You can also supply an alias for a routine using the ATTRIBUTES directive, described in the next section:

!DEC$ ATTIRIBUTES ALIAS : 'alias_name' :: routine_name

This directive specifies an alternative name with which to resolve a routine, as illustrated in the following code fragment that provides external names for three routines. In this fragment, the external name for sub1 is name1, for sub2 is name2, and for sub3 is name3.

subroutine sub
!DEC$ alias sub1 , 'name1'
!DEC$ alias sub2 : 'name2'
!DEC$ attributes alias : 'name3' :: sub3 

This directive lets you specify properties for data objects and procedures.

The syntax for the ATTRIBUTES directive is this:

!DEC$ ATTRIBUTES <list>

where <list> is one of the following:

ALIAS : 'alias_name' :: routine_name

Specifies an alternative name with which to resolve routine_name.

C :: routine_name

Specifies that the routine routine_name will have its arguments passed by value. When a routine marked C is called, arguments, except arrays, are sent by value. For characters, only the first character is passed. The standard Fortran calling convention is pass by reference.

DLLEXPORT :: name

Specifies that name is being exported from a DLL.

DLLIMPORT :: name

Specifies that name is being imported from a DLL.

NOMIXED_STR_LEN_ARG

Specifies that hidden lengths are placed in sequential order at the end of the list.

Note: This attribute only applies to routines that are compiled with -Miface=cref or that use the default Windows calling conventions.

REFERENCE :: name

Specifies that the argument name is being passed by reference. Often this attribute is used in conjunction with STDCALL, where STDCALL refers to an entire routine; then individual arguments are modified with REFERENCE.

STDCALL :: routine_name

Specifies that routine routine_name will have its arguments passed by value. When a routine marked STDCALL is called, arguments (except arrays and characters) will be sent by value. The standard Fortran calling convention is pass by reference.

VALUE :: name

Specifies that the argument 'name' is being passed by value.

The DECORATE directive specifies that the name specified in the ALIAS directive should have the prefix and postfix decorations performed on it that are associated with the calling conventions that are in effect. These declarations are the same ones performed on the name when ALIAS is not specified.

The syntax for the DECORATE directive is this:

!DEC$ DECORATE

This directive is front-end based, and tells the compiler at what point within a loop to split into two loops.

The syntax for the DISTRIBUTE directive is either of the following:

!DEC$ DISTRIBUTE POINT
!DEC$ DISTRIBUTEPOINT

subroutine dist(a,b,n)
    integer i
    integer n
    integer a(*)
    integer b(*)
    do i = 1,n
        a(i) = a(i)+2
!DEC$ DISTRIBUTE POINT
        b(i) = b(i)*4
    enddo
end subroutine 

This section describes the standard function calling sequence, including the stack frame, register usage, and parameter passing.

Sections A3.4.1 through A3.4.4 of the AMD64 Software Conventions for Win64 define the Fortran supplement. The register usage conventions set forth in that document remain the same for Fortran.

	INTEGER I, J
	COMPLEX C 
	DOUBLE COMPLEX CD
	DOUBLE PRECISION D
	COMMON /COM/ i, j, c, cd, d

	extern struct {
 int i;
 int j;
 struct {float real, imag;} c;
 struct {double real, imag;} cd;
 double d; 
	} com_; 

	extern "C" struct {
 int i;
 int j;
 struct {float real, imag;} c;
 struct {double real, imag;} cd;
 double d;
	} com_;

CHARACTER*(*) FUNCTION CHF(C1, I)
CHARACTER*(*) C1
INTEGER I
	END

	extern void chf_();
char tmp[10];
char c1[9];
int i;
chf_(tmp, 10, c1, &i, 9);

Use this property to specify a relative path to the output file directory. This directory is where the project’s output files are built.

Use this property to specify a relative path to the intermediate file directory. This directory is where the intermediate files (i.e., object files) are created when the project is built.

Use this property to specify which files in the intermediate directory should be deleted when the project is cleaned or before it is rebuilt. This property uses a semi-colon-delimited wildcard specification for the files.

Use this property to change the output type that the project produces.

When you create a project, you specify the type of output that the project produces: executable, static library, or dynamic library. If you want to change the output type, use this property to do so.

Use this property to specify the build log file that is produced when the project is built.

Use this property to specify the level of detail to be included in the build log file.

Use this property to specify the application to execute when you select Start Debugging or Start Without Debugging from the Debug menu.

• If the Startup Project in your solution is a PVF project that builds an executable, there is probably no need to change this property.
• If the Startup Project in your solution is a PVF project that builds a DLL or static library, you must use the Command property to specify an application to execute when you run (with or without debugging).

Use this property to pass command line arguments to the application when it is run or debugged.

Use this property to specify any environment variables to set for the application when it runs. One common use of this property is to augment the PATH environment variable. For example, if the application requires DLLs to run but the general environment is not set to find these, the path to these DLLs could be added to the PATH environment variable.

For more information on PATH, refer to the PGI Visual Fortran Compiler User's Guide.

If the Merge Environment property is set to Yes, then the contents of the Environment property are merged with the existing environment when the application is run or debugged.

Use this property to merge the environment variables in the Environment property with the existing environment when the application is run or debugged. To do this, set the Merge Environment property to Yes.

Use this property to generate accelerator profiling information at runtime. To do this, set the Accelerator Profiling property to Yes.

Setting this property to Yes sets the PGI_ACC_TIME environment variable to 1.

Use this property to enable MPI debugging and select local MPI debugging.

The value selected for this property determines which properties are displayed following it on the Debugging property page.

• When MPI Debugging is set to Disabled, the application is run or debugged in serial mode.
• When MPI Debugging is set to Local, the application is run or debugged using mpiexec. All processes launched are local to the system on which the application is run.

Use this property to determine whether to display the compiler’s startup banner during compilation.

Changing the property to Yes adds the -⁠V switch to the compilation line, which causes the compiler to display the startup banner during compilation.

For more information on -⁠V, refer to -V[release_number].

Use this property to add one or more directories to the compiler’s include path.

For every path that is added to this property, PVF adds -⁠I<path> to the compilation line.

There are two ways to add directories to this property:

• Type the information directly into the property page box.

  Use a semi-colon (‘;’) to separate each directory.

• Click the ellipsis (‘...’) button in the property page box to open the Additional Include Directories dialog box.

  Enter each directory on its own line in this box. Do not use semi-colons to separate directories; the semi-colons are added automatically when the box is closed.

Use this property to specify the location of module (.mod) files.

For every directory that is added to this property, PVF adds -⁠module <dir> to the compilation line, causing the compiler to search each listed directory for modules during compilation.

There are two ways to add directories to this property:

• Type the information directly into the property page box.

  Use a semi-colon (‘;’) to separate each path.

• Click the ellipsis (‘...’) button in the property page box to open the Module Path dialog box.

  Enter each directory on its own line in this box. Do not use semi-colons to separate entries; the semi-colons are added automatically when the box is closed.

Use of this property depends on whether it is being applied to a file or a project:

• File level: Use this property to set the name of the object file. Setting the name adds the -⁠o switch to the compilation line.

  For more information on -⁠o, refer to -o.

• Project level: Use this property to set the location of the object files created by a build.

  To change the default location for the object files, specify a different directory name for this property.

  Note: You must append a backslash (\) to the directory path or the value of this property will be interpreted as a file.

Use this property to specify whether the compiler should generate debug information and if so, in what format.

• The richest debugging experience is obtained when this option is set to "Full Debug Information (-g).’
• If you are debugging a project built with optimizations, you may want to select "Full Debug Information with Full Optimization (-gopt)." This selection prevents the generation of debug information from affecting optimizations.

For more information on -⁠g, refer to -g. For more information on -⁠gopt, refer to -gopt.

Use this property to select the overall code optimization.

This property can be set to one of the following values:

• No Optimization - the default value for Debug configurations.
• Maximize Speed - the default value for Release Configurations.
• Maximize Speed Across the Whole Program

Use this property to select the overall code optimization.

This property can be set to one of the following values:

• No Optimization - the default value for Debug configurations.
• Maximize Speed - the default value for Release Configurations.
• Maximize Speed Across the Whole Program

Use this property to set the compiler’s global optimization level.

Setting this property adds one of the -⁠O options to the compilation line.

For more information on -⁠O, refer to -O<level>.

Use this property to specify the type of vectorization to perform.

The PVF compilers use the -⁠Mvect options to vectorize code that is vectorizable. Select the appropriate vectorization from these options:

• Default: Accepts the default vectorization.
• Enable Vectorization: Enables vectorization by adding the -⁠Mvect switch to the PVF compilation and link lines.
• Vectorize using SSE instructions: Enables vectorization using SSE instructions by adding the -⁠Mvect=sse switch to the PVF compilation line.
• Vectorize using SIMD instructions: Enables vectorization using SIMD instructions and data, by adding the -⁠Mvect=simd switch to the PVF compilation line.
• Vectorize using 128-bit SIMD instructions: Enables vectorization using SIMD 128-bit instructions and data, by adding the -⁠Mvect=simd:128 switch to the PVF compilation line.
• Vectorize using 256-bit SIMD instructions: Enables vectorization using SIMD 256-bit instructions and data, by adding the -⁠Mvect=simd:256 switch to the PVF compilation line.

For more information on -⁠Mvect, refer to Optimization Controls.

Use this property to enable inlining of certain subprograms.

Setting this property to Yes adds the -⁠Minline switch to the compilation command line.

For more information on -⁠Minline, refer to -Minline[=option[,option,...]].

Use this property to specify whether to generate code that uses a frame pointer.

Setting this property to Yes adds the -⁠Mframe switch to the compilation command line and PVF compilers generate code that uses a frame pointer.

Setting this property to No, the default, adds the -⁠Mnoframe switch to the compilation command line and PVF compilers generate code that does not use frame pointers.

For more information on -⁠Mframe, refer to Optimization Controls.

Use this property to select the appropriate value for unrolling.

Loop unrolling is a common optimization. This property allows you to specify unrolling by two or four. Using this option adds the -⁠Munroll option to the compilation line.

For more information on -⁠Munroll, refer to Optimization Controls.

Use this property to auto-parallelize code that is parallelizable. Using this option adds the -⁠Mconcur option to the compilation line.

For more information on -⁠Mconcur, refer to Optimization Controls.

Use this property to specify whether the compiler should preprocess source files.

Setting this property to Yes adds the -⁠Mpreprocess switch to the compilation command line.

For more information on -⁠Mpreprocess, refer to Miscellaneous Controls.

Use this property to add one or more directories to the compiler’s include path.

For every path that is added to this property, PVF adds -⁠I<path> to the compilation line.

There are two ways to add directories to this property:

• Type the information directly into the property page box.

  Use a semi-colon (‘;’) to separate each directory.

• Click the ellipsis (‘...’) button in the property page box to open the Additional Include Directories dialog box.

  Enter each directory on its own line in this box. Do not use semi-colons to separate directories; the semi-colons are added automatically when the box is closed.

For more information on -⁠I<path>, refer to -I.

Use this property to specify whether the preprocessor should ignore the standard include path.

Setting this property to Yes adds the -⁠Mnostdinc switch to the compilation command line.

For more information on -⁠Mnostdinc, refer to Environment Controls.

Use this property to add one or more preprocessor definitions to compilation.

For every definition that is added to this property, PVF adds -⁠D<definition> to the compilation line.

There are two ways to add definitions to this property:

• Type the information directly into the property page box.

  Use a semi-colon (‘;’) to separate each definition.

  For example, DEF1;DEF2=2 defines DEF1, and defines DEF2 and initializes it to 2.

• Click the ellipsis (‘...’) button in the property page box to open the Preprocessor Definitions dialog box.

  Enter each definition on its own line in this box. Do not use semi-colons to separate definitions; the semi-colons are added automatically when the box is closed.

For more information on -⁠D<definition>, refer to -D.

Use this property to undefine one or more preprocessor definitions.

For every definition that is added to this property, PVF adds -⁠U<definition> to the compilation line.

There are two ways to add definitions to this property:

• Type the information directly into the property page box.

  Use a semi-colon (‘;’) to separate each definition.

  For example, DEF1;DEF2 undefines DEF1 and DEF2.

• Click the ellipsis (‘...’) button in the property page box to open the Undefine Preprocessor Definitions dialog box.

  Enter each definition on its own line in this box. Do not use semi-colons to separate definitions; the semi-colons are added automatically when the box is closed.

For more information on -⁠U<definition>, refer to -U.

Use this property to specify the type of runtime libraries to use during linking.

Default: Depends on the project:

• For executable and static library projects: multi-threaded static libraries.

  Using this option adds the -⁠Bstatic option to the compilation line. This choice corresponds to Microsoft’s /MT compilation option.

  For more information on -⁠Bstatic, refer to -Bstatic.

• For dynamic-link library projects: multi-threaded DLL libraries.

  Using this option adds the -⁠Bdynamic option to the compilation line. This choice corresponds to Microsoft’s /MD compilation option.

  For more information on -⁠Bdynamic, refer to -Bdynamic.

Use this property to select the Fortran dialect to use during compilation.

PVF supports two Fortran language dialects: Fortran 95 and FORTRAN 77. The dialect determines which PGI compiler driver is used during compilation.

• Default: The dialect is set to Fortran 95, even for fixed-format .f files, and the pgfortran driver is used.
• Fortran 77: Use the pgf77 driver. You can select the FORTRAN 77 dialect at the project or file level.

Use this property to specify how the compilers should treat the backslash (\) character.

Default: PVF treats the backslash (\) as a regular character.

This default action is equivalent to adding the -⁠Mbackslash switch to compilation.

If you want the backslash character to be treated as an escape character, which is how C and C++ compilers handle backslashes, set this property to No.

For more information on -⁠Mbackslash, refer to Fortran Language Controls.

Use this property to extend the line length for fixed-format Fortran files to 132 characters.

Fixed-format Fortran files limit the accepted line length to 72 characters. To extend the line length for these types of files to 132 characters, set this property to Yes, which adds the -⁠Mextend switch to the PVF compilation line.

For more information on -⁠Mextend, refer to Fortran Language Controls.

Use this property to enable OpenMP 3.0 directives.

Setting this property to Yes adds the -⁠mp switch to the PVF compilation and link lines.

For more information on -⁠mp, refer to -mp.

Use this property to enable OpenACC directives.

Setting this property to Yes adds the -⁠acc switch to the PVF compilation and link lines and activates access to these additional properties:

• OpenACC Autoparallelization
• OpenACC Required
• OpenACC Routineseq
• OpenACC Wait
• OpenACC Conformance Level
• OpenACC Sync

For more information on -⁠acc, refer to -acc.

When Enable OpenACC Directives is set to Yes, use this property to control loop autoparallelization within acc parallel.

• Default: Allows the compiler to control loop autoparallelization within acc parallel. This selection adds no additional sub-options to -acc.
• Yes: Directs the compiler to enable loop autoparallelization within an OpenACC parallel region (-acc=autopar).
• No: Directs the compiler to disable loop autoparallelization within an OpenACC parallel region (-acc=noautopar).

When Enable OpenACC Directives is set to Yes, use this property to control the compiler’s behavior when it is unable to accelerate a compute region.

• Default: Use the compiler defaults for handling instances where compute regions cannot be accelerated. This selection adds no additional sub-options to -acc.
• Yes: Directs the compiler to stop compilation with an error when it cannot accelerate a compute region (-acc=required).
• No: Directs the compiler to issue warnings when it cannot accelerate a compute region; compilation does not stop but accelerator kernels are not generated (-acc=norequired).

When Enable OpenACC Directives is set to Yes, use this property to compile every routine for the device.

• Default: Uses compiler defaults handling compile every routine for the device. This selection adds no additional sub-options to -acc.
• Yes: Enables compiling every routine for the device by adding -acc=routineseq switch to the PVF compilation and link lines.
• No: Disables compiling every routine for the device by adding -acc=noroutineseq switch to the PVF compilation and link lines.

When Enable OpenACC Directives is set to Yes, use this property to wait for each device kernel to finish.

• Default: Uses compiler defaults handling wait for each device kernel to finish. This selection adds no additional sub-options to -acc.
• Yes: Enables wait for each device kernel to finish by adding -acc=wait switch to the PVF compilation and link lines.
• No: Disables wait for each device kernel to finish by adding -acc=nowait switch to the PVF compilation and link lines.

When Enable OpenACC Directives is set to Yes, use this property to leverage the compiler’s detection of extensions to standard OpenACC directives.

• Default: When non-OpenACC accelerator directives are found, they are ignored..
• Strict: Add -acc=strict to the PVF compilation and link lines. The compiler emits a warning when a non-OpenACC accelerator directive is found.
• Very Strict: Add -acc=strict to the PVF compilation and link lines. The compiler stops with an error when a non-OpenACC accelerator directive is found.

When Enable OpenACC Directives is set to Yes, use this property to ignore async clauses.

Setting this property to Yes adds the -acc=sync switch to the PVF compilation and link lines.

Use this property to enable compilation and linking using the Microsoft MPI headers and libraries.

Setting this property to Microsoft MPI adds the -Mmpi=msmpi switch to the PVF compilation and link lines.

Use this property to enable CUDA Fortran.

Setting this property to Yes adds the -⁠Mcuda switch to the PVF compilation and link lines and activates access to these additional properties:

• CUDA Fortran Register Limit
• CUDA Fortran Use Fused Multiply-Adds
• CUDA Fortran Use Fast Math Library
• CUDA Fortran Debug
• CUDA Fortran Line Information
• CUDA Fortran Use NVVM Back End
• CUDA Fortran Unroll
• CUDA Fortran Flush to Zero
• CUDA Fortran Toolkit
• CUDA Fortran Compute Capability
• CUDA Fortran Keep Binary
• CUDA Fortran Keep Kernel Source
• CUDA Fortran Keep PTX
• CUDA Fortran Keep PTXAS
• CUDA Fortran Generate RDC
• CUDA Fortran Madconst

For more information on -⁠Mcuda, refer to Optimization Controls.

When Enable CUDA Fortran is set to Yes, use this property to specify the number of registers to use on the GPU.

Setting this property to an integer value, n, adds the -⁠Mcuda=maxregcount:n switch to the PVF compilation and link lines.

Leaving this property blank indicates no limit to the number of registers to use on the GPU.

For more information on -⁠Mcuda, refer to Optimization Controls.

When Enable CUDA Fortran is set to Yes, use this property to control the generation of fused multiply-add (FMA) instructions.

• Default: Allows the compiler to control generation of FMA instructions. This selection adds no additional sub-options to -Mcuda.
• Yes: Enables generation of FMA instructions by adding -Mcuda=fma switch to the PVF compilation and link lines.
• No: Disables generation of FMA instructions by adding -Mcuda=nofma switch to the PVF compilation and link lines.

For more information on -⁠Mcuda, refer to Optimization Controls.

When Enable CUDA Fortran is set to Yes, use this property to use routines from the fast math library.

Setting this property to Yes adds the -⁠Mcuda=fastmath switch to compilation and linking.

For more information on -⁠Mcuda, refer to Optimization Controls.

When Enable CUDA Fortran is set to Yes, use this property to control generatation of GPU debug information.

• Default: Allows the compiler to control generatation of GPU debug information. This selection adds no additional sub-options to -⁠Mcuda.
• Yes: Enables generatation of GPU debug information by adding the -⁠Mcuda=debug switch to the PVF compilation and link lines.
• No: Disables generatation of GPU debug information by adding the -⁠Mcuda=nodebug switch to the PVF compilation and link lines.

For more information on -⁠Mcuda, refer to Optimization Controls.

When Enable CUDA Fortran is set to Yes, use this property to control generatation of GPU line information.

• Default: Allows the compiler to control generatation of GPU line information. This selection adds no additional sub-options to -⁠Mcuda.
• Yes: Enables generatation of GPU line information by adding the -⁠Mcuda=lineinfo switch to the PVF compilation and link lines.
• No: Disables generatation of GPU line information by adding the -⁠Mcuda=nolineinfo switch to the PVF compilation and link lines.

For more information on -⁠Mcuda, refer to Optimization Controls.

When Enable CUDA Fortran is set to Yes, use this property to control using NVVM back end.

• Default: Allows the compiler to control using NVVM back end. This selection adds no additional sub-options to -⁠Mcuda.
• Yes: Use NVVM back end by adding the -⁠Mcuda=nvvm switch to the PVF compilation and link lines.
• No: Use CUDA C back end by adding the -⁠Mcuda=nonvvm switch to the PVF compilation and link lines.

For more information on -⁠Mcuda, refer to Optimization Controls.

When Enable CUDA Fortran is set to Yes, use this property to control automatic inner loop unrolling.

• Default: Allows the compiler to control automatic inner loop unrolling. This selection adds no additional sub-options to -⁠Mcuda.
• Yes: Enables automatic inner loop unrolling by adding the -⁠Mcuda=unroll switch to the PVF compilation and link lines.
• No: Disables automatic inner loop unrolling by adding the -⁠Mcuda=nounroll switch to the PVF compilation and link lines.

For more information on -⁠Mcuda, refer to Optimization Controls.

When Enable CUDA Fortran is set to Yes, use this property to control flush-to-zero mode for floating point computations on in GPU code generated for CUDA Fortran kernels.

• Default: Accepts the default handling of floating point computations in the GPU code generated for CUDA Fortran kernels.
• Yes: Enables flush-to-zero mode by adding the -⁠Mcuda=flushz switch to the PVF compilation and link lines.
• No: Disables flush-to-zero mode by adding the -⁠Mcuda=noflushz switch to the PVF compilation and link lines.

For more information on -⁠Mcuda, refer to Optimization Controls.

When Enable CUDA Fortran is set to Yes, use this property to specify the version of the CUDA Toolkit that is targeted by the compilers.

• Default: The compiler selects the default CUDA toolkit version.
• 9.2: Use version 9.2 of the CUDA toolkit. This selection adds the -⁠Mcuda=cuda9.2 switch to the PVF compilation and link lines.
• 10.0: Use version 10.0 of the CUDA toolkit. This selection adds the -⁠Mcuda=cuda10.0 switch to the PVF compilation and link lines.
• 10.1: Use version 10.1 of the CUDA toolkit. This selection adds the -⁠Mcuda=cuda10.1 switch to the PVF compilation and link lines.

For more information on -⁠Mcuda, refer to Fortran Language Controls.

When Enable CUDA Fortran is set to Yes, use this property to either automatically generate code compatible with all applicable compute capabilities, or to direct the compiler to use a manually-selected set.

Select either Automatic or Manual.

• Automatic: Let the compiler generate code for all applicable compute capabilities. This is the default.
• Manual: Choose one or more compute capabilities to target. The compiler generates code for each capability specified.

  If you select Manual, then you can select any or all of the following compute capabilities:

  • CUDA Fortran CC Kepler: Set this property to Yes to add the -⁠Mcuda:cc35 switch to the PVF compilation and link lines.
  • CUDA Fortran CC Maxwell: Set this property to Yes to add the -⁠Mcuda:cc50 switch to the PVF compilation and link lines.
  • CUDA Fortran CC Pascal: Set this property to Yes to add the -⁠Mcuda:cc60 switch to the PVF compilation and link lines.
  • CUDA Fortran CC Volta: Set this property to Yes to add the -⁠Mcuda:cc70 switch to the PVF compilation and link lines.
  • CUDA Fortran CC All: Set this property to Yes to add the -⁠Mcuda:ccall switch to the PVF compilation and link lines.

For more information on -⁠Mcuda, refer to Optimization Controls.

Use this property to keep the CUDA binary (.bin) file.

Setting this property to Yes adds the -⁠Mcuda=keepbin switch to the PVF compilation and link lines.

For more information on -⁠Mcuda, refer to Optimization Controls.

When Enable CUDA Fortran is set to Yes, use this property to keep the kernel source files.

Setting this property to Yes adds the -⁠Mcuda=keepgpu switch to the PVF compilation and link lines.

For more information on -⁠Mcuda, refer to Optimization Controls.

When Enable CUDA Fortran is set to Yes, use this property to keep the portable assembly (.ptx) file for the GPU code.

Setting this property to Yes adds the -⁠Mcuda=keepptx switch to the PVF compilation and link lines.

For more information on -⁠Mcuda, refer to Optimization Controls.

Use this property to show PTXAS informational messages during compilation.

Setting this property to Yes adds the -⁠Mcuda=ptxinfo switch to the PVF compilation and link lines.

For more information on -⁠Mcuda, refer to Optimization Controls.

Use this property to generate relocatable device code (-Mcuda=rdc).

Setting this property to Yes adds the -⁠Mcuda=rdc switch to the PVF compilation and link lines.

For more information on -⁠Mcuda, refer to Optimization Controls.

When Enable CUDA Fortran is set to Yes, use this property to control putting module array descriptors in CUDA constant memory.

Setting this property to Yes adds the -⁠Mcuda=madconst switch to the PVF compilation and link lines.

For more information on -⁠Mcuda, refer to Optimization Controls.

Use this property to enable floating point exceptions.

Setting this property to Yes adds the -⁠Ktrap=fp option to compilation.

For more information on -⁠Ktrap, refer to -K<flag>.

Use this property to enable relaxed floating point accuracy in favor of speed.

Setting this property to Yes adds the -⁠Mfprelaxed option to compilation.

For more information on -⁠Mfprelaxed, refer to Optimization Controls.

Use this property to specify how to handle denormalized floating point results.

• Default: Accepts the default handling of denormalized floating point results.
• Yes: Enables SSE flush-to-zero mode using the -⁠Mflushz compilation option.
• No: Disables SSE flush-to-zero mode using the -⁠Mnoflushz compilation option.

For more information on -⁠M[no]flushz, refer to Code Generation Controls.

Use this property to specify how to treat denormalized floating point values.

• Default: Accept the default treatment of denormalized floating point values.
• Yes: Enable the treatment of denormalized floating point values as zero using the -⁠Mdaz compilation option.
• No: Disable the treatment of denormalized floating point values as zero using the -⁠Mnodaz compilation option.

For more information on -⁠M[no]daz, refer to Code Generation Controls.

Use this option to specify IEEE floating point arithmetic.

• Default: Accept the default floating point arithmetic.
• Yes: Enable IEEE floating point arithmetic using the -⁠Kieee compilation option.
• No: Disable IEEE floating point arithmetic using the -⁠Knoieee compilation option.

For more information on -⁠K[no]ieee, refer to -K<flag>.

Use this property to specify an alternate Fortran calling convention.

• Default: Accept the default calling convention.
• C By Reference: Use the CREF calling convention. Adds -⁠Miface=cref to compilation. On x64 platforms, no trailing underscores are used with this option and this option also causes Fortran externals to be uppercase and lengths of character arguments to be put at the end of the argument list.

For more information on -⁠Miface, refer to Miscellaneous Controls.

Use this property to change where string length arguments are placed in the argument list.

• Default: Use the calling convention's default placement for passing string length arguments.
• After Every String Argument: Lengths of character arguments are placed immediately after their corresponding argument. This option adds -⁠Miface=mixed_str_len_arg to compilation.
• After All Arguments: Places lengths of character arguments at the end of the argument list. This option adds -⁠Miface=nomixed_str_len_arg to the compilation.

For more information on -⁠Miface, refer to Miscellaneous Controls.

Use this property to specify the case used for Fortran external names.

• Default: Use the calling convention's default case for external names.
• Lower Case: Make Fortran external names lower case. This option adds -⁠Mnames=lowercase to the compilation.
• Upper Case: Make Fortran external names upper case. This option adds -⁠Mnames=uppercase to the compilation.

Use this property to build for and link against the Intel Math Kernel Library (MKL), which is available from Intel.

• Yes: Use the Intel Math Kernel Library when building and linking programs.
• No: Do not use the Intel Math Kernel Library when building and linking programs.

Use this property to optimize for AMD Bulldozer and compatible processors.

Setting this property to Yes adds the -⁠tp=bulldozer switch to compilation.

Use this property to optimize for AMD Piledriver processor-based systems.

Setting this property to Yes adds the -⁠tp=piledriver switch to compilation.

Use this property to optimize for AMD Zen (Epyc, Ryzen) processor-based systems.

Setting this property to Yes adds the -⁠tp=zen switch to compilation.

Use this property to optimize for Intel Sandy Bridge architecture and compatible processors.

Setting this property to Yes adds the -⁠tp=sandybridge switch to compilation.

Use this property to optimize for Intel Haswell architecture and compatible processors.

Setting this property to Yes adds the -⁠tp=haswell switch to compilation.

Use this property to optimize for Intel Knights Landing architecture and compatible processors.

Setting this property to Yes adds the -⁠tp=knl switch to compilation.

Use this property to optimize for Intel Skylake architecture and compatible processors.

Setting this property to Yes adds the -⁠tp=skylake switch to compilation.

Use this property to optimize for any x86 processor-based system.

Setting this property to Yes adds the -⁠tp=px switch to compilation.

Use this property to select NVIDIA Tesla targets.

Setting this property to Yes adds the -⁠ta=tesla switch to the PVF compilation and link lines and activates access to these additional properties:

• Tesla Register Limit
• Tesla Use Fused Multiply-Adds
• Tesla Use Fast Math Library
• Tesla LLVM
• Tesla Noattach
• Tesla Pin Host Memory
• Tesla Autocollapse
• Tesla Debug
• Tesla Lineinfo
• Tesla Unroll
• Tesla Required
• Tesla Flush to Zero
• Tesla CUDA Toolkit
• Tesla Compute Capability
• Tesla: Keep Kernel Files

Use this property to specify the number of registers to use on the GPU.

Setting this property to an integer value, n, adds the -⁠ta=tesla:maxregcount:n switch to the PVF compilation and link lines.

Leaving this property blank indicates no limit to the number of registers to use on the GPU.

When Target NVIDIA Tesla is set to Yes, use this property to control the generation of fused multiply-add (FMA) instructions.

• Default: Allows the compiler to control generation of FMA instructions. This selection adds no additional sub-options to -⁠ta=tesla.
• Yes: Enables generation of FMA instructions by adding -⁠ta=tesla:fma to the PVF compilation and link lines.
• No: Disables generation of FMA instructions by adding -⁠ta=tesla:nofma to the PVF compilation and link lines.

When Target NVIDIA Tesla is set to Yes, use this property to use routines from the fast math library.

Setting this property to Yes adds the -⁠ta=tesla:fastmath switch to the PVF compilation and link lines.

When Target NVIDIA Tesla is set to Yes, use this property to control using of LLVM back end.

Setting this property to Yes adds the -⁠ta=tesla:llvm switch to the PVF compilation and link lines.

When Target NVIDIA Tesla is set to Yes, use this property to prevent attaching to existing CUDA context.

Setting this property to Yes adds the -⁠ta=tesla:noattach switch to the PVF compilation and link lines.

When Target NVIDIA Tesla is set to Yes, use this property to set default to pin host memory.

Setting this property to Yes adds the -⁠ta=tesla:pin switch to the PVF compilation and link lines.

When Target NVIDIA Tesla is set to Yes, use this property to automatically collapse tightly nested loops.

• Default: Allows the compiler to control automatic collapse of tightly nested loops. This select adds no additional sub-options to -⁠ta=tesla.
• Yes: Enables automatic collapse of tightly nested loops by adding the -⁠ta=tesla:autocollapse switch to the PVF compilation and link lines.
• No: Disables automatic collapse of tightly nested loops by adding the -⁠ta=tesla:noautocollapse switch to the PVF compilation and link lines.

When Target NVIDIA Tesla is set to Yes, use this property to control generation of GPU debug information.

• Default: Allows the compiler to control generation of GPU debug information. This select adds no additional sub-options to -⁠ta=tesla.
• Yes: Enables generation of GPU debug information by adding the -⁠ta=tesla:debug switch to the PVF compilation and link lines.
• No: Disables generation of GPU debug information by adding the -⁠ta=tesla:nodebug switch to the PVF compilation and link lines.

When Target NVIDIA Tesla is set to Yes, use this property to control generation of GPU line information.

• Default: Allows the compiler to control generation of GPU line information. This select adds no additional sub-options to -⁠ta=tesla.
• Yes: Enables generation of GPU line information by adding the -⁠ta=tesla:lineinfo switch to the PVF compilation and link lines.
• No: Disables generation of GPU line information by adding the -⁠ta=tesla:nolineinfo switch to the PVF compilation and link lines.

When Target NVIDIA Tesla is set to Yes, use this property to control automatic inner loop unrolling.

• Default: Allows the compiler to control automatic inner loop unrolling. This select adds no additional sub-options to -⁠ta=tesla.
• Yes: Enables automatic inner loop unrolling by adding the -⁠ta=tesla:unroll switch to the PVF compilation and link lines.
• No: Disables automatic inner loop unrolling by adding the -⁠ta=tesla:nounroll switch to the PVF compilation and link lines.

When Target NVIDIA Tesla is set to Yes, use this property to direct the compiler to issue error if the compute regions fail to accelerate.

• Default: Uses the compiler defaults for handling instances where compute regions cannot be accelerated. This select adds no additional sub-options to -⁠ta=tesla.
• Yes: Directs the compiler to stop compilation with an error when it cannot accelerate a compute region by adding the -⁠ta=tesla:required switch to the PVF compilation and link lines.
• No: Directs the compiler to issue warnings when it cannot accelerate a compute region by adding the -⁠ta=tesla:norequired switch to the PVF compilation and link lines. Compilation does not stop but accelerator kernels are not generated.

When Target NVIDIA Tesla is set to Yes, use this property to control flush-to-zero mode for floating point computations in the GPU code generated for PGI Accelerator model compute regions.

• Default: Accepts the default handling of floating point computations in the GPU code generated for CUDA Fortran kernels.
• Yes: Enables flush-to-zero mode by adding the -⁠ta=tesla:flushz switch to the PVF compilation and link lines.
• No: Disables flush-to-zero mode by adding the -⁠ta=tesla:noflushz switch to the PVF compilation and link lines.

When Target NVIDIA Tesla is set to Yes, use this property to control generation of relocatable device code.

• Default: Accepts the compiler’s default generation of relocatable device code.
• Yes: Directs the compiler to generate relocatable device code by adding -⁠ta=tesla:rdc switch to the PVF compilation and link lines.
• No: Prevents the compiler from generating relocatable device code by adding -⁠ta=tesla:nordc switch to the PVF compilation and link lines.

When Target NVIDIA Tesla is set to Yes, use this property to specify the version of the NVIDIA CUDA toolkit that is targeted by the compilers:

• Default: The compiler selects the default CUDA toolkit version.
• 9.2: Use version 9.2 of the CUDA toolkit. This selection adds the -⁠ta=tesla:cuda9.2 switch to the PVF compilation and link lines.
• 10.0: Use version 10.0 of the CUDA toolkit. This selection adds the -⁠ta=tesla:cuda10.0 switch to the PVF compilation and link lines.
• 10.1: Use version 10.1 of the CUDA toolkit. This selection adds the -⁠ta=tesla:cuda10.1 switch to the PVF compilation and link lines.

When Target NVIDIA Tesla is set to Yes, use this property to either automatically generate code compatible with all applicable compute capabilities, or to direct the compiler to use a manually-selected set.

Select either Automatic or Manual.

• Automatic: Let the compiler generate code for all applicable compute capabilities. This is the default.
• Manual: Choose one or more compute capabilities to target. The compiler generates code for each capability specified.

  If you select Manual, then you can select any or all of the following compute capabilities:

  • Tesla CC Kepler: Set this property to Yes to add the -⁠ta=tesla:cc35 switch to the PVF compilation and link lines.
  • Tesla CC Maxwell: Set this property to Yes to add the -⁠ta=tesla:cc50 switch to the PVF compilation and link lines.
  • Tesla CC Pascal: Set this property to Yes to add the -⁠ta=tesla:cc60 switch to the PVF compilation and link lines.
  • Tesla CC Volta: Set this property to Yes to add the -⁠ta=tesla:cc70 switch to the PVF compilation and link lines.
  • Tesla CC All: Set this property to Yes to add the -⁠ta=tesla:ccall switch to the PVF compilation and link lines.

When Target NVIDIA Tesla is set to Yes, use this property to keep kernel files.

Setting this property to Yes adds the -⁠ta=tesla:keep switch to the PVF compilation and link lines.

Use this property to select the level of diagnostic reporting you want the compiler to use.

There are several levels of the -⁠Minform option available through this property. For more information on this option, refer to Miscellaneous Controls.

Use this property to generate an assembly file for each compiled source file.

Setting this property to Yes adds the -⁠Mkeepasm switch to the compilation line.

For more information on -⁠Mkeepasm, refer to Miscellaneous Controls.

Use this property to generate assembly files and to annotate the assembly with source code.

Setting this property to Yes adds the -⁠Manno switch to the compilation line.

For more information on -⁠Manno, refer to Miscellaneous Controls.

Use this property to generate information about accelerator regions.

Setting this property to Yes adds the -⁠Minfo=accel switch to the compilation line.

Use this property to append common compiler feedback format (CCFF) information to object files.

Setting this property to Yes adds the -⁠Minfo=ccff switch to the compilation line.

Use this property to generate information about Fortran language features.

Setting this property to Yes adds the -⁠Minfo=ftn switch to the compilation line.

Use this property to generate information about inlining.

Setting this property to Yes adds the -⁠Minfo=inline switch to the compilation line.

Use this property to generate information about interprocedural analysis (IPA) optimizations.

Setting this property to Yes adds the -⁠Minfo=ipa switch to the compilation line.

Use this property to generate compute intensity information about loops.

Setting this property to Yes adds the -⁠Minfo=intensity switch to the compilation line.

Use this property to generate information about loop optimizations.

Setting this property to Yes adds the -⁠Minfo=loop switch to the compilation line.

Use this property to generate information about loop-carried redundancy (LRE) elimination.

Setting this property to Yes adds the -⁠Minfo=lre switch to the compilation line.

Use this property to generate information about OpenMP.

Setting this property to Yes adds the -⁠Minfo=mp switch to the compilation line.

Use this property to generate information about general optimizations.

Setting this property to Yes adds the -⁠Minfo=opt switch to the compilation line.

Use this property to generate information about parallel optimizations.

Setting this property to Yes adds the -⁠Minfo=par switch to the compilation line.

Use this property to generate information specific to the PGI Unified Binary.

Setting this property to Yes adds the -⁠Minfo=unified switch to the compilation line.

Use this property to generate vectorization information.

Setting this property to Yes adds the -⁠Minfo=vect switch to the compilation line.

Use this property to suppress profiling's default generation of CCFF information.

Setting this property to Yes adds the -⁠Mprof=noccff switch to the compiling and linking lines.

Use this property to generate limited DWARF information which can be used with performance profilers.

Setting this property to Yes adds the -⁠Mprof=dwarf switch to the compiling and linking lines.

Use this property to enable array bounds checking at runtime.

Setting this property to Yes adds the -⁠Mbounds switch to the compilation line.

Setting this property to No adds no option to the compilation line, and there is no array bounds checking at runtime. No is the default.

Use this property to perform runtime checks for pointers that are dereferenced while initialized to null.

Setting this property to Yes adds the -⁠Mchkptr switch to the compilation line.

Setting this property to No adds no option to the compilation line, and there is no runtime check for pointers that are dereferenced while initialized to null. No is the default.

Use this property to perform runtime stack checks for available space in the prologue of a function and before the start of a parallel region.

Setting this property to Yes adds the -⁠Mchkstk switch to the compilation line.

Setting this property to No adds no option to the compilation line, and there are no runtime stack checks. No is the default.

This property page contains two boxes.

• The first box, titled All options, is a read-only description of what the compilation line will be. This description is based on the values of the properties set in the Fortran property pages.
• The second box, titled Additional options, allows you to specify any other options that you want the compiler to use. Use this box when the option you need is not available through any of the Fortran property pages.

  For more information on all the compiler options that are available, refer to Command-Line Options Reference.

This property page contains two boxes.

• The first box, titled All options, is a read-only description of what the compilation line will be. This description is based on the values of the properties set in the Fortran property pages.
• The second box, titled Additional options, allows you to specify any other options that you want the compiler to use. Use this box when the option you need is not available through any of the Fortran property pages.

  For more information on all the compiler options that are available, refer to Command-Line Options Reference.

Use this property to override the default output file name.

Providing the file name and the file’s extension is equivalent to using the -⁠o switch.

For more information on -⁠o, refer to -o.

Use this property to add one or more directories to the library search path.

For every directory path that is added to this property, PVF adds /LIBPATH:[dir] to the link line.

There are two ways to add directories to this property:

• Type the information directly into the property page box.

  Use a semi-colon (‘;’) to separate each directory.

• Click the ellipsis (‘...’) button in the property page box to open the Additional Library Directories dialog box.

  Enter each directory on its own line in this box. Do not use semi-colons to separate directories; the semi-colons are added automatically when the box is closed.

Use this property to specify the total number of bytes for stack allocation in virtual memory. Use decimal notation. This property is equivalent to the -stack=reserve option. Leave this property blank to direct the linker to choose a default size for the stack.

Use this property to specify the total number of bytes for stack allocation in physical memory. Use decimal notation. This property is equivalent to the -⁠stack=reserve,commit option. Commit Size is used only if a size is also specified for Stack Reserve.

Use this property to specify whether the DLL will export symbols. This property is only visible for DLL project types.

Use this property to specify additional dependencies, such as libraries, to the link line.

There are two ways to add libraries to this property:

• Type the information directly into the property page box.
  Note: Use spaces, not semi-colons, to separate multiple libraries. If the name of a library contains a space, use double quotes around that library name.
• Click the ellipsis (‘...’) button in the property page box to open the Additional Dependencies dialog box.

  Enter each library on its own line in this box.

  Note: If you enter two libraries on the same line in this box, PVF interprets these as a single library whose name contains spaces.

This property page contains two boxes.

• The first box, titled All options, is a read-only description of what the link line will be. This value is based on the values of the properties set in the Linker property pages.
• The second box, titled Additional options allows you to specify options that you want the linker to use. Use this box when the option you need is not available through any of the Linker property pages.

  For more information on all the compiler options that are available, refer to Command-Line Options Reference.

Use this property to override the default output file name.

Providing the file name and the file’s extension is equivalent to using the -⁠o switch.

For more information on -⁠o, refer to -o.

Use this property to add one or more directories to the library search path.

For every directory path that is added to this property, PVF adds /LIBPATH:<dir> to the link line.

There are two ways to add directories to this property:

• Type the information directly into the property page box.

  Use a semi-colon (‘;’) to separate each directory.

• Click the ellipsis (‘...’) button in the property page box to open the Additional Library Directories dialog box.

  Enter each directory on its own line in this box. Do not use semi-colons to separate directories; the semi-colons are added automatically when the box is closed.

Use this property to specify additional dependencies, such as libraries, to the link line.

There are two ways to add libraries to this property:

• Type the information directly into the property page box.
  Note: Use spaces, not semi-colons, to separate multiple libraries. If the name of a library contains a space, use double quotes around that library name.
• Click the ellipsis (‘...’) button in the property page box to open the Additional Dependencies dialog box.

  Enter each library on its own line in this box.

  Note: If you enter two libraries on the same line in this box, PVF interprets these as a single library whose name contains spaces.

This property page contains two boxes.

• The first box, titled All options, is a read-only description of what the link line will be. This value is based on the values of the properties set in the Librarian property pages.
• The second box, titled Additional options, allows you to specify options that you want the librarian to use, even though these options are not available through any of the Librarian property pages.

  For more information on all the compiler options that are available, refer to Command-Line Options Reference.

Use this property to add options to the Resource compiler’s command line.

PVF’s support of resources is somewhat limited at this time and the property pages in this category reflect that. To add options to the Resource compiler’s command line, use the Additional options box on this property page.

The name of the build event describes when the event will be fired.

• The Pre-Build Event is run before a build starts.
• The Pre-Link Event is run after compilation but before linking.
• The Post-Build Event is run after the build completes.

The properties for a build event are the same for all three types of build events.

Use this property to specify the command line that the build tool will run.

This property is at the core of the build event. For example, to add a time stamp to a build, you could use time /t as the build event’s command line.

Use this property to provide feedback to the Output window. The contents of the Description property is echoed to the Output window when this event is fired.

Use this property to specify whether this build event should be excluded from the build for the current configuration.