SEARCH CONTACT US SUPPORT SERVICES PRODUCTS STORE
United States    
COMPAQ STORE | PRODUCTS | SERVICES | SUPPORT | CONTACT US | SEARCH
gears
compaq support options
support home
software & drivers
ask Compaq
reference library
support forum
frequently asked questions
support tools
warranty information
service centers
contact support
product resources
parts for your system
give us feedback
associated links
.
} what's new
.
} contract access
.
} browse patch tree
.
} search patches
.
} join mailing list
.
} feedback
.
patches by topic
.
} DOS
.
} OpenVMS
.
} Security
.
} Tru64 Unix
.
} Ultrix 32
.
} Windows
.
} Windows NT
.
connection tools
.
} nameserver lookup
.
} traceroute
.
} ping
DEC Fortran FORTECO02062 DEC Fortran V6.2 for OpenVMS VAX ECO Summary

Copyright (c) Digital Equipment Corporation 1994. All rights reserved. PRODUCT: DEC Fortran for OpenVMS VAX OP/SYS: OpenVMS VAX SOURCE: Digital Equipment Corporation ECO INFORMATION: ECO Kit Name: FORTECO02062 ECO Kits Superseded by This ECO Kit: FORTECO01062 (CSCPAT_0424) ECO Kit Approximate Size: 7380 Blocks Kit Applies To: DEC Fortran V6.2 for OpenVMS VAX OpenVMS VAX V5.4 and higher System Reboot Necessary: No ECO KIT SUMMARY: An ECO kit exists for DEC Fortran V6.2 for OpenVMS VAX on OpenVMS VAX V5.4 or higher. This kit addresses the following problems: Problems addressed in the FORTECO01062 Kit: V6.2-109 The compiler no longer issues spurious VARUNUSED diagnostics for a POINTER variable which is an actual argument or in COMMON if one of its pointees is used. V6.2-110 The compiler's checking for uninitialized variables has been improved to include variables which have not been selected for full analysis (a maximum of 128 variables are selected) but which have no stores in the program unit. V6.2-111 The compiler no longer allocates an unnecessary longword of storage when a record array declaration is seen. V6.2-112 The compiler no longer improperly processes constants of the form B'xxx', O'xxx', X'xxx' and Z'xxx' when the constant string includes embedded blanks or tabs (for example: X'123 45'). Also, the compiler no longer issues a CHACONCONTD diagnostic if a constant of the form 'xxx'X, etc. is continued across multiple source lines. V6.2-113 The compiler no longer fails with a bugcheck during the LEXSYN phase when a logical-IF contains a statement which would, if it appeared on its own, cause an "unrecognized statement" error. V6.2-114 The compiler no longer fails with a bugcheck during the PACK phase when the following combination occurs: 1) Use of the SIN, COS, TAN, ATAN, LOG, LOG10, EXP or SQRT intrinsics 2) The argument to the intrinsic is of a COMPLEX type 3) The compile command qualifiers /VECTOR and /MATH_LIBRARY=FAST were both specified Note that the /MATH_LIBRARY=FAST qualifier is documented to have an effect for real datatypes only. V6.2-115 The compiler no longer generates incorrect SCA analysis data information for a main program which begins with a DATA, DEFINE FILE, FORMAT or NAMELIST statement. In addition, the compiler now generates correct SCA typing information for variables whose first appearance is in a NAMELIST statement which occurs in the executable part of a program. V6.2-116 The compiler no longer fails with a bugcheck during the LEXSYN phase under extremely rare and unpredictable circumstances while processing an actual argument list. V6.2-117 The compiler no longer fails with a bugcheck during the LIFE phase for certain programs which have an array reference as a DO-loop bound. V6.2-118 The compiler no longer emits bounds checking code for expanded BLAS routines, even if /CHECK=BOUNDS is in effect. The bounds checking code interfered with the common use of passing multiple-dimension arrays to certain BLAS routines (for example, DSET). V6.2-119 The compiler no longer generates incorrect code for loading the argument to certain COMPLEX*16 intrinsic functions such that the address of the argument was overwritten by the real part of the argument. Problems addressed in the FORTECO02062 Kit: V6.2-120 The compiler now correctly flags as an extension the use of the INTEGER*1, LOGICAL*2 and REAL*16 types in an INTRINSIC statement when /STANDARD=MIA is in effect. V6.2-121 The compiler no longer fails with a bugcheck during the FINAL phase when a %LOC function or LOC intrinsic makes a recursive reference to the enclosing subroutine or function when the generated instruction for that reference is more than 128 bytes away from the routine entry point. Also the compiler now correctly issues the ROUREFREC diagnostic if such recursive reference occurs but the /RECURSIVE qualifier was not specified. V6.2-122 The compiler no longer issues a USEUNIVAR for the use of a character variable which was partially defined by having had a substring passed as an actual argument. V6.2-123 The compiler no longer disallows the lowercase letters 'a' through 'f' in prefix-style hexadecimal constants (eg. X'123abc'). V6.2-124 The compiler now gives the ASSDOVAR warning if a DO- loop control variable appears as an IOSTAT specifier in an I/O statement inside a DO loop. V6.2-125 The compiler now properly sign-extends bit constants when used in contexts where they are treated as INTEGER*2 or BYTE types. NOTE: For further details, see Section 1.1.1.5 of the release notes. V6.2-126 The compiler no longer gives an INVLEXEME error when a record field array is used as the buffer in an ENCODE or DECODE statement. V6.2-127 The compiler no longer fails with a bugcheck during the CODE phase for certain programs which use inlined BLAS intrinsics and are compiled /CHECK=BOUNDS. V6.2-128 The compiler now emits the correct DEBUG symbol table information for untyped (non-Fortran-77) PARAMETER constants whose value is a bit constant longer than 32 bits so that these values may be evaluated during a DEBUG session. V6.2-129 The compiler now supports /DEBUG=PARAMETERS=NONE. If this is specified, no PARAMETER constants are written to the debug symbol table. Note that /DEBUG=NOSYMBOLS prevents any debug symbol information, including PARAMETER constants, from being written. V6.2-130 The compiler now supports the command line keywords /WARNINGS=[NO]INFORMATIONAL and /ASSUME=[NO]SOURCE_ INCLUDE. V6.2-131 The compiler no longer fails with a bugcheck during the CODE phase when a pointee non-adjustable array is passed by descriptor. V6.2-132 The compiler no longer issues a VARUNUSED diagnostic for pointees. INSTALLATION NOTES: The system/cluster does not need to be rebooted after this kit is installed. If this kit is being installed on a VMScluster system, the command procedure SYS$UPDATE:FORTRAN$POST_INSTALL.COM must be run on every VAX member of the cluster so that the updated compiler and command tables are available to all users.



This patch can be found at any of these sites:

Colorado Site
Georgia Site



Files on this server are as follows:

forteco02062.README
forteco02062.CHKSUM
forteco02062.a-dcx_vaxexe

privacy and legal statement