1 Getting Started

Gfortran is the GNU Fortran 95 compiler front end, designed initially as a free replacement for, or alternative to, the unix f95 command; gfortran is command you'll use to invoke the compiler.

Gfortran is not yet a fully conformant Fortran 95 compiler. It can generate code for most constructs and expressions, but work remains to be done. In particular, there are known deficiencies with ENTRY, NAMELIST, and sophisticated use of MODULES, POINTERS and DERIVED TYPES. For those whose Fortran codes conform to either the Fortran 77 standard or the GNU Fortran 77 language, we recommend to use g77 from GCC 3.4. We recommend that distributors continue to provide packages of g77-3.4 until we announce that gfortran fully replaces g77. The gfortran developers welcome any feedback on user experience with gfortran at fortran@gcc.gnu.org.

When gfortran is finished, it will do everything you expect from any decent compiler:

• Read a user's program, stored in a file and containing instructions written in Fortran 77, Fortran 90 or Fortran 95. This file contains source code.
• Translate the user's program into instructions a computer can carry out more quickly than it takes to translate the instructions in the first place. The result after compilation of a program is machine code, code designed to be efficiently translated and processed by a machine such as your computer. Humans usually aren't as good writing machine code as they are at writing Fortran (or C++, Ada, or Java), because is easy to make tiny mistakes writing machine code.
• Provide the user with information about the reasons why the compiler is unable to create a binary from the source code. Usually this will be the case if the source code is flawed. When writing Fortran, it is easy to make big mistakes. The Fortran 90 requires that the compiler can point out mistakes to the user. An incorrect usage of the language causes an error message.

  The compiler will also attempt to diagnose cases where the user's program contains a correct usage of the language, but instructs the computer to do something questionable. This kind of diagnostics message is called a warning message.

• Provide optional information about the translation passes from the source code to machine code. This can help a user of the compiler to find the cause of certain bugs which may not be obvious in the source code, but may be more easily found at a lower level compiler output. It also helps developers to find bugs in the compiler itself.
• Provide information in the generated machine code that can make it easier to find bugs in the program (using a debugging tool, called a debugger, such as the GNU Debugger gdb).
• Locate and gather machine code already generated to perform actions requested by statements in the user's program. This machine code is organized into modules and is located and linked to the user program.

Gfortran consists of several components:

• A version of the gcc command (which also might be installed as the system's cc command) that also understands and accepts Fortran source code. The gcc command is the driver program for all the languages in the GNU Compiler Collection (GCC); With gcc, you can compiler the source code of any language for which a front end is available in GCC.
• The gfortran command itself, which also might be installed as the system's f95 command. gfortran is just another driver program, but specifically for the Fortran 95 compiler only. The difference with gcc is that gfortran will automatically link the correct libraries to your program.
• A collection of run-time libraries. These libraries contains the machine code needed to support capabilities of the Fortran language that are not directly provided by the machine code generated by the gfortran compilation phase, such as intrinsic functions and subroutines, and routines for interaction with files and the operating system.
• The Fortran compiler itself, (f951). This is the gfortran parser and code generator, linked to and interfaced with the GCC backend library. f951 “translates” the source code to assembler code. You would typically not use this program directly; instead, the gcc or gfortran driver programs will call it for you.