1 \input texinfo @c -*-texinfo-*-
3 @setfilename gfortran.info
4 @set copyrights-gfortran 1999-2005
6 @include gcc-common.texi
8 @settitle The GNU Fortran 95 Compiler
10 @c Create a separate index for command line options
12 @c Merge the standard indexes into a single one.
21 @c Use with @@smallbook.
23 @c %** start of document
25 @c Cause even numbered pages to be printed on the left hand side of
26 @c the page and odd numbered pages to be printed on the right hand
27 @c side of the page. Using this, you can print on both sides of a
28 @c sheet of paper and have the text on the same part of the sheet.
30 @c The text on right hand pages is pushed towards the right hand
31 @c margin and the text on left hand pages is pushed toward the left
33 @c (To provide the reverse effect, set bindingoffset to -0.75in.)
36 @c \global\bindingoffset=0.75in
37 @c \global\normaloffset =0.75in
41 Copyright @copyright{} @value{copyrights-gfortran} Free Software Foundation, Inc.
43 Permission is granted to copy, distribute and/or modify this document
44 under the terms of the GNU Free Documentation License, Version 1.1 or
45 any later version published by the Free Software Foundation; with the
46 Invariant Sections being ``GNU General Public License'' and ``Funding
47 Free Software'', the Front-Cover
48 texts being (a) (see below), and with the Back-Cover Texts being (b)
49 (see below). A copy of the license is included in the section entitled
50 ``GNU Free Documentation License''.
52 (a) The FSF's Front-Cover Text is:
56 (b) The FSF's Back-Cover Text is:
58 You have freedom to copy and modify this GNU Manual, like GNU
59 software. Copies published by the Free Software Foundation raise
60 funds for GNU development.
64 @dircategory Programming
66 * gfortran: (gfortran). The GNU Fortran 95 Compiler.
68 This file documents the use and the internals of
69 the GNU Fortran 95 compiler, (@command{gfortran}).
71 Published by the Free Software Foundation
72 51 Franklin Street, Fifth Floor
73 Boston, MA 02110-1301 USA
79 @setchapternewpage odd
81 @title Using GNU Fortran 95
83 @center The gfortran team
85 @vskip 0pt plus 1filll
86 For the @value{version-GCC} Version*
88 Published by the Free Software Foundation @*
89 51 Franklin Street, Fifth Floor@*
90 Boston, MA 02110-1301, USA@*
91 @c Last printed ??ber, 19??.@*
92 @c Printed copies are available for $? each.@*
105 This manual documents the use of @command{gfortran},
106 the GNU Fortran 95 compiler. You can find in this manual how to invoke
107 @command{gfortran}, as well as its features and incompatibilities.
110 @emph{Warning:} This document, and the compiler it describes, are still
111 under development. While efforts are made to keep it up-to-date, it might
112 not accurately reflect the status of the most recent @command{gfortran}.
116 @comment When you add a new menu item, please keep the right hand
117 @comment aligned to the same column. Do not use tabs. This provides
118 @comment better formatting.
121 * Getting Started:: What you should know about @command{gfortran}.
122 * GFORTRAN and GCC:: You can compile Fortran, C, or other programs.
123 * GFORTRAN and G77:: Why we chose to start from scratch.
124 * Invoking GFORTRAN:: Command options supported by @command{gfortran}.
125 * Project Status:: Status of @command{gfortran}, roadmap, proposed extensions.
126 * Contributing:: How you can help.
127 * Standards:: Standards supported by @command{gfortran}
128 * Runtime:: Influencing runtime behavior with environment variables.
129 * Extensions:: Language extensions implemented by @command{gfortran}
130 * Intrinsic Procedures:: Intrinsic procedures supported by @command{gfortran}
131 * Copying:: GNU General Public License says
132 how you can copy and share GNU Fortran.
133 * GNU Free Documentation License::
134 How you can copy and share this manual.
135 * Funding:: How to help assure continued work for free software.
136 * Index:: Index of this documentation.
141 @c ---------------------------------------------------------------------
143 @c ---------------------------------------------------------------------
145 @node Getting Started
146 @chapter Getting Started
148 Gfortran is the GNU Fortran 95 compiler front end,
149 designed initially as a free replacement for,
150 or alternative to, the unix @command{f95} command;
151 @command{gfortran} is the command you'll use to invoke the compiler.
153 Gfortran is still in an early state of development.
154 @command{gfortran} can generate code for most constructs and expressions,
155 but much work remains to be done.
157 When @command{gfortran} is finished,
158 it will do everything you expect from any decent compiler:
162 Read a user's program,
163 stored in a file and containing instructions written
164 in Fortran 77, Fortran 90 or Fortran 95.
165 This file contains @dfn{source code}.
168 Translate the user's program into instructions a computer
169 can carry out more quickly than it takes to translate the
170 instructions in the first
171 place. The result after compilation of a program is
173 code designed to be efficiently translated and processed
174 by a machine such as your computer.
175 Humans usually aren't as good writing machine code
176 as they are at writing Fortran (or C++, Ada, or Java),
177 because is easy to make tiny mistakes writing machine code.
180 Provide the user with information about the reasons why
181 the compiler is unable to create a binary from the source code.
182 Usually this will be the case if the source code is flawed.
183 When writing Fortran, it is easy to make big mistakes.
184 The Fortran 90 requires that the compiler can point out
185 mistakes to the user.
186 An incorrect usage of the language causes an @dfn{error message}.
188 The compiler will also attempt to diagnose cases where the
189 user's program contains a correct usage of the language,
190 but instructs the computer to do something questionable.
191 This kind of diagnostics message is called a @dfn{warning message}.
194 Provide optional information about the translation passes
195 from the source code to machine code.
196 This can help a user of the compiler to find the cause of
197 certain bugs which may not be obvious in the source code,
198 but may be more easily found at a lower level compiler output.
199 It also helps developers to find bugs in the compiler itself.
202 Provide information in the generated machine code that can
203 make it easier to find bugs in the program (using a debugging tool,
204 called a @dfn{debugger}, such as the GNU Debugger @command{gdb}).
207 Locate and gather machine code already generated to
208 perform actions requested by statements in the user's program.
209 This machine code is organized into @dfn{modules} and is located
210 and @dfn{linked} to the user program.
213 Gfortran consists of several components:
217 A version of the @command{gcc} command
218 (which also might be installed as the system's @command{cc} command)
219 that also understands and accepts Fortran source code.
220 The @command{gcc} command is the @dfn{driver} program for
221 all the languages in the GNU Compiler Collection (GCC);
223 you can compile the source code of any language for
224 which a front end is available in GCC.
227 The @command{gfortran} command itself,
228 which also might be installed as the
229 system's @command{f95} command.
230 @command{gfortran} is just another driver program,
231 but specifically for the Fortran 95 compiler only.
232 The difference with @command{gcc} is that @command{gfortran}
233 will automatically link the correct libraries to your program.
236 A collection of run-time libraries.
237 These libraries contain the machine code needed to support
238 capabilities of the Fortran language that are not directly
239 provided by the machine code generated by the
240 @command{gfortran} compilation phase,
241 such as intrinsic functions and subroutines,
242 and routines for interaction with files and the operating system.
243 @c and mechanisms to spawn,
244 @c unleash and pause threads in parallelized code.
247 The Fortran compiler itself, (@command{f951}).
248 This is the gfortran parser and code generator,
249 linked to and interfaced with the GCC backend library.
250 @command{f951} ``translates'' the source code to
251 assembler code. You would typically not use this
253 instead, the @command{gcc} or @command{gfortran} driver
254 programs will call it for you.
259 @c ---------------------------------------------------------------------
261 @c ---------------------------------------------------------------------
263 @node GFORTRAN and GCC
264 @chapter GFORTRAN and GCC
265 @cindex GNU Compiler Collection
267 GCC used to be the GNU ``C'' Compiler,
268 but is now known as the @dfn{GNU Compiler Collection}.
269 GCC provides the GNU system with a very versatile
270 compiler middle end (shared optimization passes),
271 and back ends (code generators) for many different
272 computer architectures and operating systems.
273 The code of the middle end and back end are shared by all
274 compiler front ends that are in the GNU Compiler Collection.
276 A GCC front end is essentially a source code parser
277 and an intermediate code generator. The code generator translates the
278 semantics of the source code into a language independent form called
281 The parser takes a source file written in a
282 particular computer language, reads and parses it,
283 and tries to make sure that the source code conforms to
285 Once the correctness of a program has been established,
286 the compiler will build a data structure known as the
287 @dfn{Abstract Syntax tree},
288 or just @dfn{AST} or ``tree'' for short.
289 This data structure represents the whole program
290 or a subroutine or a function.
291 The ``tree'' is passed to the GCC middle end,
292 which will perform optimization passes on it. The optimized AST is then
293 handed off too the back end which assembles the program unit.
295 Different phases in this translation process can be,
296 and in fact @emph{are} merged in many compiler front ends.
297 GNU Fortran 95 has a strict separation between the
298 parser and code generator.
300 The goal of the gfortran project is to build a new front end for GCC.
301 Specifically, a Fortran 95 front end.
302 In a non-gfortran installation,
303 @command{gcc} will not be able to compile Fortran 95 source code
304 (only the ``C'' front end has to be compiled if you want to build GCC,
305 all other languages are optional).
306 If you build GCC with gfortran, @command{gcc} will recognize
307 @file{.f/.f90/.f95} source files and accepts Fortran 95 specific
308 command line options.
312 @c ---------------------------------------------------------------------
314 @c ---------------------------------------------------------------------
316 @node GFORTRAN and G77
317 @chapter GFORTRAN and G77
321 Why do we write a compiler front end from scratch?
322 There's a fine Fortran 77 compiler in the
323 GNU Compiler Collection that accepts some features
324 of the Fortran 90 standard as extensions.
325 Why not start from there and revamp it?
327 One of the reasons is that Craig Burley, the author of G77,
328 has decided to stop working on the G77 front end.
329 On @uref{http://world.std.com/~burley/g77-why.html,
330 Craig explains the reasons for his decision to stop working on G77}
331 in one of the pages in his homepage.
332 Among the reasons is a lack of interest in improvements to
334 Users appear to be quite satisfied with @command{g77} as it is.
335 While @command{g77} is still being maintained (by Toon Moene),
336 it is unlikely that sufficient people will be willing
337 to completely rewrite the existing code.
339 But there are other reasons to start from scratch.
340 Many people, including Craig Burley,
341 no longer agreed with certain design decisions in the G77 front end.
342 Also, the interface of @command{g77} to the back end is written in
343 a style which is confusing and not up to date on recommended practice.
344 In fact, a full rewrite had already been planned for GCC 3.0.
346 When Craig decided to stop,
347 it just seemed to be a better idea to start a new project from scratch,
348 because it was expected to be easier to maintain code we
349 develop ourselves than to do a major overhaul of @command{g77} first,
350 and then build a Fortran 95 compiler out of it.
354 @c ---------------------------------------------------------------------
356 @c ---------------------------------------------------------------------
359 @chapter Project Status
362 As soon as gfortran can parse all of the statements correctly,
363 it will be in the ``larva'' state.
364 When we generate code, the ``puppa'' state.
365 When gfortran is done,
366 we'll see if it will be a beautiful butterfly,
367 or just a big bug....
369 --Andy Vaught, April 2000
372 The start of the GNU Fortran 95 project was announced on
373 the GCC homepage in March 18, 2000
374 (even though Andy had already been working on it for a while,
377 Gfortran is currently reaching the stage where is is able to compile real
378 world programs. However it is still under development and has many rough
384 * Proposed Extensions::
387 @node Compiler Status
388 @section Compiler Status
392 This is the part of gfortran which parses a source file, verifies that it
393 is valid Fortran 95, performs compile time replacement of constants
394 (PARAMETER variables) and reads and generate module files. This is
395 almost complete. Every Fortran 95 source should be accepted, and most
396 none-Fortran 95 source should be rejected. If you find a source file where
397 this is not true, please tell us. You can use the -fsyntax-only switch to
398 make gfortran quit after running the front end, effectively reducing it to
401 @item Middle end interface
402 These are the parts of gfortran that take the parse tree generated by the
403 front end and translate it to the GENERIC form required by the GCC back
404 end. Work is ongoing in these parts of gfortran, but a large part has
405 already been completed.
409 @section Library Status
411 Some intrinsic functions map directly to library functions, and in most
412 cases the name of the library function used depends on the type of the
413 arguments. For some intrinsics we generate inline code, and for others,
414 such as sin, cos and sqrt, we rely on the backend to use special
415 instructions in the floating point unit of the CPU if available, or to
416 fall back to a call to libm if these are not available.
418 Implementation of some non-elemental intrinsic functions (eg. DOT_PRODUCT,
419 AVERAGE) is not yet optimal. This is hard because we have to make decisions
420 whether to use inline code (good for small arrays as no function call
421 overhead occurs) or generate function calls (good for large arrays as it
422 allows use of hand-optimized assembly routines, SIMD instructions, etc.)
424 The IO library is in a mostly usable state. Unformatted I/O for
425 @code{REAL(KIND=10)} variables is currently not recommended.
427 Array intrinsics mostly work.
429 @node Proposed Extensions
430 @section Proposed Extensions
432 Here's a list of proposed extensions for @command{gfortran}, in no particular
433 order. Most of these are necessary to be fully compatible with
434 existing Fortran compilers, but they are not part of the official
435 J3 Fortran 95 standard.
437 @subsection Compiler extensions:
440 Flag for defining the kind number for default logicals.
443 User-specified alignment rules for structures.
445 Flag to generate @code{Makefile} info.
448 Automatically extend single precision constants to double.
451 Compile code that conserves memory by dynamically allocating common and
452 module storage either on stack or heap.
455 Flag to cause the compiler to distinguish between upper and lower case
456 names. The Fortran 95 standard does not distinguish them.
459 Compile flag to generate code for array conformance checking (suggest -CC).
462 User control of symbol names (underscores, etc).
465 Compile setting for maximum size of stack frame size before spilling
466 parts to static or heap.
469 Flag to force local variables into static space.
472 Flag to force local variables onto stack.
475 Flag to compile lines beginning with ``D''.
478 Flag to ignore lines beginning with ``D''.
481 Flag for maximum errors before ending compile.
484 Generate code to check for null pointer dereferences -- prints locus of
485 dereference instead of segfaulting. There was some discussion about this
486 option in the g95 development mailing list.
489 Allow setting the default unit number.
492 Option to initialize otherwise uninitialized integer and floating
496 Support for OpenMP directives. This also requires support from the runtime
497 library and the rest of the compiler.
500 Support for Fortran 200x. This includes several new features including
501 floating point exceptions, extended use of allocatable arrays, C
502 interoperability, Parameterizer data types and function pointers.
506 @subsection Environment Options
509 Pluggable library modules for random numbers, linear algebra.
510 LA should use BLAS calling conventions.
513 Environment variables controlling actions on arithmetic exceptions like
514 overflow, underflow, precision loss -- Generate NaN, abort, default.
518 Set precision for fp units that support it (i387).
521 Variable for setting fp rounding mode.
524 Variable to fill uninitialized variables with a user-defined bit
528 Environment variable controlling filename that is opened for that unit
532 Environment variable to clear/trash memory being freed.
535 Environment variable to control tracing of allocations and frees.
538 Environment variable to display allocated memory at normal program end.
541 Environment variable for filename for * IO-unit.
544 Environment variable for temporary file directory.
547 Environment variable forcing standard output to be line buffered (unix).
552 @chapter Runtime: Influencing runtime behavior with environment variables
555 The behaviour of the @command{gfortran} can be influenced by
556 environment variables.
558 * GFORTRAN_CONVERT_UNIT:: Set endianness for unformatted I/O
561 @node GFORTRAN_CONVERT_UNIT
562 @section GFORTRAN_CONVERT_UNIT --- Set endianness for unformatted I/O
564 By setting the @code{GFORTRAN_CONVERT_UNIT variable}, it is possible
565 to change the representation of data for unformatted files.
566 The syntax for the @code{GFORTRAN_CONVERT_UNIT} variable is:
568 GFORTRAN_CONVERT_UNIT: mode | mode ';' exception ;
569 mode: 'native' | 'swap' | 'big_endian' | 'little_endian' ;
570 exception: mode ':' unit_list | unit_list ;
571 unit_list: unit_spec | unit_list unit_spec ;
572 unit_spec: INTEGER | INTEGER '-' INTEGER ;
574 The variable consists of an optional default mode, followed by
575 a list of optional exceptions, which are separated by semicolons
576 from the preceding default and each other. Each exception consists
577 of a format and a comma-separated list of units. Valid values for
578 the modes are the same as for the @code{CONVERT} specifier:
581 @item @code{NATIVE} Use the native format. This is the default.
582 @item @code{SWAP} Swap between little- and big-endian.
583 @item @code{LITTLE_ENDIAN} Use the little-endian format
584 for unformatted files.
585 @item @code{BIG_ENDIAN} Use the big-endian format for unformatted files.
587 A missing mode for an exception is taken to mean @code{BIG_ENDIAN}.
588 Examples of values for @code{GFORTRAN_CONVERT_UNIT} are:
590 @item @code{'big_endian'} Do all unformatted I/O in big_endian mode.
591 @item @code{'little_endian;native:10-20,25'} Do all unformatted I/O
592 in little_endian mode, except for units 10 to 20 and 25, which are in
594 @item @code{'10-20'} Units 10 to 20 are big-endian, the rest is native.
597 Setting the environment variables should be done on the command
598 line or via the @code{export}
599 command for @code{sh}-compatible shells and via @code{setenv}
600 for @code{csh}-compatible shells.
602 Example for @code{sh}:
605 $ GFORTRAN_CONVERT_UNIT='big_endian;native:10-20' ./a.out
608 Example code for @code{csh}:
611 % setenv GFORTRAN_CONVERT_UNIT 'big_endian;native:10-20'
615 Using anything but the native representation for unformatted data
616 carries a significant speed overhead. If speed in this area matters
617 to you, it is best if you use this only for data that needs to be
620 @xref{CONVERT specifier}, for an alternative way to specify the
621 data representation for unformatted files. @xref{Runtime Options}, for
622 setting a default data representation for the whole program. The
623 @code{CONVERT} specifier overrides the @code{-fconvert} compile options.
625 @c ---------------------------------------------------------------------
627 @c ---------------------------------------------------------------------
629 @c Maybe this chapter should be merged with the 'Standards' section,
630 @c whenever that is written :-)
636 @command{gfortran} implements a number of extensions over standard
637 Fortran. This chapter contains information on their syntax and
638 meaning. There are currently two categories of @command{gfortran}
639 extensions, those that provide functionality beyond that provided
640 by any standard, and those that are supported by @command{gfortran}
641 purely for backward compatibility with legacy compilers. By default,
642 @option{-std=gnu} allows the compiler to accept both types of
643 extensions, but to warn about the use of the latter. Specifying
644 either @option{-std=f95} or @option{-std=f2003} disables both types
645 of extensions, and @option{-std=legacy} allows both without warning.
648 * Old-style kind specifications::
649 * Old-style variable initialization::
650 * Extensions to namelist::
651 * X format descriptor::
652 * Commas in FORMAT specifications::
654 * Hexadecimal constants::
655 * Real array indices::
657 * Implicitly interconvert LOGICAL and INTEGER::
658 * Hollerith constants support::
660 * CONVERT specifier::
663 @node Old-style kind specifications
664 @section Old-style kind specifications
665 @cindex Kind specifications
667 @command{gfortran} allows old-style kind specifications in
668 declarations. These look like:
672 where @code{TYPESPEC} is a basic type, and where @code{k} is a valid kind
673 number for that type. The statement then declares @code{x}, @code{y}
674 and @code{z} to be of type @code{TYPESPEC} with kind @code{k}. In
675 other words, it is equivalent to the standard conforming declaration
680 @node Old-style variable initialization
681 @section Old-style variable initialization
682 @cindex Initialization
684 @command{gfortran} allows old-style initialization of variables of the
688 REAL*8 x(2,2) /3*0.,1./
690 These are only allowed in declarations without double colons
691 (@code{::}), as these were introduced in Fortran 90 which also
692 introduced a new syntax for variable initializations. The syntax for
693 the individual initializers is as for the @code{DATA} statement, but
694 unlike in a @code{DATA} statement, an initializer only applies to the
695 variable immediately preceding. In other words, something like
696 @code{INTEGER I,J/2,3/} is not valid.
698 Examples of standard conforming code equivalent to the above example, are:
701 INTEGER(4) :: i = 1, j = 2
702 REAL(8) :: x(2,2) = RESHAPE((/0.,0.,0.,1./),SHAPE(x))
705 DOUBLE PRECISION x(2,2)
706 DATA i,j,x /1,2,3*0.,1./
709 @node Extensions to namelist
710 @section Extensions to namelist
713 @command{gfortran} fully supports the Fortran 95 standard for namelist I/O
714 including array qualifiers, substrings and fully qualified derived types.
715 The output from a namelist write is compatible with namelist read. The
716 output has all names in upper case and indentation to column 1 after the
717 namelist name. Two extensions are permitted:
719 Old-style use of $ instead of &
722 X(:)%Y(2) = 1.0 2.0 3.0
727 It should be noticed that the default terminator is / rather than &END.
729 Querying of the namelist when inputting from stdin. After at least
730 one space, entering ? sends to stdout the namelist name and the names of
731 the variables in the namelist:
742 Entering =? outputs the namelist to stdout, as if WRITE (*,NML = mynml)
748 X(1)%Y= 0.000000 , 1.000000 , 0.000000 ,
749 X(2)%Y= 0.000000 , 2.000000 , 0.000000 ,
750 X(3)%Y= 0.000000 , 3.000000 , 0.000000 ,
754 To aid this dialog, when input is from stdin, errors send their
755 messages to stderr and execution continues, even if IOSTAT is set.
757 PRINT namelist is permitted. This causes an error if -std=f95 is used.
760 REAL, dimension (4) :: x = (/1.0, 2.0, 3.0, 4.0/)
763 END PROGRAM test_print
766 @node X format descriptor
767 @section X format descriptor
768 @cindex X format descriptor
770 To support legacy codes, @command{gfortran} permits the count field
771 of the X edit descriptor in FORMAT statements to be omitted. When
772 omitted, the count is implicitly assumed to be one.
776 10 FORMAT (I1, X, I1)
779 @node Commas in FORMAT specifications
780 @section Commas in FORMAT specifications
781 @cindex Commas in FORMAT specifications
783 To support legacy codes, @command{gfortran} allows the comma separator
784 to be omitted immediately before and after character string edit
785 descriptors in FORMAT statements.
789 10 FORMAT ('FOO='I1' BAR='I2)
793 @section I/O item lists
794 @cindex I/O item lists
796 To support legacy codes, @command{gfortran} allows the input item list
797 of the READ statement, and the output item lists of the WRITE and PRINT
798 statements to start with a comma.
800 @node Hexadecimal constants
801 @section Hexadecimal constants
802 @cindex Hexadecimal constants
804 As a GNU extension, @command{gfortran} allows hexadecimal constants to
805 be specified using the X prefix, in addition to the standard Z prefix.
807 @node Real array indices
808 @section Real array indices
809 @cindex Real array indices
811 As a GNU extension, @command{gfortran} allows arrays to be indexed using
812 real types, whose values are implicitly converted to integers.
814 @node Unary operators
815 @section Unary operators
816 @cindex Unary operators
818 As a GNU extension, @command{gfortran} allows unary plus and unary
819 minus operators to appear as the second operand of binary arithmetic
820 operators without the need for parenthesis.
826 @node Implicitly interconvert LOGICAL and INTEGER
827 @section Implicitly interconvert LOGICAL and INTEGER
828 @cindex Implicitly interconvert LOGICAL and INTEGER
830 As a GNU extension for backwards compatibility with other compilers,
831 @command{gfortran} allows the implicit conversion of LOGICALs to INTEGERs
832 and vice versa. When converting from a LOGICAL to an INTEGER, the numeric
833 value of @code{.FALSE.} is zero, and that of @code{.TRUE.} is one. When
834 converting from INTEGER to LOGICAL, the value zero is interpreted as
835 @code{.FALSE.} and any nonzero value is interpreted as @code{.TRUE.}.
842 @node Hollerith constants support
843 @section Hollerith constants support
844 @cindex Hollerith constants
846 A Hollerith constant is a string of characters preceded by the letter @samp{H}
847 or @samp{h}, and there must be an literal, unsigned, nonzero default integer
848 constant indicating the number of characters in the string. Hollerith constants
849 are stored as byte strings, one character per byte.
851 @command{gfortran} supports Hollerith constants. They can be used as the right
852 hands in the @code{DATA} statement and @code{ASSIGN} statement, also as the
853 arguments. The left hands can be of Integer, Real, Complex and Logical type.
854 The constant will be padded or truncated to fit the size of left hand.
856 Valid Hollerith constants examples:
859 data x /16Habcdefghijklmnop, 16Hqrstuvwxyz012345/
861 x(1) = 16Habcdefghijklmnop
864 Invalid Hollerith constants examples:
867 a = 8H12345678 ! The Hollerith constant is too long. It will be truncated.
868 a = 0H ! At least one character needed.
872 @section Cray pointers
873 @cindex Cray pointers
875 Cray pointers are part of a non-standard extension that provides a
876 C-like pointer in Fortran. This is accomplished through a pair of
877 variables: an integer "pointer" that holds a memory address, and a
878 "pointee" that is used to dereference the pointer.
880 Pointer/pointee pairs are declared in statements of the form:
882 pointer ( <pointer> , <pointee> )
886 pointer ( <pointer1> , <pointee1> ), ( <pointer2> , <pointee2> ), ...
888 The pointer is an integer that is intended to hold a memory address.
889 The pointee may be an array or scalar. A pointee can be an assumed
890 size array -- that is, the last dimension may be left unspecified by
891 using a '*' in place of a value -- but a pointee cannot be an assumed
892 shape array. No space is allocated for the pointee.
894 The pointee may have its type declared before or after the pointer
895 statement, and its array specification (if any) may be declared
896 before, during, or after the pointer statement. The pointer may be
897 declared as an integer prior to the pointer statement. However, some
898 machines have default integer sizes that are different than the size
899 of a pointer, and so the following code is not portable:
904 If a pointer is declared with a kind that is too small, the compiler
905 will issue a warning; the resulting binary will probably not work
906 correctly, because the memory addresses stored in the pointers may be
907 truncated. It is safer to omit the first line of the above example;
908 if explicit declaration of ipt's type is omitted, then the compiler
909 will ensure that ipt is an integer variable large enough to hold a
912 Pointer arithmetic is valid with Cray pointers, but it is not the same
913 as C pointer arithmetic. Cray pointers are just ordinary integers, so
914 the user is responsible for determining how many bytes to add to a
915 pointer in order to increment it. Consider the following example:
919 pointer (ipt, pointee)
923 The last statement does not set ipt to the address of
924 @code{target(1)}, as one familiar with C pointer arithmetic might
925 expect. Adding 1 to ipt just adds one byte to the address stored in
928 Any expression involving the pointee will be translated to use the
929 value stored in the pointer as the base address.
931 To get the address of elements, this extension provides an intrinsic
932 function loc(), loc() is essentially the C '&' operator, except the
933 address is cast to an integer type:
936 pointer(ipt, arpte(10))
938 ipt = loc(ar) ! Makes arpte is an alias for ar
939 arpte(1) = 1.0 ! Sets ar(1) to 1.0
941 The pointer can also be set by a call to a malloc-type
942 function. There is no malloc intrinsic implemented as part of the
943 Cray pointer extension, but it might be a useful future addition to
944 @command{gfortran}. Even without an intrinsic malloc function,
945 dynamic memory allocation can be combined with Cray pointers by
946 calling a short C function:
950 void mymalloc_(void **ptr, int *nbytes)
952 *ptr = malloc(*nbytes);
961 pointer (ipdata, data(1024))
962 call mymalloc(ipdata,4*1024)
965 Cray pointees often are used to alias an existing variable. For
973 As long as ipt remains unchanged, iarr is now an alias for target.
974 The optimizer, however, will not detect this aliasing, so it is unsafe
975 to use iarr and target simultaneously. Using a pointee in any way
976 that violates the Fortran aliasing rules or assumptions is illegal.
977 It is the user's responsibility to avoid doing this; the compiler
978 works under the assumption that no such aliasing occurs.
980 Cray pointers will work correctly when there is no aliasing (i.e.,
981 when they're used to access a dynamically allocated block of memory),
982 and also in any routine where a pointee is used, but any variable with
983 which it shares storage is not used. Code that violates these rules
984 may not run as the user intends. This is not a bug in the optimizer;
985 any code that violates the aliasing rules is illegal. (Note that this
986 is not unique to gfortran; any Fortran compiler that supports Cray
987 pointers will ``incorrectly'' optimize code with illegal aliasing.)
989 There are a number of restrictions on the attributes that can be
990 applied to Cray pointers and pointees. Pointees may not have the
991 attributes ALLOCATABLE, INTENT, OPTIONAL, DUMMY, TARGET, EXTERNAL,
992 INTRINSIC, or POINTER. Pointers may not have the attributes
993 DIMENSION, POINTER, TARGET, ALLOCATABLE, EXTERNAL, or INTRINSIC.
994 Pointees may not occur in more than one pointer statement. A pointee
995 cannot be a pointer. Pointees cannot occur in equivalence, common, or
998 A pointer may be modified during the course of a program, and this
999 will change the location to which the pointee refers. However, when
1000 pointees are passed as arguments, they are treated as ordinary
1001 variables in the invoked function. Subsequent changes to the pointer
1002 will not change the base address of the array that was passed.
1004 @node CONVERT specifier
1005 @section CONVERT specifier
1006 @cindex CONVERT specifier
1008 gfortran allows the conversion of unformatted data between little-
1009 and big-endian representation to facilitate moving of data
1010 between different systems. The conversion can be indicated with
1011 the @code{CONVERT} specifier on the @code{OPEN} statement.
1012 @xref{GFORTRAN_CONVERT_UNIT}, for an alternative way of specifying
1013 the data format via an environment variable.
1015 Valid values for @code{CONVERT} are:
1017 @item @code{CONVERT='NATIVE'} Use the native format. This is the default.
1018 @item @code{CONVERT='SWAP'} Swap between little- and big-endian.
1019 @item @code{CONVERT='LITTLE_ENDIAN'} Use the little-endian representation
1020 for unformatted files.
1021 @item @code{CONVERT='BIG_ENDIAN'} Use the big-endian representation for
1025 Using the option could look like this:
1027 open(file='big.dat',form='unformatted',access='sequential', &
1028 convert='big_endian')
1031 The value of the conversion can be queried by using
1032 @code{INQUIRE(CONVERT=ch)}. The values returned are
1033 @code{'BIG_ENDIAN'} and @code{'LITTLE_ENDIAN'}.
1035 @code{CONVERT} works between big- and little-endian for
1036 @code{INTEGER} values of all supported kinds and for @code{REAL}
1037 on IEEE systems of kinds 4 and 8. Conversion between different
1038 ``extended double'' types on different architectures such as
1039 m68k and x86_64, which gfortran
1040 supports as @code{REAL(KIND=10)} will probably not work.
1042 @emph{Note that the values specified via the GFORTRAN_CONVERT_UNIT
1043 environment variable will override the CONVERT specifier in the
1044 open statement}. This is to give control over data formats to
1045 a user who does not have the source code of his program available.
1047 Using anything but the native representation for unformatted data
1048 carries a significant speed overhead. If speed in this area matters
1049 to you, it is best if you use this only for data that needs to be
1052 @c ---------------------------------------------------------------------
1053 @include intrinsic.texi
1054 @c ---------------------------------------------------------------------
1056 @c ---------------------------------------------------------------------
1058 @c ---------------------------------------------------------------------
1061 @chapter Contributing
1062 @cindex Contributing
1064 Free software is only possible if people contribute to efforts
1066 We're always in need of more people helping out with ideas
1067 and comments, writing documentation and contributing code.
1069 If you want to contribute to GNU Fortran 95,
1070 have a look at the long lists of projects you can take on.
1071 Some of these projects are small,
1072 some of them are large;
1073 some are completely orthogonal to the rest of what is
1074 happening on @command{gfortran},
1075 but others are ``mainstream'' projects in need of enthusiastic hackers.
1076 All of these projects are important!
1077 We'll eventually get around to the things here,
1078 but they are also things doable by someone who is willing and able.
1087 @section Contributors to GNU Fortran 95
1088 @cindex Contributors
1092 Most of the parser was hand-crafted by @emph{Andy Vaught}, who is
1093 also the initiator of the whole project. Thanks Andy!
1094 Most of the interface with GCC was written by @emph{Paul Brook}.
1096 The following individuals have contributed code and/or
1097 ideas and significant help to the gfortran project
1098 (in no particular order):
1102 @item Katherine Holcomb
1103 @item Tobias Schlüter
1104 @item Steven Bosscher
1107 @item Niels Kristian Bech Jensen
1108 @item Steven Johnson
1113 @item François-Xavier Coudert
1116 @item Janne Blomqvist
1122 The following people have contributed bug reports,
1123 smaller or larger patches,
1124 and much needed feedback and encouragement for the
1125 @command{gfortran} project:
1128 @item Erik Schnetter
1133 Many other individuals have helped debug,
1134 test and improve @command{gfortran} over the past few years,
1135 and we welcome you to do the same!
1136 If you already have done so,
1137 and you would like to see your name listed in the
1138 list above, please contact us.
1146 @item Help build the test suite
1147 Solicit more code for donation to the test suite.
1148 We can keep code private on request.
1150 @item Bug hunting/squishing
1151 Find bugs and write more test cases!
1152 Test cases are especially very welcome,
1153 because it allows us to concentrate on fixing bugs
1154 instead of isolating them.
1156 @item Smaller projects (``bug'' fixes):
1158 @item Allow init exprs to be numbers raised to integer powers.
1159 @item Implement correct rounding.
1160 @item Implement F restrictions on Fortran 95 syntax.
1161 @item See about making Emacs-parsable error messages.
1165 If you wish to work on the runtime libraries,
1166 please contact a project maintainer.
1170 @c ---------------------------------------------------------------------
1172 @c ---------------------------------------------------------------------
1178 The GNU Fortran 95 Compiler aims to be a conforming implementation of
1179 ISO/IEC 1539:1997 (Fortran 95).
1181 In the future it may also support other variants of and extensions to
1182 the Fortran language. These include ANSI Fortran 77, ISO Fortran 90,
1183 ISO Fortran 2003 and OpenMP.
1186 * Fortran 2003 status::
1189 @node Fortran 2003 status
1190 @section Fortran 2003 status
1192 Although @command{gfortran} focuses on implementing the Fortran 95
1193 standard for the time being, a few Fortran 2003 features are currently
1198 Intrinsics @code{command_argument_count}, @code{get_command},
1199 @code{get_command_argument}, and @code{get_environment_variable}.
1202 @cindex Array constructors
1203 @cindex @code{[...]}
1204 Array constructors using square brackets. That is, @code{[...]} rather
1205 than @code{(/.../)}.
1208 @cindex @code{FLUSH} statement
1209 @code{FLUSH} statement.
1212 @cindex @code{IOMSG=} specifier
1213 @code{IOMSG=} specifier for I/O statements.
1216 @cindex @code{ENUM} statement
1217 @cindex @code{ENUMERATOR} statement
1218 @cindex @command{-fshort-enums}
1219 Support for the declaration of enumeration constants via the
1220 @code{ENUM} and @code{ENUMERATOR} statements. Interoperability with
1221 @command{gcc} is guaranteed also for the case where the
1222 @command{-fshort-enums} command line option is given.
1227 @c ---------------------------------------------------------------------
1228 @c GNU General Public License
1229 @c ---------------------------------------------------------------------
1235 @c ---------------------------------------------------------------------
1236 @c GNU Free Documentation License
1237 @c ---------------------------------------------------------------------
1243 @c ---------------------------------------------------------------------
1244 @c Funding Free Software
1245 @c ---------------------------------------------------------------------
1247 @include funding.texi
1249 @c ---------------------------------------------------------------------
1251 @c ---------------------------------------------------------------------