Looking forward to the results!
No luck so far getting CPMDEC.FOR compiled.
Struggling with trying to get a compiler generated.
Various errors trying to use FORGEN. Here's a session:
.DIR FW0:
05-Oct-99
FORGEN.COM 1 05-Sep-77 FROOT .OBJ 4 04-Sep-77
F0 .OBJ 13 31-Aug-77 F1 .OBJ 9 31-Aug-77
F2 .OBJ 9 31-Aug-77 F3 .OBJ 11 31-Aug-77
F4 .OBJ 9 31-Aug-77 F5 .OBJ 18 31-Aug-77
F6 .OBJ 10 31-Aug-77 F7 .OBJ 12 31-Aug-77
F8 .OBJ 13 02-Sep-77 F9 .OBJ 13 31-Aug-77
F10 .OBJ 6 31-Aug-77 F11 .OBJ 9 31-Aug-77
F12 .OBJ 10 31-Aug-77 F13 .OBJ 17 04-Sep-77
F14 .OBJ 16 04-Sep-77 F15 .OBJ 15 31-Aug-77
F16 .OBJ 14 31-Aug-77 F17 .OBJ 14 31-Aug-77
LOOP .OBJ 18 04-Sep-77 CONVRT.OBJ 24 31-Aug-77
REGALO.OBJ 26 04-Sep-77 F21 .OBJ 15 31-Aug-77
F20 .OBJ 34 31-Aug-77 F19 .OBJ 20 31-Aug-77
PEEP .OBJ 17 02-Sep-77 OBJGSD.OBJ 22 31-Aug-77
F18 .OBJ 28 31-Aug-77 CDUMP .OBJ 26 04-Sep-77
THREAD.OBJ 1 17-Jul-77 INLINE.OBJ 1 05-Sep-77
FORTRA.HLP 5 13-Aug-77 DEMO .FOR 3 08-Aug-77
FORGEN.SAV 20 05-Sep-77 F4LINK.COM 1 18-Jul-77
F4LINL.COM 1 18-Jul-77 F4LTHR.COM 1 18-Jul-77
38 Files, 486 Blocks
0 Free blocks
.TYPE FW0:FORTRA.HLP
FORTRAN IV V2 Switches
/ALLOCATE:n - Used after the /OBJECT or /LIST option to
guarantee space for a maximum file size of
n blocks
/CODE:xxx /I Selects type of object code to be generated:
EAE selects EAE hardware
EIS selects EIS hardware
FIS selects EIS and FIS hardware
THR selects threaded code
/DIAGNOSE /B Enables expanded listings of compiler
diagnostic information
/EXTEND /E Accept source input in columns 73-80
/HEADER /O Prints Options-In-Effect
/I4 /T Default to two word integers (I*4)
/LINENUMBERS - Include ISNs for routine diagnostics (default)
/LIST:filespec - Generate a listing
/NOLINENUMBERS /S Suppress generation of ISNs
/NOOBJECT - Does not produce an object module
/NOOPTIMIZE:xxx /M:xxx Disable optimizations:
SPD disable optimization for speed
(optimize for program size)
CSE disable common subexpression
elimination
BND disable global register binding
for inline code
STR disable strength reduction
(loop optimizations)
PEP disable peephole optimizer
(inline code only)
/NOSWAP /U Disable USR swapping at runtime
/NOVECTORS /V Suppress array vectoring of multi-dimensional
arrays
/OBJECT:filespec - Produce an object file (default)
/ONDEBUG /D Compile lines with a D in column one
/OPTIMIZE:xxx /P:xxx Enable certain optimizations.
Parameters are same as /NOOPTIMIZE
/RECORD:n /R:n Specify maximum record length (4 <= n <= 4095)
/SHOW:n /L:n Specify listing options:
0 list diagnostics
only
1 or SRC list source and
diagnostics only
2 or MAP list storage map
and diagnostics only
4 or COD list generated code
and diagnostics only
7 or ALL list source, map, code,
and diagnostics
/STATISTICS /A Print compilation statistics
/SWAP - Allow USR to swap over FORTRAN program (default)
/UNITS:n /N:n Allow a maximum of n runtime I/O channels open
simultaneously (1 <= n <= 15)
/VECTORS - Allow array vectoring (default)
/WARNINGS /W Enable compiler warning diagnostics
- /H Print this text
- /Q Disable logging of program units
- /X:xxx Cross compile for indicated system:
RT selects RT11
RST selects RSTS/E
RSX selects RSX
- /Z Cause pure code and data sections to
take RO attribute
.TYPE FW0:FORGEN.COM
! ** COMPILER INSTALLATION COMMAND FILE **
!
! COPY COMPILER FILES FROM INP: TO OUP: AND SY:
!
R PIP
SY:*.*=INP:FORTRA.HLP,DEMO.FOR,F4L*.COM
^C
!
! RUN THE COMPILER CONFIGURATION PROGRAM
!
RU INP:FORGEN
@FORBLD
DEL SY:F4L*.COM/NOQ
.RUN FW0:FORGEN
Answer questions with:
"?" or carriage return (<CR>) for information,
YES(Y) for affirmation, anything else for NO.
A maximum of 56 lines are allowed per listing page.
Is this acceptable? Y
A maximum of 136 characters are allowed in a formatted
(ASCII) record. Is this acceptable? Y
A maximum of 6 channels may be open at a given time.
Is this acceptable? Y
The FORTRAN compiler can compile system-specific OPEN and CLOSE
statement keywords for RT-11, RSX-11, and RSTS/E systems. These
statements are currently compiled for the following system: RT-11
Is this acceptable? Y
FORTRAN can produce inline code for EAE, EIS or FIS hardware,
or it can produce threaded (THR) code which is hardware independent.
Should the compiler produce EAE code? NO
Should the compiler produce EIS code? NO
Should the compiler produce FIS code? NO
Should the compiler produce THR code? NO
FORTRAN can produce inline code for EAE, EIS or FIS hardware,
or it can produce threaded (THR) code which is hardware independent.
Should the compiler produce EAE code? NO
Should the compiler produce EIS code? YES
The inline compiler can optimize for SPEED or for SIZE. These
optimizations are mutually exclusive. Do you want
the optimization to be for SPEED? Y
Do you wish an inline only compiler? N
?Err 27
in routine ".MAIN." line ?
.