g77 - Linux Command g77 SYNOPSIS g77 [-câ -Sâ -E] [ ] [ -pg ] [ -O level ] [ -W warn...] [ -pedantic ] [

Size: px

Start display at page:

Download "g77 - Linux Command g77 SYNOPSIS g77 [-câ -Sâ -E] [ ] [ -pg ] [ -O level ] [ -W warn...] [ -pedantic ] ["

Damon Chapman
6 years ago
Views:

1 - CentOS Linux Users Guide - Linux Command SYNOPSIS [-câ -Sâ -E] [ [ -pg ] [ -O level ] [ -W warn...] [ -pedantic ] [ -I dir...] [ -L dir...] [ -D macro [= defn ]...] [ -U macro ] [ -f option...] [ -m machine-option...] [ -o outfile ] infile... Only the most useful options are listed here; see below for the remain- der. DESCRIPTION The command supports all the options supported by the -g] 1 / 12

2 - CentOS Linux Users Guide command. All and options are accepted both by and by (as well as any other drivers built at the same time, such as g++ ), since adding to the distribution enables acceptance of 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. OPTIONS Here is a summary of all the options specific to GNU Fortran, grouped by type. Explanations are in the following sections. Overall -fversion -fset--defaults -fno-silent Shorthand -ff66 -fno-f66 -ff77 -fno-f77 2 / 12

3 - CentOS Linux Users Guide -fno-ugly Fortran Language -ffree-form -fno-fixed-form -ff90 -fvxt -fdollar-ok -fno-backslash -fno-ugly-args -fno-ugly-assign -fno-ugly-assumed -fugly-comma -fugly-complex -fugly-init -fugly-logint -fonetrip -ftypeless-boz -fintrin-case-initcap -fintrin-case-upper -fintrin-case-lower -fintrin-case-any -fmatch-case-initcap -fmatch-case-upper -fmatch-case-lower 3 / 12

4 - CentOS Linux Users Guide -fmatch-case-any -fsource-case-upper -fsource-case-lower -fsource-case-preserve -fsymbol-case-initcap -fsymbol-case-upper -fsymbol-case-lower -fsymbol-case-any -fcase-strict-upper -fcase-strict-lower -fcase-initcap -fcase-upper -fcase-lower -fcase-preserve -ff2c-intrinsics-delete -ff2c-intrinsics-enable -fbadu77-intrinsics-delete -fbadu77-intrinsics-hide -fbadu77-intrinsics-disable -fbadu77-intrinsics-enable -ff90-intrinsics-delete -ff2c-intrinsics-hide -ff2c-intrinsics-disable -ff90-intrinsics-hide -ff90-intrinsics-disable 4 / 12

5 - CentOS Linux Users Guide -ff90-intrinsics-enable -fgnu-intrinsics-delete -fgnu-intrinsics-hide -fgnu-intrinsics-disable -fgnu-intrinsics-enable -fmil-intrinsics-delete Optimization -malign-double -ffloat-store -fforce-mem -fforce-addr -fno-inline -ffast-math -fstrength-reduce -frerun-cse-after-loop -funsafe-math-optimizations -ffinite-math-only -fno-trapping-math -fexpensive-optimizations -fdelayed-branch -fschedule-insns -fschedule-insn2 -fcaller-saves -funroll-loops -funroll-all-loops 5 / 12

6 - CentOS Linux Users Guide -fno-move-all-movables -fno-reduce-all-givs -fno-rerun-loop-opt Directory -I dir -I- Code Generation -fno-automatic -finit-local-zero -fno-f2c -ff2c-library -fno-underscoring -fno-ident -fpcc-struct-return -freg-struct-return -fshort-double -fno-common -fpack-struct -fzeros -fno-second-underscore -femulate-complex -falias-check -fargument-alias -fargument-noalias -fno-argument-noalias-global 6 / 12

7 - CentOS Linux Users Guide -fno-globals -fflatten-arrays -fbounds-check -ffortran-bounds-check Compilation can involve as many as four stages: preprocessing, code generation (often what is really meant by the term â â compilationâ â ), assembly, and linking, always in that order. The first three stages apply to an individual source file, and end by producing an object file; linking combines all the object files (those newly compiled, and those specified as input) into an executable file. For any given input file, the file name suffix determines what kind of program is contained in the file---that is, the language in which the program is written is generally indicated by the suffix. Suffixes spe- cific to GNU Fortran are listed below. file.f file.for file.for Fortran source code that should not be preprocessed. Such source code cannot contain any preprocessor directives, such as "#include", "#define", "#if", and so on. You can force.f files to be preprocessed by cpp by using -x f77-cpp-input. file.f file.fpp file.fpp cpp Fortran source code that must be preprocessed (by the C preproces- sor 7 / 12

8 - CentOS Linux Users Guide, which is part of GCC). Note that preprocessing is not extended to the contents of files included by the "INCLUDE" directive---the "#include" preprocessor "#define" and "#include", but can lead to unexpected, even mistaken, results due to Fortranâ s source file format. It is recommended that use of the C preprocessor be limited to "#include" and, in conjunction with "#define", only "#if" and related directives, thus avoiding in- line macro expansion entirely. This recommendation applies especially when using the traditional fixed source form. With free source form, fewer unexpected transformations are likely to happen, but use of con- structs such as Hollerith and character constants can nevertheless present problems, especially when these are continued across multiple source lines. These problems result, primarily, from differences between the way such constants are interpreted by the C preprocessor and by a Fortran compiler. Another example of a problem that results from using the C preprocessor is that a Fortran comment line that happens to contain any characters â â interestingâ â to the C preprocessor, such as a backslash at the end of the line, is not recognized by the preprocessor as a comment line, so instead of being passed through â â rawâ â, the line is edited accord- ing to the rules for the preprocessor. For example, the backslash at the end of the line is removed, along with the subsequent newline, resulting in the next line being effectively commented out---unfortu- nate if that line is a non-comment line of important code! Note: The -traditional and -undef flags are supplied to cpp by default, to help avoid unpleasant surprises. This means that ANSI C preprocessor features (such as the # operator) arenâ t available, and only variables in the C reserved namespace (generally, names with a leading underscore) are liable to substitution by C predefines. Thus, if you want to do system-specific tests, use, for example, #ifdef linux rather than #ifdef linux. Use the -v option to see exactly how the preprocessor is invoked. Unfortunately, the -traditional flag will not avoid an error from any- thing that cpp sees as an unterminated C comment, such as: C Some Fortran compilers accept /* as starting C an inline comment. The following options that affect overall processing are recognized by the 8 / 12

9 - CentOS Linux Users Guide and commands in a GNU Fortran installation: -fversion Ensure that the version of the compiler phase is reported, if run, and, starting in "egcs" version 1.1, that internal consistency checks in the f771 program are run. This option is supplied automatically when -v or --verbose is spec- ified as a command-line option for or and when the result- ing commands compile Fortran source files. In GCC 3.1, this is changed back to the behavior displays for stand why it is there. Also, developers who run "f771" directly might want to specify it by hand to get the same defaults as they would running "f771" via or However, such developers should, after linking a new "f771" executable, invoke it without this option once, e.g. via "./f771 -quiet < /dev/null", to ensure that they have not introduced any internal inconsistencies (such as in the table of intrin- sics) before proceeding--- will crash with a diagnostic if it detects an inconsistency. -fno-silent Print (to "stderr") the names of the program units as they are com- piled, in a form similar to that used by popular UNIX f77 implemen- tations and f2c Shorthand The following options serve as â â shorthandâ â for other options accepted by the compiler: -fugly 9 / 12

10 - CentOS Linux Users Guide Note: This option is no longer supported. The information, below, is provided to aid in the conversion of old scripts. Specify that certain â â uglyâ â constructs are to be quietly accepted. Same as: -fugly-args -fugly-assign -fugly-assumed -fugly-comma -fugly-complex -fugly-init -fugly-logint These constructs are considered inappropriate to use in new or well-maintained portable Fortran code, but widely used in old code. -fno-ugly Specify that all â â uglyâ â constructs are to be noisily rejected. Same as: -fno-ugly-args -fno-ugly-assign -fno-ugly-assumed -fno-ugly-comma -fno-ugly-complex -fno-ugly-init -fno-ugly-logint -ff66 Specify that the program is written in idiomatic FORTRAN 66. Same as -fonetrip -fugly-assumed. The -fno-f66 option is the inverse of -ff66. As such, it is the same as -fno-onetrip -fno-ugly-assumed. The meaning of this option is likely to be refined as future ver- sions of provide more compatibility with other existing and in a more widely portable dialect. -fno-f77 is the same as -fno-backslash. The meaning of this option is likely to be refined as future ver- sions of provide more compatibility with other existing and obsolete Fortran implementations. Controlling Fortran Dialect The following options control the dialect of Fortran that the compiler -ffree-form accepts: -fno-fixed-form Specify that the source file is written in free form (introduced in Fortran 90) instead of the more-traditional fixed form. -ff90 Allow certain Fortran-90 constructs. This option controls whether certain Fortran 90 constructs are rec- ognized. (Other Fortran 90 constructs might or might not be recog- nized depending on other options such as 10 / 12

11 - CentOS Linux Users Guide -fvxt, -ff90-intrinsics-enable, and the current level of support for Fortran 90.) -fvxt Specify the treatment of certain constructs that have different meanings depending on whether the code is written in GNU Fortran (based on FORTRAN 77 and akin to Fortran 90) or VXT Fortran (more like VAX FORTRAN). The default is -fno-vxt. -fvxt specifies that the VXT Fortran interpretations for those constructs are to be chosen. -fdollar-ok Allow $ as a valid character in a symbol name. -fno-backslash Specify that is not to be specially interpreted in character and Hollerith constants a la C and many UNIX Fortran compilers. For example, with -fbackslash in effect, AnB specifies three char- acters, with the second one being newline. With -fno-backslash, it specifies four characters, A,, n, and B. Note that implements a fairly general form of backslash pronarrower forms supported by some other compilers. For example, â â A 03B â â is a three-character string in whereas other compilers that support backslash might cessing that is incompatible with the not support the three-octal-digit 11 / 12

12 - CentOS Linux Users Guide form, and thus treat that string as longer than three characters. For example, DIMENSION X(1) is treated as if it had read DIMENSION X(*). -fugly-comma In an external-procedure invocation, treat a trailing comma in the specification of a trailing null argument, and of a single null argument. For example, CALL FOO(,) is treated as CALL FOO(% V argument list as treat an empty argument list as specification 12 / 12

gfortran - Linux Command

gfortran - Linux Command - Linux Command SYNOPSIS [-câ -Sâ -E] [ -g ] [ -pg ] [ -O level ] [ -W warn...] [ ] [ -I...] [ -L...] [ -D macro [= defn ]...] [ -U macro ] [ -f option...] [ -m machine-option...] [ -o outfile ] infile...