Automatically generated by Pod::Man v1.37, Pod::Parser v1.14

Standard preamble:
========================================================================

\\$1

.. ..

..

.. Set up some character translations and predefined strings. \*(-- will
give an unbreakable dash, \*(PI will give pi, \*(L" will give a left
double quote, and \*(R" will give a right double quote. | will give a
real vertical bar. \*(C+ will give a nicer C++. Capital omega is used to
do unbreakable dashes and therefore won't be available. \*(C` and \*(C'
expand to `' in nroff, nothing in troff, for use with C<>.
.tr \(*W-|\(bv\*(Tr . ds -- \(*W- . ds PI pi . if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch . if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\" diablo 12 pitch . ds L" "" . ds R" "" . ds C` "" . ds C' "" 'br\} . ds -- \|\(em\| . ds PI \(*p . ds L" `` . ds R" '' 'br\}
If the F register is turned on, we'll generate index entries on stderr for
titles (.TH), headers (.SH), subsections (.Sh), items (.Ip), and index
entries marked with X<> in POD. Of course, you'll have to process the
output yourself in some meaningful fashion.
. de IX . tm Index:\\$1\t\\n%\t"\\$2" .. . nr % 0 . rr F .\}
For nroff, turn off justification. Always turn off hyphenation; it makes
way too many mistakes in technical documents.

Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
Fear. Run. Save yourself. No user-serviceable parts.
. \" fudge factors for nroff and troff . ds #H 0 . ds #V .8m . ds #F .3m . ds #[ \f1 . ds #] .\} . ds #H ((1u-(\\\\n(.fu%2u))*.13m) . ds #V .6m . ds #F 0 . ds #[ \& . ds #] \& .\} . \" simple accents for nroff and troff . ds ' \& . ds ` \& . ds ^ \& . ds , \& . ds ~ ~ . ds / .\} . ds ' \\k:\h'-(\\n(.wu*8/10-\*(#H)'\'\h"|\\n:u" . ds ` \\k:\h'-(\\n(.wu*8/10-\*(#H)'\`\h'|\\n:u' . ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'^\h'|\\n:u' . ds , \\k:\h'-(\\n(.wu*8/10)',\h'|\\n:u' . ds ~ \\k:\h'-(\\n(.wu-\*(#H-.1m)'~\h'|\\n:u' . ds / \\k:\h'-(\\n(.wu*8/10-\*(#H)'\z\(sl\h'|\\n:u' .\} . \" troff and (daisy-wheel) nroff accents . \" corrections for vroff . \" for low resolution devices (crt and lpr) \{\ . ds : e . ds 8 ss . ds o a . ds d- d\h'-1'\(ga . ds D- D\h'-1'\(hy . ds th \o'bp' . ds Th \o'LP' . ds ae ae . ds Ae AE .\} ========================================================================

Title "GFORTRAN 1" gfortran - GNU Fortran compiler Header "SYNOPSIS" gfortran [-c|-S|-E] [-g] [-pg] [-Olevel] [-Wwarn...] [-pedantic] [-Idir...] [-Ldir...] [-Dmacro[=defn]...] [-Umacro] [-foption...] [-mmachine-option...] [-o outfile] infile...

Only the most useful options are listed here; see below for the remainder.

Header "DESCRIPTION" The gfortran command supports all the options supported by the \fBgcc command. Only options specific to \s-1GNU\s0 Fortran are documented here.

All \s-1GCC\s0 and \s-1GNU\s0 Fortran options are accepted both by gfortran and by gcc (as well as any other drivers built at the same time, such as g++), since adding \s-1GNU\s0 Fortran to the \s-1GCC\s0 distribution enables acceptance of \s-1GNU\s0 Fortran options by all of the relevant drivers.

In some cases, options have positive and negative forms; the negative form of -ffoo would be -fno-foo. This manual documents only one of these two forms, whichever one is not the default.

Header "OPTIONS" Here is a summary of all the options specific to \s-1GNU\s0 Fortran, grouped by type. Explanations are in the following sections. Item "Fortran Language Options" \fB-fall-intrinsics -ffree-form -fno-fixed-form \-fdollar-ok -fimplicit-none -fmax-identifier-length \-std=std -fd-lines-as-code -fd-lines-as-comments \-ffixed-line-length-n -ffixed-line-length-none \-ffree-line-length-n -ffree-line-length-none \-fdefault-double-8 -fdefault-integer-8 -fdefault-real-8 \-fcray-pointer -fopenmp -frange-check -fno-backslash Item "Error and Warning Options" \fB-fmax-errors=n \fB-fsyntax-only -pedantic -pedantic-errors \-w -Wall -Waliasing -Wampersand -Wcharacter-truncation -Wconversion \-Wimplicit-interface -Wline-truncation -Wnonstd-intrinsics -Wsurprising \-Wno-tabs -Wunderflow -W Item "Debugging Options" \fB-fdump-parse-tree -ffpe-trap=list Item "Directory Options" \fB-Idir -Jdir -Mdir Item "Runtime Options" \fB-fconvert=conversion -frecord-marker=length \fB-fmax-subrecord-length=length Item "Code Generation Options" \fB-fno-automatic -ff2c -fno-underscoring \-fsecond-underscore \-fbounds-check -fmax-stack-var-size=n \fB-fpack-derived -frepack-arrays -fshort-enums .Sh "Options Controlling Fortran Dialect" Subsection "Options Controlling Fortran Dialect" The following options control the details of the Fortran dialect accepted by the compiler: Item "-ffree-form"

0

Item "-ffixed-form"

Specify the layout used by the source file. The free form layout was introduced in Fortran 90. Fixed form was traditionally used in older Fortran programs. When neither option is specified, the source form is determined by the file extension.

Item "-fall-intrinsics" Accept all of the intrinsic procedures provided in libgfortran without regard to the setting of -std. In particular, this option can be quite useful with -std=f95. Additionally, \fBgfortran will ignore -Wnonstd-intrinsics. Item "-fd-lines-as-code"

0

Item "-fd-lines-as-comments"

Enable special treatment for lines beginning with \*(C`d\*(C' or \*(C`D\*(C' in fixed form sources. If the -fd-lines-as-code option is given they are treated as if the first column contained a blank. If the \fB-fd-lines-as-comments option is given, they are treated as comment lines.

Item "-fdefault-double-8" Set the \*(C`DOUBLE PRECISION\*(C' type to an 8 byte wide type. Item "-fdefault-integer-8" Set the default integer and logical types to an 8 byte wide type. Do nothing if this is already the default. Item "-fdefault-real-8" Set the default real type to an 8 byte wide type. Do nothing if this is already the default. Item "-fdollar-ok" Allow $ as a valid character in a symbol name. Item "-fno-backslash" Change the interpretation of backslashes in string literals from \*(L"C-style\*(R" escape characters to a single backslash character. Item "-ffixed-line-length-n" Set column after which characters are ignored in typical fixed-form lines in the source file, and through which spaces are assumed (as if padded to that length) after the ends of short fixed-form lines. .Sp Popular values for n include 72 (the standard and the default), 80 (card image), and 132 (corresponding to \*(L"extended-source\*(R" options in some popular compilers). \fIn may also be none, meaning that the entire line is meaningful and that continued character constants never have implicit spaces appended to them to fill out the line. \fB-ffixed-line-length-0 means the same thing as \fB-ffixed-line-length-none. Item "-ffree-line-length-n" Set column after which characters are ignored in typical free-form lines in the source file. The default value is 132. \fIn may be none, meaning that the entire line is meaningful. \fB-ffree-line-length-0 means the same thing as \fB-ffree-line-length-none. Item "-fmax-identifier-length=n" Specify the maximum allowed identifier length. Typical values are 31 (Fortran 95) and 63 (Fortran 2003). Item "-fimplicit-none" Specify that no implicit typing is allowed, unless overridden by explicit \f(CW\*(C`IMPLICIT\*(C' statements. This is the equivalent of adding \f(CW\*(C`implicit none\*(C' to the start of every procedure. Item "-fcray-pointer" Enable the Cray pointer extension, which provides C-like pointer functionality. Item "-fopenmp" Enable the OpenMP extensions. This includes OpenMP \*(C`!$omp\*(C' directives in free form and \*(C`c$omp\*(C', *$omp and \*(C`!$omp\*(C' directives in fixed form, \f(CW\*(C`!$\*(C' conditional compilation sentinels in free form and \*(C`c$\*(C', \*(C`*$\*(C' and \*(C`!$\*(C' sentinels in fixed form, and when linking arranges for the OpenMP runtime library to be linked in. Item "-frange-check" Enable range checking on results of simplification of constant expressions during compilation. For example, by default, \s-1GNU\s0 Fortran will give an overflow error at compile time when simplifying \*(C`a = EXP(1000)\*(C'. With -fno-range-check, no error will be given and the variable \*(C`a\*(C' will be assigned the value \*(C`+Infinity\*(C'. Similarly, \*(C`DATA i/Z'FFFFFFFF'/\*(C' will result in an integer overflow on most systems, but with -fno-range-check the value will \*(L"wrap around\*(R" and \*(C`i\*(C' will be initialized to -1 instead. Item "-std=std" Specify the standard to which the program is expected to conform, which may be one of f95, f2003, gnu, or legacy. The default value for std is gnu, which specifies a superset of the Fortran 95 standard that includes all of the extensions supported by \s-1GNU\s0 Fortran, although warnings will be given for obsolete extensions not recommended for use in new code. The legacy value is equivalent but without the warnings for obsolete extensions, and may be useful for old non-standard programs. The f95 and \fBf2003 values specify strict conformance to the Fortran 95 and Fortran 2003 standards, respectively; errors are given for all extensions beyond the relevant language standard, and warnings are given for the Fortran 77 features that are permitted but obsolescent in later standards. .Sh "Options to Request or Suppress Errors and Warnings" Subsection "Options to Request or Suppress Errors and Warnings" Errors are diagnostic messages that report that the \s-1GNU\s0 Fortran compiler cannot compile the relevant piece of source code. The compiler will continue to process the program in an attempt to report further errors to aid in debugging, but will not produce any compiled output.

Warnings are diagnostic messages that report constructions which are not inherently erroneous but which are risky or suggest there is likely to be a bug in the program. Unless -Werror is specified, they do not prevent compilation of the program.

You can request many specific warnings with options beginning -W, for example -Wimplicit to request warnings on implicit declarations. Each of these specific warning options also has a negative form beginning -Wno- to turn off warnings; for example, -Wno-implicit. This manual lists only one of the two forms, whichever is not the default.

These options control the amount and kinds of errors and warnings produced by \s-1GNU\s0 Fortran:

Item "-fmax-errors-n" Limits the maximum number of error messages to n, at which point \s-1GNU\s0 Fortran bails out rather than attempting to continue processing the source code. If n is 0, there is no limit on the number of error messages produced. Item "-fsyntax-only" Check the code for syntax errors, but don't do anything beyond that. Item "-pedantic" Issue warnings for uses of extensions to Fortran 95. \fB-pedantic also applies to C-language constructs where they occur in \s-1GNU\s0 Fortran source files, such as use of \ee in a character constant within a directive like \*(C`#include\*(C'. .Sp Valid Fortran 95 programs should compile properly with or without this option. However, without this option, certain \s-1GNU\s0 extensions and traditional Fortran features are supported as well. With this option, many of them are rejected. .Sp Some users try to use -pedantic to check programs for conformance. They soon find that it does not do quite what they want---it finds some nonstandard practices, but not all. However, improvements to \s-1GNU\s0 Fortran in this area are welcome. .Sp This should be used in conjunction with -std=f95 or \fB-std=f2003. Item "-pedantic-errors" Like -pedantic, except that errors are produced rather than warnings. Item "-w" Inhibit all warning messages. Item "-Wall" Enables commonly used warning options pertaining to usage that we recommend avoiding and that we believe are easy to avoid. This currently includes -Waliasing, \fB-Wampersand, -Wsurprising, -Wnonstd-intrinsics, \fB-Wno-tabs, and -Wline-truncation. Item "-Waliasing" Warn about possible aliasing of dummy arguments. Specifically, it warns if the same actual argument is associated with a dummy argument with \f(CW\*(C`INTENT(IN)\*(C' and a dummy argument with \*(C`INTENT(OUT)\*(C' in a call with an explicit interface. .Sp The following example will trigger the warning. .Sp .Vb 7 interface subroutine bar(a,b) integer, intent(in) :: a integer, intent(out) :: b end subroutine end interface integer :: a .Ve .Sp .Vb 1 call bar(a,a) .Ve Item "-Wampersand" Warn about missing ampersand in continued character constants. The warning is given with -Wampersand, -pedantic, -std=f95, and \fB-std=f2003. Note: With no ampersand given in a continued character constant, \s-1GNU\s0 Fortran assumes continuation at the first non-comment, non-whitespace character after the ampersand that initiated the continuation. Item "-Wcharacter-truncation" Warn when a character assignment will truncate the assigned string. Item "-Wconversion" Warn about implicit conversions between different types. Item "-Wimplicit-interface" Warn if a procedure is called without an explicit interface. Note this only checks that an explicit interface is present. It does not check that the declared interfaces are consistent across program units. Item "-Wnonstd-intrinsics" Warn if the user tries to use an intrinsic that does not belong to the standard the user has chosen via the -std option. Item "-Wsurprising" Produce a warning when \*(L"suspicious\*(R" code constructs are encountered. While technically legal these usually indicate that an error has been made. .Sp This currently produces a warning under the following circumstances: Item "-Wtabs" By default, tabs are accepted as whitespace, but tabs are not members of the Fortran Character Set. -Wno-tabs will cause a warning to be issued if a tab is encountered. Note, -Wno-tabs is active for -pedantic, -std=f95, -std=f2003, and \fB-Wall. Item "-Wunderflow" Produce a warning when numerical constant expressions are encountered, which yield an \s-1UNDERFLOW\s0 during compilation. Item "-Werror" Turns all warnings into errors. Item "-W" Turns on \*(L"extra warnings\*(R" and, if optimization is specified via -O, the -Wuninitialized option. (This might change in future versions of \s-1GNU\s0 Fortran.)

Some of these have no effect when compiling programs written in Fortran. .Sh "Options for Debugging Your Program or \s-1GNU\s0 Fortran" Subsection "Options for Debugging Your Program or GNU Fortran" \s-1GNU\s0 Fortran has various special options that are used for debugging either your program or the \s-1GNU\s0 Fortran compiler.

Item "-fdump-parse-tree" Output the internal parse tree before starting code generation. Only really useful for debugging the \s-1GNU\s0 Fortran compiler itself. Item "-ffpe-trap=list" Specify a list of \s-1IEEE\s0 exceptions when a Floating Point Exception (\s-1FPE\s0) should be raised. On most systems, this will result in a \s-1SIGFPE\s0 signal being sent and the program being interrupted, producing a core file useful for debugging. list is a (possibly empty) comma-separated list of the following \s-1IEEE\s0 exceptions: invalid (invalid floating point operation, such as \*(C`SQRT(-1.0)\*(C'), zero (division by zero), overflow (overflow in a floating point operation), \fBunderflow (underflow in a floating point operation), \fBprecision (loss of precision during operation) and denormal (operation produced a denormal value). .Sh "Options for Directory Search" Subsection "Options for Directory Search" These options affect how \s-1GNU\s0 Fortran searches for files specified by the \*(C`INCLUDE\*(C' directive and where it searches for previously compiled modules.

It also affects the search paths used by cpp when used to preprocess Fortran source.

Item "-Idir" These affect interpretation of the \*(C`INCLUDE\*(C' directive (as well as of the \*(C`#include\*(C' directive of the cpp preprocessor). .Sp Also note that the general behavior of -I and \f(CW\*(C`INCLUDE\*(C' is pretty much the same as of -I with \f(CW\*(C`#include\*(C' in the cpp preprocessor, with regard to looking for header.gcc files and other such things. .Sp This path is also used to search for .mod files when previously compiled modules are required by a \*(C`USE\*(C' statement. Item "-Mdir"

0

Item "-Jdir"

This option specifies where to put .mod files for compiled modules. It is also added to the list of directories to searched by an \*(C`USE\*(C' statement. .Sp The default is the current directory. .Sp \fB-J is an alias for -M to avoid conflicts with existing \s-1GCC\s0 options. .Sh "Influencing runtime behavior" Subsection "Influencing runtime behavior" These options affect the runtime behavior of programs compiled with \s-1GNU\s0 Fortran.

Item "-fconvert=conversion" Specify the representation of data for unformatted files. Valid values for conversion are: native, the default; swap, swap between big- and little-endian; big-endian, use big-endian representation for unformatted files; little-endian, use little-endian representation for unformatted files. .Sp \fIThis option has an effect only when used in the main program. The \f(CI\*(C`CONVERT\*(C' specifier and the \s-1GFORTRAN_CONVERT_UNIT\s0 environment variable override the default specified by \f(BI-fconvert. Item "-frecord-marker=length" Specify the length of record markers for unformatted files. Valid values for length are 4 and 8. Default is 4. \fIThis is different from previous versions of gfortran, which specified a default record marker length of 8 on most systems. If you want to read or write files compatible with earlier versions of gfortran, use -frecord-marker=8. Item "-fmax-subrecord-length=length" Specify the maximum length for a subrecord. The maximum permitted value for length is 2147483639, which is also the default. Only really useful for use by the gfortran testsuite. .Sh "Options for Code Generation Conventions" Subsection "Options for Code Generation Conventions" These machine-independent options control the interface conventions used in code generation.

Most of them have both positive and negative forms; the negative form of -ffoo would be -fno-foo. In the table below, only one of the forms is listed---the one which is not the default. You can figure out the other form by either removing no- or adding it.

Item "-fno-automatic" Treat each program unit as if the \*(C`SAVE\*(C' statement was specified for every local variable and array referenced in it. Does not affect common blocks. (Some Fortran compilers provide this option under the name \fB-static.) Item "-ff2c" Generate code designed to be compatible with code generated by g77 and f2c. .Sp The calling conventions used by g77 (originally implemented in f2c) require functions that return type default \*(C`REAL\*(C' to actually return the C type \*(C`double\*(C', and functions that return type \*(C`COMPLEX\*(C' to return the values via an extra argument in the calling sequence that points to where to store the return value. Under the default \s-1GNU\s0 calling conventions, such functions simply return their results as they would in \s-1GNU\s0 C---default \*(C`REAL\*(C' functions return the C type \*(C`float\*(C', and \f(CW\*(C`COMPLEX\*(C' functions return the \s-1GNU\s0 C type \*(C`complex\*(C'. Additionally, this option implies the -fsecond-underscore option, unless -fno-second-underscore is explicitly requested. .Sp This does not affect the generation of code that interfaces with the libgfortran library. .Sp \fICaution: It is not a good idea to mix Fortran code compiled with \fB-ff2c with code compiled with the default -fno-f2c calling conventions as, calling \*(C`COMPLEX\*(C' or default \*(C`REAL\*(C' functions between program parts which were compiled with different calling conventions will break at execution time. .Sp \fICaution: This will break code which passes intrinsic functions of type default \*(C`REAL\*(C' or \*(C`COMPLEX\*(C' as actual arguments, as the library implementations use the -fno-f2c calling conventions. Item "-fno-underscoring" Do not transform names of entities specified in the Fortran source file by appending underscores to them. .Sp With -funderscoring in effect, \s-1GNU\s0 Fortran appends one underscore to external names with no underscores. This is done to ensure compatibility with code produced by many \s-1UNIX\s0 Fortran compilers. .Sp \fICaution: The default behavior of \s-1GNU\s0 Fortran is incompatible with f2c and g77, please use the \fB-ff2c option if you want object files compiled with \s-1GNU\s0 Fortran to be compatible with object code created with these tools. .Sp Use of -fno-underscoring is not recommended unless you are experimenting with issues such as integration of \s-1GNU\s0 Fortran into existing system environments (vis-a-vis existing libraries, tools, and so on). .Sp For example, with -funderscoring, and assuming other defaults like \fB-fcase-lower and that \*(C`j()\*(C' and \*(C`max_count()\*(C' are external functions while \*(C`my_var\*(C' and \*(C`lvar\*(C' are local variables, a statement like .Sp .Vb 1 I = J() + MAX_COUNT (MY_VAR, LVAR) .Ve .Sp is implemented as something akin to: .Sp .Vb 1 i = j_() + max_count__(&my_var__, &lvar); .Ve .Sp With -fno-underscoring, the same statement is implemented as: .Sp .Vb 1 i = j() + max_count(&my_var, &lvar); .Ve .Sp Use of -fno-underscoring allows direct specification of user-defined names while debugging and when interfacing \s-1GNU\s0 Fortran code with other languages. .Sp Note that just because the names match does not mean that the interface implemented by \s-1GNU\s0 Fortran for an external name matches the interface implemented by some other language for that same name. That is, getting code produced by \s-1GNU\s0 Fortran to link to code produced by some other compiler using this or any other method can be only a small part of the overall solution---getting the code generated by both compilers to agree on issues other than naming can require significant effort, and, unlike naming disagreements, linkers normally cannot detect disagreements in these other areas. .Sp Also, note that with -fno-underscoring, the lack of appended underscores introduces the very real possibility that a user-defined external name will conflict with a name in a system library, which could make finding unresolved-reference bugs quite difficult in some cases---they might occur at program run time, and show up only as buggy behavior at run time. .Sp In future versions of \s-1GNU\s0 Fortran we hope to improve naming and linking issues so that debugging always involves using the names as they appear in the source, even if the names as seen by the linker are mangled to prevent accidental linking between procedures with incompatible interfaces. Item "-fsecond-underscore" By default, \s-1GNU\s0 Fortran appends an underscore to external names. If this option is used \s-1GNU\s0 Fortran appends two underscores to names with underscores and one underscore to external names with no underscores. \s-1GNU\s0 Fortran also appends two underscores to internal names with underscores to avoid naming collisions with external names. .Sp This option has no effect if -fno-underscoring is in effect. It is implied by the -ff2c option. .Sp Otherwise, with this option, an external name such as \*(C`MAX_COUNT\*(C' is implemented as a reference to the link-time external symbol \f(CW\*(C`max_count_\|_\*(C', instead of \*(C`max_count_\*(C'. This is required for compatibility with g77 and f2c, and is implied by use of the -ff2c option. Item "-fbounds-check" Enable generation of run-time checks for array subscripts and against the declared minimum and maximum values. It also checks array indices for assumed and deferred shape arrays against the actual allocated bounds. .Sp In the future this may also include other forms of checking, e.g., checking substring references. Item "-fmax-stack-var-size=n" This option specifies the size in bytes of the largest array that will be put on the stack. .Sp This option currently only affects local arrays declared with constant bounds, and may not apply to all character variables. Future versions of \s-1GNU\s0 Fortran may improve this behavior. .Sp The default value for n is 32768. Item "-fpack-derived" This option tells \s-1GNU\s0 Fortran to pack derived type members as closely as possible. Code compiled with this option is likely to be incompatible with code compiled without this option, and may execute slower. Item "-frepack-arrays" In some circumstances \s-1GNU\s0 Fortran may pass assumed shape array sections via a descriptor describing a noncontiguous area of memory. This option adds code to the function prologue to repack the data into a contiguous block at runtime. .Sp This should result in faster accesses to the array. However it can introduce significant overhead to the function call, especially when the passed data is noncontiguous. Item "-fshort-enums" This option is provided for interoperability with C code that was compiled with the -fshort-enums option. It will make \s-1GNU\s0 Fortran choose the smallest \*(C`INTEGER\*(C' kind a given enumerator set will fit in, and give all its enumerators this kind. Header "ENVIRONMENT" The gfortran compiler currently does not make use of any environment variables to control its operation above and beyond those that affect the operation of gcc. Header "BUGS" For instructions on reporting bugs, see <http://gcc.gnu.org/bugs.html>. Header "SEE ALSO" \fIgpl\|(7), gfdl\|(7), fsf-funding\|(7), \fIcpp\|(1), gcov\|(1), gcc\|(1), as\|(1), ld\|(1), gdb\|(1), adb\|(1), dbx\|(1), sdb\|(1) and the Info entries for gcc, cpp, gfortran, as, \fIld, binutils and gdb. Header "AUTHOR" See the Info entry for gfortran for contributors to \s-1GCC\s0 and \s-1GNU\s0 Fortran. Header "COPYRIGHT" Copyright (c) 2004, 2005, 2006, 2007 Free Software Foundation, Inc.

Permission is granted to copy, distribute and/or modify this document under the terms of the \s-1GNU\s0 Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with the Invariant Sections being \*(L"\s-1GNU\s0 General Public License\*(R" and \*(L"Funding Free Software\*(R", the Front-Cover texts being (a) (see below), and with the Back-Cover Texts being (b) (see below). A copy of the license is included in the gfdl\|(7) man page.

(a) The \s-1FSF\s0's Front-Cover Text is:

.Vb 1 A GNU Manual .Ve

(b) The \s-1FSF\s0's Back-Cover Text is:

.Vb 3 You have freedom to copy and modify this GNU Manual, like GNU software. Copies published by the Free Software Foundation raise funds for GNU development. .Ve