There is 1 other file named revhst.c13 in the archive. Click here to see a list.
REP 3/1 ;13C1
TITLE REVHST 10(2546) Revision History for the FORTRAN compiler
SUBTTL Authors: DCE/TFV/EGM/SRM/EDS/CKS/AHM/CDM/RVM/PLB/TJK/AlB/MEM/JB 5-Sep-85
TITLE REVHST 10(2564) Revision History for the FORTRAN compiler
SUBTTL Authors: DCE/TFV/EGM/SRM/EDS/CKS/AHM/CDM/RVM/PLB/TJK/AlB/MEM/JB 17-Dec-85
REP 6391/1 ;13C2
;.EDIT 2550 DEFINITION PTS INCORRECTLY HANDLES STMT FUNCTIONS
;; Only parameters of a statement function were used to calculate the
;; definition points of variables, however, the body of the statement
;; function must be used in definition point calculations also. A
;; variable, other than a parameter to the statement function, may be
;; changed by itself being a parameter in a function call within the
;; statement function.
; A:SRC DEFPT.BLI,REVHST.MAC
;.EDIT 2551 NEG FLAG LOST DURING COMMON SUB ELIMINATION
;; The expression -(-X+Y)+Z was transformed into X+(Y+Z) because when
;; Y and Z were put together only the flags immediately in front of them
;; were carried along. Any flags on the plus node above the Y must be
;; XORed together with Y's flags to get the new flags for Y in the
;; new expression.
; A:SRC COMSUB.BLI
;.EDIT 2552 RECTYPE ACCEPTED AS OPEN SPECIFIER
;; Removed RECTYPE as an accepted abbreviation for RECORDTYPE.
; A:SRC STA1.BLI
;;.EDIT 2553 RESERVED FOR AUTOPATCH
;.EDIT 2554 SFN WITH A USER FNCALL CAUSES BAD CODE
;; When a SFN calls a user function and passes it a non-formal variable
;; which the user function changes, then any registers containing the
;; the old value of the non-formal can not be used in place of the
;; variable in the following statements - call VARCLOBB on all such
; A:SRC REGAL2.BLI
;;.EDIT 2555 RESERVED FOR AUTOPATCH
;;.EDIT 2556 RESERVED FOR AUTOPATCH
;.EDIT 2557 ALLOW GENERIC FUNCTION NAMES IN INTRINSIC STATEMENTS
;; Check for the use of specific function names in argument lists
;; instead of in INTRINSIC statements.
; A:SRC EXPRES.BLI,STA0.BLI,STA3.BLI
;.EDIT 2560 SOME CONTINUATION LINES IGNORED
;; When a source line is continued onto several lines, CHARPOS must be
;; set back to the beginning of the line. If CHARPOS is left pointing
;; to the end of the line, then everything on that line will be ignored.
; A:SRC LEXICA.BLI
;.EDIT 2561 PROAR. AND PROSB. FLAGGED BY IMPLICIT NONE
;; When using IMPLICIT NONE with /DEBUG:BOUNDS or /DEBUG:ALL, PROAR.
;; and PROSB. get warnings for not being explicitly defined. We are
;; now making sure that the compiler knows they are library functions
;; and not user symbols.
; A:SRC ARRXPN.BLI
;.EDIT 2562 INCORRECT WARNINGS WITH IMPLICIT NONE
;; When using IMPLICIT NONE, a symbol in an EXTERNAL statement gets a
;; warning that it must be explicitly declared. If the symbol isn't
;; used as a function in the same program it shouldn't get the warning
;; because function types must be explicitly declared, whereas
;; subroutines needn't be. We added a check for this.
; A:SRC ACT1.BLI,OUTMOD.BLI
;.EDIT 2563 SPURIOUS IBIT IN MOVEM STORING FORMAL SBPGM INTO DUMMY ARG
;; When a subprogram has a subprogram name as a formal parameter, the
;; the indirect bit is set in the STE for the subprogram name after the
;; address of the subprogram has been moved into the dummy argument.
;; However, if this subprogram has an entry statement (also passing the
;; subprogram name as a parameter) the indirect bit in the STE must be
;; ignored when moving the address of the subprogram into the dummy
; A:SRC CGDO.BLI
;;.EDIT 2564 RESERVED FOR AUTOPATCH
REP 6406/1 ;13C3
EDNUM==2546 ;EDIT NUMBER
EDNUM==2564 ;EDIT NUMBER