Добавил:
Опубликованный материал нарушает ваши авторские права? Сообщите нам.
Вуз: Предмет: Файл:
E77790.pdf
Скачиваний:
2
Добавлен:
16.05.2024
Размер:
1.29 Mб
Скачать

3.4 Options Reference

memorysize unlimited demo%

Example: Set the main stack size to 64 Megabytes:

demo% limit stacksize 65536

You can set the size of the thread stack used by each slave thread by setting the STACKSIZE or

OMP_STACKSIZE environment variable. See the Oracle Developer Studio 12.6: OpenMP API User’s Guide for more information about these environment variables.

Compile with -xcheck=stkovf to enable runtime checking for stack overflow situations. See the -xcheck option for more information.

3.4.94–stop_status[={yes|no}]

Permit STOP statement to return an integer status value.

The default is -stop_status=no.

With -stop_status=yes, a STOP statement may contain an integer constant. That value will be passed to the environment as the program terminates:

STOP 123

The value must be in the range 0 to 255. Larger values are truncated and a run–time message issued. Note that

STOP ”stop string

is still accepted and returns a status value of 0 to the environment, although a compiler warning message will be issued.

The environment status variable is $status for the C shell csh, and $? for the Bourne and Korn shells, sh and ksh.

3.4.95–temp=dir

Define directory for temporary files.

Chapter 3 • Fortran Compiler Options

97

3.4 Options Reference

Set directory for temporary files used by the compiler to be dir. No space is allowed within this option string. Without this option, the files are placed in the /tmp directory.

This option takes precedence over the value of the TMPDIR environment variable.

3.4.96–time

Time each compilation phase.

The time spent and resources used in each compiler pass is displayed.

3.4.97–traceback[={%none|common|signals_list}]

Issue a stack trace if a severe error occurs in execution.

The -traceback option causes the executable to issue a stack trace to stderr, dump core, and exit if certain signals are generated by the program. If multiple threads generate a signal, a stack trace will only be produced for the first one.

To use traceback, add the -traceback option to the compiler command line when linking. The option is also accepted at compile-time but is ignored unless an executable binary is generated. Using -traceback with the -G or -shared options to create a shared library is an error.

TABLE 11

-traceback Options

 

 

Option

Meaning

 

 

common

specifies that a stack trace should be issued if any of a set of common signals occurs:

 

sigill, sigfpe, sigbus, sigsegv, or sigabrt.

signals_list

specifies a comma-separated list of names of signals that should generate a stack trace,

 

in lower case. The following signals (those that cause the generation of a core file) can

 

be caught: sigquit, sigill, sigtrap, sigabrt, sigemt, sigfpe, sigbus, sigsegv,

 

sigsys, sigxcpu, sigxfsz.

 

Any of these can be preceded with no% to disable catching the signal.

 

For example: -traceback=sigsegv,sigfpe will produce a stack trace and core dump if

 

either sigsegv or sigfpe occurs.

%none or none

disables traceback

 

 

If the option is not specified, the default is -traceback=%none

98 Oracle Developer Studio 12.6: Fortran User's Guide • July 2017

3.4 Options Reference

-traceback alone, without a value, implies -traceback=common

Note: If the core dump is not wanted, users may set the coredumpsize limit to zero using:

% limit coredumpsize 0

The -traceback option has no effect on runtime performance.

3.4.98–U

Recognize upper and lower case in source files.

Do not treat uppercase letters as equivalent to lowercase. The default is to treat uppercase as lowercase except within character–string constants. With this option, the compiler treats Delta, DELTA, and delta as different symbols. Calls to intrinsic functions are not affected by this option.

Portability and mixing Fortran with other languages may require use of -U.

3.4.99–Uname

Undefine preprocessor macro name.

This option applies only to source files that invoke the fpp or cpp preprocessor. It removes any initial definition of the preprocessor macro name created by -Dname on the same command line, including those implicitly placed there by the command-line driver, regardless of the order the options appear. It has no effect on any macro definitions in source files. Multiple -Uname flags can appear on the command line. There must be no space between -U and the macro name.

3.4.100 –u

Report undeclared variables.

Make the default type for all variables be undeclared rather than using Fortran implicit typing, as if IMPLICIT NONE appeared in each compilation unit. This option warns of undeclared variables, and does not override any IMPLICIT statements or explicit type statements.

Chapter 3 • Fortran Compiler Options

99

3.4 Options Reference

3.4.101 –unroll=n

Enable unrolling of DO loops where possible.

n is a positive integer. The choices are:

n=1 inhibits all loop unrolling.

n>1 suggests to the optimizer that it attempt to unroll loops n times.

Loop unrolling generally improves performance, but will increase the size of the executable file. See also “2.3.1.3 The UNROLL Directive” on page 32.

3.4.102 –use=list

Specify implicit USE modules.

list is a comma-separated list of module names or module file names.

Compiling with -use=module_name has the effect of adding a USE module_name statement to each subprogram or module being compiled. Compiling with -use=module_file_name has the effect of adding a USE module_name for each of the modules contained in the specified file.

See “4.9 Module Files” on page 192 for more information about modules in Fortran.

3.4.103 –V

Show name and version of each compiler pass.

This option prints the name and version of each pass as the compiler executes.

3.4.104 –v

Verbose mode -show details of each compiler pass.

100 Oracle Developer Studio 12.6: Fortran User's Guide • July 2017

Соседние файлы в предмете Информационные и сетевые технологии