The -ARCLIMIT option, described in Table A-2, controls the size of the internal table used to store data dependence information (arcs).

The -ASSUME option, described in Table A-3, controls certain global assumptions of a program.

You can also use various assertions to control these assumptions. list is any combination of the following values:

The -CONCURRENTIZE option, described in Table A-4, converts eligible loops to run in parallel.

See also NOCONCURRENTIZE.

The -DIRECTIVES option, described in Table A-5, specifies the directives and assertions to accept.

list consists of any combination of

See also NODIRECTIVES.

The -DLINES option, described in Table A-6, tells PFA to treat letter D in column one as if the letter were a character space.

PFA then parses the rest of that line as a normal Fortran 77 statement. See also NODLINES.

The -FORTRAN option, described in Table A-7, specifies the name of the PFA-transformed source.

filename is the name of the Fortran source.

The -INLINE option, described in Table A-8, specifies the routines to be inlined.

If this option is given with a (colon-separated) list of routine names, then only those routines will be inlined. If it is given without a list of names, then PFA will attempt to inline all eligible routines.

The -INLINE_CREATE option, described in Table A-9, creates a library of prepared routines for later use with the -INLINE_FROM_LIBRARIES option.

You are not required to create a library to do inlining; you can inline directly from a source file.

Constructing a library will save time if the inlining operation is to be done repeatedly. PFA analyzes the current source file and places the appropriate information into the file named with the -INLINE_CREATE option. For maximum compatibility, the filename extension .klib is recommended: for example, samp.klib.

The -INLINE_DEPTH option, described in Table A-10, restricts the number of times PFA will continue to attempt inlining on already inlined routines.

This option controls this process, as routines are only inlined to the specified depth.

As a special case, if you specify the value –1, only routines that do not reference other routines are inlined (that is, only leaf routines are inlined). The only valid negative number is –1; do not specify –2, –3, and so on. Note that there is no -IPA_DEPTH option.

The -INLINE_FROM_FILES option, described in Table A-11, specifies where to look for routines named in the -INLINE option.

Files with the extension .f are assumed to be Fortran source, while files with the extension .klib are assumed to be PFA-produced libraries. Specify multiple files and directories by using a colon-separated list.

The -INLINE_FROM_LIBRARIES option, described in Table A-12, specifies where to look for the routines named in the -INLINE option.

Files with the extension .f are assumed to be Fortran source, while files with the extension .klib are assumed to be PFA-produced libraries. Specify multiple libraries by using a colon-separated list.

The -INLINE_LOOPLEVEL option, described in Table A-13, restricts PFA occurrences within deeply nested loops.

Thus, a value of 1 restricts PFA to deal with routines only at the singlemost deeply nested level; a value of 2 restricts PFA to the deepest and second-deepest levels; and so on.

To determine what is most deeply nested, PFA constructs a call graph to account for nesting due to loops that occur farther up the call chain.

The -INLINE_MAN option, described in Table A-14, turns on recognition of the C*$*INLINE directive.

The C*$*INLINE directive allows you select individual occurrences of routines to be inlined.

The -INPUT option, described in Table A-15, specifies the name of the PFA input file.

It is not necessary to precede the input filename with this option; PFA assumes that a command line argument not preceded by a dash is the input filename.

The -IPA option, described in Table A-16, specifies the routine's IPA.

If this option is given with a colon-separated list of routine names, then only those routines will be IPAed. If it is given without a list of names, then PFA will attempt to IPA all eligible routines.

The -IPA_CREATE option, described in Table A-17, creates a library of prepared routines for later use with the -IPA_FROM_LIBRARIES option.

You are not required to create a library to do inlining; you can inline directly from a source file. Constructing a library will save time if the inlining operation is to be done repeatedly. PFA analyzes the current source file and places the appropriate information into the file named with the -INLINE_CREATE option. For maximum compatibility, the filename extension .klib is recommended: for example, samp.klib.

Libraries created for IPA only contain summary information and so can be used only for IPA.

The -IPA_FROM_FILES option, described in Table A-18, specifies where to look for the routines named in the -IPA option.

Files with the extension .f are assumed to be Fortran source, while files with the extension .klib are assumed to be PFA-produced libraries. Specify multiple files using a colon-separated list.

The -IPA_FROM_LIBRARIES option, described in Table A-19, specifies where to look for the routines named in the -IPA option.

Files with the extension .f are assumed to be Fortran source, while files with the extension .klib are assumed to be PFA-produced libraries. Specify multiple libraries by using a colon-separated list.

