1 \input texinfo @c -*-texinfo-*-
3 @setfilename gfortran.info
4 @set copyrights-gfortran 1999-2008
6 @include gcc-common.texi
8 @settitle The GNU Fortran Compiler
10 @c Create a separate index for command line options
12 @c Merge the standard indexes into a single one.
19 @c TODO: The following "Part" definitions are included here temporarily
20 @c until they are incorporated into the official Texinfo distribution.
21 @c They borrow heavily from Texinfo's \unnchapentry definitions.
28 \vglue\titlepagetopglue
30 \leftline{Part #1:@* #2}
31 \vskip4pt \hrule height 4pt width \hsize \vskip4pt
33 \writetocentry{part}{#2}{#1}
36 \writetocentry{blankpart}{}{}
38 % Part TOC-entry definition for summary contents.
39 \gdef\dosmallpartentry#1#2#3#4{%
40 \vskip .5\baselineskip plus.2\baselineskip
43 \tocentry{Part #2: #1}{\doshortpageno\bgroup#4\egroup}
46 \gdef\dosmallblankpartentry#1#2#3#4{%
47 \vskip .5\baselineskip plus.2\baselineskip
49 % Part TOC-entry definition for regular contents. This has to be
50 % equated to an existing entry to not cause problems when the PDF
52 \gdef\dopartentry#1#2#3#4{%
53 \unnchapentry{Part #2: #1}{}{#3}{#4}
55 \gdef\doblankpartentry#1#2#3#4{}
60 @c Use with @@smallbook.
62 @c %** start of document
64 @c Cause even numbered pages to be printed on the left hand side of
65 @c the page and odd numbered pages to be printed on the right hand
66 @c side of the page. Using this, you can print on both sides of a
67 @c sheet of paper and have the text on the same part of the sheet.
69 @c The text on right hand pages is pushed towards the right hand
70 @c margin and the text on left hand pages is pushed toward the left
72 @c (To provide the reverse effect, set bindingoffset to -0.75in.)
75 @c \global\bindingoffset=0.75in
76 @c \global\normaloffset =0.75in
80 Copyright @copyright{} @value{copyrights-gfortran} Free Software Foundation, Inc.
82 Permission is granted to copy, distribute and/or modify this document
83 under the terms of the GNU Free Documentation License, Version 1.2 or
84 any later version published by the Free Software Foundation; with the
85 Invariant Sections being ``Funding Free Software'', the Front-Cover
86 Texts being (a) (see below), and with the Back-Cover Texts being (b)
87 (see below). A copy of the license is included in the section entitled
88 ``GNU Free Documentation License''.
90 (a) The FSF's Front-Cover Text is:
94 (b) The FSF's Back-Cover Text is:
96 You have freedom to copy and modify this GNU Manual, like GNU
97 software. Copies published by the Free Software Foundation raise
98 funds for GNU development.
102 @dircategory Software development
104 * gfortran: (gfortran). The GNU Fortran Compiler.
106 This file documents the use and the internals of
107 the GNU Fortran compiler, (@command{gfortran}).
109 Published by the Free Software Foundation
110 51 Franklin Street, Fifth Floor
111 Boston, MA 02110-1301 USA
117 @setchapternewpage odd
119 @title Using GNU Fortran
121 @author The @t{gfortran} team
123 @vskip 0pt plus 1filll
124 Published by the Free Software Foundation@*
125 51 Franklin Street, Fifth Floor@*
126 Boston, MA 02110-1301, USA@*
127 @c Last printed ??ber, 19??.@*
128 @c Printed copies are available for $? each.@*
134 @c TODO: The following "Part" definitions are included here temporarily
135 @c until they are incorporated into the official Texinfo distribution.
138 \global\let\partentry=\dosmallpartentry
139 \global\let\blankpartentry=\dosmallblankpartentry
144 \global\let\partentry=\dopartentry
145 \global\let\blankpartentry=\doblankpartentry
151 @c ---------------------------------------------------------------------
152 @c TexInfo table of contents.
153 @c ---------------------------------------------------------------------
160 This manual documents the use of @command{gfortran},
161 the GNU Fortran compiler. You can find in this manual how to invoke
162 @command{gfortran}, as well as its features and incompatibilities.
165 @emph{Warning:} This document, and the compiler it describes, are still
166 under development. While efforts are made to keep it up-to-date, it might
167 not accurately reflect the status of the most recent GNU Fortran compiler.
171 @comment When you add a new menu item, please keep the right hand
172 @comment aligned to the same column. Do not use tabs. This provides
173 @comment better formatting.
178 Part I: Invoking GNU Fortran
179 * Invoking GNU Fortran:: Command options supported by @command{gfortran}.
180 * Runtime:: Influencing runtime behavior with environment variables.
182 Part II: Language Reference
183 * Fortran 2003 and 2008 status:: Fortran 2003 and 2008 features supported by GNU Fortran.
184 * Compiler Characteristics:: KIND type parameters supported.
185 * Mixed-Language Programming:: Interoperability with C
186 * Extensions:: Language extensions implemented by GNU Fortran.
187 * Intrinsic Procedures:: Intrinsic procedures supported by GNU Fortran.
188 * Intrinsic Modules:: Intrinsic modules supported by GNU Fortran.
190 * Contributing:: How you can help.
191 * Copying:: GNU General Public License says
192 how you can copy and share GNU Fortran.
193 * GNU Free Documentation License::
194 How you can copy and share this manual.
195 * Funding:: How to help assure continued work for free software.
196 * Option Index:: Index of command line options
197 * Keyword Index:: Index of concepts
201 @c ---------------------------------------------------------------------
203 @c ---------------------------------------------------------------------
206 @chapter Introduction
208 @c The following duplicates the text on the TexInfo table of contents.
210 This manual documents the use of @command{gfortran}, the GNU Fortran
211 compiler. You can find in this manual how to invoke @command{gfortran},
212 as well as its features and incompatibilities.
215 @emph{Warning:} This document, and the compiler it describes, are still
216 under development. While efforts are made to keep it up-to-date, it
217 might not accurately reflect the status of the most recent GNU Fortran
222 The GNU Fortran compiler front end was
223 designed initially as a free replacement for,
224 or alternative to, the unix @command{f95} command;
225 @command{gfortran} is the command you'll use to invoke the compiler.
228 * About GNU Fortran:: What you should know about the GNU Fortran compiler.
229 * GNU Fortran and GCC:: You can compile Fortran, C, or other programs.
230 * Preprocessing and conditional compilation:: The Fortran preprocessor
231 * GNU Fortran and G77:: Why we chose to start from scratch.
232 * Project Status:: Status of GNU Fortran, roadmap, proposed extensions.
233 * Standards:: Standards supported by GNU Fortran.
237 @c ---------------------------------------------------------------------
239 @c ---------------------------------------------------------------------
241 @node About GNU Fortran
242 @section About GNU Fortran
244 The GNU Fortran compiler supports the Fortran 77, 90 and 95 standards
245 completely, parts of the Fortran 2003 and Fortran 2008 standards, and
246 several vendor extensions. The development goal is to provide the
251 Read a user's program,
252 stored in a file and containing instructions written
253 in Fortran 77, Fortran 90, Fortran 95, Fortran 2003 or Fortran 2008.
254 This file contains @dfn{source code}.
257 Translate the user's program into instructions a computer
258 can carry out more quickly than it takes to translate the
259 instructions in the first
260 place. The result after compilation of a program is
262 code designed to be efficiently translated and processed
263 by a machine such as your computer.
264 Humans usually aren't as good writing machine code
265 as they are at writing Fortran (or C++, Ada, or Java),
266 because it is easy to make tiny mistakes writing machine code.
269 Provide the user with information about the reasons why
270 the compiler is unable to create a binary from the source code.
271 Usually this will be the case if the source code is flawed.
272 The Fortran 90 standard requires that the compiler can point out
273 mistakes to the user.
274 An incorrect usage of the language causes an @dfn{error message}.
276 The compiler will also attempt to diagnose cases where the
277 user's program contains a correct usage of the language,
278 but instructs the computer to do something questionable.
279 This kind of diagnostics message is called a @dfn{warning message}.
282 Provide optional information about the translation passes
283 from the source code to machine code.
284 This can help a user of the compiler to find the cause of
285 certain bugs which may not be obvious in the source code,
286 but may be more easily found at a lower level compiler output.
287 It also helps developers to find bugs in the compiler itself.
290 Provide information in the generated machine code that can
291 make it easier to find bugs in the program (using a debugging tool,
292 called a @dfn{debugger}, such as the GNU Debugger @command{gdb}).
295 Locate and gather machine code already generated to
296 perform actions requested by statements in the user's program.
297 This machine code is organized into @dfn{modules} and is located
298 and @dfn{linked} to the user program.
301 The GNU Fortran compiler consists of several components:
305 A version of the @command{gcc} command
306 (which also might be installed as the system's @command{cc} command)
307 that also understands and accepts Fortran source code.
308 The @command{gcc} command is the @dfn{driver} program for
309 all the languages in the GNU Compiler Collection (GCC);
311 you can compile the source code of any language for
312 which a front end is available in GCC.
315 The @command{gfortran} command itself,
316 which also might be installed as the
317 system's @command{f95} command.
318 @command{gfortran} is just another driver program,
319 but specifically for the Fortran compiler only.
320 The difference with @command{gcc} is that @command{gfortran}
321 will automatically link the correct libraries to your program.
324 A collection of run-time libraries.
325 These libraries contain the machine code needed to support
326 capabilities of the Fortran language that are not directly
327 provided by the machine code generated by the
328 @command{gfortran} compilation phase,
329 such as intrinsic functions and subroutines,
330 and routines for interaction with files and the operating system.
331 @c and mechanisms to spawn,
332 @c unleash and pause threads in parallelized code.
335 The Fortran compiler itself, (@command{f951}).
336 This is the GNU Fortran parser and code generator,
337 linked to and interfaced with the GCC backend library.
338 @command{f951} ``translates'' the source code to
339 assembler code. You would typically not use this
341 instead, the @command{gcc} or @command{gfortran} driver
342 programs will call it for you.
346 @c ---------------------------------------------------------------------
347 @c GNU Fortran and GCC
348 @c ---------------------------------------------------------------------
350 @node GNU Fortran and GCC
351 @section GNU Fortran and GCC
352 @cindex GNU Compiler Collection
355 GNU Fortran is a part of GCC, the @dfn{GNU Compiler Collection}. GCC
356 consists of a collection of front ends for various languages, which
357 translate the source code into a language-independent form called
358 @dfn{GENERIC}. This is then processed by a common middle end which
359 provides optimization, and then passed to one of a collection of back
360 ends which generate code for different computer architectures and
363 Functionally, this is implemented with a driver program (@command{gcc})
364 which provides the command-line interface for the compiler. It calls
365 the relevant compiler front-end program (e.g., @command{f951} for
366 Fortran) for each file in the source code, and then calls the assembler
367 and linker as appropriate to produce the compiled output. In a copy of
368 GCC which has been compiled with Fortran language support enabled,
369 @command{gcc} will recognize files with @file{.f}, @file{.for}, @file{.ftn},
370 @file{.f90}, @file{.f95}, @file{.f03} and @file{.f08} extensions as
371 Fortran source code, and compile it accordingly. A @command{gfortran}
372 driver program is also provided, which is identical to @command{gcc}
373 except that it automatically links the Fortran runtime libraries into the
376 Source files with @file{.f}, @file{.for}, @file{.fpp}, @file{.ftn}, @file{.F},
377 @file{.FOR}, @file{.FPP}, and @file{.FTN} extensions are treated as fixed form.
378 Source files with @file{.f90}, @file{.f95}, @file{.f03}, @file{.f08},
379 @file{.F90}, @file{.F95}, @file{.F03} and @file{.F08} extensions are
380 treated as free form. The capitalized versions of either form are run
381 through preprocessing. Source files with the lower case @file{.fpp}
382 extension are also run through preprocessing.
384 This manual specifically documents the Fortran front end, which handles
385 the programming language's syntax and semantics. The aspects of GCC
386 which relate to the optimization passes and the back-end code generation
387 are documented in the GCC manual; see
388 @ref{Top,,Introduction,gcc,Using the GNU Compiler Collection (GCC)}.
389 The two manuals together provide a complete reference for the GNU
393 @c ---------------------------------------------------------------------
394 @c Preprocessing and conditional compilation
395 @c ---------------------------------------------------------------------
397 @node Preprocessing and conditional compilation
398 @section Preprocessing and conditional compilation
401 @cindex Conditional compilation
402 @cindex Preprocessing
403 @cindex preprocessor, include file handling
405 Many Fortran compilers including GNU Fortran allow passing the source code
406 through a C preprocessor (CPP; sometimes also called the Fortran preprocessor,
407 FPP) to allow for conditional compilation. In the case of GNU Fortran,
408 this is the GNU C Preprocessor in the traditional mode. On systems with
409 case-preserving file names, the preprocessor is automatically invoked if the
410 filename extension is @code{.F}, @code{.FOR}, @code{.FTN}, @code{.fpp},
411 @code{.FPP}, @code{.F90}, @code{.F95}, @code{.F03} or @code{.F08}. To manually
412 invoke the preprocessor on any file, use @option{-cpp}, to disable
413 preprocessing on files where the preprocessor is run automatically, use
416 If a preprocessed file includes another file with the Fortran @code{INCLUDE}
417 statement, the included file is not preprocessed. To preprocess included
418 files, use the equivalent preprocessor statement @code{#include}.
420 If GNU Fortran invokes the preprocessor, @code{__GFORTRAN__}
421 is defined and @code{__GNUC__}, @code{__GNUC_MINOR__} and
422 @code{__GNUC_PATCHLEVEL__} can be used to determine the version of the
423 compiler. See @ref{Top,,Overview,cpp,The C Preprocessor} for details.
425 While CPP is the de-facto standard for preprocessing Fortran code,
426 Part 3 of the Fortran 95 standard (ISO/IEC 1539-3:1998) defines
427 Conditional Compilation, which is not widely used and not directly
428 supported by the GNU Fortran compiler. You can use the program coco
429 to preprocess such files (@uref{http://users.erols.com/dnagle/coco.html}).
432 @c ---------------------------------------------------------------------
433 @c GNU Fortran and G77
434 @c ---------------------------------------------------------------------
436 @node GNU Fortran and G77
437 @section GNU Fortran and G77
439 @cindex @command{g77}
441 The GNU Fortran compiler is the successor to @command{g77}, the Fortran
442 77 front end included in GCC prior to version 4. It is an entirely new
443 program that has been designed to provide Fortran 95 support and
444 extensibility for future Fortran language standards, as well as providing
445 backwards compatibility for Fortran 77 and nearly all of the GNU language
446 extensions supported by @command{g77}.
449 @c ---------------------------------------------------------------------
451 @c ---------------------------------------------------------------------
454 @section Project Status
457 As soon as @command{gfortran} can parse all of the statements correctly,
458 it will be in the ``larva'' state.
459 When we generate code, the ``puppa'' state.
460 When @command{gfortran} is done,
461 we'll see if it will be a beautiful butterfly,
462 or just a big bug....
464 --Andy Vaught, April 2000
467 The start of the GNU Fortran 95 project was announced on
468 the GCC homepage in March 18, 2000
469 (even though Andy had already been working on it for a while,
472 The GNU Fortran compiler is able to compile nearly all
473 standard-compliant Fortran 95, Fortran 90, and Fortran 77 programs,
474 including a number of standard and non-standard extensions, and can be
475 used on real-world programs. In particular, the supported extensions
476 include OpenMP, Cray-style pointers, and several Fortran 2003 and Fortran
477 2008 features such as enumeration, stream I/O, and some of the
478 enhancements to allocatable array support from TR 15581. However, it is
479 still under development and has a few remaining rough edges.
481 At present, the GNU Fortran compiler passes the
482 @uref{http://www.fortran-2000.com/ArnaudRecipes/fcvs21_f95.html,
483 NIST Fortran 77 Test Suite}, and produces acceptable results on the
484 @uref{http://www.netlib.org/lapack/faq.html#1.21, LAPACK Test Suite}.
485 It also provides respectable performance on
486 the @uref{http://www.polyhedron.com/pb05.html, Polyhedron Fortran
487 compiler benchmarks} and the
488 @uref{http://www.llnl.gov/asci_benchmarks/asci/limited/lfk/README.html,
489 Livermore Fortran Kernels test}. It has been used to compile a number of
490 large real-world programs, including
491 @uref{http://mysite.verizon.net/serveall/moene.pdf, the HIRLAM
492 weather-forecasting code} and
493 @uref{http://www.theochem.uwa.edu.au/tonto/, the Tonto quantum
494 chemistry package}; see @url{http://gcc.gnu.org/wiki/GfortranApps} for an
497 Among other things, the GNU Fortran compiler is intended as a replacement
498 for G77. At this point, nearly all programs that could be compiled with
499 G77 can be compiled with GNU Fortran, although there are a few minor known
502 The primary work remaining to be done on GNU Fortran falls into three
503 categories: bug fixing (primarily regarding the treatment of invalid code
504 and providing useful error messages), improving the compiler optimizations
505 and the performance of compiled code, and extending the compiler to support
506 future standards---in particular, Fortran 2003 and Fortran 2008.
509 @c ---------------------------------------------------------------------
511 @c ---------------------------------------------------------------------
518 * Varying Length Character Strings::
521 The GNU Fortran compiler implements
522 ISO/IEC 1539:1997 (Fortran 95). As such, it can also compile essentially all
523 standard-compliant Fortran 90 and Fortran 77 programs. It also supports
524 the ISO/IEC TR-15581 enhancements to allocatable arrays, and
525 the @uref{http://www.openmp.org/drupal/mp-documents/spec25.pdf,
526 OpenMP Application Program Interface v2.5} specification.
528 In the future, the GNU Fortran compiler will also support ISO/IEC
529 1539-1:2004 (Fortran 2003) and future Fortran standards. Partial support
530 of that standard is already provided; the current status of Fortran 2003
531 support is reported in the @ref{Fortran 2003 status} section of the
534 The next version of the Fortran standard (Fortran 2008) is currently
535 being developed and the GNU Fortran compiler supports some of its new
536 features. This support is based on the latest draft of the standard
537 (available from @url{http://www.nag.co.uk/sc22wg5/}) and no guarantee of
538 future compatibility is made, as the final standard might differ from the
539 draft. For more information, see the @ref{Fortran 2008 status} section.
541 Additionally, the GNU Fortran compilers supports the OpenMP specification
542 (version 3.0, @url{http://openmp.org/wp/openmp-specifications/}).
544 @node Varying Length Character Strings
545 @subsection Varying Length Character Strings
546 @cindex Varying length character strings
547 @cindex Varying length strings
548 @cindex strings, varying length
550 The Fortran 95 standard specifies in Part 2 (ISO/IEC 1539-2:2000)
551 varying length character strings. While GNU Fortran currently does not
552 support such strings directly, there exist two Fortran implementations
553 for them, which work with GNU Fortran. They can be found at
554 @uref{http://www.fortran.com/@/iso_varying_string.f95} and at
555 @uref{ftp://ftp.nag.co.uk/@/sc22wg5/@/ISO_VARYING_STRING/}.
559 @c =====================================================================
560 @c PART I: INVOCATION REFERENCE
561 @c =====================================================================
564 \part{I}{Invoking GNU Fortran}
567 @c ---------------------------------------------------------------------
569 @c ---------------------------------------------------------------------
574 @c ---------------------------------------------------------------------
576 @c ---------------------------------------------------------------------
579 @chapter Runtime: Influencing runtime behavior with environment variables
580 @cindex environment variable
582 The behavior of the @command{gfortran} can be influenced by
583 environment variables.
585 Malformed environment variables are silently ignored.
588 * GFORTRAN_STDIN_UNIT:: Unit number for standard input
589 * GFORTRAN_STDOUT_UNIT:: Unit number for standard output
590 * GFORTRAN_STDERR_UNIT:: Unit number for standard error
591 * GFORTRAN_USE_STDERR:: Send library output to standard error
592 * GFORTRAN_TMPDIR:: Directory for scratch files
593 * GFORTRAN_UNBUFFERED_ALL:: Don't buffer I/O for all units.
594 * GFORTRAN_UNBUFFERED_PRECONNECTED:: Don't buffer I/O for preconnected units.
595 * GFORTRAN_SHOW_LOCUS:: Show location for runtime errors
596 * GFORTRAN_OPTIONAL_PLUS:: Print leading + where permitted
597 * GFORTRAN_DEFAULT_RECL:: Default record length for new files
598 * GFORTRAN_LIST_SEPARATOR:: Separator for list output
599 * GFORTRAN_CONVERT_UNIT:: Set endianness for unformatted I/O
600 * GFORTRAN_ERROR_DUMPCORE:: Dump core on run-time errors
601 * GFORTRAN_ERROR_BACKTRACE:: Show backtrace on run-time errors
604 @node GFORTRAN_STDIN_UNIT
605 @section @env{GFORTRAN_STDIN_UNIT}---Unit number for standard input
607 This environment variable can be used to select the unit number
608 preconnected to standard input. This must be a positive integer.
609 The default value is 5.
611 @node GFORTRAN_STDOUT_UNIT
612 @section @env{GFORTRAN_STDOUT_UNIT}---Unit number for standard output
614 This environment variable can be used to select the unit number
615 preconnected to standard output. This must be a positive integer.
616 The default value is 6.
618 @node GFORTRAN_STDERR_UNIT
619 @section @env{GFORTRAN_STDERR_UNIT}---Unit number for standard error
621 This environment variable can be used to select the unit number
622 preconnected to standard error. This must be a positive integer.
623 The default value is 0.
625 @node GFORTRAN_USE_STDERR
626 @section @env{GFORTRAN_USE_STDERR}---Send library output to standard error
628 This environment variable controls where library output is sent.
629 If the first letter is @samp{y}, @samp{Y} or @samp{1}, standard
630 error is used. If the first letter is @samp{n}, @samp{N} or
631 @samp{0}, standard output is used.
633 @node GFORTRAN_TMPDIR
634 @section @env{GFORTRAN_TMPDIR}---Directory for scratch files
636 This environment variable controls where scratch files are
637 created. If this environment variable is missing,
638 GNU Fortran searches for the environment variable @env{TMP}. If
639 this is also missing, the default is @file{/tmp}.
641 @node GFORTRAN_UNBUFFERED_ALL
642 @section @env{GFORTRAN_UNBUFFERED_ALL}---Don't buffer I/O on all units
644 This environment variable controls whether all I/O is unbuffered. If
645 the first letter is @samp{y}, @samp{Y} or @samp{1}, all I/O is
646 unbuffered. This will slow down small sequential reads and writes. If
647 the first letter is @samp{n}, @samp{N} or @samp{0}, I/O is buffered.
650 @node GFORTRAN_UNBUFFERED_PRECONNECTED
651 @section @env{GFORTRAN_UNBUFFERED_PRECONNECTED}---Don't buffer I/O on preconnected units
653 The environment variable named @env{GFORTRAN_UNBUFFERED_PRECONNECTED} controls
654 whether I/O on a preconnected unit (i.e.@: STDOUT or STDERR) is unbuffered. If
655 the first letter is @samp{y}, @samp{Y} or @samp{1}, I/O is unbuffered. This
656 will slow down small sequential reads and writes. If the first letter
657 is @samp{n}, @samp{N} or @samp{0}, I/O is buffered. This is the default.
659 @node GFORTRAN_SHOW_LOCUS
660 @section @env{GFORTRAN_SHOW_LOCUS}---Show location for runtime errors
662 If the first letter is @samp{y}, @samp{Y} or @samp{1}, filename and
663 line numbers for runtime errors are printed. If the first letter is
664 @samp{n}, @samp{N} or @samp{0}, don't print filename and line numbers
665 for runtime errors. The default is to print the location.
667 @node GFORTRAN_OPTIONAL_PLUS
668 @section @env{GFORTRAN_OPTIONAL_PLUS}---Print leading + where permitted
670 If the first letter is @samp{y}, @samp{Y} or @samp{1},
671 a plus sign is printed
672 where permitted by the Fortran standard. If the first letter
673 is @samp{n}, @samp{N} or @samp{0}, a plus sign is not printed
674 in most cases. Default is not to print plus signs.
676 @node GFORTRAN_DEFAULT_RECL
677 @section @env{GFORTRAN_DEFAULT_RECL}---Default record length for new files
679 This environment variable specifies the default record length, in
680 bytes, for files which are opened without a @code{RECL} tag in the
681 @code{OPEN} statement. This must be a positive integer. The
682 default value is 1073741824 bytes (1 GB).
684 @node GFORTRAN_LIST_SEPARATOR
685 @section @env{GFORTRAN_LIST_SEPARATOR}---Separator for list output
687 This environment variable specifies the separator when writing
688 list-directed output. It may contain any number of spaces and
689 at most one comma. If you specify this on the command line,
690 be sure to quote spaces, as in
692 $ GFORTRAN_LIST_SEPARATOR=' , ' ./a.out
694 when @command{a.out} is the compiled Fortran program that you want to run.
695 Default is a single space.
697 @node GFORTRAN_CONVERT_UNIT
698 @section @env{GFORTRAN_CONVERT_UNIT}---Set endianness for unformatted I/O
700 By setting the @env{GFORTRAN_CONVERT_UNIT} variable, it is possible
701 to change the representation of data for unformatted files.
702 The syntax for the @env{GFORTRAN_CONVERT_UNIT} variable is:
704 GFORTRAN_CONVERT_UNIT: mode | mode ';' exception | exception ;
705 mode: 'native' | 'swap' | 'big_endian' | 'little_endian' ;
706 exception: mode ':' unit_list | unit_list ;
707 unit_list: unit_spec | unit_list unit_spec ;
708 unit_spec: INTEGER | INTEGER '-' INTEGER ;
710 The variable consists of an optional default mode, followed by
711 a list of optional exceptions, which are separated by semicolons
712 from the preceding default and each other. Each exception consists
713 of a format and a comma-separated list of units. Valid values for
714 the modes are the same as for the @code{CONVERT} specifier:
717 @item @code{NATIVE} Use the native format. This is the default.
718 @item @code{SWAP} Swap between little- and big-endian.
719 @item @code{LITTLE_ENDIAN} Use the little-endian format
720 for unformatted files.
721 @item @code{BIG_ENDIAN} Use the big-endian format for unformatted files.
723 A missing mode for an exception is taken to mean @code{BIG_ENDIAN}.
724 Examples of values for @env{GFORTRAN_CONVERT_UNIT} are:
726 @item @code{'big_endian'} Do all unformatted I/O in big_endian mode.
727 @item @code{'little_endian;native:10-20,25'} Do all unformatted I/O
728 in little_endian mode, except for units 10 to 20 and 25, which are in
730 @item @code{'10-20'} Units 10 to 20 are big-endian, the rest is native.
733 Setting the environment variables should be done on the command
734 line or via the @command{export}
735 command for @command{sh}-compatible shells and via @command{setenv}
736 for @command{csh}-compatible shells.
738 Example for @command{sh}:
741 $ GFORTRAN_CONVERT_UNIT='big_endian;native:10-20' ./a.out
744 Example code for @command{csh}:
747 % setenv GFORTRAN_CONVERT_UNIT 'big_endian;native:10-20'
751 Using anything but the native representation for unformatted data
752 carries a significant speed overhead. If speed in this area matters
753 to you, it is best if you use this only for data that needs to be
756 @xref{CONVERT specifier}, for an alternative way to specify the
757 data representation for unformatted files. @xref{Runtime Options}, for
758 setting a default data representation for the whole program. The
759 @code{CONVERT} specifier overrides the @option{-fconvert} compile options.
761 @emph{Note that the values specified via the GFORTRAN_CONVERT_UNIT
762 environment variable will override the CONVERT specifier in the
763 open statement}. This is to give control over data formats to
764 users who do not have the source code of their program available.
766 @node GFORTRAN_ERROR_DUMPCORE
767 @section @env{GFORTRAN_ERROR_DUMPCORE}---Dump core on run-time errors
769 If the @env{GFORTRAN_ERROR_DUMPCORE} variable is set to
770 @samp{y}, @samp{Y} or @samp{1} (only the first letter is relevant)
771 then library run-time errors cause core dumps. To disable the core
772 dumps, set the variable to @samp{n}, @samp{N}, @samp{0}. Default
773 is not to core dump unless the @option{-fdump-core} compile option
776 @node GFORTRAN_ERROR_BACKTRACE
777 @section @env{GFORTRAN_ERROR_BACKTRACE}---Show backtrace on run-time errors
779 If the @env{GFORTRAN_ERROR_BACKTRACE} variable is set to
780 @samp{y}, @samp{Y} or @samp{1} (only the first letter is relevant)
781 then a backtrace is printed when a run-time error occurs.
782 To disable the backtracing, set the variable to
783 @samp{n}, @samp{N}, @samp{0}. Default is not to print a backtrace
784 unless the @option{-fbacktrace} compile option
787 @c =====================================================================
788 @c PART II: LANGUAGE REFERENCE
789 @c =====================================================================
792 \part{II}{Language Reference}
795 @c ---------------------------------------------------------------------
796 @c Fortran 2003 and 2008 Status
797 @c ---------------------------------------------------------------------
799 @node Fortran 2003 and 2008 status
800 @chapter Fortran 2003 and 2008 Status
803 * Fortran 2003 status::
804 * Fortran 2008 status::
807 @node Fortran 2003 status
808 @section Fortran 2003 status
810 GNU Fortran supports several Fortran 2003 features; an incomplete
811 list can be found below. See also the
812 @uref{http://gcc.gnu.org/wiki/Fortran2003, wiki page} about Fortran 2003.
816 Intrinsics @code{command_argument_count}, @code{get_command},
817 @code{get_command_argument}, @code{get_environment_variable}, and
821 @cindex array, constructors
823 Array constructors using square brackets. That is, @code{[...]} rather
824 than @code{(/.../)}. Type-specification for array constructors like
825 @code{(/ some-type :: ... /)}.
828 @cindex @code{FLUSH} statement
829 @cindex statement, @code{FLUSH}
830 @code{FLUSH} statement.
833 @cindex @code{IOMSG=} specifier
834 @code{IOMSG=} specifier for I/O statements.
837 @cindex @code{ENUM} statement
838 @cindex @code{ENUMERATOR} statement
839 @cindex statement, @code{ENUM}
840 @cindex statement, @code{ENUMERATOR}
841 @opindex @code{fshort-enums}
842 Support for the declaration of enumeration constants via the
843 @code{ENUM} and @code{ENUMERATOR} statements. Interoperability with
844 @command{gcc} is guaranteed also for the case where the
845 @command{-fshort-enums} command line option is given.
852 @cindex @code{ALLOCATABLE} dummy arguments
853 @code{ALLOCATABLE} dummy arguments.
855 @cindex @code{ALLOCATABLE} function results
856 @code{ALLOCATABLE} function results
858 @cindex @code{ALLOCATABLE} components of derived types
859 @code{ALLOCATABLE} components of derived types
863 @cindex @code{ALLOCATE}
864 The @code{ERRMSG=} tag is now supported in @code{ALLOCATE} and
865 @code{DEALLOCATE} statements. The @code{SOURCE=} tag is supported
866 in an @code{ALLOCATE} statement. An @emph{intrinsic-type-spec}
867 can be used as the @emph{type-spec} in an @code{ALLOCATE} statement;
868 while the use of a @emph{derived-type-name} is currently unsupported.
871 @cindex @code{STREAM} I/O
872 @cindex @code{ACCESS='STREAM'} I/O
873 The @code{OPEN} statement supports the @code{ACCESS='STREAM'} specifier,
874 allowing I/O without any record structure.
877 Namelist input/output for internal files.
880 @cindex @code{PROTECTED} statement
881 @cindex statement, @code{PROTECTED}
882 The @code{PROTECTED} statement and attribute.
885 @cindex @code{VALUE} statement
886 @cindex statement, @code{VALUE}
887 The @code{VALUE} statement and attribute.
890 @cindex @code{VOLATILE} statement
891 @cindex statement, @code{VOLATILE}
892 The @code{VOLATILE} statement and attribute.
895 @cindex @code{IMPORT} statement
896 @cindex statement, @code{IMPORT}
897 The @code{IMPORT} statement, allowing to import
898 host-associated derived types.
901 @cindex @code{USE, INTRINSIC} statement
902 @cindex statement, @code{USE, INTRINSIC}
903 @cindex @code{ISO_FORTRAN_ENV} statement
904 @cindex statement, @code{ISO_FORTRAN_ENV}
905 @code{USE} statement with @code{INTRINSIC} and @code{NON_INTRINSIC}
906 attribute; supported intrinsic modules: @code{ISO_FORTRAN_ENV},
907 @code{OMP_LIB} and @code{OMP_LIB_KINDS}.
910 Renaming of operators in the @code{USE} statement.
913 @cindex ISO C Bindings
914 Interoperability with C (ISO C Bindings)
917 BOZ as argument of @code{INT}, @code{REAL}, @code{DBLE} and @code{CMPLX}.
920 @cindex type-bound procedure
921 @cindex type-bound operator
922 Type-bound procedures with @code{PROCEDURE} or @code{GENERIC}, and operators
923 bound to a derived-type.
926 @cindex @code{EXTENDS}
927 @cindex derived-type extension
928 Extension of derived-types (the @code{EXTENDS(...)} syntax).
931 @cindex @code{ABSTRACT} type
932 @cindex @code{DEFERRED} procedure binding
933 @code{ABSTRACT} derived-types and declaring procedure bindings @code{DEFERRED}.
938 @node Fortran 2008 status
939 @section Fortran 2008 status
941 The next version of the Fortran standard after Fortran 2003 is currently
942 being worked on by the Working Group 5 of Sub-Committee 22 of the Joint
943 Technical Committee 1 of the International Organization for
944 Standardization (ISO) and the International Electrotechnical Commission
945 (IEC). This group is known as @uref{http://www.nag.co.uk/sc22wg5/, WG5}.
946 The next revision of the Fortran standard is informally referred to as
947 Fortran 2008, reflecting its planned release year. The GNU Fortran
948 compiler has support for some of the new features in Fortran 2008. This
949 support is based on the latest draft, available from
950 @url{http://www.nag.co.uk/sc22wg5/}. However, as the final standard may
951 differ from the drafts, no guarantee of backward compatibility can be
952 made and you should only use it for experimental purposes.
954 The @uref{http://gcc.gnu.org/wiki/Fortran2008Status, wiki} has some information
955 about the current Fortran 2008 implementation status.
958 @c ---------------------------------------------------------------------
959 @c Compiler Characteristics
960 @c ---------------------------------------------------------------------
962 @node Compiler Characteristics
963 @chapter Compiler Characteristics
965 @c TODO: Formulate this introduction a little more generally once
966 @c there is more here than KIND type parameters.
968 This chapter describes certain characteristics of the GNU Fortran compiler,
969 namely the KIND type parameter values supported.
972 * KIND Type Parameters::
976 @node KIND Type Parameters
977 @section KIND Type Parameters
980 The @code{KIND} type parameters supported by GNU Fortran for the primitive
986 1, 2, 4, 8*, 16*, default: 4 (1)
989 1, 2, 4, 8*, 16*, default: 4 (1)
992 4, 8, 10**, 16**, default: 4 (2)
995 4, 8, 10**, 16**, default: 4 (2)
1003 * = not available on all systems @*
1004 ** = not available on all systems; additionally 10 and 16 are never
1005 available at the same time @*
1006 (1) Unless -fdefault-integer-8 is used @*
1007 (2) Unless -fdefault-real-8 is used
1010 The @code{KIND} value matches the storage size in bytes, except for
1011 @code{COMPLEX} where the storage size is twice as much (or both real and
1012 imaginary part are a real value of the given size). It is recommended to use
1013 the @code{SELECT_*_KIND} intrinsics instead of the concrete values.
1016 @c ---------------------------------------------------------------------
1018 @c ---------------------------------------------------------------------
1020 @c Maybe this chapter should be merged with the 'Standards' section,
1021 @c whenever that is written :-)
1027 The two sections below detail the extensions to standard Fortran that are
1028 implemented in GNU Fortran, as well as some of the popular or
1029 historically important extensions that are not (or not yet) implemented.
1030 For the latter case, we explain the alternatives available to GNU Fortran
1031 users, including replacement by standard-conforming code or GNU
1035 * Extensions implemented in GNU Fortran::
1036 * Extensions not implemented in GNU Fortran::
1040 @node Extensions implemented in GNU Fortran
1041 @section Extensions implemented in GNU Fortran
1042 @cindex extensions, implemented
1044 GNU Fortran implements a number of extensions over standard
1045 Fortran. This chapter contains information on their syntax and
1046 meaning. There are currently two categories of GNU Fortran
1047 extensions, those that provide functionality beyond that provided
1048 by any standard, and those that are supported by GNU Fortran
1049 purely for backward compatibility with legacy compilers. By default,
1050 @option{-std=gnu} allows the compiler to accept both types of
1051 extensions, but to warn about the use of the latter. Specifying
1052 either @option{-std=f95}, @option{-std=f2003} or @option{-std=f2008}
1053 disables both types of extensions, and @option{-std=legacy} allows both
1057 * Old-style kind specifications::
1058 * Old-style variable initialization::
1059 * Extensions to namelist::
1060 * X format descriptor without count field::
1061 * Commas in FORMAT specifications::
1062 * Missing period in FORMAT specifications::
1064 * BOZ literal constants::
1065 * Real array indices::
1067 * Implicitly convert LOGICAL and INTEGER values::
1068 * Hollerith constants support::
1070 * CONVERT specifier::
1072 * Argument list functions::
1075 @node Old-style kind specifications
1076 @subsection Old-style kind specifications
1077 @cindex kind, old-style
1079 GNU Fortran allows old-style kind specifications in declarations. These
1085 where @code{TYPESPEC} is a basic type (@code{INTEGER}, @code{REAL},
1086 etc.), and where @code{size} is a byte count corresponding to the
1087 storage size of a valid kind for that type. (For @code{COMPLEX}
1088 variables, @code{size} is the total size of the real and imaginary
1089 parts.) The statement then declares @code{x}, @code{y} and @code{z} to
1090 be of type @code{TYPESPEC} with the appropriate kind. This is
1091 equivalent to the standard-conforming declaration
1096 where @code{k} is the kind parameter suitable for the intended precision. As
1097 kind parameters are implementation-dependent, use the @code{KIND},
1098 @code{SELECTED_INT_KIND} and @code{SELECTED_REAL_KIND} intrinsics to retrieve
1099 the correct value, for instance @code{REAL*8 x} can be replaced by:
1101 INTEGER, PARAMETER :: dbl = KIND(1.0d0)
1105 @node Old-style variable initialization
1106 @subsection Old-style variable initialization
1108 GNU Fortran allows old-style initialization of variables of the
1112 REAL x(2,2) /3*0.,1./
1114 The syntax for the initializers is as for the @code{DATA} statement, but
1115 unlike in a @code{DATA} statement, an initializer only applies to the
1116 variable immediately preceding the initialization. In other words,
1117 something like @code{INTEGER I,J/2,3/} is not valid. This style of
1118 initialization is only allowed in declarations without double colons
1119 (@code{::}); the double colons were introduced in Fortran 90, which also
1120 introduced a standard syntax for initializing variables in type
1123 Examples of standard-conforming code equivalent to the above example
1127 INTEGER :: i = 1, j = 2
1128 REAL :: x(2,2) = RESHAPE((/0.,0.,0.,1./),SHAPE(x))
1132 DATA i/1/, j/2/, x/3*0.,1./
1135 Note that variables which are explicitly initialized in declarations
1136 or in @code{DATA} statements automatically acquire the @code{SAVE}
1139 @node Extensions to namelist
1140 @subsection Extensions to namelist
1143 GNU Fortran fully supports the Fortran 95 standard for namelist I/O
1144 including array qualifiers, substrings and fully qualified derived types.
1145 The output from a namelist write is compatible with namelist read. The
1146 output has all names in upper case and indentation to column 1 after the
1147 namelist name. Two extensions are permitted:
1149 Old-style use of @samp{$} instead of @samp{&}
1152 X(:)%Y(2) = 1.0 2.0 3.0
1157 It should be noted that the default terminator is @samp{/} rather than
1160 Querying of the namelist when inputting from stdin. After at least
1161 one space, entering @samp{?} sends to stdout the namelist name and the names of
1162 the variables in the namelist:
1173 Entering @samp{=?} outputs the namelist to stdout, as if
1174 @code{WRITE(*,NML = mynml)} had been called:
1179 X(1)%Y= 0.000000 , 1.000000 , 0.000000 ,
1180 X(2)%Y= 0.000000 , 2.000000 , 0.000000 ,
1181 X(3)%Y= 0.000000 , 3.000000 , 0.000000 ,
1185 To aid this dialog, when input is from stdin, errors send their
1186 messages to stderr and execution continues, even if @code{IOSTAT} is set.
1188 @code{PRINT} namelist is permitted. This causes an error if
1189 @option{-std=f95} is used.
1192 REAL, dimension (4) :: x = (/1.0, 2.0, 3.0, 4.0/)
1195 END PROGRAM test_print
1198 Expanded namelist reads are permitted. This causes an error if
1199 @option{-std=f95} is used. In the following example, the first element
1200 of the array will be given the value 0.00 and the two succeeding
1201 elements will be given the values 1.00 and 2.00.
1204 X(1,1) = 0.00 , 1.00 , 2.00
1208 @node X format descriptor without count field
1209 @subsection @code{X} format descriptor without count field
1211 To support legacy codes, GNU Fortran permits the count field of the
1212 @code{X} edit descriptor in @code{FORMAT} statements to be omitted.
1213 When omitted, the count is implicitly assumed to be one.
1217 10 FORMAT (I1, X, I1)
1220 @node Commas in FORMAT specifications
1221 @subsection Commas in @code{FORMAT} specifications
1223 To support legacy codes, GNU Fortran allows the comma separator
1224 to be omitted immediately before and after character string edit
1225 descriptors in @code{FORMAT} statements.
1229 10 FORMAT ('FOO='I1' BAR='I2)
1233 @node Missing period in FORMAT specifications
1234 @subsection Missing period in @code{FORMAT} specifications
1236 To support legacy codes, GNU Fortran allows missing periods in format
1237 specifications if and only if @option{-std=legacy} is given on the
1238 command line. This is considered non-conforming code and is
1247 @node I/O item lists
1248 @subsection I/O item lists
1249 @cindex I/O item lists
1251 To support legacy codes, GNU Fortran allows the input item list
1252 of the @code{READ} statement, and the output item lists of the
1253 @code{WRITE} and @code{PRINT} statements, to start with a comma.
1255 @node BOZ literal constants
1256 @subsection BOZ literal constants
1257 @cindex BOZ literal constants
1259 Besides decimal constants, Fortran also supports binary (@code{b}),
1260 octal (@code{o}) and hexadecimal (@code{z}) integer constants. The
1261 syntax is: @samp{prefix quote digits quote}, were the prefix is
1262 either @code{b}, @code{o} or @code{z}, quote is either @code{'} or
1263 @code{"} and the digits are for binary @code{0} or @code{1}, for
1264 octal between @code{0} and @code{7}, and for hexadecimal between
1265 @code{0} and @code{F}. (Example: @code{b'01011101'}.)
1267 Up to Fortran 95, BOZ literals were only allowed to initialize
1268 integer variables in DATA statements. Since Fortran 2003 BOZ literals
1269 are also allowed as argument of @code{REAL}, @code{DBLE}, @code{INT}
1270 and @code{CMPLX}; the result is the same as if the integer BOZ
1271 literal had been converted by @code{TRANSFER} to, respectively,
1272 @code{real}, @code{double precision}, @code{integer} or @code{complex}.
1273 As GNU Fortran extension the intrinsic procedures @code{FLOAT},
1274 @code{DFLOAT}, @code{COMPLEX} and @code{DCMPLX} are treated alike.
1276 As an extension, GNU Fortran allows hexadecimal BOZ literal constants to
1277 be specified using the @code{X} prefix, in addition to the standard
1278 @code{Z} prefix. The BOZ literal can also be specified by adding a
1279 suffix to the string, for example, @code{Z'ABC'} and @code{'ABC'Z} are
1282 Furthermore, GNU Fortran allows using BOZ literal constants outside
1283 DATA statements and the four intrinsic functions allowed by Fortran 2003.
1284 In DATA statements, in direct assignments, where the right-hand side
1285 only contains a BOZ literal constant, and for old-style initializers of
1286 the form @code{integer i /o'0173'/}, the constant is transferred
1287 as if @code{TRANSFER} had been used; for @code{COMPLEX} numbers, only
1288 the real part is initialized unless @code{CMPLX} is used. In all other
1289 cases, the BOZ literal constant is converted to an @code{INTEGER} value with
1290 the largest decimal representation. This value is then converted
1291 numerically to the type and kind of the variable in question.
1292 (For instance, @code{real :: r = b'0000001' + 1} initializes @code{r}
1293 with @code{2.0}.) As different compilers implement the extension
1294 differently, one should be careful when doing bitwise initialization
1295 of non-integer variables.
1297 Note that initializing an @code{INTEGER} variable with a statement such
1298 as @code{DATA i/Z'FFFFFFFF'/} will give an integer overflow error rather
1299 than the desired result of @math{-1} when @code{i} is a 32-bit integer
1300 on a system that supports 64-bit integers. The @samp{-fno-range-check}
1301 option can be used as a workaround for legacy code that initializes
1302 integers in this manner.
1304 @node Real array indices
1305 @subsection Real array indices
1306 @cindex array, indices of type real
1308 As an extension, GNU Fortran allows the use of @code{REAL} expressions
1309 or variables as array indices.
1311 @node Unary operators
1312 @subsection Unary operators
1313 @cindex operators, unary
1315 As an extension, GNU Fortran allows unary plus and unary minus operators
1316 to appear as the second operand of binary arithmetic operators without
1317 the need for parenthesis.
1323 @node Implicitly convert LOGICAL and INTEGER values
1324 @subsection Implicitly convert @code{LOGICAL} and @code{INTEGER} values
1325 @cindex conversion, to integer
1326 @cindex conversion, to logical
1328 As an extension for backwards compatibility with other compilers, GNU
1329 Fortran allows the implicit conversion of @code{LOGICAL} values to
1330 @code{INTEGER} values and vice versa. When converting from a
1331 @code{LOGICAL} to an @code{INTEGER}, @code{.FALSE.} is interpreted as
1332 zero, and @code{.TRUE.} is interpreted as one. When converting from
1333 @code{INTEGER} to @code{LOGICAL}, the value zero is interpreted as
1334 @code{.FALSE.} and any nonzero value is interpreted as @code{.TRUE.}.
1345 However, there is no implicit conversion of @code{INTEGER} values in
1346 @code{if}-statements, nor of @code{LOGICAL} or @code{INTEGER} values
1349 @node Hollerith constants support
1350 @subsection Hollerith constants support
1351 @cindex Hollerith constants
1353 GNU Fortran supports Hollerith constants in assignments, function
1354 arguments, and @code{DATA} and @code{ASSIGN} statements. A Hollerith
1355 constant is written as a string of characters preceded by an integer
1356 constant indicating the character count, and the letter @code{H} or
1357 @code{h}, and stored in bytewise fashion in a numeric (@code{INTEGER},
1358 @code{REAL}, or @code{complex}) or @code{LOGICAL} variable. The
1359 constant will be padded or truncated to fit the size of the variable in
1362 Examples of valid uses of Hollerith constants:
1365 data x /16Habcdefghijklmnop, 16Hqrstuvwxyz012345/
1366 x(1) = 16HABCDEFGHIJKLMNOP
1370 Invalid Hollerith constants examples:
1373 a = 8H12345678 ! Valid, but the Hollerith constant will be truncated.
1374 a = 0H ! At least one character is needed.
1377 In general, Hollerith constants were used to provide a rudimentary
1378 facility for handling character strings in early Fortran compilers,
1379 prior to the introduction of @code{CHARACTER} variables in Fortran 77;
1380 in those cases, the standard-compliant equivalent is to convert the
1381 program to use proper character strings. On occasion, there may be a
1382 case where the intent is specifically to initialize a numeric variable
1383 with a given byte sequence. In these cases, the same result can be
1384 obtained by using the @code{TRANSFER} statement, as in this example.
1386 INTEGER(KIND=4) :: a
1387 a = TRANSFER ("abcd", a) ! equivalent to: a = 4Habcd
1392 @subsection Cray pointers
1393 @cindex pointer, Cray
1395 Cray pointers are part of a non-standard extension that provides a
1396 C-like pointer in Fortran. This is accomplished through a pair of
1397 variables: an integer "pointer" that holds a memory address, and a
1398 "pointee" that is used to dereference the pointer.
1400 Pointer/pointee pairs are declared in statements of the form:
1402 pointer ( <pointer> , <pointee> )
1406 pointer ( <pointer1> , <pointee1> ), ( <pointer2> , <pointee2> ), ...
1408 The pointer is an integer that is intended to hold a memory address.
1409 The pointee may be an array or scalar. A pointee can be an assumed
1410 size array---that is, the last dimension may be left unspecified by
1411 using a @code{*} in place of a value---but a pointee cannot be an
1412 assumed shape array. No space is allocated for the pointee.
1414 The pointee may have its type declared before or after the pointer
1415 statement, and its array specification (if any) may be declared
1416 before, during, or after the pointer statement. The pointer may be
1417 declared as an integer prior to the pointer statement. However, some
1418 machines have default integer sizes that are different than the size
1419 of a pointer, and so the following code is not portable:
1424 If a pointer is declared with a kind that is too small, the compiler
1425 will issue a warning; the resulting binary will probably not work
1426 correctly, because the memory addresses stored in the pointers may be
1427 truncated. It is safer to omit the first line of the above example;
1428 if explicit declaration of ipt's type is omitted, then the compiler
1429 will ensure that ipt is an integer variable large enough to hold a
1432 Pointer arithmetic is valid with Cray pointers, but it is not the same
1433 as C pointer arithmetic. Cray pointers are just ordinary integers, so
1434 the user is responsible for determining how many bytes to add to a
1435 pointer in order to increment it. Consider the following example:
1439 pointer (ipt, pointee)
1443 The last statement does not set @code{ipt} to the address of
1444 @code{target(1)}, as it would in C pointer arithmetic. Adding @code{1}
1445 to @code{ipt} just adds one byte to the address stored in @code{ipt}.
1447 Any expression involving the pointee will be translated to use the
1448 value stored in the pointer as the base address.
1450 To get the address of elements, this extension provides an intrinsic
1451 function @code{LOC()}. The @code{LOC()} function is equivalent to the
1452 @code{&} operator in C, except the address is cast to an integer type:
1455 pointer(ipt, arpte(10))
1457 ipt = loc(ar) ! Makes arpte is an alias for ar
1458 arpte(1) = 1.0 ! Sets ar(1) to 1.0
1460 The pointer can also be set by a call to the @code{MALLOC} intrinsic
1463 Cray pointees often are used to alias an existing variable. For
1471 As long as @code{ipt} remains unchanged, @code{iarr} is now an alias for
1472 @code{target}. The optimizer, however, will not detect this aliasing, so
1473 it is unsafe to use @code{iarr} and @code{target} simultaneously. Using
1474 a pointee in any way that violates the Fortran aliasing rules or
1475 assumptions is illegal. It is the user's responsibility to avoid doing
1476 this; the compiler works under the assumption that no such aliasing
1479 Cray pointers will work correctly when there is no aliasing (i.e., when
1480 they are used to access a dynamically allocated block of memory), and
1481 also in any routine where a pointee is used, but any variable with which
1482 it shares storage is not used. Code that violates these rules may not
1483 run as the user intends. This is not a bug in the optimizer; any code
1484 that violates the aliasing rules is illegal. (Note that this is not
1485 unique to GNU Fortran; any Fortran compiler that supports Cray pointers
1486 will ``incorrectly'' optimize code with illegal aliasing.)
1488 There are a number of restrictions on the attributes that can be applied
1489 to Cray pointers and pointees. Pointees may not have the
1490 @code{ALLOCATABLE}, @code{INTENT}, @code{OPTIONAL}, @code{DUMMY},
1491 @code{TARGET}, @code{INTRINSIC}, or @code{POINTER} attributes. Pointers
1492 may not have the @code{DIMENSION}, @code{POINTER}, @code{TARGET},
1493 @code{ALLOCATABLE}, @code{EXTERNAL}, or @code{INTRINSIC} attributes.
1494 Pointees may not occur in more than one pointer statement. A pointee
1495 cannot be a pointer. Pointees cannot occur in equivalence, common, or
1498 A Cray pointer may also point to a function or a subroutine. For
1499 example, the following excerpt is valid:
1503 pointer (subptr,subpte)
1513 A pointer may be modified during the course of a program, and this
1514 will change the location to which the pointee refers. However, when
1515 pointees are passed as arguments, they are treated as ordinary
1516 variables in the invoked function. Subsequent changes to the pointer
1517 will not change the base address of the array that was passed.
1519 @node CONVERT specifier
1520 @subsection @code{CONVERT} specifier
1521 @cindex @code{CONVERT} specifier
1523 GNU Fortran allows the conversion of unformatted data between little-
1524 and big-endian representation to facilitate moving of data
1525 between different systems. The conversion can be indicated with
1526 the @code{CONVERT} specifier on the @code{OPEN} statement.
1527 @xref{GFORTRAN_CONVERT_UNIT}, for an alternative way of specifying
1528 the data format via an environment variable.
1530 Valid values for @code{CONVERT} are:
1532 @item @code{CONVERT='NATIVE'} Use the native format. This is the default.
1533 @item @code{CONVERT='SWAP'} Swap between little- and big-endian.
1534 @item @code{CONVERT='LITTLE_ENDIAN'} Use the little-endian representation
1535 for unformatted files.
1536 @item @code{CONVERT='BIG_ENDIAN'} Use the big-endian representation for
1540 Using the option could look like this:
1542 open(file='big.dat',form='unformatted',access='sequential', &
1543 convert='big_endian')
1546 The value of the conversion can be queried by using
1547 @code{INQUIRE(CONVERT=ch)}. The values returned are
1548 @code{'BIG_ENDIAN'} and @code{'LITTLE_ENDIAN'}.
1550 @code{CONVERT} works between big- and little-endian for
1551 @code{INTEGER} values of all supported kinds and for @code{REAL}
1552 on IEEE systems of kinds 4 and 8. Conversion between different
1553 ``extended double'' types on different architectures such as
1554 m68k and x86_64, which GNU Fortran
1555 supports as @code{REAL(KIND=10)} and @code{REAL(KIND=16)}, will
1558 @emph{Note that the values specified via the GFORTRAN_CONVERT_UNIT
1559 environment variable will override the CONVERT specifier in the
1560 open statement}. This is to give control over data formats to
1561 users who do not have the source code of their program available.
1563 Using anything but the native representation for unformatted data
1564 carries a significant speed overhead. If speed in this area matters
1565 to you, it is best if you use this only for data that needs to be
1572 OpenMP (Open Multi-Processing) is an application programming
1573 interface (API) that supports multi-platform shared memory
1574 multiprocessing programming in C/C++ and Fortran on many
1575 architectures, including Unix and Microsoft Windows platforms.
1576 It consists of a set of compiler directives, library routines,
1577 and environment variables that influence run-time behavior.
1579 GNU Fortran strives to be compatible to the
1580 @uref{http://www.openmp.org/mp-documents/spec30.pdf,
1581 OpenMP Application Program Interface v3.0}.
1583 To enable the processing of the OpenMP directive @code{!$omp} in
1584 free-form source code; the @code{c$omp}, @code{*$omp} and @code{!$omp}
1585 directives in fixed form; the @code{!$} conditional compilation sentinels
1586 in free form; and the @code{c$}, @code{*$} and @code{!$} sentinels
1587 in fixed form, @command{gfortran} needs to be invoked with the
1588 @option{-fopenmp}. This also arranges for automatic linking of the
1589 GNU OpenMP runtime library @ref{Top,,libgomp,libgomp,GNU OpenMP
1592 The OpenMP Fortran runtime library routines are provided both in a
1593 form of a Fortran 90 module named @code{omp_lib} and in a form of
1594 a Fortran @code{include} file named @file{omp_lib.h}.
1596 An example of a parallelized loop taken from Appendix A.1 of
1597 the OpenMP Application Program Interface v2.5:
1599 SUBROUTINE A1(N, A, B)
1602 !$OMP PARALLEL DO !I is private by default
1604 B(I) = (A(I) + A(I-1)) / 2.0
1606 !$OMP END PARALLEL DO
1613 @option{-fopenmp} implies @option{-frecursive}, i.e., all local arrays
1614 will be allocated on the stack. When porting existing code to OpenMP,
1615 this may lead to surprising results, especially to segmentation faults
1616 if the stacksize is limited.
1619 On glibc-based systems, OpenMP enabled applications cannot be statically
1620 linked due to limitations of the underlying pthreads-implementation. It
1621 might be possible to get a working solution if
1622 @command{-Wl,--whole-archive -lpthread -Wl,--no-whole-archive} is added
1623 to the command line. However, this is not supported by @command{gcc} and
1624 thus not recommended.
1627 @node Argument list functions
1628 @subsection Argument list functions @code{%VAL}, @code{%REF} and @code{%LOC}
1629 @cindex argument list functions
1634 GNU Fortran supports argument list functions @code{%VAL}, @code{%REF}
1635 and @code{%LOC} statements, for backward compatibility with g77.
1636 It is recommended that these should be used only for code that is
1637 accessing facilities outside of GNU Fortran, such as operating system
1638 or windowing facilities. It is best to constrain such uses to isolated
1639 portions of a program--portions that deal specifically and exclusively
1640 with low-level, system-dependent facilities. Such portions might well
1641 provide a portable interface for use by the program as a whole, but are
1642 themselves not portable, and should be thoroughly tested each time they
1643 are rebuilt using a new compiler or version of a compiler.
1645 @code{%VAL} passes a scalar argument by value, @code{%REF} passes it by
1646 reference and @code{%LOC} passes its memory location. Since gfortran
1647 already passes scalar arguments by reference, @code{%REF} is in effect
1648 a do-nothing. @code{%LOC} has the same effect as a Fortran pointer.
1650 An example of passing an argument by value to a C subroutine foo.:
1653 C prototype void foo_ (float x);
1662 For details refer to the g77 manual
1663 @uref{http://gcc.gnu.org/onlinedocs/gcc-3.4.6/g77/index.html#Top}.
1665 Also, @code{c_by_val.f} and its partner @code{c_by_val.c} of the
1666 GNU Fortran testsuite are worth a look.
1669 @node Extensions not implemented in GNU Fortran
1670 @section Extensions not implemented in GNU Fortran
1671 @cindex extensions, not implemented
1673 The long history of the Fortran language, its wide use and broad
1674 userbase, the large number of different compiler vendors and the lack of
1675 some features crucial to users in the first standards have lead to the
1676 existence of a number of important extensions to the language. While
1677 some of the most useful or popular extensions are supported by the GNU
1678 Fortran compiler, not all existing extensions are supported. This section
1679 aims at listing these extensions and offering advice on how best make
1680 code that uses them running with the GNU Fortran compiler.
1682 @c More can be found here:
1683 @c -- http://gcc.gnu.org/onlinedocs/gcc-3.4.6/g77/Missing-Features.html
1684 @c -- the list of Fortran and libgfortran bugs closed as WONTFIX:
1685 @c http://tinyurl.com/2u4h5y
1688 * STRUCTURE and RECORD::
1689 @c * UNION and MAP::
1690 * ENCODE and DECODE statements::
1691 * Variable FORMAT expressions::
1692 @c * Q edit descriptor::
1693 @c * AUTOMATIC statement::
1694 @c * TYPE and ACCEPT I/O Statements::
1695 @c * .XOR. operator::
1696 @c * CARRIAGECONTROL, DEFAULTFILE, DISPOSE and RECORDTYPE I/O specifiers::
1697 @c * Omitted arguments in procedure call:
1701 @node STRUCTURE and RECORD
1702 @subsection @code{STRUCTURE} and @code{RECORD}
1703 @cindex @code{STRUCTURE}
1704 @cindex @code{RECORD}
1706 Structures are user-defined aggregate data types; this functionality was
1707 standardized in Fortran 90 with an different syntax, under the name of
1708 ``derived types''. Here is an example of code using the non portable
1712 ! Declaring a structure named ``item'' and containing three fields:
1713 ! an integer ID, an description string and a floating-point price.
1716 CHARACTER(LEN=200) description
1720 ! Define two variables, an single record of type ``item''
1721 ! named ``pear'', and an array of items named ``store_catalog''
1722 RECORD /item/ pear, store_catalog(100)
1724 ! We can directly access the fields of both variables
1726 pear.description = "juicy D'Anjou pear"
1728 store_catalog(7).id = 7831
1729 store_catalog(7).description = "milk bottle"
1730 store_catalog(7).price = 1.2
1732 ! We can also manipulate the whole structure
1733 store_catalog(12) = pear
1734 print *, store_catalog(12)
1738 This code can easily be rewritten in the Fortran 90 syntax as following:
1741 ! ``STRUCTURE /name/ ... END STRUCTURE'' becomes
1742 ! ``TYPE name ... END TYPE''
1745 CHARACTER(LEN=200) description
1749 ! ``RECORD /name/ variable'' becomes ``TYPE(name) variable''
1750 TYPE(item) pear, store_catalog(100)
1752 ! Instead of using a dot (.) to access fields of a record, the
1753 ! standard syntax uses a percent sign (%)
1755 pear%description = "juicy D'Anjou pear"
1757 store_catalog(7)%id = 7831
1758 store_catalog(7)%description = "milk bottle"
1759 store_catalog(7)%price = 1.2
1761 ! Assignments of a whole variable don't change
1762 store_catalog(12) = pear
1763 print *, store_catalog(12)
1767 @c @node UNION and MAP
1768 @c @subsection @code{UNION} and @code{MAP}
1769 @c @cindex @code{UNION}
1770 @c @cindex @code{MAP}
1772 @c For help writing this one, see
1773 @c http://www.eng.umd.edu/~nsw/ench250/fortran1.htm#UNION and
1774 @c http://www.tacc.utexas.edu/services/userguides/pgi/pgiws_ug/pgi32u06.htm
1777 @node ENCODE and DECODE statements
1778 @subsection @code{ENCODE} and @code{DECODE} statements
1779 @cindex @code{ENCODE}
1780 @cindex @code{DECODE}
1782 GNU Fortran doesn't support the @code{ENCODE} and @code{DECODE}
1783 statements. These statements are best replaced by @code{READ} and
1784 @code{WRITE} statements involving internal files (@code{CHARACTER}
1785 variables and arrays), which have been part of the Fortran standard since
1786 Fortran 77. For example, replace a code fragment like
1791 c ... Code that sets LINE
1792 DECODE (80, 9000, LINE) A, B, C
1793 9000 FORMAT (1X, 3(F10.5))
1800 CHARACTER(LEN=80) LINE
1802 c ... Code that sets LINE
1803 READ (UNIT=LINE, FMT=9000) A, B, C
1804 9000 FORMAT (1X, 3(F10.5))
1807 Similarly, replace a code fragment like
1812 c ... Code that sets A, B and C
1813 ENCODE (80, 9000, LINE) A, B, C
1814 9000 FORMAT (1X, 'OUTPUT IS ', 3(F10.5))
1821 CHARACTER(LEN=80) LINE
1823 c ... Code that sets A, B and C
1824 WRITE (UNIT=LINE, FMT=9000) A, B, C
1825 9000 FORMAT (1X, 'OUTPUT IS ', 3(F10.5))
1829 @node Variable FORMAT expressions
1830 @subsection Variable @code{FORMAT} expressions
1831 @cindex @code{FORMAT}
1833 A variable @code{FORMAT} expression is format statement which includes
1834 angle brackets enclosing a Fortran expression: @code{FORMAT(I<N>)}. GNU
1835 Fortran does not support this legacy extension. The effect of variable
1836 format expressions can be reproduced by using the more powerful (and
1837 standard) combination of internal output and string formats. For example,
1838 replace a code fragment like this:
1849 c Variable declaration
1852 c Other code here...
1854 WRITE(FMT,'("(I", I0, ")")') N+1
1862 c Variable declaration
1863 CHARACTER(LEN=20) FMT
1865 c Other code here...
1868 WRITE(6,"(I" // ADJUSTL(FMT) // ")") INT1
1872 @c ---------------------------------------------------------------------
1873 @c Mixed-Language Programming
1874 @c ---------------------------------------------------------------------
1876 @node Mixed-Language Programming
1877 @chapter Mixed-Language Programming
1878 @cindex Interoperability
1879 @cindex Mixed-language programming
1882 * Interoperability with C::
1883 * GNU Fortran Compiler Directives::
1884 * Non-Fortran Main Program::
1887 This chapter is about mixed-language interoperability, but also applies
1888 if one links Fortran code compiled by different compilers. In most cases,
1889 use of the C Binding features of the Fortran 2003 standard is sufficient,
1890 and their use is highly recommended.
1893 @node Interoperability with C
1894 @section Interoperability with C
1898 * Further Interoperability of Fortran with C::
1899 * Derived Types and struct::
1900 * Interoperable Global Variables::
1901 * Interoperable Subroutines and Functions::
1904 Since Fortran 2003 (ISO/IEC 1539-1:2004(E)) there is a
1905 standardized way to generate procedure and derived-type
1906 declarations and global variables which are interoperable with C
1907 (ISO/IEC 9899:1999). The @code{bind(C)} attribute has been added
1908 to inform the compiler that a symbol shall be interoperable with C;
1909 also, some constraints are added. Note, however, that not
1910 all C features have a Fortran equivalent or vice versa. For instance,
1911 neither C's unsigned integers nor C's functions with variable number
1912 of arguments have an equivalent in Fortran.
1915 @node Intrinsic Types
1916 @subsection Intrinsic Types
1918 In order to ensure that exactly the same variable type and kind is used
1919 in C and Fortran, the named constants shall be used which are defined in the
1920 @code{ISO_C_BINDING} intrinsic module. That module contains named constants
1921 for kind parameters and character named constants for the escape sequences
1922 in C. For a list of the constants, see @ref{ISO_C_BINDING}.
1924 @node Derived Types and struct
1925 @subsection Derived Types and struct
1927 For compatibility of derived types with @code{struct}, one needs to use
1928 the @code{BIND(C)} attribute in the type declaration. For instance, the
1929 following type declaration
1933 TYPE, BIND(C) :: myType
1934 INTEGER(C_INT) :: i1, i2
1935 INTEGER(C_SIGNED_CHAR) :: i3
1936 REAL(C_DOUBLE) :: d1
1937 COMPLEX(C_FLOAT_COMPLEX) :: c1
1938 CHARACTER(KIND=C_CHAR) :: str(5)
1942 matches the following @code{struct} declaration in C
1947 /* Note: "char" might be signed or unsigned. */
1955 Derived types with the C binding attribute shall not have the @code{sequence}
1956 attribute, type parameters, the @code{extends} attribute, nor type-bound
1957 procedures. Every component must be of interoperable type and kind and may not
1958 have the @code{pointer} or @code{allocatable} attribute. The names of the
1959 variables are irrelevant for interoperability.
1961 As there exist no direct Fortran equivalents, neither unions nor structs
1962 with bit field or variable-length array members are interoperable.
1964 @node Interoperable Global Variables
1965 @subsection Interoperable Global Variables
1967 Variables can be made accessible from C using the C binding attribute,
1968 optionally together with specifying a binding name. Those variables
1969 have to be declared in the declaration part of a @code{MODULE},
1970 be of interoperable type, and have neither the @code{pointer} nor
1971 the @code{allocatable} attribute.
1977 integer(C_INT), bind(C, name="_MyProject_flags") :: global_flag
1978 type(myType), bind(C) :: tp
1982 Here, @code{_MyProject_flags} is the case-sensitive name of the variable
1983 as seen from C programs while @code{global_flag} is the case-insensitive
1984 name as seen from Fortran. If no binding name is specified, as for
1985 @var{tp}, the C binding name is the (lowercase) Fortran binding name.
1986 If a binding name is specified, only a single variable may be after the
1987 double colon. Note of warning: You cannot use a global variable to
1988 access @var{errno} of the C library as the C standard allows it to be
1989 a macro. Use the @code{IERRNO} intrinsic (GNU extension) instead.
1991 @node Interoperable Subroutines and Functions
1992 @subsection Interoperable Subroutines and Functions
1994 Subroutines and functions have to have the @code{BIND(C)} attribute to
1995 be compatible with C. The dummy argument declaration is relatively
1996 straightforward. However, one needs to be careful because C uses
1997 call-by-value by default while Fortran behaves usually similar to
1998 call-by-reference. Furthermore, strings and pointers are handled
1999 differently. Note that only explicit size and assumed-size arrays are
2000 supported but not assumed-shape or allocatable arrays.
2002 To pass a variable by value, use the @code{VALUE} attribute.
2003 Thus the following C prototype
2006 @code{int func(int i, int *j)}
2009 matches the Fortran declaration
2012 integer(c_int) function func(i,j)
2013 use iso_c_binding, only: c_int
2014 integer(c_int), VALUE :: i
2018 Note that pointer arguments also frequently need the @code{VALUE} attribute.
2020 Strings are handled quite differently in C and Fortran. In C a string
2021 is a @code{NUL}-terminated array of characters while in Fortran each string
2022 has a length associated with it and is thus not terminated (by e.g.
2023 @code{NUL}). For example, if one wants to use the following C function,
2027 void print_C(char *string) /* equivalent: char string[] */
2029 printf("%s\n", string);
2033 to print ``Hello World'' from Fortran, one can call it using
2036 use iso_c_binding, only: C_CHAR, C_NULL_CHAR
2038 subroutine print_c(string) bind(C, name="print_C")
2039 use iso_c_binding, only: c_char
2040 character(kind=c_char) :: string(*)
2041 end subroutine print_c
2043 call print_c(C_CHAR_"Hello World"//C_NULL_CHAR)
2046 As the example shows, one needs to ensure that the
2047 string is @code{NUL} terminated. Additionally, the dummy argument
2048 @var{string} of @code{print_C} is a length-one assumed-size
2049 array; using @code{character(len=*)} is not allowed. The example
2050 above uses @code{c_char_"Hello World"} to ensure the string
2051 literal has the right type; typically the default character
2052 kind and @code{c_char} are the same and thus @code{"Hello World"}
2053 is equivalent. However, the standard does not guarantee this.
2055 The use of pointers is now illustrated using the C library
2056 function @code{strncpy}, whose prototype is
2059 char *strncpy(char *restrict s1, const char *restrict s2, size_t n);
2062 The function @code{strncpy} copies at most @var{n} characters from
2063 string @var{s2} to @var{s1} and returns @var{s1}. In the following
2064 example, we ignore the return value:
2069 character(len=30) :: str,str2
2071 ! Ignore the return value of strncpy -> subroutine
2072 ! "restrict" is always assumed if we do not pass a pointer
2073 subroutine strncpy(dest, src, n) bind(C)
2075 character(kind=c_char), intent(out) :: dest(*)
2076 character(kind=c_char), intent(in) :: src(*)
2077 integer(c_size_t), value, intent(in) :: n
2078 end subroutine strncpy
2080 str = repeat('X',30) ! Initialize whole string with 'X'
2081 call strncpy(str, c_char_"Hello World"//C_NULL_CHAR, &
2082 len(c_char_"Hello World",kind=c_size_t))
2083 print '(a)', str ! prints: "Hello WorldXXXXXXXXXXXXXXXXXXX"
2087 C pointers are represented in Fortran via the special derived type
2088 @code{type(c_ptr)}, with private components. Thus one needs to
2089 use intrinsic conversion procedures to convert from or to C pointers.
2094 type(c_ptr) :: cptr1, cptr2
2095 integer, target :: array(7), scalar
2096 integer, pointer :: pa(:), ps
2097 cptr1 = c_loc(array(1)) ! The programmer needs to ensure that the
2098 ! array is contiguous if required by the C
2100 cptr2 = c_loc(scalar)
2101 call c_f_pointer(cptr2, ps)
2102 call c_f_pointer(cptr2, pa, shape=[7])
2105 When converting C to Fortran arrays, the one-dimensional @code{SHAPE} argument
2106 has to be passed. Note: A pointer argument @code{void *} matches
2107 @code{TYPE(C_PTR), VALUE} while @code{TYPE(C_PTR)} matches @code{void **}.
2109 Procedure pointers are handled analogously to pointers; the C type is
2110 @code{TYPE(C_FUNPTR)} and the intrinsic conversion procedures are
2111 @code{C_F_PROC_POINTER} and @code{C_FUNLOC}.
2113 The intrinsic procedures are described in @ref{Intrinsic Procedures}.
2115 @node Further Interoperability of Fortran with C
2116 @subsection Further Interoperability of Fortran with C
2118 Assumed-shape and allocatable arrays are passed using an array descriptor
2119 (dope vector). The internal structure of the array descriptor used
2120 by GNU Fortran is not yet documented and will change. There will also be
2121 a Technical Report (TR 29113) which standardizes an interoperable
2122 array descriptor. Until then, you can use the Chasm Language
2123 Interoperability Tools, @url{http://chasm-interop.sourceforge.net/},
2124 which provide an interface to GNU Fortran's array descriptor.
2126 The technical report 29113 will presumably also include support for
2127 C-interoperable @code{OPTIONAL} and for assumed-rank and assumed-type
2128 dummy arguments. However, the TR has neither been approved nor implemented
2129 in GNU Fortran; therefore, these features are not yet available.
2133 @node GNU Fortran Compiler Directives
2134 @section GNU Fortran Compiler Directives
2136 The Fortran standard standard describes how a conforming program shall
2137 behave; however, the exact implementation is not standardized. In order
2138 to allow the user to choose specific implementation details, compiler
2139 directives can be used to set attributes of variables and procedures
2140 which are not part of the standard. Whether a given attribute is
2141 supported and its exact effects depend on both the operating system and
2142 on the processor; see
2143 @ref{Top,,C Extensions,gcc,Using the GNU Compiler Collection (GCC)}
2146 For procedures and procedure pointers, the following attributes can
2147 be used to change the calling convention:
2150 @item @code{CDECL} -- standard C calling convention
2151 @item @code{STDCALL} -- convention where the called procedure pops the stack
2152 @item @code{FASTCALL} -- part of the arguments are passed via registers
2153 instead using the stack
2156 Besides changing the calling convention, the attributes also influence
2157 the decoration of the symbol name, e.g., by a leading underscore or by
2158 a trailing at-sign followed by the number of bytes on the stack. When
2159 assigning a procedure to a procedure pointer, both should use the same
2162 On some systems, procedures and global variables (module variables and
2163 @code{COMMON} blocks) need special handling to be accessible when they
2164 are in a shared library. The following attributes are available:
2167 @item @code{DLLEXPORT} -- provide a global pointer to a pointer in the DLL
2168 @item @code{DLLIMPORT} -- reference the function or variable using a global pointer
2171 The attributes are specified using the syntax
2173 @code{!GCC$ ATTRIBUTES} @var{attribute-list} @code{::} @var{variable-list}
2175 where in free-form source code only whitespace is allowed before @code{!GCC$}
2176 and in fixed-form source code @code{!GCC$}, @code{cGCC$} or @code{*GCC$} shall
2177 start in the first column.
2179 For procedures, the compiler directives shall be placed into the body
2180 of the procedure; for variables and procedure pointers, they shall be in
2181 the same declaration part as the variable or procedure pointer.
2185 @node Non-Fortran Main Program
2186 @section Non-Fortran Main Program
2189 * _gfortran_set_args:: Save command-line arguments
2190 * _gfortran_set_options:: Set library option flags
2191 * _gfortran_set_convert:: Set endian conversion
2192 * _gfortran_set_record_marker:: Set length of record markers
2193 * _gfortran_set_max_subrecord_length:: Set subrecord length
2196 Even if you are doing mixed-language programming, it is very
2197 likely that you do not need to know or use the information in this
2198 section. Since it is about the internal structure of GNU Fortran,
2199 it may also change in GCC minor releases.
2201 When you compile a @code{PROGRAM} with GNU Fortran, a function
2202 with the name @code{main} (in the symbol table of the object file)
2203 is generated, which initializes the libgfortran library and then
2204 calls the actual program which uses the name @code{MAIN__}, for
2205 historic reasons. If you link GNU Fortran compiled procedures
2206 to, e.g., a C or C++ program or to a Fortran program compiled by
2207 a different compiler, the libgfortran library is not initialized
2208 and thus a few intrinsic procedures do not work properly, e.g.
2209 those for obtaining the command-line arguments.
2211 Therefore, if your @code{PROGRAM} is not compiled with
2212 GNU Fortran and the GNU Fortran compiled procedures require
2213 intrinsics relying on the library initialization, you need to
2214 initialize the library yourself. Using the default options,
2215 gfortran calls @code{_gfortran_set_args} and
2216 @code{_gfortran_set_options}. The initialization of the former
2217 is needed if the called procedures access the command line
2218 (and for backtracing); the latter sets some flags based on the
2219 standard chosen or to enable backtracing. In typical programs,
2220 it is not necessary to call any initialization function.
2222 If your @code{PROGRAM} is compiled with GNU Fortran, you shall
2223 not call any of the following functions. The libgfortran
2224 initialization functions are shown in C syntax but using C
2225 bindings they are also accessible from Fortran.
2228 @node _gfortran_set_args
2229 @subsection @code{_gfortran_set_args} --- Save command-line arguments
2230 @fnindex _gfortran_set_args
2231 @cindex libgfortran initialization, set_args
2234 @item @emph{Description}:
2235 @code{_gfortran_set_args} saves the command-line arguments; this
2236 initialization is required if any of the command-line intrinsics
2237 is called. Additionally, it shall be called if backtracing is
2238 enabled (see @code{_gfortran_set_options}).
2240 @item @emph{Syntax}:
2241 @code{void _gfortran_set_args (int argc, char *argv[])}
2243 @item @emph{Arguments}:
2244 @multitable @columnfractions .15 .70
2245 @item @var{argc} @tab number of command line argument strings
2246 @item @var{argv} @tab the command-line argument strings; argv[0]
2247 is the pathname of the executable itself.
2250 @item @emph{Example}:
2252 int main (int argc, char *argv[])
2254 /* Initialize libgfortran. */
2255 _gfortran_set_args (argc, argv);
2262 @node _gfortran_set_options
2263 @subsection @code{_gfortran_set_options} --- Set library option flags
2264 @fnindex _gfortran_set_options
2265 @cindex libgfortran initialization, set_options
2268 @item @emph{Description}:
2269 @code{_gfortran_set_options} sets several flags related to the Fortran
2270 standard to be used, whether backtracing or core dumps should be enabled
2271 and whether range checks should be performed. The syntax allows for
2272 upward compatibility since the number of passed flags is specified; for
2273 non-passed flags, the default value is used. See also
2274 @pxref{Code Gen Options}. Please note that not all flags are actually
2277 @item @emph{Syntax}:
2278 @code{void _gfortran_set_options (int num, int options[])}
2280 @item @emph{Arguments}:
2281 @multitable @columnfractions .15 .70
2282 @item @var{num} @tab number of options passed
2283 @item @var{argv} @tab The list of flag values
2286 @item @emph{option flag list}:
2287 @multitable @columnfractions .15 .70
2288 @item @var{option}[0] @tab Allowed standard; can give run-time errors
2289 if e.g. an input-output edit descriptor is invalid in a given standard.
2290 Possible values are (bitwise or-ed) @code{GFC_STD_F77} (1),
2291 @code{GFC_STD_F95_OBS} (2), @code{GFC_STD_F95_DEL} (4), @code{GFC_STD_F95}
2292 (8), @code{GFC_STD_F2003} (16), @code{GFC_STD_GNU} (32),
2293 @code{GFC_STD_LEGACY} (64), and @code{GFC_STD_F2008} (128).
2294 Default: @code{GFC_STD_F95_OBS | GFC_STD_F95_DEL | GFC_STD_F2003
2295 | GFC_STD_F2008 | GFC_STD_F95 | GFC_STD_F77 | GFC_STD_GNU | GFC_STD_LEGACY}.
2296 @item @var{option}[1] @tab Standard-warning flag; prints a warning to
2297 standard error. Default: @code{GFC_STD_F95_DEL | GFC_STD_LEGACY}.
2298 @item @var{option}[2] @tab If non zero, enable pedantic checking.
2300 @item @var{option}[3] @tab If non zero, enable core dumps on run-time
2301 errors. Default: off.
2302 @item @var{option}[4] @tab If non zero, enable backtracing on run-time
2303 errors. Default: off.
2304 Note: Installs a signal handler and requires command-line
2305 initialization using @code{_gfortran_set_args}.
2306 @item @var{option}[5] @tab If non zero, supports signed zeros.
2308 @item @var{option}[6] @tab Enables run-time checking. Possible values
2309 are (bitwise or-ed): GFC_RTCHECK_BOUNDS (1), GFC_RTCHECK_ARRAY_TEMPS (2),
2310 GFC_RTCHECK_RECURSION (4), GFC_RTCHECK_DO (16), GFC_RTCHECK_POINTER (32).
2312 @item @var{option}[7] @tab If non zero, range checking is enabled.
2313 Default: enabled. See -frange-check (@pxref{Code Gen Options}).
2316 @item @emph{Example}:
2318 /* Use gfortran 4.5 default options. */
2319 static int options[] = @{68, 255, 0, 0, 0, 1, 0, 1@};
2320 _gfortran_set_options (8, &options);
2325 @node _gfortran_set_convert
2326 @subsection @code{_gfortran_set_convert} --- Set endian conversion
2327 @fnindex _gfortran_set_convert
2328 @cindex libgfortran initialization, set_convert
2331 @item @emph{Description}:
2332 @code{_gfortran_set_convert} set the representation of data for
2335 @item @emph{Syntax}:
2336 @code{void _gfortran_set_convert (int conv)}
2338 @item @emph{Arguments}:
2339 @multitable @columnfractions .15 .70
2340 @item @var{conv} @tab Endian conversion, possible values:
2341 GFC_CONVERT_NATIVE (0, default), GFC_CONVERT_SWAP (1),
2342 GFC_CONVERT_BIG (2), GFC_CONVERT_LITTLE (3).
2345 @item @emph{Example}:
2347 int main (int argc, char *argv[])
2349 /* Initialize libgfortran. */
2350 _gfortran_set_args (argc, argv);
2351 _gfortran_set_convert (1);
2358 @node _gfortran_set_record_marker
2359 @subsection @code{_gfortran_set_record_marker} --- Set length of record markers
2360 @fnindex _gfortran_set_record_marker
2361 @cindex libgfortran initialization, set_record_marker
2364 @item @emph{Description}:
2365 @code{_gfortran_set_record_marker} set the length of record markers
2366 for unformatted files.
2368 @item @emph{Syntax}:
2369 @code{void _gfortran_set_record_marker (int val)}
2371 @item @emph{Arguments}:
2372 @multitable @columnfractions .15 .70
2373 @item @var{val} @tab Length of the record marker; valid values
2374 are 4 and 8. Default is 4.
2377 @item @emph{Example}:
2379 int main (int argc, char *argv[])
2381 /* Initialize libgfortran. */
2382 _gfortran_set_args (argc, argv);
2383 _gfortran_set_record_marker (8);
2390 @node _gfortran_set_max_subrecord_length
2391 @subsection @code{_gfortran_set_max_subrecord_length} --- Set subrecord length
2392 @fnindex _gfortran_set_max_subrecord_length
2393 @cindex libgfortran initialization, set_max_subrecord_length
2396 @item @emph{Description}:
2397 @code{_gfortran_set_max_subrecord_length} set the maximum length
2398 for a subrecord. This option only makes sense for testing and
2399 debugging of unformatted I/O.
2401 @item @emph{Syntax}:
2402 @code{void _gfortran_set_max_subrecord_length (int val)}
2404 @item @emph{Arguments}:
2405 @multitable @columnfractions .15 .70
2406 @item @var{val} @tab the maximum length for a subrecord;
2407 the maximum permitted value is 2147483639, which is also
2411 @item @emph{Example}:
2413 int main (int argc, char *argv[])
2415 /* Initialize libgfortran. */
2416 _gfortran_set_args (argc, argv);
2417 _gfortran_set_max_subrecord_length (8);
2425 @c Intrinsic Procedures
2426 @c ---------------------------------------------------------------------
2428 @include intrinsic.texi
2435 @c ---------------------------------------------------------------------
2437 @c ---------------------------------------------------------------------
2440 @unnumbered Contributing
2441 @cindex Contributing
2443 Free software is only possible if people contribute to efforts
2445 We're always in need of more people helping out with ideas
2446 and comments, writing documentation and contributing code.
2448 If you want to contribute to GNU Fortran,
2449 have a look at the long lists of projects you can take on.
2450 Some of these projects are small,
2451 some of them are large;
2452 some are completely orthogonal to the rest of what is
2453 happening on GNU Fortran,
2454 but others are ``mainstream'' projects in need of enthusiastic hackers.
2455 All of these projects are important!
2456 We'll eventually get around to the things here,
2457 but they are also things doable by someone who is willing and able.
2462 * Proposed Extensions::
2467 @section Contributors to GNU Fortran
2468 @cindex Contributors
2472 Most of the parser was hand-crafted by @emph{Andy Vaught}, who is
2473 also the initiator of the whole project. Thanks Andy!
2474 Most of the interface with GCC was written by @emph{Paul Brook}.
2476 The following individuals have contributed code and/or
2477 ideas and significant help to the GNU Fortran project
2478 (in alphabetical order):
2481 @item Janne Blomqvist
2482 @item Steven Bosscher
2485 @item Fran@,{c}ois-Xavier Coudert
2489 @item Bernhard Fischer
2491 @item Richard Guenther
2492 @item Richard Henderson
2493 @item Katherine Holcomb
2495 @item Niels Kristian Bech Jensen
2496 @item Steven Johnson
2497 @item Steven G. Kargl
2505 @item Christopher D. Rickett
2506 @item Richard Sandiford
2507 @item Tobias Schl@"uter
2516 The following people have contributed bug reports,
2517 smaller or larger patches,
2518 and much needed feedback and encouragement for the
2519 GNU Fortran project:
2523 @item Dominique d'Humi@`eres
2525 @item Erik Schnetter
2526 @item Joost VandeVondele
2529 Many other individuals have helped debug,
2530 test and improve the GNU Fortran compiler over the past few years,
2531 and we welcome you to do the same!
2532 If you already have done so,
2533 and you would like to see your name listed in the
2534 list above, please contact us.
2542 @item Help build the test suite
2543 Solicit more code for donation to the test suite: the more extensive the
2544 testsuite, the smaller the risk of breaking things in the future! We can
2545 keep code private on request.
2547 @item Bug hunting/squishing
2548 Find bugs and write more test cases! Test cases are especially very
2549 welcome, because it allows us to concentrate on fixing bugs instead of
2550 isolating them. Going through the bugzilla database at
2551 @url{http://gcc.gnu.org/bugzilla/} to reduce testcases posted there and
2552 add more information (for example, for which version does the testcase
2553 work, for which versions does it fail?) is also very helpful.
2558 @node Proposed Extensions
2559 @section Proposed Extensions
2561 Here's a list of proposed extensions for the GNU Fortran compiler, in no particular
2562 order. Most of these are necessary to be fully compatible with
2563 existing Fortran compilers, but they are not part of the official
2564 J3 Fortran 95 standard.
2566 @subsection Compiler extensions:
2569 User-specified alignment rules for structures.
2572 Flag to generate @code{Makefile} info.
2575 Automatically extend single precision constants to double.
2578 Compile code that conserves memory by dynamically allocating common and
2579 module storage either on stack or heap.
2582 Compile flag to generate code for array conformance checking (suggest -CC).
2585 User control of symbol names (underscores, etc).
2588 Compile setting for maximum size of stack frame size before spilling
2589 parts to static or heap.
2592 Flag to force local variables into static space.
2595 Flag to force local variables onto stack.
2599 @subsection Environment Options
2602 Pluggable library modules for random numbers, linear algebra.
2603 LA should use BLAS calling conventions.
2606 Environment variables controlling actions on arithmetic exceptions like
2607 overflow, underflow, precision loss---Generate NaN, abort, default.
2611 Set precision for fp units that support it (i387).
2614 Variable for setting fp rounding mode.
2617 Variable to fill uninitialized variables with a user-defined bit
2621 Environment variable controlling filename that is opened for that unit
2625 Environment variable to clear/trash memory being freed.
2628 Environment variable to control tracing of allocations and frees.
2631 Environment variable to display allocated memory at normal program end.
2634 Environment variable for filename for * IO-unit.
2637 Environment variable for temporary file directory.
2640 Environment variable forcing standard output to be line buffered (unix).
2645 @c ---------------------------------------------------------------------
2646 @c GNU General Public License
2647 @c ---------------------------------------------------------------------
2649 @include gpl_v3.texi
2653 @c ---------------------------------------------------------------------
2654 @c GNU Free Documentation License
2655 @c ---------------------------------------------------------------------
2661 @c ---------------------------------------------------------------------
2662 @c Funding Free Software
2663 @c ---------------------------------------------------------------------
2665 @include funding.texi
2667 @c ---------------------------------------------------------------------
2669 @c ---------------------------------------------------------------------
2672 @unnumbered Option Index
2673 @command{gfortran}'s command line options are indexed here without any
2674 initial @samp{-} or @samp{--}. Where an option has both positive and
2675 negative forms (such as -foption and -fno-option), relevant entries in
2676 the manual are indexed under the most appropriate form; it may sometimes
2677 be useful to look up both forms.
2681 @unnumbered Keyword Index