Section 1: Parameters

 Options

 Indicates either special actions to be performed by the compiler or
 linker, or special properties of input or output files.

 If you specify more than one option, separate each option with a
 space.

 Certain options have the format of -option "keyword", where the
 "keyword" can be abbreviated to its shortest unique prefix.  For
 example, -assume noaccuracy can be abbreviated as -assume noac.

 For more information about command line options, see f77(1).  If
 you are using LSE, you can see f77(1) by entering the following
 command at the LSE prompt:

    LSE> cli man f77

 Filename

 Specifies one (or more) source programs to be compiled.  If you
 specify more than one filename, separate each filename with a
 space.

 The f77 command interprets filename suffixes as follows:

  o  The suffixes .f, .for, or .FOR are interpreted as FORTRAN-77
     source programs.  These programs are compiled, and the name of
     the resulting object program is the basename of the source file
     with a .o substituted for the .f, .for, or .FOR.  (For example,
     in source file myfile.f, myfile is the basename; therefore, the
     object program is named myfile.o.) If the source program is
     compiled and loaded, the .o file is deleted.

  o  The suffix .F is interpreted as a FORTRAN source program which
     must be processed by the C preprocessor (cpp(1)) before being
     compiled.

  o  The suffixes .r or .e are interpreted as ratfor or efl source
     programs, respectively.  These programs are first transformed
     by the appropriate preprocessor and then compiled.

  o  The suffix .i is interpreted as a FORTRAN-77 source program
     that has been preprocessed by cpp(1).  It is compiled without
     further preprocessing.

  o  The suffixes .o or .a are interpreted as object files or
     archive libraries, respectively.  Object files are passed to
     the ld linker.  Archive libraries are searched by the ld
     linker.

 If you omit a filename suffix (or the suffix is not .f, .for, .FOR,
 or .o), the compiler assumes the file is an object file and passes
 it directly to the linker.

 When a source program requires preprocessing by cpp(1), efl(1),
 ratfor(1), or m4(1), the name of the output file generated by the
 preprocessor consists of the basename of the source input file with
 the appropriate preprocessor suffix.  For example:

     m4     myfile.r =>  myfile.p
     efl    myfile.e =>  myfile.f 
     ratfor myfile.r =>  myfile.f
     cpp    myfile.F =>  myfile.i

 Note that if you have myfile.F and myfile.f as distinct files,
 cpp(1) overwrites myfile.f to produce an output file with the same
 name.

 Depending on which platform you are using, the f77 command defines
 the following cpp(1) macros to cpp(1):

  o  All platforms:  LANGUAGE_FORTRAN, __LANGUAGE_FORTRAN__, unix,
     __unix__

  o  RISC only:  host_mips, __host_mips__

  o  AXP only:  __alpha

  o  DEC OSF/1 only:  __osf__

  o  RISC DEC OSF/1 only:  mips=1, __mips__=1

  o  RISC ULTRIX only:  MIPSEL, mips, __mips__


 For example, if you are using an AXP DEC OSF/1 system, the
 following cpp(1) macros are defined to cpp(1):  LANGUAGE_FORTRAN,
 __LANGUAGE_FORTRAN__, unix, __unix__, __alpha, and __osf__.