2.2 Options controlling Fortran dialect
The following options control the details of the Fortran dialect
accepted by the compiler:
-ffree-form-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.
-fall-intrinsics- This option causes all intrinsic procedures (including the GNU-specific
extensions) to be accepted. This can be useful with -std=f95 to
force standard-compliance but get access to the full range of intrinsics
available with gfortran. As a consequence, -Wintrinsics-std
will be ignored and no user-defined procedure with the same name as any
intrinsic will be called except when it is explicitly declared
EXTERNAL.
-fd-lines-as-code-fd-lines-as-comments- Enable special treatment for lines beginning with
d or D
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
-fd-lines-as-comments option is given, they are treated as
comment lines.
-fdefault-double-8- Set the
DOUBLE PRECISION type to an 8 byte wide type. If
-fdefault-real-8 is given, DOUBLE PRECISION would
instead be promoted to 16 bytes if possible, and -fdefault-double-8
can be used to prevent this. The kind of real constants like 1.d0 will
not be changed by -fdefault-real-8 though, so also
-fdefault-double-8 does not affect it.
-fdefault-integer-8- Set the default integer and logical types to an 8 byte wide type.
Do nothing if this is already the default. This option also affects
the kind of integer constants like
42.
-fdefault-real-8- Set the default real type to an 8 byte wide type.
Do nothing if this is already the default. This option also affects
the kind of non-double real constants like
1.0, and does promote
the default width of DOUBLE PRECISION to 16 bytes if possible, unless
-fdefault-double-8 is given, too.
-fdollar-ok- Allow ‘$’ as a valid non-first character in a symbol name. Symbols
that start with ‘$’ are rejected since it is unclear which rules to
apply to implicit typing as different vendors implement different rules.
Using ‘$’ in
IMPLICIT statements is also rejected.
-fbackslash- Change the interpretation of backslashes in string literals from a single
backslash character to “C-style” escape characters. The following
combinations are expanded
\a, \b, \f, \n,
\r, \t, \v, \\, and \0 to the ASCII
characters alert, backspace, form feed, newline, carriage return,
horizontal tab, vertical tab, backslash, and NUL, respectively.
Additionally, \xnn, \unnnn and
\Unnnnnnnn (where each n is a hexadecimal digit) are
translated into the Unicode characters corresponding to the specified code
points. All other combinations of a character preceded by \ are
unexpanded.
-fmodule-private- Set the default accessibility of module entities to
PRIVATE.
Use-associated entities will not be accessible unless they are explicitly
declared as PUBLIC.
-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.
Popular values for n include 72 (the
standard and the default), 80 (card image), and 132 (corresponding
to “extended-source” options in some popular compilers).
n 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.
-ffixed-line-length-0 means the same thing as
-ffixed-line-length-none.
-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.
n may be ‘none’, meaning that the entire line is meaningful.
-ffree-line-length-0 means the same thing as
-ffree-line-length-none.
-fmax-identifier-length=n- Specify the maximum allowed identifier length. Typical values are
31 (Fortran 95) and 63 (Fortran 2003 and Fortran 2008).
-fimplicit-none- Specify that no implicit typing is allowed, unless overridden by explicit
IMPLICIT statements. This is the equivalent of adding
implicit none to the start of every procedure.
-fcray-pointer- Enable the Cray pointer extension, which provides C-like pointer
functionality.
-fopenmp- Enable the OpenMP extensions. This includes OpenMP
!$omp directives
in free form
and c$omp, *$omp and !$omp directives in fixed form,
!$ conditional compilation sentinels in free form
and c$, *$ and !$ sentinels in fixed form,
and when linking arranges for the OpenMP runtime library to be linked
in. The option -fopenmp implies -frecursive.
-fno-range-check- Disable range checking on results of simplification of constant
expressions during compilation. For example, GNU Fortran will give
an error at compile time when simplifying
a = 1. / 0.
With this option, no error will be given and a will be assigned
the value +Infinity. If an expression evaluates to a value
outside of the relevant range of [-HUGE():HUGE()],
then the expression will be replaced by -Inf or +Inf
as appropriate.
Similarly, DATA i/Z'FFFFFFFF'/ will result in an integer overflow
on most systems, but with -fno-range-check the value will
“wrap around” and i will be initialized to -1 instead.
-std=std- Specify the standard to which the program is expected to conform, which
may be one of ‘f95’, ‘f2003’, ‘f2008’, ‘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 GNU 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’, ‘f2003’ and ‘f2008’ values specify strict
conformance to the Fortran 95, Fortran 2003 and Fortran 2008 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.