Version 10.9 Domain FORTRAN Software Release Document
Versions 10.9.p, 10.9.pmx, 10.9.m, and 10.9.mpx
March 31, 1992
Manufacturing Part No. 019458-A00
This document describes the Domain FORTRAN Version
10.9 compilers: Versions 10.9.p and 10.9.pmx run on
DN10000 workstations and Versions 10.9.m and
10.9.mpx run onMC680x0-based workstations. This
document lists all bugs fixed since Version 10.8.
It supplements the "Domain FORTRAN Language
Reference" (000530-A01).
Domain FORTRAN 1 Version 10.9
Copyright Hewlett-Packard Co. 1992.
First Printing: March 1992
UNIX is a registered trademark of UNIX System Laboratories Inc.
NOTICE
The information contained in this document is subject to change without
notice.
HEWLETT-PACKARD MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THIS MATERIAL
INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE. Hewlett-Packard shall not be liable for
errors contained herein or for incidental or consequential damages in
connection with the furnishing, performance or use of this material.
Hewlett-Packard assumes no responsibility for the use or reliability of its
software on equipment that is not furnished by Hewlett-Packard.
This document contains proprietary information which is protected by
copyright. All rights reserved. No part of this document may be
photocopied, reproduced, or translated to another language without the prior
written consent of Hewlett-Packard Company.
RESTRICTED RIGHTS LEGEND
Use, duplication or disclosure by the U.S. Government is subject to
restrictions as set forth in subdivision (c) (1) (ii) of the Rights in
Technical Data and Computer Software Clause at DFARS 252.227.7013.
Hewlett-Packard Co.
3000 Hanover Street
Palo Alto, CA 94304 U.S.A.
Rights for non-DOD U.S. Government Departments and Agencies are as set forth
in FAR 52.227-19(c)(1,2).
Domain FORTRAN 2 Version 10.9
Reader_Notice
This document resides online in the /install/doc/apollo directory. You may
print the online copy of this document by using one of the following
commands:
If your installation uses the System V lp print daemon, use an lp command
similar to the following:
lp -dprinter_name pathname
where pathname is the pathname of the release notes, usually
For MC680x0-based workstations:
/install/doc/apollo/ftn.v.10.9.m__notes
/install/doc/apollo/ftn.v.10.9.mpx__notes
For Series 10000 workstations:
/install/doc/apollo/ftn.v.10.9.p__notes
/install/doc/apollo/ftn.v.10.9.pmx__notes
If your installation uses the Domain print system, use the following Aegis
/com/prf command:
prf pathname -pr printer_name -npag
If your installation uses the BSD lpd print daemon, use an lpr command
similar to the following:
lpr -Pprinter_name pathname
Domain FORTRAN 3 Version 10.9
Contents
CHAPTER 1 OVERVIEW OF DOMAIN FORTRAN VERSION 10.9
1.1 New f77 -qg Compiler Option ........................ 5
1.2 New ftn -nfpra Compiler Option ..................... 5
CHAPTER 2 INSTALLATION INFORMATION
2.1 Online Manual Pages for f77 ........................ 9
2.2 The mrgri Tool ..................................... 9
2.3 Running Programs on SR10.1 Nodes ................... 10
CHAPTER 3 DOCUMENTATION
3.1 Exponential Expressions ............................ 11
3.2 Length Specification for Character Variables........ 11
3.3 Error Message 326 .................................. 12
3.4 Error Message 909 .................................. 12
3.5 Model Numbers for -cpu mathchip Option ............. 13
3.6 ISO Latin-1 Character Set .......................... 13
CHAPTER 4 BUG FIXES
4.1 FORTRAN Language APRs............................... 14
4.2 FORTRAN Documentation APRs.......................... 16
4.2 Compiler APRs....................................... 16
Domain FORTRAN 4 Version 10.9
CHAPTER 1
Overview of Domain FORTRAN Version 10.9
This document describes Domain FORTRAN Version 10.9. All information
contained herein applies to both PRISM-based and MC680x0-based workstations,
unless specifically indicated otherwise.
For more information about the Domain FORTRAN compiler, refer to the "Domain
FORTRAN Language Reference" (000530-A01).
1.1 New -qg Compiler Option for SysV's f77
The -qg option tells the compiler to produce profiled code that allows
profiling with gprof(1). Upon normal termination of execution of the object
program, a gmon.out is produced. (The -qg option automatically activates the
-W0,-ncompress option. If you specify -W0,-compress in conjunction with -qg,
profiling will not work correctly.)
1.2 The -nfpra Option: Suppressing Expression Reordering
If your program does floating-point arithmetic, and if compiling your program
at optimization level 4 produces results different from those obtained at
lower optimization levels, you may want to use the compiler option -nfpra to
suppress the reordering of operands in floating-point expressions. The
-nfpra option lets you get the benefit of other level 4 optimizations
(notably inlining) without sacrificing accuracy in floating-point
operations.
When computers evaluate floating-point expressions, the algebraic law of
associativity does not apply. For example,
a + (b + c)
does not equal
(a + b) + c
Domain FORTRAN 5 Version 10.9
The associative law does not work for floating-point operations because, on
computers, floating-point operations are inherently inexact. Each operation
usually introduces a small rounding error into the result, so changing the
operations usually changes the result. For this reason, Domain compilers
ordinarily do not reorder floating-point expressions. At the highest level
of optimization, however, reordering of floating-point operands may occur in
some situations.
Most of the time, the results of reordered floating-point operations are so
close to the results of unreordered operations that no difference is
noticeable. However, occasionally a result will be remarkably different; for
example, if a result obtained without reordering is very close to the maximum
normalized value, reordering could cause the result to overflow. In such
cases, use the -nfpra option.
For more information about floating-point operations, see the "Domain
Floating-Point Guide," Order No. D-15853-B.
Domain FORTRAN 6 Version 10.9
CHAPTER 2
Installation Information
You can install Domain FORTRAN Version 10.9 on a user node (one equipped with
monitor and keyboard) or a Domain Server Processor (DSP) that is running
Software Release 10.0 or a more recent version of the Domain/OS operating
system. (In order to run Domain FORTRAN Version 10.9 on a node running
SR10.1, you must install a patch version of /lib/pmlib. For more
information, see Section 2.3.)
Two compiler packages are available:
o The MC680x0-based workstation package contains Version 10.9.m and
Version 10.9.mpx.
o The Series 10000 workstation package contains Version 10.9.p and
Version 10.9.pmx.
Table 2-1 shows the four variants of Domain FORTRAN Version 10.9.
Table 2-1. Domain FORTRAN Compiler Variants
Variant Runs_on Generates_Code_For
Version 680x0-based 680x0-based
10.9.m workstations workstations
Version 680x0-based Series 10000
10.9.mpx workstations workstations
Version Series 10000 Series 10000
10.9.p workstations workstations
Version Series 10000 680x0-based
10.9.pmx workstations workstations
Domain FORTRAN 7 Version 10.9
You can install the whole package or a single compiler version. The media
for an MC680x0-based workstation contains the products listed in Table 2-2.
Table 2-2. Media Contents for MC680x0-Based Workstation
Product Version Selection_Files Override_Files
ftn 10.9.m aa.ftn ov.ftn
ftn 10.9.mpx aa.ftn ov.ftn
The media for a Series 10000 workstation contains the products listed in
Table 2-3.
Table 2-3. Media Contents for Series 10000 Workstation
Product Version Selection_Files Override_Files
ftn 10.9.p aa.ftn ov.ftn
ftn 10.9.pmx aa.ftn ov.ftn
You can install the whole package or a single compiler version. Table 2-4
lists the amount of disk space required for the various versions.
Table 2-4. Disk Storage Requirements
Version(s) Blocks_Required
ftn.m 1905
ftn.mpx 4096
both ftn.m and ftn.mpx 5461
ftn.p 5522
ftn.pmx 2526
both ftn.p and ftn.pmx 7502
Selection and override files reside in the directory
//<authorized_area>/install/templates/apollo/<product_name>.v.<version>
where <authorizedarea> is your authorized area, <productname> is the
product name (as listed in the first column of Tables 2-2 and 2-3 above), and
<version> is the version number (as listed in the second column of the Tables
2-2 and 2-3).
For directions about how to install this product and about the use of
selection and override files, see the manual "Installing Domain Software",
Order No. 008860-A03.
Domain FORTRAN 8 Version 10.9
NOTE: When you install a new version of a Domain compiler, do not use the
update subcommand with either the config or the install tool. This
subcommand does not work correctly when you install compilers.
2.1 Online Manual Pages for f77
As of Version 10.8, the installation process for the Domain FORTRAN compiler
installs the SysV and BSD manual pages for the f77 command.
The man pages are also installed as part of the Domain/OS operating system,
but the Domain/OS man pages for f77 may not be the latest ones. If you
install Domain/OS and you want to have the latest versions of the f77 man
pages, install the FORTRAN compiler after you install Domain/OS.
2.2 The mrgri Tool
Compilers that run on different machine types but produce code for the same
machine type can have their release indexes merged using the mrgri tool. For
instance, the ftn.p and the ftn.mpx compilers can be merged, yielding a
cmpexe compiler that runs on any Apollo workstation and produces code for the
Series 10000 workstation.
SR10.3 and later versions of Domain/OS include a new version of the mrgri
installation tool. The SR10.2 version of mrgri enabled you to merge only
patches with products, or to merge two products that were the same except for
different ISP types. The new version is less restrictive; it permits you to
merge any two products, assuming the products are deemed mergeable in the
products' release notes. A significant advantage of the new mrgri is the
ability to merge Product Support Kits (PSKs) with Domain/OS.
The new version of mrgri has two new command line switches: -merge and
-cmpexe. Otherwise, the command-line syntax is the same as the SR10.2
version. The -merge and -cmpexe switches are described below. For
descriptions of the other command-line options and a more comprehensive
description of mrgri, see "Installing Domain Software", Order No. 008860-A03,
and the mrgri help file in //<authorizedarea>/install/help/mrgri.hlp.
The new mrgri syntax is
mrgri { -merge | -cmpexe } [-i] -s source_AA [-t target_AA]
[-v new_version] [-p new_name] primary_product secondary_product
Domain FORTRAN 9 Version 10.9
You must use either the -merge or the -cmpexe switch:
-merge Used to merge two different products; for example, a patch with
a layered product or with Domain/OS, or a PSK with Domain/OS.
The two products to be merged must either have the same ISP type
(m68k, a88k, or cmpexe) or the primary_product must be a cmpexe
product.
-cmpexe Used to create compound (cmpexe) products; that is, to combine
two products with the same name but with different ISP types.
The two products to be combined must have different ISP types.
NOTE: mrgri checks only that the ISP types of the primary_product and
secondary_product conform to the rules described for the -merge and
-cmpexe switches; it does not check the products or product names
in any way to ensure that they can be merged successfully. Before
attempting to merge products, check the products' release notes to
determine whether the product can be merged, which versions can be
merged, and what restrictions you must follow, if any, when
installing and using the merged product.
2.3 Running Programs on SR10.1 Nodes
Domain FORTRAN Version 10.9 will not run on a 680x0-based workstation running
SR10.1. Also, if you compile and link a program on a workstation running
SR10.3 or a later version of Domain/OS, the program will not run on a
680x0-based workstation running SR10.1.
In both cases, you will receive the following error message:
absolute load address already occupied (process manager/loader)
The problem is with the SR10.1 version of /lib/pmlib. Patch_m0159 contains a
new /lib/pmlib that you can install on a workstation running SR10.1. The new
pmlib allows the workstation to run Domain FORTRAN Version 10.9 as well as
programs linked on workstations running SR10.3 or later.
Domain FORTRAN 10 Version 10.9
CHAPTER 3
Documentation
The "Domain FORTRAN Language Reference" was revised for Version 10.8. This
edition (Order No. 000530-A01) describes all features of Domain FORTRAN
through Version 10.8. This chapter describes several corrections to this
edition of the manual.
You can call the Tech Pubs Connection with questions or comments about any of
our documentation, or to find out about new manuals.
o In the USA, call 1-800-441-2909
o Outside the USA, call (508) 256-6600 ext. 4965
To order manuals, call HP Apollo DIRECT at 1-800-637-7740. Outside the USA,
call (508) 256-6600 and ask for HP/Apollo DIRECT.
3.1 Exponential Expressions
The note on p. 3-7 of the manual should read:
NOTE: In the exponential expresssion, x**n, where x is a real*4 or
real*8 and n is an integer*4, the result is unspecified if the
absolute value of n is greater than 2**16 - 1. This limitation
applies only to MC680x0-based workstations.
3.2 Length Specification for Character Variables
The manual (p. 3-11) does not mention that you can declare a character
variable as having a different length from that specified by
"character*len". The manual should show the syntax for declaring character
variables as:
character[*len] name1[*len1][...,nameN[*lenN]]
Domain FORTRAN 11 Version 10.9
where len1 (if specified) specifies a length that overrides the length
specified by character[*len]. Note that, if *len is not specified, the
default (as always) is 1.
3.3 Error Message 326
The manual does not explain the error message issued by the compiler for
Error 326. The following explains the error:
326 ERROR Argument to statement function is not the correct data type.
The data type of an actual argument to a statement function
does not match the data type of the corresponding dummy
argument. If, for example, you have relied on FORTRAN's
default naming conventions to determine the data type of a
dummy argument as an integer, the data type of the actual
argument must also an be integer.
3.4 Error Message 909
The manual does not explain the error message issued by the compiler for
Error 909. The following explains the error:
909 ERROR Compiler failure, no free disk space.
The compiler has run out of disk space and cannot finish
the compilation. If your program or subprogram is very
large, try to break it into smaller components. Also,
check the amount of free disk space on your system. If
you seem to have enough free disk space. contact either
your HP Response Center or your local HP representative.
Domain FORTRAN 12 Version 10.9
3.5 Model Numbers for -cpu mathchip Option
In Section 6.5.8 (p. 6-22), the list of workstations for which the -cpu
mathchip option generates the best code should also include the following
model number:
HP Apollo 9000 Series 400 Model 400dl
3.6 ISO Latin-1 Character Set
The note at the beginning of Appendix B should add that the characters with
decimal numbers 152 through 154 are also missing from the table because they
are reserved for future standardization. In Table B-1, the character with
decimal number 96 is a grave accent, not an apostrophe.
Domain FORTRAN 13 Version 10.9
CHAPTER 4
Bug Fixes
This chapter lists all FORTRAN Language APRs (Apollo Product Reports) that
have been fixed since Domain FORTRAN Version 10.8. It also lists the fixed
APRs that apply to all compilers included in this release.
4.1 FORTRAN Language APRs
The following fixed APRs relate just to the Domain FORTRAN compiler:
APR Description_of_Problem
000DDC16 Customer wanted FORTRAN ASFs to always behave like macros that get
expanded inline.
0890391A DN10000 compiler failed while compiling customer's code at -opt 4.
08904EBF Opening an empty include file caused the compiler to misinterpret
the remaining source code.
08905EF4 Compiling code with Domain FORTRAN compiler versions 10.7
or 10.8 caused data type errors.
08906C2C The compiler format size was too restrictive. If the format
statement contained more than 1830 characters, the progam did not
compile.
0890766A The hidden length parameters of the character definitions caused a
compile of code to fail on DN10000s.
08908334 Compiling with the -mp option caused compiler to fail.
26C6DF14 Certain FORTRAN code modules could not be compiled successfully
using the current release of the ftn compiler (version 10.8).
The error occurred when compiling with -save and -opt 3 or
-opt 4.
45CDB645 When name of an intrinsic function was used as a user defined
variable within a DATA statement, the compiler expected it to be
the intrinsic.
5B54F0B1 Uplevel references to procedure parameters in f77 resulted in a
segmentation fault.
7CF2E638 DN10000 compiler incorrectly compiled user's source at optimization
levels greater than 1. This caused the resulting program to produce
erroneous results at runtime.
Domain FORTRAN 14 Version 10.9
7D9808FF Use of a non executable label as the target of an alternate entry
was not caught by the compiler and resulted in a fatal error.
7D981646 FORTRAN cross reference information didn't display all of the lines
on which a symbol appears.
7D9816DF If the name of a function parameter matched an external symbol, the
compiler generated a call to that symbol instead of the value of
the parameter.
7D98526C When compiling two particular DATA statements with arrays with
implied DO-loops, the compiler issued incorrect diagnostic
message stating that the arrays are out of range.
7D9853B2 Static data initialization with DATA implied DO statements
caused compiler to generate spurious error messages.
7D985639 Static initialization of two-byte integers with values greater than
what is representable (32767, -32768) were not caught at compile
time.
7D986EB5 Illegal code was generated if substrings of very large strings were
concatenated.
7D987099 FORTRAN crashed at compile-time due to unanticipated intermediate
language patterns in the vectorizer phase of the optimizer.
7D987F6E An extraneous ELSE IF statement caused compiler to fault instead
of giving the correct diagnostic.
7D9885B4 Compiler silently generated bad code at -opt 4 which caused
error to be generated. Code worked correctly at optimization
level 3.
7D9888CB COMPLEX code fails when -subchk was used with optimization.
7D9888CC Leaving the IF off an ENDIF in a FORTRAN program caused
compiler to crash.
7D989BEE7 A program using "statement function statements" incurred a memory
fault when compiled on DN10000 compiler.
7D98C50B Compiler failed at -opt 3 and above, due to a cascaded error in
the optimizer.
7D98C71a Equivalencing dynamic locals with common block variables caused bad
code to be generated with optimization turned on.
7D98DFA0 Code produced an invalid character error (#176) at 10.7 but
produced a backend failure at 10.8.
7D98E67C An extraneous comma left at the end of an I/O list was not caught by
compiler.
7D98E95E The optimizer did not properly handle labels assigned to
ASSIGNED GOTO variables, causing user's code to produce incorrect
results at runtime.
7D98EB9F Array accesses within a loop were not behaving correctly, due to
corruption of a compiler-created pointer variable (a "strength-
reduction temporary").
7D98FF4C Functions which required extendtops over funccalltops were
misdiagnosed as errors by the DISCARD statement processor.
Domain FORTRAN 15 Version 10.9
4.2 FORTRAN Documentation APRs
The following APRs relating to FORTRAN documentation have been fixed:
APR Description_of_Problem
7D98D855 The f77 man pages incorrectly documented several of the -W0 and -wp
options.
4.3 Compiler APRs
The following fixed APRs pertain to all compilers in this software release:
APR Description_of_Problem
000DDD6A Optimizer did not fold an AND-over-shift into zero.
000DE01A 68k compiler failed at -opt 3 with the message: "internal error --
Procedure length exceeds 32k."
000DE3BD The procedure inliner did not properly inline an array actual
parameter into a call site.
04607F31 DDE was unable to print the values of the arguments in a parameter
list of a subroutine.
0460C41B The -pic option sometimes resulted in programs producing incorrect
results with double precision floating-point subtraction.
06AE4EA0 An application consisting largely of a huge CASE statement crashed
at runtime, even when compiled with -dba.
06AE2771 Compiler didn't generate a proper diagnostic error message if the
include file specified in the user's source program was based upon
an undefined environment variable.
06AE9627 Customer's code did not run properly at -opt 3. In particular,
a loop did not terminate as expected.
06AEC7CC Compiler failed (Error #145) when optimization was used.
089034E2 User program produced correct output with -opt 0 and -opt 1, but
produced incorrect output with -opt 2, -opt 3, and -opt 4.
08907992 Short constants (constants less than 32768) were not handled
correctly.
089079C0 On a DN10000, FORTRAN code which read data from a file and printed
it to the screen failed with a segmentation fault.
08908334 DN10000 backend failure occurred at -opt 3, and -opt 4.
0890EFDE User's code behaved incorrectly at runtime if compiled at
optimization levels greater than 2.
1584A3B1 Compiler failed (Error #904) when compiling user program with
-opt 3.
26C6DB3E The compilers did not detect when a variable was uninitialized along
some execution path.
26CCDD53 At higher levels of optimization, the order of two lines of code
was wrongly reversed.
45CD68A7 Cross reference listings only printed out 7 digits for the common
block size.
Domain FORTRAN 16 Version 10.9
45CDF8E4 The -es and -esf options, when used together, precluded binary
and/or listing options.
7C321F46 Compiler-generated code failed at runtime with an operand error in
an assignment statement.
7C32369B User program compiled with FORTRAN Version 10.7, but resulted in
backend failure with Version 10.8.
7C32EC6C Spurious warnings were generated indicating that variables had not
been initialized.
7CF2CA7F FScc instruction was broken on some 68040 chips.
7D98000C DN10000 backend failure occurred at optimization level 3.
7D980DBE Code compiled with -opt 3 failed at runtime, but worked at lower
optimization levels.
7D981181 The -cpu 3000 option produced code that failed to execute on an
FPX board.
7D9812AA The debugger was unable to print assumed size arrays.
7D98141A User program produced incorrect results when compiled with -opt 4,
but not when compiled with -opt 3.
7D9818FE DO loop in program was incorrectly optimized by the compiler.
7D981D40 Code compiled with -opt 3 generated Error #319, but not when
compiled with -opt 2.
7D981F8E Compiler failed (Error #904) when compiling user program with
-cpu any -save.
7D98239A User program compiled with FORTRAN Version 10.7 works, but produced
incorrect results with Version 10.8.
7d984506 Compiler didn't catch ANSI standard violation (reported Error #319
instead).
7D98494E Incorrect execution of floating-point comparison occurs unless
optimizer is turned off.
7D985979 The compiler crashed when optimization level 3 or higher is used.
7D985EC0 The compiler appeared to hang when attempting to compile.
7D98665E Compiler failed (Error #144) when compiling user program with
-opt 4.
7D9866A4 Compiler produced incorrect locpool symbol records for some
variables.
7D98689F Multidimension static array initialization with FORTRAN using a
DATA implied DO caused the compiler to fail.
7D986B35 The compiler warning "Relocatable address on non-word boundary"
occurred when the number of elements in a static char array was an
exact multiple of 16.
7D987099 Compiler failed with error message: "vector_transform: bad kind
for loop_trip_count."
7D98717C Program that used online example of fault handler did not work.
7D987258 User program failed at runtime (floating point divide by zero)
when compiled with both -pic and -cpu mathlib.
7D984574 User's source compiled on 68k machines, but resulted in compiler
failure ("illegal address") on DN10000s at optimization levels
greater than 1.
7D987728 User program failed when compiled with -opt 3 or higher, giving
incorrect results for complex arithmetic calculations.
7D987D84 User's optimized code (DN10000 compiler only) produced incorrect
results at runtime due to a variable in a loop having incorrect
values assigned to it.
Domain FORTRAN 17 Version 10.9
7D988040 Compiler issued spurious "use of uninitialized variable" warnings
when optimizer was enabled.
7D9882C5 User program behaved differently when compiled with -cpu mathlib
than when compiled with -cpu mathlibsr10, at -opt 1.
7D988710 Customer's code failed to execute properly when compiled with
-opt 3.
7D989877 The ftn option -i*2 resulted in Fatal Error #923.
7D989A1B Program revealed failures of the DN10000, DN4500 and DN2500.
7D98A2E7 User program produced incorrect results at any optimization
setting except -dba.
7D98A371 Error #923 occurred with default optimization, but not with
-opt 2.
7D98A6BF User's source compiled if the -save option was not specified or if
the optimization level was 2 or less, but resulted in a fatal
compiler error otherwise.
7D98ABB8 DN10000 compiler crashed with "reference to illegal address" message
when compiling at optimization levels greater than 2.
7D98B2E9 Information in cross reference listings for the first element in a
common block was incorrect.
7D98B390 User program compiled with FORTRAN Version 10.7 worked, but failed
with Version 10.8.
7D98B475 Compiler failed with the message "TR_UTILS_$autoindex_within_bb:
intend to modify opr should be last."
7D98B625 Compiler failure "lost value of node."
7D98B95A Compiler emitted spurious "use of uninitialized variable" warning
messages.
7D98BFF8 Multidimensional arrays using negative indices caused the compiler
to emit an erroneous error message.
7D98C84D The compiler failed when the limit for global variables was exceeded.
7D98CA26 Listings did not accurately reflect the -cpu settings mathlib or
mathlibsr10.
7D98D2F9 DN10000 compiler crashed with internal error when compiling at
optimization levels greater than 1.
7D98D3FC Compiler aborted when code was compiled at -opt 3 -cpu mathlib.
7D98DFB3 Arithmetic operations on short data types yielded incorrect
results.
7D98E695 Compiler aborted with an internal "registers locked" message when
compiling customer's code with both -O and -DBUILTINS switch.
7D98E710 Customer's application failed at -opt 3 and above.
7D98F36B When using DDE to debug a FORTRAN program on a DN10000, the
contents of a variable located in stack ext or save ext was wrong.
7D98F971 User program produced different output on a 68040-based node at
-opt 3 or above.
7D98FA73 Compiler failed (Error #903) when compiling user program with -opt
set at greater than 2.
Domain FORTRAN 18 Version 10.9