.\" Copyright (c) 1995-1997 Free Software Foundation -*-Text-*-
.\" See section COPYING for conditions for redistribution
.\" FIXME: no info here on predefines. Should there be? extra for F77...
-.TH G77 1 "1998-09-01" "GNU Tools" "GNU Tools"
+.TH G77 1 "1999-02-14" "GNU Tools" "GNU Tools"
.de BP
.sp
.ti \-.2i
F77 source files use the suffix `\|\c
.B .f\c
-\&\|' or `\|\c
+\&\|', `\|\c
.B .for\c
+\&\|', or `\|\c
+.B .FOR\c
\&\|'; F77 files to be preprocessed by
.BR cpp ( 1 )
use the suffix `\|\c
.B .F\c
-\&\|' or `\|\c
+\&\|', `\|\c
.B .fpp\c
+\&\|', or `\|\c
+.B .FPP\c
\&\|'; Ratfor source files use the suffix `\|\c
.B .r\c
\&\|' (though
.br
file.for Fortran source file
.br
+file.FOR Fortran source file
+.br
file.F preprocessed Fortran source file
.br
file.fpp preprocessed Fortran source file
.br
+file.FPP preprocessed Fortran source file
+.br
file.r Ratfor source file (ratfor not included)
.br
file.s assembly language file
@c %**start of header
@setfilename g77.info
-@set last-up-date 1998-09-01
+@set last-up-date 1999-02-14
@set version-g77 0.5.24
@set email-general egcs@@egcs.cygnus.com
@set email-bugs egcs-bugs@@egcs.cygnus.com
information on suffixes recognized by GNU CC.
@table @code
+@cindex .f filename suffix
+@cindex .for filename suffix
+@cindex .FOR filename suffix
@item @var{file}.f
@item @var{file}.for
+@item @var{file}.FOR
Fortran source code that should not be preprocessed.
Such source code cannot contain any preprocessor directives, such
@cindex programs, cpp
@cindex .F filename suffix
@cindex .fpp filename suffix
+@cindex .FPP filename suffix
@item @var{file}.F
@item @var{file}.fpp
+@item @var{file}.FPP
Fortran source code that must be preprocessed (by the C preprocessor
@code{cpp}, which is part of GNU CC).
@email{fortran@@gnu.org} asking for a recent copy of the
GNU Fortran @file{.plan} file.
+@heading In @code{egcs 1.2}:
+@itemize @bullet
+@item
+Source file names with the suffixes @samp{.FOR} and @samp{.FPP}
+now are recognized by @code{g77}
+as if they ended in @samp{.for} and @samp{.fpp}, respectively.
+@end itemize
+
@heading In @code{egcs} 1.1 (versus 0.5.24):
@itemize @bullet
@cindex alignment
@code{#include}, @code{#if}, and so on is likely one that
requires preprocessing.
-If the file's suffix is @samp{.f} or @samp{.for}, the file
-will normally be compiled @emph{without} preprocessing by @code{g77}.
+If the file's suffix is @samp{.f}, @samp{.for}, or @samp{.FOR},
+the file normally will be compiled @emph{without} preprocessing
+by @code{g77}.
-Change the file's suffix from @samp{.f} to @samp{.F} (or, on
-systems with case-insensitive file names, to @samp{.fpp}) or
-from @samp{.for} to @samp{.fpp}.
+Change the file's suffix from @samp{.f} to @samp{.F}
+(or, on systems with case-insensitive file names,
+to @samp{.fpp} or @samp{.FPP}),
+from @samp{.for} to @samp{.fpp},
+or from @samp{.FOR} to @samp{.FPP}.
@code{g77} compiles files with such names @emph{with}
preprocessing.
{".F", {"@f77-cpp-input"}},
{".fpp", {"@f77-cpp-input"}},
+ {".FPP", {"@f77-cpp-input"}},
{"@f77-cpp-input",
/* For f77 we want -traditional to avoid errors with, for
instance, mismatched '. Also, we avoid unpleasant surprises
%{!pipe:%g.s} %A\n }}"}},
{".f", {"@f77"}},
{".for", {"@f77"}},
+ {".FOR", {"@f77"}},
{"@f77",
{"%{!M:%{!MM:%{!E:f771 %i %(f771) \
%{!Q:-quiet} -dumpbase %b.f %{d*} %{m*} %{a}\