The -IPA_LOOPLEVEL option, described in Table A-20, restricts PFA to occurrences within deeply nested loops.

A value of 1 restricts PFA to routines only at the singlemost deeply nested level; a value of 2 restricts PFA to the deepest and second-deepest levels; and so on. To determine what is most deeply nested, PFA constructs a call graph to account for nesting due to loops that occur further up the call chain.

The -IPA_MAN option, described in Table A-21, turns on recognition of the C*$*IPA directive.

The C*$*IPA directive allows you select individual occurrences of routines to be IPAed.

The -LIMIT option, described in Table A-22, reduces PFA processing time by limiting the amount of time PFA can spend on trying to determine whether a loop is safe to run in parallel.

PFA estimates how much time is required to analyze each loop nest construct. If an outer loop looks like it would take too much time to analyze, PFA ignores the outer loop and recursively visits the inner loops.

Larger limits often allow PFA to generate parallel code for deeply nested loop structures that it might not otherwise be able to run safely in parallel. However, with larger limits PFA can also take more time to analyze a program. (The limit does not correspond to the DO loop nest level. It is an estimate of the number of loop orderings that PFA can generate from a loop nest.)

The -LINES option, described in Table A-23, paginates the listing for printing.

Use this option to change the number of lines per page. Specifying -LINES=0 paginates at subroutine boundaries.

The -LIST option, described in Table A-24, specifies the name of the PFA listing file.

filename is the name of the Fortran source.

The -LISTOPTIONS option, described in Table A-25, specifies the information to include in the listing file (.l).

list consists of any combination of

The -MINCONCURRENT option, described in Table A-26, establishes the minimum amount of work needed inside the loop to make executing a loop in parallel profitable.

If the loop does not contain at least this much work, the loop will not be run in parallel. If the loop bounds are not constants, an IF clause will be automatically added to the PFA-generated DOACROSS directive to test at run time whether sufficient work exists.

The MINCONCURRENT value is a count of the number of operations (for example, add, multiply, load, store) in the loop, multiplied by the number of times the loop will be executed.

The -NOCONCURRENTIZE option, described in Table A-27, prevents PFA from converting loops to run in parallel.

See also CONCURRENTIZE.

The -NODIRECTIVES option, described in Table A-28, tells PFA to ignore all directives and assertions.

See also DIRECTIVES.

The -NODLINES option, described in Table A-29, tells PFA to treat lines starting with D as though they were comments.

See also DLINES.

The -NOONETRIP option, described in Table A-30, conforms to the Fortran 77 standard, which specifies that a DO loop whose termination condition is initially satisfied is not executed.

See also ONETRIP.

The -ONETRIP option, described in Table A-31, allows compatibility with older versions of Fortran where a DO loop is always executed at least once.

See also NOONETRIP.

The -OPTIMIZE option, described in Table A-32, sets the optimization level.

The higher you set the optimization level, the more code is optimized and the longer PFA runs.

Valid values for n are the integers

The -ROUNDOFF option, described in Table A-33, controls whether PFA runs a reduction operation in parallel.

Valid values for n are

Table A-34 describes the -SAVE option.

Either of the following values are valid for c:

The -SCALAROPT=n option, described in Table A-35, controls the amount of standard scalar optimizations attempted by PFA.

Valid values for n are

The -SCAN option, described in Table A-36, controls the number of columns that are assumed to be significant (PFA ignores anything beyond the specified column).

Specifying any of the following f77 options automatically sets this option: -col72, -col120, or -extend _source.

The -SUPPRESS option, described in Table A-37, lets you individually disable classes of PFA messages that are normally included in the listing (.l) file.

These messages range from syntax warnings and error messages to messages about the optimizations performed.

list is of any combination of the following:

Setting the -SYNTAX option, described in Table A-38, alters the interpretation of the Fortran input to be in compliance with other standards.

c is any of the following values:

The -UNROLL option, described in Table A-39, unrolls scalar inner loops when PFA cannot run the loops in parallel.

When PFA unrolls a loop, it replicates the body of the loop a certain number of times, making the loop run faster. (In previous releases of PFA the default value was 1.)

The -UNROLL2 option, described in Table A-40, allows you to adjust the number of operations used by the -UNROLL option.

Selecting a larger value for -UNROLL2 allows PFA to unroll loops containing more calculations.

This form of unrolling applies only to the innermost loops in a nest of loops. You can unroll loops whether they execute serially or concurrently.

f 77 passes this option to PFA automatically when you specify the f77 -d lines option.