diff -Nrc3pad gcc-3.2.3/gcc/f/bad.c gcc-3.3/gcc/f/bad.c
*** gcc-3.2.3/gcc/f/bad.c	2002-01-23 03:01:52.000000000 +0000
--- gcc-3.3/gcc/f/bad.c	2002-06-11 23:11:34.000000000 +0000
*************** the Free Software Foundation, 59 Temple 
*** 43,48 ****
--- 43,49 ----
  #include "toplev.h"
  #include "where.h"
  #include "intl.h"
+ #include "diagnostic.h"
  
  /* Externals defined here. */
  
*************** ffebad_start_ (bool lex_override, ffebad
*** 202,208 ****
        if ((ffebad_severity_ != FFEBAD_severityPEDANTIC)
  	  || !flag_pedantic_errors)
  	{
! 	  if (count_error (1) == 0)
  	    {			/* User wants no warnings. */
  	      ffebad_is_temp_inhibited_ = TRUE;
  	      return FALSE;
--- 203,209 ----
        if ((ffebad_severity_ != FFEBAD_severityPEDANTIC)
  	  || !flag_pedantic_errors)
  	{
! 	  if (!diagnostic_count_diagnostic (global_dc, DK_WARNING))
  	    {			/* User wants no warnings. */
  	      ffebad_is_temp_inhibited_ = TRUE;
  	      return FALSE;
*************** ffebad_start_ (bool lex_override, ffebad
*** 214,220 ****
      case FFEBAD_severityWEIRD:
      case FFEBAD_severitySEVERE:
      case FFEBAD_severityDISASTER:
!       count_error (0);
        break;
  
      default:
--- 215,221 ----
      case FFEBAD_severityWEIRD:
      case FFEBAD_severitySEVERE:
      case FFEBAD_severityDISASTER:
!       diagnostic_count_diagnostic (global_dc, DK_ERROR);
        break;
  
      default:
*************** ffebad_finish ()
*** 420,426 ****
  	{
  	  if (bi != 0)
  	    fputc ('\n', stderr);
! 	  report_error_function (fn);
  	  fprintf (stderr,
  		   /* the trailing space on the <file>:<line>: line
  		      fools emacs19 compilation mode into finding the
--- 421,427 ----
  	{
  	  if (bi != 0)
  	    fputc ('\n', stderr);
! 	  diagnostic_report_current_function (global_dc);
  	  fprintf (stderr,
  		   /* the trailing space on the <file>:<line>: line
  		      fools emacs19 compilation mode into finding the
diff -Nrc3pad gcc-3.2.3/gcc/f/bit.c gcc-3.3/gcc/f/bit.c
*** gcc-3.2.3/gcc/f/bit.c	2000-06-21 20:11:14.000000000 +0000
--- gcc-3.3/gcc/f/bit.c	2002-06-17 21:21:01.000000000 +0000
*************** the Free Software Foundation, 59 Temple 
*** 31,37 ****
  /* Include files. */
  
  #include "proj.h"
- #include "glimits.h"
  #include "bit.h"
  #include "malloc.h"
  
--- 31,36 ----
diff -Nrc3pad gcc-3.2.3/gcc/f/bld.c gcc-3.3/gcc/f/bld.c
*** gcc-3.2.3/gcc/f/bld.c	2001-12-23 04:59:08.000000000 +0000
--- gcc-3.3/gcc/f/bld.c	2002-05-28 17:32:58.000000000 +0000
*************** the Free Software Foundation, 59 Temple 
*** 43,48 ****
--- 43,49 ----
  #include "malloc.h"
  #include "target.h"
  #include "where.h"
+ #include "real.h"
  
  /* Externals defined here.  */
  
diff -Nrc3pad gcc-3.2.3/gcc/f/BUGS gcc-3.3/gcc/f/BUGS
*** gcc-3.2.3/gcc/f/BUGS	2003-04-22 09:53:56.000000000 +0000
--- gcc-3.3/gcc/f/BUGS	2003-05-14 02:47:28.000000000 +0000
*************** _Note:_ This file is automatically gener
*** 2,20 ****
  `bugs0.texi' and `bugs.texi'.  `BUGS' is _not_ a source file, although
  it is normally included within source distributions.
  
!    This file lists known bugs in the GCC-3.2.3 version of the GNU
! Fortran compiler.  Copyright (C)
! 1995,1996,1997,1998,1999,2000,2001,2002 Free Software Foundation, Inc.
! You may copy, distribute, and modify it freely as long as you preserve
! this copyright notice and permission notice.
  
  Known Bugs In GNU Fortran
  *************************
  
     This section identifies bugs that `g77' _users_ might run into in
! the GCC-3.2.3 version of `g77'.  This includes bugs that are actually
! in the `gcc' back end (GBE) or in `libf2c', because those sets of code
! are at least somewhat under the control of (and necessarily intertwined
  with) `g77', so it isn't worth separating them out.
  
     For information on bugs in _other_ versions of `g77', see
--- 2,20 ----
  `bugs0.texi' and `bugs.texi'.  `BUGS' is _not_ a source file, although
  it is normally included within source distributions.
  
!    This file lists known bugs in the GCC-3.3 version of the GNU Fortran
! compiler.  Copyright (C) 1995,1996,1997,1998,1999,2000,2001,2002 Free
! Software Foundation, Inc.  You may copy, distribute, and modify it
! freely as long as you preserve this copyright notice and permission
! notice.
  
  Known Bugs In GNU Fortran
  *************************
  
     This section identifies bugs that `g77' _users_ might run into in
! the GCC-3.3 version of `g77'.  This includes bugs that are actually in
! the `gcc' back end (GBE) or in `libf2c', because those sets of code are
! at least somewhat under the control of (and necessarily intertwined
  with) `g77', so it isn't worth separating them out.
  
     For information on bugs in _other_ versions of `g77', see
*************** with) `g77', so it isn't worth separatin
*** 23,30 ****
  
     An online, "live" version of this document (derived directly from
  the mainline, development version of `g77' within `gcc') is available
! via `http://www.gnu.org/software/gcc/onlinedocs/g77/Trouble.html'.
! Follow the "Known Bugs" link.
  
     The following information was last updated on 2002-02-01:
  
--- 23,30 ----
  
     An online, "live" version of this document (derived directly from
  the mainline, development version of `g77' within `gcc') is available
! via `http://gcc.gnu.org/onlinedocs/g77/Trouble.html'.  Follow the
! "Known Bugs" link.
  
     The following information was last updated on 2002-02-01:
  
diff -Nrc3pad gcc-3.2.3/gcc/f/bugs.texi gcc-3.3/gcc/f/bugs.texi
*** gcc-3.2.3/gcc/f/bugs.texi	2002-08-28 15:41:10.000000000 +0000
--- gcc-3.3/gcc/f/bugs.texi	2002-12-23 19:38:40.000000000 +0000
***************
*** 1,4 ****
! @c Copyright (C) 1995, 1996, 1997, 1998, 1999, 2000, 2001 Free Software Foundation, Inc.
  @c This is part of the G77 manual.
  @c For copying conditions, see the file g77.texi.
  
--- 1,4 ----
! @c Copyright (C) 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002 Free Software Foundation, Inc.
  @c This is part of the G77 manual.
  @c For copying conditions, see the file g77.texi.
  
***************
*** 11,19 ****
  
  @set last-update-bugs 2002-02-01
  
- @include root.texi
- 
  @ifset DOC-BUGS
  @c The immediately following lines apply to the BUGS file
  @c which is derived from this file.
  @emph{Note:} This file is automatically generated from the files
--- 11,18 ----
  
  @set last-update-bugs 2002-02-01
  
  @ifset DOC-BUGS
+ @include root.texi
  @c The immediately following lines apply to the BUGS file
  @c which is derived from this file.
  @emph{Note:} This file is automatically generated from the files
*************** An online, ``live'' version of this docu
*** 79,85 ****
  (derived directly from the mainline, development version
  of @code{g77} within @code{gcc})
  is available via
! @uref{http://www.gnu.org/software/gcc/onlinedocs/g77/Trouble.html}.
  Follow the ``Known Bugs'' link.
  
  The following information was last updated on @value{last-update-bugs}:
--- 78,84 ----
  (derived directly from the mainline, development version
  of @code{g77} within @code{gcc})
  is available via
! @uref{http://gcc.gnu.org/onlinedocs/g77/Trouble.html}.
  Follow the ``Known Bugs'' link.
  
  The following information was last updated on @value{last-update-bugs}:
diff -Nrc3pad gcc-3.2.3/gcc/f/ChangeLog gcc-3.3/gcc/f/ChangeLog
*** gcc-3.2.3/gcc/f/ChangeLog	2003-04-22 06:14:59.000000000 +0000
--- gcc-3.3/gcc/f/ChangeLog	2003-05-14 00:10:00.000000000 +0000
***************
*** 1,57 ****
! 2003-04-22  Release Manager
  
! 	* GCC 3.2.3 Released.
  
! 2003-02-05  Gabriel Dos Reis  <gdr@integrable-solutions.net>
  
! 	* root.texi: Bump version.
! 	* version.c (ffe_version_string): Update.
  
! 2003-02-05  Release Manager
  
! 	* GCC 3.2.2 Released.
  
! 2003-01-28  Christian Cornelssen  <ccorn@cs.tu-berlin.de>
  
  	* Make-lang.in (f77.install-common, f77.install-info)
  	(f77.install-man, f77.uninstall): Prepend $(DESTDIR) to
  	destination paths in all (un)installation commands.
  
! 2002-11-22  Toon Moene  <toon@moene.indiv.nluug.nl>
  
  	* invoke.texi: Explain the purpose of -fmove-all-movables,
  	-freduce-all-givs and -frerun-loop-opts better.
  
! 2002-11-19  Release Manager
  
! 	* GCC 3.2.1 Released.
  
! 2002-11-19  Release Manager
  
! 	* GCC 3.2.1 Released.
  
! 2002-11-18  Release Manager
  
! 	* GCC 3.2.1 Released.
  
! 2002-10-28  Andris Pavenis  <pavenis@latnet.lv>
!             Toon Moene  <toon@moene.indiv.nluug.nl>
  
! 	PR fortran/8308
! 	* lang-specs.h: Correct ratfor specs.
! 	* news.texi: Document this fix.
  
! 2002-09-14  Hans-Peter Nilsson  <hp@bitrange.com>
  
! 	* target.c (ffetarget_memcpy_): Don't test nonexistent
! 	HOST_BYTES_BIG_ENDIAN, HOST_BITS_BIG_ENDIAN.  Check
! 	HOST_WORDS_BIG_ENDIAN against both WORDS_BIG_ENDIAN and
! 	BYTES_BIG_ENDIAN.
  
  2002-09-07  Jan Hubicka  <jh@suse.cz>
  
  	* com.c (ffe_type_for_mode): Handle long double.
  
  2002-08-30  Alan Modra  <amodra@bigpond.net.au>
  
  	* target.h (FFETARGET_32bit_longs): Don't define for powerpc64 or
--- 1,239 ----
! 2003-05-13  Release Manager
  
! 	* GCC 3.3 Released.
  
! 2003-05-13  Release Manager
  
! 	* GCC 3.3 Released.
  
! 2003-05-13  Release Manager
  
! 	* GCC 3.3 Released.
  
! 2003-04-11  Bud Davis <bdavis9659@comcast.net>
! 
! 	PR Fortran/9263
! 	* gcc/f/data.c (ffedata_advance_): Check initial, final and
! 	increment values for INTEGER typeness.
! 	* gcc/f/news.texi: Document these fixes.
! 
! 2003-03-26  Roger Sayle  <roger@eyesopen.com>
! 
! 	PR fortran/9793
! 	* target.h (ffetarget_divide_integer1): Perform division by -1
! 	using negation to prevent possible overflow trap on the host.
! 
! 2003-03-25  Marcelo Abreu  <mmabreu@inf.ufrgs.br>
! 
! 	PR fortran/10204
! 	* ffe.texi: Reference the GCC web site in the URL.
! 
! 2003-03-24  Toon Moene  <toon@moene.indiv.nluug.nl>
! 
! 	PR fortran/10197
! 	* news.texi: Document PR fortran/10197 fixed.
! 
! Sun Mar 23 23:43:45 2003  Mark Mitchell  <mark@codesourcery.com>
! 
! 	PR c++/7086
! 	* com.c (ffecom_sym_transform_): Adjust calls to
! 	put_var_into_stack.
! 	(ffe_mark_addressable): Likewise.
! 
! 2003-03-22  Bud Davis  <bdavis9659@comcast.net>
! 
! 	* com.c (ffecom_constantunion_with_type): New function.
! 	* com.h (ffecom_constantunion_with_type): Declare.
! 	* stc.c (ffestc_R810): Check for kind type.
! 	* ste.c (ffeste_R810): Use ffecom_constantunion_with_type
! 	to discern SELECT CASE variables.
! 
! 2003-03-15  Andreas Jaeger  <aj@suse.de>
! 
! 	* g77spec.c (DEFAULT_SWITCH_TAKES_ARG): Remove.
! 	(DEFAULT_WORD_SWITCH_TAKES_ARG): Remove.
! 
! 2003-02-21  Toon Moene  <toon@moene.indiv.nluug.nl>
! 
! 	* news.texi: Document fixing PR fortran/9038.
! 
! 2003-02-04  Joseph S. Myers  <jsm@polyomino.org.uk>
! 
! 	* g77.texi, invoke.texi: Update to GFDL 1.2.
! 
! 2003-01-30  Toon Moene  <toon@moene.indiv.nluug.nl>
! 
! 	* news.texi: Document fixing PR fortran/7681
! 	and PR optimization/9258.
! 
! 2003-01-26  Toon Moene  <toon@moene.indiv.nluug.nl>
! 
! 	* lang-specs.h: Revert change to solve 9038.
! 	* news.texi: Document this.
! 
! 2003-01-26  Christian Cornelssen  <ccorn@cs.tu-berlin.de>
  
  	* Make-lang.in (f77.install-common, f77.install-info)
  	(f77.install-man, f77.uninstall): Prepend $(DESTDIR) to
  	destination paths in all (un)installation commands.
  
! 2003-01-05  Steven Bosscher  <s.bosscher@student.tudelft.nl>
! 
! 	PR Fortran/9038
! 	* lang-specs.h: Prevent -f<option> from being passed
! 	to cc1.
! 	* news.texi: Document this fix.
! 
! 2003-01-03  Bud Davis <bdavis11@directvinternet.com>
! 
! 	* stc.c (ffestc_R810): Allow any kind integer in
! 	case statements.
! 	* ste.c (ffeste_R810): Give error message when
! 	case selector exceeds its valid values.
! 
! 2003-01-01  Andreas Jaeger  <aj@suse.de>
! 
! 	* f/Make-lang.in ($(srcdir)/f/BUGS): Add include path for
! 	gcc-common.texi.
! 	($(srcdir)/f/NEWS): Likewise.
! 
! 2002-12-28  Joseph S. Myers  <jsm@polyomino.org.uk>
! 
! 	* g77.texi: Use @copying.
! 
! 2002-12-23  Joseph S. Myers  <jsm@polyomino.org.uk>
! 
! 	* root.texi: Include gcc-common.texi.
! 	* bugs.texi, news.texi: Don't include root.texi as part of full
! 	manual.
! 	* g77.texi: Update for use of gcc-common.texi.
! 	* Make-lang.in ($(srcdir)/f/g77.info, f/g77.dvi): Depend on
! 	$(srcdir)/doc/include/gcc-common.texi.
! 
! 2002-12-19  Kazu Hirata  <kazu@cs.umass.edu>
! 
! 	* intdoc.in: Fix typos.
! 
! 2002-12-18  Kazu Hirata  <kazu@cs.umass.edu>
! 
! 	* g77.texi: Fix typos.
! 	* intdoc.texi: Likewise.
! 	* news.texi: Follow spelling conventions.
! 
! Mon Dec 16 13:55:24 2002  Mark Mitchell  <mark@codesourcery.com>
! 
! 	* root.texi (DEVELOPMENT): @clear it.
! 
! 2002-11-20  Toon Moene  <toon@moene.indiv.nluug.nl>
  
  	* invoke.texi: Explain the purpose of -fmove-all-movables,
  	-freduce-all-givs and -frerun-loop-opts better.
  
! 2002-11-19  Toon Moene  <toon@moene.indiv.nluug.nl>
  
! 	PR fortran/8587
! 	* news.texi: Show PR fortran/8587 fixed.
  
! 2002-11-19  Jason Thorpe  <thorpej@wasabisystems.com>
  
! 	* g77spec.c (lang_specific_spec_functions): New.
  
! 2002-11-02  Toon Moene  <toon@moene.indiv.nluug.nl>
  
! 	* g77.texi: Correct documentation on generating C++ prototypes
! 	of Fortran routines with f2c.
! 	* news.texi: Document fixes in GCC-3.3, 3.2 and 3.1.
  
! 2002-10-30  Roger Sayle  <roger@eyesopen.com>
  
! 	* com.c (ffecom_subscript_check_): Cast the failure branch
! 	of the bounds check COND_EXPR to void, to indicate noreturn.
! 	(ffe_truthvalue_conversion): Only apply truth value conversion
! 	to the non-void branches of a COND_EXPR.
  
! 2002-10-26  Andris Pavenis  <pavenis@latnet.lv>
  
! 	* lang-specs.h: Fix ratfor specs.
! 
! 2002-10-15  Richard Henderson  <rth@redhat.com>
! 
! 	* target.h (ffetarget_print_real1, ffetarget_print_real2): Use
! 	real_to_decimal directly, and with the new arguments.
! 
! 2002-09-23  Zack Weinberg  <zack@codesourcery.com>
! 
! 	* Make-lang.in (g77spec.o): Don't depend on f/version.h.
! 	(f/parse.o): Depend on version.h not f/version.h.
! 	(g77version.o, f/version.o): Delete all references.
! 
! 	* com.c (ffecom_init_0): Fix transposed array indices in bsearch test.
! 	* g77spec.c: Don't include f/version.h or refer to ffe_version_string.
! 	* parse.c: Use version_string, not ffe_version_string.
! 	* version.c, version.h: Delete files.
! 
! 2002-09-23  Kazu Hirata  <kazu@cs.umass.edu>
! 
! 	* ChangeLog: Follow spelling conventions.
! 	* ChangeLog.0: Likewise.
! 	* com.c: Likewise.
! 	* ffe.texi: Likewise.
! 	* g77.texi: Likewise.
! 	* intdoc.in: Likewise.
! 	* invoke.texi: Likewise.
! 	* news.texi: Likewise.
! 	* intdoc.texi: Regenerate.
! 
! 2002-09-16  Geoffrey Keating  <geoffk@apple.com>
! 
! 	* com.c (union lang_tree_node): Add chain_next option.
! 
! 2002-09-16  Richard Henderson  <rth@redhat.com>
! 
! 	* target.c (ffetarget_real1): Don't pass FFETARGET_ATOF_
! 	directly to ffetarget_make_real1.
! 	(ffetarget_real2): Similarly.
! 	* target.h (ffetarget_cvt_r1_to_rv_, ffetarget_cvt_rv_to_r2_,
! 	ffetarget_cvt_r2_to_rv_): Use new real.h interface and simplify.
! 
! 2002-09-15  Kazu Hirata  <kazu@cs.umass.edu>
! 
! 	* intdoc.texi: Regenerate.
! 
! 2002-09-15  Kazu Hirata  <kazu@cs.umass.edu>
! 
! 	* ChangeLog: Follow spelling conventions.
! 	* intdoc.in: Likewise.
! 
! 2002-09-09  Gerald Pfeifer  <pfeifer@dbai.tuwien.ac.at>
! 
! 	Fix PR web/7596:
! 	* ffe.texi (Front End): Fix broken links.
! 	* bugs.texi (Known Bugs): Refer to gcc.gnu.org instead of
! 	www.gnu.org for onlinedocs.
! 	* news.texi (News): Ditto.
  
  2002-09-07  Jan Hubicka  <jh@suse.cz>
  
  	* com.c (ffe_type_for_mode): Handle long double.
  
+ 2002-09-04  Richard Henderson  <rth@redhat.com>
+ 
+ 	* target.h (ffetarget_print_real1, ffetarget_print_real2): Update
+ 	call to REAL_VALUE_TO_DECIMAL.
+ 
+ 2002-08-31  Toon Moene  <toon@moene.indiv.nluug.nl>
+ 
+ 	* com.c: Don't set flag_finite_math_only by default.
+ 	* invoke.texi: Reverse the documentation of option
+ 	-ffinite-math-only to reflect the new default.
+ 
+ 2002-08-30  Hans-Peter Nilsson  <hp@bitrange.com>
+ 
+ 	* target.c (ffetarget_memcpy_): Don't test nonexistent
+ 	HOST_BYTES_BIG_ENDIAN, HOST_BITS_BIG_ENDIAN.  Check
+ 	HOST_WORDS_BIG_ENDIAN against both WORDS_BIG_ENDIAN and
+ 	BYTES_BIG_ENDIAN.
+ 
  2002-08-30  Alan Modra  <amodra@bigpond.net.au>
  
  	* target.h (FFETARGET_32bit_longs): Don't define for powerpc64 or
***************
*** 62,106 ****
  	* bugs.texi, news.texi: Update URLs for online news and bugs
  	lists.
  
! 2002-08-14  Release Manager
  
! 	* GCC 3.2 Released.
  
! 2002-08-04  Toon Moene  <toon@moene.indiv.nluug.nl>
  
! 	* news.texi: Mention nothing changed for 3.2.
  
! Sun Aug  4 16:48:53 2002  Joseph S. Myers  <jsm@polyomino.org.uk>
  
! 	* root.texi (version-gcc): Increase to 3.2.
  
! 2002-07-25  Release Manager
  
! 	* GCC 3.1.1 Released.
  
! 2002-06-30  Toon Moene  <toon@moene.indiv.nluug.nl>
  
  	* news.texi: Mention 2 Gbyte limit on 32-bit targets
  	for arrays explicitly in news on g77-3.1.
  
! 2002-05-14  Release Manager
  
! 	* GCC 3.1 Released.
  
! 2002-05-14  Release Manager
  
! 	* GCC 3.1 Released.
  
  2002-04-29  Joseph S. Myers  <jsm28@cam.ac.uk>
  
  	* invoke.texi: Use @gol at ends of lines inside @gccoptlist.
  	* g77.texi: Update last update date.
  
  2002-04-20  Toon Moene  <toon@moene.indiv.nluug.nl>
  
  	* root.texi: Remove variable version-g77.
  	* g77.texi: Remove the single use of that variable.
  
  Tue Apr 16 14:55:47 2002  Mark Mitchell  <mark@codesourcery.com>
  
  	* com.c (ffecom_expr_power_integer): Add has_scope argument to
--- 244,429 ----
  	* bugs.texi, news.texi: Update URLs for online news and bugs
  	lists.
  
! 2002-08-22  Hans-Peter Nilsson  <hp@bitrange.com>
  
! 	* where.h (struct _ffewhere_file_): Mark GTY.
! 	(ffewhere_file_kill): Remove prototype.
! 	* where.c: Include ggc.h.
! 	(struct _ffewhere_ll_, struct _ffewhere_root_ll_): Mark GTY.
! 	(ffewhere_root_ll_): Ditto.  Change type from struct
! 	_ffewhere_root_ll_ to struct _ffewhere_root_ll_*.  All uses
! 	changed.
! 	(ffewhere_file_kill): Remove.
! 	(ffewhere_file_new): Use GC to allocate ffewhereFile objects.
! 	(ffewhere_file_set): Use GC to allocate ffewhereLL_ objects.
! 	(ffewhere_init_1): Use GC to allocate ffewhere_root_ll_ sentinel.
! 	Include gt-f-where.h.
! 	* lex.c (ffelex_current_wf_, ffelex_include_wherefile_): Mark GTY.
! 	Include gt-f-lex.h.
! 	* std.c (ffestd_S3P4): Don't call ffewhere_file_kill.
! 	* config-lang.in (gtfiles): Add f/where.h f/where.c and f/lex.c.
! 	* Make-lang.in (gt-f-lex.h gt-f-where.h): Add to dependents of
! 	s-gtype.
! 	(f/lex.o): Depend on gt-f-lex.h.
! 	(f/where.o): Depend on gt-f-where.h.
  
! Tue Aug 20 16:49:40 2002  Kaveh R. Ghazi  <ghazi@caip.rutgers.edu>
  
! 	* where.c (ffewhere_track): Remove impossible if-then clause.
  
! Thu Aug  8 10:06:14 2002  Nathan Sidwell  <nathan@codesourcery.com>
  
! 	* f/Make-lang.in (f.mostlyclean): Remove coverage files.
  
! 2002-08-06  Gerald Pfeifer  <pfeifer@dbai.tuwien.ac.at>
  
! 	* g77.texi (Top): Rename Index to Keyword Index.
  
! 2002-08-05  Toon Moene  <toon@moene.indiv.nluug.nl>
! 
! 	* invoke.texi: Improve description of
! 	-fno-finite-math-only flag.
! 
! Sun Aug  4 16:45:49 2002  Joseph S. Myers  <jsm@polyomino.org.uk>
! 
! 	* root.texi (version-gcc): Increase to 3.3.
! 
! 2002-07-30  Toon Moene  <toon@moene.indiv.nluug.nl>
! 
! 	* com.c (ffe_init_options): Set
! 	flag_finite_math_only.
! 	* invoke.texi: Document -fno-finite-math-only.
! 
! Mon Jul 29 22:05:35 2002  Kaveh R. Ghazi  <ghazi@caip.rutgers.edu>
! 
! 	* com.c (read_name_map): Use concat in lieu of xmalloc/strcpy.
! 
! 2002-07-25  Toon Moene  <toon@moene.indiv.nluug.nl>
! 
! 	* news.texi: Document better handling of (no-)alias
! 	information of dummy arguments and induction variables
! 	on loop unrolling.
! 
! 2002-07-01  Roger Sayle  <roger@eyesopen.com>
! 
! 	* f/com.c (builtin_function): Accept additional parameter.
! 	(ffe_com_init_0): Pass an additional NULL_TREE argument to
! 	builtin_function.
! 
! 2002-06-28  Toon Moene  <toon@moene.indiv.nluug.nl>
  
  	* news.texi: Mention 2 Gbyte limit on 32-bit targets
  	for arrays explicitly in news on g77-3.1.
  
! Thu Jun 20 21:56:34 2002  Neil Booth  <neil@daikokuya.co.uk>
  
! 	* lang-specs.h: Use cc1 for traditional preprocessing.
  
! 2002-06-20  Andreas Jaeger  <aj@suse.de>
  
! 	* com.c (ffecom_prepare_expr_,ffecom_expr_power_integer_):
! 	Remove #ifdefed HAHA sections.
! 
! 2002-06-20  Nathanael Nerode  <neroden@twcny.rr.com>
! 
! 	* com.c: Remove #ifdef HOHO sections.
! 
! 2002-06-17  Jason Thorpe  <thorpej@wasabisystems.com>
! 
! 	* bit.c: Don't include glimits.h.
! 	* target.c: Likewise.
! 	* where.h: Likewise.
! 
! 2002-06-12  Gabriel Dos Reis  <gdr@codesourcery.com>
! 
! 	* bad.c (ffebad_start_): Adjust calls to diagnostic_count_error.
! 
! 2002-06-04  Gabriel Dos Reis  <gdr@codesourcery.com>
! 
! 	* bad.c (ffebad_start_): Adjust call to count_error.
! 	* Make-lang.in (f/bad.o): Depend on diagnostic.h
! 	* bad.c: #include diagnostic.h
! 
! 2002-06-03  Geoffrey Keating  <geoffk@redhat.com>
! 
! 	* Make-lang.in (f/com.o): Depend on debug.h.
! 	* com.c: Include debug.h.
! 	(LANG_HOOKS_MARK_TREE): Delete.
! 	(struct lang_identifier): Use gengtype.
! 	(union lang_tree_node): New.
! 	(struct lang_decl): New dummy definition.
! 	(struct lang_type): New dummy definition.
! 	(ffe_mark_tree): Delete.
! 
! 	* com.c (struct language_function): New dummy structure.
! 
! 	* Make-lang.in: Add rules to generate gt-f-ste.h gtype-f.h; allow
! 	for filename changes.
! 	(com.o): Allow for filename changes; add gtype-f.h as dependency.
! 	(ste.o): Add gt-f-ste.h as dependency.
! 	* config-lang.in (gtfiles): Add com.h, ste.c.
! 	* com.c: Replace uses of ggc_add_* with GTY markers.  Include
! 	gtype-f.h.
! 	(mark_binding_level): Delete.
! 	* com.h: Replace uses of ggc_add_* with GTY markers.
! 	* ste.c: Replace uses of ggc_add_* with GTY markers.  Include
! 	gt-f-ste.h.
! 
! 	* Make-lang.in (f/gt-com.h): Build using gengtype.
! 	(com.o): Depend on f/gt-com.h.
! 	* com.c: Rename struct binding_level to f_binding_level.
! 	(struct f_binding_level): Use gengtype.
! 	(struct tree_ggc_tracker): Use gengtype.
! 	(mark_tracker_head): Use gt_ggc_m_tree_ggc_tracker.
! 	(make_binding_level): Use GGC.
! 	(mark_binding_level): Use gt_ggc_m_f_binding_level.
! 	(ffecom_init_decl_processing): Change free_binding_level
! 	to a deletable root.
! 	* config-lang.in (gtfiles): Define.
! 	* where.c: Strings need no longer be allocated in GCable memory;
! 	remove my change of 30 Dec 1999.
! 
! 2002-05-31  Matthew Woodcraft  <mattheww@chiark.greenend.org.uk>
! 
! 	* lang-specs.h: Use cpp_debug_options.
! 
! 2002-05-28  Zack Weinberg  <zack@codesourcery.com>
! 
! 	* bld.c, com.c, expr.c, target.c: Include real.h.
! 	* Make-lang.in: Update dependency lists.
! 
! 2002-05-16  Rainer Orth  <ro@TechFak.Uni-Bielefeld.DE>
! 
! 	* Make-lang.in: Allow for PWDCMD to override hardcoded pwd.
! 
! 2002-05-09  Hassan Aurag  <aurag@cae.com>
! 
! 	* expr.c (ffeexpr_reduced_ugly2log_): Allow logicals-as-integers
! 	under -fugly-logint as arguments of .and., .or., .xor.
! 
! 2002-05-07  Jan Hubicka  <jh@suse.cz>
! 
! 	* target.h (FFETARGET_32bit_longs): Undefine for x86-64.
  
  2002-04-29  Joseph S. Myers  <jsm28@cam.ac.uk>
  
  	* invoke.texi: Use @gol at ends of lines inside @gccoptlist.
  	* g77.texi: Update last update date.
  
+ Thu Apr 25 07:44:44 2002  Neil Booth  <neil@daikokuya.demon.co.uk>
+ 
+ 	* com.h (ffe_parse_file): Update.
+ 	* lex.c (ffe_parse_file): Update.
+ 
  2002-04-20  Toon Moene  <toon@moene.indiv.nluug.nl>
  
  	* root.texi: Remove variable version-g77.
  	* g77.texi: Remove the single use of that variable.
  
+ Thu Apr 18 19:10:44 2002  Neil Booth  <neil@daikokuya.demon.co.uk>
+ 
+ 	* com.c (incomplete_type_error): Remove.
+ 
  Tue Apr 16 14:55:47 2002  Mark Mitchell  <mark@codesourcery.com>
  
  	* com.c (ffecom_expr_power_integer): Add has_scope argument to
*************** Mon Apr 15 10:59:14 2002  Mark Mitchell 
*** 110,130 ****
  
  	* g77.texi: Remove Chill reference.
  
! 2002-04-14  Hans-Peter Nilsson  <hp@bitrange.com>
  
  	* Make-lang.in (f/target.o): Depend on diagnostic.h.
  	* target.c: Include diagnostic.h.
  	(ffetarget_memcpy_): Call sorry if host and target endians are
  	not matching.
  
! 2002-04-13  Toon Moene  <toon@moene.indiv.nluug.nl>
  
! 	* news.texi: Deprecate frontend version number;
! 	update list of fixed bugs.
  
! 2002-04-01  Phil Edwards  <pme@gcc.gnu.org>
  
! 	* version.c:  Fix misplaced leading blanks on first line.
  
  2002-03-23  Toon Moene  <toon@moene.indiv.nluug.nl>
  
--- 433,495 ----
  
  	* g77.texi: Remove Chill reference.
  
! 2002-04-13  Toon Moene  <toon@moene.indiv.nluug.nl>
! 
! 	* news.texi: Deprecate frontend version number;
! 	update list of fixed bugs.
! 
! 2002-04-08  Hans-Peter Nilsson  <hp@bitrange.com>
  
  	* Make-lang.in (f/target.o): Depend on diagnostic.h.
  	* target.c: Include diagnostic.h.
  	(ffetarget_memcpy_): Call sorry if host and target endians are
  	not matching.
  
! Thu Apr  4 23:29:48 2002  Neil Booth  <neil@daikokuya.demon.co.uk>
  
! 	* com.c (LANG_HOOKS_TRUTHVALUE_CONVERSION): Redefine.
! 	(truthvalue_conversion): Rename.  Update.  Make static.
! 	(ffecom_truth_value): Update.
  
! Mon Apr  1 21:39:36 2002  Neil Booth  <neil@daikokuya.demon.co.uk>
  
! 	* com.c (LANG_HOOKS_MARK_ADDRESSABLE): Redefine.
! 	(mark_addressable): Rename.
! 	(ffecom_arrayref_, ffecom_1): Update.
! 
! Mon Apr  1 09:59:53 2002  Neil Booth  <neil@daikokuya.demon.co.uk>
! 
! 	* com.c (LANG_HOOKS_SIGNED_TYPE, LANG_HOOKS_UNSIGNED_TYPE,
! 	LANG_HOOKS_SIGNED_OR_UNSIGNED_TYPE): New.
! 	(unsigned_type, signed_type, signed_or_unsigned_type): Rename.
! 
! Sun Mar 31 23:50:22 2002  Neil Booth  <neil@daikokuya.demon.co.uk>
! 
! 	* com.c (lang_print_error_function): Rename.
! 	(LANG_HOOKS_PRINT_ERROR_FUNCTION): Redefine.
! 	(ffe_init): Don't set hook.
! 
! Fri Mar 29 21:59:15 2002  Neil Booth  <neil@daikokuya.demon.co.uk>
! 
! 	* com.c (LANG_HOOKS_TYPE_FOR_MODE, LANG_HOOKS_TYPE_FOR_SIZE):
! 	Redefine.
! 	(type_for_mode, type_for_size): Rename.
! 	(signed_or_unsigned_type, signed_type, truthvalue_conversion,
! 	unsigned_type):	Use new hooks.
! 
! Tue Mar 26 10:30:05 2002  Andrew Cagney  <ac131313@redhat.com>
! 
! 	* invoke.texi (Warning Options): Mention -Wswitch-enum.
! 	Fix PR c/5044.
! 
! Tue Mar 26 07:30:51 2002  Neil Booth  <neil@daikokuya.demon.co.uk>
! 
! 	* com.c (LANG_HOOKS_MARK_TREE): Redefine.
! 	(lang_mark_tree): Rename ffe_mark_tree, make static.
! 
! Mon Mar 25 19:27:11 2002  Neil Booth  <neil@daikokuya.demon.co.uk>
! 
! 	* com.c (maybe_build_cleanup): Remove.
  
  2002-03-23  Toon Moene  <toon@moene.indiv.nluug.nl>
  
*************** Mon Apr 15 10:59:14 2002  Mark Mitchell 
*** 133,141 ****
  	addressing get caught.
  	* news.texi: Document the fixing of this problem.
  
! Mon Mar 18 18:43:22 CET 2002  Jan Hubicka  <jh@suse.cz>
  
! 	* target.h (FFETARGET_32bit_longs): Undefine for x86-64.
  
  2002-02-13  Toon Moene  <toon@moene.indiv.nluug.nl>
  
--- 498,557 ----
  	addressing get caught.
  	* news.texi: Document the fixing of this problem.
  
! Sat Mar 23 11:18:17 2002  Andrew Cagney  <ac131313@redhat.com>
  
! 	* invoke.texi (Warning Options): Mention -Wswitch-default.
! 
! Thu Mar 21 18:55:41 2002  Neil Booth  <neil@daikokuya.demon.co.uk>
! 
! 	* cp-tree.h (pushdecl, pushlevel, poplevel, set_block,
! 	insert_block, getdecls, global_bindings_p): New.
! 
! Wed Mar 20 08:03:42 2002  Neil Booth  <neil@daikokuya.demon.co.uk>
! 
! 	* com.c (lang_printable_name): Rename.
! 	(LANG_HOOKS_DECL_PRINTABLE_NAME): Redefine.
! 	(ffe_init): Don't use old hook.
! 
! Sun Mar 17 18:50:15 2002  Kaveh R. Ghazi  <ghazi@caip.rutgers.edu>
! 
! 	* com.h (ffe_parse_file): Prototype.
! 
! Sun Mar 17 20:57:30 2002  Neil Booth  <neil@daikokuya.demon.co.uk>
! 
! 	* com.c (LANG_HOOKS_PARSE_FILE): Redefine.
! 	* com.h (ffe_parse_file): New.
! 	* parse.c (NAME_OF_STDIN): Remove.
! 	(yyparse): Rename ffe_parse_file.
! 
! Tue Mar 12 20:23:18 2002  Kaveh R. Ghazi  <ghazi@caip.rutgers.edu>
! 
! 	* com.c (tree_code_type, tree_code_length, tree_code_name):
! 	Define.
! 
! Sun Mar 10 12:37:42 2002  Kaveh R. Ghazi  <ghazi@caip.rutgers.edu>
! 
! 	* target.c (ffetarget_print_hex): Const-ify.
! 
! 2002-03-06  Phil Edwards  <pme@gcc.gnu.org>
! 
! 	* version.c:  Fix misplaced leading blanks on first line.
! 
! 2002-03-03  Zack Weinberg  <zack@codesourcery.com>
! 
! 	* com.c, target.h: Remove all #ifndef REAL_ARITHMETIC
! 	blocks, make all #ifdef REAL_ARITHMETIC blocks unconditional.
! 	Delete some further #ifdef blocks predicated on REAL_ARITHMETIC.
! 
! Thu Feb 28 07:53:46 2002  Neil Booth  <neil@daikokuya.demon.co.uk>
! 
! 	* com.c (copy_lang_decl): Delete.
! 
! 2002-02-27  Zack Weinberg  <zack@codesourcery.com>
! 
! 	* com.c, lex.c, top.c: Delete traditional-mode-related code
! 	copied from the C front end but not used, or used only to
! 	permit the compiler to link.
  
  2002-02-13  Toon Moene  <toon@moene.indiv.nluug.nl>
  
*************** Fri Sep 24 10:48:10 1999  Bernd Schmidt 
*** 1537,1543 ****
  
  Tue Sep 21 09:08:30 1999  Toon Moene  <toon@moene.indiv.nluug.nl>
  
! 	* g77spec.c (lang_specific_driver): Initialise return value.
  
  Thu Sep 16 18:07:11 1999  Kaveh R. Ghazi  <ghazi@caip.rutgers.edu>
  
--- 1953,1959 ----
  
  Tue Sep 21 09:08:30 1999  Toon Moene  <toon@moene.indiv.nluug.nl>
  
! 	* g77spec.c (lang_specific_driver): Initialize return value.
  
  Thu Sep 16 18:07:11 1999  Kaveh R. Ghazi  <ghazi@caip.rutgers.edu>
  
*************** Sat Jul 11 19:24:32 1998  Craig Burley  
*** 2817,2823 ****
  Sat Jul 11 18:24:37 1998  Craig Burley  <burley@gnu.org>
  
  	* com.c (ffecom_expr_) [FFEBLD_opCONTER]: Die if padding
! 	for constant is non-zero.
  
  	* com.c (__eprintf): Delete this function, it is obsolete.
  
--- 3233,3239 ----
  Sat Jul 11 18:24:37 1998  Craig Burley  <burley@gnu.org>
  
  	* com.c (ffecom_expr_) [FFEBLD_opCONTER]: Die if padding
! 	for constant is nonzero.
  
  	* com.c (__eprintf): Delete this function, it is obsolete.
  
*************** Wed Jul  1 11:19:13 1998  Craig Burley  
*** 2873,2879 ****
  	and even more elegantly than those.
  
  	* target.c (ffetarget_align): Make sure alignments
! 	are non-zero, just in case.
  
  See ChangeLog.0 for earlier changes.
  
--- 3289,3295 ----
  	and even more elegantly than those.
  
  	* target.c (ffetarget_align): Make sure alignments
! 	are nonzero, just in case.
  
  See ChangeLog.0 for earlier changes.
  
diff -Nrc3pad gcc-3.2.3/gcc/f/ChangeLog.0 gcc-3.3/gcc/f/ChangeLog.0
*** gcc-3.2.3/gcc/f/ChangeLog.0	1999-09-04 15:09:00.000000000 +0000
--- gcc-3.3/gcc/f/ChangeLog.0	2002-09-23 11:23:06.000000000 +0000
*************** Mon Jun 29 09:47:33 1998  Craig Burley  
*** 38,44 ****
  	of equiv area, extend lowering to maintain needed alignment.
  	* target.c (ffetarget_align): Handle negative offset correctly.
  
! 	* global.c (ffeglobal_pad_common): Warn about non-zero
  	padding only the first time its seen.
  	If new padding larger than old, update old.
  	(ffeglobal_save_common): Use correct type for size throughout.
--- 38,44 ----
  	of equiv area, extend lowering to maintain needed alignment.
  	* target.c (ffetarget_align): Handle negative offset correctly.
  
! 	* global.c (ffeglobal_pad_common): Warn about nonzero
  	padding only the first time its seen.
  	If new padding larger than old, update old.
  	(ffeglobal_save_common): Use correct type for size throughout.
*************** Sat Nov  2 13:50:31 1996  Craig Burley  
*** 2419,2425 ****
  	function call to the type in the fall-through case).
  
  	* ste.c (ffeste_R909_finish): Don't special-case list-directed
! 	I/O, now that libf2c can return non-zero status codes.
  	(ffeste_R910_finish): Ditto.
  	(ffeste_io_call_): Simplify logic.
  	(ffeste_io_impdo_):
--- 2419,2425 ----
  	function call to the type in the fall-through case).
  
  	* ste.c (ffeste_R909_finish): Don't special-case list-directed
! 	I/O, now that libf2c can return nonzero status codes.
  	(ffeste_R910_finish): Ditto.
  	(ffeste_io_call_): Simplify logic.
  	(ffeste_io_impdo_):
diff -Nrc3pad gcc-3.2.3/gcc/f/com.c gcc-3.3/gcc/f/com.c
*** gcc-3.2.3/gcc/f/com.c	2002-09-07 19:18:46.000000000 +0000
--- gcc-3.3/gcc/f/com.c	2003-03-24 07:44:49.000000000 +0000
*************** the Free Software Foundation, 59 Temple 
*** 82,87 ****
--- 82,88 ----
  
  #include "proj.h"
  #include "flags.h"
+ #include "real.h"
  #include "rtl.h"
  #include "toplev.h"
  #include "tree.h"
*************** the Free Software Foundation, 59 Temple 
*** 92,97 ****
--- 93,99 ----
  #include "intl.h"
  #include "langhooks.h"
  #include "langhooks-def.h"
+ #include "debug.h"
  
  /* VMS-specific definitions */
  #ifdef VMS
*************** tree string_type_node;
*** 154,160 ****
     inventions should be renamed to be canonical.  Note that only
     the ones currently required to be global are so.  */
  
! static tree ffecom_tree_fun_type_void;
  
  tree ffecom_integer_type_node;	/* Abbrev for _tree_type[blah][blah]. */
  tree ffecom_integer_zero_node;	/* Like *_*_* with g77's integer type. */
--- 156,162 ----
     inventions should be renamed to be canonical.  Note that only
     the ones currently required to be global are so.  */
  
! static GTY(()) tree ffecom_tree_fun_type_void;
  
  tree ffecom_integer_type_node;	/* Abbrev for _tree_type[blah][blah]. */
  tree ffecom_integer_zero_node;	/* Like *_*_* with g77's integer type. */
*************** tree ffecom_tree_type[FFEINFO_basictype]
*** 165,177 ****
     just use build_function_type and build_pointer_type on the
     appropriate _tree_type array element.  */
  
! static tree ffecom_tree_fun_type[FFEINFO_basictype][FFEINFO_kindtype];
! static tree ffecom_tree_ptr_to_fun_type[FFEINFO_basictype][FFEINFO_kindtype];
! static tree ffecom_tree_subr_type;
! static tree ffecom_tree_ptr_to_subr_type;
! static tree ffecom_tree_blockdata_type;
  
! static tree ffecom_tree_xargc_;
  
  ffecomSymbol ffecom_symbol_null_
  =
--- 167,180 ----
     just use build_function_type and build_pointer_type on the
     appropriate _tree_type array element.  */
  
! static GTY(()) tree ffecom_tree_fun_type[FFEINFO_basictype][FFEINFO_kindtype];
! static GTY(()) tree 
!   ffecom_tree_ptr_to_fun_type[FFEINFO_basictype][FFEINFO_kindtype];
! static GTY(()) tree ffecom_tree_subr_type;
! static GTY(()) tree ffecom_tree_ptr_to_subr_type;
! static GTY(()) tree ffecom_tree_blockdata_type;
  
! static GTY(()) tree ffecom_tree_xargc_;
  
  ffecomSymbol ffecom_symbol_null_
  =
*************** ffeinfoKindtype ffecom_label_kind_ = FFE
*** 187,196 ****
  
  int ffecom_f2c_typecode_[FFEINFO_basictype][FFEINFO_kindtype];
  tree ffecom_f2c_integer_type_node;
! tree ffecom_f2c_ptr_to_integer_type_node;
  tree ffecom_f2c_address_type_node;
  tree ffecom_f2c_real_type_node;
! tree ffecom_f2c_ptr_to_real_type_node;
  tree ffecom_f2c_doublereal_type_node;
  tree ffecom_f2c_complex_type_node;
  tree ffecom_f2c_doublecomplex_type_node;
--- 190,199 ----
  
  int ffecom_f2c_typecode_[FFEINFO_basictype][FFEINFO_kindtype];
  tree ffecom_f2c_integer_type_node;
! static GTY(()) tree ffecom_f2c_ptr_to_integer_type_node;
  tree ffecom_f2c_address_type_node;
  tree ffecom_f2c_real_type_node;
! static GTY(()) tree ffecom_f2c_ptr_to_real_type_node;
  tree ffecom_f2c_doublereal_type_node;
  tree ffecom_f2c_complex_type_node;
  tree ffecom_f2c_doublecomplex_type_node;
*************** struct _ffecom_concat_list_
*** 261,266 ****
--- 264,276 ----
  
  /* Static functions (internal). */
  
+ static tree ffe_type_for_mode PARAMS ((enum machine_mode, int));
+ static tree ffe_type_for_size PARAMS ((unsigned int, int));
+ static tree ffe_unsigned_type PARAMS ((tree));
+ static tree ffe_signed_type PARAMS ((tree));
+ static tree ffe_signed_or_unsigned_type PARAMS ((int, tree));
+ static bool ffe_mark_addressable PARAMS ((tree));
+ static tree ffe_truthvalue_conversion PARAMS ((tree));
  static void ffecom_init_decl_processing PARAMS ((void));
  static tree ffecom_arglist_expr_ (const char *argstring, ffebld args);
  static tree ffecom_widest_expr_type_ (ffebld list);
*************** static void delete_block (tree block);
*** 364,372 ****
  static int duplicate_decls (tree newdecl, tree olddecl);
  static void finish_decl (tree decl, tree init, bool is_top_level);
  static void finish_function (int nested);
! static const char *lang_printable_name (tree decl, int v);
  static tree lookup_name_current_level (tree name);
! static struct binding_level *make_binding_level (void);
  static void pop_f_function_context (void);
  static void push_f_function_context (void);
  static void push_parm_decl (tree parm);
--- 374,383 ----
  static int duplicate_decls (tree newdecl, tree olddecl);
  static void finish_decl (tree decl, tree init, bool is_top_level);
  static void finish_function (int nested);
! static const char *ffe_printable_name (tree decl, int v);
! static void ffe_print_error_function (diagnostic_context *, const char *);
  static tree lookup_name_current_level (tree name);
! static struct f_binding_level *make_binding_level (void);
  static void pop_f_function_context (void);
  static void push_f_function_context (void);
  static void push_parm_decl (tree parm);
*************** static ffesymbol ffecom_primary_entry_ =
*** 388,402 ****
  static ffesymbol ffecom_nested_entry_ = NULL;
  static ffeinfoKind ffecom_primary_entry_kind_;
  static bool ffecom_primary_entry_is_proc_;
! static tree ffecom_outer_function_decl_;
! static tree ffecom_previous_function_decl_;
! static tree ffecom_which_entrypoint_decl_;
! static tree ffecom_float_zero_ = NULL_TREE;
! static tree ffecom_float_half_ = NULL_TREE;
! static tree ffecom_double_zero_ = NULL_TREE;
! static tree ffecom_double_half_ = NULL_TREE;
! static tree ffecom_func_result_;/* For functions. */
! static tree ffecom_func_length_;/* For CHARACTER fns. */
  static ffebld ffecom_list_blockdata_;
  static ffebld ffecom_list_common_;
  static ffebld ffecom_master_arglist_;
--- 399,413 ----
  static ffesymbol ffecom_nested_entry_ = NULL;
  static ffeinfoKind ffecom_primary_entry_kind_;
  static bool ffecom_primary_entry_is_proc_;
! static GTY(()) tree ffecom_outer_function_decl_;
! static GTY(()) tree ffecom_previous_function_decl_;
! static GTY(()) tree ffecom_which_entrypoint_decl_;
! static GTY(()) tree ffecom_float_zero_;
! static GTY(()) tree ffecom_float_half_;
! static GTY(()) tree ffecom_double_zero_;
! static GTY(()) tree ffecom_double_half_;
! static GTY(()) tree ffecom_func_result_;/* For functions. */
! static GTY(()) tree ffecom_func_length_;/* For CHARACTER fns. */
  static ffebld ffecom_list_blockdata_;
  static ffebld ffecom_list_common_;
  static ffebld ffecom_master_arglist_;
*************** static ffetargetCharacterSize ffecom_mas
*** 406,414 ****
  static int ffecom_num_fns_ = 0;
  static int ffecom_num_entrypoints_ = 0;
  static bool ffecom_is_altreturning_ = FALSE;
! static tree ffecom_multi_type_node_;
! static tree ffecom_multi_retval_;
! static tree
    ffecom_multi_fields_[FFEINFO_basictype][FFEINFO_kindtype];
  static bool ffecom_member_namelisted_;	/* _member_phase1_ namelisted? */
  static bool ffecom_doing_entry_ = FALSE;
--- 417,425 ----
  static int ffecom_num_fns_ = 0;
  static int ffecom_num_entrypoints_ = 0;
  static bool ffecom_is_altreturning_ = FALSE;
! static GTY(()) tree ffecom_multi_type_node_;
! static GTY(()) tree ffecom_multi_retval_;
! static GTY(()) tree
    ffecom_multi_fields_[FFEINFO_basictype][FFEINFO_kindtype];
  static bool ffecom_member_namelisted_;	/* _member_phase1_ namelisted? */
  static bool ffecom_doing_entry_ = FALSE;
*************** static int ffecom_typesize_integer1_;
*** 418,430 ****
  
  /* Holds pointer-to-function expressions.  */
  
! static tree ffecom_gfrt_[FFECOM_gfrt]
! =
! {
! #define DEFGFRT(CODE,NAME,TYPE,ARGS,VOLATILE,COMPLEX,CONST) NULL_TREE,
! #include "com-rt.def"
! #undef DEFGFRT
! };
  
  /* Holds the external names of the functions.  */
  
--- 429,435 ----
  
  /* Holds pointer-to-function expressions.  */
  
! static GTY(()) tree ffecom_gfrt_[FFECOM_gfrt];
  
  /* Holds the external names of the functions.  */
  
*************** static const char *const ffecom_gfrt_arg
*** 521,527 ****
  /* Note that the information in the `names' component of the global contour
     is duplicated in the IDENTIFIER_GLOBAL_VALUEs of all identifiers.  */
  
! struct binding_level
    {
      /* A chain of _DECL nodes for all variables, constants, functions,
         and typedef types.  These are in the reverse of the order supplied.
--- 526,532 ----
  /* Note that the information in the `names' component of the global contour
     is duplicated in the IDENTIFIER_GLOBAL_VALUEs of all identifiers.  */
  
! struct f_binding_level GTY(())
    {
      /* A chain of _DECL nodes for all variables, constants, functions,
         and typedef types.  These are in the reverse of the order supplied.
*************** struct binding_level
*** 538,544 ****
      tree this_block;
  
      /* The binding level which this one is contained in (inherits from).  */
!     struct binding_level *level_chain;
  
      /* 0: no ffecom_prepare_* functions called at this level yet;
         1: ffecom_prepare* functions called, except not ffecom_prepare_end;
--- 543,549 ----
      tree this_block;
  
      /* The binding level which this one is contained in (inherits from).  */
!     struct f_binding_level *level_chain;
  
      /* 0: no ffecom_prepare_* functions called at this level yet;
         1: ffecom_prepare* functions called, except not ffecom_prepare_end;
*************** struct binding_level
*** 546,581 ****
      int prep_state;
    };
  
! #define NULL_BINDING_LEVEL (struct binding_level *) NULL
  
  /* The binding level currently in effect.  */
  
! static struct binding_level *current_binding_level;
  
  /* A chain of binding_level structures awaiting reuse.  */
  
! static struct binding_level *free_binding_level;
  
  /* The outermost binding level, for names of file scope.
     This is created when the compiler is started and exists
     through the entire run.  */
  
! static struct binding_level *global_binding_level;
  
  /* Binding level structures are initialized by copying this one.  */
  
! static const struct binding_level clear_binding_level
  =
  {NULL, NULL, NULL, NULL_BINDING_LEVEL, 0};
  
  /* Language-dependent contents of an identifier.  */
  
! struct lang_identifier
!   {
!     struct tree_identifier ignore;
!     tree global_value, local_value, label_value;
!     bool invented;
!   };
  
  /* Macros for access to language-specific slots in an identifier.  */
  /* Each of these slots contains a DECL node or null.  */
--- 551,588 ----
      int prep_state;
    };
  
! #define NULL_BINDING_LEVEL (struct f_binding_level *) NULL
  
  /* The binding level currently in effect.  */
  
! static GTY(()) struct f_binding_level *current_binding_level;
  
  /* A chain of binding_level structures awaiting reuse.  */
  
! static GTY((deletable (""))) struct f_binding_level *free_binding_level;
  
  /* The outermost binding level, for names of file scope.
     This is created when the compiler is started and exists
     through the entire run.  */
  
! static struct f_binding_level *global_binding_level;
  
  /* Binding level structures are initialized by copying this one.  */
  
! static const struct f_binding_level clear_binding_level
  =
  {NULL, NULL, NULL, NULL_BINDING_LEVEL, 0};
  
  /* Language-dependent contents of an identifier.  */
  
! struct lang_identifier GTY(())
! {
!   struct tree_identifier common;
!   tree global_value;
!   tree local_value;
!   tree label_value;
!   bool invented;
! };
  
  /* Macros for access to language-specific slots in an identifier.  */
  /* Each of these slots contains a DECL node or null.  */
*************** struct lang_identifier
*** 596,601 ****
--- 603,627 ----
  #define IDENTIFIER_INVENTED(NODE)	\
    (((struct lang_identifier *)(NODE))->invented)
  
+ /* The resulting tree type.  */
+ union lang_tree_node 
+   GTY((desc ("TREE_CODE (&%h.generic) == IDENTIFIER_NODE"),
+        chain_next ("(union lang_tree_node *)TREE_CHAIN (&%h.generic)")))
+ {
+   union tree_node GTY ((tag ("0"), 
+ 			desc ("tree_node_structure (&%h)"))) 
+     generic;
+   struct lang_identifier GTY ((tag ("1"))) identifier;
+ };
+ 
+ /* Fortran doesn't use either of these.  */
+ struct lang_decl GTY(()) 
+ {
+ };
+ struct lang_type GTY(())
+ {
+ };
+ 
  /* In identifiers, C uses the following fields in a special way:
     TREE_PUBLIC	      to record that there was a previous local extern decl.
     TREE_USED	      to record that such a decl was used.
*************** struct lang_identifier
*** 605,615 ****
     that have names.  Here so we can clear out their names' definitions
     at the end of the function.  */
  
! static tree named_labels;
  
  /* A list of LABEL_DECLs from outer contexts that are currently shadowed.  */
  
! static tree shadowed_labels;
  
  /* Return the subscript expression, modified to do range-checking.
  
--- 631,641 ----
     that have names.  Here so we can clear out their names' definitions
     at the end of the function.  */
  
! static GTY(()) tree named_labels;
  
  /* A list of LABEL_DECLs from outer contexts that are currently shadowed.  */
  
! static GTY(()) tree shadowed_labels;
  
  /* Return the subscript expression, modified to do range-checking.
  
*************** ffecom_subscript_check_ (tree array, tre
*** 780,785 ****
--- 806,812 ----
    die = ffecom_call_gfrt (FFECOM_gfrtRANGE,
  			  args, NULL_TREE);
    TREE_SIDE_EFFECTS (die) = 1;
+   die = convert (void_type_node, die);
  
    element = ffecom_3 (COND_EXPR,
  		      TREE_TYPE (element),
*************** ffecom_subscript_check_ (tree array, tre
*** 795,801 ****
     `item' is NULL_TREE, or the transformed pointer to the array.
     `expr' is the original opARRAYREF expression, which is transformed
       if `item' is NULL_TREE.
!    `want_ptr' is non-zero if a pointer to the element, instead of
       the element itself, is to be returned.  */
  
  static tree
--- 822,828 ----
     `item' is NULL_TREE, or the transformed pointer to the array.
     `expr' is the original opARRAYREF expression, which is transformed
       if `item' is NULL_TREE.
!    `want_ptr' is nonzero if a pointer to the element, instead of
       the element itself, is to be returned.  */
  
  static tree
*************** ffecom_arrayref_ (tree item, ffebld expr
*** 854,860 ****
  	return item;
  
        if (ffeinfo_where (ffebld_info (expr)) == FFEINFO_whereFLEETING
! 	  && ! mark_addressable (item))
  	return error_mark_node;
      }
  
--- 881,887 ----
  	return item;
  
        if (ffeinfo_where (ffebld_info (expr)) == FFEINFO_whereFLEETING
! 	  && ! ffe_mark_addressable (item))
  	return error_mark_node;
      }
  
*************** ffecom_call_ (tree fn, ffeinfoKindtype k
*** 1787,1801 ****
  				       callee_commons,
  				       scalar_args))
  	{
- #ifdef HOHO
- 	  tempvar = ffecom_make_tempvar (ffecom_tree_type
- 					 [FFEINFO_basictypeCOMPLEX][kt],
- 					 FFETARGET_charactersizeNONE,
- 					 -1);
- #else
  	  tempvar = hook;
  	  assert (tempvar);
- #endif
  	}
        else
  	{
--- 1814,1821 ----
*************** ffecom_char_args_x_ (tree *xitem, tree *
*** 2143,2155 ****
  	    if (!ffesymbol_hook (s).addr)
  	      item = ffecom_1_fn (item);
  	  }
- 
- #ifdef HOHO
- 	tempvar = ffecom_push_tempvar (char_type_node, size, -1, TRUE);
- #else
  	tempvar = ffebld_nonter_hook (expr);
  	assert (tempvar);
- #endif
  	tempvar = ffecom_1 (ADDR_EXPR,
  			    build_pointer_type (TREE_TYPE (tempvar)),
  			    tempvar);
--- 2163,2170 ----
*************** ffecom_char_args_x_ (tree *xitem, tree *
*** 2201,2213 ****
  	  tree args;
  	  tree newlen;
  
- #ifdef HOHO
- 	  tempvar = ffecom_make_tempvar (char_type_node,
- 					 ffebld_size (expr), -1);
- #else
  	  tempvar = ffebld_nonter_hook (expr);
  	  assert (tempvar);
- #endif
  	  tempvar = ffecom_1 (ADDR_EXPR,
  			      build_pointer_type (TREE_TYPE (tempvar)),
  			      tempvar);
--- 2216,2223 ----
*************** ffecom_expr_intrinsic_ (ffebld expr, tre
*** 4021,4032 ****
  
      case FFEINTRIN_impCHAR:
      case FFEINTRIN_impACHAR:
- #ifdef HOHO
-       tempvar = ffecom_make_tempvar (char_type_node, 1, -1);
- #else
        tempvar = ffebld_nonter_hook (expr);
        assert (tempvar);
- #endif
        {
  	tree tmv = TYPE_MAIN_VARIANT (TREE_TYPE (TREE_TYPE (tempvar)));
  
--- 4031,4038 ----
*************** ffecom_expr_power_integer_ (ffebld expr)
*** 5599,5605 ****
  
      ffecom_start_compstmt ();
  
- #ifndef HAHA
      rtmp = ffecom_make_tempvar ("power_r", rtype,
  				FFETARGET_charactersizeNONE, -1);
      ltmp = ffecom_make_tempvar ("power_l", ltype,
--- 5605,5610 ----
*************** ffecom_expr_power_integer_ (ffebld expr)
*** 5612,5636 ****
  				    FFETARGET_charactersizeNONE, -1);
      else
        divide = NULL_TREE;
- #else  /* HAHA */
-     {
-       tree hook;
- 
-       hook = ffebld_nonter_hook (expr);
-       assert (hook);
-       assert (TREE_CODE (hook) == TREE_VEC);
-       assert (TREE_VEC_LENGTH (hook) == 4);
-       rtmp = TREE_VEC_ELT (hook, 0);
-       ltmp = TREE_VEC_ELT (hook, 1);
-       result = TREE_VEC_ELT (hook, 2);
-       divide = TREE_VEC_ELT (hook, 3);
-       if (TREE_CODE (ltype) == COMPLEX_TYPE
- 	  || TREE_CODE (ltype) == RECORD_TYPE)
- 	assert (divide);
-       else
- 	assert (! divide);
-     }
- #endif  /* HAHA */
  
      expand_expr_stmt (ffecom_modify (void_type_node,
  				     rtmp,
--- 5617,5622 ----
*************** ffecom_gfrt_tree_ (ffecomGfrt ix)
*** 6267,6293 ****
  /* A somewhat evil way to prevent the garbage collector
     from collecting 'tree' structures.  */
  #define NUM_TRACKED_CHUNK 63
! static struct tree_ggc_tracker
  {
    struct tree_ggc_tracker *next;
    tree trees[NUM_TRACKED_CHUNK];
! } *tracker_head = NULL;
! 
! static void
! mark_tracker_head (void *arg)
! {
!   struct tree_ggc_tracker *head;
!   int i;
! 
!   for (head = * (struct tree_ggc_tracker **) arg;
!        head != NULL;
!        head = head->next)
!   {
!     ggc_mark (head);
!     for (i = 0; i < NUM_TRACKED_CHUNK; i++)
!       ggc_mark_tree (head->trees[i]);
!   }
! }
  
  void
  ffecom_save_tree_forever (tree t)
--- 6253,6264 ----
  /* A somewhat evil way to prevent the garbage collector
     from collecting 'tree' structures.  */
  #define NUM_TRACKED_CHUNK 63
! struct tree_ggc_tracker GTY(())
  {
    struct tree_ggc_tracker *next;
    tree trees[NUM_TRACKED_CHUNK];
! };
! static GTY(()) struct tree_ggc_tracker *tracker_head;
  
  void
  ffecom_save_tree_forever (tree t)
*************** ffecom_let_char_ (tree dest_tree, tree d
*** 6725,6739 ****
      tree citem;
      tree clength;
  
- #ifdef HOHO
-     length_array
-       = lengths
-       = ffecom_push_tempvar (ffecom_f2c_ftnlen_type_node,
- 			     FFETARGET_charactersizeNONE, count, TRUE);
-     item_array = items = ffecom_push_tempvar (ffecom_f2c_address_type_node,
- 					      FFETARGET_charactersizeNONE,
- 					      count, TRUE);
- #else
      {
        tree hook;
  
--- 6696,6701 ----
*************** ffecom_let_char_ (tree dest_tree, tree d
*** 6744,6750 ****
        length_array = lengths = TREE_VEC_ELT (hook, 0);
        item_array = items = TREE_VEC_ELT (hook, 1);
      }
- #endif
  
      for (i = 0; i < count; ++i)
        {
--- 6706,6711 ----
*************** ffecom_sym_transform_ (ffesymbol s)
*** 7484,7490 ****
  		assert (et != NULL_TREE);
  
  		if (! TREE_STATIC (et))
! 		  put_var_into_stack (et);
  
  		offset = ffestorag_modulo (est)
  		  + ffestorag_offset (ffesymbol_storage (s))
--- 7445,7451 ----
  		assert (et != NULL_TREE);
  
  		if (! TREE_STATIC (et))
! 		  put_var_into_stack (et, /*rescan=*/true);
  
  		offset = ffestorag_modulo (est)
  		  + ffestorag_offset (ffesymbol_storage (s))
*************** ffecom_type_localvar_ (ffesymbol s, ffei
*** 9205,9219 ****
  
  /* Build Namelist type.  */
  
  static tree
  ffecom_type_namelist_ ()
  {
!   static tree type = NULL_TREE;
! 
!   if (type == NULL_TREE)
      {
!       static tree namefield, varsfield, nvarsfield;
!       tree vardesctype;
  
        vardesctype = ffecom_type_vardesc_ ();
  
--- 9166,9178 ----
  
  /* Build Namelist type.  */
  
+ static GTY(()) tree ffecom_type_namelist_var;
  static tree
  ffecom_type_namelist_ ()
  {
!   if (ffecom_type_namelist_var == NULL_TREE)
      {
!       tree namefield, varsfield, nvarsfield, vardesctype, type;
  
        vardesctype = ffecom_type_vardesc_ ();
  
*************** ffecom_type_namelist_ ()
*** 9230,9251 ****
        TYPE_FIELDS (type) = namefield;
        layout_type (type);
  
!       ggc_add_tree_root (&type, 1);
      }
  
!   return type;
  }
  
  /* Build Vardesc type.  */
  
  static tree
  ffecom_type_vardesc_ ()
  {
!   static tree type = NULL_TREE;
!   static tree namefield, addrfield, dimsfield, typefield;
! 
!   if (type == NULL_TREE)
      {
        type = make_node (RECORD_TYPE);
  
        namefield = ffecom_decl_field (type, NULL_TREE, "name",
--- 9189,9209 ----
        TYPE_FIELDS (type) = namefield;
        layout_type (type);
  
!       ffecom_type_namelist_var = type;
      }
  
!   return ffecom_type_namelist_var;
  }
  
  /* Build Vardesc type.  */
  
+ static GTY(()) tree ffecom_type_vardesc_var;
  static tree
  ffecom_type_vardesc_ ()
  {
!   if (ffecom_type_vardesc_var == NULL_TREE)
      {
+       tree namefield, addrfield, dimsfield, typefield, type;
        type = make_node (RECORD_TYPE);
  
        namefield = ffecom_decl_field (type, NULL_TREE, "name",
*************** ffecom_type_vardesc_ ()
*** 9260,9269 ****
        TYPE_FIELDS (type) = namefield;
        layout_type (type);
  
!       ggc_add_tree_root (&type, 1);
      }
  
!   return type;
  }
  
  static tree
--- 9218,9227 ----
        TYPE_FIELDS (type) = namefield;
        layout_type (type);
  
!       ffecom_type_vardesc_var = type;
      }
  
!   return ffecom_type_vardesc_var;
  }
  
  static tree
*************** ffecom_1 (enum tree_code code, tree type
*** 9525,9531 ****
  
    if (code == ADDR_EXPR)
      {
!       if (!mark_addressable (node))
  	assert ("can't mark_addressable this node!" == NULL);
      }
  
--- 9483,9489 ----
  
    if (code == ADDR_EXPR)
      {
!       if (!ffe_mark_addressable (node))
  	assert ("can't mark_addressable this node!" == NULL);
      }
  
*************** ffecom_arg_ptr_to_expr (ffebld expr, tre
*** 10251,10268 ****
      /* ~~Kludge! */
      assert (sz != FFETARGET_charactersizeNONE);
  
- #ifdef HOHO
-     length_array
-       = lengths
-       = ffecom_push_tempvar (ffecom_f2c_ftnlen_type_node,
- 			     FFETARGET_charactersizeNONE, count, TRUE);
-     item_array
-       = items
-       = ffecom_push_tempvar (ffecom_f2c_address_type_node,
- 			     FFETARGET_charactersizeNONE, count, TRUE);
-     temporary = ffecom_push_tempvar (char_type_node,
- 				     sz, -1, TRUE);
- #else
      {
        tree hook;
  
--- 10209,10214 ----
*************** ffecom_arg_ptr_to_expr (ffebld expr, tre
*** 10274,10280 ****
        item_array = items = TREE_VEC_ELT (hook, 1);
        temporary = TREE_VEC_ELT (hook, 2);
      }
- #endif
  
      known_length = ffecom_f2c_ftnlen_zero_node;
  
--- 10220,10225 ----
*************** ffecom_constantunion (ffebldConstantUnio
*** 10648,10653 ****
--- 10593,10670 ----
    return item;
  }
  
+ /* Transform constant-union to tree, with the type known.  */
+ 
+ tree
+ ffecom_constantunion_with_type (ffebldConstantUnion *cu,
+ 		      tree tree_type, ffebldConst ct)
+ {
+   tree item;
+ 
+   int val;
+ 
+   switch (ct)
+   {
+ #if FFETARGET_okINTEGER1
+ 	  case  FFEBLD_constINTEGER1:
+          	  val = ffebld_cu_val_integer1 (*cu);
+ 		  item = build_int_2 (val, (val < 0) ? -1 : 0);
+ 		  break;
+ #endif
+ #if FFETARGET_okINTEGER2
+ 	  case  FFEBLD_constINTEGER2:
+ 		  val = ffebld_cu_val_integer2 (*cu);
+ 		  item = build_int_2 (val, (val < 0) ? -1 : 0);
+ 		  break;
+ #endif
+ #if FFETARGET_okINTEGER3
+ 	  case  FFEBLD_constINTEGER3:
+ 		  val = ffebld_cu_val_integer3 (*cu);
+ 		  item = build_int_2 (val, (val < 0) ? -1 : 0);
+ 		  break;
+ #endif
+ #if FFETARGET_okINTEGER4
+ 	  case  FFEBLD_constINTEGER4:
+ 		  val = ffebld_cu_val_integer4 (*cu);
+ 		  item = build_int_2 (val, (val < 0) ? -1 : 0);
+ 		  break;
+ #endif
+ #if FFETARGET_okLOGICAL1
+ 	  case  FFEBLD_constLOGICAL1:
+ 		  val = ffebld_cu_val_logical1 (*cu);
+ 		  item = build_int_2 (val, (val < 0) ? -1 : 0);
+ 		  break;
+ #endif
+ #if FFETARGET_okLOGICAL2
+           case  FFEBLD_constLOGICAL2:
+ 		  val = ffebld_cu_val_logical2 (*cu);
+ 		  item = build_int_2 (val, (val < 0) ? -1 : 0);
+ 		  break;
+ #endif
+ #if FFETARGET_okLOGICAL3
+ 	  case  FFEBLD_constLOGICAL3:
+ 		  val = ffebld_cu_val_logical3 (*cu);
+ 		  item = build_int_2 (val, (val < 0) ? -1 : 0);
+ 		  break;
+ #endif
+ #if FFETARGET_okLOGICAL4
+ 	  case  FFEBLD_constLOGICAL4:
+ 		  val = ffebld_cu_val_logical4 (*cu);
+ 		  item = build_int_2 (val, (val < 0) ? -1 : 0);
+ 		  break;
+ #endif
+ 	  default:
+ 		  assert ("constant type not supported"==NULL);
+ 		  return error_mark_node;
+ 		  break;
+   }
+ 
+   TREE_TYPE (item) = tree_type;
+ 
+   TREE_CONSTANT (item) = 1;
+ 
+   return item;
+ }
  /* Transform expression into constant tree.
  
     If the expression can be transformed into a tree that is constant,
*************** ffecom_init_0 ()
*** 11180,11186 ****
  
        name = bsearch ("foo", &names[0], ARRAY_SIZE (names), sizeof (names[0]),
  		      (int (*)(const void *, const void *)) strcmp);
!       if (name != &names[0][2])
  	{
  	  assert ("bsearch doesn't work, #define FFEPROJ_BSEARCH 0 in proj.h"
  		  == NULL);
--- 11197,11203 ----
  
        name = bsearch ("foo", &names[0], ARRAY_SIZE (names), sizeof (names[0]),
  		      (int (*)(const void *, const void *)) strcmp);
!       if (name != &names[2][0])
  	{
  	  assert ("bsearch doesn't work, #define FFEPROJ_BSEARCH 0 in proj.h"
  		  == NULL);
*************** ffecom_init_0 ()
*** 11724,11746 ****
      = build_function_type (void_type_node, NULL_TREE);
  
    builtin_function ("__builtin_sqrtf", float_ftype_float,
! 		    BUILT_IN_SQRTF, BUILT_IN_NORMAL, "sqrtf");
    builtin_function ("__builtin_sqrt", double_ftype_double,
! 		    BUILT_IN_SQRT, BUILT_IN_NORMAL, "sqrt");
    builtin_function ("__builtin_sqrtl", ldouble_ftype_ldouble,
! 		    BUILT_IN_SQRTL, BUILT_IN_NORMAL, "sqrtl");
    builtin_function ("__builtin_sinf", float_ftype_float,
! 		    BUILT_IN_SINF, BUILT_IN_NORMAL, "sinf");
    builtin_function ("__builtin_sin", double_ftype_double,
! 		    BUILT_IN_SIN, BUILT_IN_NORMAL, "sin");
    builtin_function ("__builtin_sinl", ldouble_ftype_ldouble,
! 		    BUILT_IN_SINL, BUILT_IN_NORMAL, "sinl");
    builtin_function ("__builtin_cosf", float_ftype_float,
! 		    BUILT_IN_COSF, BUILT_IN_NORMAL, "cosf");
    builtin_function ("__builtin_cos", double_ftype_double,
! 		    BUILT_IN_COS, BUILT_IN_NORMAL, "cos");
    builtin_function ("__builtin_cosl", ldouble_ftype_ldouble,
! 		    BUILT_IN_COSL, BUILT_IN_NORMAL, "cosl");
  
    pedantic_lvalues = FALSE;
  
--- 11741,11763 ----
      = build_function_type (void_type_node, NULL_TREE);
  
    builtin_function ("__builtin_sqrtf", float_ftype_float,
! 		    BUILT_IN_SQRTF, BUILT_IN_NORMAL, "sqrtf", NULL_TREE);
    builtin_function ("__builtin_sqrt", double_ftype_double,
! 		    BUILT_IN_SQRT, BUILT_IN_NORMAL, "sqrt", NULL_TREE);
    builtin_function ("__builtin_sqrtl", ldouble_ftype_ldouble,
! 		    BUILT_IN_SQRTL, BUILT_IN_NORMAL, "sqrtl", NULL_TREE);
    builtin_function ("__builtin_sinf", float_ftype_float,
! 		    BUILT_IN_SINF, BUILT_IN_NORMAL, "sinf", NULL_TREE);
    builtin_function ("__builtin_sin", double_ftype_double,
! 		    BUILT_IN_SIN, BUILT_IN_NORMAL, "sin", NULL_TREE);
    builtin_function ("__builtin_sinl", ldouble_ftype_ldouble,
! 		    BUILT_IN_SINL, BUILT_IN_NORMAL, "sinl", NULL_TREE);
    builtin_function ("__builtin_cosf", float_ftype_float,
! 		    BUILT_IN_COSF, BUILT_IN_NORMAL, "cosf", NULL_TREE);
    builtin_function ("__builtin_cos", double_ftype_double,
! 		    BUILT_IN_COS, BUILT_IN_NORMAL, "cos", NULL_TREE);
    builtin_function ("__builtin_cosl", ldouble_ftype_ldouble,
! 		    BUILT_IN_COSL, BUILT_IN_NORMAL, "cosl", NULL_TREE);
  
    pedantic_lvalues = FALSE;
  
*************** ffecom_init_0 ()
*** 11804,11814 ****
    {
      REAL_VALUE_TYPE point_5;
  
- #ifdef REAL_ARITHMETIC
      REAL_ARITHMETIC (point_5, RDIV_EXPR, dconst1, dconst2);
- #else
-     point_5 = .5;
- #endif
      ffecom_float_half_ = build_real (float_type_node, point_5);
      ffecom_double_half_ = build_real (double_type_node, point_5);
    }
--- 11821,11827 ----
*************** ffecom_prepare_expr_ (ffebld expr, ffebl
*** 12466,12492 ****
  	}
        break;
  
- #ifdef HAHA
-     case FFEBLD_opPOWER:
-       {
- 	tree rtype, ltype;
- 	tree rtmp, ltmp, result;
- 
- 	ltype = ffecom_type_expr (ffebld_left (expr));
- 	rtype = ffecom_type_expr (ffebld_right (expr));
- 
- 	rtmp = ffecom_make_tempvar (rtype, FFETARGET_charactersizeNONE, -1);
- 	ltmp = ffecom_make_tempvar (ltype, FFETARGET_charactersizeNONE, -1);
- 	result = ffecom_make_tempvar (ltype, FFETARGET_charactersizeNONE, -1);
- 
- 	tempvar = make_tree_vec (3);
- 	TREE_VEC_ELT (tempvar, 0) = rtmp;
- 	TREE_VEC_ELT (tempvar, 1) = ltmp;
- 	TREE_VEC_ELT (tempvar, 2) = result;
-       }
-       break;
- #endif  /* HAHA */
- 
      case FFEBLD_opCONCATENATE:
        {
  	/* This gets special handling, because only one set of temps
--- 12479,12484 ----
*************** ffecom_temp_label ()
*** 13009,13015 ****
  tree
  ffecom_truth_value (tree expr)
  {
!   return truthvalue_conversion (expr);
  }
  
  /* Return the inversion of a truth value (the inversion of what
--- 13001,13007 ----
  tree
  ffecom_truth_value (tree expr)
  {
!   return ffe_truthvalue_conversion (expr);
  }
  
  /* Return the inversion of a truth value (the inversion of what
*************** bison_rule_compstmt_ ()
*** 13154,13165 ****
     See tree.h for its possible values.
  
     If LIBRARY_NAME is nonzero, use that for DECL_ASSEMBLER_NAME,
!    the name to be called if we can't opencode the function.  */
  
  tree
  builtin_function (const char *name, tree type, int function_code,
  		  enum built_in_class class,
! 		  const char *library_name)
  {
    tree decl = build_decl (FUNCTION_DECL, get_identifier (name), type);
    DECL_EXTERNAL (decl) = 1;
--- 13146,13159 ----
     See tree.h for its possible values.
  
     If LIBRARY_NAME is nonzero, use that for DECL_ASSEMBLER_NAME,
!    the name to be called if we can't opencode the function.  If
!    ATTRS is nonzero, use that for the function's attribute list.  */
  
  tree
  builtin_function (const char *name, tree type, int function_code,
  		  enum built_in_class class,
! 		  const char *library_name,
! 		  tree attrs ATTRIBUTE_UNUSED)
  {
    tree decl = build_decl (FUNCTION_DECL, get_identifier (name), type);
    DECL_EXTERNAL (decl) = 1;
*************** finish_function (int nested)
*** 13639,13645 ****
     nested function and all).  */
  
  static const char *
! lang_printable_name (tree decl, int v)
  {
    /* Just to keep GCC quiet about the unused variable.
       In theory, differing values of V should produce different
--- 13633,13639 ----
     nested function and all).  */
  
  static const char *
! ffe_printable_name (tree decl, int v)
  {
    /* Just to keep GCC quiet about the unused variable.
       In theory, differing values of V should produce different
*************** lang_printable_name (tree decl, int v)
*** 13657,13664 ****
     an error.  */
  
  static void
! lang_print_error_function (diagnostic_context *context __attribute__((unused)),
!                            const char *file)
  {
    static ffeglobal last_g = NULL;
    static ffesymbol last_s = NULL;
--- 13651,13658 ----
     an error.  */
  
  static void
! ffe_print_error_function (diagnostic_context *context __attribute__((unused)),
! 			  const char *file)
  {
    static ffeglobal last_g = NULL;
    static ffesymbol last_s = NULL;
*************** lookup_name_current_level (tree name)
*** 13727,13739 ****
    return t;
  }
  
! /* Create a new `struct binding_level'.  */
  
! static struct binding_level *
  make_binding_level ()
  {
    /* NOSTRICT */
!   return (struct binding_level *) xmalloc (sizeof (struct binding_level));
  }
  
  /* Save and restore the variables in this file and elsewhere
--- 13721,13733 ----
    return t;
  }
  
! /* Create a new `struct f_binding_level'.  */
  
! static struct f_binding_level *
  make_binding_level ()
  {
    /* NOSTRICT */
!   return ggc_alloc (sizeof (struct f_binding_level));
  }
  
  /* Save and restore the variables in this file and elsewhere
*************** struct f_function
*** 13745,13751 ****
    struct f_function *next;
    tree named_labels;
    tree shadowed_labels;
!   struct binding_level *binding_level;
  };
  
  struct f_function *f_function_chain;
--- 13739,13745 ----
    struct f_function *next;
    tree named_labels;
    tree shadowed_labels;
!   struct f_binding_level *binding_level;
  };
  
  struct f_function *f_function_chain;
*************** pushdecl_top_level (x)
*** 13833,13839 ****
       tree x;
  {
    register tree t;
!   register struct binding_level *b = current_binding_level;
    register tree f = current_function_decl;
  
    current_binding_level = global_binding_level;
--- 13827,13833 ----
       tree x;
  {
    register tree t;
!   register struct f_binding_level *b = current_binding_level;
    register tree f = current_function_decl;
  
    current_binding_level = global_binding_level;
*************** start_decl (tree decl, bool is_top_level
*** 13937,13943 ****
  
     Returns 1 on success.  If the DECLARATOR is not suitable for a function
     (it defines a datum instead), we return 0, which tells
!    yyparse to report a parse error.
  
     NESTED is nonzero for a function nested within another function.  */
  
--- 13931,13937 ----
  
     Returns 1 on success.  If the DECLARATOR is not suitable for a function
     (it defines a datum instead), we return 0, which tells
!    ffe_parse_file to report a parse error.
  
     NESTED is nonzero for a function nested within another function.  */
  
*************** convert (type, expr)
*** 14054,14068 ****
    return error_mark_node;
  }
  
- /* integrate_decl_tree calls this function, but since we don't use the
-    DECL_LANG_SPECIFIC field, this is a no-op.  */
- 
- void
- copy_lang_decl (node)
-      tree node UNUSED;
- {
- }
- 
  /* Return the list of declarations of the current level.
     Note that this list is in reverse order unless/until
     you nreverse it; and when you do nreverse it, you must
--- 14048,14053 ----
*************** global_bindings_p ()
*** 14082,14182 ****
    return current_binding_level == global_binding_level;
  }
  
- /* Print an error message for invalid use of an incomplete type.
-    VALUE is the expression that was used (or 0 if that isn't known)
-    and TYPE is the type that was invalid.  */
- 
- void
- incomplete_type_error (value, type)
-      tree value UNUSED;
-      tree type;
- {
-   if (TREE_CODE (type) == ERROR_MARK)
-     return;
- 
-   assert ("incomplete type?!?" == NULL);
- }
- 
- /* Mark ARG for GC.  */
- static void
- mark_binding_level (void *arg)
- {
-   struct binding_level *level = *(struct binding_level **) arg;
- 
-   while (level)
-     {
-       ggc_mark_tree (level->names);
-       ggc_mark_tree (level->blocks);
-       ggc_mark_tree (level->this_block);
-       level = level->level_chain;
-     }
- }
- 
  static void
  ffecom_init_decl_processing ()
  {
-   static tree *const tree_roots[] = {
-     &current_function_decl,
-     &string_type_node,
-     &ffecom_tree_fun_type_void,
-     &ffecom_integer_zero_node,
-     &ffecom_integer_one_node,
-     &ffecom_tree_subr_type,
-     &ffecom_tree_ptr_to_subr_type,
-     &ffecom_tree_blockdata_type,
-     &ffecom_tree_xargc_,
-     &ffecom_f2c_integer_type_node,
-     &ffecom_f2c_ptr_to_integer_type_node,
-     &ffecom_f2c_address_type_node,
-     &ffecom_f2c_real_type_node,
-     &ffecom_f2c_ptr_to_real_type_node,
-     &ffecom_f2c_doublereal_type_node,
-     &ffecom_f2c_complex_type_node,
-     &ffecom_f2c_doublecomplex_type_node,
-     &ffecom_f2c_longint_type_node,
-     &ffecom_f2c_logical_type_node,
-     &ffecom_f2c_flag_type_node,
-     &ffecom_f2c_ftnlen_type_node,
-     &ffecom_f2c_ftnlen_zero_node,
-     &ffecom_f2c_ftnlen_one_node,
-     &ffecom_f2c_ftnlen_two_node,
-     &ffecom_f2c_ptr_to_ftnlen_type_node,
-     &ffecom_f2c_ftnint_type_node,
-     &ffecom_f2c_ptr_to_ftnint_type_node,
-     &ffecom_outer_function_decl_,
-     &ffecom_previous_function_decl_,
-     &ffecom_which_entrypoint_decl_,
-     &ffecom_float_zero_,
-     &ffecom_float_half_,
-     &ffecom_double_zero_,
-     &ffecom_double_half_,
-     &ffecom_func_result_,
-     &ffecom_func_length_,
-     &ffecom_multi_type_node_,
-     &ffecom_multi_retval_,
-     &named_labels,
-     &shadowed_labels
-   };
-   size_t i;
- 
    malloc_init ();
  
-   /* Record our roots.  */
-   for (i = 0; i < ARRAY_SIZE (tree_roots); i++)
-     ggc_add_tree_root (tree_roots[i], 1);
-   ggc_add_tree_root (&ffecom_tree_type[0][0],
- 		     FFEINFO_basictype*FFEINFO_kindtype);
-   ggc_add_tree_root (&ffecom_tree_fun_type[0][0],
- 		     FFEINFO_basictype*FFEINFO_kindtype);
-   ggc_add_tree_root (&ffecom_tree_ptr_to_fun_type[0][0],
- 		     FFEINFO_basictype*FFEINFO_kindtype);
-   ggc_add_tree_root (ffecom_gfrt_, FFECOM_gfrt);
-   ggc_add_root (&current_binding_level, 1, sizeof current_binding_level,
-                 mark_binding_level);
-   ggc_add_root (&free_binding_level, 1, sizeof current_binding_level,
-                 mark_binding_level);
-   ggc_add_root (&tracker_head, 1, sizeof tracker_head, mark_tracker_head);
- 
    ffe_init_0 ();
  }
  
--- 14067,14077 ----
*************** static void ffe_finish PARAMS ((void));
*** 14219,14224 ****
--- 14114,14124 ----
  static void ffe_init_options PARAMS ((void));
  static void ffe_print_identifier PARAMS ((FILE *, tree, int));
  
+ struct language_function GTY(())
+ {
+   int unused;
+ };
+ 
  #undef  LANG_HOOKS_NAME
  #define LANG_HOOKS_NAME			"GNU F77"
  #undef  LANG_HOOKS_INIT
*************** static void ffe_print_identifier PARAMS 
*** 14229,14236 ****
--- 14129,14157 ----
  #define LANG_HOOKS_INIT_OPTIONS		ffe_init_options
  #undef  LANG_HOOKS_DECODE_OPTION
  #define LANG_HOOKS_DECODE_OPTION	ffe_decode_option
+ #undef  LANG_HOOKS_PARSE_FILE
+ #define LANG_HOOKS_PARSE_FILE		ffe_parse_file
+ #undef  LANG_HOOKS_MARK_ADDRESSABLE
+ #define LANG_HOOKS_MARK_ADDRESSABLE	ffe_mark_addressable
  #undef  LANG_HOOKS_PRINT_IDENTIFIER
  #define LANG_HOOKS_PRINT_IDENTIFIER	ffe_print_identifier
+ #undef  LANG_HOOKS_DECL_PRINTABLE_NAME
+ #define LANG_HOOKS_DECL_PRINTABLE_NAME	ffe_printable_name
+ #undef  LANG_HOOKS_PRINT_ERROR_FUNCTION
+ #define LANG_HOOKS_PRINT_ERROR_FUNCTION ffe_print_error_function
+ #undef  LANG_HOOKS_TRUTHVALUE_CONVERSION
+ #define LANG_HOOKS_TRUTHVALUE_CONVERSION ffe_truthvalue_conversion
+ 
+ #undef  LANG_HOOKS_TYPE_FOR_MODE
+ #define LANG_HOOKS_TYPE_FOR_MODE	ffe_type_for_mode
+ #undef  LANG_HOOKS_TYPE_FOR_SIZE
+ #define LANG_HOOKS_TYPE_FOR_SIZE	ffe_type_for_size
+ #undef  LANG_HOOKS_SIGNED_TYPE
+ #define LANG_HOOKS_SIGNED_TYPE		ffe_signed_type
+ #undef  LANG_HOOKS_UNSIGNED_TYPE
+ #define LANG_HOOKS_UNSIGNED_TYPE	ffe_unsigned_type
+ #undef  LANG_HOOKS_SIGNED_OR_UNSIGNED_TYPE
+ #define LANG_HOOKS_SIGNED_OR_UNSIGNED_TYPE ffe_signed_or_unsigned_type
  
  /* We do not wish to use alias-set based aliasing at all.  Used in the
     extreme (every object with its own set, with equivalences recorded) it
*************** static void ffe_print_identifier PARAMS 
*** 14242,14247 ****
--- 14163,14199 ----
  
  const struct lang_hooks lang_hooks = LANG_HOOKS_INITIALIZER;
  
+ /* Table indexed by tree code giving a string containing a character
+    classifying the tree code.  Possibilities are
+    t, d, s, c, r, <, 1, 2 and e.  See tree.def for details.  */
+ 
+ #define DEFTREECODE(SYM, NAME, TYPE, LENGTH) TYPE,
+ 
+ const char tree_code_type[] = {
+ #include "tree.def"
+ };
+ #undef DEFTREECODE
+ 
+ /* Table indexed by tree code giving number of expression
+    operands beyond the fixed part of the node structure.
+    Not used for types or decls.  */
+ 
+ #define DEFTREECODE(SYM, NAME, TYPE, LENGTH) LENGTH,
+ 
+ const unsigned char tree_code_length[] = {
+ #include "tree.def"
+ };
+ #undef DEFTREECODE
+ 
+ /* Names of tree components.
+    Used for printing out the tree and error messages.  */
+ #define DEFTREECODE(SYM, NAME, TYPE, LEN) NAME,
+ 
+ const char *const tree_code_name[] = {
+ #include "tree.def"
+ };
+ #undef DEFTREECODE
+ 
  static const char *
  ffe_init (filename)
       const char *filename;
*************** ffe_init (filename)
*** 14262,14269 ****
  #endif
  
    ffecom_init_decl_processing ();
-   decl_printable_name = lang_printable_name;
-   print_error_function = lang_print_error_function;
  
    /* If the file is output from cpp, it should contain a first line
       `# 1 "real-filename"', and the current design of gcc (toplev.c
--- 14214,14219 ----
*************** ffe_init_options ()
*** 14304,14311 ****
    flag_complex_divide_method = 1;
  }
  
! int
! mark_addressable (exp)
       tree exp;
  {
    register tree x = exp;
--- 14254,14261 ----
    flag_complex_divide_method = 1;
  }
  
! static bool
! ffe_mark_addressable (exp)
       tree exp;
  {
    register tree x = exp;
*************** mark_addressable (exp)
*** 14320,14326 ****
  
        case CONSTRUCTOR:
  	TREE_ADDRESSABLE (x) = 1;
! 	return 1;
  
        case VAR_DECL:
        case CONST_DECL:
--- 14270,14276 ----
  
        case CONSTRUCTOR:
  	TREE_ADDRESSABLE (x) = 1;
! 	return true;
  
        case VAR_DECL:
        case CONST_DECL:
*************** mark_addressable (exp)
*** 14332,14338 ****
  	    if (TREE_PUBLIC (x))
  	      {
  		assert ("address of global register var requested" == NULL);
! 		return 0;
  	      }
  	    assert ("address of register variable requested" == NULL);
  	  }
--- 14282,14288 ----
  	    if (TREE_PUBLIC (x))
  	      {
  		assert ("address of global register var requested" == NULL);
! 		return false;
  	      }
  	    assert ("address of register variable requested" == NULL);
  	  }
*************** mark_addressable (exp)
*** 14341,14351 ****
  	    if (TREE_PUBLIC (x))
  	      {
  		assert ("address of global register var requested" == NULL);
! 		return 0;
  	      }
  	    assert ("address of register var requested" == NULL);
  	  }
! 	put_var_into_stack (x);
  
  	/* drops in */
        case FUNCTION_DECL:
--- 14291,14301 ----
  	    if (TREE_PUBLIC (x))
  	      {
  		assert ("address of global register var requested" == NULL);
! 		return false;
  	      }
  	    assert ("address of register var requested" == NULL);
  	  }
! 	put_var_into_stack (x, /*rescan=*/true);
  
  	/* drops in */
        case FUNCTION_DECL:
*************** mark_addressable (exp)
*** 14356,14376 ****
  #endif
  
        default:
! 	return 1;
        }
  }
  
- /* If DECL has a cleanup, build and return that cleanup here.
-    This is a callback called by expand_expr.  */
- 
- tree
- maybe_build_cleanup (decl)
-      tree decl UNUSED;
- {
-   /* There are no cleanups in Fortran.  */
-   return NULL_TREE;
- }
- 
  /* Exit a binding level.
     Pop the level off, and restore the state of the identifier-decl mappings
     that were in effect when this level was entered.
--- 14306,14315 ----
  #endif
  
        default:
! 	return true;
        }
  }
  
  /* Exit a binding level.
     Pop the level off, and restore the state of the identifier-decl mappings
     that were in effect when this level was entered.
*************** poplevel (keep, reverse, functionbody)
*** 14494,14500 ****
    /* Pop the current level, and free the structure for reuse.  */
  
    {
!     register struct binding_level *level = current_binding_level;
      current_binding_level = current_binding_level->level_chain;
  
      level->level_chain = free_binding_level;
--- 14433,14439 ----
    /* Pop the current level, and free the structure for reuse.  */
  
    {
!     register struct f_binding_level *level = current_binding_level;
      current_binding_level = current_binding_level->level_chain;
  
      level->level_chain = free_binding_level;
*************** pushdecl (x)
*** 14549,14555 ****
  {
    register tree t;
    register tree name = DECL_NAME (x);
!   register struct binding_level *b = current_binding_level;
  
    if ((TREE_CODE (x) == FUNCTION_DECL)
        && (DECL_INITIAL (x) == 0)
--- 14488,14494 ----
  {
    register tree t;
    register tree name = DECL_NAME (x);
!   register struct f_binding_level *b = current_binding_level;
  
    if ((TREE_CODE (x) == FUNCTION_DECL)
        && (DECL_INITIAL (x) == 0)
*************** void
*** 14681,14687 ****
  pushlevel (tag_transparent)
       int tag_transparent;
  {
!   register struct binding_level *newlevel = NULL_BINDING_LEVEL;
  
    assert (! tag_transparent);
  
--- 14620,14626 ----
  pushlevel (tag_transparent)
       int tag_transparent;
  {
!   register struct f_binding_level *newlevel = NULL_BINDING_LEVEL;
  
    assert (! tag_transparent);
  
*************** set_block (block)
*** 14724,14731 ****
  					   BLOCK_SUBBLOCKS (block));
  }
  
! tree
! signed_or_unsigned_type (unsignedp, type)
       int unsignedp;
       tree type;
  {
--- 14663,14670 ----
  					   BLOCK_SUBBLOCKS (block));
  }
  
! static tree
! ffe_signed_or_unsigned_type (unsignedp, type)
       int unsignedp;
       tree type;
  {
*************** signed_or_unsigned_type (unsignedp, type
*** 14745,14759 ****
      return (unsignedp ? long_long_unsigned_type_node
  	    : long_long_integer_type_node);
  
!   type2 = type_for_size (TYPE_PRECISION (type), unsignedp);
    if (type2 == NULL_TREE)
      return type;
  
    return type2;
  }
  
! tree
! signed_type (type)
       tree type;
  {
    tree type1 = TYPE_MAIN_VARIANT (type);
--- 14684,14698 ----
      return (unsignedp ? long_long_unsigned_type_node
  	    : long_long_integer_type_node);
  
!   type2 = ffe_type_for_size (TYPE_PRECISION (type), unsignedp);
    if (type2 == NULL_TREE)
      return type;
  
    return type2;
  }
  
! static tree
! ffe_signed_type (type)
       tree type;
  {
    tree type1 = TYPE_MAIN_VARIANT (type);
*************** signed_type (type)
*** 14781,14787 ****
      return intQI_type_node;
  #endif
  
!   type2 = type_for_size (TYPE_PRECISION (type1), 0);
    if (type2 != NULL_TREE)
      return type2;
  
--- 14720,14726 ----
      return intQI_type_node;
  #endif
  
!   type2 = ffe_type_for_size (TYPE_PRECISION (type1), 0);
    if (type2 != NULL_TREE)
      return type2;
  
*************** signed_type (type)
*** 14807,14814 ****
  
     The resulting type should always be `integer_type_node'.  */
  
! tree
! truthvalue_conversion (expr)
       tree expr;
  {
    if (TREE_CODE (expr) == ERROR_MARK)
--- 14746,14753 ----
  
     The resulting type should always be `integer_type_node'.  */
  
! static tree
! ffe_truthvalue_conversion (expr)
       tree expr;
  {
    if (TREE_CODE (expr) == ERROR_MARK)
*************** truthvalue_conversion (expr)
*** 14885,14915 ****
        return ffecom_2 ((TREE_SIDE_EFFECTS (TREE_OPERAND (expr, 1))
  			? TRUTH_OR_EXPR : TRUTH_ORIF_EXPR),
  		       integer_type_node,
! 		       truthvalue_conversion (TREE_OPERAND (expr, 0)),
! 		       truthvalue_conversion (TREE_OPERAND (expr, 1)));
  
      case NEGATE_EXPR:
      case ABS_EXPR:
      case FLOAT_EXPR:
      case FFS_EXPR:
!       /* These don't change whether an object is non-zero or zero.  */
!       return truthvalue_conversion (TREE_OPERAND (expr, 0));
  
      case LROTATE_EXPR:
      case RROTATE_EXPR:
!       /* These don't change whether an object is zero or non-zero, but
  	 we can't ignore them if their second arg has side-effects.  */
        if (TREE_SIDE_EFFECTS (TREE_OPERAND (expr, 1)))
  	return build (COMPOUND_EXPR, integer_type_node, TREE_OPERAND (expr, 1),
! 		      truthvalue_conversion (TREE_OPERAND (expr, 0)));
        else
! 	return truthvalue_conversion (TREE_OPERAND (expr, 0));
  
      case COND_EXPR:
!       /* Distribute the conversion into the arms of a COND_EXPR.  */
!       return fold (build (COND_EXPR, integer_type_node, TREE_OPERAND (expr, 0),
! 			  truthvalue_conversion (TREE_OPERAND (expr, 1)),
! 			  truthvalue_conversion (TREE_OPERAND (expr, 2))));
  
      case CONVERT_EXPR:
        /* Don't cancel the effect of a CONVERT_EXPR from a REFERENCE_TYPE,
--- 14824,14861 ----
        return ffecom_2 ((TREE_SIDE_EFFECTS (TREE_OPERAND (expr, 1))
  			? TRUTH_OR_EXPR : TRUTH_ORIF_EXPR),
  		       integer_type_node,
! 		       ffe_truthvalue_conversion (TREE_OPERAND (expr, 0)),
! 		       ffe_truthvalue_conversion (TREE_OPERAND (expr, 1)));
  
      case NEGATE_EXPR:
      case ABS_EXPR:
      case FLOAT_EXPR:
      case FFS_EXPR:
!       /* These don't change whether an object is nonzero or zero.  */
!       return ffe_truthvalue_conversion (TREE_OPERAND (expr, 0));
  
      case LROTATE_EXPR:
      case RROTATE_EXPR:
!       /* These don't change whether an object is zero or nonzero, but
  	 we can't ignore them if their second arg has side-effects.  */
        if (TREE_SIDE_EFFECTS (TREE_OPERAND (expr, 1)))
  	return build (COMPOUND_EXPR, integer_type_node, TREE_OPERAND (expr, 1),
! 		      ffe_truthvalue_conversion (TREE_OPERAND (expr, 0)));
        else
! 	return ffe_truthvalue_conversion (TREE_OPERAND (expr, 0));
  
      case COND_EXPR:
!       {
! 	/* Distribute the conversion into the arms of a COND_EXPR.  */
! 	tree arg1 = TREE_OPERAND (expr, 1);
! 	tree arg2 = TREE_OPERAND (expr, 2);
! 	if (! VOID_TYPE_P (TREE_TYPE (arg1)))
! 	  arg1 = ffe_truthvalue_conversion (arg1);
! 	if (! VOID_TYPE_P (TREE_TYPE (arg2)))
! 	  arg2 = ffe_truthvalue_conversion (arg2);
! 	return fold (build (COND_EXPR, integer_type_node,
! 			    TREE_OPERAND (expr, 0), arg1, arg2));
!       }
  
      case CONVERT_EXPR:
        /* Don't cancel the effect of a CONVERT_EXPR from a REFERENCE_TYPE,
*************** truthvalue_conversion (expr)
*** 14922,14928 ****
        /* If this is widening the argument, we can ignore it.  */
        if (TYPE_PRECISION (TREE_TYPE (expr))
  	  >= TYPE_PRECISION (TREE_TYPE (TREE_OPERAND (expr, 0))))
! 	return truthvalue_conversion (TREE_OPERAND (expr, 0));
        break;
  
      case MINUS_EXPR:
--- 14868,14874 ----
        /* If this is widening the argument, we can ignore it.  */
        if (TYPE_PRECISION (TREE_TYPE (expr))
  	  >= TYPE_PRECISION (TREE_TYPE (TREE_OPERAND (expr, 0))))
! 	return ffe_truthvalue_conversion (TREE_OPERAND (expr, 0));
        break;
  
      case MINUS_EXPR:
*************** truthvalue_conversion (expr)
*** 14967,14986 ****
  	    ((TREE_SIDE_EFFECTS (expr)
  	      ? TRUTH_OR_EXPR : TRUTH_ORIF_EXPR),
  	     integer_type_node,
! 	     truthvalue_conversion (ffecom_1 (REALPART_EXPR,
! 					      TREE_TYPE (TREE_TYPE (expr)),
! 					      expr)),
! 	     truthvalue_conversion (ffecom_1 (IMAGPART_EXPR,
! 					      TREE_TYPE (TREE_TYPE (expr)),
! 					      expr))));
  
    return ffecom_2 (NE_EXPR, integer_type_node,
  		   expr,
  		   convert (TREE_TYPE (expr), integer_zero_node));
  }
  
! tree
! type_for_mode (mode, unsignedp)
       enum machine_mode mode;
       int unsignedp;
  {
--- 14913,14932 ----
  	    ((TREE_SIDE_EFFECTS (expr)
  	      ? TRUTH_OR_EXPR : TRUTH_ORIF_EXPR),
  	     integer_type_node,
! 	     ffe_truthvalue_conversion (ffecom_1 (REALPART_EXPR,
! 						  TREE_TYPE (TREE_TYPE (expr)),
! 						  expr)),
! 	     ffe_truthvalue_conversion (ffecom_1 (IMAGPART_EXPR,
! 						  TREE_TYPE (TREE_TYPE (expr)),
! 						  expr))));
  
    return ffecom_2 (NE_EXPR, integer_type_node,
  		   expr,
  		   convert (TREE_TYPE (expr), integer_zero_node));
  }
  
! static tree
! ffe_type_for_mode (mode, unsignedp)
       enum machine_mode mode;
       int unsignedp;
  {
*************** type_for_mode (mode, unsignedp)
*** 15039,15046 ****
    return 0;
  }
  
! tree
! type_for_size (bits, unsignedp)
       unsigned bits;
       int unsignedp;
  {
--- 14985,14992 ----
    return 0;
  }
  
! static tree
! ffe_type_for_size (bits, unsignedp)
       unsigned bits;
       int unsignedp;
  {
*************** type_for_size (bits, unsignedp)
*** 15075,15082 ****
    return 0;
  }
  
! tree
! unsigned_type (type)
       tree type;
  {
    tree type1 = TYPE_MAIN_VARIANT (type);
--- 15021,15028 ----
    return 0;
  }
  
! static tree
! ffe_unsigned_type (type)
       tree type;
  {
    tree type1 = TYPE_MAIN_VARIANT (type);
*************** unsigned_type (type)
*** 15104,15110 ****
      return unsigned_intQI_type_node;
  #endif
  
!   type2 = type_for_size (TYPE_PRECISION (type1), 1);
    if (type2 != NULL_TREE)
      return type2;
  
--- 15050,15056 ----
      return unsigned_intQI_type_node;
  #endif
  
!   type2 = ffe_type_for_size (TYPE_PRECISION (type1), 1);
    if (type2 != NULL_TREE)
      return type2;
  
*************** unsigned_type (type)
*** 15118,15138 ****
  
    return type;
  }
- 
- void
- lang_mark_tree (t)
-      union tree_node *t ATTRIBUTE_UNUSED;
- {
-   if (TREE_CODE (t) == IDENTIFIER_NODE)
-     {
-       struct lang_identifier *i = (struct lang_identifier *) t;
-       ggc_mark_tree (IDENTIFIER_GLOBAL_VALUE (i));
-       ggc_mark_tree (IDENTIFIER_LOCAL_VALUE (i));
-       ggc_mark_tree (IDENTIFIER_LABEL_VALUE (i));
-     }
-   else if (TYPE_P (t) && TYPE_LANG_SPECIFIC (t))
-     ggc_mark (TYPE_LANG_SPECIFIC (t));
- }
  
  /* From gcc/cccp.c, the code to handle -I.  */
  
--- 15064,15069 ----
*************** struct file_name_list
*** 15178,15184 ****
      char *fname;
      /* Mapping of file names for this directory.  */
      struct file_name_map *name_map;
!     /* Non-zero if name_map is valid.  */
      int got_name_map;
    };
  
--- 15109,15115 ----
      char *fname;
      /* Mapping of file names for this directory.  */
      struct file_name_map *name_map;
!     /* Nonzero if name_map is valid.  */
      int got_name_map;
    };
  
*************** read_name_map (dirname)
*** 15465,15474 ****
  
    dirlen = strlen (dirname);
    separator_needed = dirlen != 0 && dirname[dirlen - 1] != '/';
!   name = (char *) xmalloc (dirlen + strlen (FILE_NAME_MAP_FILE) + 2);
!   strcpy (name, dirname);
!   name[dirlen] = '/';
!   strcpy (name + dirlen + separator_needed, FILE_NAME_MAP_FILE);
    f = fopen (name, "r");
    free (name);
    if (!f)
--- 15396,15405 ----
  
    dirlen = strlen (dirname);
    separator_needed = dirlen != 0 && dirname[dirlen - 1] != '/';
!   if (separator_needed)
!     name = concat (dirname, "/", FILE_NAME_MAP_FILE, NULL);
!   else
!     name = concat (dirname, FILE_NAME_MAP_FILE, NULL);
    f = fopen (name, "r");
    free (name);
    if (!f)
*************** read_name_map (dirname)
*** 15498,15507 ****
  	    ptr->map_to = to;
  	  else
  	    {
! 	      ptr->map_to = xmalloc (dirlen + strlen (to) + 2);
! 	      strcpy (ptr->map_to, dirname);
! 	      ptr->map_to[dirlen] = '/';
! 	      strcpy (ptr->map_to + dirlen + separator_needed, to);
  	      free (to);
  	    }
  
--- 15429,15438 ----
  	    ptr->map_to = to;
  	  else
  	    {
! 	      if (separator_needed)
! 		ptr->map_to = concat (dirname, "/", to, NULL);
! 	      else
! 		ptr->map_to = concat (dirname, to, NULL);
  	      free (to);
  	    }
  
*************** typedef doublereal E_f; // real function
*** 16205,16211 ****
  
  // (No such symbols should be defined in a strict ANSI C compiler.
     We can avoid trouble with f2c-translated code by using
!    gcc -ansi [-traditional].) //
  
  
  
--- 16136,16142 ----
  
  // (No such symbols should be defined in a strict ANSI C compiler.
     We can avoid trouble with f2c-translated code by using
!    gcc -ansi.) //
  
  
  
*************** typedef doublereal E_f; // real function
*** 16636,16638 ****
--- 16567,16572 ----
  -------- (end output file from f2c)
  
  */
+ 
+ #include "gt-f-com.h"
+ #include "gtype-f.h"
diff -Nrc3pad gcc-3.2.3/gcc/f/com.h gcc-3.3/gcc/f/com.h
*** gcc-3.2.3/gcc/f/com.h	2001-10-17 22:34:51.000000000 +0000
--- gcc-3.3/gcc/f/com.h	2003-03-22 15:24:51.000000000 +0000
*************** struct _ffecom_symbol_
*** 157,193 ****
  #include "storag.h"
  #include "symbol.h"
  
! /* Structure definitions. */
! 
  
  /* Global objects accessed by users of this module. */
  
! extern tree string_type_node;
! extern tree ffecom_integer_type_node;
! extern tree ffecom_integer_zero_node;
! extern tree ffecom_integer_one_node;
! extern tree ffecom_tree_type[FFEINFO_basictype][FFEINFO_kindtype];
  extern ffecomSymbol ffecom_symbol_null_;
  extern ffeinfoKindtype ffecom_pointer_kind_;
  extern ffeinfoKindtype ffecom_label_kind_;
  
  extern int ffecom_f2c_typecode_[FFEINFO_basictype][FFEINFO_kindtype];
! extern tree ffecom_f2c_integer_type_node;
! extern tree ffecom_f2c_address_type_node;
! extern tree ffecom_f2c_real_type_node;
! extern tree ffecom_f2c_doublereal_type_node;
! extern tree ffecom_f2c_complex_type_node;
! extern tree ffecom_f2c_doublecomplex_type_node;
! extern tree ffecom_f2c_longint_type_node;
! extern tree ffecom_f2c_logical_type_node;
! extern tree ffecom_f2c_flag_type_node;
! extern tree ffecom_f2c_ftnlen_type_node;
! extern tree ffecom_f2c_ftnlen_zero_node;
! extern tree ffecom_f2c_ftnlen_one_node;
! extern tree ffecom_f2c_ftnlen_two_node;
! extern tree ffecom_f2c_ptr_to_ftnlen_type_node;
! extern tree ffecom_f2c_ftnint_type_node;
! extern tree ffecom_f2c_ptr_to_ftnint_type_node;
  
  /* Declare functions with prototypes. */
  
--- 157,198 ----
  #include "storag.h"
  #include "symbol.h"
  
! extern int global_bindings_p			PARAMS ((void));
! extern tree getdecls				PARAMS ((void));
! extern void pushlevel				PARAMS ((int));
! extern tree poplevel				PARAMS ((int,int, int));
! extern void insert_block			PARAMS ((tree));
! extern void set_block				PARAMS ((tree));
! extern tree pushdecl				PARAMS ((tree));
  
  /* Global objects accessed by users of this module. */
  
! extern GTY(()) tree string_type_node;
! extern GTY(()) tree ffecom_integer_type_node;
! extern GTY(()) tree ffecom_integer_zero_node;
! extern GTY(()) tree ffecom_integer_one_node;
! extern GTY(()) tree ffecom_tree_type[FFEINFO_basictype][FFEINFO_kindtype];
  extern ffecomSymbol ffecom_symbol_null_;
  extern ffeinfoKindtype ffecom_pointer_kind_;
  extern ffeinfoKindtype ffecom_label_kind_;
  
  extern int ffecom_f2c_typecode_[FFEINFO_basictype][FFEINFO_kindtype];
! extern GTY(()) tree ffecom_f2c_integer_type_node;
! extern GTY(()) tree ffecom_f2c_address_type_node;
! extern GTY(()) tree ffecom_f2c_real_type_node;
! extern GTY(()) tree ffecom_f2c_doublereal_type_node;
! extern GTY(()) tree ffecom_f2c_complex_type_node;
! extern GTY(()) tree ffecom_f2c_doublecomplex_type_node;
! extern GTY(()) tree ffecom_f2c_longint_type_node;
! extern GTY(()) tree ffecom_f2c_logical_type_node;
! extern GTY(()) tree ffecom_f2c_flag_type_node;
! extern GTY(()) tree ffecom_f2c_ftnlen_type_node;
! extern GTY(()) tree ffecom_f2c_ftnlen_zero_node;
! extern GTY(()) tree ffecom_f2c_ftnlen_one_node;
! extern GTY(()) tree ffecom_f2c_ftnlen_two_node;
! extern GTY(()) tree ffecom_f2c_ptr_to_ftnlen_type_node;
! extern GTY(()) tree ffecom_f2c_ftnint_type_node;
! extern GTY(()) tree ffecom_f2c_ptr_to_ftnint_type_node;
  
  /* Declare functions with prototypes. */
  
*************** tree ffecom_arg_expr (ffebld expr, tree 
*** 205,210 ****
--- 210,217 ----
  tree ffecom_arg_ptr_to_const_expr (ffebld expr, tree *length);
  tree ffecom_arg_ptr_to_expr (ffebld expr, tree *length);
  tree ffecom_call_gfrt (ffecomGfrt ix, tree args, tree hook);
+ tree ffecom_constantunion_with_type (ffebldConstantUnion *cu, 
+ 		            tree tree_type,ffebldConst ct);
  tree ffecom_constantunion (ffebldConstantUnion *cu, ffeinfoBasictype bt,
  			   ffeinfoKindtype kt, tree tree_type);
  tree ffecom_const_expr (ffebld expr);
*************** tree ffecom_truth_value (tree expr);
*** 265,270 ****
--- 272,278 ----
  tree ffecom_truth_value_invert (tree expr);
  tree ffecom_type_expr (ffebld expr);
  tree ffecom_which_entrypoint_decl (void);
+ void ffe_parse_file (int);
  
  /* Define macros. */
  
diff -Nrc3pad gcc-3.2.3/gcc/f/config-lang.in gcc-3.3/gcc/f/config-lang.in
*** gcc-3.2.3/gcc/f/config-lang.in	2001-12-20 00:20:46.000000000 +0000
--- gcc-3.3/gcc/f/config-lang.in	2002-08-22 02:20:42.000000000 +0000
***************
*** 1,5 ****
  # Top level configure fragment for GNU FORTRAN.
! #   Copyright (C) 1995, 1996, 1997, 2000, 2001 Free Software Foundation, Inc.
  
  #This file is part of GNU Fortran.
  
--- 1,5 ----
  # Top level configure fragment for GNU FORTRAN.
! #   Copyright (C) 1995, 1996, 1997, 2000, 2001, 2002 Free Software Foundation, Inc.
  
  #This file is part of GNU Fortran.
  
*************** compilers="f771\$(exeext)"
*** 32,34 ****
--- 32,36 ----
  stagestuff="g77\$(exeext) g77-cross\$(exeext) f771\$(exeext)"
  
  target_libs=target-libf2c
+ 
+ gtfiles="\$(srcdir)/f/com.c \$(srcdir)/f/com.h \$(srcdir)/f/ste.c \$(srcdir)/f/where.h \$(srcdir)/f/where.c \$(srcdir)/f/lex.c"
diff -Nrc3pad gcc-3.2.3/gcc/f/data.c gcc-3.3/gcc/f/data.c
*** gcc-3.2.3/gcc/f/data.c	2002-02-13 07:39:56.000000000 +0000
--- gcc-3.3/gcc/f/data.c	2003-04-11 19:29:10.000000000 +0000
***************
*** 1,5 ****
  /* data.c -- Implementation File (module.c template V1.0)
!    Copyright (C) 1995, 1996, 2002 Free Software Foundation, Inc.
     Contributed by James Craig Burley.
  
  This file is part of GNU Fortran.
--- 1,5 ----
  /* data.c -- Implementation File (module.c template V1.0)
!    Copyright (C) 1995, 1996, 2002, 2003 Free Software Foundation, Inc.
     Contributed by James Craig Burley.
  
  This file is part of GNU Fortran.
*************** tail_recurse:			/* :::::::::::::::::::: 
*** 591,603 ****
  	assert (ffeinfo_kindtype (ffebld_info (itervar))
  		== FFEINFO_kindtypeINTEGERDEFAULT);
  	ffedata_stack_->itervar = ffebld_symter (itervar);
! 
  	assert (ffeinfo_basictype (ffebld_info (start))
  		== FFEINFO_basictypeINTEGER);
  	assert (ffeinfo_kindtype (ffebld_info (start))
  		== FFEINFO_kindtypeINTEGERDEFAULT);
  	ffesymbol_set_value (ffedata_stack_->itervar, ffedata_eval_integer1_ (start));
! 
  	assert (ffeinfo_basictype (ffebld_info (end))
  		== FFEINFO_basictypeINTEGER);
  	assert (ffeinfo_kindtype (ffebld_info (end))
--- 591,619 ----
  	assert (ffeinfo_kindtype (ffebld_info (itervar))
  		== FFEINFO_kindtypeINTEGERDEFAULT);
  	ffedata_stack_->itervar = ffebld_symter (itervar);
! 	if (ffeinfo_basictype (ffebld_info (start)) != FFEINFO_basictypeINTEGER)
! 	  {
! 	    ffebad_start (FFEBAD_DATA_EVAL);
! 	    ffest_ffebad_here_current_stmt (0);
! 	    ffebad_finish ();
! 	    ffedata_pop_ ();
! 	    ffedata_reported_error_ = TRUE;
! 	    return FALSE;
! 	  }
  	assert (ffeinfo_basictype (ffebld_info (start))
  		== FFEINFO_basictypeINTEGER);
  	assert (ffeinfo_kindtype (ffebld_info (start))
  		== FFEINFO_kindtypeINTEGERDEFAULT);
  	ffesymbol_set_value (ffedata_stack_->itervar, ffedata_eval_integer1_ (start));
! 	if (ffeinfo_basictype (ffebld_info (end)) != FFEINFO_basictypeINTEGER)
! 	  {
! 	    ffebad_start (FFEBAD_DATA_EVAL);
! 	    ffest_ffebad_here_current_stmt (0);
! 	    ffebad_finish ();
! 	    ffedata_pop_ ();
! 	    ffedata_reported_error_ = TRUE;
! 	    return FALSE;
! 	  }
  	assert (ffeinfo_basictype (ffebld_info (end))
  		== FFEINFO_basictypeINTEGER);
  	assert (ffeinfo_kindtype (ffebld_info (end))
*************** tail_recurse:			/* :::::::::::::::::::: 
*** 608,613 ****
--- 624,638 ----
  	  ffedata_stack_->increment = 1;
  	else
  	  {
+ 	    if (ffeinfo_basictype (ffebld_info (incr)) != FFEINFO_basictypeINTEGER)
+ 	      {
+ 		ffebad_start (FFEBAD_DATA_EVAL);
+ 		ffest_ffebad_here_current_stmt (0);
+ 		ffebad_finish ();
+ 		ffedata_pop_ ();
+ 		ffedata_reported_error_ = TRUE;
+ 		return FALSE;
+ 	      }
  	    assert (ffeinfo_basictype (ffebld_info (incr))
  		    == FFEINFO_basictypeINTEGER);
  	    assert (ffeinfo_kindtype (ffebld_info (incr))
diff -Nrc3pad gcc-3.2.3/gcc/f/expr.c gcc-3.3/gcc/f/expr.c
*** gcc-3.2.3/gcc/f/expr.c	2002-02-04 15:58:50.000000000 +0000
--- gcc-3.3/gcc/f/expr.c	2002-05-28 17:33:01.000000000 +0000
*************** the Free Software Foundation, 59 Temple 
*** 48,53 ****
--- 48,54 ----
  #include "str.h"
  #include "target.h"
  #include "where.h"
+ #include "real.h"
  
  /* Externals defined here. */
  
*************** ffeexpr_reduced_ugly2log_ (ffebld reduce
*** 11501,11506 ****
--- 11502,11525 ----
        /* else Leave it alone. */
      }
  
+   if (lbt == FFEINFO_basictypeLOGICAL)
+   {
+ 	  ffebld_set_left (reduced, ffeexpr_convert (ffebld_left (reduced),
+ 				  l->token, op->token, FFEINFO_basictypeINTEGER,
+ 				  FFEINFO_kindtypeINTEGERDEFAULT, 0,
+ 				  FFETARGET_charactersizeNONE,
+ 				  FFEEXPR_contextLET));
+   }
+ 
+   if (rbt == FFEINFO_basictypeLOGICAL)
+   {
+ 	  ffebld_set_right (reduced, ffeexpr_convert (ffebld_right (reduced),
+ 				  r->token, op->token, FFEINFO_basictypeINTEGER,
+ 				  FFEINFO_kindtypeINTEGERDEFAULT, 0,
+ 				  FFETARGET_charactersizeNONE,
+ 				  FFEEXPR_contextLET));
+   }
+   
    return reduced;
  }
  
diff -Nrc3pad gcc-3.2.3/gcc/f/ffe.texi gcc-3.3/gcc/f/ffe.texi
*** gcc-3.2.3/gcc/f/ffe.texi	2002-02-01 22:43:03.000000000 +0000
--- gcc-3.3/gcc/f/ffe.texi	2003-03-26 01:43:07.000000000 +0000
*************** search for the string TBD.
*** 17,23 ****
  If you want to help by working on one or more of these items,
  email @email{gcc@@gcc.gnu.org}.
  If you're planning to do more than just research issues and offer comments,
! see @uref{http://www.gnu.org/software/contribute.html} for steps you might
  need to take first.
  
  @menu
--- 17,23 ----
  If you want to help by working on one or more of these items,
  email @email{gcc@@gcc.gnu.org}.
  If you're planning to do more than just research issues and offer comments,
! see @uref{http://gcc.gnu.org/contribute.html} for steps you might
  need to take first.
  
  @menu
*************** Initializes, usually a module.  No type.
*** 2028,2034 ****
  A generic integer of type @code{int}.
  
  @item is
! A generic integer that contains a true (non-zero) or false (zero) value.
  
  @item len
  A generic integer that contains the length of something.
--- 2028,2034 ----
  A generic integer of type @code{int}.
  
  @item is
! A generic integer that contains a true (nonzero) or false (zero) value.
  
  @item len
  A generic integer that contains the length of something.
diff -Nrc3pad gcc-3.2.3/gcc/f/g77.1 gcc-3.3/gcc/f/g77.1
*** gcc-3.2.3/gcc/f/g77.1	2003-04-22 07:07:36.000000000 +0000
--- gcc-3.3/gcc/f/g77.1	2003-05-14 00:32:08.000000000 +0000
***************
*** 1,8 ****
! .\" Automatically generated by Pod::Man version 1.15
! .\" Tue Apr 22 07:07:35 2003
  .\"
  .\" Standard preamble:
! .\" ======================================================================
  .de Sh \" Subsection heading
  .br
  .if t .Sp
--- 1,7 ----
! .\" Automatically generated by Pod::Man v1.34, Pod::Parser v1.13
  .\"
  .\" Standard preamble:
! .\" ========================================================================
  .de Sh \" Subsection heading
  .br
  .if t .Sp
***************
*** 15,26 ****
  .if t .sp .5v
  .if n .sp
  ..
- .de Ip \" List item
- .br
- .ie \\n(.$>=3 .ne \\$3
- .el .ne 3
- .IP "\\$1" \\$2
- ..
  .de Vb \" Begin verbatim text
  .ft CW
  .nf
--- 14,19 ----
***************
*** 28,42 ****
  ..
  .de Ve \" End verbatim text
  .ft R
- 
  .fi
  ..
  .\" Set up some character translations and predefined strings.  \*(-- will
  .\" give an unbreakable dash, \*(PI will give pi, \*(L" will give a left
  .\" double quote, and \*(R" will give a right double quote.  | will give a
! .\" real vertical bar.  \*(C+ will give a nicer C++.  Capital omega is used
! .\" to do unbreakable dashes and therefore won't be available.  \*(C` and
! .\" \*(C' expand to `' in nroff, nothing in troff, for use with C<>
  .tr \(*W-|\(bv\*(Tr
  .ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p'
  .ie n \{\
--- 21,34 ----
  ..
  .de Ve \" End verbatim text
  .ft R
  .fi
  ..
  .\" Set up some character translations and predefined strings.  \*(-- will
  .\" give an unbreakable dash, \*(PI will give pi, \*(L" will give a left
  .\" double quote, and \*(R" will give a right double quote.  | will give a
! .\" real vertical bar.  \*(C+ will give a nicer C++.  Capital omega is used to
! .\" do unbreakable dashes and therefore won't be available.  \*(C` and \*(C'
! .\" expand to `' in nroff, nothing in troff, for use with C<>.
  .tr \(*W-|\(bv\*(Tr
  .ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p'
  .ie n \{\
***************
*** 56,65 ****
  .    ds R" ''
  'br\}
  .\"
! .\" If the F register is turned on, we'll generate index entries on stderr
! .\" for titles (.TH), headers (.SH), subsections (.Sh), items (.Ip), and
! .\" index entries marked with X<> in POD.  Of course, you'll have to process
! .\" the output yourself in some meaningful fashion.
  .if \nF \{\
  .    de IX
  .    tm Index:\\$1\t\\n%\t"\\$2"
--- 48,57 ----
  .    ds R" ''
  'br\}
  .\"
! .\" If the F register is turned on, we'll generate index entries on stderr for
! .\" titles (.TH), headers (.SH), subsections (.Sh), items (.Ip), and index
! .\" entries marked with X<> in POD.  Of course, you'll have to process the
! .\" output yourself in some meaningful fashion.
  .if \nF \{\
  .    de IX
  .    tm Index:\\$1\t\\n%\t"\\$2"
***************
*** 68,81 ****
  .    rr F
  .\}
  .\"
! .\" For nroff, turn off justification.  Always turn off hyphenation; it
! .\" makes way too many mistakes in technical documents.
  .hy 0
  .if n .na
  .\"
  .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
  .\" Fear.  Run.  Save yourself.  No user-serviceable parts.
- .bd B 3
  .    \" fudge factors for nroff and troff
  .if n \{\
  .    ds #H 0
--- 60,72 ----
  .    rr F
  .\}
  .\"
! .\" For nroff, turn off justification.  Always turn off hyphenation; it makes
! .\" way too many mistakes in technical documents.
  .hy 0
  .if n .na
  .\"
  .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
  .\" Fear.  Run.  Save yourself.  No user-serviceable parts.
  .    \" fudge factors for nroff and troff
  .if n \{\
  .    ds #H 0
***************
*** 135,147 ****
  .    ds Ae AE
  .\}
  .rm #[ #] #H #V #F C
! .\" ======================================================================
  .\"
  .IX Title "G77 1"
! .TH G77 1 "gcc-3.2.3" "2003-04-22" "GNU"
! .UC
  .SH "NAME"
! g77 \- \s-1GNU\s0 project Fortran 77 compiler
  .SH "SYNOPSIS"
  .IX Header "SYNOPSIS"
  g77 [\fB\-c\fR|\fB\-S\fR|\fB\-E\fR]
--- 126,137 ----
  .    ds Ae AE
  .\}
  .rm #[ #] #H #V #F C
! .\" ========================================================================
  .\"
  .IX Title "G77 1"
! .TH G77 1 "2003-05-14" "gcc-3.3" "GNU"
  .SH "NAME"
! g77 \- GNU project Fortran 77 compiler
  .SH "SYNOPSIS"
  .IX Header "SYNOPSIS"
  g77 [\fB\-c\fR|\fB\-S\fR|\fB\-E\fR]
*************** enables acceptance of \fBg77\fR options
*** 168,253 ****
  by all of the relevant drivers.
  .PP
  In some cases, options have positive and negative forms;
! the negative form of \fB\-ffoo\fR would be \fB\-fno-foo\fR.
  This manual documents only one of these two forms, whichever
  one is not the default.
  .SH "OPTIONS"
  .IX Header "OPTIONS"
  Here is a summary of all the options specific to \s-1GNU\s0 Fortran, grouped
  by type.  Explanations are in the following sections.
! .Ip "\fIOverall Options\fR" 4
  .IX Item "Overall Options"
! \&\fB\-fversion  \-fset-g77\-defaults  \-fno-silent\fR
! .Ip "\fIShorthand Options\fR" 4
  .IX Item "Shorthand Options"
! \&\fB\-ff66  \-fno-f66  \-ff77  \-fno-f77  \-fno-ugly\fR
! .Ip "\fIFortran Language Options\fR" 4
  .IX Item "Fortran Language Options"
! \&\fB\-ffree-form  \-fno-fixed-form  \-ff90 
! \&\-fvxt  \-fdollar-ok  \-fno-backslash 
! \&\-fno-ugly-args  \-fno-ugly-assign  \-fno-ugly-assumed 
! \&\-fugly-comma  \-fugly-complex  \-fugly-init  \-fugly-logint 
! \&\-fonetrip  \-ftypeless-boz 
! \&\-fintrin-case-initcap  \-fintrin-case-upper 
! \&\-fintrin-case-lower  \-fintrin-case-any 
! \&\-fmatch-case-initcap  \-fmatch-case-upper 
! \&\-fmatch-case-lower  \-fmatch-case-any 
! \&\-fsource-case-upper  \-fsource-case-lower 
! \&\-fsource-case-preserve 
! \&\-fsymbol-case-initcap  \-fsymbol-case-upper 
! \&\-fsymbol-case-lower  \-fsymbol-case-any 
! \&\-fcase-strict-upper  \-fcase-strict-lower 
! \&\-fcase-initcap  \-fcase-upper  \-fcase-lower  \-fcase-preserve 
! \&\-ff2c-intrinsics-delete  \-ff2c-intrinsics-hide 
! \&\-ff2c-intrinsics-disable  \-ff2c-intrinsics-enable 
! \&\-fbadu77\-intrinsics-delete  \-fbadu77\-intrinsics-hide 
! \&\-fbadu77\-intrinsics-disable  \-fbadu77\-intrinsics-enable 
! \&\-ff90\-intrinsics-delete  \-ff90\-intrinsics-hide 
! \&\-ff90\-intrinsics-disable  \-ff90\-intrinsics-enable 
! \&\-fgnu-intrinsics-delete  \-fgnu-intrinsics-hide 
! \&\-fgnu-intrinsics-disable  \-fgnu-intrinsics-enable 
! \&\-fmil-intrinsics-delete  \-fmil-intrinsics-hide 
! \&\-fmil-intrinsics-disable  \-fmil-intrinsics-enable 
! \&\-funix-intrinsics-delete  \-funix-intrinsics-hide 
! \&\-funix-intrinsics-disable  \-funix-intrinsics-enable 
! \&\-fvxt-intrinsics-delete  \-fvxt-intrinsics-hide 
! \&\-fvxt-intrinsics-disable  \-fvxt-intrinsics-enable 
! \&\-ffixed-line-length-\fR\fIn\fR  \fB\-ffixed-line-length-none\fR
! .Ip "\fIWarning Options\fR" 4
  .IX Item "Warning Options"
! \&\fB\-fsyntax-only  \-pedantic  \-pedantic-errors  \-fpedantic 
! \&\-w  \-Wno-globals  \-Wimplicit  \-Wunused  \-Wuninitialized 
  \&\-Wall  \-Wsurprising 
  \&\-Werror  \-W\fR
! .Ip "\fIDebugging Options\fR" 4
  .IX Item "Debugging Options"
  \&\fB\-g\fR
! .Ip "\fIOptimization Options\fR" 4
  .IX Item "Optimization Options"
! \&\fB\-malign-double 
! \&\-ffloat-store  \-fforce-mem  \-fforce-addr  \-fno-inline 
! \&\-ffast-math  \-fstrength-reduce  \-frerun-cse-after-loop 
! \&\-funsafe-math-optimizations \-fno-trapping-math 
! \&\-fexpensive-optimizations  \-fdelayed-branch 
! \&\-fschedule-insns  \-fschedule-insn2  \-fcaller-saves 
! \&\-funroll-loops  \-funroll-all-loops 
! \&\-fno-move-all-movables  \-fno-reduce-all-givs 
! \&\-fno-rerun-loop-opt\fR
! .Ip "\fIDirectory Options\fR" 4
  .IX Item "Directory Options"
! \&\fB\-I\fR\fIdir\fR  \fB\-I-\fR
! .Ip "\fICode Generation Options\fR" 4
  .IX Item "Code Generation Options"
! \&\fB\-fno-automatic  \-finit-local-zero  \-fno-f2c 
! \&\-ff2c-library  \-fno-underscoring  \-fno-ident 
! \&\-fpcc-struct-return  \-freg-struct-return 
! \&\-fshort-double  \-fno-common  \-fpack-struct 
! \&\-fzeros  \-fno-second-underscore 
! \&\-femulate-complex 
! \&\-falias-check  \-fargument-alias 
! \&\-fargument-noalias  \-fno-argument-noalias-global 
! \&\-fno-globals  \-fflatten-arrays 
! \&\-fbounds-check  \-ffortran-bounds-check\fR
  .PP
  Compilation can involve as many as four stages: preprocessing, code
  generation (often what is really meant by the term ``compilation''),
--- 158,243 ----
  by all of the relevant drivers.
  .PP
  In some cases, options have positive and negative forms;
! the negative form of \fB\-ffoo\fR would be \fB\-fno\-foo\fR.
  This manual documents only one of these two forms, whichever
  one is not the default.
  .SH "OPTIONS"
  .IX Header "OPTIONS"
  Here is a summary of all the options specific to \s-1GNU\s0 Fortran, grouped
  by type.  Explanations are in the following sections.
! .IP "\fIOverall Options\fR" 4
  .IX Item "Overall Options"
! \&\fB\-fversion  \-fset\-g77\-defaults  \-fno\-silent\fR
! .IP "\fIShorthand Options\fR" 4
  .IX Item "Shorthand Options"
! \&\fB\-ff66  \-fno\-f66  \-ff77  \-fno\-f77  \-fno\-ugly\fR
! .IP "\fIFortran Language Options\fR" 4
  .IX Item "Fortran Language Options"
! \&\fB\-ffree\-form  \-fno\-fixed\-form  \-ff90 
! \&\-fvxt  \-fdollar\-ok  \-fno\-backslash 
! \&\-fno\-ugly\-args  \-fno\-ugly\-assign  \-fno\-ugly\-assumed 
! \&\-fugly\-comma  \-fugly\-complex  \-fugly\-init  \-fugly\-logint 
! \&\-fonetrip  \-ftypeless\-boz 
! \&\-fintrin\-case\-initcap  \-fintrin\-case\-upper 
! \&\-fintrin\-case\-lower  \-fintrin\-case\-any 
! \&\-fmatch\-case\-initcap  \-fmatch\-case\-upper 
! \&\-fmatch\-case\-lower  \-fmatch\-case\-any 
! \&\-fsource\-case\-upper  \-fsource\-case\-lower 
! \&\-fsource\-case\-preserve 
! \&\-fsymbol\-case\-initcap  \-fsymbol\-case\-upper 
! \&\-fsymbol\-case\-lower  \-fsymbol\-case\-any 
! \&\-fcase\-strict\-upper  \-fcase\-strict\-lower 
! \&\-fcase\-initcap  \-fcase\-upper  \-fcase\-lower  \-fcase\-preserve 
! \&\-ff2c\-intrinsics\-delete  \-ff2c\-intrinsics\-hide 
! \&\-ff2c\-intrinsics\-disable  \-ff2c\-intrinsics\-enable 
! \&\-fbadu77\-intrinsics\-delete  \-fbadu77\-intrinsics\-hide 
! \&\-fbadu77\-intrinsics\-disable  \-fbadu77\-intrinsics\-enable 
! \&\-ff90\-intrinsics\-delete  \-ff90\-intrinsics\-hide 
! \&\-ff90\-intrinsics\-disable  \-ff90\-intrinsics\-enable 
! \&\-fgnu\-intrinsics\-delete  \-fgnu\-intrinsics\-hide 
! \&\-fgnu\-intrinsics\-disable  \-fgnu\-intrinsics\-enable 
! \&\-fmil\-intrinsics\-delete  \-fmil\-intrinsics\-hide 
! \&\-fmil\-intrinsics\-disable  \-fmil\-intrinsics\-enable 
! \&\-funix\-intrinsics\-delete  \-funix\-intrinsics\-hide 
! \&\-funix\-intrinsics\-disable  \-funix\-intrinsics\-enable 
! \&\-fvxt\-intrinsics\-delete  \-fvxt\-intrinsics\-hide 
! \&\-fvxt\-intrinsics\-disable  \-fvxt\-intrinsics\-enable 
! \&\-ffixed\-line\-length\-\fR\fIn\fR  \fB\-ffixed\-line\-length\-none\fR
! .IP "\fIWarning Options\fR" 4
  .IX Item "Warning Options"
! \&\fB\-fsyntax\-only  \-pedantic  \-pedantic\-errors  \-fpedantic 
! \&\-w  \-Wno\-globals  \-Wimplicit  \-Wunused  \-Wuninitialized 
  \&\-Wall  \-Wsurprising 
  \&\-Werror  \-W\fR
! .IP "\fIDebugging Options\fR" 4
  .IX Item "Debugging Options"
  \&\fB\-g\fR
! .IP "\fIOptimization Options\fR" 4
  .IX Item "Optimization Options"
! \&\fB\-malign\-double 
! \&\-ffloat\-store  \-fforce\-mem  \-fforce\-addr  \-fno\-inline 
! \&\-ffast\-math  \-fstrength\-reduce  \-frerun\-cse\-after\-loop 
! \&\-funsafe\-math\-optimizations \-ffinite\-math\-only \-fno\-trapping\-math 
! \&\-fexpensive\-optimizations  \-fdelayed\-branch 
! \&\-fschedule\-insns  \-fschedule\-insn2  \-fcaller\-saves 
! \&\-funroll\-loops  \-funroll\-all\-loops 
! \&\-fno\-move\-all\-movables  \-fno\-reduce\-all\-givs 
! \&\-fno\-rerun\-loop\-opt\fR
! .IP "\fIDirectory Options\fR" 4
  .IX Item "Directory Options"
! \&\fB\-I\fR\fIdir\fR  \fB\-I\-\fR
! .IP "\fICode Generation Options\fR" 4
  .IX Item "Code Generation Options"
! \&\fB\-fno\-automatic  \-finit\-local\-zero  \-fno\-f2c 
! \&\-ff2c\-library  \-fno\-underscoring  \-fno\-ident 
! \&\-fpcc\-struct\-return  \-freg\-struct\-return 
! \&\-fshort\-double  \-fno\-common  \-fpack\-struct 
! \&\-fzeros  \-fno\-second\-underscore 
! \&\-femulate\-complex 
! \&\-falias\-check  \-fargument\-alias 
! \&\-fargument\-noalias  \-fno\-argument\-noalias\-global 
! \&\-fno\-globals  \-fflatten\-arrays 
! \&\-fbounds\-check  \-ffortran\-bounds\-check\fR
  .PP
  Compilation can involve as many as four stages: preprocessing, code
  generation (often what is really meant by the term ``compilation''),
*************** For any given input file, the file name 
*** 260,271 ****
  program is contained in the file\-\-\-that is, the language in which the
  program is written is generally indicated by the suffix.
  Suffixes specific to \s-1GNU\s0 Fortran are listed below.
! .Ip "\fIfile\fR\fB.f\fR" 4
  .IX Item "file.f"
  .PD 0
! .Ip "\fIfile\fR\fB.for\fR" 4
  .IX Item "file.for"
! .Ip "\fIfile\fR\fB.FOR\fR" 4
  .IX Item "file.FOR"
  .PD
  Fortran source code that should not be preprocessed.
--- 250,261 ----
  program is contained in the file\-\-\-that is, the language in which the
  program is written is generally indicated by the suffix.
  Suffixes specific to \s-1GNU\s0 Fortran are listed below.
! .IP "\fIfile\fR\fB.f\fR" 4
  .IX Item "file.f"
  .PD 0
! .IP "\fIfile\fR\fB.for\fR" 4
  .IX Item "file.for"
! .IP "\fIfile\fR\fB.FOR\fR" 4
  .IX Item "file.FOR"
  .PD
  Fortran source code that should not be preprocessed.
*************** Such source code cannot contain any prep
*** 274,286 ****
  as \f(CW\*(C`#include\*(C'\fR, \f(CW\*(C`#define\*(C'\fR, \f(CW\*(C`#if\*(C'\fR, and so on.
  .Sp
  You can force \fB.f\fR files to be preprocessed by \fBcpp\fR by using
! \&\fB\-x f77\-cpp-input\fR.
! .Ip "\fIfile\fR\fB.F\fR" 4
  .IX Item "file.F"
  .PD 0
! .Ip "\fIfile\fR\fB.fpp\fR" 4
  .IX Item "file.fpp"
! .Ip "\fIfile\fR\fB.FPP\fR" 4
  .IX Item "file.FPP"
  .PD
  Fortran source code that must be preprocessed (by the C preprocessor
--- 264,276 ----
  as \f(CW\*(C`#include\*(C'\fR, \f(CW\*(C`#define\*(C'\fR, \f(CW\*(C`#if\*(C'\fR, and so on.
  .Sp
  You can force \fB.f\fR files to be preprocessed by \fBcpp\fR by using
! \&\fB\-x f77\-cpp\-input\fR.
! .IP "\fIfile\fR\fB.F\fR" 4
  .IX Item "file.F"
  .PD 0
! .IP "\fIfile\fR\fB.fpp\fR" 4
  .IX Item "file.fpp"
! .IP "\fIfile\fR\fB.FPP\fR" 4
  .IX Item "file.FPP"
  .PD
  Fortran source code that must be preprocessed (by the C preprocessor
*************** Fortran source code that must be preproc
*** 289,295 ****
  Note that preprocessing is not extended to the contents of
  files included by the \f(CW\*(C`INCLUDE\*(C'\fR directive\-\-\-the \f(CW\*(C`#include\*(C'\fR
  preprocessor directive must be used instead.
! .Ip "\fIfile\fR\fB.r\fR" 4
  .IX Item "file.r"
  Ratfor source code, which must be preprocessed by the \fBratfor\fR
  command, which is available separately (as it is not yet part of the \s-1GNU\s0
--- 279,285 ----
  Note that preprocessing is not extended to the contents of
  files included by the \f(CW\*(C`INCLUDE\*(C'\fR directive\-\-\-the \f(CW\*(C`#include\*(C'\fR
  preprocessor directive must be used instead.
! .IP "\fIfile\fR\fB.r\fR" 4
  .IX Item "file.r"
  Ratfor source code, which must be preprocessed by the \fBratfor\fR
  command, which is available separately (as it is not yet part of the \s-1GNU\s0
*************** distinguish upper-case
*** 306,312 ****
  letters from lower-case letters in their file names, typically use
  the \fI\fIfile\fI.for\fR and \fI\fIfile\fI.fpp\fR nomenclature.
  .PP
! Use of the preprocessor \fBcpp\fR allows use of C-like
  constructs such as \f(CW\*(C`#define\*(C'\fR and \f(CW\*(C`#include\*(C'\fR, but can
  lead to unexpected, even mistaken, results due to Fortran's source file
  format.
--- 296,302 ----
  letters from lower-case letters in their file names, typically use
  the \fI\fIfile\fI.for\fR and \fI\fIfile\fI.fpp\fR nomenclature.
  .PP
! Use of the preprocessor \fBcpp\fR allows use of C\-like
  constructs such as \f(CW\*(C`#define\*(C'\fR and \f(CW\*(C`#include\*(C'\fR, but can
  lead to unexpected, even mistaken, results due to Fortran's source file
  format.
*************** anything that \fBcpp\fR sees as an unter
*** 355,376 ****
  \&        C Some Fortran compilers accept /* as starting
  \&        C an inline comment.
  .Ve
  The following options that affect overall processing are recognized
  by the \fBg77\fR and \fBgcc\fR commands in a \s-1GNU\s0 Fortran installation:
! .Ip "\fB\-fversion\fR" 4
  .IX Item "-fversion"
  Ensure that the \fBg77\fR version of the compiler phase is reported,
  if run,
  and, starting in \f(CW\*(C`egcs\*(C'\fR version 1.1,
  that internal consistency checks in the \fIf771\fR program are run.
  .Sp
! This option is supplied automatically when \fB\-v\fR or \fB\*(--verbose\fR
  is specified as a command-line option for \fBg77\fR or \fBgcc\fR
  and when the resulting commands compile Fortran source files.
  .Sp
! In \s-1GCC\s0 3.1, this is changed back to the behaviour \fBgcc\fR displays
  for \fB.c\fR files.
! .Ip "\fB\-fset-g77\-defaults\fR" 4
  .IX Item "-fset-g77-defaults"
  \&\fIVersion info:\fR
  This option was obsolete as of \f(CW\*(C`egcs\*(C'\fR
--- 345,367 ----
  \&        C Some Fortran compilers accept /* as starting
  \&        C an inline comment.
  .Ve
+ .PP
  The following options that affect overall processing are recognized
  by the \fBg77\fR and \fBgcc\fR commands in a \s-1GNU\s0 Fortran installation:
! .IP "\fB\-fversion\fR" 4
  .IX Item "-fversion"
  Ensure that the \fBg77\fR version of the compiler phase is reported,
  if run,
  and, starting in \f(CW\*(C`egcs\*(C'\fR version 1.1,
  that internal consistency checks in the \fIf771\fR program are run.
  .Sp
! This option is supplied automatically when \fB\-v\fR or \fB\-\-verbose\fR
  is specified as a command-line option for \fBg77\fR or \fBgcc\fR
  and when the resulting commands compile Fortran source files.
  .Sp
! In \s-1GCC\s0 3.1, this is changed back to the behavior \fBgcc\fR displays
  for \fB.c\fR files.
! .IP "\fB\-fset\-g77\-defaults\fR" 4
  .IX Item "-fset-g77-defaults"
  \&\fIVersion info:\fR
  This option was obsolete as of \f(CW\*(C`egcs\*(C'\fR
*************** executable, invoke it without this optio
*** 397,405 ****
  e.g. via \f(CW\*(C`./f771 \-quiet < /dev/null\*(C'\fR,
  to ensure that they have not introduced any
  internal inconsistencies (such as in the table of
! intrinsics) before proceeding\-\--\fBg77\fR will crash
  with a diagnostic if it detects an inconsistency.
! .Ip "\fB\-fno-silent\fR" 4
  .IX Item "-fno-silent"
  Print (to \f(CW\*(C`stderr\*(C'\fR) the names of the program units as
  they are compiled, in a form similar to that used by popular
--- 388,396 ----
  e.g. via \f(CW\*(C`./f771 \-quiet < /dev/null\*(C'\fR,
  to ensure that they have not introduced any
  internal inconsistencies (such as in the table of
! intrinsics) before proceeding\-\-\-\fBg77\fR will crash
  with a diagnostic if it detects an inconsistency.
! .IP "\fB\-fno\-silent\fR" 4
  .IX Item "-fno-silent"
  Print (to \f(CW\*(C`stderr\*(C'\fR) the names of the program units as
  they are compiled, in a form similar to that used by popular
*************** they are compiled, in a form similar to 
*** 408,414 ****
  .IX Subsection "Shorthand Options"
  The following options serve as ``shorthand''
  for other options accepted by the compiler:
! .Ip "\fB\-fugly\fR" 4
  .IX Item "-fugly"
  \&\fINote:\fR This option is no longer supported.
  The information, below, is provided to aid
--- 399,405 ----
  .IX Subsection "Shorthand Options"
  The following options serve as ``shorthand''
  for other options accepted by the compiler:
! .IP "\fB\-fugly\fR" 4
  .IX Item "-fugly"
  \&\fINote:\fR This option is no longer supported.
  The information, below, is provided to aid
*************** Same as:
*** 422,431 ****
  \&        -fugly-comma -fugly-complex -fugly-init
  \&        -fugly-logint
  .Ve
  These constructs are considered inappropriate to use in new
  or well-maintained portable Fortran code, but widely used
  in old code.
! .Ip "\fB\-fno-ugly\fR" 4
  .IX Item "-fno-ugly"
  Specify that all ``ugly'' constructs are to be noisily rejected.
  Same as:
--- 413,423 ----
  \&        -fugly-comma -fugly-complex -fugly-init
  \&        -fugly-logint
  .Ve
+ .Sp
  These constructs are considered inappropriate to use in new
  or well-maintained portable Fortran code, but widely used
  in old code.
! .IP "\fB\-fno\-ugly\fR" 4
  .IX Item "-fno-ugly"
  Specify that all ``ugly'' constructs are to be noisily rejected.
  Same as:
*************** Same as:
*** 435,467 ****
  \&        -fno-ugly-comma -fno-ugly-complex -fno-ugly-init
  \&        -fno-ugly-logint
  .Ve
! .Ip "\fB\-ff66\fR" 4
  .IX Item "-ff66"
  Specify that the program is written in idiomatic \s-1FORTRAN\s0 66.
! Same as \fB\-fonetrip \-fugly-assumed\fR.
  .Sp
! The \fB\-fno-f66\fR option is the inverse of \fB\-ff66\fR.
! As such, it is the same as \fB\-fno-onetrip \-fno-ugly-assumed\fR.
  .Sp
  The meaning of this option is likely to be refined as future
  versions of \fBg77\fR provide more compatibility with other
  existing and obsolete Fortran implementations.
! .Ip "\fB\-ff77\fR" 4
  .IX Item "-ff77"
  Specify that the program is written in idiomatic \s-1UNIX\s0 \s-1FORTRAN\s0 77
  and/or the dialect accepted by the \fBf2c\fR product.
! Same as \fB\-fbackslash \-fno-typeless-boz\fR.
  .Sp
  The meaning of this option is likely to be refined as future
  versions of \fBg77\fR provide more compatibility with other
  existing and obsolete Fortran implementations.
! .Ip "\fB\-fno-f77\fR" 4
  .IX Item "-fno-f77"
! The \fB\-fno-f77\fR option is \fInot\fR the inverse
  of \fB\-ff77\fR.
  It specifies that the program is not written in idiomatic \s-1UNIX\s0
  \&\s-1FORTRAN\s0 77 or \fBf2c\fR but in a more widely portable dialect.
! \&\fB\-fno-f77\fR is the same as \fB\-fno-backslash\fR.
  .Sp
  The meaning of this option is likely to be refined as future
  versions of \fBg77\fR provide more compatibility with other
--- 427,459 ----
  \&        -fno-ugly-comma -fno-ugly-complex -fno-ugly-init
  \&        -fno-ugly-logint
  .Ve
! .IP "\fB\-ff66\fR" 4
  .IX Item "-ff66"
  Specify that the program is written in idiomatic \s-1FORTRAN\s0 66.
! Same as \fB\-fonetrip \-fugly\-assumed\fR.
  .Sp
! The \fB\-fno\-f66\fR option is the inverse of \fB\-ff66\fR.
! As such, it is the same as \fB\-fno\-onetrip \-fno\-ugly\-assumed\fR.
  .Sp
  The meaning of this option is likely to be refined as future
  versions of \fBg77\fR provide more compatibility with other
  existing and obsolete Fortran implementations.
! .IP "\fB\-ff77\fR" 4
  .IX Item "-ff77"
  Specify that the program is written in idiomatic \s-1UNIX\s0 \s-1FORTRAN\s0 77
  and/or the dialect accepted by the \fBf2c\fR product.
! Same as \fB\-fbackslash \-fno\-typeless\-boz\fR.
  .Sp
  The meaning of this option is likely to be refined as future
  versions of \fBg77\fR provide more compatibility with other
  existing and obsolete Fortran implementations.
! .IP "\fB\-fno\-f77\fR" 4
  .IX Item "-fno-f77"
! The \fB\-fno\-f77\fR option is \fInot\fR the inverse
  of \fB\-ff77\fR.
  It specifies that the program is not written in idiomatic \s-1UNIX\s0
  \&\s-1FORTRAN\s0 77 or \fBf2c\fR but in a more widely portable dialect.
! \&\fB\-fno\-f77\fR is the same as \fB\-fno\-backslash\fR.
  .Sp
  The meaning of this option is likely to be refined as future
  versions of \fBg77\fR provide more compatibility with other
*************** existing and obsolete Fortran implementa
*** 470,514 ****
  .IX Subsection "Options Controlling Fortran Dialect"
  The following options control the dialect of Fortran
  that the compiler accepts:
! .Ip "\fB\-ffree-form\fR" 4
  .IX Item "-ffree-form"
  .PD 0
! .Ip "\fB\-fno-fixed-form\fR" 4
  .IX Item "-fno-fixed-form"
  .PD
  Specify that the source file is written in free form
  (introduced in Fortran 90) instead of the more-traditional fixed form.
! .Ip "\fB\-ff90\fR" 4
  .IX Item "-ff90"
! Allow certain Fortran-90 constructs.
  .Sp
  This option controls whether certain
  Fortran 90 constructs are recognized.
  (Other Fortran 90 constructs
  might or might not be recognized depending on other options such as
! \&\fB\-fvxt\fR, \fB\-ff90\-intrinsics-enable\fR, and the
  current level of support for Fortran 90.)
! .Ip "\fB\-fvxt\fR" 4
  .IX Item "-fvxt"
  Specify the treatment of certain constructs that have different
  meanings depending on whether the code is written in
  \&\s-1GNU\s0 Fortran (based on \s-1FORTRAN\s0 77 and akin to Fortran 90)
  or \s-1VXT\s0 Fortran (more like \s-1VAX\s0 \s-1FORTRAN\s0).
  .Sp
! The default is \fB\-fno-vxt\fR.
  \&\fB\-fvxt\fR specifies that the \s-1VXT\s0 Fortran interpretations
  for those constructs are to be chosen.
! .Ip "\fB\-fdollar-ok\fR" 4
  .IX Item "-fdollar-ok"
  Allow \fB$\fR as a valid character in a symbol name.
! .Ip "\fB\-fno-backslash\fR" 4
  .IX Item "-fno-backslash"
  Specify that \fB\e\fR is not to be specially interpreted in character
  and Hollerith constants a la C and many \s-1UNIX\s0 Fortran compilers.
  .Sp
  For example, with \fB\-fbackslash\fR in effect, \fBA\enB\fR specifies
  three characters, with the second one being newline.
! With \fB\-fno-backslash\fR, it specifies four characters,
  \&\fBA\fR, \fB\e\fR, \fBn\fR, and \fBB\fR.
  .Sp
  Note that \fBg77\fR implements a fairly general form of backslash
--- 462,506 ----
  .IX Subsection "Options Controlling Fortran Dialect"
  The following options control the dialect of Fortran
  that the compiler accepts:
! .IP "\fB\-ffree\-form\fR" 4
  .IX Item "-ffree-form"
  .PD 0
! .IP "\fB\-fno\-fixed\-form\fR" 4
  .IX Item "-fno-fixed-form"
  .PD
  Specify that the source file is written in free form
  (introduced in Fortran 90) instead of the more-traditional fixed form.
! .IP "\fB\-ff90\fR" 4
  .IX Item "-ff90"
! Allow certain Fortran\-90 constructs.
  .Sp
  This option controls whether certain
  Fortran 90 constructs are recognized.
  (Other Fortran 90 constructs
  might or might not be recognized depending on other options such as
! \&\fB\-fvxt\fR, \fB\-ff90\-intrinsics\-enable\fR, and the
  current level of support for Fortran 90.)
! .IP "\fB\-fvxt\fR" 4
  .IX Item "-fvxt"
  Specify the treatment of certain constructs that have different
  meanings depending on whether the code is written in
  \&\s-1GNU\s0 Fortran (based on \s-1FORTRAN\s0 77 and akin to Fortran 90)
  or \s-1VXT\s0 Fortran (more like \s-1VAX\s0 \s-1FORTRAN\s0).
  .Sp
! The default is \fB\-fno\-vxt\fR.
  \&\fB\-fvxt\fR specifies that the \s-1VXT\s0 Fortran interpretations
  for those constructs are to be chosen.
! .IP "\fB\-fdollar\-ok\fR" 4
  .IX Item "-fdollar-ok"
  Allow \fB$\fR as a valid character in a symbol name.
! .IP "\fB\-fno\-backslash\fR" 4
  .IX Item "-fno-backslash"
  Specify that \fB\e\fR is not to be specially interpreted in character
  and Hollerith constants a la C and many \s-1UNIX\s0 Fortran compilers.
  .Sp
  For example, with \fB\-fbackslash\fR in effect, \fBA\enB\fR specifies
  three characters, with the second one being newline.
! With \fB\-fno\-backslash\fR, it specifies four characters,
  \&\fBA\fR, \fB\e\fR, \fBn\fR, and \fBB\fR.
  .Sp
  Note that \fBg77\fR implements a fairly general form of backslash
*************** For example, \fB'A\e003B'\fR is a three-
*** 518,534 ****
  whereas other compilers that support backslash might not support
  the three-octal-digit form, and thus treat that string as longer
  than three characters.
! .Ip "\fB\-fno-ugly-args\fR" 4
  .IX Item "-fno-ugly-args"
  Disallow passing Hollerith and typeless constants as actual
! arguments (for example, \fB\s-1CALL\s0 FOO(4HABCD)\fR).
! .Ip "\fB\-fugly-assign\fR" 4
  .IX Item "-fugly-assign"
  Use the same storage for a given variable regardless of
  whether it is used to hold an assigned-statement label
  (as in \fB\s-1ASSIGN\s0 10 \s-1TO\s0 I\fR) or used to hold numeric data
  (as in \fBI = 3\fR).
! .Ip "\fB\-fugly-assumed\fR" 4
  .IX Item "-fugly-assumed"
  Assume any dummy array with a final dimension specified as \fB1\fR
  is really an assumed-size array, as if \fB*\fR had been specified
--- 510,526 ----
  whereas other compilers that support backslash might not support
  the three-octal-digit form, and thus treat that string as longer
  than three characters.
! .IP "\fB\-fno\-ugly\-args\fR" 4
  .IX Item "-fno-ugly-args"
  Disallow passing Hollerith and typeless constants as actual
! arguments (for example, \fB\s-1CALL\s0 \s-1FOO\s0(4HABCD)\fR).
! .IP "\fB\-fugly\-assign\fR" 4
  .IX Item "-fugly-assign"
  Use the same storage for a given variable regardless of
  whether it is used to hold an assigned-statement label
  (as in \fB\s-1ASSIGN\s0 10 \s-1TO\s0 I\fR) or used to hold numeric data
  (as in \fBI = 3\fR).
! .IP "\fB\-fugly\-assumed\fR" 4
  .IX Item "-fugly-assumed"
  Assume any dummy array with a final dimension specified as \fB1\fR
  is really an assumed-size array, as if \fB*\fR had been specified
*************** for the final dimension instead of \fB1\
*** 536,542 ****
  .Sp
  For example, \fB\s-1DIMENSION\s0 X(1)\fR is treated as if it
  had read \fB\s-1DIMENSION\s0 X(*)\fR.
! .Ip "\fB\-fugly-comma\fR" 4
  .IX Item "-fugly-comma"
  In an external-procedure invocation,
  treat a trailing comma in the argument list
--- 528,534 ----
  .Sp
  For example, \fB\s-1DIMENSION\s0 X(1)\fR is treated as if it
  had read \fB\s-1DIMENSION\s0 X(*)\fR.
! .IP "\fB\-fugly\-comma\fR" 4
  .IX Item "-fugly-comma"
  In an external-procedure invocation,
  treat a trailing comma in the argument list
*************** as specification of a trailing null argu
*** 544,570 ****
  and treat an empty argument list
  as specification of a single null argument.
  .Sp
! For example, \fB\s-1CALL\s0 \f(BIFOO\fB\|(,)\fR is treated as
! \&\fB\s-1CALL\s0 FOO(%\f(BIVAL\fB\|(0), %\f(BIVAL\fB\|(0))\fR.
  That is, \fItwo\fR null arguments are specified
! by the procedure call when \fB\-fugly-comma\fR is in force.
! And \fBF = \f(BIFUNC()\fB\fR is treated as \fBF = FUNC(%\f(BIVAL\fB\|(0))\fR.
  .Sp
! The default behavior, \fB\-fno-ugly-comma\fR, is to ignore
  a single trailing comma in an argument list.
! So, by default, \fB\s-1CALL\s0 FOO(X,)\fR is treated
! exactly the same as \fB\s-1CALL\s0 \f(BIFOO\fB\|(X)\fR.
! .Ip "\fB\-fugly-complex\fR" 4
  .IX Item "-fugly-complex"
! Do not complain about \fBREAL(\fR\fIexpr\fR\fB)\fR or
! \&\fBAIMAG(\fR\fIexpr\fR\fB)\fR when \fIexpr\fR is a \f(CW\*(C`COMPLEX\*(C'\fR
  type other than \f(CW\*(C`COMPLEX(KIND=1)\*(C'\fR\-\-\-usually
  this is used to permit \f(CW\*(C`COMPLEX(KIND=2)\*(C'\fR
  (\f(CW\*(C`DOUBLE COMPLEX\*(C'\fR) operands.
  .Sp
  The \fB\-ff90\fR option controls the interpretation
  of this construct.
! .Ip "\fB\-fno-ugly-init\fR" 4
  .IX Item "-fno-ugly-init"
  Disallow use of Hollerith and typeless constants as initial
  values (in \f(CW\*(C`PARAMETER\*(C'\fR and \f(CW\*(C`DATA\*(C'\fR statements), and
--- 536,562 ----
  and treat an empty argument list
  as specification of a single null argument.
  .Sp
! For example, \fB\s-1CALL\s0 \s-1FOO\s0(,)\fR is treated as
! \&\fB\s-1CALL\s0 \s-1FOO\s0(%\f(BIVAL\fB\|(0), %\f(BIVAL\fB\|(0))\fR.
  That is, \fItwo\fR null arguments are specified
! by the procedure call when \fB\-fugly\-comma\fR is in force.
! And \fBF = \s-1\f(BIFUNC\s0()\fB\fR is treated as \fBF = \s-1FUNC\s0(%\f(BIVAL\fB\|(0))\fR.
  .Sp
! The default behavior, \fB\-fno\-ugly\-comma\fR, is to ignore
  a single trailing comma in an argument list.
! So, by default, \fB\s-1CALL\s0 \s-1FOO\s0(X,)\fR is treated
! exactly the same as \fB\s-1CALL\s0 \s-1FOO\s0(X)\fR.
! .IP "\fB\-fugly\-complex\fR" 4
  .IX Item "-fugly-complex"
! Do not complain about \fB\s-1REAL\s0(\fR\fIexpr\fR\fB)\fR or
! \&\fB\s-1AIMAG\s0(\fR\fIexpr\fR\fB)\fR when \fIexpr\fR is a \f(CW\*(C`COMPLEX\*(C'\fR
  type other than \f(CW\*(C`COMPLEX(KIND=1)\*(C'\fR\-\-\-usually
  this is used to permit \f(CW\*(C`COMPLEX(KIND=2)\*(C'\fR
  (\f(CW\*(C`DOUBLE COMPLEX\*(C'\fR) operands.
  .Sp
  The \fB\-ff90\fR option controls the interpretation
  of this construct.
! .IP "\fB\-fno\-ugly\-init\fR" 4
  .IX Item "-fno-ugly-init"
  Disallow use of Hollerith and typeless constants as initial
  values (in \f(CW\*(C`PARAMETER\*(C'\fR and \f(CW\*(C`DATA\*(C'\fR statements), and
*************** use of character constants to
*** 572,586 ****
  initialize numeric types and vice versa.
  .Sp
  For example, \fB\s-1DATA\s0 I/'F'/, \s-1CHRVAR/65/\s0, J/4HABCD/\fR is disallowed by
! \&\fB\-fno-ugly-init\fR.
! .Ip "\fB\-fugly-logint\fR" 4
  .IX Item "-fugly-logint"
  Treat \f(CW\*(C`INTEGER\*(C'\fR and \f(CW\*(C`LOGICAL\*(C'\fR variables and
  expressions as potential stand-ins for each other.
  .Sp
  For example, automatic conversion between \f(CW\*(C`INTEGER\*(C'\fR and
  \&\f(CW\*(C`LOGICAL\*(C'\fR is enabled, for many contexts, via this option.
! .Ip "\fB\-fonetrip\fR" 4
  .IX Item "-fonetrip"
  Executable iterative \f(CW\*(C`DO\*(C'\fR loops are to be executed at
  least once each time they are reached.
--- 564,578 ----
  initialize numeric types and vice versa.
  .Sp
  For example, \fB\s-1DATA\s0 I/'F'/, \s-1CHRVAR/65/\s0, J/4HABCD/\fR is disallowed by
! \&\fB\-fno\-ugly\-init\fR.
! .IP "\fB\-fugly\-logint\fR" 4
  .IX Item "-fugly-logint"
  Treat \f(CW\*(C`INTEGER\*(C'\fR and \f(CW\*(C`LOGICAL\*(C'\fR variables and
  expressions as potential stand-ins for each other.
  .Sp
  For example, automatic conversion between \f(CW\*(C`INTEGER\*(C'\fR and
  \&\f(CW\*(C`LOGICAL\*(C'\fR is enabled, for many contexts, via this option.
! .IP "\fB\-fonetrip\fR" 4
  .IX Item "-fonetrip"
  Executable iterative \f(CW\*(C`DO\*(C'\fR loops are to be executed at
  least once each time they are reached.
*************** For example, some code written to the \s
*** 601,614 ****
  expects this behavior from its \f(CW\*(C`DO\*(C'\fR loops, although that
  standard did not specify this behavior.
  .Sp
! The \fB\-fonetrip\fR option specifies that the source \fIfile\fR\|(s) being
  compiled require one-trip loops.
  .Sp
  This option affects only those loops specified by the (iterative) \f(CW\*(C`DO\*(C'\fR
! statement and by implied-\f(CW\*(C`DO\*(C'\fR lists in I/O statements.
! Loops specified by implied-\f(CW\*(C`DO\*(C'\fR lists in \f(CW\*(C`DATA\*(C'\fR and
! specification (non-executable) statements are not affected.
! .Ip "\fB\-ftypeless-boz\fR" 4
  .IX Item "-ftypeless-boz"
  Specifies that prefix-radix non-decimal constants, such as
  \&\fBZ'\s-1ABCD\s0'\fR, are typeless instead of \f(CW\*(C`INTEGER(KIND=1)\*(C'\fR.
--- 593,606 ----
  expects this behavior from its \f(CW\*(C`DO\*(C'\fR loops, although that
  standard did not specify this behavior.
  .Sp
! The \fB\-fonetrip\fR option specifies that the source file(s) being
  compiled require one-trip loops.
  .Sp
  This option affects only those loops specified by the (iterative) \f(CW\*(C`DO\*(C'\fR
! statement and by implied\-\f(CW\*(C`DO\*(C'\fR lists in I/O statements.
! Loops specified by implied\-\f(CW\*(C`DO\*(C'\fR lists in \f(CW\*(C`DATA\*(C'\fR and
! specification (non\-executable) statements are not affected.
! .IP "\fB\-ftypeless\-boz\fR" 4
  .IX Item "-ftypeless-boz"
  Specifies that prefix-radix non-decimal constants, such as
  \&\fBZ'\s-1ABCD\s0'\fR, are typeless instead of \f(CW\*(C`INTEGER(KIND=1)\*(C'\fR.
*************** following program:
*** 625,800 ****
  \&        IF (J .NE. I) PRINT *, 'Prefix form is INTEGER'
  \&        END
  .Ve
  Reports indicate that many compilers process this form as
  \&\f(CW\*(C`INTEGER(KIND=1)\*(C'\fR, though a few as typeless, and at least one
  based on a command-line option specifying some kind of
  compatibility.
! .Ip "\fB\-fintrin-case-initcap\fR" 4
  .IX Item "-fintrin-case-initcap"
  .PD 0
! .Ip "\fB\-fintrin-case-upper\fR" 4
  .IX Item "-fintrin-case-upper"
! .Ip "\fB\-fintrin-case-lower\fR" 4
  .IX Item "-fintrin-case-lower"
! .Ip "\fB\-fintrin-case-any\fR" 4
  .IX Item "-fintrin-case-any"
  .PD
  Specify expected case for intrinsic names.
! \&\fB\-fintrin-case-lower\fR is the default.
! .Ip "\fB\-fmatch-case-initcap\fR" 4
  .IX Item "-fmatch-case-initcap"
  .PD 0
! .Ip "\fB\-fmatch-case-upper\fR" 4
  .IX Item "-fmatch-case-upper"
! .Ip "\fB\-fmatch-case-lower\fR" 4
  .IX Item "-fmatch-case-lower"
! .Ip "\fB\-fmatch-case-any\fR" 4
  .IX Item "-fmatch-case-any"
  .PD
  Specify expected case for keywords.
! \&\fB\-fmatch-case-lower\fR is the default.
! .Ip "\fB\-fsource-case-upper\fR" 4
  .IX Item "-fsource-case-upper"
  .PD 0
! .Ip "\fB\-fsource-case-lower\fR" 4
  .IX Item "-fsource-case-lower"
! .Ip "\fB\-fsource-case-preserve\fR" 4
  .IX Item "-fsource-case-preserve"
  .PD
  Specify whether source text other than character and Hollerith constants
  is to be translated to uppercase, to lowercase, or preserved as is.
! \&\fB\-fsource-case-lower\fR is the default.
! .Ip "\fB\-fsymbol-case-initcap\fR" 4
  .IX Item "-fsymbol-case-initcap"
  .PD 0
! .Ip "\fB\-fsymbol-case-upper\fR" 4
  .IX Item "-fsymbol-case-upper"
! .Ip "\fB\-fsymbol-case-lower\fR" 4
  .IX Item "-fsymbol-case-lower"
! .Ip "\fB\-fsymbol-case-any\fR" 4
  .IX Item "-fsymbol-case-any"
  .PD
  Specify valid cases for user-defined symbol names.
! \&\fB\-fsymbol-case-any\fR is the default.
! .Ip "\fB\-fcase-strict-upper\fR" 4
  .IX Item "-fcase-strict-upper"
! Same as \fB\-fintrin-case-upper \-fmatch-case-upper \-fsource-case-preserve
! \&\-fsymbol-case-upper\fR.
  (Requires all pertinent source to be in uppercase.)
! .Ip "\fB\-fcase-strict-lower\fR" 4
  .IX Item "-fcase-strict-lower"
! Same as \fB\-fintrin-case-lower \-fmatch-case-lower \-fsource-case-preserve
! \&\-fsymbol-case-lower\fR.
  (Requires all pertinent source to be in lowercase.)
! .Ip "\fB\-fcase-initcap\fR" 4
  .IX Item "-fcase-initcap"
! Same as \fB\-fintrin-case-initcap \-fmatch-case-initcap \-fsource-case-preserve
! \&\-fsymbol-case-initcap\fR.
  (Requires all pertinent source to be in initial capitals,
  as in \fBPrint *,SqRt(Value)\fR.)
! .Ip "\fB\-fcase-upper\fR" 4
  .IX Item "-fcase-upper"
! Same as \fB\-fintrin-case-any \-fmatch-case-any \-fsource-case-upper
! \&\-fsymbol-case-any\fR.
  (Maps all pertinent source to uppercase.)
! .Ip "\fB\-fcase-lower\fR" 4
  .IX Item "-fcase-lower"
! Same as \fB\-fintrin-case-any \-fmatch-case-any \-fsource-case-lower
! \&\-fsymbol-case-any\fR.
  (Maps all pertinent source to lowercase.)
! .Ip "\fB\-fcase-preserve\fR" 4
  .IX Item "-fcase-preserve"
! Same as \fB\-fintrin-case-any \-fmatch-case-any \-fsource-case-preserve
! \&\-fsymbol-case-any\fR.
  (Preserves all case in user-defined symbols,
  while allowing any-case matching of intrinsics and keywords.
  For example, \fBcall Foo(i,I)\fR would pass two \fIdifferent\fR
  variables named \fBi\fR and \fBI\fR to a procedure named \fBFoo\fR.)
! .Ip "\fB\-fbadu77\-intrinsics-delete\fR" 4
  .IX Item "-fbadu77-intrinsics-delete"
  .PD 0
! .Ip "\fB\-fbadu77\-intrinsics-hide\fR" 4
  .IX Item "-fbadu77-intrinsics-hide"
! .Ip "\fB\-fbadu77\-intrinsics-disable\fR" 4
  .IX Item "-fbadu77-intrinsics-disable"
! .Ip "\fB\-fbadu77\-intrinsics-enable\fR" 4
  .IX Item "-fbadu77-intrinsics-enable"
  .PD
  Specify status of \s-1UNIX\s0 intrinsics having inappropriate forms.
! \&\fB\-fbadu77\-intrinsics-enable\fR is the default.
! .Ip "\fB\-ff2c-intrinsics-delete\fR" 4
  .IX Item "-ff2c-intrinsics-delete"
  .PD 0
! .Ip "\fB\-ff2c-intrinsics-hide\fR" 4
  .IX Item "-ff2c-intrinsics-hide"
! .Ip "\fB\-ff2c-intrinsics-disable\fR" 4
  .IX Item "-ff2c-intrinsics-disable"
! .Ip "\fB\-ff2c-intrinsics-enable\fR" 4
  .IX Item "-ff2c-intrinsics-enable"
  .PD
! Specify status of f2c-specific intrinsics.
! \&\fB\-ff2c-intrinsics-enable\fR is the default.
! .Ip "\fB\-ff90\-intrinsics-delete\fR" 4
  .IX Item "-ff90-intrinsics-delete"
  .PD 0
! .Ip "\fB\-ff90\-intrinsics-hide\fR" 4
  .IX Item "-ff90-intrinsics-hide"
! .Ip "\fB\-ff90\-intrinsics-disable\fR" 4
  .IX Item "-ff90-intrinsics-disable"
! .Ip "\fB\-ff90\-intrinsics-enable\fR" 4
  .IX Item "-ff90-intrinsics-enable"
  .PD
  Specify status of F90\-specific intrinsics.
! \&\fB\-ff90\-intrinsics-enable\fR is the default.
! .Ip "\fB\-fgnu-intrinsics-delete\fR" 4
  .IX Item "-fgnu-intrinsics-delete"
  .PD 0
! .Ip "\fB\-fgnu-intrinsics-hide\fR" 4
  .IX Item "-fgnu-intrinsics-hide"
! .Ip "\fB\-fgnu-intrinsics-disable\fR" 4
  .IX Item "-fgnu-intrinsics-disable"
! .Ip "\fB\-fgnu-intrinsics-enable\fR" 4
  .IX Item "-fgnu-intrinsics-enable"
  .PD
  Specify status of Digital's COMPLEX-related intrinsics.
! \&\fB\-fgnu-intrinsics-enable\fR is the default.
! .Ip "\fB\-fmil-intrinsics-delete\fR" 4
  .IX Item "-fmil-intrinsics-delete"
  .PD 0
! .Ip "\fB\-fmil-intrinsics-hide\fR" 4
  .IX Item "-fmil-intrinsics-hide"
! .Ip "\fB\-fmil-intrinsics-disable\fR" 4
  .IX Item "-fmil-intrinsics-disable"
! .Ip "\fB\-fmil-intrinsics-enable\fR" 4
  .IX Item "-fmil-intrinsics-enable"
  .PD
! Specify status of MIL-STD-1753\-specific intrinsics.
! \&\fB\-fmil-intrinsics-enable\fR is the default.
! .Ip "\fB\-funix-intrinsics-delete\fR" 4
  .IX Item "-funix-intrinsics-delete"
  .PD 0
! .Ip "\fB\-funix-intrinsics-hide\fR" 4
  .IX Item "-funix-intrinsics-hide"
! .Ip "\fB\-funix-intrinsics-disable\fR" 4
  .IX Item "-funix-intrinsics-disable"
! .Ip "\fB\-funix-intrinsics-enable\fR" 4
  .IX Item "-funix-intrinsics-enable"
  .PD
  Specify status of \s-1UNIX\s0 intrinsics.
! \&\fB\-funix-intrinsics-enable\fR is the default.
! .Ip "\fB\-fvxt-intrinsics-delete\fR" 4
  .IX Item "-fvxt-intrinsics-delete"
  .PD 0
! .Ip "\fB\-fvxt-intrinsics-hide\fR" 4
  .IX Item "-fvxt-intrinsics-hide"
! .Ip "\fB\-fvxt-intrinsics-disable\fR" 4
  .IX Item "-fvxt-intrinsics-disable"
! .Ip "\fB\-fvxt-intrinsics-enable\fR" 4
  .IX Item "-fvxt-intrinsics-enable"
  .PD
  Specify status of \s-1VXT\s0 intrinsics.
! \&\fB\-fvxt-intrinsics-enable\fR is the default.
! .Ip "\fB\-ffixed-line-length-\fR\fIn\fR" 4
  .IX Item "-ffixed-line-length-n"
  Set column after which characters are ignored in typical fixed-form
  lines in the source file, and through which spaces are assumed (as
--- 617,793 ----
  \&        IF (J .NE. I) PRINT *, 'Prefix form is INTEGER'
  \&        END
  .Ve
+ .Sp
  Reports indicate that many compilers process this form as
  \&\f(CW\*(C`INTEGER(KIND=1)\*(C'\fR, though a few as typeless, and at least one
  based on a command-line option specifying some kind of
  compatibility.
! .IP "\fB\-fintrin\-case\-initcap\fR" 4
  .IX Item "-fintrin-case-initcap"
  .PD 0
! .IP "\fB\-fintrin\-case\-upper\fR" 4
  .IX Item "-fintrin-case-upper"
! .IP "\fB\-fintrin\-case\-lower\fR" 4
  .IX Item "-fintrin-case-lower"
! .IP "\fB\-fintrin\-case\-any\fR" 4
  .IX Item "-fintrin-case-any"
  .PD
  Specify expected case for intrinsic names.
! \&\fB\-fintrin\-case\-lower\fR is the default.
! .IP "\fB\-fmatch\-case\-initcap\fR" 4
  .IX Item "-fmatch-case-initcap"
  .PD 0
! .IP "\fB\-fmatch\-case\-upper\fR" 4
  .IX Item "-fmatch-case-upper"
! .IP "\fB\-fmatch\-case\-lower\fR" 4
  .IX Item "-fmatch-case-lower"
! .IP "\fB\-fmatch\-case\-any\fR" 4
  .IX Item "-fmatch-case-any"
  .PD
  Specify expected case for keywords.
! \&\fB\-fmatch\-case\-lower\fR is the default.
! .IP "\fB\-fsource\-case\-upper\fR" 4
  .IX Item "-fsource-case-upper"
  .PD 0
! .IP "\fB\-fsource\-case\-lower\fR" 4
  .IX Item "-fsource-case-lower"
! .IP "\fB\-fsource\-case\-preserve\fR" 4
  .IX Item "-fsource-case-preserve"
  .PD
  Specify whether source text other than character and Hollerith constants
  is to be translated to uppercase, to lowercase, or preserved as is.
! \&\fB\-fsource\-case\-lower\fR is the default.
! .IP "\fB\-fsymbol\-case\-initcap\fR" 4
  .IX Item "-fsymbol-case-initcap"
  .PD 0
! .IP "\fB\-fsymbol\-case\-upper\fR" 4
  .IX Item "-fsymbol-case-upper"
! .IP "\fB\-fsymbol\-case\-lower\fR" 4
  .IX Item "-fsymbol-case-lower"
! .IP "\fB\-fsymbol\-case\-any\fR" 4
  .IX Item "-fsymbol-case-any"
  .PD
  Specify valid cases for user-defined symbol names.
! \&\fB\-fsymbol\-case\-any\fR is the default.
! .IP "\fB\-fcase\-strict\-upper\fR" 4
  .IX Item "-fcase-strict-upper"
! Same as \fB\-fintrin\-case\-upper \-fmatch\-case\-upper \-fsource\-case\-preserve
! \&\-fsymbol\-case\-upper\fR.
  (Requires all pertinent source to be in uppercase.)
! .IP "\fB\-fcase\-strict\-lower\fR" 4
  .IX Item "-fcase-strict-lower"
! Same as \fB\-fintrin\-case\-lower \-fmatch\-case\-lower \-fsource\-case\-preserve
! \&\-fsymbol\-case\-lower\fR.
  (Requires all pertinent source to be in lowercase.)
! .IP "\fB\-fcase\-initcap\fR" 4
  .IX Item "-fcase-initcap"
! Same as \fB\-fintrin\-case\-initcap \-fmatch\-case\-initcap \-fsource\-case\-preserve
! \&\-fsymbol\-case\-initcap\fR.
  (Requires all pertinent source to be in initial capitals,
  as in \fBPrint *,SqRt(Value)\fR.)
! .IP "\fB\-fcase\-upper\fR" 4
  .IX Item "-fcase-upper"
! Same as \fB\-fintrin\-case\-any \-fmatch\-case\-any \-fsource\-case\-upper
! \&\-fsymbol\-case\-any\fR.
  (Maps all pertinent source to uppercase.)
! .IP "\fB\-fcase\-lower\fR" 4
  .IX Item "-fcase-lower"
! Same as \fB\-fintrin\-case\-any \-fmatch\-case\-any \-fsource\-case\-lower
! \&\-fsymbol\-case\-any\fR.
  (Maps all pertinent source to lowercase.)
! .IP "\fB\-fcase\-preserve\fR" 4
  .IX Item "-fcase-preserve"
! Same as \fB\-fintrin\-case\-any \-fmatch\-case\-any \-fsource\-case\-preserve
! \&\-fsymbol\-case\-any\fR.
  (Preserves all case in user-defined symbols,
  while allowing any-case matching of intrinsics and keywords.
  For example, \fBcall Foo(i,I)\fR would pass two \fIdifferent\fR
  variables named \fBi\fR and \fBI\fR to a procedure named \fBFoo\fR.)
! .IP "\fB\-fbadu77\-intrinsics\-delete\fR" 4
  .IX Item "-fbadu77-intrinsics-delete"
  .PD 0
! .IP "\fB\-fbadu77\-intrinsics\-hide\fR" 4
  .IX Item "-fbadu77-intrinsics-hide"
! .IP "\fB\-fbadu77\-intrinsics\-disable\fR" 4
  .IX Item "-fbadu77-intrinsics-disable"
! .IP "\fB\-fbadu77\-intrinsics\-enable\fR" 4
  .IX Item "-fbadu77-intrinsics-enable"
  .PD
  Specify status of \s-1UNIX\s0 intrinsics having inappropriate forms.
! \&\fB\-fbadu77\-intrinsics\-enable\fR is the default.
! .IP "\fB\-ff2c\-intrinsics\-delete\fR" 4
  .IX Item "-ff2c-intrinsics-delete"
  .PD 0
! .IP "\fB\-ff2c\-intrinsics\-hide\fR" 4
  .IX Item "-ff2c-intrinsics-hide"
! .IP "\fB\-ff2c\-intrinsics\-disable\fR" 4
  .IX Item "-ff2c-intrinsics-disable"
! .IP "\fB\-ff2c\-intrinsics\-enable\fR" 4
  .IX Item "-ff2c-intrinsics-enable"
  .PD
! Specify status of f2c\-specific intrinsics.
! \&\fB\-ff2c\-intrinsics\-enable\fR is the default.
! .IP "\fB\-ff90\-intrinsics\-delete\fR" 4
  .IX Item "-ff90-intrinsics-delete"
  .PD 0
! .IP "\fB\-ff90\-intrinsics\-hide\fR" 4
  .IX Item "-ff90-intrinsics-hide"
! .IP "\fB\-ff90\-intrinsics\-disable\fR" 4
  .IX Item "-ff90-intrinsics-disable"
! .IP "\fB\-ff90\-intrinsics\-enable\fR" 4
  .IX Item "-ff90-intrinsics-enable"
  .PD
  Specify status of F90\-specific intrinsics.
! \&\fB\-ff90\-intrinsics\-enable\fR is the default.
! .IP "\fB\-fgnu\-intrinsics\-delete\fR" 4
  .IX Item "-fgnu-intrinsics-delete"
  .PD 0
! .IP "\fB\-fgnu\-intrinsics\-hide\fR" 4
  .IX Item "-fgnu-intrinsics-hide"
! .IP "\fB\-fgnu\-intrinsics\-disable\fR" 4
  .IX Item "-fgnu-intrinsics-disable"
! .IP "\fB\-fgnu\-intrinsics\-enable\fR" 4
  .IX Item "-fgnu-intrinsics-enable"
  .PD
  Specify status of Digital's COMPLEX-related intrinsics.
! \&\fB\-fgnu\-intrinsics\-enable\fR is the default.
! .IP "\fB\-fmil\-intrinsics\-delete\fR" 4
  .IX Item "-fmil-intrinsics-delete"
  .PD 0
! .IP "\fB\-fmil\-intrinsics\-hide\fR" 4
  .IX Item "-fmil-intrinsics-hide"
! .IP "\fB\-fmil\-intrinsics\-disable\fR" 4
  .IX Item "-fmil-intrinsics-disable"
! .IP "\fB\-fmil\-intrinsics\-enable\fR" 4
  .IX Item "-fmil-intrinsics-enable"
  .PD
! Specify status of MIL\-STD\-1753\-specific intrinsics.
! \&\fB\-fmil\-intrinsics\-enable\fR is the default.
! .IP "\fB\-funix\-intrinsics\-delete\fR" 4
  .IX Item "-funix-intrinsics-delete"
  .PD 0
! .IP "\fB\-funix\-intrinsics\-hide\fR" 4
  .IX Item "-funix-intrinsics-hide"
! .IP "\fB\-funix\-intrinsics\-disable\fR" 4
  .IX Item "-funix-intrinsics-disable"
! .IP "\fB\-funix\-intrinsics\-enable\fR" 4
  .IX Item "-funix-intrinsics-enable"
  .PD
  Specify status of \s-1UNIX\s0 intrinsics.
! \&\fB\-funix\-intrinsics\-enable\fR is the default.
! .IP "\fB\-fvxt\-intrinsics\-delete\fR" 4
  .IX Item "-fvxt-intrinsics-delete"
  .PD 0
! .IP "\fB\-fvxt\-intrinsics\-hide\fR" 4
  .IX Item "-fvxt-intrinsics-hide"
! .IP "\fB\-fvxt\-intrinsics\-disable\fR" 4
  .IX Item "-fvxt-intrinsics-disable"
! .IP "\fB\-fvxt\-intrinsics\-enable\fR" 4
  .IX Item "-fvxt-intrinsics-enable"
  .PD
  Specify status of \s-1VXT\s0 intrinsics.
! \&\fB\-fvxt\-intrinsics\-enable\fR is the default.
! .IP "\fB\-ffixed\-line\-length\-\fR\fIn\fR" 4
  .IX Item "-ffixed-line-length-n"
  Set column after which characters are ignored in typical fixed-form
  lines in the source file, and through which spaces are assumed (as
*************** if padded to that length) after the ends
*** 802,813 ****
  .Sp
  Popular values for \fIn\fR include 72 (the
  standard and the default), 80 (card image), and 132 (corresponds
! to ``extended-source'' options in some popular compilers).
  \&\fIn\fR may be \fBnone\fR, meaning that the entire line is meaningful
  and that continued character constants never have implicit spaces appended
  to them to fill out the line.
! \&\fB\-ffixed-line-length-0\fR means the same thing as
! \&\fB\-ffixed-line-length-none\fR.
  .Sh "Options to Request or Suppress Warnings"
  .IX Subsection "Options to Request or Suppress Warnings"
  Warnings are diagnostic messages that report constructions which
--- 795,806 ----
  .Sp
  Popular values for \fIn\fR include 72 (the
  standard and the default), 80 (card image), and 132 (corresponds
! to ``extended\-source'' options in some popular compilers).
  \&\fIn\fR may be \fBnone\fR, meaning that the entire line is meaningful
  and that continued character constants never have implicit spaces appended
  to them to fill out the line.
! \&\fB\-ffixed\-line\-length\-0\fR means the same thing as
! \&\fB\-ffixed\-line\-length\-none\fR.
  .Sh "Options to Request or Suppress Warnings"
  .IX Subsection "Options to Request or Suppress Warnings"
  Warnings are diagnostic messages that report constructions which
*************** might have been an error.
*** 817,835 ****
  You can request many specific warnings with options beginning \fB\-W\fR,
  for example \fB\-Wimplicit\fR to request warnings on implicit
  declarations.  Each of these specific warning options also has a
! negative form beginning \fB\-Wno-\fR to turn off warnings;
! for example, \fB\-Wno-implicit\fR.  This manual lists only one of the
  two forms, whichever is not the default.
  .PP
  These options control the amount and kinds of warnings produced by \s-1GNU\s0
  Fortran:
! .Ip "\fB\-fsyntax-only\fR" 4
  .IX Item "-fsyntax-only"
  Check the code for syntax errors, but don't do anything beyond that.
! .Ip "\fB\-pedantic\fR" 4
  .IX Item "-pedantic"
  Issue warnings for uses of extensions to \s-1ANSI\s0 \s-1FORTRAN\s0 77.
! \&\fB\-pedantic\fR also applies to C-language constructs where they
  occur in \s-1GNU\s0 Fortran source files, such as use of \fB\ee\fR in a
  character constant within a directive like \fB#include\fR.
  .Sp
--- 810,828 ----
  You can request many specific warnings with options beginning \fB\-W\fR,
  for example \fB\-Wimplicit\fR to request warnings on implicit
  declarations.  Each of these specific warning options also has a
! negative form beginning \fB\-Wno\-\fR to turn off warnings;
! for example, \fB\-Wno\-implicit\fR.  This manual lists only one of the
  two forms, whichever is not the default.
  .PP
  These options control the amount and kinds of warnings produced by \s-1GNU\s0
  Fortran:
! .IP "\fB\-fsyntax\-only\fR" 4
  .IX Item "-fsyntax-only"
  Check the code for syntax errors, but don't do anything beyond that.
! .IP "\fB\-pedantic\fR" 4
  .IX Item "-pedantic"
  Issue warnings for uses of extensions to \s-1ANSI\s0 \s-1FORTRAN\s0 77.
! \&\fB\-pedantic\fR also applies to C\-language constructs where they
  occur in \s-1GNU\s0 Fortran source files, such as use of \fB\ee\fR in a
  character constant within a directive like \fB#include\fR.
  .Sp
*************** conformance.
*** 844,860 ****
  They soon find that it does not do quite what they want\-\-\-it finds some
  non-ANSI practices, but not all.
  However, improvements to \fBg77\fR in this area are welcome.
! .Ip "\fB\-pedantic-errors\fR" 4
  .IX Item "-pedantic-errors"
  Like \fB\-pedantic\fR, except that errors are produced rather than
  warnings.
! .Ip "\fB\-fpedantic\fR" 4
  .IX Item "-fpedantic"
  Like \fB\-pedantic\fR, but applies only to Fortran constructs.
! .Ip "\fB\-w\fR" 4
  .IX Item "-w"
  Inhibit all warning messages.
! .Ip "\fB\-Wno-globals\fR" 4
  .IX Item "-Wno-globals"
  Inhibit warnings about use of a name as both a global name
  (a subroutine, function, or block data program unit, or a
--- 837,853 ----
  They soon find that it does not do quite what they want\-\-\-it finds some
  non-ANSI practices, but not all.
  However, improvements to \fBg77\fR in this area are welcome.
! .IP "\fB\-pedantic\-errors\fR" 4
  .IX Item "-pedantic-errors"
  Like \fB\-pedantic\fR, except that errors are produced rather than
  warnings.
! .IP "\fB\-fpedantic\fR" 4
  .IX Item "-fpedantic"
  Like \fB\-pedantic\fR, but applies only to Fortran constructs.
! .IP "\fB\-w\fR" 4
  .IX Item "-w"
  Inhibit all warning messages.
! .IP "\fB\-Wno\-globals\fR" 4
  .IX Item "-Wno-globals"
  Inhibit warnings about use of a name as both a global name
  (a subroutine, function, or block data program unit, or a
*************** Also inhibit warnings about inconsistent
*** 865,871 ****
  definitions of global procedures (function and subroutines).
  Such inconsistencies include different numbers of arguments
  and different types of arguments.
! .Ip "\fB\-Wimplicit\fR" 4
  .IX Item "-Wimplicit"
  Warn whenever a variable, array, or function is implicitly
  declared.
--- 858,864 ----
  definitions of global procedures (function and subroutines).
  Such inconsistencies include different numbers of arguments
  and different types of arguments.
! .IP "\fB\-Wimplicit\fR" 4
  .IX Item "-Wimplicit"
  Warn whenever a variable, array, or function is implicitly
  declared.
*************** Has an effect similar to using the \f(CW
*** 873,882 ****
  in every program unit.
  (Some Fortran compilers provide this feature by an option
  named \fB\-u\fR or \fB/WARNINGS=DECLARATIONS\fR.)
! .Ip "\fB\-Wunused\fR" 4
  .IX Item "-Wunused"
  Warn whenever a variable is unused aside from its declaration.
! .Ip "\fB\-Wuninitialized\fR" 4
  .IX Item "-Wuninitialized"
  Warn whenever an automatic variable is used without first being initialized.
  .Sp
--- 866,875 ----
  in every program unit.
  (Some Fortran compilers provide this feature by an option
  named \fB\-u\fR or \fB/WARNINGS=DECLARATIONS\fR.)
! .IP "\fB\-Wunused\fR" 4
  .IX Item "-Wunused"
  Warn whenever a variable is unused aside from its declaration.
! .IP "\fB\-Wuninitialized\fR" 4
  .IX Item "-Wuninitialized"
  Warn whenever an automatic variable is used without first being initialized.
  .Sp
*************** this can happen:
*** 909,914 ****
--- 902,908 ----
  \&        CALL FOO(I)
  \&        END
  .Ve
+ .Sp
  If the value of \f(CW\*(C`J\*(C'\fR is always 1, 2 or 3, then \f(CW\*(C`I\*(C'\fR is
  always initialized, but \s-1GNU\s0 Fortran doesn't know this.  Here is
  another common case:
*************** another common case:
*** 921,928 ****
  \&        IF (FLAG) PRINT *, VALUE
  \&        END
  .Ve
  This has no bug because \f(CW\*(C`VALUE\*(C'\fR is used only if it is set.
! .Ip "\fB\-Wall\fR" 4
  .IX Item "-Wall"
  The \fB\-Wunused\fR and \fB\-Wuninitialized\fR options combined.
  These are all the
--- 915,923 ----
  \&        IF (FLAG) PRINT *, VALUE
  \&        END
  .Ve
+ .Sp
  This has no bug because \f(CW\*(C`VALUE\*(C'\fR is used only if it is set.
! .IP "\fB\-Wall\fR" 4
  .IX Item "-Wall"
  The \fB\-Wunused\fR and \fB\-Wuninitialized\fR options combined.
  These are all the
*************** be added to the list enabled by \fB\-Wal
*** 934,949 ****
  The remaining \fB\-W...\fR options are not implied by \fB\-Wall\fR
  because they warn about constructions that we consider reasonable to
  use, on occasion, in clean programs.
! .Ip "\fB\-Wsurprising\fR" 4
  .IX Item "-Wsurprising"
  Warn about ``suspicious'' constructs that are interpreted
  by the compiler in a way that might well be surprising to
  someone reading the code.
  These differences can result in subtle, compiler-dependent
! (even machine-dependent) behavioral differences.
  The constructs warned about include:
  .RS 4
! .Ip "\(bu" 4
  Expressions having two arithmetic operators in a row, such
  as \fBX*\-Y\fR.
  Such a construct is nonstandard, and can produce
--- 929,944 ----
  The remaining \fB\-W...\fR options are not implied by \fB\-Wall\fR
  because they warn about constructions that we consider reasonable to
  use, on occasion, in clean programs.
! .IP "\fB\-Wsurprising\fR" 4
  .IX Item "-Wsurprising"
  Warn about ``suspicious'' constructs that are interpreted
  by the compiler in a way that might well be surprising to
  someone reading the code.
  These differences can result in subtle, compiler-dependent
! (even machine\-dependent) behavioral differences.
  The constructs warned about include:
  .RS 4
! .IP "\(bu" 4
  Expressions having two arithmetic operators in a row, such
  as \fBX*\-Y\fR.
  Such a construct is nonstandard, and can produce
*************** type promotion.
*** 963,969 ****
  .Sp
  (The \fB\-fpedantic\fR option also warns about expressions
  having two arithmetic operators in a row.)
! .Ip "\(bu" 4
  Expressions with a unary minus followed by an operand and then
  a binary operator other than plus or minus.
  For example, \fB\-2**2\fR produces a warning, because
--- 958,964 ----
  .Sp
  (The \fB\-fpedantic\fR option also warns about expressions
  having two arithmetic operators in a row.)
! .IP "\(bu" 4
  Expressions with a unary minus followed by an operand and then
  a binary operator other than plus or minus.
  For example, \fB\-2**2\fR produces a warning, because
*************** of this warning is to warn about differi
*** 989,995 ****
  and encourage a better style of coding, not to identify
  only those places where bugs might exist in the user's
  code.
! .Ip "\(bu" 4
  \&\f(CW\*(C`DO\*(C'\fR loops with \f(CW\*(C`DO\*(C'\fR variables that are not
  of integral type\-\-\-that is, using \f(CW\*(C`REAL\*(C'\fR
  variables as loop control variables.
--- 984,990 ----
  and encourage a better style of coding, not to identify
  only those places where bugs might exist in the user's
  code.
! .IP "\(bu" 4
  \&\f(CW\*(C`DO\*(C'\fR loops with \f(CW\*(C`DO\*(C'\fR variables that are not
  of integral type\-\-\-that is, using \f(CW\*(C`REAL\*(C'\fR
  variables as loop control variables.
*************** are pronounced for non-integral loop con
*** 1002,1011 ****
  .RE
  .RS 4
  .RE
! .Ip "\fB\-Werror\fR" 4
  .IX Item "-Werror"
  Make all warnings into errors.
! .Ip "\fB\-W\fR" 4
  .IX Item "-W"
  Turns on ``extra warnings'' and, if optimization is specified
  via \fB\-O\fR, the \fB\-Wuninitialized\fR option.
--- 997,1006 ----
  .RE
  .RS 4
  .RE
! .IP "\fB\-Werror\fR" 4
  .IX Item "-Werror"
  Make all warnings into errors.
! .IP "\fB\-W\fR" 4
  .IX Item "-W"
  Turns on ``extra warnings'' and, if optimization is specified
  via \fB\-O\fR, the \fB\-Wuninitialized\fR option.
*************** via \fB\-O\fR, the \fB\-Wuninitialized\f
*** 1013,1022 ****
  .Sp
  ``Extra warnings'' are issued for:
  .RS 4
! .Ip "\(bu" 4
  Unused parameters to a procedure (when \fB\-Wunused\fR also is
  specified).
! .Ip "\(bu" 4
  Overflows involving floating-point constants (not available
  for certain configurations).
  .RE
--- 1008,1017 ----
  .Sp
  ``Extra warnings'' are issued for:
  .RS 4
! .IP "\(bu" 4
  Unused parameters to a procedure (when \fB\-Wunused\fR also is
  specified).
! .IP "\(bu" 4
  Overflows involving floating-point constants (not available
  for certain configurations).
  .RE
*************** for certain configurations).
*** 1024,1051 ****
  .RE
  .PP
  Some of these have no effect when compiling programs written in Fortran:
! .Ip "\fB\-Wcomment\fR" 4
  .IX Item "-Wcomment"
  .PD 0
! .Ip "\fB\-Wformat\fR" 4
  .IX Item "-Wformat"
! .Ip "\fB\-Wparentheses\fR" 4
  .IX Item "-Wparentheses"
! .Ip "\fB\-Wswitch\fR" 4
  .IX Item "-Wswitch"
! .Ip "\fB\-Wtraditional\fR" 4
  .IX Item "-Wtraditional"
! .Ip "\fB\-Wshadow\fR" 4
  .IX Item "-Wshadow"
! .Ip "\fB\-Wid-clash-\fR\fIlen\fR" 4
  .IX Item "-Wid-clash-len"
! .Ip "\fB\-Wlarger-than-\fR\fIlen\fR" 4
  .IX Item "-Wlarger-than-len"
! .Ip "\fB\-Wconversion\fR" 4
  .IX Item "-Wconversion"
! .Ip "\fB\-Waggregate-return\fR" 4
  .IX Item "-Waggregate-return"
! .Ip "\fB\-Wredundant-decls\fR" 4
  .IX Item "-Wredundant-decls"
  .PD
  These options all could have some relevant meaning for
--- 1019,1050 ----
  .RE
  .PP
  Some of these have no effect when compiling programs written in Fortran:
! .IP "\fB\-Wcomment\fR" 4
  .IX Item "-Wcomment"
  .PD 0
! .IP "\fB\-Wformat\fR" 4
  .IX Item "-Wformat"
! .IP "\fB\-Wparentheses\fR" 4
  .IX Item "-Wparentheses"
! .IP "\fB\-Wswitch\fR" 4
  .IX Item "-Wswitch"
! .IP "\fB\-Wswitch\-default\fR" 4
! .IX Item "-Wswitch-default"
! .IP "\fB\-Wswitch\-enum\fR" 4
! .IX Item "-Wswitch-enum"
! .IP "\fB\-Wtraditional\fR" 4
  .IX Item "-Wtraditional"
! .IP "\fB\-Wshadow\fR" 4
  .IX Item "-Wshadow"
! .IP "\fB\-Wid\-clash\-\fR\fIlen\fR" 4
  .IX Item "-Wid-clash-len"
! .IP "\fB\-Wlarger\-than\-\fR\fIlen\fR" 4
  .IX Item "-Wlarger-than-len"
! .IP "\fB\-Wconversion\fR" 4
  .IX Item "-Wconversion"
! .IP "\fB\-Waggregate\-return\fR" 4
  .IX Item "-Waggregate-return"
! .IP "\fB\-Wredundant\-decls\fR" 4
  .IX Item "-Wredundant-decls"
  .PD
  These options all could have some relevant meaning for
*************** These options all could have some releva
*** 1054,1060 ****
  .IX Subsection "Options for Debugging Your Program or GNU Fortran"
  \&\s-1GNU\s0 Fortran has various special options that are used for debugging
  either your program or \fBg77\fR
! .Ip "\fB\-g\fR" 4
  .IX Item "-g"
  Produce debugging information in the operating system's native format
  (stabs, \s-1COFF\s0, \s-1XCOFF\s0, or \s-1DWARF\s0).  \s-1GDB\s0 can work with this debugging
--- 1053,1059 ----
  .IX Subsection "Options for Debugging Your Program or GNU Fortran"
  \&\s-1GNU\s0 Fortran has various special options that are used for debugging
  either your program or \fBg77\fR
! .IP "\fB\-g\fR" 4
  .IX Item "-g"
  Produce debugging information in the operating system's native format
  (stabs, \s-1COFF\s0, \s-1XCOFF\s0, or \s-1DWARF\s0).  \s-1GDB\s0 can work with this debugging
*************** A sample debugging session looks like th
*** 1088,1093 ****
--- 1087,1093 ----
  \&        $2 = 4
  \&        ...
  .Ve
+ .Sp
  One could also add the setting of the breakpoint and the first run command
  to the file \fI.gdbinit\fR in the current directory, to simplify the debugging
  session.
*************** must use \fB\-O\fR or \fB\-O2\fR to get 
*** 1102,1108 ****
  .PP
  The following flags have particular applicability when
  compiling Fortran programs:
! .Ip "\fB\-malign-double\fR" 4
  .IX Item "-malign-double"
  (Intel x86 architecture only.)
  .Sp
--- 1102,1108 ----
  .PP
  The following flags have particular applicability when
  compiling Fortran programs:
! .IP "\fB\-malign\-double\fR" 4
  .IX Item "-malign-double"
  (Intel x86 architecture only.)
  .Sp
*************** and data sets.
*** 1124,1139 ****
  this option does not apply, generally speaking, to Fortran
  code compiled by \fBg77\fR
  .Sp
! \&\fIAlso also note:\fR The negative form of \fB\-malign-double\fR
! is \fB\-mno-align-double\fR, not \fB\-benign-double\fR.
! .Ip "\fB\-ffloat-store\fR" 4
  .IX Item "-ffloat-store"
  Might help a Fortran program that depends on exact \s-1IEEE\s0 conformance on
  some machines, but might slow down a program that doesn't.
  .Sp
  This option is effective when the floating-point unit is set to work in
  \&\s-1IEEE\s0 854 `extended precision'\-\-\-as it typically is on x86 and m68k \s-1GNU\s0
! systems\-\-\-rather than \s-1IEEE\s0 754 double precision.  \fB\-ffloat-store\fR
  tries to remove the extra precision by spilling data from floating-point
  registers into memory and this typically involves a big performance
  hit.  However, it doesn't affect intermediate results, so that it is
--- 1124,1139 ----
  this option does not apply, generally speaking, to Fortran
  code compiled by \fBg77\fR
  .Sp
! \&\fIAlso also note:\fR The negative form of \fB\-malign\-double\fR
! is \fB\-mno\-align\-double\fR, not \fB\-benign\-double\fR.
! .IP "\fB\-ffloat\-store\fR" 4
  .IX Item "-ffloat-store"
  Might help a Fortran program that depends on exact \s-1IEEE\s0 conformance on
  some machines, but might slow down a program that doesn't.
  .Sp
  This option is effective when the floating-point unit is set to work in
  \&\s-1IEEE\s0 854 `extended precision'\-\-\-as it typically is on x86 and m68k \s-1GNU\s0
! systems\-\-\-rather than \s-1IEEE\s0 754 double precision.  \fB\-ffloat\-store\fR
  tries to remove the extra precision by spilling data from floating-point
  registers into memory and this typically involves a big performance
  hit.  However, it doesn't affect intermediate results, so that it is
*************** only partially effective.  `Excess preci
*** 1143,1203 ****
  \&        a = b + c
  \&        d = a * e
  .Ve
  but not in code like:
  .Sp
  .Vb 1
  \&              d = (b + c) * e
  .Ve
  For another, potentially better, way of controlling the precision,
! see \f(CW@ref\fR{Floating-point precision}.
! .Ip "\fB\-fforce-mem\fR" 4
  .IX Item "-fforce-mem"
  .PD 0
! .Ip "\fB\-fforce-addr\fR" 4
  .IX Item "-fforce-addr"
  .PD
  Might improve optimization of loops.
! .Ip "\fB\-fno-inline\fR" 4
  .IX Item "-fno-inline"
  Don't compile statement functions inline.
  Might reduce the size of a program unit\-\-\-which might be at
  expense of some speed (though it should compile faster).
  Note that if you are not optimizing, no functions can be expanded inline.
! .Ip "\fB\-ffast-math\fR" 4
  .IX Item "-ffast-math"
  Might allow some programs designed to not be too dependent
  on \s-1IEEE\s0 behavior for floating-point to run faster, or die trying.
! Sets \fB\-funsafe-math-optimizations\fR, and
! \&\fB\-fno-trapping-math\fR.
! .Ip "\fB\-funsafe-math-optimizations\fR" 4
  .IX Item "-funsafe-math-optimizations"
  Allow optimizations that may be give incorrect results
  for certain \s-1IEEE\s0 inputs.
! .Ip "\fB\-fno-trapping-math\fR" 4
  .IX Item "-fno-trapping-math"
  Allow the compiler to assume that floating-point arithmetic
  will not generate traps on any inputs.  This is useful, for
! example, when running a program using \s-1IEEE\s0 \*(L"non-stop\*(R"
  floating-point arithmetic.
! .Ip "\fB\-fstrength-reduce\fR" 4
  .IX Item "-fstrength-reduce"
  Might make some loops run faster.
! .Ip "\fB\-frerun-cse-after-loop\fR" 4
  .IX Item "-frerun-cse-after-loop"
  .PD 0
! .Ip "\fB\-fexpensive-optimizations\fR" 4
  .IX Item "-fexpensive-optimizations"
! .Ip "\fB\-fdelayed-branch\fR" 4
  .IX Item "-fdelayed-branch"
! .Ip "\fB\-fschedule-insns\fR" 4
  .IX Item "-fschedule-insns"
! .Ip "\fB\-fschedule-insns2\fR" 4
  .IX Item "-fschedule-insns2"
! .Ip "\fB\-fcaller-saves\fR" 4
  .IX Item "-fcaller-saves"
  .PD
  Might improve performance on some code.
! .Ip "\fB\-funroll-loops\fR" 4
  .IX Item "-funroll-loops"
  Typically improves performance on code using iterative \f(CW\*(C`DO\*(C'\fR loops by
  unrolling them and is probably generally appropriate for Fortran, though
--- 1143,1215 ----
  \&        a = b + c
  \&        d = a * e
  .Ve
+ .Sp
  but not in code like:
  .Sp
  .Vb 1
  \&              d = (b + c) * e
  .Ve
+ .Sp
  For another, potentially better, way of controlling the precision,
! see \f(CW@ref\fR{Floating\-point precision}.
! .IP "\fB\-fforce\-mem\fR" 4
  .IX Item "-fforce-mem"
  .PD 0
! .IP "\fB\-fforce\-addr\fR" 4
  .IX Item "-fforce-addr"
  .PD
  Might improve optimization of loops.
! .IP "\fB\-fno\-inline\fR" 4
  .IX Item "-fno-inline"
  Don't compile statement functions inline.
  Might reduce the size of a program unit\-\-\-which might be at
  expense of some speed (though it should compile faster).
  Note that if you are not optimizing, no functions can be expanded inline.
! .IP "\fB\-ffast\-math\fR" 4
  .IX Item "-ffast-math"
  Might allow some programs designed to not be too dependent
  on \s-1IEEE\s0 behavior for floating-point to run faster, or die trying.
! Sets \fB\-funsafe\-math\-optimizations\fR, \fB\-ffinite\-math\-only\fR,
! and \fB\-fno\-trapping\-math\fR.
! .IP "\fB\-funsafe\-math\-optimizations\fR" 4
  .IX Item "-funsafe-math-optimizations"
  Allow optimizations that may be give incorrect results
  for certain \s-1IEEE\s0 inputs.
! .IP "\fB\-ffinite\-math\-only\fR" 4
! .IX Item "-ffinite-math-only"
! Allow optimizations for floating-point arithmetic that assume
! that arguments and results are not NaNs or +\-Infs.
! .Sp
! This option should never be turned on by any \fB\-O\fR option since
! it can result in incorrect output for programs which depend on
! an exact implementation of \s-1IEEE\s0 or \s-1ISO\s0 rules/specifications.
! .Sp
! The default is \fB\-fno\-finite\-math\-only\fR.
! .IP "\fB\-fno\-trapping\-math\fR" 4
  .IX Item "-fno-trapping-math"
  Allow the compiler to assume that floating-point arithmetic
  will not generate traps on any inputs.  This is useful, for
! example, when running a program using \s-1IEEE\s0 \*(L"non\-stop\*(R"
  floating-point arithmetic.
! .IP "\fB\-fstrength\-reduce\fR" 4
  .IX Item "-fstrength-reduce"
  Might make some loops run faster.
! .IP "\fB\-frerun\-cse\-after\-loop\fR" 4
  .IX Item "-frerun-cse-after-loop"
  .PD 0
! .IP "\fB\-fexpensive\-optimizations\fR" 4
  .IX Item "-fexpensive-optimizations"
! .IP "\fB\-fdelayed\-branch\fR" 4
  .IX Item "-fdelayed-branch"
! .IP "\fB\-fschedule\-insns\fR" 4
  .IX Item "-fschedule-insns"
! .IP "\fB\-fschedule\-insns2\fR" 4
  .IX Item "-fschedule-insns2"
! .IP "\fB\-fcaller\-saves\fR" 4
  .IX Item "-fcaller-saves"
  .PD
  Might improve performance on some code.
! .IP "\fB\-funroll\-loops\fR" 4
  .IX Item "-funroll-loops"
  Typically improves performance on code using iterative \f(CW\*(C`DO\*(C'\fR loops by
  unrolling them and is probably generally appropriate for Fortran, though
*************** benefit from loop optimizations, includi
*** 1210,1238 ****
  to\-\-\-unrolling.  Loops written with \f(CW\*(C`IF\*(C'\fR and \f(CW\*(C`GOTO\*(C'\fR are not
  currently recognized as such.  This option unrolls only iterative
  \&\f(CW\*(C`DO\*(C'\fR loops, not \f(CW\*(C`DO WHILE\*(C'\fR loops.
! .Ip "\fB\-funroll-all-loops\fR" 4
  .IX Item "-funroll-all-loops"
  Probably improves performance on code using \f(CW\*(C`DO WHILE\*(C'\fR loops by
  unrolling them in addition to iterative \f(CW\*(C`DO\*(C'\fR loops.  In the absence
! of \f(CW\*(C`DO WHILE\*(C'\fR, this option is equivalent to \fB\-funroll-loops\fR
  but possibly slower.
! .Ip "\fB\-fno-move-all-movables\fR" 4
  .IX Item "-fno-move-all-movables"
  .PD 0
! .Ip "\fB\-fno-reduce-all-givs\fR" 4
  .IX Item "-fno-reduce-all-givs"
! .Ip "\fB\-fno-rerun-loop-opt\fR" 4
  .IX Item "-fno-rerun-loop-opt"
  .PD
  In general, the optimizations enabled with these options will lead to
  faster code being generated by \s-1GNU\s0 Fortran; hence they are enabled by default
  when issuing the \fBg77\fR command.
  .Sp
! \&\fB\-fmove-all-movables\fR and \fB\-freduce-all-givs\fR will enable
  loop optimization to move all loop-invariant index computations in nested
  loops over multi-rank array dummy arguments out of these loops.
  .Sp
! \&\fB\-frerun-loop-opt\fR will move offset calculations resulting
  from the fact that Fortran arrays by default have a lower bound of 1
  out of the loops.
  .Sp
--- 1222,1250 ----
  to\-\-\-unrolling.  Loops written with \f(CW\*(C`IF\*(C'\fR and \f(CW\*(C`GOTO\*(C'\fR are not
  currently recognized as such.  This option unrolls only iterative
  \&\f(CW\*(C`DO\*(C'\fR loops, not \f(CW\*(C`DO WHILE\*(C'\fR loops.
! .IP "\fB\-funroll\-all\-loops\fR" 4
  .IX Item "-funroll-all-loops"
  Probably improves performance on code using \f(CW\*(C`DO WHILE\*(C'\fR loops by
  unrolling them in addition to iterative \f(CW\*(C`DO\*(C'\fR loops.  In the absence
! of \f(CW\*(C`DO WHILE\*(C'\fR, this option is equivalent to \fB\-funroll\-loops\fR
  but possibly slower.
! .IP "\fB\-fno\-move\-all\-movables\fR" 4
  .IX Item "-fno-move-all-movables"
  .PD 0
! .IP "\fB\-fno\-reduce\-all\-givs\fR" 4
  .IX Item "-fno-reduce-all-givs"
! .IP "\fB\-fno\-rerun\-loop\-opt\fR" 4
  .IX Item "-fno-rerun-loop-opt"
  .PD
  In general, the optimizations enabled with these options will lead to
  faster code being generated by \s-1GNU\s0 Fortran; hence they are enabled by default
  when issuing the \fBg77\fR command.
  .Sp
! \&\fB\-fmove\-all\-movables\fR and \fB\-freduce\-all\-givs\fR will enable
  loop optimization to move all loop-invariant index computations in nested
  loops over multi-rank array dummy arguments out of these loops.
  .Sp
! \&\fB\-frerun\-loop\-opt\fR will move offset calculations resulting
  from the fact that Fortran arrays by default have a lower bound of 1
  out of the loops.
  .Sp
*************** for files specified via the \f(CW\*(C`IN
*** 1271,1280 ****
  although files included by that directive are not,
  themselves, preprocessed.
  These options are:
! .Ip "\fB\-I-\fR" 4
  .IX Item "-I-"
  .PD 0
! .Ip "\fB\-I\fR\fIdir\fR" 4
  .IX Item "-Idir"
  .PD
  These affect interpretation of the \f(CW\*(C`INCLUDE\*(C'\fR directive
--- 1283,1292 ----
  although files included by that directive are not,
  themselves, preprocessed.
  These options are:
! .IP "\fB\-I\-\fR" 4
  .IX Item "-I-"
  .PD 0
! .IP "\fB\-I\fR\fIdir\fR" 4
  .IX Item "-Idir"
  .PD
  These affect interpretation of the \f(CW\*(C`INCLUDE\*(C'\fR directive
*************** These machine-independent options contro
*** 1296,1313 ****
  used in code generation.
  .PP
  Most of them have both positive and negative forms; the negative form
! of \fB\-ffoo\fR would be \fB\-fno-foo\fR.  In the table below, only
  one of the forms is listed\-\-\-the one which is not the default.  You
! can figure out the other form by either removing \fBno-\fR or adding
  it.
! .Ip "\fB\-fno-automatic\fR" 4
  .IX Item "-fno-automatic"
  Treat each program unit as if the \f(CW\*(C`SAVE\*(C'\fR statement was specified
  for every local variable and array referenced in it.
  Does not affect common blocks.
  (Some Fortran compilers provide this option under
  the name \fB\-static\fR.)
! .Ip "\fB\-finit-local-zero\fR" 4
  .IX Item "-finit-local-zero"
  Specify that variables and arrays that are local to a program unit
  (not in a common block and not passed as an argument) are to be initialized
--- 1308,1325 ----
  used in code generation.
  .PP
  Most of them have both positive and negative forms; the negative form
! of \fB\-ffoo\fR would be \fB\-fno\-foo\fR.  In the table below, only
  one of the forms is listed\-\-\-the one which is not the default.  You
! can figure out the other form by either removing \fBno\-\fR or adding
  it.
! .IP "\fB\-fno\-automatic\fR" 4
  .IX Item "-fno-automatic"
  Treat each program unit as if the \f(CW\*(C`SAVE\*(C'\fR statement was specified
  for every local variable and array referenced in it.
  Does not affect common blocks.
  (Some Fortran compilers provide this option under
  the name \fB\-static\fR.)
! .IP "\fB\-finit\-local\-zero\fR" 4
  .IX Item "-finit-local-zero"
  Specify that variables and arrays that are local to a program unit
  (not in a common block and not passed as an argument) are to be initialized
*************** to binary zeros.
*** 1315,1322 ****
  .Sp
  Since there is a run-time penalty for initialization of variables
  that are not given the \f(CW\*(C`SAVE\*(C'\fR attribute, it might be a
! good idea to also use \fB\-fno-automatic\fR with \fB\-finit-local-zero\fR.
! .Ip "\fB\-fno-f2c\fR" 4
  .IX Item "-fno-f2c"
  Do not generate code designed to be compatible with code generated
  by \fBf2c\fR use the \s-1GNU\s0 calling conventions instead.
--- 1327,1334 ----
  .Sp
  Since there is a run-time penalty for initialization of variables
  that are not given the \f(CW\*(C`SAVE\*(C'\fR attribute, it might be a
! good idea to also use \fB\-fno\-automatic\fR with \fB\-finit\-local\-zero\fR.
! .IP "\fB\-fno\-f2c\fR" 4
  .IX Item "-fno-f2c"
  Do not generate code designed to be compatible with code generated
  by \fBf2c\fR use the \s-1GNU\s0 calling conventions instead.
*************** and functions that return type \f(CW\*(C
*** 1327,1333 ****
  values via an extra argument in the calling sequence that points
  to where to store the return value.
  Under the \s-1GNU\s0 calling conventions, such functions simply return
! their results as they would in \s-1GNU\s0 C\-\--\f(CW\*(C`REAL(KIND=1)\*(C'\fR functions
  return the C type \f(CW\*(C`float\*(C'\fR, and \f(CW\*(C`COMPLEX\*(C'\fR functions
  return the \s-1GNU\s0 C type \f(CW\*(C`complex\*(C'\fR (or its \f(CW\*(C`struct\*(C'\fR
  equivalent).
--- 1339,1345 ----
  values via an extra argument in the calling sequence that points
  to where to store the return value.
  Under the \s-1GNU\s0 calling conventions, such functions simply return
! their results as they would in \s-1GNU\s0 C\-\-\-\f(CW\*(C`REAL(KIND=1)\*(C'\fR functions
  return the C type \f(CW\*(C`float\*(C'\fR, and \f(CW\*(C`COMPLEX\*(C'\fR functions
  return the \s-1GNU\s0 C type \f(CW\*(C`complex\*(C'\fR (or its \f(CW\*(C`struct\*(C'\fR
  equivalent).
*************** This does not affect the generation of c
*** 1338,1373 ****
  However, because the \f(CW\*(C`libg2c\*(C'\fR library uses \fBf2c\fR
  calling conventions, \fBg77\fR rejects attempts to pass
  intrinsics implemented by routines in this library as actual
! arguments when \fB\-fno-f2c\fR is used, to avoid bugs when
  they are actually called by code expecting the \s-1GNU\s0 calling
  conventions to work.
  .Sp
! For example, \fB\s-1INTRINSIC\s0 \s-1ABS\s0;CALL FOO(\s-1ABS\s0)\fR is
! rejected when \fB\-fno-f2c\fR is in force.
  (Future versions of the \fBg77\fR run-time library might
  offer routines that provide GNU-callable versions of the
  routines that implement the \fBf2c\fR intrinsics
  that may be passed as actual arguments, so that
! valid programs need not be rejected when \fB\-fno-f2c\fR
  is used.)
  .Sp
! \&\fBCaution:\fR If \fB\-fno-f2c\fR is used when compiling any
  source file used in a program, it must be used when compiling
  \&\fIall\fR Fortran source files used in that program.
! .Ip "\fB\-ff2c-library\fR" 4
  .IX Item "-ff2c-library"
  Specify that use of \f(CW\*(C`libg2c\*(C'\fR (or the original \f(CW\*(C`libf2c\*(C'\fR)
  is required.
  This is the default for the current version of \fBg77\fR
  .Sp
  Currently it is not
! valid to specify \fB\-fno-f2c-library\fR.
  This option is provided so users can specify it in shell
  scripts that build programs and libraries that require the
  \&\f(CW\*(C`libf2c\*(C'\fR library, even when being compiled by future
  versions of \fBg77\fR that might otherwise default to
  generating code for an incompatible library.
! .Ip "\fB\-fno-underscoring\fR" 4
  .IX Item "-fno-underscoring"
  Do not transform names of entities specified in the Fortran
  source file by appending underscores to them.
--- 1350,1385 ----
  However, because the \f(CW\*(C`libg2c\*(C'\fR library uses \fBf2c\fR
  calling conventions, \fBg77\fR rejects attempts to pass
  intrinsics implemented by routines in this library as actual
! arguments when \fB\-fno\-f2c\fR is used, to avoid bugs when
  they are actually called by code expecting the \s-1GNU\s0 calling
  conventions to work.
  .Sp
! For example, \fB\s-1INTRINSIC\s0 \s-1ABS\s0;CALL \s-1FOO\s0(\s-1ABS\s0)\fR is
! rejected when \fB\-fno\-f2c\fR is in force.
  (Future versions of the \fBg77\fR run-time library might
  offer routines that provide GNU-callable versions of the
  routines that implement the \fBf2c\fR intrinsics
  that may be passed as actual arguments, so that
! valid programs need not be rejected when \fB\-fno\-f2c\fR
  is used.)
  .Sp
! \&\fBCaution:\fR If \fB\-fno\-f2c\fR is used when compiling any
  source file used in a program, it must be used when compiling
  \&\fIall\fR Fortran source files used in that program.
! .IP "\fB\-ff2c\-library\fR" 4
  .IX Item "-ff2c-library"
  Specify that use of \f(CW\*(C`libg2c\*(C'\fR (or the original \f(CW\*(C`libf2c\*(C'\fR)
  is required.
  This is the default for the current version of \fBg77\fR
  .Sp
  Currently it is not
! valid to specify \fB\-fno\-f2c\-library\fR.
  This option is provided so users can specify it in shell
  scripts that build programs and libraries that require the
  \&\f(CW\*(C`libf2c\*(C'\fR library, even when being compiled by future
  versions of \fBg77\fR that might otherwise default to
  generating code for an incompatible library.
! .IP "\fB\-fno\-underscoring\fR" 4
  .IX Item "-fno-underscoring"
  Do not transform names of entities specified in the Fortran
  source file by appending underscores to them.
*************** With \fB\-funderscoring\fR in effect, \f
*** 1376,1412 ****
  to names with underscores and one underscore to external names with
  no underscores.  (\fBg77\fR also appends two underscores to internal
  names with underscores to avoid naming collisions with external names.
! The \fB\-fno-second-underscore\fR option disables appending of the
  second underscore in all cases.)
  .Sp
  This is done to ensure compatibility with code produced by many
  \&\s-1UNIX\s0 Fortran compilers, including \fBf2c\fR which perform the
  same transformations.
  .Sp
! Use of \fB\-fno-underscoring\fR is not recommended unless you are
  experimenting with issues such as integration of (\s-1GNU\s0) Fortran into
! existing system environments (vis-a-vis existing libraries, tools, and
  so on).
  .Sp
  For example, with \fB\-funderscoring\fR, and assuming other defaults like
! \&\fB\-fcase-lower\fR and that \fB\f(BIj()\fB\fR and \fB\f(BImax_count()\fB\fR are
  external functions while \fBmy_var\fR and \fBlvar\fR are local variables,
  a statement like
  .Sp
  .Vb 1
  \&        I = J() + MAX_COUNT (MY_VAR, LVAR)
  .Ve
  is implemented as something akin to:
  .Sp
  .Vb 1
  \&        i = j_() + max_count__(&my_var__, &lvar);
  .Ve
! With \fB\-fno-underscoring\fR, the same statement is implemented as:
  .Sp
  .Vb 1
  \&        i = j() + max_count(&my_var, &lvar);
  .Ve
! Use of \fB\-fno-underscoring\fR allows direct specification of
  user-defined names while debugging and when interfacing \fBg77\fR
  code with other languages.
  .Sp
--- 1388,1427 ----
  to names with underscores and one underscore to external names with
  no underscores.  (\fBg77\fR also appends two underscores to internal
  names with underscores to avoid naming collisions with external names.
! The \fB\-fno\-second\-underscore\fR option disables appending of the
  second underscore in all cases.)
  .Sp
  This is done to ensure compatibility with code produced by many
  \&\s-1UNIX\s0 Fortran compilers, including \fBf2c\fR which perform the
  same transformations.
  .Sp
! Use of \fB\-fno\-underscoring\fR is not recommended unless you are
  experimenting with issues such as integration of (\s-1GNU\s0) Fortran into
! existing system environments (vis\-a\-vis existing libraries, tools, and
  so on).
  .Sp
  For example, with \fB\-funderscoring\fR, and assuming other defaults like
! \&\fB\-fcase\-lower\fR and that \fBj()\fR and \fB\f(BImax_count()\fB\fR are
  external functions while \fBmy_var\fR and \fBlvar\fR are local variables,
  a statement like
  .Sp
  .Vb 1
  \&        I = J() + MAX_COUNT (MY_VAR, LVAR)
  .Ve
+ .Sp
  is implemented as something akin to:
  .Sp
  .Vb 1
  \&        i = j_() + max_count__(&my_var__, &lvar);
  .Ve
! .Sp
! With \fB\-fno\-underscoring\fR, the same statement is implemented as:
  .Sp
  .Vb 1
  \&        i = j() + max_count(&my_var, &lvar);
  .Ve
! .Sp
! Use of \fB\-fno\-underscoring\fR allows direct specification of
  user-defined names while debugging and when interfacing \fBg77\fR
  code with other languages.
  .Sp
*************** both compilers to agree on issues other 
*** 1420,1426 ****
  significant effort, and, unlike naming disagreements, linkers normally
  cannot detect disagreements in these other areas.
  .Sp
! Also, note that with \fB\-fno-underscoring\fR, the lack of appended
  underscores introduces the very real possibility that a user-defined
  external name will conflict with a name in a system library, which
  could make finding unresolved-reference bugs quite difficult in some
--- 1435,1441 ----
  significant effort, and, unlike naming disagreements, linkers normally
  cannot detect disagreements in these other areas.
  .Sp
! Also, note that with \fB\-fno\-underscoring\fR, the lack of appended
  underscores introduces the very real possibility that a user-defined
  external name will conflict with a name in a system library, which
  could make finding unresolved-reference bugs quite difficult in some
*************** issues so that debugging always involves
*** 1432,1452 ****
  in the source, even if the names as seen by the linker are mangled to
  prevent accidental linking between procedures with incompatible
  interfaces.
! .Ip "\fB\-fno-second-underscore\fR" 4
  .IX Item "-fno-second-underscore"
  Do not append a second underscore to names of entities specified
  in the Fortran source file.
  .Sp
! This option has no effect if \fB\-fno-underscoring\fR is
  in effect.
  .Sp
  Otherwise, with this option, an external name such as \fB\s-1MAX_COUNT\s0\fR
  is implemented as a reference to the link-time external symbol
  \&\fBmax_count_\fR, instead of \fBmax_count_\|_\fR.
! .Ip "\fB\-fno-ident\fR" 4
  .IX Item "-fno-ident"
  Ignore the \fB#ident\fR directive.
! .Ip "\fB\-fzeros\fR" 4
  .IX Item "-fzeros"
  Treat initial values of zero as if they were any other value.
  .Sp
--- 1447,1467 ----
  in the source, even if the names as seen by the linker are mangled to
  prevent accidental linking between procedures with incompatible
  interfaces.
! .IP "\fB\-fno\-second\-underscore\fR" 4
  .IX Item "-fno-second-underscore"
  Do not append a second underscore to names of entities specified
  in the Fortran source file.
  .Sp
! This option has no effect if \fB\-fno\-underscoring\fR is
  in effect.
  .Sp
  Otherwise, with this option, an external name such as \fB\s-1MAX_COUNT\s0\fR
  is implemented as a reference to the link-time external symbol
  \&\fBmax_count_\fR, instead of \fBmax_count_\|_\fR.
! .IP "\fB\-fno\-ident\fR" 4
  .IX Item "-fno-ident"
  Ignore the \fB#ident\fR directive.
! .IP "\fB\-fzeros\fR" 4
  .IX Item "-fzeros"
  Treat initial values of zero as if they were any other value.
  .Sp
*************** all initializations, zero or otherwise.
*** 1468,1474 ****
  differently.
  The interpretation changes will affect only non-standard
  programs; standard-conforming programs should not be affected.
! .Ip "\fB\-femulate-complex\fR" 4
  .IX Item "-femulate-complex"
  Implement \f(CW\*(C`COMPLEX\*(C'\fR arithmetic via emulation,
  instead of using the facilities of
--- 1483,1489 ----
  differently.
  The interpretation changes will affect only non-standard
  programs; standard-conforming programs should not be affected.
! .IP "\fB\-femulate\-complex\fR" 4
  .IX Item "-femulate-complex"
  Implement \f(CW\*(C`COMPLEX\*(C'\fR arithmetic via emulation,
  instead of using the facilities of
*************** the \fBgcc\fR back end that provide dire
*** 1479,1485 ****
  for \f(CW\*(C`complex\*(C'\fR arithmetic, due primarily to the support not being
  completed as of version 2.8.1 and \f(CW\*(C`egcs\*(C'\fR 1.1.2.)
  .Sp
! Use \fB\-femulate-complex\fR if you suspect code-generation bugs,
  or experience compiler crashes,
  that might result from \fBg77\fR using the \f(CW\*(C`COMPLEX\*(C'\fR support
  in the \fBgcc\fR back end.
--- 1494,1500 ----
  for \f(CW\*(C`complex\*(C'\fR arithmetic, due primarily to the support not being
  completed as of version 2.8.1 and \f(CW\*(C`egcs\*(C'\fR 1.1.2.)
  .Sp
! Use \fB\-femulate\-complex\fR if you suspect code-generation bugs,
  or experience compiler crashes,
  that might result from \fBg77\fR using the \f(CW\*(C`COMPLEX\*(C'\fR support
  in the \fBgcc\fR back end.
*************** As of \s-1GCC\s0 version 3.0, this optio
*** 1498,1511 ****
  .Sp
  \&\fICaution:\fR Future versions of \fBg77\fR might ignore both forms
  of this option.
! .Ip "\fB\-falias-check\fR" 4
  .IX Item "-falias-check"
  .PD 0
! .Ip "\fB\-fargument-alias\fR" 4
  .IX Item "-fargument-alias"
! .Ip "\fB\-fargument-noalias\fR" 4
  .IX Item "-fargument-noalias"
! .Ip "\fB\-fno-argument-noalias-global\fR" 4
  .IX Item "-fno-argument-noalias-global"
  .PD
  \&\fIVersion info:\fR
--- 1513,1526 ----
  .Sp
  \&\fICaution:\fR Future versions of \fBg77\fR might ignore both forms
  of this option.
! .IP "\fB\-falias\-check\fR" 4
  .IX Item "-falias-check"
  .PD 0
! .IP "\fB\-fargument\-alias\fR" 4
  .IX Item "-fargument-alias"
! .IP "\fB\-fargument\-noalias\fR" 4
  .IX Item "-fargument-noalias"
! .IP "\fB\-fno\-argument\-noalias\-global\fR" 4
  .IX Item "-fno-argument-noalias-global"
  .PD
  \&\fIVersion info:\fR
*************** arguments (passed as pointers) and \f(CW
*** 1519,1532 ****
  public) storage.
  .Sp
  The default for Fortran code, as mandated by the \s-1FORTRAN\s0 77 and
! Fortran 90 standards, is \fB\-fargument-noalias-global\fR.
  The default for code written in the C language family is
! \&\fB\-fargument-alias\fR.
  .Sp
! Note that, on some systems, compiling with \fB\-fforce-addr\fR in
  effect can produce more optimal code when the default aliasing
  options are in effect (and when optimization is enabled).
! .Ip "\fB\-fno-globals\fR" 4
  .IX Item "-fno-globals"
  Disable diagnostics about inter-procedural
  analysis problems, such as disagreements about the
--- 1534,1547 ----
  public) storage.
  .Sp
  The default for Fortran code, as mandated by the \s-1FORTRAN\s0 77 and
! Fortran 90 standards, is \fB\-fargument\-noalias\-global\fR.
  The default for code written in the C language family is
! \&\fB\-fargument\-alias\fR.
  .Sp
! Note that, on some systems, compiling with \fB\-fforce\-addr\fR in
  effect can produce more optimal code when the default aliasing
  options are in effect (and when optimization is enabled).
! .IP "\fB\-fno\-globals\fR" 4
  .IX Item "-fno-globals"
  Disable diagnostics about inter-procedural
  analysis problems, such as disagreements about the
*************** that might cause a compiler crash when a
*** 1535,1541 ****
  to inline a reference to a procedure within a
  program unit.
  (The diagnostics themselves are still produced, but
! as warnings, unless \fB\-Wno-globals\fR is specified,
  in which case no relevant diagnostics are produced.)
  .Sp
  Further, this option disables such inlining, to
--- 1550,1556 ----
  to inline a reference to a procedure within a
  program unit.
  (The diagnostics themselves are still produced, but
! as warnings, unless \fB\-Wno\-globals\fR is specified,
  in which case no relevant diagnostics are produced.)
  .Sp
  Further, this option disables such inlining, to
*************** and warns about similar disagreements
*** 1564,1572 ****
  that are currently believed to not
  likely to result in the compiler later crashing
  or producing incorrect code.
! .Ip "\fB\-fflatten-arrays\fR" 4
  .IX Item "-fflatten-arrays"
! Use back end's C-like constructs
  (pointer plus offset)
  instead of its \f(CW\*(C`ARRAY_REF\*(C'\fR construct
  to handle all array references.
--- 1579,1587 ----
  that are currently believed to not
  likely to result in the compiler later crashing
  or producing incorrect code.
! .IP "\fB\-fflatten\-arrays\fR" 4
  .IX Item "-fflatten-arrays"
! Use back end's C\-like constructs
  (pointer plus offset)
  instead of its \f(CW\*(C`ARRAY_REF\*(C'\fR construct
  to handle all array references.
*************** to handle all array references.
*** 1575,1584 ****
  It is intended for use only by \fBg77\fR developers,
  to evaluate code-generation issues.
  It might be removed at any time.
! .Ip "\fB\-fbounds-check\fR" 4
  .IX Item "-fbounds-check"
  .PD 0
! .Ip "\fB\-ffortran-bounds-check\fR" 4
  .IX Item "-ffortran-bounds-check"
  .PD
  Enable generation of run-time checks for array subscripts
--- 1590,1599 ----
  It is intended for use only by \fBg77\fR developers,
  to evaluate code-generation issues.
  It might be removed at any time.
! .IP "\fB\-fbounds\-check\fR" 4
  .IX Item "-fbounds-check"
  .PD 0
! .IP "\fB\-ffortran\-bounds\-check\fR" 4
  .IX Item "-ffortran-bounds-check"
  .PD
  Enable generation of run-time checks for array subscripts
*************** such as references to below the beginnin
*** 1598,1604 ****
  \&\fBg77\fR also generates checks for \f(CW\*(C`CHARACTER\*(C'\fR substring references,
  something \fBf2c\fR currently does not do.
  .Sp
! Use the new \fB\-ffortran-bounds-check\fR option
  to specify bounds-checking for only the Fortran code you are compiling,
  not necessarily for code written in other languages.
  .Sp
--- 1613,1619 ----
  \&\fBg77\fR also generates checks for \f(CW\*(C`CHARACTER\*(C'\fR substring references,
  something \fBf2c\fR currently does not do.
  .Sp
! Use the new \fB\-ffortran\-bounds\-check\fR option
  to specify bounds-checking for only the Fortran code you are compiling,
  not necessarily for code written in other languages.
  .Sp
*************** Here's a sample diagnostic:
*** 1612,1617 ****
--- 1627,1633 ----
  \&        Attempt to access the -6-th element of variable b[subscript-2-of-2].
  \&        Aborted
  .Ve
+ .Sp
  The above message indicates that the offending source line is
  line 4 of the file \fIrnge.f\fR,
  within the program unit (or statement function) named \fBbf\fR.
*************** this appearance:
*** 1625,1630 ****
--- 1641,1647 ----
  .Vb 1
  \&        Attempt to access the 11-th element of variable a[start-substring].
  .Ve
+ .Sp
  This indicates that the offended \f(CW\*(C`CHARACTER\*(C'\fR variable or array
  is named \fBa\fR,
  the offended substring position is the starting (leftmost) position,
*************** the above information should provide ade
*** 1636,1660 ****
  to it users.)
  .PP
  Some of these do \fInot\fR work when compiling programs written in Fortran:
! .Ip "\fB\-fpcc-struct-return\fR" 4
  .IX Item "-fpcc-struct-return"
  .PD 0
! .Ip "\fB\-freg-struct-return\fR" 4
  .IX Item "-freg-struct-return"
  .PD
  You should not use these except strictly the same way as you
  used them to build the version of \f(CW\*(C`libg2c\*(C'\fR with which
  you will be linking all code compiled by \fBg77\fR with the
  same option.
! .Ip "\fB\-fshort-double\fR" 4
  .IX Item "-fshort-double"
  This probably either has no effect on Fortran programs, or
  makes them act loopy.
! .Ip "\fB\-fno-common\fR" 4
  .IX Item "-fno-common"
  Do not use this when compiling Fortran programs,
  or there will be Trouble.
! .Ip "\fB\-fpack-struct\fR" 4
  .IX Item "-fpack-struct"
  This probably will break any calls to the \f(CW\*(C`libg2c\*(C'\fR library,
  at the very least, even if it is built with the same option.
--- 1653,1677 ----
  to it users.)
  .PP
  Some of these do \fInot\fR work when compiling programs written in Fortran:
! .IP "\fB\-fpcc\-struct\-return\fR" 4
  .IX Item "-fpcc-struct-return"
  .PD 0
! .IP "\fB\-freg\-struct\-return\fR" 4
  .IX Item "-freg-struct-return"
  .PD
  You should not use these except strictly the same way as you
  used them to build the version of \f(CW\*(C`libg2c\*(C'\fR with which
  you will be linking all code compiled by \fBg77\fR with the
  same option.
! .IP "\fB\-fshort\-double\fR" 4
  .IX Item "-fshort-double"
  This probably either has no effect on Fortran programs, or
  makes them act loopy.
! .IP "\fB\-fno\-common\fR" 4
  .IX Item "-fno-common"
  Do not use this when compiling Fortran programs,
  or there will be Trouble.
! .IP "\fB\-fpack\-struct\fR" 4
  .IX Item "-fpack-struct"
  This probably will break any calls to the \f(CW\*(C`libg2c\*(C'\fR library,
  at the very least, even if it is built with the same option.
*************** For instructions on reporting bugs, see
*** 1670,1676 ****
  script to report bugs is recommended.
  .SH "FOOTNOTES"
  .IX Header "FOOTNOTES"
! .Ip "1." 4
  \&\fIloop discovery\fR refers to the
  process by which a compiler, or indeed any reader of a program,
  determines which portions of the program are more likely to be executed
--- 1687,1693 ----
  script to report bugs is recommended.
  .SH "FOOTNOTES"
  .IX Header "FOOTNOTES"
! .IP "1." 4
  \&\fIloop discovery\fR refers to the
  process by which a compiler, or indeed any reader of a program,
  determines which portions of the program are more likely to be executed
*************** constructed out of lower-level construct
*** 1685,1691 ****
  than otherwise.
  .SH "SEE ALSO"
  .IX Header "SEE ALSO"
! \&\fIgpl\fR\|(7), \fIgfdl\fR\|(7), \fIfsf-funding\fR\|(7),
  \&\fIcpp\fR\|(1), \fIgcov\fR\|(1), \fIgcc\fR\|(1), \fIas\fR\|(1), \fIld\fR\|(1), \fIgdb\fR\|(1), \fIadb\fR\|(1), \fIdbx\fR\|(1), \fIsdb\fR\|(1)
  and the Info entries for \fIgcc\fR, \fIcpp\fR, \fIg77\fR, \fIas\fR,
  \&\fIld\fR, \fIbinutils\fR and \fIgdb\fR.
--- 1702,1708 ----
  than otherwise.
  .SH "SEE ALSO"
  .IX Header "SEE ALSO"
! \&\fIgpl\fR\|(7), \fIgfdl\fR\|(7), \fIfsf\-funding\fR\|(7),
  \&\fIcpp\fR\|(1), \fIgcov\fR\|(1), \fIgcc\fR\|(1), \fIas\fR\|(1), \fIld\fR\|(1), \fIgdb\fR\|(1), \fIadb\fR\|(1), \fIdbx\fR\|(1), \fIsdb\fR\|(1)
  and the Info entries for \fIgcc\fR, \fIcpp\fR, \fIg77\fR, \fIas\fR,
  \&\fIld\fR, \fIbinutils\fR and \fIgdb\fR.
*************** Copyright (c) 1996, 1997, 1998, 1999, 20
*** 1698,1704 ****
  Free Software Foundation, Inc.
  .PP
  Permission is granted to copy, distribute and/or modify this document
! under the terms of the \s-1GNU\s0 Free Documentation License, Version 1.1 or
  any later version published by the Free Software Foundation; with the
  Invariant Sections being ``\s-1GNU\s0 General Public License'' and ``Funding
  Free Software'', the Front-Cover texts being (a) (see below), and with
--- 1715,1721 ----
  Free Software Foundation, Inc.
  .PP
  Permission is granted to copy, distribute and/or modify this document
! under the terms of the \s-1GNU\s0 Free Documentation License, Version 1.2 or
  any later version published by the Free Software Foundation; with the
  Invariant Sections being ``\s-1GNU\s0 General Public License'' and ``Funding
  Free Software'', the Front-Cover texts being (a) (see below), and with
*************** included in the \fIgfdl\fR\|(7) man page
*** 1710,1715 ****
--- 1727,1733 ----
  .Vb 1
  \&     A GNU Manual
  .Ve
+ .PP
  (b) The \s-1FSF\s0's Back-Cover Text is:
  .PP
  .Vb 3
diff -Nrc3pad gcc-3.2.3/gcc/f/g77.info gcc-3.3/gcc/f/g77.info
*** gcc-3.2.3/gcc/f/g77.info	2003-04-22 07:07:25.000000000 +0000
--- gcc-3.3/gcc/f/g77.info	2003-05-14 00:31:48.000000000 +0000
***************
*** 1,20 ****
! This is g77.info, produced by makeinfo version 4.5 from g77.texi.
  
  INFO-DIR-SECTION Programming
  START-INFO-DIR-ENTRY
  * g77: (g77).                  The GNU Fortran compiler.
  END-INFO-DIR-ENTRY
     This file documents the use and the internals of the GNU Fortran
! (`g77') compiler.  It corresponds to the GCC-3.2.3 version of `g77'.
  
     Published by the Free Software Foundation 59 Temple Place - Suite 330
  Boston, MA 02111-1307 USA
  
!    Copyright (C) 1995,1996,1997,1998,1999,2000,2001,2002 Free Software
  Foundation, Inc.
  
     Permission is granted to copy, distribute and/or modify this document
! under the terms of the GNU Free Documentation License, Version 1.1 or
  any later version published by the Free Software Foundation; with the
  Invariant Sections being "GNU General Public License" and "Funding Free
  Software", the Front-Cover texts being (a) (see below), and with the
--- 1,40 ----
! This is g77.info, produced by makeinfo version 4.2 from g77.texi.
! 
! Copyright (C) 1995,1996,1997,1998,1999,2000,2001,2002 Free Software
! Foundation, Inc.
! 
!    Permission is granted to copy, distribute and/or modify this document
! under the terms of the GNU Free Documentation License, Version 1.2 or
! any later version published by the Free Software Foundation; with the
! Invariant Sections being "GNU General Public License" and "Funding Free
! Software", the Front-Cover texts being (a) (see below), and with the
! Back-Cover Texts being (b) (see below).  A copy of the license is
! included in the section entitled "GNU Free Documentation License".
! 
!    (a) The FSF's Front-Cover Text is:
! 
!    A GNU Manual
  
+    (b) The FSF's Back-Cover Text is:
+ 
+    You have freedom to copy and modify this GNU Manual, like GNU
+ software.  Copies published by the Free Software Foundation raise
+ funds for GNU development.
  INFO-DIR-SECTION Programming
  START-INFO-DIR-ENTRY
  * g77: (g77).                  The GNU Fortran compiler.
  END-INFO-DIR-ENTRY
     This file documents the use and the internals of the GNU Fortran
! (`g77') compiler.  It corresponds to the GCC-3.3 version of `g77'.
  
     Published by the Free Software Foundation 59 Temple Place - Suite 330
  Boston, MA 02111-1307 USA
  
! Copyright (C) 1995,1996,1997,1998,1999,2000,2001,2002 Free Software
  Foundation, Inc.
  
     Permission is granted to copy, distribute and/or modify this document
! under the terms of the GNU Free Documentation License, Version 1.2 or
  any later version published by the Free Software Foundation; with the
  Invariant Sections being "GNU General Public License" and "Funding Free
  Software", the Front-Cover texts being (a) (see below), and with the
*************** included in the section entitled "GNU Fr
*** 30,765 ****
     You have freedom to copy and modify this GNU Manual, like GNU
  software.  Copies published by the Free Software Foundation raise
  funds for GNU development.
- 
     Contributed by James Craig Burley (<craig@jcb-sc.com>).  Inspired by
  a first pass at translating `g77-0.5.16/f/DOC' that was contributed to
  Craig by David Ronis (<ronis@onsager.chem.mcgill.ca>).
  
  
! Indirect:
! g77.info-1: 1460
! g77.info-2: 49509
! g77.info-3: 98817
! g77.info-4: 124552
! g77.info-5: 176715
! g77.info-6: 225206
! g77.info-7: 270209
! g77.info-8: 319613
! g77.info-9: 369073
! g77.info-10: 418640
! g77.info-11: 463040
! g77.info-12: 512588
! g77.info-13: 562579
! g77.info-14: 609603
! g77.info-15: 653767
! g77.info-16: 701448
! g77.info-17: 751000
! g77.info-18: 799364
! g77.info-19: 841909
! g77.info-20: 885662
! g77.info-21: 904652
  
  Tag Table:
! (Indirect)
! Node: Top1460
! Node: Copying3417
! Node: GNU Free Documentation License22620
! Node: Contributors42504
! Node: Funding45783
! Node: Funding GNU Fortran48295
! Node: Getting Started49509
! Node: What is GNU Fortran?51758
! Node: G77 and GCC61646
! Node: Invoking G7762864
! Node: Option Summary64802
! Node: Overall Options69642
! Node: Shorthand Options76383
! Node: Fortran Dialect Options78680
! Node: Warning Options89937
! Node: Debugging Options98817
! Node: Optimize Options100407
! Ref: Optimize Options-Footnote-1106004
! Node: Preprocessor Options106697
! Node: Directory Options107878
! Node: Code Gen Options109190
! Node: Environment Variables124097
! Node: News124552
! Node: Changes176715
! Node: Language202308
! Node: Direction of Language Development204511
! Node: Standard Support210750
! Node: No Passing External Assumed-length211471
! Node: No Passing Dummy Assumed-length211948
! Node: No Pathological Implied-DO212463
! Node: No Useless Implied-DO213150
! Node: Conformance213881
! Node: Notation Used215904
! Node: Terms and Concepts220110
! Node: Syntactic Items220622
! Node: Statements Comments Lines221304
! Node: Scope of Names and Labels223169
! Node: Characters Lines Sequence223599
! Node: Character Set224205
! Node: Lines225206
! Node: Continuation Line227682
! Node: Statements228637
! Node: Statement Labels229593
! Node: Order230285
! Node: INCLUDE231170
! Node: Cpp-style directives233942
! Node: Data Types and Constants234397
! Node: Types237918
! Node: Double Notation239007
! Node: Star Notation240079
! Node: Kind Notation243024
! Node: Constants251444
! Node: Integer Type252960
! Node: Character Type253558
! Node: Expressions254322
! Node: %LOC()254738
! Node: Specification Statements257468
! Node: NAMELIST257925
! Node: DOUBLE COMPLEX258676
! Node: Control Statements258930
! Node: DO WHILE259422
! Node: END DO259727
! Node: Construct Names260734
! Node: CYCLE and EXIT261474
! Node: Functions and Subroutines264238
! Node: %VAL()264884
! Node: %REF()266248
! Node: %DESCR()268076
! Node: Generics and Specifics270209
! Node: REAL() and AIMAG() of Complex277411
! Node: CMPLX() of DOUBLE PRECISION279244
! Node: MIL-STD 1753280970
! Node: f77/f2c Intrinsics281312
! Node: Table of Intrinsic Functions281882
! Node: Abort Intrinsic298594
! Node: Abs Intrinsic298858
! Node: Access Intrinsic299721
! Node: AChar Intrinsic300557
! Node: ACos Intrinsic301079
! Node: AdjustL Intrinsic301540
! Node: AdjustR Intrinsic301865
! Node: AImag Intrinsic302191
! Node: AInt Intrinsic302996
! Node: Alarm Intrinsic303624
! Node: All Intrinsic304456
! Node: Allocated Intrinsic304768
! Node: ALog Intrinsic305097
! Node: ALog10 Intrinsic305487
! Node: AMax0 Intrinsic305885
! Node: AMax1 Intrinsic306370
! Node: AMin0 Intrinsic306823
! Node: AMin1 Intrinsic307307
! Node: AMod Intrinsic307759
! Node: And Intrinsic308185
! Node: ANInt Intrinsic308691
! Node: Any Intrinsic309455
! Node: ASin Intrinsic309762
! Node: Associated Intrinsic310220
! Node: ATan Intrinsic310554
! Node: ATan2 Intrinsic311020
! Node: BesJ0 Intrinsic311571
! Node: BesJ1 Intrinsic312032
! Node: BesJN Intrinsic312493
! Node: BesY0 Intrinsic313024
! Node: BesY1 Intrinsic313486
! Node: BesYN Intrinsic313948
! Node: Bit_Size Intrinsic314483
! Node: BTest Intrinsic315142
! Node: CAbs Intrinsic315862
! Node: CCos Intrinsic316249
! Node: Ceiling Intrinsic316641
! Node: CExp Intrinsic316963
! Node: Char Intrinsic317355
! Node: ChDir Intrinsic (subroutine)318609
! Node: ChMod Intrinsic (subroutine)319613
! Node: CLog Intrinsic320884
! Node: Cmplx Intrinsic321288
! Node: Complex Intrinsic322089
! Node: Conjg Intrinsic323535
! Node: Cos Intrinsic323959
! Node: CosH Intrinsic324422
! Node: Count Intrinsic324797
! Node: CPU_Time Intrinsic325115
! Node: CShift Intrinsic325906
! Node: CSin Intrinsic326228
! Node: CSqRt Intrinsic326620
! Node: CTime Intrinsic (subroutine)327030
! Node: CTime Intrinsic (function)327785
! Node: DAbs Intrinsic328419
! Node: DACos Intrinsic328815
! Node: DASin Intrinsic329206
! Node: DATan Intrinsic329598
! Node: DATan2 Intrinsic329991
! Node: Date_and_Time Intrinsic330446
! Node: DbesJ0 Intrinsic331810
! Node: DbesJ1 Intrinsic332203
! Node: DbesJN Intrinsic332589
! Node: DbesY0 Intrinsic333045
! Node: DbesY1 Intrinsic333431
! Node: DbesYN Intrinsic333817
! Node: Dble Intrinsic334271
! Node: DCos Intrinsic334977
! Node: DCosH Intrinsic335361
! Node: DDiM Intrinsic335751
! Node: DErF Intrinsic336183
! Node: DErFC Intrinsic336552
! Node: DExp Intrinsic336927
! Node: Digits Intrinsic337313
! Node: DiM Intrinsic337630
! Node: DInt Intrinsic338129
! Node: DLog Intrinsic338513
! Node: DLog10 Intrinsic338898
! Node: DMax1 Intrinsic339296
! Node: DMin1 Intrinsic339750
! Node: DMod Intrinsic340202
! Node: DNInt Intrinsic340630
! Node: Dot_Product Intrinsic341029
! Node: DProd Intrinsic341369
! Node: DSign Intrinsic341751
! Node: DSin Intrinsic342190
! Node: DSinH Intrinsic342575
! Node: DSqRt Intrinsic342966
! Node: DTan Intrinsic343357
! Node: DTanH Intrinsic343742
! Node: DTime Intrinsic (subroutine)344146
! Node: EOShift Intrinsic345417
! Node: Epsilon Intrinsic345756
! Node: ErF Intrinsic346080
! Node: ErFC Intrinsic346486
! Node: ETime Intrinsic (subroutine)347046
! Node: ETime Intrinsic (function)348209
! Node: Exit Intrinsic349249
! Node: Exp Intrinsic349758
! Node: Exponent Intrinsic350220
! Node: FDate Intrinsic (subroutine)350559
! Node: FDate Intrinsic (function)351469
! Node: FGet Intrinsic (subroutine)352241
! Node: FGetC Intrinsic (subroutine)353078
! Node: Float Intrinsic353955
! Node: Floor Intrinsic354355
! Node: Flush Intrinsic354671
! Node: FNum Intrinsic355250
! Node: FPut Intrinsic (subroutine)355698
! Node: FPutC Intrinsic (subroutine)356495
! Node: Fraction Intrinsic357342
! Node: FSeek Intrinsic357683
! Node: FStat Intrinsic (subroutine)358408
! Node: FStat Intrinsic (function)359933
! Node: FTell Intrinsic (subroutine)361223
! Node: FTell Intrinsic (function)361896
! Node: GError Intrinsic362413
! Node: GetArg Intrinsic362787
! Node: GetCWD Intrinsic (subroutine)363455
! Node: GetCWD Intrinsic (function)364311
! Node: GetEnv Intrinsic364931
! Node: GetGId Intrinsic365518
! Node: GetLog Intrinsic365824
! Node: GetPId Intrinsic366362
! Node: GetUId Intrinsic366670
! Node: GMTime Intrinsic366975
! Node: HostNm Intrinsic (subroutine)367983
! Node: HostNm Intrinsic (function)369073
! Node: Huge Intrinsic369916
! Node: IAbs Intrinsic370239
! Node: IAChar Intrinsic370630
! Node: IAnd Intrinsic371170
! Node: IArgC Intrinsic371658
! Node: IBClr Intrinsic372034
! Node: IBits Intrinsic372545
! Node: IBSet Intrinsic373259
! Node: IChar Intrinsic373761
! Node: IDate Intrinsic (UNIX)374980
! Node: IDiM Intrinsic375783
! Node: IDInt Intrinsic376232
! Node: IDNInt Intrinsic376625
! Node: IEOr Intrinsic377024
! Node: IErrNo Intrinsic377522
! Node: IFix Intrinsic377849
! Node: Imag Intrinsic378237
! Node: ImagPart Intrinsic379242
! Node: Index Intrinsic380268
! Node: Int Intrinsic380821
! Node: Int2 Intrinsic381536
! Node: Int8 Intrinsic382246
! Node: IOr Intrinsic382956
! Node: IRand Intrinsic383436
! Node: IsaTty Intrinsic384356
! Node: IShft Intrinsic384780
! Node: IShftC Intrinsic385610
! Node: ISign Intrinsic386539
! Node: ITime Intrinsic386989
! Node: Kill Intrinsic (subroutine)387391
! Node: Kind Intrinsic388228
! Node: LBound Intrinsic388553
! Node: Len Intrinsic388870
! Node: Len_Trim Intrinsic389506
! Node: LGe Intrinsic389918
! Node: LGt Intrinsic391331
! Node: Link Intrinsic (subroutine)392236
! Node: LLe Intrinsic393201
! Node: LLt Intrinsic394106
! Node: LnBlnk Intrinsic395000
! Node: Loc Intrinsic395403
! Node: Log Intrinsic395834
! Node: Log10 Intrinsic396425
! Node: Logical Intrinsic396967
! Node: Long Intrinsic397290
! Node: LShift Intrinsic397814
! Node: LStat Intrinsic (subroutine)398850
! Node: LStat Intrinsic (function)400662
! Node: LTime Intrinsic402225
! Node: MatMul Intrinsic403229
! Node: Max Intrinsic403547
! Node: Max0 Intrinsic404098
! Node: Max1 Intrinsic404549
! Node: MaxExponent Intrinsic405033
! Node: MaxLoc Intrinsic405373
! Node: MaxVal Intrinsic405700
! Node: MClock Intrinsic406022
! Node: MClock8 Intrinsic406920
! Node: Merge Intrinsic408108
! Node: Min Intrinsic408424
! Node: Min0 Intrinsic408975
! Node: Min1 Intrinsic409426
! Node: MinExponent Intrinsic409910
! Node: MinLoc Intrinsic410250
! Node: MinVal Intrinsic410577
! Node: Mod Intrinsic410896
! Node: Modulo Intrinsic411419
! Node: MvBits Intrinsic411738
! Node: Nearest Intrinsic412604
! Node: NInt Intrinsic412928
! Node: Not Intrinsic413766
! Node: Or Intrinsic414161
! Node: Pack Intrinsic414659
! Node: PError Intrinsic414969
! Node: Precision Intrinsic415423
! Node: Present Intrinsic415758
! Node: Product Intrinsic416088
! Node: Radix Intrinsic416414
! Node: Rand Intrinsic416731
! Node: Random_Number Intrinsic417618
! Node: Random_Seed Intrinsic417971
! Node: Range Intrinsic418319
! Node: Real Intrinsic418640
! Node: RealPart Intrinsic419646
! Node: Rename Intrinsic (subroutine)420679
! Node: Repeat Intrinsic421651
! Node: Reshape Intrinsic421987
! Node: RRSpacing Intrinsic422316
! Node: RShift Intrinsic422651
! Node: Scale Intrinsic423649
! Node: Scan Intrinsic423965
! Node: Second Intrinsic (function)424289
! Node: Second Intrinsic (subroutine)425120
! Node: Selected_Int_Kind Intrinsic426095
! Node: Selected_Real_Kind Intrinsic426486
! Node: Set_Exponent Intrinsic426873
! Node: Shape Intrinsic427230
! Node: Short Intrinsic427553
! Node: Sign Intrinsic428249
! Node: Signal Intrinsic (subroutine)428849
! Node: Sin Intrinsic431063
! Node: SinH Intrinsic431538
! Node: Sleep Intrinsic431911
! Node: Sngl Intrinsic432253
! Node: Spacing Intrinsic432642
! Node: Spread Intrinsic432966
! Node: SqRt Intrinsic433287
! Node: SRand Intrinsic433891
! Node: Stat Intrinsic (subroutine)434268
! Node: Stat Intrinsic (function)435883
! Node: Sum Intrinsic437247
! Node: SymLnk Intrinsic (subroutine)437579
! Node: System Intrinsic (subroutine)438611
! Node: System_Clock Intrinsic439550
! Node: Tan Intrinsic440674
! Node: TanH Intrinsic441134
! Node: Time Intrinsic (UNIX)441516
! Node: Time8 Intrinsic442501
! Node: Tiny Intrinsic443680
! Node: Transfer Intrinsic443995
! Node: Transpose Intrinsic444326
! Node: Trim Intrinsic444660
! Node: TtyNam Intrinsic (subroutine)444990
! Node: TtyNam Intrinsic (function)445692
! Node: UBound Intrinsic446261
! Node: UMask Intrinsic (subroutine)446606
! Node: Unlink Intrinsic (subroutine)447303
! Node: Unpack Intrinsic448201
! Node: Verify Intrinsic448536
! Node: XOr Intrinsic448855
! Node: ZAbs Intrinsic449371
! Node: ZCos Intrinsic449740
! Node: ZExp Intrinsic450113
! Node: ZLog Intrinsic450486
! Node: ZSin Intrinsic450859
! Node: ZSqRt Intrinsic451233
! Node: Scope and Classes of Names451590
! Node: Underscores in Symbol Names452072
! Node: I/O452319
! Node: Fortran 90 Features453092
! Node: Other Dialects455894
! Node: Source Form457053
! Node: Carriage Returns458268
! Node: Tabs458597
! Node: Short Lines459470
! Node: Long Lines460444
! Node: Ampersands461055
! Node: Trailing Comment461309
! Node: Debug Line462085
! Node: Dollar Signs462754
! Node: Case Sensitivity463040
! Node: VXT Fortran471656
! Node: Double Quote Meaning472839
! Node: Exclamation Point473767
! Node: Fortran 90474810
! Node: Pedantic Compilation475862
! Node: Distensions479826
! Node: Ugly Implicit Argument Conversion480790
! Node: Ugly Assumed-Size Arrays481404
! Node: Ugly Complex Part Extraction483125
! Node: Ugly Null Arguments484747
! Node: Ugly Conversion of Initializers486350
! Node: Ugly Integer Conversions488115
! Node: Ugly Assigned Labels489223
! Node: Compiler491154
! Node: Compiler Limits491792
! Node: Run-time Environment Limits492683
! Node: Timer Wraparounds494625
! Node: Year 2000 (Y2K) Problems495904
! Node: Array Size500410
! Node: Character-variable Length501595
! Node: Year 10000 (Y10K) Problems502104
! Node: Compiler Types502650
! Node: Compiler Constants507361
! Node: Compiler Intrinsics508220
! Node: Intrinsic Groups509147
! Node: Other Intrinsics512588
! Node: ACosD Intrinsic520186
! Node: AIMax0 Intrinsic520467
! Node: AIMin0 Intrinsic520776
! Node: AJMax0 Intrinsic521086
! Node: AJMin0 Intrinsic521396
! Node: ASinD Intrinsic521705
! Node: ATan2D Intrinsic522011
! Node: ATanD Intrinsic522319
! Node: BITest Intrinsic522625
! Node: BJTest Intrinsic522934
! Node: CDAbs Intrinsic523243
! Node: CDCos Intrinsic523616
! Node: CDExp Intrinsic523991
! Node: CDLog Intrinsic524366
! Node: CDSin Intrinsic524741
! Node: CDSqRt Intrinsic525117
! Node: ChDir Intrinsic (function)525510
! Node: ChMod Intrinsic (function)526339
! Node: CosD Intrinsic527453
! Node: DACosD Intrinsic527765
! Node: DASinD Intrinsic528073
! Node: DATan2D Intrinsic528384
! Node: DATanD Intrinsic528698
! Node: Date Intrinsic529007
! Node: DbleQ Intrinsic529726
! Node: DCmplx Intrinsic530030
! Node: DConjg Intrinsic531661
! Node: DCosD Intrinsic532046
! Node: DFloat Intrinsic532352
! Node: DFlotI Intrinsic532724
! Node: DFlotJ Intrinsic533034
! Node: DImag Intrinsic533343
! Node: DReal Intrinsic533720
! Node: DSinD Intrinsic534867
! Node: DTanD Intrinsic535171
! Node: DTime Intrinsic (function)535486
! Node: FGet Intrinsic (function)536716
! Node: FGetC Intrinsic (function)537489
! Node: FloatI Intrinsic538305
! Node: FloatJ Intrinsic538625
! Node: FPut Intrinsic (function)538944
! Node: FPutC Intrinsic (function)539680
! Node: IDate Intrinsic (VXT)540473
! Node: IIAbs Intrinsic541517
! Node: IIAnd Intrinsic541827
! Node: IIBClr Intrinsic542132
! Node: IIBits Intrinsic542441
! Node: IIBSet Intrinsic542751
! Node: IIDiM Intrinsic543060
! Node: IIDInt Intrinsic543366
! Node: IIDNnt Intrinsic543675
! Node: IIEOr Intrinsic543984
! Node: IIFix Intrinsic544289
! Node: IInt Intrinsic544592
! Node: IIOr Intrinsic544891
! Node: IIQint Intrinsic545191
! Node: IIQNnt Intrinsic545499
! Node: IIShftC Intrinsic545810
! Node: IISign Intrinsic546124
! Node: IMax0 Intrinsic546434
! Node: IMax1 Intrinsic546739
! Node: IMin0 Intrinsic547043
! Node: IMin1 Intrinsic547347
! Node: IMod Intrinsic547650
! Node: INInt Intrinsic547950
! Node: INot Intrinsic548252
! Node: IZExt Intrinsic548552
! Node: JIAbs Intrinsic548855
! Node: JIAnd Intrinsic549159
! Node: JIBClr Intrinsic549464
! Node: JIBits Intrinsic549773
! Node: JIBSet Intrinsic550083
! Node: JIDiM Intrinsic550392
! Node: JIDInt Intrinsic550698
! Node: JIDNnt Intrinsic551007
! Node: JIEOr Intrinsic551316
! Node: JIFix Intrinsic551621
! Node: JInt Intrinsic551924
! Node: JIOr Intrinsic552223
! Node: JIQint Intrinsic552523
! Node: JIQNnt Intrinsic552831
! Node: JIShft Intrinsic553141
! Node: JIShftC Intrinsic553452
! Node: JISign Intrinsic553766
! Node: JMax0 Intrinsic554076
! Node: JMax1 Intrinsic554381
! Node: JMin0 Intrinsic554685
! Node: JMin1 Intrinsic554989
! Node: JMod Intrinsic555292
! Node: JNInt Intrinsic555592
! Node: JNot Intrinsic555894
! Node: JZExt Intrinsic556194
! Node: Kill Intrinsic (function)556507
! Node: Link Intrinsic (function)557189
! Node: QAbs Intrinsic558001
! Node: QACos Intrinsic558311
! Node: QACosD Intrinsic558615
! Node: QASin Intrinsic558923
! Node: QASinD Intrinsic559229
! Node: QATan Intrinsic559537
! Node: QATan2 Intrinsic559843
! Node: QATan2D Intrinsic560153
! Node: QATanD Intrinsic560467
! Node: QCos Intrinsic560776
! Node: QCosD Intrinsic561077
! Node: QCosH Intrinsic561380
! Node: QDiM Intrinsic561683
! Node: QExp Intrinsic561982
! Node: QExt Intrinsic562280
! Node: QExtD Intrinsic562579
! Node: QFloat Intrinsic562883
! Node: QInt Intrinsic563190
! Node: QLog Intrinsic563490
! Node: QLog10 Intrinsic563790
! Node: QMax1 Intrinsic564097
! Node: QMin1 Intrinsic564402
! Node: QMod Intrinsic564705
! Node: QNInt Intrinsic565005
! Node: QSin Intrinsic565307
! Node: QSinD Intrinsic565607
! Node: QSinH Intrinsic565910
! Node: QSqRt Intrinsic566214
! Node: QTan Intrinsic566517
! Node: QTanD Intrinsic566817
! Node: QTanH Intrinsic567120
! Node: Rename Intrinsic (function)567436
! Node: Secnds Intrinsic568241
! Node: Signal Intrinsic (function)568840
! Node: SinD Intrinsic571669
! Node: SnglQ Intrinsic571981
! Node: SymLnk Intrinsic (function)572296
! Node: System Intrinsic (function)573164
! Node: TanD Intrinsic574491
! Node: Time Intrinsic (VXT)574808
! Node: UMask Intrinsic (function)575562
! Node: Unlink Intrinsic (function)576170
! Node: ZExt Intrinsic576899
! Node: Other Compilers577187
! Node: Dropping f2c Compatibility579707
! Node: Compilers Other Than f2c582779
! Node: Other Languages584577
! Node: Interoperating with C and C++584842
! Node: C Interfacing Tools585875
! Node: C Access to Type Information586803
! Node: f2c Skeletons and Prototypes587490
! Ref: f2c Skeletons and Prototypes-Footnote-1588937
! Node: C++ Considerations589191
! Node: Startup Code589846
! Node: Debugging and Interfacing594635
! Node: Main Program Unit597322
! Node: Procedures599816
! Node: Functions602474
! Node: Names604092
! Node: Common Blocks607235
! Node: Local Equivalence Areas607499
! Node: Complex Variables608483
! Node: Arrays609603
! Node: Adjustable Arrays612937
! Node: Alternate Entry Points615796
! Node: Alternate Returns622498
! Node: Assigned Statement Labels623399
! Node: Run-time Library Errors625244
! Node: Collected Fortran Wisdom627196
! Node: Advantages Over f2c628632
! Node: Language Extensions629613
! Node: Diagnostic Abilities630787
! Node: Compiler Options631178
! Node: Compiler Speed632226
! Node: Program Speed632936
! Node: Ease of Debugging634521
! Node: Character and Hollerith Constants636951
! Node: Block Data and Libraries637923
! Node: Loops641252
! Node: Working Programs646478
! Node: Not My Type647222
! Node: Variables Assumed To Be Zero649153
! Node: Variables Assumed To Be Saved650207
! Node: Unwanted Variables651577
! Node: Unused Arguments652457
! Node: Surprising Interpretations of Code652920
! Node: Aliasing Assumed To Work653767
! Node: Output Assumed To Flush659964
! Node: Large File Unit Numbers662737
! Node: Floating-point precision664889
! Node: Inconsistent Calling Sequences666150
! Node: Overly Convenient Options667130
! Node: Faster Programs670436
! Node: Aligned Data670882
! Node: Prefer Automatic Uninitialized Variables675759
! Node: Avoid f2c Compatibility677125
! Node: Use Submodel Options677593
! Node: Trouble678597
! Node: But-bugs680059
! Node: Signal 11 and Friends681832
! Node: Cannot Link Fortran Programs683912
! Node: Large Common Blocks685195
! Node: Debugger Problems685621
! Node: NeXTStep Problems686336
! Node: Stack Overflow688162
! Node: Nothing Happens691051
! Node: Strange Behavior at Run Time692665
! Node: Floating-point Errors695154
! Node: Known Bugs701448
! Node: Missing Features708751
! Node: Better Source Model710678
! Node: Fortran 90 Support712447
! Node: Intrinsics in PARAMETER Statements713548
! Node: Arbitrary Concatenation714299
! Node: SELECT CASE on CHARACTER Type714702
! Node: RECURSIVE Keyword714989
! Node: Increasing Precision/Range715416
! Node: Popular Non-standard Types716954
! Node: Full Support for Compiler Types717293
! Node: Array Bounds Expressions717929
! Node: POINTER Statements718376
! Node: Sensible Non-standard Constructs719259
! Node: READONLY Keyword721585
! Node: FLUSH Statement722495
! Node: Expressions in FORMAT Statements722865
! Node: Explicit Assembler Code724040
! Node: Q Edit Descriptor724329
! Node: Old-style PARAMETER Statements724833
! Node: TYPE and ACCEPT I/O Statements725567
! Node: STRUCTURE UNION RECORD MAP726133
! Node: OPEN CLOSE and INQUIRE Keywords726619
! Node: ENCODE and DECODE727599
! Node: AUTOMATIC Statement728694
! Node: Suppressing Space Padding729941
! Node: Fortran Preprocessor731168
! Node: Bit Operations on Floating-point Data731741
! Node: Really Ugly Character Assignments732274
! Node: POSIX Standard732649
! Node: Floating-point Exception Handling732889
! Node: Nonportable Conversions734293
! Node: Large Automatic Arrays734836
! Node: Support for Threads735243
! Node: Enabling Debug Lines735668
! Node: Better Warnings736045
! Node: Gracefully Handle Sensible Bad Code737681
! Node: Non-standard Conversions738425
! Node: Non-standard Intrinsics738768
! Node: Modifying DO Variable739184
! Node: Better Pedantic Compilation739860
! Node: Warn About Implicit Conversions740488
! Node: Invalid Use of Hollerith Constant741075
! Node: Dummy Array Without Dimensioning Dummy741618
! Node: Invalid FORMAT Specifiers742531
! Node: Ambiguous Dialects742932
! Node: Unused Labels743343
! Node: Informational Messages743565
! Node: Uninitialized Variables at Run Time743968
! Node: Portable Unformatted Files744574
! Ref: Portable Unformatted Files-Footnote-1747530
! Node: Better List-directed I/O747558
! Node: Default to Console I/O748463
! Node: Labels Visible to Debugger749111
! Node: Disappointments749512
! Node: Mangling of Names750150
! Node: Multiple Definitions of External Names751000
! Node: Limitation on Implicit Declarations752363
! Node: Non-bugs752647
! Node: Backslash in Constants753772
! Node: Initializing Before Specifying758661
! Node: Context-Sensitive Intrinsicness759803
! Node: Context-Sensitive Constants761699
! Node: Equivalence Versus Equality764655
! Node: Order of Side Effects767698
! Node: Warnings and Errors769426
! Node: Open Questions770824
! Node: Bugs771293
! Node: Bug Criteria772732
! Node: Bug Lists778965
! Node: Bug Reporting779754
! Node: Service793370
! Node: Adding Options793836
! Node: Projects798429
! Node: Efficiency799364
! Node: Better Optimization802261
! Node: Simplify Porting805631
! Node: More Extensions807386
! Node: Machine Model810474
! Node: Internals Documentation811760
! Node: Internals Improvements812067
! Node: Better Diagnostics815611
! Node: Front End816528
! Node: Overview of Sources817315
! Node: Overview of Translation Process824704
! Node: g77stripcard828982
! Node: lex.c831459
! Node: sta.c840999
! Node: sti.c841110
! Node: stq.c841221
! Node: stb.c841332
! Node: expr.c841444
! Node: stc.c841558
! Node: std.c841670
! Node: ste.c841781
! Node: Gotchas (Transforming)841909
! Node: TBD (Transforming)850028
! Node: Philosophy of Code Generation852724
! Node: Two-pass Design858628
! Node: Two-pass Code859785
! Node: Why Two Passes860518
! Node: Challenges Posed866586
! Node: Transforming Statements869070
! Node: Statements Needing Temporaries869920
! Node: Transforming DO WHILE872684
! Node: Transforming Iterative DO873867
! Node: Transforming Block IF874696
! Node: Transforming SELECT CASE876061
! Node: Transforming Expressions879283
! Node: Internal Naming Conventions881272
! Node: Diagnostics884272
! Node: CMPAMBIG885662
! Node: EXPIMP892079
! Node: INTGLOB893315
! Node: LEX895559
! Node: GLOBALS901014
! Node: LINKFAIL903678
! Node: Y2KBAD904302
! Node: Index904652
  
  End Tag Table
--- 50,27773 ----
     You have freedom to copy and modify this GNU Manual, like GNU
  software.  Copies published by the Free Software Foundation raise
  funds for GNU development.
     Contributed by James Craig Burley (<craig@jcb-sc.com>).  Inspired by
  a first pass at translating `g77-0.5.16/f/DOC' that was contributed to
  Craig by David Ronis (<ronis@onsager.chem.mcgill.ca>).
  
  
! File: g77.info,  Node: Top,  Next: Copying,  Up: (DIR)
! 
! Introduction
! ************
! 
!    This manual documents how to run, install and port `g77', as well as
! its new features and incompatibilities, and how to report bugs.  It
! corresponds to the GCC-3.3 version of `g77'.
! 
! * Menu:
! 
! * Copying::         GNU General Public License says
!                     how you can copy and share GNU Fortran.
! * GNU Free Documentation License::
! 		    How you can copy and share this manual.
! * Contributors::    People who have contributed to GNU Fortran.
! * Funding::         How to help assure continued work for free software.
! * Funding GNU Fortran::  How to help assure continued work on GNU Fortran.
! 
! * Getting Started:: Finding your way around this manual.
! * What is GNU Fortran?::  How `g77' fits into the universe.
! * G77 and GCC::     You can compile Fortran, C, or other programs.
! * Invoking G77::    Command options supported by `g77'.
! * News::            News about recent releases of `g77'.
! * Changes::         User-visible changes to recent releases of `g77'.
! * Language::        The GNU Fortran language.
! * Compiler::        The GNU Fortran compiler.
! * Other Dialects::  Dialects of Fortran supported by `g77'.
! * Other Compilers:: Fortran compilers other than `g77'.
! * Other Languages:: Languages other than Fortran.
! * Debugging and Interfacing::  How `g77' generates code.
! * Collected Fortran Wisdom::  How to avoid Trouble.
! * Trouble::         If you have trouble with GNU Fortran.
! * Open Questions::  Things we'd like to know.
! * Bugs::            How, why, and where to report bugs.
! * Service::         How to find suppliers of support for GNU Fortran.
! 
! * Adding Options::  Guidance on teaching `g77' about new options.
! * Projects::        Projects for `g77' internals hackers.
! * Front End::       Design and implementation of the `g77' front end.
! 
! * M: Diagnostics.   Diagnostics produced by `g77'.
! 
! * Keyword Index::   Index of concepts and symbol names.
! 
! 
! File: g77.info,  Node: Copying,  Next: GNU Free Documentation License,  Prev: Top,  Up: Top
! 
! GNU GENERAL PUBLIC LICENSE
! **************************
! 
!                          Version 2, June 1991
!      Copyright (C) 1989, 1991 Free Software Foundation, Inc.
!      59 Temple Place - Suite 330, Boston, MA  02111-1307, USA
!      
!      Everyone is permitted to copy and distribute verbatim copies
!      of this license document, but changing it is not allowed.
! 
! Preamble
! ========
! 
!    The licenses for most software are designed to take away your
! freedom to share and change it.  By contrast, the GNU General Public
! License is intended to guarantee your freedom to share and change free
! software--to make sure the software is free for all its users.  This
! General Public License applies to most of the Free Software
! Foundation's software and to any other program whose authors commit to
! using it.  (Some other Free Software Foundation software is covered by
! the GNU Library General Public License instead.)  You can apply it to
! your programs, too.
! 
!    When we speak of free software, we are referring to freedom, not
! price.  Our General Public Licenses are designed to make sure that you
! have the freedom to distribute copies of free software (and charge for
! this service if you wish), that you receive source code or can get it
! if you want it, that you can change the software or use pieces of it in
! new free programs; and that you know you can do these things.
! 
!    To protect your rights, we need to make restrictions that forbid
! anyone to deny you these rights or to ask you to surrender the rights.
! These restrictions translate to certain responsibilities for you if you
! distribute copies of the software, or if you modify it.
! 
!    For example, if you distribute copies of such a program, whether
! gratis or for a fee, you must give the recipients all the rights that
! you have.  You must make sure that they, too, receive or can get the
! source code.  And you must show them these terms so they know their
! rights.
! 
!    We protect your rights with two steps: (1) copyright the software,
! and (2) offer you this license which gives you legal permission to copy,
! distribute and/or modify the software.
! 
!    Also, for each author's protection and ours, we want to make certain
! that everyone understands that there is no warranty for this free
! software.  If the software is modified by someone else and passed on, we
! want its recipients to know that what they have is not the original, so
! that any problems introduced by others will not reflect on the original
! authors' reputations.
! 
!    Finally, any free program is threatened constantly by software
! patents.  We wish to avoid the danger that redistributors of a free
! program will individually obtain patent licenses, in effect making the
! program proprietary.  To prevent this, we have made it clear that any
! patent must be licensed for everyone's free use or not licensed at all.
! 
!    The precise terms and conditions for copying, distribution and
! modification follow.
! 
!     TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
!   0. This License applies to any program or other work which contains a
!      notice placed by the copyright holder saying it may be distributed
!      under the terms of this General Public License.  The "Program",
!      below, refers to any such program or work, and a "work based on
!      the Program" means either the Program or any derivative work under
!      copyright law: that is to say, a work containing the Program or a
!      portion of it, either verbatim or with modifications and/or
!      translated into another language.  (Hereinafter, translation is
!      included without limitation in the term "modification".)  Each
!      licensee is addressed as "you".
! 
!      Activities other than copying, distribution and modification are
!      not covered by this License; they are outside its scope.  The act
!      of running the Program is not restricted, and the output from the
!      Program is covered only if its contents constitute a work based on
!      the Program (independent of having been made by running the
!      Program).  Whether that is true depends on what the Program does.
! 
!   1. You may copy and distribute verbatim copies of the Program's
!      source code as you receive it, in any medium, provided that you
!      conspicuously and appropriately publish on each copy an appropriate
!      copyright notice and disclaimer of warranty; keep intact all the
!      notices that refer to this License and to the absence of any
!      warranty; and give any other recipients of the Program a copy of
!      this License along with the Program.
! 
!      You may charge a fee for the physical act of transferring a copy,
!      and you may at your option offer warranty protection in exchange
!      for a fee.
! 
!   2. You may modify your copy or copies of the Program or any portion
!      of it, thus forming a work based on the Program, and copy and
!      distribute such modifications or work under the terms of Section 1
!      above, provided that you also meet all of these conditions:
! 
!        a. You must cause the modified files to carry prominent notices
!           stating that you changed the files and the date of any change.
! 
!        b. You must cause any work that you distribute or publish, that
!           in whole or in part contains or is derived from the Program
!           or any part thereof, to be licensed as a whole at no charge
!           to all third parties under the terms of this License.
! 
!        c. If the modified program normally reads commands interactively
!           when run, you must cause it, when started running for such
!           interactive use in the most ordinary way, to print or display
!           an announcement including an appropriate copyright notice and
!           a notice that there is no warranty (or else, saying that you
!           provide a warranty) and that users may redistribute the
!           program under these conditions, and telling the user how to
!           view a copy of this License.  (Exception: if the Program
!           itself is interactive but does not normally print such an
!           announcement, your work based on the Program is not required
!           to print an announcement.)
! 
!      These requirements apply to the modified work as a whole.  If
!      identifiable sections of that work are not derived from the
!      Program, and can be reasonably considered independent and separate
!      works in themselves, then this License, and its terms, do not
!      apply to those sections when you distribute them as separate
!      works.  But when you distribute the same sections as part of a
!      whole which is a work based on the Program, the distribution of
!      the whole must be on the terms of this License, whose permissions
!      for other licensees extend to the entire whole, and thus to each
!      and every part regardless of who wrote it.
! 
!      Thus, it is not the intent of this section to claim rights or
!      contest your rights to work written entirely by you; rather, the
!      intent is to exercise the right to control the distribution of
!      derivative or collective works based on the Program.
! 
!      In addition, mere aggregation of another work not based on the
!      Program with the Program (or with a work based on the Program) on
!      a volume of a storage or distribution medium does not bring the
!      other work under the scope of this License.
! 
!   3. You may copy and distribute the Program (or a work based on it,
!      under Section 2) in object code or executable form under the terms
!      of Sections 1 and 2 above provided that you also do one of the
!      following:
! 
!        a. Accompany it with the complete corresponding machine-readable
!           source code, which must be distributed under the terms of
!           Sections 1 and 2 above on a medium customarily used for
!           software interchange; or,
! 
!        b. Accompany it with a written offer, valid for at least three
!           years, to give any third party, for a charge no more than your
!           cost of physically performing source distribution, a complete
!           machine-readable copy of the corresponding source code, to be
!           distributed under the terms of Sections 1 and 2 above on a
!           medium customarily used for software interchange; or,
! 
!        c. Accompany it with the information you received as to the offer
!           to distribute corresponding source code.  (This alternative is
!           allowed only for noncommercial distribution and only if you
!           received the program in object code or executable form with
!           such an offer, in accord with Subsection b above.)
! 
!      The source code for a work means the preferred form of the work for
!      making modifications to it.  For an executable work, complete
!      source code means all the source code for all modules it contains,
!      plus any associated interface definition files, plus the scripts
!      used to control compilation and installation of the executable.
!      However, as a special exception, the source code distributed need
!      not include anything that is normally distributed (in either
!      source or binary form) with the major components (compiler,
!      kernel, and so on) of the operating system on which the executable
!      runs, unless that component itself accompanies the executable.
! 
!      If distribution of executable or object code is made by offering
!      access to copy from a designated place, then offering equivalent
!      access to copy the source code from the same place counts as
!      distribution of the source code, even though third parties are not
!      compelled to copy the source along with the object code.
! 
!   4. You may not copy, modify, sublicense, or distribute the Program
!      except as expressly provided under this License.  Any attempt
!      otherwise to copy, modify, sublicense or distribute the Program is
!      void, and will automatically terminate your rights under this
!      License.  However, parties who have received copies, or rights,
!      from you under this License will not have their licenses
!      terminated so long as such parties remain in full compliance.
! 
!   5. You are not required to accept this License, since you have not
!      signed it.  However, nothing else grants you permission to modify
!      or distribute the Program or its derivative works.  These actions
!      are prohibited by law if you do not accept this License.
!      Therefore, by modifying or distributing the Program (or any work
!      based on the Program), you indicate your acceptance of this
!      License to do so, and all its terms and conditions for copying,
!      distributing or modifying the Program or works based on it.
! 
!   6. Each time you redistribute the Program (or any work based on the
!      Program), the recipient automatically receives a license from the
!      original licensor to copy, distribute or modify the Program
!      subject to these terms and conditions.  You may not impose any
!      further restrictions on the recipients' exercise of the rights
!      granted herein.  You are not responsible for enforcing compliance
!      by third parties to this License.
! 
!   7. If, as a consequence of a court judgment or allegation of patent
!      infringement or for any other reason (not limited to patent
!      issues), conditions are imposed on you (whether by court order,
!      agreement or otherwise) that contradict the conditions of this
!      License, they do not excuse you from the conditions of this
!      License.  If you cannot distribute so as to satisfy simultaneously
!      your obligations under this License and any other pertinent
!      obligations, then as a consequence you may not distribute the
!      Program at all.  For example, if a patent license would not permit
!      royalty-free redistribution of the Program by all those who
!      receive copies directly or indirectly through you, then the only
!      way you could satisfy both it and this License would be to refrain
!      entirely from distribution of the Program.
! 
!      If any portion of this section is held invalid or unenforceable
!      under any particular circumstance, the balance of the section is
!      intended to apply and the section as a whole is intended to apply
!      in other circumstances.
! 
!      It is not the purpose of this section to induce you to infringe any
!      patents or other property right claims or to contest validity of
!      any such claims; this section has the sole purpose of protecting
!      the integrity of the free software distribution system, which is
!      implemented by public license practices.  Many people have made
!      generous contributions to the wide range of software distributed
!      through that system in reliance on consistent application of that
!      system; it is up to the author/donor to decide if he or she is
!      willing to distribute software through any other system and a
!      licensee cannot impose that choice.
! 
!      This section is intended to make thoroughly clear what is believed
!      to be a consequence of the rest of this License.
! 
!   8. If the distribution and/or use of the Program is restricted in
!      certain countries either by patents or by copyrighted interfaces,
!      the original copyright holder who places the Program under this
!      License may add an explicit geographical distribution limitation
!      excluding those countries, so that distribution is permitted only
!      in or among countries not thus excluded.  In such case, this
!      License incorporates the limitation as if written in the body of
!      this License.
! 
!   9. The Free Software Foundation may publish revised and/or new
!      versions of the General Public License from time to time.  Such
!      new versions will be similar in spirit to the present version, but
!      may differ in detail to address new problems or concerns.
! 
!      Each version is given a distinguishing version number.  If the
!      Program specifies a version number of this License which applies
!      to it and "any later version", you have the option of following
!      the terms and conditions either of that version or of any later
!      version published by the Free Software Foundation.  If the Program
!      does not specify a version number of this License, you may choose
!      any version ever published by the Free Software Foundation.
! 
!  10. If you wish to incorporate parts of the Program into other free
!      programs whose distribution conditions are different, write to the
!      author to ask for permission.  For software which is copyrighted
!      by the Free Software Foundation, write to the Free Software
!      Foundation; we sometimes make exceptions for this.  Our decision
!      will be guided by the two goals of preserving the free status of
!      all derivatives of our free software and of promoting the sharing
!      and reuse of software generally.
! 
!                                 NO WARRANTY
! 
!  11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO
!      WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE
!      LAW.  EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
!      HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT
!      WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT
!      NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
!      FITNESS FOR A PARTICULAR PURPOSE.  THE ENTIRE RISK AS TO THE
!      QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.  SHOULD THE
!      PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY
!      SERVICING, REPAIR OR CORRECTION.
! 
!  12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN
!      WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY
!      MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE
!      LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL,
!      INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR
!      INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
!      DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU
!      OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY
!      OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN
!      ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
! 
!                       END OF TERMS AND CONDITIONS
! 
! How to Apply These Terms to Your New Programs
! =============================================
! 
!    If you develop a new program, and you want it to be of the greatest
! possible use to the public, the best way to achieve this is to make it
! free software which everyone can redistribute and change under these
! terms.
! 
!    To do so, attach the following notices to the program.  It is safest
! to attach them to the start of each source file to most effectively
! convey the exclusion of warranty; and each file should have at least
! the "copyright" line and a pointer to where the full notice is found.
! 
!      ONE LINE TO GIVE THE PROGRAM'S NAME AND A BRIEF IDEA OF WHAT IT DOES.
!      Copyright (C) YEAR  NAME OF AUTHOR
!      
!      This program is free software; you can redistribute it and/or modify
!      it under the terms of the GNU General Public License as published by
!      the Free Software Foundation; either version 2 of the License, or
!      (at your option) any later version.
!      
!      This program is distributed in the hope that it will be useful,
!      but WITHOUT ANY WARRANTY; without even the implied warranty of
!      MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
!      GNU General Public License for more details.
!      
!      You should have received a copy of the GNU General Public License
!      along with this program; if not, write to the Free Software Foundation,
!      Inc., 59 Temple Place - Suite 330, Boston, MA  02111-1307, USA.
! 
!    Also add information on how to contact you by electronic and paper
! mail.
! 
!    If the program is interactive, make it output a short notice like
! this when it starts in an interactive mode:
! 
!      Gnomovision version 69, Copyright (C) YEAR NAME OF AUTHOR
!      Gnomovision comes with ABSOLUTELY NO WARRANTY; for details
!      type `show w'.
!      This is free software, and you are welcome to redistribute it
!      under certain conditions; type `show c' for details.
! 
!    The hypothetical commands `show w' and `show c' should show the
! appropriate parts of the General Public License.  Of course, the
! commands you use may be called something other than `show w' and `show
! c'; they could even be mouse-clicks or menu items--whatever suits your
! program.
! 
!    You should also get your employer (if you work as a programmer) or
! your school, if any, to sign a "copyright disclaimer" for the program,
! if necessary.  Here is a sample; alter the names:
! 
!      Yoyodyne, Inc., hereby disclaims all copyright interest in the program
!      `Gnomovision' (which makes passes at compilers) written by James Hacker.
!      
!      SIGNATURE OF TY COON, 1 April 1989
!      Ty Coon, President of Vice
! 
!    This General Public License does not permit incorporating your
! program into proprietary programs.  If your program is a subroutine
! library, you may consider it more useful to permit linking proprietary
! applications with the library.  If this is what you want to do, use the
! GNU Library General Public License instead of this License.
! 
! 
! File: g77.info,  Node: GNU Free Documentation License,  Next: Contributors,  Prev: Copying,  Up: Top
! 
! GNU Free Documentation License
! ******************************
! 
!                       Version 1.2, November 2002
!      Copyright (C) 2000,2001,2002 Free Software Foundation, Inc.
!      59 Temple Place, Suite 330, Boston, MA  02111-1307, USA
!      
!      Everyone is permitted to copy and distribute verbatim copies
!      of this license document, but changing it is not allowed.
! 
!   0. PREAMBLE
! 
!      The purpose of this License is to make a manual, textbook, or other
!      functional and useful document "free" in the sense of freedom: to
!      assure everyone the effective freedom to copy and redistribute it,
!      with or without modifying it, either commercially or
!      noncommercially.  Secondarily, this License preserves for the
!      author and publisher a way to get credit for their work, while not
!      being considered responsible for modifications made by others.
! 
!      This License is a kind of "copyleft", which means that derivative
!      works of the document must themselves be free in the same sense.
!      It complements the GNU General Public License, which is a copyleft
!      license designed for free software.
! 
!      We have designed this License in order to use it for manuals for
!      free software, because free software needs free documentation: a
!      free program should come with manuals providing the same freedoms
!      that the software does.  But this License is not limited to
!      software manuals; it can be used for any textual work, regardless
!      of subject matter or whether it is published as a printed book.
!      We recommend this License principally for works whose purpose is
!      instruction or reference.
! 
!   1. APPLICABILITY AND DEFINITIONS
! 
!      This License applies to any manual or other work, in any medium,
!      that contains a notice placed by the copyright holder saying it
!      can be distributed under the terms of this License.  Such a notice
!      grants a world-wide, royalty-free license, unlimited in duration,
!      to use that work under the conditions stated herein.  The
!      "Document", below, refers to any such manual or work.  Any member
!      of the public is a licensee, and is addressed as "you".  You
!      accept the license if you copy, modify or distribute the work in a
!      way requiring permission under copyright law.
! 
!      A "Modified Version" of the Document means any work containing the
!      Document or a portion of it, either copied verbatim, or with
!      modifications and/or translated into another language.
! 
!      A "Secondary Section" is a named appendix or a front-matter section
!      of the Document that deals exclusively with the relationship of the
!      publishers or authors of the Document to the Document's overall
!      subject (or to related matters) and contains nothing that could
!      fall directly within that overall subject.  (Thus, if the Document
!      is in part a textbook of mathematics, a Secondary Section may not
!      explain any mathematics.)  The relationship could be a matter of
!      historical connection with the subject or with related matters, or
!      of legal, commercial, philosophical, ethical or political position
!      regarding them.
! 
!      The "Invariant Sections" are certain Secondary Sections whose
!      titles are designated, as being those of Invariant Sections, in
!      the notice that says that the Document is released under this
!      License.  If a section does not fit the above definition of
!      Secondary then it is not allowed to be designated as Invariant.
!      The Document may contain zero Invariant Sections.  If the Document
!      does not identify any Invariant Sections then there are none.
! 
!      The "Cover Texts" are certain short passages of text that are
!      listed, as Front-Cover Texts or Back-Cover Texts, in the notice
!      that says that the Document is released under this License.  A
!      Front-Cover Text may be at most 5 words, and a Back-Cover Text may
!      be at most 25 words.
! 
!      A "Transparent" copy of the Document means a machine-readable copy,
!      represented in a format whose specification is available to the
!      general public, that is suitable for revising the document
!      straightforwardly with generic text editors or (for images
!      composed of pixels) generic paint programs or (for drawings) some
!      widely available drawing editor, and that is suitable for input to
!      text formatters or for automatic translation to a variety of
!      formats suitable for input to text formatters.  A copy made in an
!      otherwise Transparent file format whose markup, or absence of
!      markup, has been arranged to thwart or discourage subsequent
!      modification by readers is not Transparent.  An image format is
!      not Transparent if used for any substantial amount of text.  A
!      copy that is not "Transparent" is called "Opaque".
! 
!      Examples of suitable formats for Transparent copies include plain
!      ASCII without markup, Texinfo input format, LaTeX input format,
!      SGML or XML using a publicly available DTD, and
!      standard-conforming simple HTML, PostScript or PDF designed for
!      human modification.  Examples of transparent image formats include
!      PNG, XCF and JPG.  Opaque formats include proprietary formats that
!      can be read and edited only by proprietary word processors, SGML or
!      XML for which the DTD and/or processing tools are not generally
!      available, and the machine-generated HTML, PostScript or PDF
!      produced by some word processors for output purposes only.
! 
!      The "Title Page" means, for a printed book, the title page itself,
!      plus such following pages as are needed to hold, legibly, the
!      material this License requires to appear in the title page.  For
!      works in formats which do not have any title page as such, "Title
!      Page" means the text near the most prominent appearance of the
!      work's title, preceding the beginning of the body of the text.
! 
!      A section "Entitled XYZ" means a named subunit of the Document
!      whose title either is precisely XYZ or contains XYZ in parentheses
!      following text that translates XYZ in another language.  (Here XYZ
!      stands for a specific section name mentioned below, such as
!      "Acknowledgements", "Dedications", "Endorsements", or "History".)
!      To "Preserve the Title" of such a section when you modify the
!      Document means that it remains a section "Entitled XYZ" according
!      to this definition.
! 
!      The Document may include Warranty Disclaimers next to the notice
!      which states that this License applies to the Document.  These
!      Warranty Disclaimers are considered to be included by reference in
!      this License, but only as regards disclaiming warranties: any other
!      implication that these Warranty Disclaimers may have is void and
!      has no effect on the meaning of this License.
! 
!   2. VERBATIM COPYING
! 
!      You may copy and distribute the Document in any medium, either
!      commercially or noncommercially, provided that this License, the
!      copyright notices, and the license notice saying this License
!      applies to the Document are reproduced in all copies, and that you
!      add no other conditions whatsoever to those of this License.  You
!      may not use technical measures to obstruct or control the reading
!      or further copying of the copies you make or distribute.  However,
!      you may accept compensation in exchange for copies.  If you
!      distribute a large enough number of copies you must also follow
!      the conditions in section 3.
! 
!      You may also lend copies, under the same conditions stated above,
!      and you may publicly display copies.
! 
!   3. COPYING IN QUANTITY
! 
!      If you publish printed copies (or copies in media that commonly
!      have printed covers) of the Document, numbering more than 100, and
!      the Document's license notice requires Cover Texts, you must
!      enclose the copies in covers that carry, clearly and legibly, all
!      these Cover Texts: Front-Cover Texts on the front cover, and
!      Back-Cover Texts on the back cover.  Both covers must also clearly
!      and legibly identify you as the publisher of these copies.  The
!      front cover must present the full title with all words of the
!      title equally prominent and visible.  You may add other material
!      on the covers in addition.  Copying with changes limited to the
!      covers, as long as they preserve the title of the Document and
!      satisfy these conditions, can be treated as verbatim copying in
!      other respects.
! 
!      If the required texts for either cover are too voluminous to fit
!      legibly, you should put the first ones listed (as many as fit
!      reasonably) on the actual cover, and continue the rest onto
!      adjacent pages.
! 
!      If you publish or distribute Opaque copies of the Document
!      numbering more than 100, you must either include a
!      machine-readable Transparent copy along with each Opaque copy, or
!      state in or with each Opaque copy a computer-network location from
!      which the general network-using public has access to download
!      using public-standard network protocols a complete Transparent
!      copy of the Document, free of added material.  If you use the
!      latter option, you must take reasonably prudent steps, when you
!      begin distribution of Opaque copies in quantity, to ensure that
!      this Transparent copy will remain thus accessible at the stated
!      location until at least one year after the last time you
!      distribute an Opaque copy (directly or through your agents or
!      retailers) of that edition to the public.
! 
!      It is requested, but not required, that you contact the authors of
!      the Document well before redistributing any large number of
!      copies, to give them a chance to provide you with an updated
!      version of the Document.
! 
!   4. MODIFICATIONS
! 
!      You may copy and distribute a Modified Version of the Document
!      under the conditions of sections 2 and 3 above, provided that you
!      release the Modified Version under precisely this License, with
!      the Modified Version filling the role of the Document, thus
!      licensing distribution and modification of the Modified Version to
!      whoever possesses a copy of it.  In addition, you must do these
!      things in the Modified Version:
! 
!        A. Use in the Title Page (and on the covers, if any) a title
!           distinct from that of the Document, and from those of
!           previous versions (which should, if there were any, be listed
!           in the History section of the Document).  You may use the
!           same title as a previous version if the original publisher of
!           that version gives permission.
! 
!        B. List on the Title Page, as authors, one or more persons or
!           entities responsible for authorship of the modifications in
!           the Modified Version, together with at least five of the
!           principal authors of the Document (all of its principal
!           authors, if it has fewer than five), unless they release you
!           from this requirement.
! 
!        C. State on the Title page the name of the publisher of the
!           Modified Version, as the publisher.
! 
!        D. Preserve all the copyright notices of the Document.
! 
!        E. Add an appropriate copyright notice for your modifications
!           adjacent to the other copyright notices.
! 
!        F. Include, immediately after the copyright notices, a license
!           notice giving the public permission to use the Modified
!           Version under the terms of this License, in the form shown in
!           the Addendum below.
! 
!        G. Preserve in that license notice the full lists of Invariant
!           Sections and required Cover Texts given in the Document's
!           license notice.
! 
!        H. Include an unaltered copy of this License.
! 
!        I. Preserve the section Entitled "History", Preserve its Title,
!           and add to it an item stating at least the title, year, new
!           authors, and publisher of the Modified Version as given on
!           the Title Page.  If there is no section Entitled "History" in
!           the Document, create one stating the title, year, authors,
!           and publisher of the Document as given on its Title Page,
!           then add an item describing the Modified Version as stated in
!           the previous sentence.
! 
!        J. Preserve the network location, if any, given in the Document
!           for public access to a Transparent copy of the Document, and
!           likewise the network locations given in the Document for
!           previous versions it was based on.  These may be placed in
!           the "History" section.  You may omit a network location for a
!           work that was published at least four years before the
!           Document itself, or if the original publisher of the version
!           it refers to gives permission.
! 
!        K. For any section Entitled "Acknowledgements" or "Dedications",
!           Preserve the Title of the section, and preserve in the
!           section all the substance and tone of each of the contributor
!           acknowledgements and/or dedications given therein.
! 
!        L. Preserve all the Invariant Sections of the Document,
!           unaltered in their text and in their titles.  Section numbers
!           or the equivalent are not considered part of the section
!           titles.
! 
!        M. Delete any section Entitled "Endorsements".  Such a section
!           may not be included in the Modified Version.
! 
!        N. Do not retitle any existing section to be Entitled
!           "Endorsements" or to conflict in title with any Invariant
!           Section.
! 
!        O. Preserve any Warranty Disclaimers.
! 
!      If the Modified Version includes new front-matter sections or
!      appendices that qualify as Secondary Sections and contain no
!      material copied from the Document, you may at your option
!      designate some or all of these sections as invariant.  To do this,
!      add their titles to the list of Invariant Sections in the Modified
!      Version's license notice.  These titles must be distinct from any
!      other section titles.
! 
!      You may add a section Entitled "Endorsements", provided it contains
!      nothing but endorsements of your Modified Version by various
!      parties--for example, statements of peer review or that the text
!      has been approved by an organization as the authoritative
!      definition of a standard.
! 
!      You may add a passage of up to five words as a Front-Cover Text,
!      and a passage of up to 25 words as a Back-Cover Text, to the end
!      of the list of Cover Texts in the Modified Version.  Only one
!      passage of Front-Cover Text and one of Back-Cover Text may be
!      added by (or through arrangements made by) any one entity.  If the
!      Document already includes a cover text for the same cover,
!      previously added by you or by arrangement made by the same entity
!      you are acting on behalf of, you may not add another; but you may
!      replace the old one, on explicit permission from the previous
!      publisher that added the old one.
! 
!      The author(s) and publisher(s) of the Document do not by this
!      License give permission to use their names for publicity for or to
!      assert or imply endorsement of any Modified Version.
! 
!   5. COMBINING DOCUMENTS
! 
!      You may combine the Document with other documents released under
!      this License, under the terms defined in section 4 above for
!      modified versions, provided that you include in the combination
!      all of the Invariant Sections of all of the original documents,
!      unmodified, and list them all as Invariant Sections of your
!      combined work in its license notice, and that you preserve all
!      their Warranty Disclaimers.
! 
!      The combined work need only contain one copy of this License, and
!      multiple identical Invariant Sections may be replaced with a single
!      copy.  If there are multiple Invariant Sections with the same name
!      but different contents, make the title of each such section unique
!      by adding at the end of it, in parentheses, the name of the
!      original author or publisher of that section if known, or else a
!      unique number.  Make the same adjustment to the section titles in
!      the list of Invariant Sections in the license notice of the
!      combined work.
! 
!      In the combination, you must combine any sections Entitled
!      "History" in the various original documents, forming one section
!      Entitled "History"; likewise combine any sections Entitled
!      "Acknowledgements", and any sections Entitled "Dedications".  You
!      must delete all sections Entitled "Endorsements."
! 
!   6. COLLECTIONS OF DOCUMENTS
! 
!      You may make a collection consisting of the Document and other
!      documents released under this License, and replace the individual
!      copies of this License in the various documents with a single copy
!      that is included in the collection, provided that you follow the
!      rules of this License for verbatim copying of each of the
!      documents in all other respects.
! 
!      You may extract a single document from such a collection, and
!      distribute it individually under this License, provided you insert
!      a copy of this License into the extracted document, and follow
!      this License in all other respects regarding verbatim copying of
!      that document.
! 
!   7. AGGREGATION WITH INDEPENDENT WORKS
! 
!      A compilation of the Document or its derivatives with other
!      separate and independent documents or works, in or on a volume of
!      a storage or distribution medium, is called an "aggregate" if the
!      copyright resulting from the compilation is not used to limit the
!      legal rights of the compilation's users beyond what the individual
!      works permit.  When the Document is included an aggregate, this
!      License does not apply to the other works in the aggregate which
!      are not themselves derivative works of the Document.
! 
!      If the Cover Text requirement of section 3 is applicable to these
!      copies of the Document, then if the Document is less than one half
!      of the entire aggregate, the Document's Cover Texts may be placed
!      on covers that bracket the Document within the aggregate, or the
!      electronic equivalent of covers if the Document is in electronic
!      form.  Otherwise they must appear on printed covers that bracket
!      the whole aggregate.
! 
!   8. TRANSLATION
! 
!      Translation is considered a kind of modification, so you may
!      distribute translations of the Document under the terms of section
!      4.  Replacing Invariant Sections with translations requires special
!      permission from their copyright holders, but you may include
!      translations of some or all Invariant Sections in addition to the
!      original versions of these Invariant Sections.  You may include a
!      translation of this License, and all the license notices in the
!      Document, and any Warrany Disclaimers, provided that you also
!      include the original English version of this License and the
!      original versions of those notices and disclaimers.  In case of a
!      disagreement between the translation and the original version of
!      this License or a notice or disclaimer, the original version will
!      prevail.
! 
!      If a section in the Document is Entitled "Acknowledgements",
!      "Dedications", or "History", the requirement (section 4) to
!      Preserve its Title (section 1) will typically require changing the
!      actual title.
! 
!   9. TERMINATION
! 
!      You may not copy, modify, sublicense, or distribute the Document
!      except as expressly provided for under this License.  Any other
!      attempt to copy, modify, sublicense or distribute the Document is
!      void, and will automatically terminate your rights under this
!      License.  However, parties who have received copies, or rights,
!      from you under this License will not have their licenses
!      terminated so long as such parties remain in full compliance.
! 
!  10. FUTURE REVISIONS OF THIS LICENSE
! 
!      The Free Software Foundation may publish new, revised versions of
!      the GNU Free Documentation License from time to time.  Such new
!      versions will be similar in spirit to the present version, but may
!      differ in detail to address new problems or concerns.  See
!      `http://www.gnu.org/copyleft/'.
! 
!      Each version of the License is given a distinguishing version
!      number.  If the Document specifies that a particular numbered
!      version of this License "or any later version" applies to it, you
!      have the option of following the terms and conditions either of
!      that specified version or of any later version that has been
!      published (not as a draft) by the Free Software Foundation.  If
!      the Document does not specify a version number of this License,
!      you may choose any version ever published (not as a draft) by the
!      Free Software Foundation.
! 
! ADDENDUM: How to use this License for your documents
! ====================================================
! 
!    To use this License in a document you have written, include a copy of
! the License in the document and put the following copyright and license
! notices just after the title page:
! 
!        Copyright (C)  YEAR  YOUR NAME.
!        Permission is granted to copy, distribute and/or modify this document
!        under the terms of the GNU Free Documentation License, Version 1.2
!        or any later version published by the Free Software Foundation;
!        with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.
!        A copy of the license is included in the section entitled ``GNU
!        Free Documentation License''.
! 
!    If you have Invariant Sections, Front-Cover Texts and Back-Cover
! Texts, replace the "with...Texts." line with this:
! 
!          with the Invariant Sections being LIST THEIR TITLES, with
!          the Front-Cover Texts being LIST, and with the Back-Cover Texts
!          being LIST.
! 
!    If you have Invariant Sections without Cover Texts, or some other
! combination of the three, merge those two alternatives to suit the
! situation.
! 
!    If your document contains nontrivial examples of program code, we
! recommend releasing these examples in parallel under your choice of
! free software license, such as the GNU General Public License, to
! permit their use in free software.
! 
! 
! File: g77.info,  Node: Contributors,  Next: Funding,  Prev: GNU Free Documentation License,  Up: Top
! 
! Contributors to GNU Fortran
! ***************************
! 
!    In addition to James Craig Burley, who wrote the front end, many
! people have helped create and improve GNU Fortran.
! 
!    * The packaging and compiler portions of GNU Fortran are based
!      largely on the GNU CC compiler.  *Note Contributors to GCC:
!      (gcc)Contributors, for more information.
! 
!    * The run-time library used by GNU Fortran is a repackaged version
!      of the `libf2c' library (combined from the `libF77' and `libI77'
!      libraries) provided as part of `f2c', available for free from
!      `netlib' sites on the Internet.
! 
!    * Cygnus Support and The Free Software Foundation contributed
!      significant money and/or equipment to Craig's efforts.
! 
!    * The following individuals served as alpha testers prior to `g77''s
!      public release.  This work consisted of testing, researching,
!      sometimes debugging, and occasionally providing small amounts of
!      code and fixes for `g77', plus offering plenty of helpful advice
!      to Craig:
! 
!           Jonathan Corbet
! 
!           Dr. Mark Fernyhough
! 
!           Takafumi Hayashi (The University of
!           Aizu)--<takafumi@u-aizu.ac.jp>
! 
!           Kate Hedstrom
! 
!           Michel Kern (INRIA and Rice
!           University)--<Michel.Kern@inria.fr>
! 
!           Dr. A. O. V. Le Blanc
! 
!           Dave Love
! 
!           Rick Lutowski
! 
!           Toon Moene
! 
!           Rick Niles
! 
!           Derk Reefman
! 
!           Wayne K. Schroll
! 
!           Bill Thorson
! 
!           Pedro A. M. Vazquez
! 
!           Ian Watson
! 
!    * Dave Love (<d.love@dl.ac.uk>) wrote the libU77 part of the
!      run-time library.
! 
!    * Scott Snyder (<snyder@d0sgif.fnal.gov>) provided the patch to add
!      rudimentary support for `INTEGER*1', `INTEGER*2', and `LOGICAL*1'.
!      This inspired Craig to add further support, even though the
!      resulting support would still be incomplete.
! 
!    * David Ronis (<ronis@onsager.chem.mcgill.ca>) inspired and
!      encouraged Craig to rewrite the documentation in texinfo format by
!      contributing a first pass at a translation of the old
!      `g77-0.5.16/f/DOC' file.
! 
!    * Toon Moene (<toon@moene.indiv.nluug.nl>) performed some analysis
!      of generated code as part of an overall project to improve `g77'
!      code generation to at least be as good as `f2c' used in
!      conjunction with `gcc'.  So far, this has resulted in the three,
!      somewhat experimental, options added by `g77' to the `gcc'
!      compiler and its back end.
! 
!      (These, in turn, had made their way into the `egcs' version of the
!      compiler, and do not exist in `gcc' version 2.8 or versions of
!      `g77' based on that version of `gcc'.)
! 
!    * John Carr (<jfc@mit.edu>) wrote the alias analysis improvements.
! 
!    * Thanks to Mary Cortani and the staff at Craftwork Solutions
!      (<support@craftwork.com>) for all of their support.
! 
!    * Many other individuals have helped debug, test, and improve `g77'
!      over the past several years, and undoubtedly more people will be
!      doing so in the future.  If you have done so, and would like to
!      see your name listed in the above list, please ask!  The default
!      is that people wish to remain anonymous.
! 
! 
! File: g77.info,  Node: Funding,  Next: Funding GNU Fortran,  Prev: Contributors,  Up: Top
! 
! Funding Free Software
! *********************
! 
!    If you want to have more free software a few years from now, it makes
! sense for you to help encourage people to contribute funds for its
! development.  The most effective approach known is to encourage
! commercial redistributors to donate.
! 
!    Users of free software systems can boost the pace of development by
! encouraging for-a-fee distributors to donate part of their selling price
! to free software developers--the Free Software Foundation, and others.
! 
!    The way to convince distributors to do this is to demand it and
! expect it from them.  So when you compare distributors, judge them
! partly by how much they give to free software development.  Show
! distributors they must compete to be the one who gives the most.
! 
!    To make this approach work, you must insist on numbers that you can
! compare, such as, "We will donate ten dollars to the Frobnitz project
! for each disk sold."  Don't be satisfied with a vague promise, such as
! "A portion of the profits are donated," since it doesn't give a basis
! for comparison.
! 
!    Even a precise fraction "of the profits from this disk" is not very
! meaningful, since creative accounting and unrelated business decisions
! can greatly alter what fraction of the sales price counts as profit.
! If the price you pay is $50, ten percent of the profit is probably less
! than a dollar; it might be a few cents, or nothing at all.
! 
!    Some redistributors do development work themselves.  This is useful
! too; but to keep everyone honest, you need to inquire how much they do,
! and what kind.  Some kinds of development make much more long-term
! difference than others.  For example, maintaining a separate version of
! a program contributes very little; maintaining the standard version of a
! program for the whole community contributes much.  Easy new ports
! contribute little, since someone else would surely do them; difficult
! ports such as adding a new CPU to the GNU Compiler Collection
! contribute more; major new features or packages contribute the most.
! 
!    By establishing the idea that supporting further development is "the
! proper thing to do" when distributing free software for a fee, we can
! assure a steady flow of resources into making more free software.
! 
!      Copyright (C) 1994 Free Software Foundation, Inc.
!      Verbatim copying and redistribution of this section is permitted
!      without royalty; alteration is not permitted.
! 
! 
! File: g77.info,  Node: Funding GNU Fortran,  Next: Getting Started,  Prev: Funding,  Up: Top
! 
! Funding GNU Fortran
! *******************
! 
!    James Craig Burley (<craig@jcb-sc.com>), the original author of
! `g77', stopped working on it in September 1999 (He has a web page at
! `http://world.std.com/%7Eburley'.)
! 
!    GNU Fortran is currently maintained by Toon Moene
! (<toon@moene.indiv.nluug.nl>), with the help of countless other
! volunteers.
! 
!    As with other GNU software, funding is important because it can pay
! for needed equipment, personnel, and so on.
! 
!    The FSF provides information on the best way to fund ongoing
! development of GNU software (such as GNU Fortran) in documents such as
! the "GNUS Bulletin".  Email <gnu@gnu.org> for information on funding
! the FSF.
! 
!    Another important way to support work on GNU Fortran is to volunteer
! to help out.
! 
!    Email <gcc@gcc.gnu.org> to volunteer for this work.
! 
!    However, we strongly expect that there will never be a version 0.6
! of `g77'.  Work on this compiler has stopped as of the release of GCC
! 3.1, except for bug fixing.  `g77' will be succeeded by `g95' - see
! `http://g95.sourceforge.net'.
! 
!    *Note Funding Free Software: Funding, for more information.
! 
! 
! File: g77.info,  Node: Getting Started,  Next: What is GNU Fortran?,  Prev: Funding GNU Fortran,  Up: Top
! 
! Getting Started
! ***************
! 
!    If you don't need help getting started reading the portions of this
! manual that are most important to you, you should skip this portion of
! the manual.
! 
!    If you are new to compilers, especially Fortran compilers, or new to
! how compilers are structured under UNIX and UNIX-like systems, you'll
! want to see *Note What is GNU Fortran?::.
! 
!    If you are new to GNU compilers, or have used only one GNU compiler
! in the past and not had to delve into how it lets you manage various
! versions and configurations of `gcc', you should see *Note G77 and
! GCC::.
! 
!    Everyone except experienced `g77' users should see *Note Invoking
! G77::.
! 
!    If you're acquainted with previous versions of `g77', you should see
! *Note News About GNU Fortran: News.  Further, if you've actually used
! previous versions of `g77', especially if you've written or modified
! Fortran code to be compiled by previous versions of `g77', you should
! see *Note Changes::.
! 
!    If you intend to write or otherwise compile code that is not already
! strictly conforming ANSI FORTRAN 77--and this is probably everyone--you
! should see *Note Language::.
! 
!    If you run into trouble getting Fortran code to compile, link, run,
! or work properly, you might find answers if you see *Note Debugging and
! Interfacing::, see *Note Collected Fortran Wisdom::, and see *Note
! Trouble::.  You might also find that the problems you are encountering
! are bugs in `g77'--see *Note Bugs::, for information on reporting them,
! after reading the other material.
! 
!    If you need further help with `g77', or with freely redistributable
! software in general, see *Note Service::.
! 
!    If you would like to help the `g77' project, see *Note Funding GNU
! Fortran::, for information on helping financially, and see *Note
! Projects::, for information on helping in other ways.
! 
!    If you're generally curious about the future of `g77', see *Note
! Projects::.  If you're curious about its past, see *Note Contributors::,
! and see *Note Funding GNU Fortran::.
! 
!    To see a few of the questions maintainers of `g77' have, and that
! you might be able to answer, see *Note Open Questions::.
! 
! 
! File: g77.info,  Node: What is GNU Fortran?,  Next: G77 and GCC,  Prev: Getting Started,  Up: Top
! 
! What is GNU Fortran?
! ********************
! 
!    GNU Fortran, or `g77', is designed initially as a free replacement
! for, or alternative to, the UNIX `f77' command.  (Similarly, `gcc' is
! designed as a replacement for the UNIX `cc' command.)
! 
!    `g77' also is designed to fit in well with the other fine GNU
! compilers and tools.
! 
!    Sometimes these design goals conflict--in such cases, resolution
! often is made in favor of fitting in well with Project GNU.  These
! cases are usually identified in the appropriate sections of this manual.
! 
!    As compilers, `g77', `gcc', and `f77' share the following
! characteristics:
! 
!    * They read a user's program, stored in a file and containing
!      instructions written in the appropriate language (Fortran, C, and
!      so on).  This file contains "source code".
! 
!    * They translate the user's program into instructions a computer can
!      carry out more quickly than it takes to translate the instructions
!      in the first place.  These instructions are called "machine
!      code"--code designed to be efficiently translated and processed by
!      a machine such as a computer.  Humans usually aren't as good
!      writing machine code as they are at writing Fortran or C, because
!      it is easy to make tiny mistakes writing machine code.  When
!      writing Fortran or C, it is easy to make big mistakes.
! 
!    * They provide information in the generated machine code that can
!      make it easier to find bugs in the program (using a debugging
!      tool, called a "debugger", such as `gdb').
! 
!    * They locate and gather machine code already generated to perform
!      actions requested by statements in the user's program.  This
!      machine code is organized into "libraries" and is located and
!      gathered during the "link" phase of the compilation process.
!      (Linking often is thought of as a separate step, because it can be
!      directly invoked via the `ld' command.  However, the `g77' and
!      `gcc' commands, as with most compiler commands, automatically
!      perform the linking step by calling on `ld' directly, unless asked
!      to not do so by the user.)
! 
!    * They attempt to diagnose cases where the user's program contains
!      incorrect usages of the language.  The "diagnostics" produced by
!      the compiler indicate the problem and the location in the user's
!      source file where the problem was first noticed.  The user can use
!      this information to locate and fix the problem.  (Sometimes an
!      incorrect usage of the language leads to a situation where the
!      compiler can no longer make any sense of what follows--while a
!      human might be able to--and thus ends up complaining about many
!      "problems" it encounters that, in fact, stem from just one
!      problem, usually the first one reported.)
! 
!    * They attempt to diagnose cases where the user's program contains a
!      correct usage of the language, but instructs the computer to do
!      something questionable.  These diagnostics often are in the form
!      of "warnings", instead of the "errors" that indicate incorrect
!      usage of the language.
! 
!    How these actions are performed is generally under the control of
! the user.  Using command-line options, the user can specify how
! persnickety the compiler is to be regarding the program (whether to
! diagnose questionable usage of the language), how much time to spend
! making the generated machine code run faster, and so on.
! 
!    `g77' consists of several components:
! 
!    * A modified version of the `gcc' command, which also might be
!      installed as the system's `cc' command.  (In many cases, `cc'
!      refers to the system's "native" C compiler, which might be a
!      non-GNU compiler, or an older version of `gcc' considered more
!      stable or that is used to build the operating system kernel.)
! 
!    * The `g77' command itself, which also might be installed as the
!      system's `f77' command.
! 
!    * The `libg2c' run-time library.  This library contains the machine
!      code needed to support capabilities of the Fortran language that
!      are not directly provided by the machine code generated by the
!      `g77' compilation phase.
! 
!      `libg2c' is just the unique name `g77' gives to its version of
!      `libf2c' to distinguish it from any copy of `libf2c' installed
!      from `f2c' (or versions of `g77' that built `libf2c' under that
!      same name) on the system.
! 
!      The maintainer of `libf2c' currently is <dmg@bell-labs.com>.
! 
!    * The compiler itself, internally named `f771'.
! 
!      Note that `f771' does not generate machine code directly--it
!      generates "assembly code" that is a more readable form of machine
!      code, leaving the conversion to actual machine code to an
!      "assembler", usually named `as'.
! 
!    `gcc' is often thought of as "the C compiler" only, but it does more
! than that.  Based on command-line options and the names given for files
! on the command line, `gcc' determines which actions to perform,
! including preprocessing, compiling (in a variety of possible
! languages), assembling, and linking.
! 
!    For example, the command `gcc foo.c' "drives" the file `foo.c'
! through the preprocessor `cpp', then the C compiler (internally named
! `cc1'), then the assembler (usually `as'), then the linker (`ld'),
! producing an executable program named `a.out' (on UNIX systems).
! 
!    As another example, the command `gcc foo.cc' would do much the same
! as `gcc foo.c', but instead of using the C compiler named `cc1', `gcc'
! would use the C++ compiler (named `cc1plus').
! 
!    In a GNU Fortran installation, `gcc' recognizes Fortran source files
! by name just like it does C and C++ source files.  It knows to use the
! Fortran compiler named `f771', instead of `cc1' or `cc1plus', to
! compile Fortran files.
! 
!    Non-Fortran-related operation of `gcc' is generally unaffected by
! installing the GNU Fortran version of `gcc'.  However, without the
! installed version of `gcc' being the GNU Fortran version, `gcc' will
! not be able to compile and link Fortran programs--and since `g77' uses
! `gcc' to do most of the actual work, neither will `g77'!
! 
!    The `g77' command is essentially just a front-end for the `gcc'
! command.  Fortran users will normally use `g77' instead of `gcc',
! because `g77' knows how to specify the libraries needed to link with
! Fortran programs (`libg2c' and `lm').  `g77' can still compile and link
! programs and source files written in other languages, just like `gcc'.
! 
!    The command `g77 -v' is a quick way to display lots of version
! information for the various programs used to compile a typical
! preprocessed Fortran source file--this produces much more output than
! `gcc -v' currently does.  (If it produces an error message near the end
! of the output--diagnostics from the linker, usually `ld'--you might
! have an out-of-date `libf2c' that improperly handles complex
! arithmetic.)  In the output of this command, the line beginning `GNU
! Fortran Front End' identifies the version number of GNU Fortran;
! immediately preceding that line is a line identifying the version of
! `gcc' with which that version of `g77' was built.
! 
!    The `libf2c' library is distributed with GNU Fortran for the
! convenience of its users, but is not part of GNU Fortran.  It contains
! the procedures needed by Fortran programs while they are running.
! 
!    For example, while code generated by `g77' is likely to do
! additions, subtractions, and multiplications "in line"--in the actual
! compiled code--it is not likely to do trigonometric functions this way.
! 
!    Instead, operations like trigonometric functions are compiled by the
! `f771' compiler (invoked by `g77' when compiling Fortran code) into
! machine code that, when run, calls on functions in `libg2c', so
! `libg2c' must be linked with almost every useful program having any
! component compiled by GNU Fortran.  (As mentioned above, the `g77'
! command takes care of all this for you.)
! 
!    The `f771' program represents most of what is unique to GNU Fortran.
! While much of the `libg2c' component comes from the `libf2c' component
! of `f2c', a free Fortran-to-C converter distributed by Bellcore (AT&T),
! plus `libU77', provided by Dave Love, and the `g77' command is just a
! small front-end to `gcc', `f771' is a combination of two rather large
! chunks of code.
! 
!    One chunk is the so-called "GNU Back End", or GBE, which knows how
! to generate fast code for a wide variety of processors.  The same GBE
! is used by the C, C++, and Fortran compiler programs `cc1', `cc1plus',
! and `f771', plus others.  Often the GBE is referred to as the "gcc back
! end" or even just "gcc"--in this manual, the term GBE is used whenever
! the distinction is important.
! 
!    The other chunk of `f771' is the majority of what is unique about
! GNU Fortran--the code that knows how to interpret Fortran programs to
! determine what they are intending to do, and then communicate that
! knowledge to the GBE for actual compilation of those programs.  This
! chunk is called the "Fortran Front End" (FFE).  The `cc1' and `cc1plus'
! programs have their own front ends, for the C and C++ languages,
! respectively.  These fronts ends are responsible for diagnosing
! incorrect usage of their respective languages by the programs the
! process, and are responsible for most of the warnings about
! questionable constructs as well.  (The GBE handles producing some
! warnings, like those concerning possible references to undefined
! variables.)
! 
!    Because so much is shared among the compilers for various languages,
! much of the behavior and many of the user-selectable options for these
! compilers are similar.  For example, diagnostics (error messages and
! warnings) are similar in appearance; command-line options like `-Wall'
! have generally similar effects; and the quality of generated code (in
! terms of speed and size) is roughly similar (since that work is done by
! the shared GBE).
! 
! 
! File: g77.info,  Node: G77 and GCC,  Next: Invoking G77,  Prev: What is GNU Fortran?,  Up: Top
! 
! Compile Fortran, C, or Other Programs
! *************************************
! 
!    A GNU Fortran installation includes a modified version of the `gcc'
! command.
! 
!    In a non-Fortran installation, `gcc' recognizes C, C++, and
! Objective-C source files.
! 
!    In a GNU Fortran installation, `gcc' also recognizes Fortran source
! files and accepts Fortran-specific command-line options, plus some
! command-line options that are designed to cater to Fortran users but
! apply to other languages as well.
! 
!    *Note Compile C; C++; Objective-C; Ada; Fortran; or Java: (gcc)G++
! and GCC, for information on the way different languages are handled by
! the GNU CC compiler (`gcc').
! 
!    Also provided as part of GNU Fortran is the `g77' command.  The
! `g77' command is designed to make compiling and linking Fortran
! programs somewhat easier than when using the `gcc' command for these
! tasks.  It does this by analyzing the command line somewhat and
! changing it appropriately before submitting it to the `gcc' command.
! 
!    Use the `-v' option with `g77' to see what is going on--the first
! line of output is the invocation of the `gcc' command.
! 
! 
! File: g77.info,  Node: Invoking G77,  Next: News,  Prev: G77 and GCC,  Up: Top
! 
! GNU Fortran Command Options
! ***************************
! 
!    The `g77' command supports all the options supported by the `gcc'
! command.  *Note GCC Command Options: (gcc)Invoking GCC, for information
! on the non-Fortran-specific aspects of the `gcc' command (and,
! therefore, the `g77' command).
! 
!    All `gcc' and `g77' options are accepted both by `g77' and by `gcc'
! (as well as any other drivers built at the same time, such as `g++'),
! since adding `g77' to the `gcc' distribution enables acceptance of
! `g77' options by all of the relevant drivers.
! 
!    In some cases, options have positive and negative forms; the
! negative form of `-ffoo' would be `-fno-foo'.  This manual documents
! only one of these two forms, whichever one is not the default.
! 
! * Menu:
! 
! * Option Summary::      Brief list of all `g77' options,
!                         without explanations.
! * Overall Options::     Controlling the kind of output:
!                         an executable, object files, assembler files,
!                         or preprocessed source.
! * Shorthand Options::   Options that are shorthand for other options.
! * Fortran Dialect Options::  Controlling the variant of Fortran language
!                              compiled.
! * Warning Options::     How picky should the compiler be?
! * Debugging Options::   Symbol tables, measurements, and debugging dumps.
! * Optimize Options::    How much optimization?
! * Preprocessor Options:: Controlling header files and macro definitions.
!                          Also, getting dependency information for Make.
! * Directory Options::   Where to find header files and libraries.
!                         Where to find the compiler executable files.
! * Code Gen Options::    Specifying conventions for function calls, data layout
!                         and register usage.
! * Environment Variables:: Env vars that affect GNU Fortran.
! 
! 
! File: g77.info,  Node: Option Summary,  Next: Overall Options,  Up: Invoking G77
! 
! Option Summary
! ==============
! 
!    Here is a summary of all the options specific to GNU Fortran, grouped
! by type.  Explanations are in the following sections.
! 
! _Overall Options_
!      *Note Options Controlling the Kind of Output: Overall Options.
!           -fversion  -fset-g77-defaults  -fno-silent
! 
! _Shorthand Options_
!      *Note Shorthand Options::.
!           -ff66  -fno-f66  -ff77  -fno-f77  -fno-ugly
! 
! _Fortran Language Options_
!      *Note Options Controlling Fortran Dialect: Fortran Dialect Options.
!           -ffree-form  -fno-fixed-form  -ff90 
!           -fvxt  -fdollar-ok  -fno-backslash 
!           -fno-ugly-args  -fno-ugly-assign  -fno-ugly-assumed 
!           -fugly-comma  -fugly-complex  -fugly-init  -fugly-logint 
!           -fonetrip  -ftypeless-boz 
!           -fintrin-case-initcap  -fintrin-case-upper 
!           -fintrin-case-lower  -fintrin-case-any 
!           -fmatch-case-initcap  -fmatch-case-upper 
!           -fmatch-case-lower  -fmatch-case-any 
!           -fsource-case-upper  -fsource-case-lower 
!           -fsource-case-preserve 
!           -fsymbol-case-initcap  -fsymbol-case-upper 
!           -fsymbol-case-lower  -fsymbol-case-any 
!           -fcase-strict-upper  -fcase-strict-lower 
!           -fcase-initcap  -fcase-upper  -fcase-lower  -fcase-preserve 
!           -ff2c-intrinsics-delete  -ff2c-intrinsics-hide 
!           -ff2c-intrinsics-disable  -ff2c-intrinsics-enable 
!           -fbadu77-intrinsics-delete  -fbadu77-intrinsics-hide 
!           -fbadu77-intrinsics-disable  -fbadu77-intrinsics-enable 
!           -ff90-intrinsics-delete  -ff90-intrinsics-hide 
!           -ff90-intrinsics-disable  -ff90-intrinsics-enable 
!           -fgnu-intrinsics-delete  -fgnu-intrinsics-hide 
!           -fgnu-intrinsics-disable  -fgnu-intrinsics-enable 
!           -fmil-intrinsics-delete  -fmil-intrinsics-hide 
!           -fmil-intrinsics-disable  -fmil-intrinsics-enable 
!           -funix-intrinsics-delete  -funix-intrinsics-hide 
!           -funix-intrinsics-disable  -funix-intrinsics-enable 
!           -fvxt-intrinsics-delete  -fvxt-intrinsics-hide 
!           -fvxt-intrinsics-disable  -fvxt-intrinsics-enable 
!           -ffixed-line-length-N  -ffixed-line-length-none
! 
! _Warning Options_
!      *Note Options to Request or Suppress Warnings: Warning Options.
!           -fsyntax-only  -pedantic  -pedantic-errors  -fpedantic 
!           -w  -Wno-globals  -Wimplicit  -Wunused  -Wuninitialized 
!           -Wall  -Wsurprising 
!           -Werror  -W
! 
! _Debugging Options_
!      *Note Options for Debugging Your Program or GCC: Debugging Options.
!           -g
! 
! _Optimization Options_
!      *Note Options that Control Optimization: Optimize Options.
!           -malign-double 
!           -ffloat-store  -fforce-mem  -fforce-addr  -fno-inline 
!           -ffast-math  -fstrength-reduce  -frerun-cse-after-loop 
!           -funsafe-math-optimizations -ffinite-math-only -fno-trapping-math 
!           -fexpensive-optimizations  -fdelayed-branch 
!           -fschedule-insns  -fschedule-insn2  -fcaller-saves 
!           -funroll-loops  -funroll-all-loops 
!           -fno-move-all-movables  -fno-reduce-all-givs 
!           -fno-rerun-loop-opt
! 
! _Directory Options_
!      *Note Options for Directory Search: Directory Options.
!           -IDIR  -I-
! 
! _Code Generation Options_
!      *Note Options for Code Generation Conventions: Code Gen Options.
!           -fno-automatic  -finit-local-zero  -fno-f2c 
!           -ff2c-library  -fno-underscoring  -fno-ident 
!           -fpcc-struct-return  -freg-struct-return 
!           -fshort-double  -fno-common  -fpack-struct 
!           -fzeros  -fno-second-underscore 
!           -femulate-complex 
!           -falias-check  -fargument-alias 
!           -fargument-noalias  -fno-argument-noalias-global 
!           -fno-globals  -fflatten-arrays 
!           -fbounds-check  -ffortran-bounds-check
! 
! * Menu:
! 
! * Overall Options::     Controlling the kind of output:
!                         an executable, object files, assembler files,
!                         or preprocessed source.
! * Shorthand Options::   Options that are shorthand for other options.
! * Fortran Dialect Options::  Controlling the variant of Fortran language
!                              compiled.
! * Warning Options::     How picky should the compiler be?
! * Debugging Options::   Symbol tables, measurements, and debugging dumps.
! * Optimize Options::    How much optimization?
! * Preprocessor Options:: Controlling header files and macro definitions.
!                          Also, getting dependency information for Make.
! * Directory Options::   Where to find header files and libraries.
!                         Where to find the compiler executable files.
! * Code Gen Options::    Specifying conventions for function calls, data layout
!                         and register usage.
! 
! 
! File: g77.info,  Node: Overall Options,  Next: Shorthand Options,  Prev: Option Summary,  Up: Invoking G77
! 
! Options Controlling the Kind of Output
! ======================================
! 
!    Compilation can involve as many as four stages: preprocessing, code
! generation (often what is really meant by the term "compilation"),
! assembly, and linking, always in that order.  The first three stages
! apply to an individual source file, and end by producing an object
! file; linking combines all the object files (those newly compiled, and
! those specified as input) into an executable file.
! 
!    For any given input file, the file name suffix determines what kind
! of program is contained in the file--that is, the language in which the
! program is written is generally indicated by the suffix.  Suffixes
! specific to GNU Fortran are listed below.  *Note Options Controlling
! the Kind of Output: (gcc)Overall Options, for information on suffixes
! recognized by GNU CC.
! 
! `FILE.f'
! 
! `FILE.for'
! 
! `FILE.FOR'
!      Fortran source code that should not be preprocessed.
! 
!      Such source code cannot contain any preprocessor directives, such
!      as `#include', `#define', `#if', and so on.
! 
!      You can force `.f' files to be preprocessed by `cpp' by using `-x
!      f77-cpp-input'.  *Note LEX::.
! 
! `FILE.F'
! 
! `FILE.fpp'
! 
! `FILE.FPP'
!      Fortran source code that must be preprocessed (by the C
!      preprocessor `cpp', which is part of GNU CC).
! 
!      Note that preprocessing is not extended to the contents of files
!      included by the `INCLUDE' directive--the `#include' preprocessor
!      directive must be used instead.
! 
! `FILE.r'
!      Ratfor source code, which must be preprocessed by the `ratfor'
!      command, which is available separately (as it is not yet part of
!      the GNU Fortran distribution).  One version in Fortran, adapted
!      for use with `g77' is at `ftp://members.aol.com/n8tm/rat7.uue' (of
!      uncertain copyright status).  Another, public domain version in C
!      is at `http://sepwww.stanford.edu/sep/prof/ratfor.shar.2'.
! 
!    UNIX users typically use the `FILE.f' and `FILE.F' nomenclature.
! Users of other operating systems, especially those that cannot
! distinguish upper-case letters from lower-case letters in their file
! names, typically use the `FILE.for' and `FILE.fpp' nomenclature.
! 
!    Use of the preprocessor `cpp' allows use of C-like constructs such
! as `#define' and `#include', but can lead to unexpected, even mistaken,
! results due to Fortran's source file format.  It is recommended that
! use of the C preprocessor be limited to `#include' and, in conjunction
! with `#define', only `#if' and related directives, thus avoiding
! in-line macro expansion entirely.  This recommendation applies
! especially when using the traditional fixed source form.  With free
! source form, fewer unexpected transformations are likely to happen, but
! use of constructs such as Hollerith and character constants can
! nevertheless present problems, especially when these are continued
! across multiple source lines.  These problems result, primarily, from
! differences between the way such constants are interpreted by the C
! preprocessor and by a Fortran compiler.
! 
!    Another example of a problem that results from using the C
! preprocessor is that a Fortran comment line that happens to contain any
! characters "interesting" to the C preprocessor, such as a backslash at
! the end of the line, is not recognized by the preprocessor as a comment
! line, so instead of being passed through "raw", the line is edited
! according to the rules for the preprocessor.  For example, the
! backslash at the end of the line is removed, along with the subsequent
! newline, resulting in the next line being effectively commented
! out--unfortunate if that line is a non-comment line of important code!
! 
!    _Note:_ The `-traditional' and `-undef' flags are supplied to `cpp'
! by default, to help avoid unpleasant surprises.  *Note Options
! Controlling the Preprocessor: (gcc)Preprocessor Options.  This means
! that ANSI C preprocessor features (such as the `#' operator) aren't
! available, and only variables in the C reserved namespace (generally,
! names with a leading underscore) are liable to substitution by C
! predefines.  Thus, if you want to do system-specific tests, use, for
! example, `#ifdef __linux__' rather than `#ifdef linux'.  Use the `-v'
! option to see exactly how the preprocessor is invoked.
! 
!    Unfortunately, the `-traditional' flag will not avoid an error from
! anything that `cpp' sees as an unterminated C comment, such as:
!      C Some Fortran compilers accept /* as starting
!      C an inline comment.
!    *Note Trailing Comment::.
! 
!    The following options that affect overall processing are recognized
! by the `g77' and `gcc' commands in a GNU Fortran installation:
! 
! `-fversion'
!      Ensure that the `g77' version of the compiler phase is reported,
!      if run, and, starting in `egcs' version 1.1, that internal
!      consistency checks in the `f771' program are run.
! 
!      This option is supplied automatically when `-v' or `--verbose' is
!      specified as a command-line option for `g77' or `gcc' and when the
!      resulting commands compile Fortran source files.
! 
!      In GCC 3.1, this is changed back to the behavior `gcc' displays
!      for `.c' files.
! 
! `-fset-g77-defaults'
!      _Version info:_ This option was obsolete as of `egcs' version 1.1.
!      The effect is instead achieved by the `lang_init_options' routine
!      in `gcc/gcc/f/com.c'.
! 
!      Set up whatever `gcc' options are to apply to Fortran
!      compilations, and avoid running internal consistency checks that
!      might take some time.
! 
!      This option is supplied automatically when compiling Fortran code
!      via the `g77' or `gcc' command.  The description of this option is
!      provided so that users seeing it in the output of, say, `g77 -v'
!      understand why it is there.
! 
!      Also, developers who run `f771' directly might want to specify it
!      by hand to get the same defaults as they would running `f771' via
!      `g77' or `gcc' However, such developers should, after linking a
!      new `f771' executable, invoke it without this option once, e.g.
!      via `./f771 -quiet < /dev/null', to ensure that they have not
!      introduced any internal inconsistencies (such as in the table of
!      intrinsics) before proceeding--`g77' will crash with a diagnostic
!      if it detects an inconsistency.
! 
! `-fno-silent'
!      Print (to `stderr') the names of the program units as they are
!      compiled, in a form similar to that used by popular UNIX `f77'
!      implementations and `f2c'
! 
!    *Note Options Controlling the Kind of Output: (gcc)Overall Options,
! for information on more options that control the overall operation of
! the `gcc' command (and, by extension, the `g77' command).
! 
! 
! File: g77.info,  Node: Shorthand Options,  Next: Fortran Dialect Options,  Prev: Overall Options,  Up: Invoking G77
! 
! Shorthand Options
! =================
! 
!    The following options serve as "shorthand" for other options
! accepted by the compiler:
! 
! `-fugly'
!      _Note:_ This option is no longer supported.  The information,
!      below, is provided to aid in the conversion of old scripts.
! 
!      Specify that certain "ugly" constructs are to be quietly accepted.
!      Same as:
! 
!           -fugly-args -fugly-assign -fugly-assumed
!           -fugly-comma -fugly-complex -fugly-init
!           -fugly-logint
! 
!      These constructs are considered inappropriate to use in new or
!      well-maintained portable Fortran code, but widely used in old code.
!      *Note Distensions::, for more information.
! 
! `-fno-ugly'
!      Specify that all "ugly" constructs are to be noisily rejected.
!      Same as:
! 
!           -fno-ugly-args -fno-ugly-assign -fno-ugly-assumed
!           -fno-ugly-comma -fno-ugly-complex -fno-ugly-init
!           -fno-ugly-logint
! 
!      *Note Distensions::, for more information.
! 
! `-ff66'
!      Specify that the program is written in idiomatic FORTRAN 66.  Same
!      as `-fonetrip -fugly-assumed'.
! 
!      The `-fno-f66' option is the inverse of `-ff66'.  As such, it is
!      the same as `-fno-onetrip -fno-ugly-assumed'.
! 
!      The meaning of this option is likely to be refined as future
!      versions of `g77' provide more compatibility with other existing
!      and obsolete Fortran implementations.
! 
! `-ff77'
!      Specify that the program is written in idiomatic UNIX FORTRAN 77
!      and/or the dialect accepted by the `f2c' product.  Same as
!      `-fbackslash -fno-typeless-boz'.
! 
!      The meaning of this option is likely to be refined as future
!      versions of `g77' provide more compatibility with other existing
!      and obsolete Fortran implementations.
! 
! `-fno-f77'
!      The `-fno-f77' option is _not_ the inverse of `-ff77'.  It
!      specifies that the program is not written in idiomatic UNIX
!      FORTRAN 77 or `f2c' but in a more widely portable dialect.
!      `-fno-f77' is the same as `-fno-backslash'.
! 
!      The meaning of this option is likely to be refined as future
!      versions of `g77' provide more compatibility with other existing
!      and obsolete Fortran implementations.
! 
! 
! File: g77.info,  Node: Fortran Dialect Options,  Next: Warning Options,  Prev: Shorthand Options,  Up: Invoking G77
! 
! Options Controlling Fortran Dialect
! ===================================
! 
!    The following options control the dialect of Fortran that the
! compiler accepts:
! 
! `-ffree-form'
! 
! `-fno-fixed-form'
!      Specify that the source file is written in free form (introduced
!      in Fortran 90) instead of the more-traditional fixed form.
! 
! `-ff90'
!      Allow certain Fortran-90 constructs.
! 
!      This option controls whether certain Fortran 90 constructs are
!      recognized.  (Other Fortran 90 constructs might or might not be
!      recognized depending on other options such as `-fvxt',
!      `-ff90-intrinsics-enable', and the current level of support for
!      Fortran 90.)
! 
!      *Note Fortran 90::, for more information.
! 
! `-fvxt'
!      Specify the treatment of certain constructs that have different
!      meanings depending on whether the code is written in GNU Fortran
!      (based on FORTRAN 77 and akin to Fortran 90) or VXT Fortran (more
!      like VAX FORTRAN).
! 
!      The default is `-fno-vxt'.  `-fvxt' specifies that the VXT Fortran
!      interpretations for those constructs are to be chosen.
! 
!      *Note VXT Fortran::, for more information.
! 
! `-fdollar-ok'
!      Allow `$' as a valid character in a symbol name.
! 
! `-fno-backslash'
!      Specify that `\' is not to be specially interpreted in character
!      and Hollerith constants a la C and many UNIX Fortran compilers.
! 
!      For example, with `-fbackslash' in effect, `A\nB' specifies three
!      characters, with the second one being newline.  With
!      `-fno-backslash', it specifies four characters, `A', `\', `n', and
!      `B'.
! 
!      Note that `g77' implements a fairly general form of backslash
!      processing that is incompatible with the narrower forms supported
!      by some other compilers.  For example, `'A\003B'' is a
!      three-character string in `g77' whereas other compilers that
!      support backslash might not support the three-octal-digit form,
!      and thus treat that string as longer than three characters.
! 
!      *Note Backslash in Constants::, for information on why
!      `-fbackslash' is the default instead of `-fno-backslash'.
! 
! `-fno-ugly-args'
!      Disallow passing Hollerith and typeless constants as actual
!      arguments (for example, `CALL FOO(4HABCD)').
! 
!      *Note Ugly Implicit Argument Conversion::, for more information.
! 
! `-fugly-assign'
!      Use the same storage for a given variable regardless of whether it
!      is used to hold an assigned-statement label (as in `ASSIGN 10 TO
!      I') or used to hold numeric data (as in `I = 3').
! 
!      *Note Ugly Assigned Labels::, for more information.
! 
! `-fugly-assumed'
!      Assume any dummy array with a final dimension specified as `1' is
!      really an assumed-size array, as if `*' had been specified for the
!      final dimension instead of `1'.
! 
!      For example, `DIMENSION X(1)' is treated as if it had read
!      `DIMENSION X(*)'.
! 
!      *Note Ugly Assumed-Size Arrays::, for more information.
! 
! `-fugly-comma'
!      In an external-procedure invocation, treat a trailing comma in the
!      argument list as specification of a trailing null argument, and
!      treat an empty argument list as specification of a single null
!      argument.
! 
!      For example, `CALL FOO(,)' is treated as `CALL FOO(%VAL(0),
!      %VAL(0))'.  That is, _two_ null arguments are specified by the
!      procedure call when `-fugly-comma' is in force.  And `F = FUNC()'
!      is treated as `F = FUNC(%VAL(0))'.
! 
!      The default behavior, `-fno-ugly-comma', is to ignore a single
!      trailing comma in an argument list.  So, by default, `CALL
!      FOO(X,)' is treated exactly the same as `CALL FOO(X)'.
! 
!      *Note Ugly Null Arguments::, for more information.
! 
! `-fugly-complex'
!      Do not complain about `REAL(EXPR)' or `AIMAG(EXPR)' when EXPR is a
!      `COMPLEX' type other than `COMPLEX(KIND=1)'--usually this is used
!      to permit `COMPLEX(KIND=2)' (`DOUBLE COMPLEX') operands.
! 
!      The `-ff90' option controls the interpretation of this construct.
! 
!      *Note Ugly Complex Part Extraction::, for more information.
! 
! `-fno-ugly-init'
!      Disallow use of Hollerith and typeless constants as initial values
!      (in `PARAMETER' and `DATA' statements), and use of character
!      constants to initialize numeric types and vice versa.
! 
!      For example, `DATA I/'F'/, CHRVAR/65/, J/4HABCD/' is disallowed by
!      `-fno-ugly-init'.
! 
!      *Note Ugly Conversion of Initializers::, for more information.
! 
! `-fugly-logint'
!      Treat `INTEGER' and `LOGICAL' variables and expressions as
!      potential stand-ins for each other.
! 
!      For example, automatic conversion between `INTEGER' and `LOGICAL'
!      is enabled, for many contexts, via this option.
! 
!      *Note Ugly Integer Conversions::, for more information.
! 
! `-fonetrip'
!      Executable iterative `DO' loops are to be executed at least once
!      each time they are reached.
! 
!      ANSI FORTRAN 77 and more recent versions of the Fortran standard
!      specify that the body of an iterative `DO' loop is not executed if
!      the number of iterations calculated from the parameters of the
!      loop is less than 1.  (For example, `DO 10 I = 1, 0'.)  Such a
!      loop is called a "zero-trip loop".
! 
!      Prior to ANSI FORTRAN 77, many compilers implemented `DO' loops
!      such that the body of a loop would be executed at least once, even
!      if the iteration count was zero.  Fortran code written assuming
!      this behavior is said to require "one-trip loops".  For example,
!      some code written to the FORTRAN 66 standard expects this behavior
!      from its `DO' loops, although that standard did not specify this
!      behavior.
! 
!      The `-fonetrip' option specifies that the source file(s) being
!      compiled require one-trip loops.
! 
!      This option affects only those loops specified by the (iterative)
!      `DO' statement and by implied-`DO' lists in I/O statements.  Loops
!      specified by implied-`DO' lists in `DATA' and specification
!      (non-executable) statements are not affected.
! 
! `-ftypeless-boz'
!      Specifies that prefix-radix non-decimal constants, such as
!      `Z'ABCD'', are typeless instead of `INTEGER(KIND=1)'.
! 
!      You can test for yourself whether a particular compiler treats the
!      prefix form as `INTEGER(KIND=1)' or typeless by running the
!      following program:
! 
!           EQUIVALENCE (I, R)
!           R = Z'ABCD1234'
!           J = Z'ABCD1234'
!           IF (J .EQ. I) PRINT *, 'Prefix form is TYPELESS'
!           IF (J .NE. I) PRINT *, 'Prefix form is INTEGER'
!           END
! 
!      Reports indicate that many compilers process this form as
!      `INTEGER(KIND=1)', though a few as typeless, and at least one
!      based on a command-line option specifying some kind of
!      compatibility.
! 
! `-fintrin-case-initcap'
! 
! `-fintrin-case-upper'
! 
! `-fintrin-case-lower'
! 
! `-fintrin-case-any'
!      Specify expected case for intrinsic names.  `-fintrin-case-lower'
!      is the default.
! 
! `-fmatch-case-initcap'
! 
! `-fmatch-case-upper'
! 
! `-fmatch-case-lower'
! 
! `-fmatch-case-any'
!      Specify expected case for keywords.  `-fmatch-case-lower' is the
!      default.
! 
! `-fsource-case-upper'
! 
! `-fsource-case-lower'
! 
! `-fsource-case-preserve'
!      Specify whether source text other than character and Hollerith
!      constants is to be translated to uppercase, to lowercase, or
!      preserved as is.  `-fsource-case-lower' is the default.
! 
! `-fsymbol-case-initcap'
! 
! `-fsymbol-case-upper'
! 
! `-fsymbol-case-lower'
! 
! `-fsymbol-case-any'
!      Specify valid cases for user-defined symbol names.
!      `-fsymbol-case-any' is the default.
! 
! `-fcase-strict-upper'
!      Same as `-fintrin-case-upper -fmatch-case-upper
!      -fsource-case-preserve -fsymbol-case-upper'.  (Requires all
!      pertinent source to be in uppercase.)
! 
! `-fcase-strict-lower'
!      Same as `-fintrin-case-lower -fmatch-case-lower
!      -fsource-case-preserve -fsymbol-case-lower'.  (Requires all
!      pertinent source to be in lowercase.)
! 
! `-fcase-initcap'
!      Same as `-fintrin-case-initcap -fmatch-case-initcap
!      -fsource-case-preserve -fsymbol-case-initcap'.  (Requires all
!      pertinent source to be in initial capitals, as in `Print
!      *,SqRt(Value)'.)
! 
! `-fcase-upper'
!      Same as `-fintrin-case-any -fmatch-case-any -fsource-case-upper
!      -fsymbol-case-any'.  (Maps all pertinent source to uppercase.)
! 
! `-fcase-lower'
!      Same as `-fintrin-case-any -fmatch-case-any -fsource-case-lower
!      -fsymbol-case-any'.  (Maps all pertinent source to lowercase.)
! 
! `-fcase-preserve'
!      Same as `-fintrin-case-any -fmatch-case-any -fsource-case-preserve
!      -fsymbol-case-any'.  (Preserves all case in user-defined symbols,
!      while allowing any-case matching of intrinsics and keywords.  For
!      example, `call Foo(i,I)' would pass two _different_ variables
!      named `i' and `I' to a procedure named `Foo'.)
! 
! `-fbadu77-intrinsics-delete'
! 
! `-fbadu77-intrinsics-hide'
! 
! `-fbadu77-intrinsics-disable'
! 
! `-fbadu77-intrinsics-enable'
!      Specify status of UNIX intrinsics having inappropriate forms.
!      `-fbadu77-intrinsics-enable' is the default.  *Note Intrinsic
!      Groups::.
! 
! `-ff2c-intrinsics-delete'
! 
! `-ff2c-intrinsics-hide'
! 
! `-ff2c-intrinsics-disable'
! 
! `-ff2c-intrinsics-enable'
!      Specify status of f2c-specific intrinsics.
!      `-ff2c-intrinsics-enable' is the default.  *Note Intrinsic
!      Groups::.
! 
! `-ff90-intrinsics-delete'
! 
! `-ff90-intrinsics-hide'
! 
! `-ff90-intrinsics-disable'
! 
! `-ff90-intrinsics-enable'
!      Specify status of F90-specific intrinsics.
!      `-ff90-intrinsics-enable' is the default.  *Note Intrinsic
!      Groups::.
! 
! `-fgnu-intrinsics-delete'
! 
! `-fgnu-intrinsics-hide'
! 
! `-fgnu-intrinsics-disable'
! 
! `-fgnu-intrinsics-enable'
!      Specify status of Digital's COMPLEX-related intrinsics.
!      `-fgnu-intrinsics-enable' is the default.  *Note Intrinsic
!      Groups::.
! 
! `-fmil-intrinsics-delete'
! 
! `-fmil-intrinsics-hide'
! 
! `-fmil-intrinsics-disable'
! 
! `-fmil-intrinsics-enable'
!      Specify status of MIL-STD-1753-specific intrinsics.
!      `-fmil-intrinsics-enable' is the default.  *Note Intrinsic
!      Groups::.
! 
! `-funix-intrinsics-delete'
! 
! `-funix-intrinsics-hide'
! 
! `-funix-intrinsics-disable'
! 
! `-funix-intrinsics-enable'
!      Specify status of UNIX intrinsics.  `-funix-intrinsics-enable' is
!      the default.  *Note Intrinsic Groups::.
! 
! `-fvxt-intrinsics-delete'
! 
! `-fvxt-intrinsics-hide'
! 
! `-fvxt-intrinsics-disable'
! 
! `-fvxt-intrinsics-enable'
!      Specify status of VXT intrinsics.  `-fvxt-intrinsics-enable' is
!      the default.  *Note Intrinsic Groups::.
! 
! `-ffixed-line-length-N'
!      Set column after which characters are ignored in typical fixed-form
!      lines in the source file, and through which spaces are assumed (as
!      if padded to that length) after the ends of short fixed-form lines.
! 
!      Popular values for N include 72 (the standard and the default), 80
!      (card image), and 132 (corresponds to "extended-source" options in
!      some popular compilers).  N may be `none', meaning that the entire
!      line is meaningful and that continued character constants never
!      have implicit spaces appended to them to fill out the line.
!      `-ffixed-line-length-0' means the same thing as
!      `-ffixed-line-length-none'.
! 
!      *Note Source Form::, for more information.
! 
! 
! File: g77.info,  Node: Warning Options,  Next: Debugging Options,  Prev: Fortran Dialect Options,  Up: Invoking G77
! 
! Options to Request or Suppress Warnings
! =======================================
! 
!    Warnings are diagnostic messages that report constructions which are
! not inherently erroneous but which are risky or suggest there might
! have been an error.
! 
!    You can request many specific warnings with options beginning `-W',
! for example `-Wimplicit' to request warnings on implicit declarations.
! Each of these specific warning options also has a negative form
! beginning `-Wno-' to turn off warnings; for example, `-Wno-implicit'.
! This manual lists only one of the two forms, whichever is not the
! default.
! 
!    These options control the amount and kinds of warnings produced by
! GNU Fortran:
! 
! `-fsyntax-only'
!      Check the code for syntax errors, but don't do anything beyond
!      that.
! 
! `-pedantic'
!      Issue warnings for uses of extensions to ANSI FORTRAN 77.
!      `-pedantic' also applies to C-language constructs where they occur
!      in GNU Fortran source files, such as use of `\e' in a character
!      constant within a directive like `#include'.
! 
!      Valid ANSI FORTRAN 77 programs should compile properly with or
!      without this option.  However, without this option, certain GNU
!      extensions and traditional Fortran features are supported as well.
!      With this option, many of them are rejected.
! 
!      Some users try to use `-pedantic' to check programs for strict ANSI
!      conformance.  They soon find that it does not do quite what they
!      want--it finds some non-ANSI practices, but not all.  However,
!      improvements to `g77' in this area are welcome.
! 
! `-pedantic-errors'
!      Like `-pedantic', except that errors are produced rather than
!      warnings.
! 
! `-fpedantic'
!      Like `-pedantic', but applies only to Fortran constructs.
! 
! `-w'
!      Inhibit all warning messages.
! 
! `-Wno-globals'
!      Inhibit warnings about use of a name as both a global name (a
!      subroutine, function, or block data program unit, or a common
!      block) and implicitly as the name of an intrinsic in a source file.
! 
!      Also inhibit warnings about inconsistent invocations and/or
!      definitions of global procedures (function and subroutines).  Such
!      inconsistencies include different numbers of arguments and
!      different types of arguments.
! 
! `-Wimplicit'
!      Warn whenever a variable, array, or function is implicitly
!      declared.  Has an effect similar to using the `IMPLICIT NONE'
!      statement in every program unit.  (Some Fortran compilers provide
!      this feature by an option named `-u' or `/WARNINGS=DECLARATIONS'.)
! 
! `-Wunused'
!      Warn whenever a variable is unused aside from its declaration.
! 
! `-Wuninitialized'
!      Warn whenever an automatic variable is used without first being
!      initialized.
! 
!      These warnings are possible only in optimizing compilation,
!      because they require data-flow information that is computed only
!      when optimizing.  If you don't specify `-O', you simply won't get
!      these warnings.
! 
!      These warnings occur only for variables that are candidates for
!      register allocation.  Therefore, they do not occur for a variable
!      whose address is taken, or whose size is other than 1, 2, 4 or 8
!      bytes.  Also, they do not occur for arrays, even when they are in
!      registers.
! 
!      Note that there might be no warning about a variable that is used
!      only to compute a value that itself is never used, because such
!      computations may be deleted by data-flow analysis before the
!      warnings are printed.
! 
!      These warnings are made optional because GNU Fortran is not smart
!      enough to see all the reasons why the code might be correct
!      despite appearing to have an error.  Here is one example of how
!      this can happen:
! 
!           SUBROUTINE DISPAT(J)
!           IF (J.EQ.1) I=1
!           IF (J.EQ.2) I=4
!           IF (J.EQ.3) I=5
!           CALL FOO(I)
!           END
! 
!      If the value of `J' is always 1, 2 or 3, then `I' is always
!      initialized, but GNU Fortran doesn't know this.  Here is another
!      common case:
! 
!           SUBROUTINE MAYBE(FLAG)
!           LOGICAL FLAG
!           IF (FLAG) VALUE = 9.4
!           ...
!           IF (FLAG) PRINT *, VALUE
!           END
! 
!      This has no bug because `VALUE' is used only if it is set.
! 
! `-Wall'
!      The `-Wunused' and `-Wuninitialized' options combined.  These are
!      all the options which pertain to usage that we recommend avoiding
!      and that we believe is easy to avoid.  (As more warnings are added
!      to `g77' some might be added to the list enabled by `-Wall'.)
! 
!    The remaining `-W...' options are not implied by `-Wall' because
! they warn about constructions that we consider reasonable to use, on
! occasion, in clean programs.
! 
! `-Wsurprising'
!      Warn about "suspicious" constructs that are interpreted by the
!      compiler in a way that might well be surprising to someone reading
!      the code.  These differences can result in subtle,
!      compiler-dependent (even machine-dependent) behavioral differences.
!      The constructs warned about include:
! 
!         * Expressions having two arithmetic operators in a row, such as
!           `X*-Y'.  Such a construct is nonstandard, and can produce
!           unexpected results in more complicated situations such as
!           `X**-Y*Z'.  `g77' along with many other compilers, interprets
!           this example differently than many programmers, and a few
!           other compilers.  Specifically, `g77' interprets `X**-Y*Z' as
!           `(X**(-Y))*Z', while others might think it should be
!           interpreted as `X**(-(Y*Z))'.
! 
!           A revealing example is the constant expression `2**-2*1.',
!           which `g77' evaluates to .25, while others might evaluate it
!           to 0., the difference resulting from the way precedence
!           affects type promotion.
! 
!           (The `-fpedantic' option also warns about expressions having
!           two arithmetic operators in a row.)
! 
!         * Expressions with a unary minus followed by an operand and then
!           a binary operator other than plus or minus.  For example,
!           `-2**2' produces a warning, because the precedence is
!           `-(2**2)', yielding -4, not `(-2)**2', which yields 4, and
!           which might represent what a programmer expects.
! 
!           An example of an expression producing different results in a
!           surprising way is `-I*S', where I holds the value
!           `-2147483648' and S holds `0.5'.  On many systems, negating I
!           results in the same value, not a positive number, because it
!           is already the lower bound of what an `INTEGER(KIND=1)'
!           variable can hold.  So, the expression evaluates to a
!           positive number, while the "expected" interpretation,
!           `(-I)*S', would evaluate to a negative number.
! 
!           Even cases such as `-I*J' produce warnings, even though, in
!           most configurations and situations, there is no computational
!           difference between the results of the two
!           interpretations--the purpose of this warning is to warn about
!           differing interpretations and encourage a better style of
!           coding, not to identify only those places where bugs might
!           exist in the user's code.
! 
!         * `DO' loops with `DO' variables that are not of integral
!           type--that is, using `REAL' variables as loop control
!           variables.  Although such loops can be written to work in the
!           "obvious" way, the way `g77' is required by the Fortran
!           standard to interpret such code is likely to be quite
!           different from the way many programmers expect.  (This is
!           true of all `DO' loops, but the differences are pronounced
!           for non-integral loop control variables.)
! 
!           *Note Loops::, for more information.
! 
! `-Werror'
!      Make all warnings into errors.
! 
! `-W'
!      Turns on "extra warnings" and, if optimization is specified via
!      `-O', the `-Wuninitialized' option.  (This might change in future
!      versions of `g77'
! 
!      "Extra warnings" are issued for:
! 
!         * Unused parameters to a procedure (when `-Wunused' also is
!           specified).
! 
!         * Overflows involving floating-point constants (not available
!           for certain configurations).
! 
!    *Note Options to Request or Suppress Warnings: (gcc)Warning Options,
! for information on more options offered by the GBE shared by `g77'
! `gcc' and other GNU compilers.
! 
!    Some of these have no effect when compiling programs written in
! Fortran:
! 
! `-Wcomment'
! 
! `-Wformat'
! 
! `-Wparentheses'
! 
! `-Wswitch'
! 
! `-Wswitch-default'
! 
! `-Wswitch-enum'
! 
! `-Wtraditional'
! 
! `-Wshadow'
! 
! `-Wid-clash-LEN'
! 
! `-Wlarger-than-LEN'
! 
! `-Wconversion'
! 
! `-Waggregate-return'
! 
! `-Wredundant-decls'
!      These options all could have some relevant meaning for GNU Fortran
!      programs, but are not yet supported.
! 
! 
! File: g77.info,  Node: Debugging Options,  Next: Optimize Options,  Prev: Warning Options,  Up: Invoking G77
! 
! Options for Debugging Your Program or GNU Fortran
! =================================================
! 
!    GNU Fortran has various special options that are used for debugging
! either your program or `g77'
! 
! `-g'
!      Produce debugging information in the operating system's native
!      format (stabs, COFF, XCOFF, or DWARF).  GDB can work with this
!      debugging information.
! 
!      A sample debugging session looks like this (note the use of the
!      breakpoint):
!           $ cat gdb.f
!                 PROGRAM PROG
!                 DIMENSION A(10)
!                 DATA A /1.,2.,3.,4.,5.,6.,7.,8.,9.,10./
!                 A(5) = 4.
!                 PRINT*,A
!                 END
!           $ g77 -g -O gdb.f
!           $ gdb a.out
!           ...
!           (gdb) break MAIN__
!           Breakpoint 1 at 0x8048e96: file gdb.f, line 4.
!           (gdb) run
!           Starting program: /home/toon/g77-bugs/./a.out
!           Breakpoint 1, MAIN__ () at gdb.f:4
!           4             A(5) = 4.
!           Current language:  auto; currently fortran
!           (gdb) print a(5)
!           $1 = 5
!           (gdb) step
!           5             PRINT*,A
!           (gdb) print a(5)
!           $2 = 4
!           ...
!      One could also add the setting of the breakpoint and the first run
!      command to the file `.gdbinit' in the current directory, to
!      simplify the debugging session.
! 
!    *Note Options for Debugging Your Program or GCC: (gcc)Debugging
! Options, for more information on debugging options.
! 
! 
! File: g77.info,  Node: Optimize Options,  Next: Preprocessor Options,  Prev: Debugging Options,  Up: Invoking G77
! 
! Options That Control Optimization
! =================================
! 
!    Most Fortran users will want to use no optimization when developing
! and testing programs, and use `-O' or `-O2' when compiling programs for
! late-cycle testing and for production use.  However, note that certain
! diagnostics--such as for uninitialized variables--depend on the flow
! analysis done by `-O', i.e. you must use `-O' or `-O2' to get such
! diagnostics.
! 
!    The following flags have particular applicability when compiling
! Fortran programs:
! 
! `-malign-double'
!      (Intel x86 architecture only.)
! 
!      Noticeably improves performance of `g77' programs making heavy use
!      of `REAL(KIND=2)' (`DOUBLE PRECISION') data on some systems.  In
!      particular, systems using Pentium, Pentium Pro, 586, and 686
!      implementations of the i386 architecture execute programs faster
!      when `REAL(KIND=2)' (`DOUBLE PRECISION') data are aligned on
!      64-bit boundaries in memory.
! 
!      This option can, at least, make benchmark results more consistent
!      across various system configurations, versions of the program, and
!      data sets.
! 
!      _Note:_ The warning in the `gcc' documentation about this option
!      does not apply, generally speaking, to Fortran code compiled by
!      `g77'
! 
!      *Note Aligned Data::, for more information on alignment issues.
! 
!      _Also also note:_ The negative form of `-malign-double' is
!      `-mno-align-double', not `-benign-double'.
! 
! `-ffloat-store'
!      Might help a Fortran program that depends on exact IEEE
!      conformance on some machines, but might slow down a program that
!      doesn't.
! 
!      This option is effective when the floating-point unit is set to
!      work in IEEE 854 `extended precision'--as it typically is on x86
!      and m68k GNU systems--rather than IEEE 754 double precision.
!      `-ffloat-store' tries to remove the extra precision by spilling
!      data from floating-point registers into memory and this typically
!      involves a big performance hit.  However, it doesn't affect
!      intermediate results, so that it is only partially effective.
!      `Excess precision' is avoided in code like:
!           a = b + c
!           d = a * e
!      but not in code like:
!                 d = (b + c) * e
! 
!      For another, potentially better, way of controlling the precision,
!      see *Note Floating-point precision::.
! 
! `-fforce-mem'
! 
! `-fforce-addr'
!      Might improve optimization of loops.
! 
! `-fno-inline'
!      Don't compile statement functions inline.  Might reduce the size
!      of a program unit--which might be at expense of some speed (though
!      it should compile faster).  Note that if you are not optimizing,
!      no functions can be expanded inline.
! 
! `-ffast-math'
!      Might allow some programs designed to not be too dependent on IEEE
!      behavior for floating-point to run faster, or die trying.  Sets
!      `-funsafe-math-optimizations', `-ffinite-math-only', and
!      `-fno-trapping-math'.
! 
! `-funsafe-math-optimizations'
!      Allow optimizations that may be give incorrect results for certain
!      IEEE inputs.
! 
! `-ffinite-math-only'
!      Allow optimizations for floating-point arithmetic that assume that
!      arguments and results are not NaNs or +-Infs.
! 
!      This option should never be turned on by any `-O' option since it
!      can result in incorrect output for programs which depend on an
!      exact implementation of IEEE or ISO rules/specifications.
! 
!      The default is `-fno-finite-math-only'.
! 
! `-fno-trapping-math'
!      Allow the compiler to assume that floating-point arithmetic will
!      not generate traps on any inputs.  This is useful, for example,
!      when running a program using IEEE "non-stop" floating-point
!      arithmetic.
! 
! `-fstrength-reduce'
!      Might make some loops run faster.
! 
! `-frerun-cse-after-loop'
! 
! `-fexpensive-optimizations'
! 
! `-fdelayed-branch'
! 
! `-fschedule-insns'
! 
! `-fschedule-insns2'
! 
! `-fcaller-saves'
!      Might improve performance on some code.
! 
! `-funroll-loops'
!      Typically improves performance on code using iterative `DO' loops
!      by unrolling them and is probably generally appropriate for
!      Fortran, though it is not turned on at any optimization level.
!      Note that outer loop unrolling isn't done specifically; decisions
!      about whether to unroll a loop are made on the basis of its
!      instruction count.
! 
!      Also, no `loop discovery'(1) is done, so only loops written with
!      `DO' benefit from loop optimizations, including--but not limited
!      to--unrolling.  Loops written with `IF' and `GOTO' are not
!      currently recognized as such.  This option unrolls only iterative
!      `DO' loops, not `DO WHILE' loops.
! 
! `-funroll-all-loops'
!      Probably improves performance on code using `DO WHILE' loops by
!      unrolling them in addition to iterative `DO' loops.  In the absence
!      of `DO WHILE', this option is equivalent to `-funroll-loops' but
!      possibly slower.
! 
! `-fno-move-all-movables'
! 
! `-fno-reduce-all-givs'
! 
! `-fno-rerun-loop-opt'
!      In general, the optimizations enabled with these options will lead
!      to faster code being generated by GNU Fortran; hence they are
!      enabled by default when issuing the `g77' command.
! 
!      `-fmove-all-movables' and `-freduce-all-givs' will enable loop
!      optimization to move all loop-invariant index computations in
!      nested loops over multi-rank array dummy arguments out of these
!      loops.
! 
!      `-frerun-loop-opt' will move offset calculations resulting from
!      the fact that Fortran arrays by default have a lower bound of 1
!      out of the loops.
! 
!      These three options are intended to be removed someday, once loop
!      optimization is sufficiently advanced to perform all those
!      transformations without help from these options.
! 
!    *Note Options That Control Optimization: (gcc)Optimize Options, for
! more information on options to optimize the generated machine code.
! 
!    ---------- Footnotes ----------
! 
!    (1) "loop discovery" refers to the process by which a compiler, or
! indeed any reader of a program, determines which portions of the
! program are more likely to be executed repeatedly as it is being run.
! Such discovery typically is done early when compiling using
! optimization techniques, so the "discovered" loops get more
! attention--and more run-time resources, such as registers--from the
! compiler.  It is easy to "discover" loops that are constructed out of
! looping constructs in the language (such as Fortran's `DO').  For some
! programs, "discovering" loops constructed out of lower-level constructs
! (such as `IF' and `GOTO') can lead to generation of more optimal code
! than otherwise.
! 
! 
! File: g77.info,  Node: Preprocessor Options,  Next: Directory Options,  Prev: Optimize Options,  Up: Invoking G77
! 
! Options Controlling the Preprocessor
! ====================================
! 
!    These options control the C preprocessor, which is run on each C
! source file before actual compilation.
! 
!    *Note Options Controlling the Preprocessor: (gcc)Preprocessor
! Options, for information on C preprocessor options.
! 
!    Some of these options also affect how `g77' processes the `INCLUDE'
! directive.  Since this directive is processed even when preprocessing
! is not requested, it is not described in this section.  *Note Options
! for Directory Search: Directory Options, for information on how `g77'
! processes the `INCLUDE' directive.
! 
!    However, the `INCLUDE' directive does not apply preprocessing to the
! contents of the included file itself.
! 
!    Therefore, any file that contains preprocessor directives (such as
! `#include', `#define', and `#if') must be included via the `#include'
! directive, not via the `INCLUDE' directive.  Therefore, any file
! containing preprocessor directives, if included, is necessarily
! included by a file that itself contains preprocessor directives.
! 
! 
! File: g77.info,  Node: Directory Options,  Next: Code Gen Options,  Prev: Preprocessor Options,  Up: Invoking G77
! 
! Options for Directory Search
! ============================
! 
!    These options affect how the `cpp' preprocessor searches for files
! specified via the `#include' directive.  Therefore, when compiling
! Fortran programs, they are meaningful when the preprocessor is used.
! 
!    Some of these options also affect how `g77' searches for files
! specified via the `INCLUDE' directive, although files included by that
! directive are not, themselves, preprocessed.  These options are:
! 
! `-I-'
! 
! `-IDIR'
!      These affect interpretation of the `INCLUDE' directive (as well as
!      of the `#include' directive of the `cpp' preprocessor).
! 
!      Note that `-IDIR' must be specified _without_ any spaces between
!      `-I' and the directory name--that is, `-Ifoo/bar' is valid, but
!      `-I foo/bar' is rejected by the `g77' compiler (though the
!      preprocessor supports the latter form).  Also note that the
!      general behavior of `-I' and `INCLUDE' is pretty much the same as
!      of `-I' with `#include' in the `cpp' preprocessor, with regard to
!      looking for `header.gcc' files and other such things.
! 
!      *Note Options for Directory Search: (gcc)Directory Options, for
!      information on the `-I' option.
! 
! 
! File: g77.info,  Node: Code Gen Options,  Next: Environment Variables,  Prev: Directory Options,  Up: Invoking G77
! 
! Options for Code Generation Conventions
! =======================================
! 
!    These machine-independent options control the interface conventions
! used in code generation.
! 
!    Most of them have both positive and negative forms; the negative form
! of `-ffoo' would be `-fno-foo'.  In the table below, only one of the
! forms is listed--the one which is not the default.  You can figure out
! the other form by either removing `no-' or adding it.
! 
! `-fno-automatic'
!      Treat each program unit as if the `SAVE' statement was specified
!      for every local variable and array referenced in it.  Does not
!      affect common blocks.  (Some Fortran compilers provide this option
!      under the name `-static'.)
! 
! `-finit-local-zero'
!      Specify that variables and arrays that are local to a program unit
!      (not in a common block and not passed as an argument) are to be
!      initialized to binary zeros.
! 
!      Since there is a run-time penalty for initialization of variables
!      that are not given the `SAVE' attribute, it might be a good idea
!      to also use `-fno-automatic' with `-finit-local-zero'.
! 
! `-fno-f2c'
!      Do not generate code designed to be compatible with code generated
!      by `f2c' use the GNU calling conventions instead.
! 
!      The `f2c' calling conventions require functions that return type
!      `REAL(KIND=1)' to actually return the C type `double', and
!      functions that return type `COMPLEX' to return the values via an
!      extra argument in the calling sequence that points to where to
!      store the return value.  Under the GNU calling conventions, such
!      functions simply return their results as they would in GNU
!      C--`REAL(KIND=1)' functions return the C type `float', and
!      `COMPLEX' functions return the GNU C type `complex' (or its
!      `struct' equivalent).
! 
!      This does not affect the generation of code that interfaces with
!      the `libg2c' library.
! 
!      However, because the `libg2c' library uses `f2c' calling
!      conventions, `g77' rejects attempts to pass intrinsics implemented
!      by routines in this library as actual arguments when `-fno-f2c' is
!      used, to avoid bugs when they are actually called by code
!      expecting the GNU calling conventions to work.
! 
!      For example, `INTRINSIC ABS;CALL FOO(ABS)' is rejected when
!      `-fno-f2c' is in force.  (Future versions of the `g77' run-time
!      library might offer routines that provide GNU-callable versions of
!      the routines that implement the `f2c' intrinsics that may be
!      passed as actual arguments, so that valid programs need not be
!      rejected when `-fno-f2c' is used.)
! 
!      *Caution:* If `-fno-f2c' is used when compiling any source file
!      used in a program, it must be used when compiling _all_ Fortran
!      source files used in that program.
! 
! `-ff2c-library'
!      Specify that use of `libg2c' (or the original `libf2c') is
!      required.  This is the default for the current version of `g77'
! 
!      Currently it is not valid to specify `-fno-f2c-library'.  This
!      option is provided so users can specify it in shell scripts that
!      build programs and libraries that require the `libf2c' library,
!      even when being compiled by future versions of `g77' that might
!      otherwise default to generating code for an incompatible library.
! 
! `-fno-underscoring'
!      Do not transform names of entities specified in the Fortran source
!      file by appending underscores to them.
! 
!      With `-funderscoring' in effect, `g77' appends two underscores to
!      names with underscores and one underscore to external names with
!      no underscores.  (`g77' also appends two underscores to internal
!      names with underscores to avoid naming collisions with external
!      names.  The `-fno-second-underscore' option disables appending of
!      the second underscore in all cases.)
! 
!      This is done to ensure compatibility with code produced by many
!      UNIX Fortran compilers, including `f2c' which perform the same
!      transformations.
! 
!      Use of `-fno-underscoring' is not recommended unless you are
!      experimenting with issues such as integration of (GNU) Fortran into
!      existing system environments (vis-a-vis existing libraries, tools,
!      and so on).
! 
!      For example, with `-funderscoring', and assuming other defaults
!      like `-fcase-lower' and that `j()' and `max_count()' are external
!      functions while `my_var' and `lvar' are local variables, a
!      statement like
! 
!           I = J() + MAX_COUNT (MY_VAR, LVAR)
! 
!      is implemented as something akin to:
! 
!           i = j_() + max_count__(&my_var__, &lvar);
! 
!      With `-fno-underscoring', the same statement is implemented as:
! 
!           i = j() + max_count(&my_var, &lvar);
! 
!      Use of `-fno-underscoring' allows direct specification of
!      user-defined names while debugging and when interfacing `g77' code
!      with other languages.
! 
!      Note that just because the names match does _not_ mean that the
!      interface implemented by `g77' for an external name matches the
!      interface implemented by some other language for that same name.
!      That is, getting code produced by `g77' to link to code produced
!      by some other compiler using this or any other method can be only a
!      small part of the overall solution--getting the code generated by
!      both compilers to agree on issues other than naming can require
!      significant effort, and, unlike naming disagreements, linkers
!      normally cannot detect disagreements in these other areas.
! 
!      Also, note that with `-fno-underscoring', the lack of appended
!      underscores introduces the very real possibility that a
!      user-defined external name will conflict with a name in a system
!      library, which could make finding unresolved-reference bugs quite
!      difficult in some cases--they might occur at program run time, and
!      show up only as buggy behavior at run time.
! 
!      In future versions of `g77' we hope to improve naming and linking
!      issues so that debugging always involves using the names as they
!      appear in the source, even if the names as seen by the linker are
!      mangled to prevent accidental linking between procedures with
!      incompatible interfaces.
! 
! `-fno-second-underscore'
!      Do not append a second underscore to names of entities specified
!      in the Fortran source file.
! 
!      This option has no effect if `-fno-underscoring' is in effect.
! 
!      Otherwise, with this option, an external name such as `MAX_COUNT'
!      is implemented as a reference to the link-time external symbol
!      `max_count_', instead of `max_count__'.
! 
! `-fno-ident'
!      Ignore the `#ident' directive.
! 
! `-fzeros'
!      Treat initial values of zero as if they were any other value.
! 
!      As of version 0.5.18, `g77' normally treats `DATA' and other
!      statements that are used to specify initial values of zero for
!      variables and arrays as if no values were actually specified, in
!      the sense that no diagnostics regarding multiple initializations
!      are produced.
! 
!      This is done to speed up compiling of programs that initialize
!      large arrays to zeros.
! 
!      Use `-fzeros' to revert to the simpler, slower behavior that can
!      catch multiple initializations by keeping track of all
!      initializations, zero or otherwise.
! 
!      _Caution:_ Future versions of `g77' might disregard this option
!      (and its negative form, the default) or interpret it somewhat
!      differently.  The interpretation changes will affect only
!      non-standard programs; standard-conforming programs should not be
!      affected.
! 
! `-femulate-complex'
!      Implement `COMPLEX' arithmetic via emulation, instead of using the
!      facilities of the `gcc' back end that provide direct support of
!      `complex' arithmetic.
! 
!      (`gcc' had some bugs in its back-end support for `complex'
!      arithmetic, due primarily to the support not being completed as of
!      version 2.8.1 and `egcs' 1.1.2.)
! 
!      Use `-femulate-complex' if you suspect code-generation bugs, or
!      experience compiler crashes, that might result from `g77' using
!      the `COMPLEX' support in the `gcc' back end.  If using that option
!      fixes the bugs or crashes you are seeing, that indicates a likely
!      `g77' bugs (though, all compiler crashes are considered bugs), so,
!      please report it.  (Note that the known bugs, now believed fixed,
!      produced compiler crashes rather than causing the generation of
!      incorrect code.)
! 
!      Use of this option should not affect how Fortran code compiled by
!      `g77' works in terms of its interfaces to other code, e.g. that
!      compiled by `f2c'
! 
!      As of GCC version 3.0, this option is not necessary anymore.
! 
!      _Caution:_ Future versions of `g77' might ignore both forms of
!      this option.
! 
! `-falias-check'
! 
! `-fargument-alias'
! 
! `-fargument-noalias'
! 
! `-fno-argument-noalias-global'
!      _Version info:_ These options are not supported by versions of
!      `g77' based on `gcc' version 2.8.
! 
!      These options specify to what degree aliasing (overlap) is
!      permitted between arguments (passed as pointers) and `COMMON'
!      (external, or public) storage.
! 
!      The default for Fortran code, as mandated by the FORTRAN 77 and
!      Fortran 90 standards, is `-fargument-noalias-global'.  The default
!      for code written in the C language family is `-fargument-alias'.
! 
!      Note that, on some systems, compiling with `-fforce-addr' in
!      effect can produce more optimal code when the default aliasing
!      options are in effect (and when optimization is enabled).
! 
!      *Note Aliasing Assumed To Work::, for detailed information on the
!      implications of compiling Fortran code that depends on the ability
!      to alias dummy arguments.
! 
! `-fno-globals'
!      Disable diagnostics about inter-procedural analysis problems, such
!      as disagreements about the type of a function or a procedure's
!      argument, that might cause a compiler crash when attempting to
!      inline a reference to a procedure within a program unit.  (The
!      diagnostics themselves are still produced, but as warnings, unless
!      `-Wno-globals' is specified, in which case no relevant diagnostics
!      are produced.)
! 
!      Further, this option disables such inlining, to avoid compiler
!      crashes resulting from incorrect code that would otherwise be
!      diagnosed.
! 
!      As such, this option might be quite useful when compiling
!      existing, "working" code that happens to have a few bugs that do
!      not generally show themselves, but which `g77' diagnoses.
! 
!      Use of this option therefore has the effect of instructing `g77'
!      to behave more like it did up through version 0.5.19.1, when it
!      paid little or no attention to disagreements between program units
!      about a procedure's type and argument information, and when it
!      performed no inlining of procedures (except statement functions).
! 
!      Without this option, `g77' defaults to performing the potentially
!      inlining procedures as it started doing in version 0.5.20, but as
!      of version 0.5.21, it also diagnoses disagreements that might
!      cause such inlining to crash the compiler as (fatal) errors, and
!      warns about similar disagreements that are currently believed to
!      not likely to result in the compiler later crashing or producing
!      incorrect code.
! 
! `-fflatten-arrays'
!      Use back end's C-like constructs (pointer plus offset) instead of
!      its `ARRAY_REF' construct to handle all array references.
! 
!      _Note:_ This option is not supported.  It is intended for use only
!      by `g77' developers, to evaluate code-generation issues.  It might
!      be removed at any time.
! 
! `-fbounds-check'
! `-ffortran-bounds-check'
!      Enable generation of run-time checks for array subscripts and
!      substring start and end points against the (locally) declared
!      minimum and maximum values.
! 
!      The current implementation uses the `libf2c' library routine
!      `s_rnge' to print the diagnostic.
! 
!      However, whereas `f2c' generates a single check per reference for
!      a multi-dimensional array, of the computed offset against the
!      valid offset range (0 through the size of the array), `g77'
!      generates a single check per _subscript_ expression.  This catches
!      some cases of potential bugs that `f2c' does not, such as
!      references to below the beginning of an assumed-size array.
! 
!      `g77' also generates checks for `CHARACTER' substring references,
!      something `f2c' currently does not do.
! 
!      Use the new `-ffortran-bounds-check' option to specify
!      bounds-checking for only the Fortran code you are compiling, not
!      necessarily for code written in other languages.
! 
!      _Note:_ To provide more detailed information on the offending
!      subscript, `g77' provides the `libg2c' run-time library routine
!      `s_rnge' with somewhat differently-formatted information.  Here's
!      a sample diagnostic:
! 
!           Subscript out of range on file line 4, procedure rnge.f/bf.
!           Attempt to access the -6-th element of variable b[subscript-2-of-2].
!           Aborted
! 
!      The above message indicates that the offending source line is line
!      4 of the file `rnge.f', within the program unit (or statement
!      function) named `bf'.  The offended array is named `b'.  The
!      offended array dimension is the second for a two-dimensional array,
!      and the offending, computed subscript expression was `-6'.
! 
!      For a `CHARACTER' substring reference, the second line has this
!      appearance:
! 
!           Attempt to access the 11-th element of variable a[start-substring].
! 
!      This indicates that the offended `CHARACTER' variable or array is
!      named `a', the offended substring position is the starting
!      (leftmost) position, and the offending substring expression is
!      `11'.
! 
!      (Though the verbage of `s_rnge' is not ideal for the purpose of
!      the `g77' compiler, the above information should provide adequate
!      diagnostic abilities to it users.)
! 
!    *Note Options for Code Generation Conventions: (gcc)Code Gen
! Options, for information on more options offered by the GBE shared by
! `g77' `gcc' and other GNU compilers.
! 
!    Some of these do _not_ work when compiling programs written in
! Fortran:
! 
! `-fpcc-struct-return'
! 
! `-freg-struct-return'
!      You should not use these except strictly the same way as you used
!      them to build the version of `libg2c' with which you will be
!      linking all code compiled by `g77' with the same option.
! 
! `-fshort-double'
!      This probably either has no effect on Fortran programs, or makes
!      them act loopy.
! 
! `-fno-common'
!      Do not use this when compiling Fortran programs, or there will be
!      Trouble.
! 
! `-fpack-struct'
!      This probably will break any calls to the `libg2c' library, at the
!      very least, even if it is built with the same option.
! 
! 
! File: g77.info,  Node: Environment Variables,  Prev: Code Gen Options,  Up: Invoking G77
! 
! Environment Variables Affecting GNU Fortran
! ===========================================
! 
!    GNU Fortran currently does not make use of any environment variables
! to control its operation above and beyond those that affect the
! operation of `gcc'.
! 
!    *Note Environment Variables Affecting GCC: (gcc)Environment
! Variables, for information on environment variables.
! 
! 
! File: g77.info,  Node: News,  Next: Changes,  Prev: Invoking G77,  Up: Top
! 
! News About GNU Fortran
! **********************
! 
!    Changes made to recent versions of GNU Fortran are listed below,
! with the most recent version first.
! 
!    The changes are generally listed in order:
! 
!   1. Code-generation and run-time-library bug-fixes
! 
!   2. Compiler and run-time-library crashes involving valid code that
!      have been fixed
! 
!   3. New features
! 
!   4. Fixes and enhancements to existing features
! 
!   5. New diagnostics
! 
!   6. Internal improvements
! 
!   7. Miscellany
! 
!    This order is not strict--for example, some items involve a
! combination of these elements.
! 
!    Note that two variants of `g77' are tracked below.  The `egcs'
! variant is described vis-a-vis previous versions of `egcs' and/or an
! official FSF version, as appropriate.  Note that all such variants are
! obsolete _as of July 1999_ - the information is retained here only for
! its historical value.
! 
!    Therefore, `egcs' versions sometimes have multiple listings to help
! clarify how they differ from other versions, though this can make
! getting a complete picture of what a particular `egcs' version contains
! somewhat more difficult.
! 
!    For information on bugs in the GCC-3.3 version of `g77', see *Note
! Known Bugs In GNU Fortran: Known Bugs.
! 
!    An online, "live" version of this document (derived directly from
! the mainline, development version of `g77' within `gcc') is available at
! `http://gcc.gnu.org/onlinedocs/g77/News.html'.
! 
!    The following information was last updated on 2003-04-11:
! 
! In `GCC' 3.3 versus `GCC' 3.2:
! ==============================
! 
!    * Problem Reports fixed (in chronological order of submission):
!     `1832'
!           -list directed i/o overflow hangs, -fbounds-check doesn't
!           detect
! 
!     `3924'
!           g77 generates code which is rejected by GAS if COFF debugging
!           info is requested
! 
!     `6286'
!           Broken links on web pages
! 
!     `6367'
!           (libf2c) multiple repeat counts confuse namelist read into
!           array
! 
!     `6491'
!           Logical operations error on logicals when using -fugly-logint
! 
!     `6742'
!           Generation of C++ Prototype for FORTRAN and extern "C"
! 
!     `7113'
!           Failure of g77.f-torture/execute/f90-intrinsic-bit.f -Os on
!           irix6.5
! 
!     `7236'
!           (libf2c) OPEN(...,RECL=nnn,...) without ACCESS='DIRECT'
!           should assume a direct access file
! 
!     `7278'
!           g77 "bug"; the executable misbehave (use of options -O2
!           -fno-automatic gave wrong results)
! 
!     `7384'
!           (libf2c) DATE_AND_TIME milliseconds field inactive on Windows
! 
!     `7388'
!           Incorrect output with 0-based array of characters
! 
!     `8587'
!           Double complex zero ** double precision number -> NaN instead
!           of zero
! 
!     `9038'
!           -ffixed-line-length-none -x f77-cpp-input gives: Warning:
!           unknown register name line-length-none
! 
!     `9263'
!           ICE caused by invalid PARAMETER in implied DO loop
! 
!     `10197'
!           Direct access files not unformatted by default
! 
!    * Richard Henderson (<rth@redhat.com>) analyzed and improved the
!      handling of (no-)aliasing information for dummy arguments and
!      improved the optimization of induction variables in unrolled loops.
! 
! In `GCC' 3.2 versus `GCC' 3.1:
! ==============================
! 
!    * Problem Reports fixed (in chronological order of submission):
!     `7681'
!           ICE in compensate_edge, at reg-stack.c:2591
! 
!     `8308'
!           gcc-3.x does not compile files with suffix .r (RATFOR) [Fixed
!           in 3.2.1]
! 
!     `9258'
!           [3.2/3.3/3.4 regression] ICE in compensate_edge, at
!           reg-stack.c:2589
! 
! In `GCC' 3.1 (formerly known as g77-0.5.27) versus `GCC' 3.0:
! =============================================================
! 
!    * Problem Reports fixed (in chronological order of submission):
!     `947'
!           Data statement initialization with subscript of kind INTEGER*2
! 
!     `3743'
!           Reference to intrinsic `ISHFT' invalid
! 
!     `3807'
!           Function BESJN(integer,double) problems
! 
!     `3957'
!           g77 -pipe -xf77-cpp-input sends output to stdout
! 
!     `4279'
!           g77 -h" gives bogus output
! 
!     `4730'
!           ICE on valid input using CALL EXIT(%VAL(...))
! 
!     `4752'
!           g77 -v -c -xf77-version /dev/null -xnone causes ice
! 
!     `4885'
!           BACKSPACE example that doesn't work as of gcc/g77-3.0.x
! 
!     `5122'
!           g77 rejects accepted use of INTEGER*2 as type of DATA
!           statement loop index
! 
!     `5397'
!           ICE on compiling source with 540 000 000 REAL array
! 
!     `5473'
!           ICE on BESJN(integer*8,real)
! 
!     `5837'
!           bug in loop unrolling
! 
!     `6106'
!           sparc-sun-solaris2.7 gcc-3.1 extra g77 testsuite failures
!           w/-m64
! 
!     `6138'
!           Incorrect acces of integer*1 variables on PA
! 
!     `6304'
!           Failure of LAPACK test dtest on irix6.5 with -mabi=64 -O2
! 
!    * `g77' now has its man page generated from the texinfo
!      documentation, to guarantee that it remains up to date.
! 
!    * `g77' used to reject the following program on 32-bit targets:
!           PROGRAM PROG
!           DIMENSION A(140 000 000)
!           END
!      with the message:
!           prog.f: In program `prog':
!           prog.f:2:
!                    DIMENSION A(140 000 000)
!                              ^
!           Array `a' at (^) is too large to handle
!      because 140 000 000 REALs is larger than the largest bit-extent
!      that can be expressed in 32 bits.  However, bit-sizes never play a
!      role after offsets have been converted to byte addresses.
!      Therefore this check has been removed, and the limit is now 2
!      Gbyte of memory (around 530 000 000 REALs).  Note: On GNU/Linux
!      systems one has to compile and link programs that occupy more than
!      1 Gbyte statically, i.e. `g77 -static ...'.
! 
!    * Based on work done by Juergen Pfeifer (<juergen.pfeifer@gmx.net>)
!      libf2c is now a shared library.  One can still link in all objects
!      with the program by specifying the `-static' option.
! 
!    * Robert Anderson (<rwa@alumni.princeton.edu>) thought up a two line
!      change that enables g77 to compile such code as:
!           SUBROUTINE SUB(A, N)
!           DIMENSION N(2)
!           DIMENSION A(N(1),N(2))
!           A(1,1) = 1.
!           END
!      Note the use of array elements in the bounds of the adjustable
!      array A.
! 
!    * George Helffrich (<george@geo.titech.ac.jp>) implemented a change
!      in substring index checking (when specifying `-fbounds-check')
!      that permits the use of zero length substrings of the form
!      `string(1:0)'.
! 
!    * Based on code developed by Pedro Vazquez
!      (<vazquez@penelope.iqm.unicamp.br>), the `libf2c' library is now
!      able to read and write files larger than 2 Gbyte on 32-bit target
!      machines, if the operating system supports this.
! 
! In 0.5.26, `GCC' 3.0 versus `GCC' 2.95:
! =======================================
! 
!    * When a REWIND was issued after a WRITE statement on an unformatted
!      file, the implicit truncation was performed by copying the
!      truncated file to /tmp and copying the result back.  This has been
!      fixed by using the `ftruncate' OS function.  Thanks go to the
!      GAMESS developers for bringing this to our attention.
! 
!    * Using options `-g', `-ggdb' or `-gdwarf[-2]' (where appropriate
!      for your target) now also enables debugging information for COMMON
!      BLOCK and EQUIVALENCE items to be emitted.  Thanks go to Andrew
!      Vaught (<andy@xena.eas.asu.edu>) and George Helffrich
!      (<george@geology.bristol.ac.uk>) for fixing this longstanding
!      problem.
! 
!    * It is not necessary anymore to use the option `-femulate-complex'
!      to compile Fortran code using COMPLEX arithmetic, even on 64-bit
!      machines (like the Alpha).  This will improve code generation.
! 
!    * INTRINSIC arithmetic functions are now treated as routines that do
!      not depend on anything but their argument(s).  This enables
!      further instruction scheduling, because it is known that they
!      cannot read or modify arbitrary locations.
! 
!    * Upgrade to `libf2c' as of 2000-12-05.
! 
!      This fixes a bug where a namelist containing initialization of
!      LOGICAL items and a variable starting with T or F would be read
!      incorrectly.
! 
!    * The `TtyNam' intrinsics now set NAME to all spaces (at run time)
!      if the system has no `ttyname' implementation available.
! 
!    * Upgrade to `libf2c' as of 1999-06-28.
! 
!      This fixes a bug whereby input to a `NAMELIST' read involving a
!      repeat count, such as `K(5)=10*3', was not properly handled by
!      `libf2c'.  The first item was written to `K(5)', but the remaining
!      nine were written elsewhere (still within the array), not
!      necessarily starting at `K(6)'.
! 
! In 0.5.25, `GCC' 2.95 (`EGCS' 1.2) versus `EGCS' 1.1.2:
! =======================================================
! 
!    * `g77' no longer generates bad code for assignments, or other
!      conversions, of `REAL' or `COMPLEX' constant expressions to type
!      `INTEGER(KIND=2)' (often referred to as `INTEGER*8').
! 
!      For example, `INTEGER*8 J; J = 4E10' now works as documented.
! 
!    * `g77' no longer truncates `INTEGER(KIND=2)' (usually `INTEGER*8')
!      subscript expressions when evaluating array references on systems
!      with pointers widers than `INTEGER(KIND=1)' (such as Alphas).
! 
!    * `g77' no longer generates bad code for an assignment to a
!      `COMPLEX' variable or array that partially overlaps one or more of
!      the sources of the same assignment (a very rare construction).  It
!      now assigns through a temporary, in cases where such partial
!      overlap is deemed possible.
! 
!    * `libg2c' (`libf2c') no longer loses track of the file being worked
!      on during a `BACKSPACE' operation.
! 
!    * `libg2c' (`libf2c') fixes a bug whereby input to a `NAMELIST' read
!      involving a repeat count, such as `K(5)=10*3', was not properly
!      handled by `libf2c'.  The first item was written to `K(5)', but
!      the remaining nine were written elsewhere (still within the array),
!      not necessarily starting at `K(6)'.
! 
!    * Automatic arrays now seem to be working on HP-UX systems.
! 
!    * The `Date' intrinsic now returns the correct result on big-endian
!      systems.
! 
!    * Fix `g77' so it no longer crashes when compiling I/O statements
!      using keywords that define `INTEGER' values, such as `IOSTAT=J',
!      where J is other than default `INTEGER' (such as `INTEGER*2').
!      Instead, it issues a diagnostic.
! 
!    * Fix `g77' so it properly handles `DATA A/RPT*VAL/', where RPT is
!      not default `INTEGER', such as `INTEGER*2', instead of producing a
!      spurious diagnostic.  Also fix `DATA (A(I),I=1,N)', where `N' is
!      not default `INTEGER' to work instead of crashing `g77'.
! 
!    * The `-ax' option is now obeyed when compiling Fortran programs.
!      (It is passed to the `f771' driver.)
! 
!    * The new `-fbounds-check' option causes `g77' to compile run-time
!      bounds checks of array subscripts, as well as of substring start
!      and end points.
! 
!    * `libg2c' now supports building as multilibbed library, which
!      provides better support for systems that require options such as
!      `-mieee' to work properly.
! 
!    * Source file names with the suffixes `.FOR' and `.FPP' now are
!      recognized by `g77' as if they ended in `.for' and `.fpp',
!      respectively.
! 
!    * The order of arguments to the _subroutine_ forms of the `CTime',
!      `DTime', `ETime', and `TtyNam' intrinsics has been swapped.  The
!      argument serving as the returned value for the corresponding
!      function forms now is the _second_ argument, making these
!      consistent with the other subroutine forms of `libU77' intrinsics.
! 
!    * `g77' now warns about a reference to an intrinsic that has an
!      interface that is not Year 2000 (Y2K) compliant.  Also, `libg2c'
!      has been changed to increase the likelihood of catching references
!      to the implementations of these intrinsics using the `EXTERNAL'
!      mechanism (which would avoid the new warnings).
! 
!      *Note Year 2000 (Y2K) Problems::, for more information.
! 
!    * `g77' now warns about a reference to a function when the
!      corresponding _subsequent_ function program unit disagrees with
!      the reference concerning the type of the function.
! 
!    * `-fno-emulate-complex' is now the default option.  This should
!      result in improved performance of code that uses the `COMPLEX'
!      data type.
! 
!    * The `-malign-double' option now reliably aligns _all_
!      double-precision variables and arrays on Intel x86 targets.
! 
!    * Even without the `-malign-double' option, `g77' reliably aligns
!      local double-precision variables that are not in `EQUIVALENCE'
!      areas and not `SAVE''d.
! 
!    * `g77' now open-codes ("inlines") division of `COMPLEX' operands
!      instead of generating a run-time call to the `libf2c' routines
!      `c_div' or `z_div', unless the `-Os' option is specified.
! 
!    * `g77' no longer generates code to maintain `errno', a C-language
!      concept, when performing operations such as the `SqRt' intrinsic.
! 
!    * `g77' developers can temporarily use the `-fflatten-arrays' option
!      to compare how the compiler handles code generation using C-like
!      constructs as compared to the Fortran-like method constructs
!      normally used.
! 
!    * A substantial portion of the `g77' front end's code-generation
!      component was rewritten.  It now generates code using facilities
!      more robustly supported by the `gcc' back end.  One effect of this
!      rewrite is that some codes no longer produce a spurious "label LAB
!      used before containing binding contour" message.
! 
!    * Support for the `-fugly' option has been removed.
! 
!    * Improve documentation and indexing, including information on Year
!      2000 (Y2K) compliance, and providing more information on internals
!      of the front end.
! 
!    * Upgrade to `libf2c' as of 1999-05-10.
! 
! In 0.5.24 versus 0.5.23:
! ========================
! 
!    There is no `g77' version 0.5.24 at this time, or planned.  0.5.24
! is the version number designated for bug fixes and, perhaps, some new
! features added, to 0.5.23.  Version 0.5.23 requires `gcc' 2.8.1, as
! 0.5.24 was planned to require.
! 
!    Due to `EGCS' becoming `GCC' (which is now an acronym for "GNU
! Compiler Collection"), and `EGCS' 1.2 becoming officially designated
! `GCC' 2.95, there seems to be no need for an actual 0.5.24 release.
! 
!    To reduce the confusion already resulting from use of 0.5.24 to
! designate `g77' versions within `EGCS' versions 1.0 and 1.1, as well as
! in versions of `g77' documentation and notices during that period,
! "mainline" `g77' version numbering resumes at 0.5.25 with `GCC' 2.95
! (`EGCS' 1.2), skipping over 0.5.24 as a placeholder version number.
! 
!    To repeat, there is no `g77' 0.5.24, but there is now a 0.5.25.
! Please remain calm and return to your keypunch units.
! 
! In `EGCS' 1.1.2 versus `EGCS' 1.1.1:
! ====================================
! 
!    * Fix the `IDate' intrinsic (VXT) (in `libg2c') so the returned year
!      is in the documented, non-Y2K-compliant range of 0-99, instead of
!      being returned as 100 in the year 2000.
! 
!      *Note IDate Intrinsic (VXT)::, for more information.
! 
!    * Fix the `Date_and_Time' intrinsic (in `libg2c') to return the
!      milliseconds value properly in VALUES(8).
! 
!    * Fix the `LStat' intrinsic (in `libg2c') to return device-ID
!      information properly in SARRAY(7).
! 
!    * Improve documentation.
! 
! In `EGCS' 1.1.1 versus `EGCS' 1.1:
! ==================================
! 
!    * Fix `libg2c' so it performs an implicit `ENDFILE' operation (as
!      appropriate) whenever a `REWIND' is done.
! 
!      (This bug was introduced in 0.5.23 and `egcs' 1.1 in `g77''s
!      version of `libf2c'.)
! 
!    * Fix `libg2c' so it no longer crashes with a spurious diagnostic
!      upon doing any I/O following a direct formatted write.
! 
!      (This bug was introduced in 0.5.23 and `egcs' 1.1 in `g77''s
!      version of `libf2c'.)
! 
!    * Fix `g77' so it no longer crashes compiling references to the
!      `Rand' intrinsic on some systems.
! 
!    * Fix `g77' portion of installation process so it works better on
!      some systems (those with shells requiring `else true' clauses on
!      `if' constructs for the completion code to be set properly).
! 
! In `EGCS' 1.1 versus `EGCS' 1.0.3:
! ==================================
! 
!    * Fix bugs in the `libU77' intrinsic `HostNm' that wrote one byte
!      beyond the end of its `CHARACTER' argument, and in the `libU77'
!      intrinsics `GMTime' and `LTime' that overwrote their arguments.
! 
!    * Assumed arrays with negative bounds (such as `REAL A(-1:*)') no
!      longer elicit spurious diagnostics from `g77', even on systems
!      with pointers having different sizes than integers.
! 
!      This bug is not known to have existed in any recent version of
!      `gcc'.  It was introduced in an early release of `egcs'.
! 
!    * Valid combinations of `EXTERNAL', passing that external as a dummy
!      argument without explicitly giving it a type, and, in a subsequent
!      program unit, referencing that external as an external function
!      with a different type no longer crash `g77'.
! 
!    * `CASE DEFAULT' no longer crashes `g77'.
! 
!    * The `-Wunused' option no longer issues a spurious warning about
!      the "master" procedure generated by `g77' for procedures
!      containing `ENTRY' statements.
! 
!    * Support `FORMAT(I<EXPR>)' when EXPR is a compile-time constant
!      `INTEGER' expression.
! 
!    * Fix `g77' `-g' option so procedures that use `ENTRY' can be
!      stepped through, line by line, in `gdb'.
! 
!    * Allow any `REAL' argument to intrinsics `Second' and `CPU_Time'.
! 
!    * Use `tempnam', if available, to open scratch files (as in
!      `OPEN(STATUS='SCRATCH')') so that the `TMPDIR' environment
!      variable, if present, is used.
! 
!    * `g77''s version of `libf2c' separates out the setting of global
!      state (such as command-line arguments and signal handling) from
!      `main.o' into distinct, new library archive members.
! 
!      This should make it easier to write portable applications that
!      have their own (non-Fortran) `main()' routine properly set up the
!      `libf2c' environment, even when `libf2c' (now `libg2c') is a
!      shared library.
! 
!    * `g77' no longer installs the `f77' command and `f77.1' man page in
!      the `/usr' or `/usr/local' hierarchy, even if the `f77-install-ok'
!      file exists in the source or build directory.  See the
!      installation documentation for more information.
! 
!    * `g77' no longer installs the `libf2c.a' library and `f2c.h'
!      include file in the `/usr' or `/usr/local' hierarchy, even if the
!      `f2c-install-ok' or `f2c-exists-ok' files exist in the source or
!      build directory.  See the installation documentation for more
!      information.
! 
!    * The `libf2c.a' library produced by `g77' has been renamed to
!      `libg2c.a'.  It is installed only in the `gcc' "private" directory
!      hierarchy, `gcc-lib'.  This allows system administrators and users
!      to choose which version of the `libf2c' library from `netlib' they
!      wish to use on a case-by-case basis.  See the installation
!      documentation for more information.
! 
!    * The `f2c.h' include (header) file produced by `g77' has been
!      renamed to `g2c.h'.  It is installed only in the `gcc' "private"
!      directory hierarchy, `gcc-lib'.  This allows system administrators
!      and users to choose which version of the include file from
!      `netlib' they wish to use on a case-by-case basis.  See the
!      installation documentation for more information.
! 
!    * The `g77' command now expects the run-time library to be named
!      `libg2c.a' instead of `libf2c.a', to ensure that a version other
!      than the one built and installed as part of the same `g77' version
!      is picked up.
! 
!    * During the configuration and build process, `g77' creates
!      subdirectories it needs only as it needs them.  Other cleaning up
!      of the configuration and build process has been performed as well.
! 
!    * `install-info' now used to update the directory of Info
!      documentation to contain an entry for `g77' (during installation).
! 
!    * Some diagnostics have been changed from warnings to errors, to
!      prevent inadvertent use of the resulting, probably buggy, programs.
!      These mostly include diagnostics about use of unsupported features
!      in the `OPEN', `INQUIRE', `READ', and `WRITE' statements, and
!      about truncations of various sorts of constants.
! 
!    * Improve compilation of `FORMAT' expressions so that a null byte is
!      appended to the last operand if it is a constant.  This provides a
!      cleaner run-time diagnostic as provided by `libf2c' for statements
!      like `PRINT '(I1', 42'.
! 
!    * Improve documentation and indexing.
! 
!    * The upgrade to `libf2c' as of 1998-06-18 should fix a variety of
!      problems, including those involving some uses of the `T' format
!      specifier, and perhaps some build (porting) problems as well.
! 
! In `EGCS' 1.1 versus `g77' 0.5.23:
! ==================================
! 
!    * Fix a code-generation bug that afflicted Intel x86 targets when
!      `-O2' was specified compiling, for example, an old version of the
!      `DNRM2' routine.
! 
!      The x87 coprocessor stack was being mismanaged in cases involving
!      assigned `GOTO' and `ASSIGN'.
! 
!    * `g77' no longer produces incorrect code and initial values for
!      `EQUIVALENCE' and `COMMON' aggregates that, due to "unnatural"
!      ordering of members vis-a-vis their types, require initial padding.
! 
!    * Fix `g77' crash compiling code containing the construct
!      `CMPLX(0.)' or similar.
! 
!    * `g77' no longer crashes when compiling code containing
!      specification statements such as `INTEGER(KIND=7) PTR'.
! 
!    * `g77' no longer crashes when compiling code such as `J = SIGNAL(1,
!      2)'.
! 
!    * `g77' now treats `%LOC(EXPR)' and `LOC(EXPR)' as "ordinary"
!      expressions when they are used as arguments in procedure calls.
!      This change applies only to global (filewide) analysis, making it
!      consistent with how `g77' actually generates code for these cases.
! 
!      Previously, `g77' treated these expressions as denoting special
!      "pointer" arguments for the purposes of filewide analysis.
! 
!    * Fix `g77' crash (or apparently infinite run-time) when compiling
!      certain complicated expressions involving `COMPLEX' arithmetic
!      (especially multiplication).
! 
!    * Align static double-precision variables and arrays on Intel x86
!      targets regardless of whether `-malign-double' is specified.
! 
!      Generally, this affects only local variables and arrays having the
!      `SAVE' attribute or given initial values via `DATA'.
! 
!    * The `g77' driver now ensures that `-lg2c' is specified in the link
!      phase prior to any occurrence of `-lm'.  This prevents
!      accidentally linking to a routine in the SunOS4 `-lm' library when
!      the generated code wants to link to the one in `libf2c' (`libg2c').
! 
!    * `g77' emits more debugging information when `-g' is used.
! 
!      This new information allows, for example, `which __g77_length_a'
!      to be used in `gdb' to determine the type of the phantom length
!      argument supplied with `CHARACTER' variables.
! 
!      This information pertains to internally-generated type, variable,
!      and other information, not to the longstanding deficiencies
!      vis-a-vis `COMMON' and `EQUIVALENCE'.
! 
!    * The F90 `Date_and_Time' intrinsic now is supported.
! 
!    * The F90 `System_Clock' intrinsic allows the optional arguments
!      (except for the `Count' argument) to be omitted.
! 
!    * Upgrade to `libf2c' as of 1998-06-18.
! 
!    * Improve documentation and indexing.
! 
! In 0.5.23 versus 0.5.22:
! ========================
! 
!    * This release contains several regressions against version 0.5.22
!      of `g77', due to using the "vanilla" `gcc' back end instead of
!      patching it to fix a few bugs and improve performance in a few
!      cases.
! 
!      Features that have been dropped from this version of `g77' due to
!      their being implemented via `g77'-specific patches to the `gcc'
!      back end in previous releases include:
! 
!         - Support for `__restrict__' keyword, the options
!           `-fargument-alias', `-fargument-noalias', and
!           `-fargument-noalias-global', and the corresponding
!           alias-analysis code.
! 
!           (`egcs' has the alias-analysis code, but not the
!           `__restrict__' keyword.  `egcs' `g77' users benefit from the
!           alias-analysis code despite the lack of the `__restrict__'
!           keyword, which is a C-language construct.)
! 
!         - Support for the GNU compiler options `-fmove-all-movables',
!           `-freduce-all-givs', and `-frerun-loop-opt'.
! 
!           (`egcs' supports these options.  `g77' users of `egcs'
!           benefit from them even if they are not explicitly specified,
!           because the defaults are optimized for `g77' users.)
! 
!         - Support for the `-W' option warning about integer division by
!           zero.
! 
!         - The Intel x86-specific option `-malign-double' applying to
!           stack-allocated data as well as statically-allocate data.
! 
!      Note that the `gcc/f/gbe/' subdirectory has been removed from this
!      distribution as a result of `g77' no longer including patches for
!      the `gcc' back end.
! 
!    * Fix bugs in the `libU77' intrinsic `HostNm' that wrote one byte
!      beyond the end of its `CHARACTER' argument, and in the `libU77'
!      intrinsics `GMTime' and `LTime' that overwrote their arguments.
! 
!    * Support `gcc' version 2.8, and remove support for prior versions
!      of `gcc'.
! 
!    * Remove support for the `--driver' option, as `g77' now does all
!      the driving, just like `gcc'.
! 
!    * `CASE DEFAULT' no longer crashes `g77'.
! 
!    * Valid combinations of `EXTERNAL', passing that external as a dummy
!      argument without explicitly giving it a type, and, in a subsequent
!      program unit, referencing that external as an external function
!      with a different type no longer crash `g77'.
! 
!    * `g77' no longer installs the `f77' command and `f77.1' man page in
!      the `/usr' or `/usr/local' hierarchy, even if the `f77-install-ok'
!      file exists in the source or build directory.  See the
!      installation documentation for more information.
! 
!    * `g77' no longer installs the `libf2c.a' library and `f2c.h'
!      include file in the `/usr' or `/usr/local' hierarchy, even if the
!      `f2c-install-ok' or `f2c-exists-ok' files exist in the source or
!      build directory.  See the installation documentation for more
!      information.
! 
!    * The `libf2c.a' library produced by `g77' has been renamed to
!      `libg2c.a'.  It is installed only in the `gcc' "private" directory
!      hierarchy, `gcc-lib'.  This allows system administrators and users
!      to choose which version of the `libf2c' library from `netlib' they
!      wish to use on a case-by-case basis.  See the installation
!      documentation for more information.
! 
!    * The `f2c.h' include (header) file produced by `g77' has been
!      renamed to `g2c.h'.  It is installed only in the `gcc' "private"
!      directory hierarchy, `gcc-lib'.  This allows system administrators
!      and users to choose which version of the include file from
!      `netlib' they wish to use on a case-by-case basis.  See the
!      installation documentation for more information.
! 
!    * The `g77' command now expects the run-time library to be named
!      `libg2c.a' instead of `libf2c.a', to ensure that a version other
!      than the one built and installed as part of the same `g77' version
!      is picked up.
! 
!    * The `-Wunused' option no longer issues a spurious warning about
!      the "master" procedure generated by `g77' for procedures
!      containing `ENTRY' statements.
! 
!    * `g77''s version of `libf2c' separates out the setting of global
!      state (such as command-line arguments and signal handling) from
!      `main.o' into distinct, new library archive members.
! 
!      This should make it easier to write portable applications that
!      have their own (non-Fortran) `main()' routine properly set up the
!      `libf2c' environment, even when `libf2c' (now `libg2c') is a
!      shared library.
! 
!    * During the configuration and build process, `g77' creates
!      subdirectories it needs only as it needs them, thus avoiding
!      unnecessary creation of, for example, `stage1/f/runtime' when
!      doing a non-bootstrap build.  Other cleaning up of the
!      configuration and build process has been performed as well.
! 
!    * `install-info' now used to update the directory of Info
!      documentation to contain an entry for `g77' (during installation).
! 
!    * Some diagnostics have been changed from warnings to errors, to
!      prevent inadvertent use of the resulting, probably buggy, programs.
!      These mostly include diagnostics about use of unsupported features
!      in the `OPEN', `INQUIRE', `READ', and `WRITE' statements, and
!      about truncations of various sorts of constants.
! 
!    * Improve documentation and indexing.
! 
!    * Upgrade to `libf2c' as of 1998-04-20.
! 
!      This should fix a variety of problems, including those involving
!      some uses of the `T' format specifier, and perhaps some build
!      (porting) problems as well.
! 
! In 0.5.22 versus 0.5.21:
! ========================
! 
!    * Fix code generation for iterative `DO' loops that have one or more
!      references to the iteration variable, or to aliases of it, in
!      their control expressions.  For example, `DO 10 J=2,J' now is
!      compiled correctly.
! 
!    * Fix a code-generation bug that afflicted Intel x86 targets when
!      `-O2' was specified compiling, for example, an old version of the
!      `DNRM2' routine.
! 
!      The x87 coprocessor stack was being mismanaged in cases involving
!      assigned `GOTO' and `ASSIGN'.
! 
!    * Fix `DTime' intrinsic so as not to truncate results to integer
!      values (on some systems).
! 
!    * Fix `Signal' intrinsic so it offers portable support for 64-bit
!      systems (such as Digital Alphas running GNU/Linux).
! 
!    * Fix run-time crash involving `NAMELIST' on 64-bit machines such as
!      Alphas.
! 
!    * Fix `g77' version of `libf2c' so it no longer produces a spurious
!      `I/O recursion' diagnostic at run time when an I/O operation (such
!      as `READ *,I') is interrupted in a manner that causes the program
!      to be terminated via the `f_exit' routine (such as via `C-c').
! 
!    * Fix `g77' crash triggered by `CASE' statement with an omitted
!      lower or upper bound.
! 
!    * Fix `g77' crash compiling references to `CPU_Time' intrinsic.
! 
!    * Fix `g77' crash (or apparently infinite run-time) when compiling
!      certain complicated expressions involving `COMPLEX' arithmetic
!      (especially multiplication).
! 
!    * Fix `g77' crash on statements such as `PRINT *,
!      (REAL(Z(I)),I=1,2)', where `Z' is `DOUBLE COMPLEX'.
! 
!    * Fix a `g++' crash.
! 
!    * Support `FORMAT(I<EXPR>)' when EXPR is a compile-time constant
!      `INTEGER' expression.
! 
!    * Fix `g77' `-g' option so procedures that use `ENTRY' can be
!      stepped through, line by line, in `gdb'.
! 
!    * Fix a profiling-related bug in `gcc' back end for Intel x86
!      architecture.
! 
!    * Allow any `REAL' argument to intrinsics `Second' and `CPU_Time'.
! 
!    * Allow any numeric argument to intrinsics `Int2' and `Int8'.
! 
!    * Use `tempnam', if available, to open scratch files (as in
!      `OPEN(STATUS='SCRATCH')') so that the `TMPDIR' environment
!      variable, if present, is used.
! 
!    * Rename the `gcc' keyword `restrict' to `__restrict__', to avoid
!      rejecting valid, existing, C programs.  Support for `restrict' is
!      now more like support for `complex'.
! 
!    * Fix `-fpedantic' to not reject procedure invocations such as
!      `I=J()' and `CALL FOO()'.
! 
!    * Fix `-fugly-comma' to affect invocations of only external
!      procedures.  Restore rejection of gratuitous trailing omitted
!      arguments to intrinsics, as in `I=MAX(3,4,,)'.
! 
!    * Fix compiler so it accepts `-fgnu-intrinsics-*' and
!      `-fbadu77-intrinsics-*' options.
! 
!    * Improve diagnostic messages from `libf2c' so it is more likely
!      that the printing of the active format string is limited to the
!      string, with no trailing garbage being printed.
! 
!      (Unlike `f2c', `g77' did not append a null byte to its compiled
!      form of every format string specified via a `FORMAT' statement.
!      However, `f2c' would exhibit the problem anyway for a statement
!      like `PRINT '(I)garbage', 1' by printing `(I)garbage' as the
!      format string.)
! 
!    * Improve compilation of `FORMAT' expressions so that a null byte is
!      appended to the last operand if it is a constant.  This provides a
!      cleaner run-time diagnostic as provided by `libf2c' for statements
!      like `PRINT '(I1', 42'.
! 
!    * Fix various crashes involving code with diagnosed errors.
! 
!    * Fix cross-compilation bug when configuring `libf2c'.
! 
!    * Improve diagnostics.
! 
!    * Improve documentation and indexing.
! 
!    * Upgrade to `libf2c' as of 1997-09-23.  This fixes a formatted-I/O
!      bug that afflicted 64-bit systems with 32-bit integers (such as
!      Digital Alpha running GNU/Linux).
! 
! In `EGCS' 1.0.2 versus `EGCS' 1.0.1:
! ====================================
! 
!    * Fix `g77' crash triggered by `CASE' statement with an omitted
!      lower or upper bound.
! 
!    * Fix `g77' crash on statements such as `PRINT *,
!      (REAL(Z(I)),I=1,2)', where `Z' is `DOUBLE COMPLEX'.
! 
!    * Fix `-fPIC' (such as compiling for ELF targets) on the Intel x86
!      architecture target so invalid assembler code is no longer
!      produced.
! 
!    * Fix `-fpedantic' to not reject procedure invocations such as
!      `I=J()' and `CALL FOO()'.
! 
!    * Fix `-fugly-comma' to affect invocations of only external
!      procedures.  Restore rejection of gratuitous trailing omitted
!      arguments to intrinsics, as in `I=MAX(3,4,,)'.
! 
!    * Fix compiler so it accepts `-fgnu-intrinsics-*' and
!      `-fbadu77-intrinsics-*' options.
! 
! In `EGCS' 1.0.1 versus `EGCS' 1.0:
! ==================================
! 
!    * Fix run-time crash involving `NAMELIST' on 64-bit machines such as
!      Alphas.
! 
! In `EGCS' 1.0 versus `g77' 0.5.21:
! ==================================
! 
!    * Version 1.0 of `egcs' contains several regressions against version
!      0.5.21 of `g77', due to using the "vanilla" `gcc' back end instead
!      of patching it to fix a few bugs and improve performance in a few
!      cases.
! 
!      Features that have been dropped from this version of `g77' due to
!      their being implemented via `g77'-specific patches to the `gcc'
!      back end in previous releases include:
! 
!         - Support for the C-language `restrict' keyword.
! 
!         - Support for the `-W' option warning about integer division by
!           zero.
! 
!         - The Intel x86-specific option `-malign-double' applying to
!           stack-allocated data as well as statically-allocate data.
! 
!      Note that the `gcc/f/gbe/' subdirectory has been removed from this
!      distribution as a result of `g77' being fully integrated with the
!      `egcs' variant of the `gcc' back end.
! 
!    * Fix code generation for iterative `DO' loops that have one or more
!      references to the iteration variable, or to aliases of it, in
!      their control expressions.  For example, `DO 10 J=2,J' now is
!      compiled correctly.
! 
!    * Fix `DTime' intrinsic so as not to truncate results to integer
!      values (on some systems).
! 
!    * Some Fortran code, miscompiled by `g77' built on `gcc' version
!      2.8.1 on m68k-next-nextstep3 configurations when using the `-O2'
!      option, is now compiled correctly.  It is believed that a C
!      function known to miscompile on that configuration when using the
!      `-O2 -funroll-loops' options also is now compiled correctly.
! 
!    * Remove support for non-`egcs' versions of `gcc'.
! 
!    * Remove support for the `--driver' option, as `g77' now does all
!      the driving, just like `gcc'.
! 
!    * Allow any numeric argument to intrinsics `Int2' and `Int8'.
! 
!    * Improve diagnostic messages from `libf2c' so it is more likely
!      that the printing of the active format string is limited to the
!      string, with no trailing garbage being printed.
! 
!      (Unlike `f2c', `g77' did not append a null byte to its compiled
!      form of every format string specified via a `FORMAT' statement.
!      However, `f2c' would exhibit the problem anyway for a statement
!      like `PRINT '(I)garbage', 1' by printing `(I)garbage' as the
!      format string.)
! 
!    * Upgrade to `libf2c' as of 1997-09-23.  This fixes a formatted-I/O
!      bug that afflicted 64-bit systems with 32-bit integers (such as
!      Digital Alpha running GNU/Linux).
! 
! In 0.5.21:
! ==========
! 
!    * Fix a code-generation bug introduced by 0.5.20 caused by loop
!      unrolling (by specifying `-funroll-loops' or similar).  This bug
!      afflicted all code compiled by version 2.7.2.2.f.2 of `gcc' (C,
!      C++, Fortran, and so on).
! 
!    * Fix a code-generation bug manifested when combining local
!      `EQUIVALENCE' with a `DATA' statement that follows the first
!      executable statement (or is treated as an executable-context
!      statement as a result of using the `-fpedantic' option).
! 
!    * Fix a compiler crash that occurred when an integer division by a
!      constant zero is detected.  Instead, when the `-W' option is
!      specified, the `gcc' back end issues a warning about such a case.
!      This bug afflicted all code compiled by version 2.7.2.2.f.2 of
!      `gcc' (C, C++, Fortran, and so on).
! 
!    * Fix a compiler crash that occurred in some cases of procedure
!      inlining.  (Such cases became more frequent in 0.5.20.)
! 
!    * Fix a compiler crash resulting from using `DATA' or similar to
!      initialize a `COMPLEX' variable or array to zero.
! 
!    * Fix compiler crashes involving use of `AND', `OR', or `XOR'
!      intrinsics.
! 
!    * Fix compiler bug triggered when using a `COMMON' or `EQUIVALENCE'
!      variable as the target of an `ASSIGN' or assigned-`GOTO' statement.
! 
!    * Fix compiler crashes due to using the name of a some non-standard
!      intrinsics (such as `FTell' or `FPutC') as such and as the name of
!      a procedure or common block.  Such dual use of a name in a program
!      is allowed by the standard.
! 
!    * Place automatic arrays on the stack, even if `SAVE' or the
!      `-fno-automatic' option is in effect.  This avoids a compiler
!      crash in some cases.
! 
!    * The `-malign-double' option now reliably aligns `DOUBLE PRECISION'
!      optimally on Pentium and Pentium Pro architectures (586 and 686 in
!      `gcc').
! 
!    * New option `-Wno-globals' disables warnings about "suspicious" use
!      of a name both as a global name and as the implicit name of an
!      intrinsic, and warnings about disagreements over the number or
!      natures of arguments passed to global procedures, or the natures
!      of the procedures themselves.
! 
!      The default is to issue such warnings, which are new as of this
!      version of `g77'.
! 
!    * New option `-fno-globals' disables diagnostics about potentially
!      fatal disagreements analysis problems, such as disagreements over
!      the number or natures of arguments passed to global procedures, or
!      the natures of those procedures themselves.
! 
!      The default is to issue such diagnostics and flag the compilation
!      as unsuccessful.  With this option, the diagnostics are issued as
!      warnings, or, if `-Wno-globals' is specified, are not issued at
!      all.
! 
!      This option also disables inlining of global procedures, to avoid
!      compiler crashes resulting from coding errors that these
!      diagnostics normally would identify.
! 
!    * Diagnose cases where a reference to a procedure disagrees with the
!      type of that procedure, or where disagreements about the number or
!      nature of arguments exist.  This avoids a compiler crash.
! 
!    * Fix parsing bug whereby `g77' rejected a second initialization
!      specification immediately following the first's closing `/' without
!      an intervening comma in a `DATA' statement, and the second
!      specification was an implied-DO list.
! 
!    * Improve performance of the `gcc' back end so certain complicated
!      expressions involving `COMPLEX' arithmetic (especially
!      multiplication) don't appear to take forever to compile.
! 
!    * Fix a couple of profiling-related bugs in `gcc' back end.
! 
!    * Integrate GNU Ada's (GNAT's) changes to the back end, which
!      consist almost entirely of bug fixes.  These fixes are circa
!      version 3.10p of GNAT.
! 
!    * Include some other `gcc' fixes that seem useful in `g77''s version
!      of `gcc'.  (See `gcc/ChangeLog' for details--compare it to that
!      file in the vanilla `gcc-2.7.2.3.tar.gz' distribution.)
! 
!    * Fix `libU77' routines that accept file and other names to strip
!      trailing blanks from them, for consistency with other
!      implementations.  Blanks may be forcibly appended to such names by
!      appending a single null character (`CHAR(0)') to the significant
!      trailing blanks.
! 
!    * Fix `CHMOD' intrinsic to work with file names that have embedded
!      blanks, commas, and so on.
! 
!    * Fix `SIGNAL' intrinsic so it accepts an optional third `Status'
!      argument.
! 
!    * Fix `IDATE()' intrinsic subroutine (VXT form) so it accepts
!      arguments in the correct order.  Documentation fixed accordingly,
!      and for `GMTIME()' and `LTIME()' as well.
! 
!    * Make many changes to `libU77' intrinsics to support existing code
!      more directly.
! 
!      Such changes include allowing both subroutine and function forms
!      of many routines, changing `MCLOCK()' and `TIME()' to return
!      `INTEGER(KIND=1)' values, introducing `MCLOCK8()' and `TIME8()' to
!      return `INTEGER(KIND=2)' values, and placing functions that are
!      intended to perform side effects in a new intrinsic group,
!      `badu77'.
! 
!    * Improve `libU77' so it is more portable.
! 
!    * Add options `-fbadu77-intrinsics-delete',
!      `-fbadu77-intrinsics-hide', and so on.
! 
!    * Fix crashes involving diagnosed or invalid code.
! 
!    * `g77' and `gcc' now do a somewhat better job detecting and
!      diagnosing arrays that are too large to handle before these cause
!      diagnostics during the assembler or linker phase, a compiler
!      crash, or generation of incorrect code.
! 
!    * Make some fixes to alias analysis code.
! 
!    * Add support for `restrict' keyword in `gcc' front end.
! 
!    * Support `gcc' version 2.7.2.3 (modified by `g77' into version
!      2.7.2.3.f.1), and remove support for prior versions of `gcc'.
! 
!    * Incorporate GNAT's patches to the `gcc' back end into `g77''s, so
!      GNAT users do not need to apply GNAT's patches to build both GNAT
!      and `g77' from the same source tree.
! 
!    * Modify `make' rules and related code so that generation of Info
!      documentation doesn't require compilation using `gcc'.  Now, any
!      ANSI C compiler should be adequate to produce the `g77'
!      documentation (in particular, the tables of intrinsics) from
!      scratch.
! 
!    * Add `INT2' and `INT8' intrinsics.
! 
!    * Add `CPU_TIME' intrinsic.
! 
!    * Add `ALARM' intrinsic.
! 
!    * `CTIME' intrinsic now accepts any `INTEGER' argument, not just
!      `INTEGER(KIND=2)'.
! 
!    * Warn when explicit type declaration disagrees with the type of an
!      intrinsic invocation.
! 
!    * Support `*f771' entry in `gcc' `specs' file.
! 
!    * Fix typo in `make' rule `g77-cross', used only for cross-compiling.
! 
!    * Fix `libf2c' build procedure to re-archive library if previous
!      attempt to archive was interrupted.
! 
!    * Change `gcc' to unroll loops only during the last invocation (of
!      as many as two invocations) of loop optimization.
! 
!    * Improve handling of `-fno-f2c' so that code that attempts to pass
!      an intrinsic as an actual argument, such as `CALL FOO(ABS)', is
!      rejected due to the fact that the run-time-library routine is,
!      effectively, compiled with `-ff2c' in effect.
! 
!    * Fix `g77' driver to recognize `-fsyntax-only' as an option that
!      inhibits linking, just like `-c' or `-S', and to recognize and
!      properly handle the `-nostdlib', `-M', `-MM', `-nodefaultlibs',
!      and `-Xlinker' options.
! 
!    * Upgrade to `libf2c' as of 1997-08-16.
! 
!    * Modify `libf2c' to consistently and clearly diagnose recursive I/O
!      (at run time).
! 
!    * `g77' driver now prints version information (such as produced by
!      `g77 -v') to `stderr' instead of `stdout'.
! 
!    * The `.r' suffix now designates a Ratfor source file, to be
!      preprocessed via the `ratfor' command, available separately.
! 
!    * Fix some aspects of how `gcc' determines what kind of system is
!      being configured and what kinds are supported.  For example, GNU
!      Linux/Alpha ELF systems now are directly supported.
! 
!    * Improve diagnostics.
! 
!    * Improve documentation and indexing.
! 
!    * Include all pertinent files for `libf2c' that come from
!      `netlib.bell-labs.com'; give any such files that aren't quite
!      accurate in `g77''s version of `libf2c' the suffix `.netlib'.
! 
!    * Reserve `INTEGER(KIND=0)' for future use.
! 
! In 0.5.20:
! ==========
! 
!    * The `-fno-typeless-boz' option is now the default.
! 
!      This option specifies that non-decimal-radix constants using the
!      prefixed-radix form (such as `Z'1234'') are to be interpreted as
!      `INTEGER(KIND=1)' constants.  Specify `-ftypeless-boz' to cause
!      such constants to be interpreted as typeless.
! 
!      (Version 0.5.19 introduced `-fno-typeless-boz' and its inverse.)
! 
!      *Note Options Controlling Fortran Dialect: Fortran Dialect Options,
!      for information on the `-ftypeless-boz' option.
! 
!    * Options `-ff90-intrinsics-enable' and `-fvxt-intrinsics-enable'
!      now are the defaults.
! 
!      Some programs might use names that clash with intrinsic names
!      defined (and now enabled) by these options or by the new `libU77'
!      intrinsics.  Users of such programs might need to compile them
!      differently (using, for example, `-ff90-intrinsics-disable') or,
!      better yet, insert appropriate `EXTERNAL' statements specifying
!      that these names are not intended to be names of intrinsics.
! 
!    * The `ALWAYS_FLUSH' macro is no longer defined when building
!      `libf2c', which should result in improved I/O performance,
!      especially over NFS.
! 
!      _Note:_ If you have code that depends on the behavior of `libf2c'
!      when built with `ALWAYS_FLUSH' defined, you will have to modify
!      `libf2c' accordingly before building it from this and future
!      versions of `g77'.
! 
!      *Note Output Assumed To Flush::, for more information.
! 
!    * Dave Love's implementation of `libU77' has been added to the
!      version of `libf2c' distributed with and built as part of `g77'.
!      `g77' now knows about the routines in this library as intrinsics.
! 
!    * New option `-fvxt' specifies that the source file is written in
!      VXT Fortran, instead of GNU Fortran.
! 
!      *Note VXT Fortran::, for more information on the constructs
!      recognized when the `-fvxt' option is specified.
! 
!    * The `-fvxt-not-f90' option has been deleted, along with its
!      inverse, `-ff90-not-vxt'.
! 
!      If you used one of these deleted options, you should re-read the
!      pertinent documentation to determine which options, if any, are
!      appropriate for compiling your code with this version of `g77'.
! 
!      *Note Other Dialects::, for more information.
! 
!    * The `-fugly' option now issues a warning, as it likely will be
!      removed in a future version.
! 
!      (Enabling all the `-fugly-*' options is unlikely to be feasible,
!      or sensible, in the future, so users should learn to specify only
!      those `-fugly-*' options they really need for a particular source
!      file.)
! 
!    * The `-fugly-assumed' option, introduced in version 0.5.19, has
!      been changed to better accommodate old and new code.
! 
!      *Note Ugly Assumed-Size Arrays::, for more information.
! 
!    * Make a number of fixes to the `g77' front end and the `gcc' back
!      end to better support Alpha (AXP) machines.  This includes
!      providing at least one bug-fix to the `gcc' back end for Alphas.
! 
!    * Related to supporting Alpha (AXP) machines, the `LOC()' intrinsic
!      and `%LOC()' construct now return values of `INTEGER(KIND=0)' type,
!      as defined by the GNU Fortran language.
! 
!      This type is wide enough (holds the same number of bits) as the
!      character-pointer type on the machine.
! 
!      On most machines, this won't make a difference, whereas, on Alphas
!      and other systems with 64-bit pointers, the `INTEGER(KIND=0)' type
!      is equivalent to `INTEGER(KIND=2)' (often referred to as
!      `INTEGER*8') instead of the more common `INTEGER(KIND=1)' (often
!      referred to as `INTEGER*4').
! 
!    * Emulate `COMPLEX' arithmetic in the `g77' front end, to avoid bugs
!      in `complex' support in the `gcc' back end.  New option
!      `-fno-emulate-complex' causes `g77' to revert the 0.5.19 behavior.
! 
!    * Fix bug whereby `REAL A(1)', for example, caused a compiler crash
!      if `-fugly-assumed' was in effect and A was a local (automatic)
!      array.  That case is no longer affected by the new handling of
!      `-fugly-assumed'.
! 
!    * Fix `g77' command driver so that `g77 -o foo.f' no longer deletes
!      `foo.f' before issuing other diagnostics, and so the `-x' option
!      is properly handled.
! 
!    * Enable inlining of subroutines and functions by the `gcc' back end.
!      This works as it does for `gcc' itself--program units may be
!      inlined for invocations that follow them in the same program unit,
!      as long as the appropriate compile-time options are specified.
! 
!    * Dummy arguments are no longer assumed to potentially alias
!      (overlap) other dummy arguments or `COMMON' areas when any of
!      these are defined (assigned to) by Fortran code.
! 
!      This can result in faster and/or smaller programs when compiling
!      with optimization enabled, though on some systems this effect is
!      observed only when `-fforce-addr' also is specified.
! 
!      New options `-falias-check', `-fargument-alias',
!      `-fargument-noalias', and `-fno-argument-noalias-global' control
!      the way `g77' handles potential aliasing.
! 
!      *Note Aliasing Assumed To Work::, for detailed information on why
!      the new defaults might result in some programs no longer working
!      the way they did when compiled by previous versions of `g77'.
! 
!    * The `CONJG()' and `DCONJG()' intrinsics now are compiled in-line.
! 
!    * The bug-fix for 0.5.19.1 has been re-done.  The `g77' compiler has
!      been changed back to assume `libf2c' has no aliasing problems in
!      its implementations of the `COMPLEX' (and `DOUBLE COMPLEX')
!      intrinsics.  The `libf2c' has been changed to have no such
!      problems.
! 
!      As a result, 0.5.20 is expected to offer improved performance over
!      0.5.19.1, perhaps as good as 0.5.19 in most or all cases, due to
!      this change alone.
! 
!      _Note:_ This change requires version 0.5.20 of `libf2c', at least,
!      when linking code produced by any versions of `g77' other than
!      0.5.19.1.  Use `g77 -v' to determine the version numbers of the
!      `libF77', `libI77', and `libU77' components of the `libf2c'
!      library.  (If these version numbers are not printed--in
!      particular, if the linker complains about unresolved references to
!      names like `g77__fvers__'--that strongly suggests your
!      installation has an obsolete version of `libf2c'.)
! 
!    * New option `-fugly-assign' specifies that the same memory
!      locations are to be used to hold the values assigned by both
!      statements `I = 3' and `ASSIGN 10 TO I', for example.  (Normally,
!      `g77' uses a separate memory location to hold assigned statement
!      labels.)
! 
!      *Note Ugly Assigned Labels::, for more information.
! 
!    * `FORMAT' and `ENTRY' statements now are allowed to precede
!      `IMPLICIT NONE' statements.
! 
!    * Produce diagnostic for unsupported `SELECT CASE' on `CHARACTER'
!      type, instead of crashing, at compile time.
! 
!    * Fix crashes involving diagnosed or invalid code.
! 
!    * Change approach to building `libf2c' archive (`libf2c.a') so that
!      members are added to it only when truly necessary, so the user
!      that installs an already-built `g77' doesn't need to have write
!      access to the build tree (whereas the user doing the build might
!      not have access to install new software on the system).
! 
!    * Support `gcc' version 2.7.2.2 (modified by `g77' into version
!      2.7.2.2.f.2), and remove support for prior versions of `gcc'.
! 
!    * Upgrade to `libf2c' as of 1997-02-08, and fix up some of the build
!      procedures.
! 
!    * Improve general build procedures for `g77', fixing minor bugs
!      (such as deletion of any file named `f771' in the parent directory
!      of `gcc/').
! 
!    * Enable full support of `INTEGER(KIND=2)' (often referred to as
!      `INTEGER*8') available in `libf2c' and `f2c.h' so that `f2c' users
!      may make full use of its features via the `g77' version of `f2c.h'
!      and the `INTEGER(KIND=2)' support routines in the `g77' version of
!      `libf2c'.
! 
!    * Improve `g77' driver and `libf2c' so that `g77 -v' yields version
!      information on the library.
! 
!    * The `SNGL' and `FLOAT' intrinsics now are specific intrinsics,
!      instead of synonyms for the generic intrinsic `REAL'.
! 
!    * New intrinsics have been added.  These are `REALPART', `IMAGPART',
!      `COMPLEX', `LONG', and `SHORT'.
! 
!    * A new group of intrinsics, `gnu', has been added to contain the
!      new `REALPART', `IMAGPART', and `COMPLEX' intrinsics.  An old
!      group, `dcp', has been removed.
! 
!    * Complain about industry-wide ambiguous references `REAL(EXPR)' and
!      `AIMAG(EXPR)', where EXPR is `DOUBLE COMPLEX' (or any complex type
!      other than `COMPLEX'), unless `-ff90' option specifies Fortran 90
!      interpretation or new `-fugly-complex' option, in conjunction with
!      `-fnot-f90', specifies `f2c' interpretation.
! 
!    * Make improvements to diagnostics.
! 
!    * Speed up compiler a bit.
! 
!    * Improvements to documentation and indexing, including a new
!      chapter containing information on one, later more, diagnostics
!      that users are directed to pull up automatically via a message in
!      the diagnostic itself.
! 
!      (Hence the menu item `M' for the node `Diagnostics' in the
!      top-level menu of the Info documentation.)
! 
! In previous versions:
! =====================
! 
!    Information on previous versions is archived in `gcc/gcc/f/news.texi'
! following the test of the `DOC-OLDNEWS' macro.
! 
! 
! File: g77.info,  Node: Changes,  Next: Language,  Prev: News,  Up: Top
! 
! User-visible Changes
! ********************
! 
!    This chapter describes changes to `g77' that are visible to the
! programmers who actually write and maintain Fortran code they compile
! with `g77'.  Information on changes to installation procedures, changes
! to the documentation, and bug fixes is not provided here, unless it is
! likely to affect how users use `g77'.  *Note News About GNU Fortran:
! News, for information on such changes to `g77'.
! 
!    Note that two variants of `g77' are tracked below.  The `egcs'
! variant is described vis-a-vis previous versions of `egcs' and/or an
! official FSF version, as appropriate.  Note that all such variants are
! obsolete _as of July 1999_ - the information is retained here only for
! its historical value.
! 
!    Therefore, `egcs' versions sometimes have multiple listings to help
! clarify how they differ from other versions, though this can make
! getting a complete picture of what a particular `egcs' version contains
! somewhat more difficult.
! 
!    For information on bugs in the GCC-3.3 version of `g77', see *Note
! Known Bugs In GNU Fortran: Known Bugs.
! 
!    The following information was last updated on 2003-04-11:
! 
! In `GCC' 3.3 versus `GCC' 3.2:
! ==============================
! 
!    * Problem Reports fixed (in chronological order of submission):
!     `1832'
!           -list directed i/o overflow hangs, -fbounds-check doesn't
!           detect
! 
!     `3924'
!           g77 generates code which is rejected by GAS if COFF debugging
!           info is requested
! 
!     `6286'
!           Broken links on web pages
! 
!     `6367'
!           (libf2c) multiple repeat counts confuse namelist read into
!           array
! 
!     `6491'
!           Logical operations error on logicals when using -fugly-logint
! 
!     `6742'
!           Generation of C++ Prototype for FORTRAN and extern "C"
! 
!     `7113'
!           Failure of g77.f-torture/execute/f90-intrinsic-bit.f -Os on
!           irix6.5
! 
!     `7236'
!           (libf2c) OPEN(...,RECL=nnn,...) without ACCESS='DIRECT'
!           should assume a direct access file
! 
!     `7278'
!           g77 "bug"; the executable misbehave (use of options -O2
!           -fno-automatic gave wrong results)
! 
!     `7384'
!           (libf2c) DATE_AND_TIME milliseconds field inactive on Windows
! 
!     `7388'
!           Incorrect output with 0-based array of characters
! 
!     `8587'
!           Double complex zero ** double precision number -> NaN instead
!           of zero
! 
!     `9038'
!           -ffixed-line-length-none -x f77-cpp-input gives: Warning:
!           unknown register name line-length-none
! 
!     `9263'
!           ICE caused by invalid PARAMETER in implied DO loop
! 
!     `10197'
!           Direct access files not unformatted by default
! 
!    * Richard Henderson (<rth@redhat.com>) analyzed and improved the
!      handling of (no-)aliasing information for dummy arguments and
!      improved the optimization of induction variables in unrolled loops.
! 
! In `GCC' 3.2 versus `GCC' 3.1:
! ==============================
! 
!    * Problem Reports fixed (in chronological order of submission):
!     `7681'
!           ICE in compensate_edge, at reg-stack.c:2591
! 
!     `8308'
!           gcc-3.x does not compile files with suffix .r (RATFOR) [Fixed
!           in 3.2.1]
! 
!     `9258'
!           [3.2/3.3/3.4 regression] ICE in compensate_edge, at
!           reg-stack.c:2589
! 
! In `GCC' 3.1 (formerly known as g77-0.5.27) versus `GCC' 3.0:
! =============================================================
! 
!    * Problem Reports fixed (in chronological order of submission):
!     `947'
!           Data statement initialization with subscript of kind INTEGER*2
! 
!     `3743'
!           Reference to intrinsic `ISHFT' invalid
! 
!     `3807'
!           Function BESJN(integer,double) problems
! 
!     `3957'
!           g77 -pipe -xf77-cpp-input sends output to stdout
! 
!     `4279'
!           g77 -h" gives bogus output
! 
!     `4730'
!           ICE on valid input using CALL EXIT(%VAL(...))
! 
!     `4752'
!           g77 -v -c -xf77-version /dev/null -xnone causes ice
! 
!     `4885'
!           BACKSPACE example that doesn't work as of gcc/g77-3.0.x
! 
!     `5122'
!           g77 rejects accepted use of INTEGER*2 as type of DATA
!           statement loop index
! 
!     `5397'
!           ICE on compiling source with 540 000 000 REAL array
! 
!     `5473'
!           ICE on BESJN(integer*8,real)
! 
!     `5837'
!           bug in loop unrolling
! 
!     `6106'
!           sparc-sun-solaris2.7 gcc-3.1 extra g77 testsuite failures
!           w/-m64
! 
!     `6138'
!           Incorrect acces of integer*1 variables on PA
! 
!     `6304'
!           Failure of LAPACK test dtest on irix6.5 with -mabi=64 -O2
! 
!    * `g77' now has its man page generated from the texinfo
!      documentation, to guarantee that it remains up to date.
! 
!    * `g77' used to reject the following program on 32-bit targets:
!           PROGRAM PROG
!           DIMENSION A(140 000 000)
!           END
!      with the message:
!           prog.f: In program `prog':
!           prog.f:2:
!                    DIMENSION A(140 000 000)
!                              ^
!           Array `a' at (^) is too large to handle
!      because 140 000 000 REALs is larger than the largest bit-extent
!      that can be expressed in 32 bits.  However, bit-sizes never play a
!      role after offsets have been converted to byte addresses.
!      Therefore this check has been removed, and the limit is now 2
!      Gbyte of memory (around 530 000 000 REALs).  Note: On GNU/Linux
!      systems one has to compile and link programs that occupy more than
!      1 Gbyte statically, i.e. `g77 -static ...'.
! 
!    * Based on work done by Juergen Pfeifer (<juergen.pfeifer@gmx.net>)
!      libf2c is now a shared library.  One can still link in all objects
!      with the program by specifying the `-static' option.
! 
!    * Robert Anderson (<rwa@alumni.princeton.edu>) thought up a two line
!      change that enables g77 to compile such code as:
!           SUBROUTINE SUB(A, N)
!           DIMENSION N(2)
!           DIMENSION A(N(1),N(2))
!           A(1,1) = 1.
!           END
!      Note the use of array elements in the bounds of the adjustable
!      array A.
! 
!    * George Helffrich (<george@geo.titech.ac.jp>) implemented a change
!      in substring index checking (when specifying `-fbounds-check')
!      that permits the use of zero length substrings of the form
!      `string(1:0)'.
! 
!    * Based on code developed by Pedro Vazquez
!      (<vazquez@penelope.iqm.unicamp.br>), the `libf2c' library is now
!      able to read and write files larger than 2 Gbyte on 32-bit target
!      machines, if the operating system supports this.
! 
! In 0.5.26, `GCC' 3.0 versus `GCC' 2.95:
! =======================================
! 
!    * When a REWIND was issued after a WRITE statement on an unformatted
!      file, the implicit truncation was performed by copying the
!      truncated file to /tmp and copying the result back.  This has been
!      fixed by using the `ftruncate' OS function.  Thanks go to the
!      GAMESS developers for bringing this to our attention.
! 
!    * Using options `-g', `-ggdb' or `-gdwarf[-2]' (where appropriate
!      for your target) now also enables debugging information for COMMON
!      BLOCK and EQUIVALENCE items to be emitted.  Thanks go to Andrew
!      Vaught (<andy@xena.eas.asu.edu>) and George Helffrich
!      (<george@geology.bristol.ac.uk>) for fixing this longstanding
!      problem.
! 
!    * It is not necessary anymore to use the option `-femulate-complex'
!      to compile Fortran code using COMPLEX arithmetic, even on 64-bit
!      machines (like the Alpha).  This will improve code generation.
! 
!    * INTRINSIC arithmetic functions are now treated as routines that do
!      not depend on anything but their argument(s).  This enables
!      further instruction scheduling, because it is known that they
!      cannot read or modify arbitrary locations.
! 
! 
! In 0.5.25, `GCC' 2.95 (`EGCS' 1.2) versus `EGCS' 1.1.2:
! =======================================================
! 
!    * The new `-fbounds-check' option causes `g77' to compile run-time
!      bounds checks of array subscripts, as well as of substring start
!      and end points.
! 
!    * `libg2c' now supports building as multilibbed library, which
!      provides better support for systems that require options such as
!      `-mieee' to work properly.
! 
!    * Source file names with the suffixes `.FOR' and `.FPP' now are
!      recognized by `g77' as if they ended in `.for' and `.fpp',
!      respectively.
! 
!    * The order of arguments to the _subroutine_ forms of the `CTime',
!      `DTime', `ETime', and `TtyNam' intrinsics has been swapped.  The
!      argument serving as the returned value for the corresponding
!      function forms now is the _second_ argument, making these
!      consistent with the other subroutine forms of `libU77' intrinsics.
! 
!    * `g77' now warns about a reference to an intrinsic that has an
!      interface that is not Year 2000 (Y2K) compliant.  Also, `libg2c'
!      has been changed to increase the likelihood of catching references
!      to the implementations of these intrinsics using the `EXTERNAL'
!      mechanism (which would avoid the new warnings).
! 
!      *Note Year 2000 (Y2K) Problems::, for more information.
! 
!    * `-fno-emulate-complex' is now the default option.  This should
!      result in improved performance of code that uses the `COMPLEX'
!      data type.
! 
!    * The `-malign-double' option now reliably aligns _all_
!      double-precision variables and arrays on Intel x86 targets.
! 
!    * `g77' no longer generates code to maintain `errno', a C-language
!      concept, when performing operations such as the `SqRt' intrinsic.
! 
!    * Support for the `-fugly' option has been removed.
! 
! 
! In 0.5.24 versus 0.5.23:
! ========================
! 
!    There is no `g77' version 0.5.24 at this time, or planned.  0.5.24
! is the version number designated for bug fixes and, perhaps, some new
! features added, to 0.5.23.  Version 0.5.23 requires `gcc' 2.8.1, as
! 0.5.24 was planned to require.
! 
!    Due to `EGCS' becoming `GCC' (which is now an acronym for "GNU
! Compiler Collection"), and `EGCS' 1.2 becoming officially designated
! `GCC' 2.95, there seems to be no need for an actual 0.5.24 release.
! 
!    To reduce the confusion already resulting from use of 0.5.24 to
! designate `g77' versions within `EGCS' versions 1.0 and 1.1, as well as
! in versions of `g77' documentation and notices during that period,
! "mainline" `g77' version numbering resumes at 0.5.25 with `GCC' 2.95
! (`EGCS' 1.2), skipping over 0.5.24 as a placeholder version number.
! 
!    To repeat, there is no `g77' 0.5.24, but there is now a 0.5.25.
! Please remain calm and return to your keypunch units.
! 
! In `EGCS' 1.1.2 versus `EGCS' 1.1.1:
! ====================================
! 
! In `EGCS' 1.1.1 versus `EGCS' 1.1:
! ==================================
! 
! In `EGCS' 1.1 versus `EGCS' 1.0.3:
! ==================================
! 
!    * Support `FORMAT(I<EXPR>)' when EXPR is a compile-time constant
!      `INTEGER' expression.
! 
!    * Fix `g77' `-g' option so procedures that use `ENTRY' can be
!      stepped through, line by line, in `gdb'.
! 
!    * Allow any `REAL' argument to intrinsics `Second' and `CPU_Time'.
! 
!    * Use `tempnam', if available, to open scratch files (as in
!      `OPEN(STATUS='SCRATCH')') so that the `TMPDIR' environment
!      variable, if present, is used.
! 
!    * `g77''s version of `libf2c' separates out the setting of global
!      state (such as command-line arguments and signal handling) from
!      `main.o' into distinct, new library archive members.
! 
!      This should make it easier to write portable applications that
!      have their own (non-Fortran) `main()' routine properly set up the
!      `libf2c' environment, even when `libf2c' (now `libg2c') is a
!      shared library.
! 
!    * The `g77' command now expects the run-time library to be named
!      `libg2c.a' instead of `libf2c.a', to ensure that a version other
!      than the one built and installed as part of the same `g77' version
!      is picked up.
! 
!    * Some diagnostics have been changed from warnings to errors, to
!      prevent inadvertent use of the resulting, probably buggy, programs.
!      These mostly include diagnostics about use of unsupported features
!      in the `OPEN', `INQUIRE', `READ', and `WRITE' statements, and
!      about truncations of various sorts of constants.
! 
! 
! In `EGCS' 1.1 versus `g77' 0.5.23:
! ==================================
! 
!    * `g77' now treats `%LOC(EXPR)' and `LOC(EXPR)' as "ordinary"
!      expressions when they are used as arguments in procedure calls.
!      This change applies only to global (filewide) analysis, making it
!      consistent with how `g77' actually generates code for these cases.
! 
!      Previously, `g77' treated these expressions as denoting special
!      "pointer" arguments for the purposes of filewide analysis.
! 
!    * Align static double-precision variables and arrays on Intel x86
!      targets regardless of whether `-malign-double' is specified.
! 
!      Generally, this affects only local variables and arrays having the
!      `SAVE' attribute or given initial values via `DATA'.
! 
!    * The `g77' driver now ensures that `-lg2c' is specified in the link
!      phase prior to any occurrence of `-lm'.  This prevents
!      accidentally linking to a routine in the SunOS4 `-lm' library when
!      the generated code wants to link to the one in `libf2c' (`libg2c').
! 
!    * `g77' emits more debugging information when `-g' is used.
! 
!      This new information allows, for example, `which __g77_length_a'
!      to be used in `gdb' to determine the type of the phantom length
!      argument supplied with `CHARACTER' variables.
! 
!      This information pertains to internally-generated type, variable,
!      and other information, not to the longstanding deficiencies
!      vis-a-vis `COMMON' and `EQUIVALENCE'.
! 
!    * The F90 `Date_and_Time' intrinsic now is supported.
! 
!    * The F90 `System_Clock' intrinsic allows the optional arguments
!      (except for the `Count' argument) to be omitted.
! 
! 
! In 0.5.23 versus 0.5.22:
! ========================
! 
!    * This release contains several regressions against version 0.5.22
!      of `g77', due to using the "vanilla" `gcc' back end instead of
!      patching it to fix a few bugs and improve performance in a few
!      cases.
! 
!      Features that have been dropped from this version of `g77' due to
!      their being implemented via `g77'-specific patches to the `gcc'
!      back end in previous releases include:
! 
!         - Support for `__restrict__' keyword, the options
!           `-fargument-alias', `-fargument-noalias', and
!           `-fargument-noalias-global', and the corresponding
!           alias-analysis code.
! 
!           (`egcs' has the alias-analysis code, but not the
!           `__restrict__' keyword.  `egcs' `g77' users benefit from the
!           alias-analysis code despite the lack of the `__restrict__'
!           keyword, which is a C-language construct.)
! 
!         - Support for the GNU compiler options `-fmove-all-movables',
!           `-freduce-all-givs', and `-frerun-loop-opt'.
! 
!           (`egcs' supports these options.  `g77' users of `egcs'
!           benefit from them even if they are not explicitly specified,
!           because the defaults are optimized for `g77' users.)
! 
!         - Support for the `-W' option warning about integer division by
!           zero.
! 
!         - The Intel x86-specific option `-malign-double' applying to
!           stack-allocated data as well as statically-allocate data.
! 
!    * Support `gcc' version 2.8, and remove support for prior versions
!      of `gcc'.
! 
!    * Remove support for the `--driver' option, as `g77' now does all
!      the driving, just like `gcc'.
! 
!    * The `g77' command now expects the run-time library to be named
!      `libg2c.a' instead of `libf2c.a', to ensure that a version other
!      than the one built and installed as part of the same `g77' version
!      is picked up.
! 
!    * `g77''s version of `libf2c' separates out the setting of global
!      state (such as command-line arguments and signal handling) from
!      `main.o' into distinct, new library archive members.
! 
!      This should make it easier to write portable applications that
!      have their own (non-Fortran) `main()' routine properly set up the
!      `libf2c' environment, even when `libf2c' (now `libg2c') is a
!      shared library.
! 
!    * Some diagnostics have been changed from warnings to errors, to
!      prevent inadvertent use of the resulting, probably buggy, programs.
!      These mostly include diagnostics about use of unsupported features
!      in the `OPEN', `INQUIRE', `READ', and `WRITE' statements, and
!      about truncations of various sorts of constants.
! 
! 
! In 0.5.22 versus 0.5.21:
! ========================
! 
!    * Fix `Signal' intrinsic so it offers portable support for 64-bit
!      systems (such as Digital Alphas running GNU/Linux).
! 
!    * Support `FORMAT(I<EXPR>)' when EXPR is a compile-time constant
!      `INTEGER' expression.
! 
!    * Fix `g77' `-g' option so procedures that use `ENTRY' can be
!      stepped through, line by line, in `gdb'.
! 
!    * Allow any `REAL' argument to intrinsics `Second' and `CPU_Time'.
! 
!    * Allow any numeric argument to intrinsics `Int2' and `Int8'.
! 
!    * Use `tempnam', if available, to open scratch files (as in
!      `OPEN(STATUS='SCRATCH')') so that the `TMPDIR' environment
!      variable, if present, is used.
! 
!    * Rename the `gcc' keyword `restrict' to `__restrict__', to avoid
!      rejecting valid, existing, C programs.  Support for `restrict' is
!      now more like support for `complex'.
! 
!    * Fix `-fugly-comma' to affect invocations of only external
!      procedures.  Restore rejection of gratuitous trailing omitted
!      arguments to intrinsics, as in `I=MAX(3,4,,)'.
! 
!    * Fix compiler so it accepts `-fgnu-intrinsics-*' and
!      `-fbadu77-intrinsics-*' options.
! 
! 
! In `EGCS' 1.0.2 versus `EGCS' 1.0.1:
! ====================================
! 
!    * Fix compiler so it accepts `-fgnu-intrinsics-*' and
!      `-fbadu77-intrinsics-*' options.
! 
! In `EGCS' 1.0.1 versus `EGCS' 1.0:
! ==================================
! 
! In `EGCS' 1.0 versus `g77' 0.5.21:
! ==================================
! 
!    * Version 1.0 of `egcs' contains several regressions against version
!      0.5.21 of `g77', due to using the "vanilla" `gcc' back end instead
!      of patching it to fix a few bugs and improve performance in a few
!      cases.
! 
!      Features that have been dropped from this version of `g77' due to
!      their being implemented via `g77'-specific patches to the `gcc'
!      back end in previous releases include:
! 
!         - Support for the C-language `restrict' keyword.
! 
!         - Support for the `-W' option warning about integer division by
!           zero.
! 
!         - The Intel x86-specific option `-malign-double' applying to
!           stack-allocated data as well as statically-allocate data.
! 
!    * Remove support for the `--driver' option, as `g77' now does all
!      the driving, just like `gcc'.
! 
!    * Allow any numeric argument to intrinsics `Int2' and `Int8'.
! 
! 
! In 0.5.21:
! ==========
! 
!    * When the `-W' option is specified, `gcc', `g77', and other GNU
!      compilers that incorporate the `gcc' back end as modified by
!      `g77', issue a warning about integer division by constant zero.
! 
!    * New option `-Wno-globals' disables warnings about "suspicious" use
!      of a name both as a global name and as the implicit name of an
!      intrinsic, and warnings about disagreements over the number or
!      natures of arguments passed to global procedures, or the natures
!      of the procedures themselves.
! 
!      The default is to issue such warnings, which are new as of this
!      version of `g77'.
! 
!    * New option `-fno-globals' disables diagnostics about potentially
!      fatal disagreements analysis problems, such as disagreements over
!      the number or natures of arguments passed to global procedures, or
!      the natures of those procedures themselves.
! 
!      The default is to issue such diagnostics and flag the compilation
!      as unsuccessful.  With this option, the diagnostics are issued as
!      warnings, or, if `-Wno-globals' is specified, are not issued at
!      all.
! 
!      This option also disables inlining of global procedures, to avoid
!      compiler crashes resulting from coding errors that these
!      diagnostics normally would identify.
! 
!    * Fix `libU77' routines that accept file and other names to strip
!      trailing blanks from them, for consistency with other
!      implementations.  Blanks may be forcibly appended to such names by
!      appending a single null character (`CHAR(0)') to the significant
!      trailing blanks.
! 
!    * Fix `CHMOD' intrinsic to work with file names that have embedded
!      blanks, commas, and so on.
! 
!    * Fix `SIGNAL' intrinsic so it accepts an optional third `Status'
!      argument.
! 
!    * Make many changes to `libU77' intrinsics to support existing code
!      more directly.
! 
!      Such changes include allowing both subroutine and function forms
!      of many routines, changing `MCLOCK()' and `TIME()' to return
!      `INTEGER(KIND=1)' values, introducing `MCLOCK8()' and `TIME8()' to
!      return `INTEGER(KIND=2)' values, and placing functions that are
!      intended to perform side effects in a new intrinsic group,
!      `badu77'.
! 
!    * Add options `-fbadu77-intrinsics-delete',
!      `-fbadu77-intrinsics-hide', and so on.
! 
!    * Add `INT2' and `INT8' intrinsics.
! 
!    * Add `CPU_TIME' intrinsic.
! 
!    * Add `ALARM' intrinsic.
! 
!    * `CTIME' intrinsic now accepts any `INTEGER' argument, not just
!      `INTEGER(KIND=2)'.
! 
!    * `g77' driver now prints version information (such as produced by
!      `g77 -v') to `stderr' instead of `stdout'.
! 
!    * The `.r' suffix now designates a Ratfor source file, to be
!      preprocessed via the `ratfor' command, available separately.
! 
! 
! In 0.5.20:
! ==========
! 
!    * The `-fno-typeless-boz' option is now the default.
! 
!      This option specifies that non-decimal-radix constants using the
!      prefixed-radix form (such as `Z'1234'') are to be interpreted as
!      `INTEGER(KIND=1)' constants.  Specify `-ftypeless-boz' to cause
!      such constants to be interpreted as typeless.
! 
!      (Version 0.5.19 introduced `-fno-typeless-boz' and its inverse.)
! 
!      *Note Options Controlling Fortran Dialect: Fortran Dialect Options,
!      for information on the `-ftypeless-boz' option.
! 
!    * Options `-ff90-intrinsics-enable' and `-fvxt-intrinsics-enable'
!      now are the defaults.
! 
!      Some programs might use names that clash with intrinsic names
!      defined (and now enabled) by these options or by the new `libU77'
!      intrinsics.  Users of such programs might need to compile them
!      differently (using, for example, `-ff90-intrinsics-disable') or,
!      better yet, insert appropriate `EXTERNAL' statements specifying
!      that these names are not intended to be names of intrinsics.
! 
!    * The `ALWAYS_FLUSH' macro is no longer defined when building
!      `libf2c', which should result in improved I/O performance,
!      especially over NFS.
! 
!      _Note:_ If you have code that depends on the behavior of `libf2c'
!      when built with `ALWAYS_FLUSH' defined, you will have to modify
!      `libf2c' accordingly before building it from this and future
!      versions of `g77'.
! 
!      *Note Output Assumed To Flush::, for more information.
! 
!    * Dave Love's implementation of `libU77' has been added to the
!      version of `libf2c' distributed with and built as part of `g77'.
!      `g77' now knows about the routines in this library as intrinsics.
! 
!    * New option `-fvxt' specifies that the source file is written in
!      VXT Fortran, instead of GNU Fortran.
! 
!      *Note VXT Fortran::, for more information on the constructs
!      recognized when the `-fvxt' option is specified.
! 
!    * The `-fvxt-not-f90' option has been deleted, along with its
!      inverse, `-ff90-not-vxt'.
! 
!      If you used one of these deleted options, you should re-read the
!      pertinent documentation to determine which options, if any, are
!      appropriate for compiling your code with this version of `g77'.
! 
!      *Note Other Dialects::, for more information.
! 
!    * The `-fugly' option now issues a warning, as it likely will be
!      removed in a future version.
! 
!      (Enabling all the `-fugly-*' options is unlikely to be feasible,
!      or sensible, in the future, so users should learn to specify only
!      those `-fugly-*' options they really need for a particular source
!      file.)
! 
!    * The `-fugly-assumed' option, introduced in version 0.5.19, has
!      been changed to better accommodate old and new code.
! 
!      *Note Ugly Assumed-Size Arrays::, for more information.
! 
!    * Related to supporting Alpha (AXP) machines, the `LOC()' intrinsic
!      and `%LOC()' construct now return values of `INTEGER(KIND=0)' type,
!      as defined by the GNU Fortran language.
! 
!      This type is wide enough (holds the same number of bits) as the
!      character-pointer type on the machine.
! 
!      On most machines, this won't make a difference, whereas, on Alphas
!      and other systems with 64-bit pointers, the `INTEGER(KIND=0)' type
!      is equivalent to `INTEGER(KIND=2)' (often referred to as
!      `INTEGER*8') instead of the more common `INTEGER(KIND=1)' (often
!      referred to as `INTEGER*4').
! 
!    * Emulate `COMPLEX' arithmetic in the `g77' front end, to avoid bugs
!      in `complex' support in the `gcc' back end.  New option
!      `-fno-emulate-complex' causes `g77' to revert the 0.5.19 behavior.
! 
!    * Dummy arguments are no longer assumed to potentially alias
!      (overlap) other dummy arguments or `COMMON' areas when any of
!      these are defined (assigned to) by Fortran code.
! 
!      This can result in faster and/or smaller programs when compiling
!      with optimization enabled, though on some systems this effect is
!      observed only when `-fforce-addr' also is specified.
! 
!      New options `-falias-check', `-fargument-alias',
!      `-fargument-noalias', and `-fno-argument-noalias-global' control
!      the way `g77' handles potential aliasing.
! 
!      *Note Aliasing Assumed To Work::, for detailed information on why
!      the new defaults might result in some programs no longer working
!      the way they did when compiled by previous versions of `g77'.
! 
!    * New option `-fugly-assign' specifies that the same memory
!      locations are to be used to hold the values assigned by both
!      statements `I = 3' and `ASSIGN 10 TO I', for example.  (Normally,
!      `g77' uses a separate memory location to hold assigned statement
!      labels.)
! 
!      *Note Ugly Assigned Labels::, for more information.
! 
!    * `FORMAT' and `ENTRY' statements now are allowed to precede
!      `IMPLICIT NONE' statements.
! 
!    * Enable full support of `INTEGER(KIND=2)' (often referred to as
!      `INTEGER*8') available in `libf2c' and `f2c.h' so that `f2c' users
!      may make full use of its features via the `g77' version of `f2c.h'
!      and the `INTEGER(KIND=2)' support routines in the `g77' version of
!      `libf2c'.
! 
!    * Improve `g77' driver and `libf2c' so that `g77 -v' yields version
!      information on the library.
! 
!    * The `SNGL' and `FLOAT' intrinsics now are specific intrinsics,
!      instead of synonyms for the generic intrinsic `REAL'.
! 
!    * New intrinsics have been added.  These are `REALPART', `IMAGPART',
!      `COMPLEX', `LONG', and `SHORT'.
! 
!    * A new group of intrinsics, `gnu', has been added to contain the
!      new `REALPART', `IMAGPART', and `COMPLEX' intrinsics.  An old
!      group, `dcp', has been removed.
! 
!    * Complain about industry-wide ambiguous references `REAL(EXPR)' and
!      `AIMAG(EXPR)', where EXPR is `DOUBLE COMPLEX' (or any complex type
!      other than `COMPLEX'), unless `-ff90' option specifies Fortran 90
!      interpretation or new `-fugly-complex' option, in conjunction with
!      `-fnot-f90', specifies `f2c' interpretation.
! 
! 
! In previous versions:
! =====================
! 
!    Information on previous versions is archived in `gcc/gcc/f/news.texi'
! following the test of the `DOC-OLDNEWS' macro.
! 
! 
! File: g77.info,  Node: Language,  Next: Compiler,  Prev: Changes,  Up: Top
! 
! The GNU Fortran Language
! ************************
! 
!    GNU Fortran supports a variety of extensions to, and dialects of,
! the Fortran language.  Its primary base is the ANSI FORTRAN 77
! standard, currently available on the network at
! `http://www.fortran.com/fortran/F77_std/rjcnf0001.html' or as
! monolithic text at
! `http://www.fortran.com/fortran/F77_std/f77_std.html'.  It offers some
! extensions that are popular among users of UNIX `f77' and `f2c'
! compilers, some that are popular among users of other compilers (such
! as Digital products), some that are popular among users of the newer
! Fortran 90 standard, and some that are introduced by GNU Fortran.
! 
!    (If you need a text on Fortran, a few freely available electronic
! references have pointers from `http://www.fortran.com/fortran/Books/'.
! There is a `cooperative net project', `User Notes on Fortran
! Programming' at `ftp://vms.huji.ac.il/fortran/' and mirrors elsewhere;
! some of this material might not apply specifically to `g77'.)
! 
!    Part of what defines a particular implementation of a Fortran
! system, such as `g77', is the particular characteristics of how it
! supports types, constants, and so on.  Much of this is left up to the
! implementation by the various Fortran standards and accepted practice
! in the industry.
! 
!    The GNU Fortran _language_ is described below.  Much of the material
! is organized along the same lines as the ANSI FORTRAN 77 standard
! itself.
! 
!    *Note Other Dialects::, for information on features `g77' supports
! that are not part of the GNU Fortran language.
! 
!    _Note_: This portion of the documentation definitely needs a lot of
! work!
! 
! * Menu:
! 
! Relationship to the ANSI FORTRAN 77 standard:
! * Direction of Language Development::  Where GNU Fortran is headed.
! * Standard Support::  Degree of support for the standard.
! 
! Extensions to the ANSI FORTRAN 77 standard:
! * Conformance::
! * Notation Used::
! * Terms and Concepts::
! * Characters Lines Sequence::
! * Data Types and Constants::
! * Expressions::
! * Specification Statements::
! * Control Statements::
! * Functions and Subroutines::
! * Scope and Classes of Names::
! * I/O::
! * Fortran 90 Features::
! 
! 
! File: g77.info,  Node: Direction of Language Development,  Next: Standard Support,  Up: Language
! 
! Direction of Language Development
! =================================
! 
!    The purpose of the following description of the GNU Fortran language
! is to promote wide portability of GNU Fortran programs.
! 
!    GNU Fortran is an evolving language, due to the fact that `g77'
! itself is in beta test.  Some current features of the language might
! later be redefined as dialects of Fortran supported by `g77' when
! better ways to express these features are added to `g77', for example.
! Such features would still be supported by `g77', but would be available
! only when one or more command-line options were used.
! 
!    The GNU Fortran _language_ is distinct from the GNU Fortran
! _compilation system_ (`g77').
! 
!    For example, `g77' supports various dialects of Fortran--in a sense,
! these are languages other than GNU Fortran--though its primary purpose
! is to support the GNU Fortran language, which also is described in its
! documentation and by its implementation.
! 
!    On the other hand, non-GNU compilers might offer support for the GNU
! Fortran language, and are encouraged to do so.
! 
!    Currently, the GNU Fortran language is a fairly fuzzy object.  It
! represents something of a cross between what `g77' accepts when
! compiling using the prevailing defaults and what this document
! describes as being part of the language.
! 
!    Future versions of `g77' are expected to clarify the definition of
! the language in the documentation.  Often, this will mean adding new
! features to the language, in the form of both new documentation and new
! support in `g77'.  However, it might occasionally mean removing a
! feature from the language itself to "dialect" status.  In such a case,
! the documentation would be adjusted to reflect the change, and `g77'
! itself would likely be changed to require one or more command-line
! options to continue supporting the feature.
! 
!    The development of the GNU Fortran language is intended to strike a
! balance between:
! 
!    * Serving as a mostly-upwards-compatible language from the de facto
!      UNIX Fortran dialect as supported by `f77'.
! 
!    * Offering new, well-designed language features.  Attributes of such
!      features include not making existing code any harder to read (for
!      those who might be unaware that the new features are not in use)
!      and not making state-of-the-art compilers take longer to issue
!      diagnostics, among others.
! 
!    * Supporting existing, well-written code without gratuitously
!      rejecting non-standard constructs, regardless of the origin of the
!      code (its dialect).
! 
!    * Offering default behavior and command-line options to reduce and,
!      where reasonable, eliminate the need for programmers to make any
!      modifications to code that already works in existing production
!      environments.
! 
!    * Diagnosing constructs that have different meanings in different
!      systems, languages, and dialects, while offering clear, less
!      ambiguous ways to express each of the different meanings so
!      programmers can change their code appropriately.
! 
!    One of the biggest practical challenges for the developers of the
! GNU Fortran language is meeting the sometimes contradictory demands of
! the above items.
! 
!    For example, a feature might be widely used in one popular
! environment, but the exact same code that utilizes that feature might
! not work as expected--perhaps it might mean something entirely
! different--in another popular environment.
! 
!    Traditionally, Fortran compilers--even portable ones--have solved
! this problem by simply offering the appropriate feature to users of the
! respective systems.  This approach treats users of various Fortran
! systems and dialects as remote "islands", or camps, of programmers, and
! assume that these camps rarely come into contact with each other (or,
! especially, with each other's code).
! 
!    Project GNU takes a radically different approach to software and
! language design, in that it assumes that users of GNU software do not
! necessarily care what kind of underlying system they are using,
! regardless of whether they are using software (at the user-interface
! level) or writing it (for example, writing Fortran or C code).
! 
!    As such, GNU users rarely need consider just what kind of underlying
! hardware (or, in many cases, operating system) they are using at any
! particular time.  They can use and write software designed for a
! general-purpose, widely portable, heterogeneous environment--the GNU
! environment.
! 
!    In line with this philosophy, GNU Fortran must evolve into a product
! that is widely ported and portable not only in the sense that it can be
! successfully built, installed, and run by users, but in the larger
! sense that its users can use it in the same way, and expect largely the
! same behaviors from it, regardless of the kind of system they are using
! at any particular time.
! 
!    This approach constrains the solutions `g77' can use to resolve
! conflicts between various camps of Fortran users.  If these two camps
! disagree about what a particular construct should mean, `g77' cannot
! simply be changed to treat that particular construct as having one
! meaning without comment (such as a warning), lest the users expecting
! it to have the other meaning are unpleasantly surprised that their code
! misbehaves when executed.
! 
!    The use of the ASCII backslash character in character constants is
! an excellent (and still somewhat unresolved) example of this kind of
! controversy.  *Note Backslash in Constants::.  Other examples are
! likely to arise in the future, as `g77' developers strive to improve
! its ability to accept an ever-wider variety of existing Fortran code
! without requiring significant modifications to said code.
! 
!    Development of GNU Fortran is further constrained by the desire to
! avoid requiring programmers to change their code.  This is important
! because it allows programmers, administrators, and others to more
! faithfully evaluate and validate `g77' (as an overall product and as
! new versions are distributed) without having to support multiple
! versions of their programs so that they continue to work the same way
! on their existing systems (non-GNU perhaps, but possibly also earlier
! versions of `g77').
! 
! 
! File: g77.info,  Node: Standard Support,  Next: Conformance,  Prev: Direction of Language Development,  Up: Language
! 
! ANSI FORTRAN 77 Standard Support
! ================================
! 
!    GNU Fortran supports ANSI FORTRAN 77 with the following caveats.  In
! summary, the only ANSI FORTRAN 77 features `g77' doesn't support are
! those that are probably rarely used in actual code, some of which are
! explicitly disallowed by the Fortran 90 standard.
! 
! * Menu:
! 
! * No Passing External Assumed-length::  CHAR*(*) CFUNC restriction.
! * No Passing Dummy Assumed-length::     CHAR*(*) CFUNC restriction.
! * No Pathological Implied-DO::          No `((..., I=...), I=...)'.
! * No Useless Implied-DO::               No `(A, I=1, 1)'.
! 
! 
! File: g77.info,  Node: No Passing External Assumed-length,  Next: No Passing Dummy Assumed-length,  Up: Standard Support
! 
! No Passing External Assumed-length
! ----------------------------------
! 
!    `g77' disallows passing of an external procedure as an actual
! argument if the procedure's type is declared `CHARACTER*(*)'.  For
! example:
! 
!      CHARACTER*(*) CFUNC
!      EXTERNAL CFUNC
!      CALL FOO(CFUNC)
!      END
! 
! It isn't clear whether the standard considers this conforming.
! 
! 
! File: g77.info,  Node: No Passing Dummy Assumed-length,  Next: No Pathological Implied-DO,  Prev: No Passing External Assumed-length,  Up: Standard Support
! 
! No Passing Dummy Assumed-length
! -------------------------------
! 
!    `g77' disallows passing of a dummy procedure as an actual argument
! if the procedure's type is declared `CHARACTER*(*)'.
! 
!      SUBROUTINE BAR(CFUNC)
!      CHARACTER*(*) CFUNC
!      EXTERNAL CFUNC
!      CALL FOO(CFUNC)
!      END
! 
! It isn't clear whether the standard considers this conforming.
! 
! 
! File: g77.info,  Node: No Pathological Implied-DO,  Next: No Useless Implied-DO,  Prev: No Passing Dummy Assumed-length,  Up: Standard Support
! 
! No Pathological Implied-DO
! --------------------------
! 
!    The `DO' variable for an implied-`DO' construct in a `DATA'
! statement may not be used as the `DO' variable for an outer
! implied-`DO' construct.  For example, this fragment is disallowed by
! `g77':
! 
!      DATA ((A(I, I), I= 1, 10), I= 1, 10) /.../
! 
! This also is disallowed by Fortran 90, as it offers no additional
! capabilities and would have a variety of possible meanings.
! 
!    Note that it is _very_ unlikely that any production Fortran code
! tries to use this unsupported construct.
! 
! 
! File: g77.info,  Node: No Useless Implied-DO,  Prev: No Pathological Implied-DO,  Up: Standard Support
! 
! No Useless Implied-DO
! ---------------------
! 
!    An array element initializer in an implied-`DO' construct in a
! `DATA' statement must contain at least one reference to the `DO'
! variables of each outer implied-`DO' construct.  For example, this
! fragment is disallowed by `g77':
! 
!      DATA (A, I= 1, 1) /1./
! 
! This also is disallowed by Fortran 90, as FORTRAN 77's more permissive
! requirements offer no additional capabilities.  However, `g77' doesn't
! necessarily diagnose all cases where this requirement is not met.
! 
!    Note that it is _very_ unlikely that any production Fortran code
! tries to use this unsupported construct.
! 
! 
! File: g77.info,  Node: Conformance,  Next: Notation Used,  Prev: Standard Support,  Up: Language
! 
! Conformance
! ===========
! 
!    (The following information augments or overrides the information in
! Section 1.4 of ANSI X3.9-1978 FORTRAN 77 in specifying the GNU Fortran
! language.  Chapter 1 of that document otherwise serves as the basis for
! the relevant aspects of GNU Fortran.)
! 
!    The definition of the GNU Fortran language is akin to that of the
! ANSI FORTRAN 77 language in that it does not generally require
! conforming implementations to diagnose cases where programs do not
! conform to the language.
! 
!    However, `g77' as a compiler is being developed in a way that is
! intended to enable it to diagnose such cases in an easy-to-understand
! manner.
! 
!    A program that conforms to the GNU Fortran language should, when
! compiled, linked, and executed using a properly installed `g77' system,
! perform as described by the GNU Fortran language definition.  Reasons
! for different behavior include, among others:
! 
!    * Use of resources (memory--heap, stack, and so on; disk space; CPU
!      time; etc.) exceeds those of the system.
! 
!    * Range and/or precision of calculations required by the program
!      exceeds that of the system.
! 
!    * Excessive reliance on behaviors that are system-dependent
!      (non-portable Fortran code).
! 
!    * Bugs in the program.
! 
!    * Bug in `g77'.
! 
!    * Bugs in the system.
! 
!    Despite these "loopholes", the availability of a clear specification
! of the language of programs submitted to `g77', as this document is
! intended to provide, is considered an important aspect of providing a
! robust, clean, predictable Fortran implementation.
! 
!    The definition of the GNU Fortran language, while having no special
! legal status, can therefore be viewed as a sort of contract, or
! agreement.  This agreement says, in essence, "if you write a program in
! this language, and run it in an environment (such as a `g77' system)
! that supports this language, the program should behave in a largely
! predictable way".
! 
! 
! File: g77.info,  Node: Notation Used,  Next: Terms and Concepts,  Prev: Conformance,  Up: Language
! 
! Notation Used in This Chapter
! =============================
! 
!    (The following information augments or overrides the information in
! Section 1.5 of ANSI X3.9-1978 FORTRAN 77 in specifying the GNU Fortran
! language.  Chapter 1 of that document otherwise serves as the basis for
! the relevant aspects of GNU Fortran.)
! 
!    In this chapter, "must" denotes a requirement, "may" denotes
! permission, and "must not" and "may not" denote prohibition.  Terms
! such as "might", "should", and "can" generally add little or nothing in
! the way of weight to the GNU Fortran language itself, but are used to
! explain or illustrate the language.
! 
!    For example:
! 
!      ``The `FROBNITZ' statement must precede all executable
!      statements in a program unit, and may not specify any dummy
!      arguments.  It may specify local or common variables and arrays.
!      Its use should be limited to portions of the program designed to
!      be non-portable and system-specific, because it might cause the
!      containing program unit to behave quite differently on different
!      systems.''
! 
!    Insofar as the GNU Fortran language is specified, the requirements
! and permissions denoted by the above sample statement are limited to
! the placement of the statement and the kinds of things it may specify.
! The rest of the statement--the content regarding non-portable portions
! of the program and the differing behavior of program units containing
! the `FROBNITZ' statement--does not pertain the GNU Fortran language
! itself.  That content offers advice and warnings about the `FROBNITZ'
! statement.
! 
!    _Remember:_ The GNU Fortran language definition specifies both what
! constitutes a valid GNU Fortran program and how, given such a program,
! a valid GNU Fortran implementation is to interpret that program.
! 
!    It is _not_ incumbent upon a valid GNU Fortran implementation to
! behave in any particular way, any consistent way, or any predictable
! way when it is asked to interpret input that is _not_ a valid GNU
! Fortran program.
! 
!    Such input is said to have "undefined" behavior when interpreted by
! a valid GNU Fortran implementation, though an implementation may choose
! to specify behaviors for some cases of inputs that are not valid GNU
! Fortran programs.
! 
!    Other notation used herein is that of the GNU texinfo format, which
! is used to generate printed hardcopy, on-line hypertext (Info), and
! on-line HTML versions, all from a single source document.  This
! notation is used as follows:
! 
!    * Keywords defined by the GNU Fortran language are shown in
!      uppercase, as in: `COMMON', `INTEGER', and `BLOCK DATA'.
! 
!      Note that, in practice, many Fortran programs are written in
!      lowercase--uppercase is used in this manual as a means to readily
!      distinguish keywords and sample Fortran-related text from the
!      prose in this document.
! 
!    * Portions of actual sample program, input, or output text look like
!      this: `Actual program text'.
! 
!      Generally, uppercase is used for all Fortran-specific and
!      Fortran-related text, though this does not always include literal
!      text within Fortran code.
! 
!      For example: `PRINT *, 'My name is Bob''.
! 
!    * A metasyntactic variable--that is, a name used in this document to
!      serve as a placeholder for whatever text is used by the user or
!      programmer--appears as shown in the following example:
! 
!      "The `INTEGER IVAR' statement specifies that IVAR is a variable or
!      array of type `INTEGER'."
! 
!      In the above example, any valid text may be substituted for the
!      metasyntactic variable IVAR to make the statement apply to a
!      specific instance, as long as the same text is substituted for
!      _both_ occurrences of IVAR.
! 
!    * Ellipses ("...") are used to indicate further text that is either
!      unimportant or expanded upon further, elsewhere.
! 
!    * Names of data types are in the style of Fortran 90, in most cases.
! 
!      *Note Kind Notation::, for information on the relationship between
!      Fortran 90 nomenclature (such as `INTEGER(KIND=1)') and the more
!      traditional, less portably concise nomenclature (such as
!      `INTEGER*4').
! 
! 
! File: g77.info,  Node: Terms and Concepts,  Next: Characters Lines Sequence,  Prev: Notation Used,  Up: Language
! 
! Fortran Terms and Concepts
! ==========================
! 
!    (The following information augments or overrides the information in
! Chapter 2 of ANSI X3.9-1978 FORTRAN 77 in specifying the GNU Fortran
! language.  Chapter 2 of that document otherwise serves as the basis for
! the relevant aspects of GNU Fortran.)
! 
! * Menu:
! 
! * Syntactic Items::
! * Statements Comments Lines::
! * Scope of Names and Labels::
! 
! 
! File: g77.info,  Node: Syntactic Items,  Next: Statements Comments Lines,  Up: Terms and Concepts
! 
! Syntactic Items
! ---------------
! 
!    (Corresponds to Section 2.2 of ANSI X3.9-1978 FORTRAN 77.)
! 
!    In GNU Fortran, a symbolic name is at least one character long, and
! has no arbitrary upper limit on length.  However, names of entities
! requiring external linkage (such as external functions, external
! subroutines, and `COMMON' areas) might be restricted to some arbitrary
! length by the system.  Such a restriction is no more constrained than
! that of one through six characters.
! 
!    Underscores (`_') are accepted in symbol names after the first
! character (which must be a letter).
! 
! 
! File: g77.info,  Node: Statements Comments Lines,  Next: Scope of Names and Labels,  Prev: Syntactic Items,  Up: Terms and Concepts
! 
! Statements, Comments, and Lines
! -------------------------------
! 
!    (Corresponds to Section 2.3 of ANSI X3.9-1978 FORTRAN 77.)
! 
!    Use of an exclamation point (`!') to begin a trailing comment (a
! comment that extends to the end of the same source line) is permitted
! under the following conditions:
! 
!    * The exclamation point does not appear in column 6.  Otherwise, it
!      is treated as an indicator of a continuation line.
! 
!    * The exclamation point appears outside a character or Hollerith
!      constant.  Otherwise, the exclamation point is considered part of
!      the constant.
! 
!    * The exclamation point appears to the left of any other possible
!      trailing comment.  That is, a trailing comment may contain
!      exclamation points in their commentary text.
! 
!    Use of a semicolon (`;') as a statement separator is permitted under
! the following conditions:
! 
!    * The semicolon appears outside a character or Hollerith constant.
!      Otherwise, the semicolon is considered part of the constant.
! 
!    * The semicolon appears to the left of a trailing comment.
!      Otherwise, the semicolon is considered part of that comment.
! 
!    * Neither a logical `IF' statement nor a non-construct `WHERE'
!      statement (a Fortran 90 feature) may be followed (in the same,
!      possibly continued, line) by a semicolon used as a statement
!      separator.
! 
!      This restriction avoids the confusion that can result when reading
!      a line such as:
! 
!           IF (VALIDP) CALL FOO; CALL BAR
! 
!      Some readers might think the `CALL BAR' is executed only if
!      `VALIDP' is `.TRUE.', while others might assume its execution is
!      unconditional.
! 
!      (At present, `g77' does not diagnose code that violates this
!      restriction.)
! 
! 
! File: g77.info,  Node: Scope of Names and Labels,  Prev: Statements Comments Lines,  Up: Terms and Concepts
! 
! Scope of Symbolic Names and Statement Labels
! --------------------------------------------
! 
!    (Corresponds to Section 2.9 of ANSI X3.9-1978 FORTRAN 77.)
! 
!    Included in the list of entities that have a scope of a program unit
! are construct names (a Fortran 90 feature).  *Note Construct Names::,
! for more information.
! 
! 
! File: g77.info,  Node: Characters Lines Sequence,  Next: Data Types and Constants,  Prev: Terms and Concepts,  Up: Language
! 
! Characters, Lines, and Execution Sequence
! =========================================
! 
!    (The following information augments or overrides the information in
! Chapter 3 of ANSI X3.9-1978 FORTRAN 77 in specifying the GNU Fortran
! language.  Chapter 3 of that document otherwise serves as the basis for
! the relevant aspects of GNU Fortran.)
! 
! * Menu:
! 
! * Character Set::
! * Lines::
! * Continuation Line::
! * Statements::
! * Statement Labels::
! * Order::
! * INCLUDE::
! * Cpp-style directives::
! 
! 
! File: g77.info,  Node: Character Set,  Next: Lines,  Up: Characters Lines Sequence
! 
! GNU Fortran Character Set
! -------------------------
! 
!    (Corresponds to Section 3.1 of ANSI X3.9-1978 FORTRAN 77.)
! 
!    Letters include uppercase letters (the twenty-six characters of the
! English alphabet) and lowercase letters (their lowercase equivalent).
! Generally, lowercase letters may be used in place of uppercase letters,
! though in character and Hollerith constants, they are distinct.
! 
!    Special characters include:
! 
!    * Semicolon (`;')
! 
!    * Exclamation point (`!')
! 
!    * Double quote (`"')
! 
!    * Backslash (`\')
! 
!    * Question mark (`?')
! 
!    * Hash mark (`#')
! 
!    * Ampersand (`&')
! 
!    * Percent sign (`%')
! 
!    * Underscore (`_')
! 
!    * Open angle (`<')
! 
!    * Close angle (`>')
! 
!    * The FORTRAN 77 special characters (<SPC>, `=', `+', `-', `*', `/',
!      `(', `)', `,', `.', `$', `'', and `:')
! 
!    Note that this document refers to <SPC> as "space", while X3.9-1978
! FORTRAN 77 refers to it as "blank".
! 
! 
! File: g77.info,  Node: Lines,  Next: Continuation Line,  Prev: Character Set,  Up: Characters Lines Sequence
! 
! Lines
! -----
! 
!    (Corresponds to Section 3.2 of ANSI X3.9-1978 FORTRAN 77.)
! 
!    The way a Fortran compiler views source files depends entirely on the
! implementation choices made for the compiler, since those choices are
! explicitly left to the implementation by the published Fortran
! standards.
! 
!    The GNU Fortran language mandates a view applicable to UNIX-like
! text files--files that are made up of an arbitrary number of lines,
! each with an arbitrary number of characters (sometimes called
! stream-based files).
! 
!    This view does not apply to types of files that are specified as
! having a particular number of characters on every single line (sometimes
! referred to as record-based files).
! 
!    Because a "line in a program unit is a sequence of 72 characters",
! to quote X3.9-1978, the GNU Fortran language specifies that a
! stream-based text file is translated to GNU Fortran lines as follows:
! 
!    * A newline in the file is the character that represents the end of
!      a line of text to the underlying system.  For example, on
!      ASCII-based systems, a newline is the <NL> character, which has
!      ASCII value 10 (decimal).
! 
!    * Each newline in the file serves to end the line of text that
!      precedes it (and that does not contain a newline).
! 
!    * The end-of-file marker (`EOF') also serves to end the line of text
!      that precedes it (and that does not contain a newline).
! 
!    * Any line of text that is shorter than 72 characters is padded to
!      that length with spaces (called "blanks" in the standard).
! 
!    * Any line of text that is longer than 72 characters is truncated to
!      that length, but the truncated remainder must consist entirely of
!      spaces.
! 
!    * Characters other than newline and the GNU Fortran character set
!      are invalid.
! 
!    For the purposes of the remainder of this description of the GNU
! Fortran language, the translation described above has already taken
! place, unless otherwise specified.
! 
!    The result of the above translation is that the source file appears,
! in terms of the remainder of this description of the GNU Fortran
! language, as if it had an arbitrary number of 72-character lines, each
! character being among the GNU Fortran character set.
! 
!    For example, if the source file itself has two newlines in a row,
! the second newline becomes, after the above translation, a single line
! containing 72 spaces.
! 
! 
! File: g77.info,  Node: Continuation Line,  Next: Statements,  Prev: Lines,  Up: Characters Lines Sequence
! 
! Continuation Line
! -----------------
! 
!    (Corresponds to Section 3.2.3 of ANSI X3.9-1978 FORTRAN 77.)
! 
!    A continuation line is any line that both
! 
!    * Contains a continuation character, and
! 
!    * Contains only spaces in columns 1 through 5
! 
!    A continuation character is any character of the GNU Fortran
! character set other than space (<SPC>) or zero (`0') in column 6, or a
! digit (`0' through `9') in column 7 through 72 of a line that has only
! spaces to the left of that digit.
! 
!    The continuation character is ignored as far as the content of the
! statement is concerned.
! 
!    The GNU Fortran language places no limit on the number of
! continuation lines in a statement.  In practice, the limit depends on a
! variety of factors, such as available memory, statement content, and so
! on, but no GNU Fortran system may impose an arbitrary limit.
! 
! 
! File: g77.info,  Node: Statements,  Next: Statement Labels,  Prev: Continuation Line,  Up: Characters Lines Sequence
! 
! Statements
! ----------
! 
!    (Corresponds to Section 3.3 of ANSI X3.9-1978 FORTRAN 77.)
! 
!    Statements may be written using an arbitrary number of continuation
! lines.
! 
!    Statements may be separated using the semicolon (`;'), except that
! the logical `IF' and non-construct `WHERE' statements may not be
! separated from subsequent statements using only a semicolon as
! statement separator.
! 
!    The `END PROGRAM', `END SUBROUTINE', `END FUNCTION', and `END BLOCK
! DATA' statements are alternatives to the `END' statement.  These
! alternatives may be written as normal statements--they are not subject
! to the restrictions of the `END' statement.
! 
!    However, no statement other than `END' may have an initial line that
! appears to be an `END' statement--even `END PROGRAM', for example, must
! not be written as:
! 
!            END
!           &PROGRAM
! 
! 
! File: g77.info,  Node: Statement Labels,  Next: Order,  Prev: Statements,  Up: Characters Lines Sequence
! 
! Statement Labels
! ----------------
! 
!    (Corresponds to Section 3.4 of ANSI X3.9-1978 FORTRAN 77.)
! 
!    A statement separated from its predecessor via a semicolon may be
! labeled as follows:
! 
!    * The semicolon is followed by the label for the statement, which in
!      turn follows the label.
! 
!    * The label must be no more than five digits in length.
! 
!    * The first digit of the label for the statement is not the first
!      non-space character on a line.  Otherwise, that character is
!      treated as a continuation character.
! 
!    A statement may have only one label defined for it.
! 
! 
! File: g77.info,  Node: Order,  Next: INCLUDE,  Prev: Statement Labels,  Up: Characters Lines Sequence
! 
! Order of Statements and Lines
! -----------------------------
! 
!    (Corresponds to Section 3.5 of ANSI X3.9-1978 FORTRAN 77.)
! 
!    Generally, `DATA' statements may precede executable statements.
! However, specification statements pertaining to any entities
! initialized by a `DATA' statement must precede that `DATA' statement.
! For example, after `DATA I/1/', `INTEGER I' is not permitted, but
! `INTEGER J' is permitted.
! 
!    The last line of a program unit may be an `END' statement, or may be:
! 
!    * An `END PROGRAM' statement, if the program unit is a main program.
! 
!    * An `END SUBROUTINE' statement, if the program unit is a subroutine.
! 
!    * An `END FUNCTION' statement, if the program unit is a function.
! 
!    * An `END BLOCK DATA' statement, if the program unit is a block data.
! 
! 
! File: g77.info,  Node: INCLUDE,  Next: Cpp-style directives,  Prev: Order,  Up: Characters Lines Sequence
! 
! Including Source Text
! ---------------------
! 
!    Additional source text may be included in the processing of the
! source file via the `INCLUDE' directive:
! 
!      INCLUDE FILENAME
! 
! The source text to be included is identified by FILENAME, which is a
! literal GNU Fortran character constant.  The meaning and interpretation
! of FILENAME depends on the implementation, but typically is a filename.
! 
!    (`g77' treats it as a filename that it searches for in the current
! directory and/or directories specified via the `-I' command-line
! option.)
! 
!    The effect of the `INCLUDE' directive is as if the included text
! directly replaced the directive in the source file prior to
! interpretation of the program.  Included text may itself use `INCLUDE'.
! The depth of nested `INCLUDE' references depends on the implementation,
! but typically is a positive integer.
! 
!    This virtual replacement treats the statements and `INCLUDE'
! directives in the included text as syntactically distinct from those in
! the including text.
! 
!    Therefore, the first non-comment line of the included text must not
! be a continuation line.  The included text must therefore have, after
! the non-comment lines, either an initial line (statement), an `INCLUDE'
! directive, or nothing (the end of the included text).
! 
!    Similarly, the including text may end the `INCLUDE' directive with a
! semicolon or the end of the line, but it cannot follow an `INCLUDE'
! directive at the end of its line with a continuation line.  Thus, the
! last statement in an included text may not be continued.
! 
!    Any statements between two `INCLUDE' directives on the same line are
! treated as if they appeared in between the respective included texts.
! For example:
! 
!      INCLUDE 'A'; PRINT *, 'B'; INCLUDE 'C'; END PROGRAM
! 
! If the text included by `INCLUDE 'A'' constitutes a `PRINT *, 'A''
! statement and the text included by `INCLUDE 'C'' constitutes a `PRINT
! *, 'C'' statement, then the output of the above sample program would be
! 
!      A
!      B
!      C
! 
! (with suitable allowances for how an implementation defines its
! handling of output).
! 
!    Included text must not include itself directly or indirectly,
! regardless of whether the FILENAME used to reference the text is the
! same.
! 
!    Note that `INCLUDE' is _not_ a statement.  As such, it is neither a
! non-executable or executable statement.  However, if the text it
! includes constitutes one or more executable statements, then the
! placement of `INCLUDE' is subject to effectively the same restrictions
! as those on executable statements.
! 
!    An `INCLUDE' directive may be continued across multiple lines as if
! it were a statement.  This permits long names to be used for FILENAME.
! 
! 
! File: g77.info,  Node: Cpp-style directives,  Prev: INCLUDE,  Up: Characters Lines Sequence
! 
! Cpp-style directives
! --------------------
! 
!    `cpp' output-style `#' directives (*note C Preprocessor Output:
! (cpp)C Preprocessor Output.)  are recognized by the compiler even when
! the preprocessor isn't run on the input (as it is when compiling `.F'
! files).  (Note the distinction between these `cpp' `#' _output_
! directives and `#line' _input_ directives.)
! 
! 
! File: g77.info,  Node: Data Types and Constants,  Next: Expressions,  Prev: Characters Lines Sequence,  Up: Language
! 
! Data Types and Constants
! ========================
! 
!    (The following information augments or overrides the information in
! Chapter 4 of ANSI X3.9-1978 FORTRAN 77 in specifying the GNU Fortran
! language.  Chapter 4 of that document otherwise serves as the basis for
! the relevant aspects of GNU Fortran.)
! 
!    To more concisely express the appropriate types for entities, this
! document uses the more concise Fortran 90 nomenclature such as
! `INTEGER(KIND=1)' instead of the more traditional, but less portably
! concise, byte-size-based nomenclature such as `INTEGER*4', wherever
! reasonable.
! 
!    When referring to generic types--in contexts where the specific
! precision and range of a type are not important--this document uses the
! generic type names `INTEGER', `LOGICAL', `REAL', `COMPLEX', and
! `CHARACTER'.
! 
!    In some cases, the context requires specification of a particular
! type.  This document uses the `KIND=' notation to accomplish this
! throughout, sometimes supplying the more traditional notation for
! clarification, though the traditional notation might not work the same
! way on all GNU Fortran implementations.
! 
!    Use of `KIND=' makes this document more concise because `g77' is
! able to define values for `KIND=' that have the same meanings on all
! systems, due to the way the Fortran 90 standard specifies these values
! are to be used.
! 
!    (In particular, that standard permits an implementation to
! arbitrarily assign nonnegative values.  There are four distinct sets of
! assignments: one to the `CHARACTER' type; one to the `INTEGER' type;
! one to the `LOGICAL' type; and the fourth to both the `REAL' and
! `COMPLEX' types.  Implementations are free to assign these values in
! any order, leave gaps in the ordering of assignments, and assign more
! than one value to a representation.)
! 
!    This makes `KIND=' values superior to the values used in
! non-standard statements such as `INTEGER*4', because the meanings of
! the values in those statements vary from machine to machine, compiler
! to compiler, even operating system to operating system.
! 
!    However, use of `KIND=' is _not_ generally recommended when writing
! portable code (unless, for example, the code is going to be compiled
! only via `g77', which is a widely ported compiler).  GNU Fortran does
! not yet have adequate language constructs to permit use of `KIND=' in a
! fashion that would make the code portable to Fortran 90
! implementations; and, this construct is known to _not_ be accepted by
! many popular FORTRAN 77 implementations, so it cannot be used in code
! that is to be ported to those.
! 
!    The distinction here is that this document is able to use specific
! values for `KIND=' to concisely document the types of various
! operations and operands.
! 
!    A Fortran program should use the FORTRAN 77 designations for the
! appropriate GNU Fortran types--such as `INTEGER' for `INTEGER(KIND=1)',
! `REAL' for `REAL(KIND=1)', and `DOUBLE COMPLEX' for
! `COMPLEX(KIND=2)'--and, where no such designations exist, make use of
! appropriate techniques (preprocessor macros, parameters, and so on) to
! specify the types in a fashion that may be easily adjusted to suit each
! particular implementation to which the program is ported.  (These types
! generally won't need to be adjusted for ports of `g77'.)
! 
!    Further details regarding GNU Fortran data types and constants are
! provided below.
! 
! * Menu:
! 
! * Types::
! * Constants::
! * Integer Type::
! * Character Type::
! 
! 
! File: g77.info,  Node: Types,  Next: Constants,  Up: Data Types and Constants
! 
! Data Types
! ----------
! 
!    (Corresponds to Section 4.1 of ANSI X3.9-1978 FORTRAN 77.)
! 
!    GNU Fortran supports these types:
! 
!   1. Integer (generic type `INTEGER')
! 
!   2. Real (generic type `REAL')
! 
!   3. Double precision
! 
!   4. Complex (generic type `COMPLEX')
! 
!   5. Logical (generic type `LOGICAL')
! 
!   6. Character (generic type `CHARACTER')
! 
!   7. Double Complex
! 
!    (The types numbered 1 through 6 above are standard FORTRAN 77 types.)
! 
!    The generic types shown above are referred to in this document using
! only their generic type names.  Such references usually indicate that
! any specific type (kind) of that generic type is valid.
! 
!    For example, a context described in this document as accepting the
! `COMPLEX' type also is likely to accept the `DOUBLE COMPLEX' type.
! 
!    The GNU Fortran language supports three ways to specify a specific
! kind of a generic type.
! 
! * Menu:
! 
! * Double Notation::  As in `DOUBLE COMPLEX'.
! * Star Notation::    As in `INTEGER*4'.
! * Kind Notation::    As in `INTEGER(KIND=1)'.
! 
! 
! File: g77.info,  Node: Double Notation,  Next: Star Notation,  Up: Types
! 
! Double Notation
! ...............
! 
!    The GNU Fortran language supports two uses of the keyword `DOUBLE'
! to specify a specific kind of type:
! 
!    * `DOUBLE PRECISION', equivalent to `REAL(KIND=2)'
! 
!    * `DOUBLE COMPLEX', equivalent to `COMPLEX(KIND=2)'
! 
!    Use one of the above forms where a type name is valid.
! 
!    While use of this notation is popular, it doesn't scale well in a
! language or dialect rich in intrinsic types, as is the case for the GNU
! Fortran language (especially planned future versions of it).
! 
!    After all, one rarely sees type names such as `DOUBLE INTEGER',
! `QUADRUPLE REAL', or `QUARTER INTEGER'.  Instead, `INTEGER*8',
! `REAL*16', and `INTEGER*1' often are substituted for these,
! respectively, even though they do not always have the same meanings on
! all systems.  (And, the fact that `DOUBLE REAL' does not exist as such
! is an inconsistency.)
! 
!    Therefore, this document uses "double notation" only on occasion for
! the benefit of those readers who are accustomed to it.
! 
! 
! File: g77.info,  Node: Star Notation,  Next: Kind Notation,  Prev: Double Notation,  Up: Types
! 
! Star Notation
! .............
! 
!    The following notation specifies the storage size for a type:
! 
!      GENERIC-TYPE*N
! 
! GENERIC-TYPE must be a generic type--one of `INTEGER', `REAL',
! `COMPLEX', `LOGICAL', or `CHARACTER'.  N must be one or more digits
! comprising a decimal integer number greater than zero.
! 
!    Use the above form where a type name is valid.
! 
!    The `*N' notation specifies that the amount of storage occupied by
! variables and array elements of that type is N times the storage
! occupied by a `CHARACTER*1' variable.
! 
!    This notation might indicate a different degree of precision and/or
! range for such variables and array elements, and the functions that
! return values of types using this notation.  It does not limit the
! precision or range of values of that type in any particular way--use
! explicit code to do that.
! 
!    Further, the GNU Fortran language requires no particular values for
! N to be supported by an implementation via the `*N' notation.  `g77'
! supports `INTEGER*1' (as `INTEGER(KIND=3)') on all systems, for example,
! but not all implementations are required to do so, and `g77' is known
! to not support `REAL*1' on most (or all) systems.
! 
!    As a result, except for GENERIC-TYPE of `CHARACTER', uses of this
! notation should be limited to isolated portions of a program that are
! intended to handle system-specific tasks and are expected to be
! non-portable.
! 
!    (Standard FORTRAN 77 supports the `*N' notation for only
! `CHARACTER', where it signifies not only the amount of storage
! occupied, but the number of characters in entities of that type.
! However, almost all Fortran compilers have supported this notation for
! generic types, though with a variety of meanings for N.)
! 
!    Specifications of types using the `*N' notation always are
! interpreted as specifications of the appropriate types described in
! this document using the `KIND=N' notation, described below.
! 
!    While use of this notation is popular, it doesn't serve well in the
! context of a widely portable dialect of Fortran, such as the GNU
! Fortran language.
! 
!    For example, even on one particular machine, two or more popular
! Fortran compilers might well disagree on the size of a type declared
! `INTEGER*2' or `REAL*16'.  Certainly there is known to be disagreement
! over such things among Fortran compilers on _different_ systems.
! 
!    Further, this notation offers no elegant way to specify sizes that
! are not even multiples of the "byte size" typically designated by
! `INTEGER*1'.  Use of "absurd" values (such as `INTEGER*1000') would
! certainly be possible, but would perhaps be stretching the original
! intent of this notation beyond the breaking point in terms of
! widespread readability of documentation and code making use of it.
! 
!    Therefore, this document uses "star notation" only on occasion for
! the benefit of those readers who are accustomed to it.
! 
! 
! File: g77.info,  Node: Kind Notation,  Prev: Star Notation,  Up: Types
! 
! Kind Notation
! .............
! 
!    The following notation specifies the kind-type selector of a type:
! 
!      GENERIC-TYPE(KIND=N)
! 
! Use the above form where a type name is valid.
! 
!    GENERIC-TYPE must be a generic type--one of `INTEGER', `REAL',
! `COMPLEX', `LOGICAL', or `CHARACTER'.  N must be an integer
! initialization expression that is a positive, nonzero value.
! 
!    Programmers are discouraged from writing these values directly into
! their code.  Future versions of the GNU Fortran language will offer
! facilities that will make the writing of code portable to `g77' _and_
! Fortran 90 implementations simpler.
! 
!    However, writing code that ports to existing FORTRAN 77
! implementations depends on avoiding the `KIND=' construct.
! 
!    The `KIND=' construct is thus useful in the context of GNU Fortran
! for two reasons:
! 
!    * It provides a means to specify a type in a fashion that is
!      portable across all GNU Fortran implementations (though not other
!      FORTRAN 77 and Fortran 90 implementations).
! 
!    * It provides a sort of Rosetta stone for this document to use to
!      concisely describe the types of various operations and operands.
! 
!    The values of N in the GNU Fortran language are assigned using a
! scheme that:
! 
!    * Attempts to maximize the ability of readers of this document to
!      quickly familiarize themselves with assignments for popular types
! 
!    * Provides a unique value for each specific desired meaning
! 
!    * Provides a means to automatically assign new values so they have a
!      "natural" relationship to existing values, if appropriate, or, if
!      no such relationship exists, will not interfere with future values
!      assigned on the basis of such relationships
! 
!    * Avoids using values that are similar to values used in the
!      existing, popular `*N' notation, to prevent readers from expecting
!      that these implied correspondences work on all GNU Fortran
!      implementations
! 
!    The assignment system accomplishes this by assigning to each
! "fundamental meaning" of a specific type a unique prime number.
! Combinations of fundamental meanings--for example, a type that is two
! times the size of some other type--are assigned values of N that are
! the products of the values for those fundamental meanings.
! 
!    A prime value of N is never given more than one fundamental meaning,
! to avoid situations where some code or system cannot reasonably provide
! those meanings in the form of a single type.
! 
!    The values of N assigned so far are:
! 
! `KIND=0'
!      This value is reserved for future use.
! 
!      The planned future use is for this value to designate, explicitly,
!      context-sensitive kind-type selection.  For example, the
!      expression `1D0 * 0.1_0' would be equivalent to `1D0 * 0.1D0'.
! 
! `KIND=1'
!      This corresponds to the default types for `REAL', `INTEGER',
!      `LOGICAL', `COMPLEX', and `CHARACTER', as appropriate.
! 
!      These are the "default" types described in the Fortran 90 standard,
!      though that standard does not assign any particular `KIND=' value
!      to these types.
! 
!      (Typically, these are `REAL*4', `INTEGER*4', `LOGICAL*4', and
!      `COMPLEX*8'.)
! 
! `KIND=2'
!      This corresponds to types that occupy twice as much storage as the
!      default types.  `REAL(KIND=2)' is `DOUBLE PRECISION' (typically
!      `REAL*8'), `COMPLEX(KIND=2)' is `DOUBLE COMPLEX' (typically
!      `COMPLEX*16'),
! 
!      These are the "double precision" types described in the Fortran 90
!      standard, though that standard does not assign any particular
!      `KIND=' value to these types.
! 
!      N of 4 thus corresponds to types that occupy four times as much
!      storage as the default types, N of 8 to types that occupy eight
!      times as much storage, and so on.
! 
!      The `INTEGER(KIND=2)' and `LOGICAL(KIND=2)' types are not
!      necessarily supported by every GNU Fortran implementation.
! 
! `KIND=3'
!      This corresponds to types that occupy as much storage as the
!      default `CHARACTER' type, which is the same effective type as
!      `CHARACTER(KIND=1)' (making that type effectively the same as
!      `CHARACTER(KIND=3)').
! 
!      (Typically, these are `INTEGER*1' and `LOGICAL*1'.)
! 
!      N of 6 thus corresponds to types that occupy twice as much storage
!      as the N=3 types, N of 12 to types that occupy four times as much
!      storage, and so on.
! 
!      These are not necessarily supported by every GNU Fortran
!      implementation.
! 
! `KIND=5'
!      This corresponds to types that occupy half the storage as the
!      default (N=1) types.
! 
!      (Typically, these are `INTEGER*2' and `LOGICAL*2'.)
! 
!      N of 25 thus corresponds to types that occupy one-quarter as much
!      storage as the default types.
! 
!      These are not necessarily supported by every GNU Fortran
!      implementation.
! 
! `KIND=7'
!      This is valid only as `INTEGER(KIND=7)' and denotes the `INTEGER'
!      type that has the smallest storage size that holds a pointer on
!      the system.
! 
!      A pointer representable by this type is capable of uniquely
!      addressing a `CHARACTER*1' variable, array, array element, or
!      substring.
! 
!      (Typically this is equivalent to `INTEGER*4' or, on 64-bit
!      systems, `INTEGER*8'.  In a compatible C implementation, it
!      typically would be the same size and semantics of the C type `void
!      *'.)
! 
!    Note that these are _proposed_ correspondences and might change in
! future versions of `g77'--avoid writing code depending on them while
! `g77', and therefore the GNU Fortran language it defines, is in beta
! testing.
! 
!    Values not specified in the above list are reserved to future
! versions of the GNU Fortran language.
! 
!    Implementation-dependent meanings will be assigned new, unique prime
! numbers so as to not interfere with other implementation-dependent
! meanings, and offer the possibility of increasing the portability of
! code depending on such types by offering support for them in other GNU
! Fortran implementations.
! 
!    Other meanings that might be given unique values are:
! 
!    * Types that make use of only half their storage size for
!      representing precision and range.
! 
!      For example, some compilers offer options that cause `INTEGER'
!      types to occupy the amount of storage that would be needed for
!      `INTEGER(KIND=2)' types, but the range remains that of
!      `INTEGER(KIND=1)'.
! 
!    * The IEEE single floating-point type.
! 
!    * Types with a specific bit pattern (endianness), such as the
!      little-endian form of `INTEGER(KIND=1)'.  These could permit,
!      conceptually, use of portable code and implementations on data
!      files written by existing systems.
! 
!    Future _prime_ numbers should be given meanings in as incremental a
! fashion as possible, to allow for flexibility and expressiveness in
! combining types.
! 
!    For example, instead of defining a prime number for little-endian
! IEEE doubles, one prime number might be assigned the meaning
! "little-endian", another the meaning "IEEE double", and the value of N
! for a little-endian IEEE double would thus naturally be the product of
! those two respective assigned values.  (It could even be reasonable to
! have IEEE values result from the products of prime values denoting
! exponent and fraction sizes and meanings, hidden bit usage,
! availability and representations of special values such as subnormals,
! infinities, and Not-A-Numbers (NaNs), and so on.)
! 
!    This assignment mechanism, while not inherently required for future
! versions of the GNU Fortran language, is worth using because it could
! ease management of the "space" of supported types much easier in the
! long run.
! 
!    The above approach suggests a mechanism for specifying inheritance
! of intrinsic (built-in) types for an entire, widely portable product
! line.  It is certainly reasonable that, unlike programmers of other
! languages offering inheritance mechanisms that employ verbose names for
! classes and subclasses, along with graphical browsers to elucidate the
! relationships, Fortran programmers would employ a mechanism that works
! by multiplying prime numbers together and finding the prime factors of
! such products.
! 
!    Most of the advantages for the above scheme have been explained
! above.  One disadvantage is that it could lead to the defining, by the
! GNU Fortran language, of some fairly large prime numbers.  This could
! lead to the GNU Fortran language being declared "munitions" by the
! United States Department of Defense.
! 
! 
! File: g77.info,  Node: Constants,  Next: Integer Type,  Prev: Types,  Up: Data Types and Constants
! 
! Constants
! ---------
! 
!    (Corresponds to Section 4.2 of ANSI X3.9-1978 FORTRAN 77.)
! 
!    A "typeless constant" has one of the following forms:
! 
!      'BINARY-DIGITS'B
!      'OCTAL-DIGITS'O
!      'HEXADECIMAL-DIGITS'Z
!      'HEXADECIMAL-DIGITS'X
! 
! BINARY-DIGITS, OCTAL-DIGITS, and HEXADECIMAL-DIGITS are nonempty
! strings of characters in the set `01', `01234567', and
! `0123456789ABCDEFabcdef', respectively.  (The value for `A' (and `a')
! is 10, for `B' and `b' is 11, and so on.)
! 
!    A prefix-radix constant, such as `Z'ABCD'', can optionally be
! treated as typeless.  *Note Options Controlling Fortran Dialect:
! Fortran Dialect Options, for information on the `-ftypeless-boz' option.
! 
!    Typeless constants have values that depend on the context in which
! they are used.
! 
!    All other constants, called "typed constants", are
! interpreted--converted to internal form--according to their inherent
! type.  Thus, context is _never_ a determining factor for the type, and
! hence the interpretation, of a typed constant.  (All constants in the
! ANSI FORTRAN 77 language are typed constants.)
! 
!    For example, `1' is always type `INTEGER(KIND=1)' in GNU Fortran
! (called default INTEGER in Fortran 90), `9.435784839284958' is always
! type `REAL(KIND=1)' (even if the additional precision specified is
! lost, and even when used in a `REAL(KIND=2)' context), `1E0' is always
! type `REAL(KIND=2)', and `1D0' is always type `REAL(KIND=2)'.
! 
! 
! File: g77.info,  Node: Integer Type,  Next: Character Type,  Prev: Constants,  Up: Data Types and Constants
! 
! Integer Type
! ------------
! 
!    (Corresponds to Section 4.3 of ANSI X3.9-1978 FORTRAN 77.)
! 
!    An integer constant also may have one of the following forms:
! 
!      B'BINARY-DIGITS'
!      O'OCTAL-DIGITS'
!      Z'HEXADECIMAL-DIGITS'
!      X'HEXADECIMAL-DIGITS'
! 
! BINARY-DIGITS, OCTAL-DIGITS, and HEXADECIMAL-DIGITS are nonempty
! strings of characters in the set `01', `01234567', and
! `0123456789ABCDEFabcdef', respectively.  (The value for `A' (and `a')
! is 10, for `B' and `b' is 11, and so on.)
! 
! 
! File: g77.info,  Node: Character Type,  Prev: Integer Type,  Up: Data Types and Constants
! 
! Character Type
! --------------
! 
!    (Corresponds to Section 4.8 of ANSI X3.9-1978 FORTRAN 77.)
! 
!    A character constant may be delimited by a pair of double quotes
! (`"') instead of apostrophes.  In this case, an apostrophe within the
! constant represents a single apostrophe, while a double quote is
! represented in the source text of the constant by two consecutive double
! quotes with no intervening spaces.
! 
!    A character constant may be empty (have a length of zero).
! 
!    A character constant may include a substring specification, The
! value of such a constant is the value of the substring--for example,
! the value of `'hello'(3:5)' is the same as the value of `'llo''.
! 
! 
! File: g77.info,  Node: Expressions,  Next: Specification Statements,  Prev: Data Types and Constants,  Up: Language
! 
! Expressions
! ===========
! 
!    (The following information augments or overrides the information in
! Chapter 6 of ANSI X3.9-1978 FORTRAN 77 in specifying the GNU Fortran
! language.  Chapter 6 of that document otherwise serves as the basis for
! the relevant aspects of GNU Fortran.)
! 
! * Menu:
! 
! * %LOC()::
! 
! 
! File: g77.info,  Node: %LOC(),  Up: Expressions
! 
! The `%LOC()' Construct
! ----------------------
! 
!      %LOC(ARG)
! 
!    The `%LOC()' construct is an expression that yields the value of the
! location of its argument, ARG, in memory.  The size of the type of the
! expression depends on the system--typically, it is equivalent to either
! `INTEGER(KIND=1)' or `INTEGER(KIND=2)', though it is actually type
! `INTEGER(KIND=7)'.
! 
!    The argument to `%LOC()' must be suitable as the left-hand side of
! an assignment statement.  That is, it may not be a general expression
! involving operators such as addition, subtraction, and so on, nor may
! it be a constant.
! 
!    Use of `%LOC()' is recommended only for code that is accessing
! facilities outside of GNU Fortran, such as operating system or
! windowing facilities.  It is best to constrain such uses to isolated
! portions of a program--portions that deal specifically and exclusively
! with low-level, system-dependent facilities.  Such portions might well
! provide a portable interface for use by the program as a whole, but are
! themselves not portable, and should be thoroughly tested each time they
! are rebuilt using a new compiler or version of a compiler.
! 
!    Do not depend on `%LOC()' returning a pointer that can be safely
! used to _define_ (change) the argument.  While this might work in some
! circumstances, it is hard to predict whether it will continue to work
! when a program (that works using this unsafe behavior) is recompiled
! using different command-line options or a different version of `g77'.
! 
!    Generally, `%LOC()' is safe when used as an argument to a procedure
! that makes use of the value of the corresponding dummy argument only
! during its activation, and only when such use is restricted to
! referencing (reading) the value of the argument to `%LOC()'.
! 
!    _Implementation Note:_ Currently, `g77' passes arguments (those not
! passed using a construct such as `%VAL()') by reference or descriptor,
! depending on the type of the actual argument.  Thus, given `INTEGER I',
! `CALL FOO(I)' would seem to mean the same thing as `CALL
! FOO(%VAL(%LOC(I)))', and in fact might compile to identical code.
! 
!    However, `CALL FOO(%VAL(%LOC(I)))' emphatically means "pass, by
! value, the address of `I' in memory".  While `CALL FOO(I)' might use
! that same approach in a particular version of `g77', another version or
! compiler might choose a different implementation, such as
! copy-in/copy-out, to effect the desired behavior--and which will
! therefore not necessarily compile to the same code as would `CALL
! FOO(%VAL(%LOC(I)))' using the same version or compiler.
! 
!    *Note Debugging and Interfacing::, for detailed information on how
! this particular version of `g77' implements various constructs.
! 
! 
! File: g77.info,  Node: Specification Statements,  Next: Control Statements,  Prev: Expressions,  Up: Language
! 
! Specification Statements
! ========================
! 
!    (The following information augments or overrides the information in
! Chapter 8 of ANSI X3.9-1978 FORTRAN 77 in specifying the GNU Fortran
! language.  Chapter 8 of that document otherwise serves as the basis for
! the relevant aspects of GNU Fortran.)
! 
! * Menu:
! 
! * NAMELIST::
! * DOUBLE COMPLEX::
! 
! 
! File: g77.info,  Node: NAMELIST,  Next: DOUBLE COMPLEX,  Up: Specification Statements
! 
! `NAMELIST' Statement
! --------------------
! 
!    The `NAMELIST' statement, and related I/O constructs, are supported
! by the GNU Fortran language in essentially the same way as they are by
! `f2c'.
! 
!    This follows Fortran 90 with the restriction that on `NAMELIST'
! input, subscripts must have the form
!      SUBSCRIPT [ `:' SUBSCRIPT [ `:' STRIDE]]
!    i.e.
!      &xx x(1:3,8:10:2)=1,2,3,4,5,6/
!    is allowed, but not, say,
!      &xx x(:3,8::2)=1,2,3,4,5,6/
! 
!    As an extension of the Fortran 90 form, `$' and `$END' may be used
! in place of `&' and `/' in `NAMELIST' input, so that
!      $&xx x(1:3,8:10:2)=1,2,3,4,5,6 $end
!    could be used instead of the example above.
! 
! 
! File: g77.info,  Node: DOUBLE COMPLEX,  Prev: NAMELIST,  Up: Specification Statements
! 
! `DOUBLE COMPLEX' Statement
! --------------------------
! 
!    `DOUBLE COMPLEX' is a type-statement (and type) that specifies the
! type `COMPLEX(KIND=2)' in GNU Fortran.
! 
! 
! File: g77.info,  Node: Control Statements,  Next: Functions and Subroutines,  Prev: Specification Statements,  Up: Language
! 
! Control Statements
! ==================
! 
!    (The following information augments or overrides the information in
! Chapter 11 of ANSI X3.9-1978 FORTRAN 77 in specifying the GNU Fortran
! language.  Chapter 11 of that document otherwise serves as the basis
! for the relevant aspects of GNU Fortran.)
! 
! * Menu:
! 
! * DO WHILE::
! * END DO::
! * Construct Names::
! * CYCLE and EXIT::
! 
! 
! File: g77.info,  Node: DO WHILE,  Next: END DO,  Up: Control Statements
! 
! DO WHILE
! --------
! 
!    The `DO WHILE' statement, a feature of both the MIL-STD 1753 and
! Fortran 90 standards, is provided by the GNU Fortran language.  The
! Fortran 90 "do forever" statement comprising just `DO' is also
! supported.
! 
! 
! File: g77.info,  Node: END DO,  Next: Construct Names,  Prev: DO WHILE,  Up: Control Statements
! 
! END DO
! ------
! 
!    The `END DO' statement is provided by the GNU Fortran language.
! 
!    This statement is used in one of two ways:
! 
!    * The Fortran 90 meaning, in which it specifies the termination
!      point of a single `DO' loop started with a `DO' statement that
!      specifies no termination label.
! 
!    * The MIL-STD 1753 meaning, in which it specifies the termination
!      point of one or more `DO' loops, all of which start with a `DO'
!      statement that specify the label defined for the `END DO'
!      statement.
! 
!      This kind of `END DO' statement is merely a synonym for
!      `CONTINUE', except it is permitted only when the statement is
!      labeled and a target of one or more labeled `DO' loops.
! 
!      It is expected that this use of `END DO' will be removed from the
!      GNU Fortran language in the future, though it is likely that it
!      will long be supported by `g77' as a dialect form.
! 
! 
! File: g77.info,  Node: Construct Names,  Next: CYCLE and EXIT,  Prev: END DO,  Up: Control Statements
! 
! Construct Names
! ---------------
! 
!    The GNU Fortran language supports construct names as defined by the
! Fortran 90 standard.  These names are local to the program unit and are
! defined as follows:
! 
!      CONSTRUCT-NAME: BLOCK-STATEMENT
! 
! Here, CONSTRUCT-NAME is the construct name itself; its definition is
! connoted by the single colon (`:'); and BLOCK-STATEMENT is an `IF',
! `DO', or `SELECT CASE' statement that begins a block.
! 
!    A block that is given a construct name must also specify the same
! construct name in its termination statement:
! 
!      END BLOCK CONSTRUCT-NAME
! 
! Here, BLOCK must be `IF', `DO', or `SELECT', as appropriate.
! 
! 
! File: g77.info,  Node: CYCLE and EXIT,  Prev: Construct Names,  Up: Control Statements
! 
! The `CYCLE' and `EXIT' Statements
! ---------------------------------
! 
!    The `CYCLE' and `EXIT' statements specify that the remaining
! statements in the current iteration of a particular active (enclosing)
! `DO' loop are to be skipped.
! 
!    `CYCLE' specifies that these statements are skipped, but the `END
! DO' statement that marks the end of the `DO' loop be executed--that is,
! the next iteration, if any, is to be started.  If the statement marking
! the end of the `DO' loop is not `END DO'--in other words, if the loop
! is not a block `DO'--the `CYCLE' statement does not execute that
! statement, but does start the next iteration (if any).
! 
!    `EXIT' specifies that the loop specified by the `DO' construct is
! terminated.
! 
!    The `DO' loop affected by `CYCLE' and `EXIT' is the innermost
! enclosing `DO' loop when the following forms are used:
! 
!      CYCLE
!      EXIT
! 
!    Otherwise, the following forms specify the construct name of the
! pertinent `DO' loop:
! 
!      CYCLE CONSTRUCT-NAME
!      EXIT CONSTRUCT-NAME
! 
!    `CYCLE' and `EXIT' can be viewed as glorified `GO TO' statements.
! However, they cannot be easily thought of as `GO TO' statements in
! obscure cases involving FORTRAN 77 loops.  For example:
! 
!            DO 10 I = 1, 5
!            DO 10 J = 1, 5
!               IF (J .EQ. 5) EXIT
!            DO 10 K = 1, 5
!               IF (K .EQ. 3) CYCLE
!      10    PRINT *, 'I=', I, ' J=', J, ' K=', K
!      20    CONTINUE
! 
! In particular, neither the `EXIT' nor `CYCLE' statements above are
! equivalent to a `GO TO' statement to either label `10' or `20'.
! 
!    To understand the effect of `CYCLE' and `EXIT' in the above
! fragment, it is helpful to first translate it to its equivalent using
! only block `DO' loops:
! 
!            DO I = 1, 5
!               DO J = 1, 5
!                  IF (J .EQ. 5) EXIT
!                  DO K = 1, 5
!                     IF (K .EQ. 3) CYCLE
!      10             PRINT *, 'I=', I, ' J=', J, ' K=', K
!                  END DO
!               END DO
!            END DO
!      20    CONTINUE
! 
!    Adding new labels allows translation of `CYCLE' and `EXIT' to `GO
! TO' so they may be more easily understood by programmers accustomed to
! FORTRAN coding:
! 
!            DO I = 1, 5
!               DO J = 1, 5
!                  IF (J .EQ. 5) GOTO 18
!                  DO K = 1, 5
!                     IF (K .EQ. 3) GO TO 12
!      10             PRINT *, 'I=', I, ' J=', J, ' K=', K
!      12          END DO
!               END DO
!      18    END DO
!      20    CONTINUE
! 
! Thus, the `CYCLE' statement in the innermost loop skips over the
! `PRINT' statement as it begins the next iteration of the loop, while
! the `EXIT' statement in the middle loop ends that loop but _not_ the
! outermost loop.
! 
! 
! File: g77.info,  Node: Functions and Subroutines,  Next: Scope and Classes of Names,  Prev: Control Statements,  Up: Language
! 
! Functions and Subroutines
! =========================
! 
!    (The following information augments or overrides the information in
! Chapter 15 of ANSI X3.9-1978 FORTRAN 77 in specifying the GNU Fortran
! language.  Chapter 15 of that document otherwise serves as the basis
! for the relevant aspects of GNU Fortran.)
! 
! * Menu:
! 
! * %VAL()::
! * %REF()::
! * %DESCR()::
! * Generics and Specifics::
! * REAL() and AIMAG() of Complex::
! * CMPLX() of DOUBLE PRECISION::
! * MIL-STD 1753::
! * f77/f2c Intrinsics::
! * Table of Intrinsic Functions::
! 
! 
! File: g77.info,  Node: %VAL(),  Next: %REF(),  Up: Functions and Subroutines
! 
! The `%VAL()' Construct
! ----------------------
! 
!      %VAL(ARG)
! 
!    The `%VAL()' construct specifies that an argument, ARG, is to be
! passed by value, instead of by reference or descriptor.
! 
!    `%VAL()' is restricted to actual arguments in invocations of
! external procedures.
! 
!    Use of `%VAL()' is recommended only for code that is accessing
! facilities outside of GNU Fortran, such as operating system or
! windowing facilities.  It is best to constrain such uses to isolated
! portions of a program--portions the deal specifically and exclusively
! with low-level, system-dependent facilities.  Such portions might well
! provide a portable interface for use by the program as a whole, but are
! themselves not portable, and should be thoroughly tested each time they
! are rebuilt using a new compiler or version of a compiler.
! 
!    _Implementation Note:_ Currently, `g77' passes all arguments either
! by reference or by descriptor.
! 
!    Thus, use of `%VAL()' tends to be restricted to cases where the
! called procedure is written in a language other than Fortran that
! supports call-by-value semantics.  (C is an example of such a language.)
! 
!    *Note Procedures (SUBROUTINE and FUNCTION): Procedures, for detailed
! information on how this particular version of `g77' passes arguments to
! procedures.
! 
! 
! File: g77.info,  Node: %REF(),  Next: %DESCR(),  Prev: %VAL(),  Up: Functions and Subroutines
! 
! The `%REF()' Construct
! ----------------------
! 
!      %REF(ARG)
! 
!    The `%REF()' construct specifies that an argument, ARG, is to be
! passed by reference, instead of by value or descriptor.
! 
!    `%REF()' is restricted to actual arguments in invocations of
! external procedures.
! 
!    Use of `%REF()' is recommended only for code that is accessing
! facilities outside of GNU Fortran, such as operating system or
! windowing facilities.  It is best to constrain such uses to isolated
! portions of a program--portions the deal specifically and exclusively
! with low-level, system-dependent facilities.  Such portions might well
! provide a portable interface for use by the program as a whole, but are
! themselves not portable, and should be thoroughly tested each time they
! are rebuilt using a new compiler or version of a compiler.
! 
!    Do not depend on `%REF()' supplying a pointer to the procedure being
! invoked.  While that is a likely implementation choice, other
! implementation choices are available that preserve Fortran
! pass-by-reference semantics without passing a pointer to the argument,
! ARG.  (For example, a copy-in/copy-out implementation.)
! 
!    _Implementation Note:_ Currently, `g77' passes all arguments (other
! than variables and arrays of type `CHARACTER') by reference.  Future
! versions of, or dialects supported by, `g77' might not pass `CHARACTER'
! functions by reference.
! 
!    Thus, use of `%REF()' tends to be restricted to cases where ARG is
! type `CHARACTER' but the called procedure accesses it via a means other
! than the method used for Fortran `CHARACTER' arguments.
! 
!    *Note Procedures (SUBROUTINE and FUNCTION): Procedures, for detailed
! information on how this particular version of `g77' passes arguments to
! procedures.
! 
! 
! File: g77.info,  Node: %DESCR(),  Next: Generics and Specifics,  Prev: %REF(),  Up: Functions and Subroutines
! 
! The `%DESCR()' Construct
! ------------------------
! 
!      %DESCR(ARG)
! 
!    The `%DESCR()' construct specifies that an argument, ARG, is to be
! passed by descriptor, instead of by value or reference.
! 
!    `%DESCR()' is restricted to actual arguments in invocations of
! external procedures.
! 
!    Use of `%DESCR()' is recommended only for code that is accessing
! facilities outside of GNU Fortran, such as operating system or
! windowing facilities.  It is best to constrain such uses to isolated
! portions of a program--portions the deal specifically and exclusively
! with low-level, system-dependent facilities.  Such portions might well
! provide a portable interface for use by the program as a whole, but are
! themselves not portable, and should be thoroughly tested each time they
! are rebuilt using a new compiler or version of a compiler.
! 
!    Do not depend on `%DESCR()' supplying a pointer and/or a length
! passed by value to the procedure being invoked.  While that is a likely
! implementation choice, other implementation choices are available that
! preserve the pass-by-reference semantics without passing a pointer to
! the argument, ARG.  (For example, a copy-in/copy-out implementation.)
! And, future versions of `g77' might change the way descriptors are
! implemented, such as passing a single argument pointing to a record
! containing the pointer/length information instead of passing that same
! information via two arguments as it currently does.
! 
!    _Implementation Note:_ Currently, `g77' passes all variables and
! arrays of type `CHARACTER' by descriptor.  Future versions of, or
! dialects supported by, `g77' might pass `CHARACTER' functions by
! descriptor as well.
! 
!    Thus, use of `%DESCR()' tends to be restricted to cases where ARG is
! not type `CHARACTER' but the called procedure accesses it via a means
! similar to the method used for Fortran `CHARACTER' arguments.
! 
!    *Note Procedures (SUBROUTINE and FUNCTION): Procedures, for detailed
! information on how this particular version of `g77' passes arguments to
! procedures.
! 
! 
! File: g77.info,  Node: Generics and Specifics,  Next: REAL() and AIMAG() of Complex,  Prev: %DESCR(),  Up: Functions and Subroutines
! 
! Generics and Specifics
! ----------------------
! 
!    The ANSI FORTRAN 77 language defines generic and specific intrinsics.
! In short, the distinctions are:
! 
!    * _Specific_ intrinsics have specific types for their arguments and
!      a specific return type.
! 
!    * _Generic_ intrinsics are treated, on a case-by-case basis in the
!      program's source code, as one of several possible specific
!      intrinsics.
! 
!      Typically, a generic intrinsic has a return type that is
!      determined by the type of one or more of its arguments.
! 
!    The GNU Fortran language generalizes these concepts somewhat,
! especially by providing intrinsic subroutines and generic intrinsics
! that are treated as either a specific intrinsic subroutine or a
! specific intrinsic function (e.g. `SECOND').
! 
!    However, GNU Fortran avoids generalizing this concept to the point
! where existing code would be accepted as meaning something possibly
! different than what was intended.
! 
!    For example, `ABS' is a generic intrinsic, so all working code
! written using `ABS' of an `INTEGER' argument expects an `INTEGER'
! return value.  Similarly, all such code expects that `ABS' of an
! `INTEGER*2' argument returns an `INTEGER*2' return value.
! 
!    Yet, `IABS' is a _specific_ intrinsic that accepts only an
! `INTEGER(KIND=1)' argument.  Code that passes something other than an
! `INTEGER(KIND=1)' argument to `IABS' is not valid GNU Fortran code,
! because it is not clear what the author intended.
! 
!    For example, if `J' is `INTEGER(KIND=6)', `IABS(J)' is not defined
! by the GNU Fortran language, because the programmer might have used
! that construct to mean any of the following, subtly different, things:
! 
!    * Convert `J' to `INTEGER(KIND=1)' first (as if `IABS(INT(J))' had
!      been written).
! 
!    * Convert the result of the intrinsic to `INTEGER(KIND=1)' (as if
!      `INT(ABS(J))' had been written).
! 
!    * No conversion (as if `ABS(J)' had been written).
! 
!    The distinctions matter especially when types and values wider than
! `INTEGER(KIND=1)' (such as `INTEGER(KIND=2)'), or when operations
! performing more "arithmetic" than absolute-value, are involved.
! 
!    The following sample program is not a valid GNU Fortran program, but
! might be accepted by other compilers.  If so, the output is likely to
! be revealing in terms of how a given compiler treats intrinsics (that
! normally are specific) when they are given arguments that do not
! conform to their stated requirements:
! 
!            PROGRAM JCB002
!      C Version 1:
!      C Modified 1999-02-15 (Burley) to delete my email address.
!      C Modified 1997-05-21 (Burley) to accommodate compilers that implement
!      C INT(I1-I2) as INT(I1)-INT(I2) given INTEGER*2 I1,I2.
!      C
!      C Version 0:
!      C Written by James Craig Burley 1997-02-20.
!      C
!      C Purpose:
!      C Determine how compilers handle non-standard IDIM
!      C on INTEGER*2 operands, which presumably can be
!      C extrapolated into understanding how the compiler
!      C generally treats specific intrinsics that are passed
!      C arguments not of the correct types.
!      C
!      C If your compiler implements INTEGER*2 and INTEGER
!      C as the same type, change all INTEGER*2 below to
!      C INTEGER*1.
!      C
!            INTEGER*2 I0, I4
!            INTEGER I1, I2, I3
!            INTEGER*2 ISMALL, ILARGE
!            INTEGER*2 ITOOLG, ITWO
!            INTEGER*2 ITMP
!            LOGICAL L2, L3, L4
!      C
!      C Find smallest INTEGER*2 number.
!      C
!            ISMALL=0
!       10   I0 = ISMALL-1
!            IF ((I0 .GE. ISMALL) .OR. (I0+1 .NE. ISMALL)) GOTO 20
!            ISMALL = I0
!            GOTO 10
!       20   CONTINUE
!      C
!      C Find largest INTEGER*2 number.
!      C
!            ILARGE=0
!       30   I0 = ILARGE+1
!            IF ((I0 .LE. ILARGE) .OR. (I0-1 .NE. ILARGE)) GOTO 40
!            ILARGE = I0
!            GOTO 30
!       40   CONTINUE
!      C
!      C Multiplying by two adds stress to the situation.
!      C
!            ITWO = 2
!      C
!      C Need a number that, added to -2, is too wide to fit in I*2.
!      C
!            ITOOLG = ISMALL
!      C
!      C Use IDIM the straightforward way.
!      C
!            I1 = IDIM (ILARGE, ISMALL) * ITWO + ITOOLG
!      C
!      C Calculate result for first interpretation.
!      C
!            I2 = (INT (ILARGE) - INT (ISMALL)) * ITWO + ITOOLG
!      C
!      C Calculate result for second interpretation.
!      C
!            ITMP = ILARGE - ISMALL
!            I3 = (INT (ITMP)) * ITWO + ITOOLG
!      C
!      C Calculate result for third interpretation.
!      C
!            I4 = (ILARGE - ISMALL) * ITWO + ITOOLG
!      C
!      C Print results.
!      C
!            PRINT *, 'ILARGE=', ILARGE
!            PRINT *, 'ITWO=', ITWO
!            PRINT *, 'ITOOLG=', ITOOLG
!            PRINT *, 'ISMALL=', ISMALL
!            PRINT *, 'I1=', I1
!            PRINT *, 'I2=', I2
!            PRINT *, 'I3=', I3
!            PRINT *, 'I4=', I4
!            PRINT *
!            L2 = (I1 .EQ. I2)
!            L3 = (I1 .EQ. I3)
!            L4 = (I1 .EQ. I4)
!            IF (L2 .AND. .NOT.L3 .AND. .NOT.L4) THEN
!               PRINT *, 'Interp 1: IDIM(I*2,I*2) => IDIM(INT(I*2),INT(I*2))'
!               STOP
!            END IF
!            IF (L3 .AND. .NOT.L2 .AND. .NOT.L4) THEN
!               PRINT *, 'Interp 2: IDIM(I*2,I*2) => INT(DIM(I*2,I*2))'
!               STOP
!            END IF
!            IF (L4 .AND. .NOT.L2 .AND. .NOT.L3) THEN
!               PRINT *, 'Interp 3: IDIM(I*2,I*2) => DIM(I*2,I*2)'
!               STOP
!            END IF
!            PRINT *, 'Results need careful analysis.'
!            END
! 
!    No future version of the GNU Fortran language will likely permit
! specific intrinsic invocations with wrong-typed arguments (such as
! `IDIM' in the above example), since it has been determined that
! disagreements exist among many production compilers on the
! interpretation of such invocations.  These disagreements strongly
! suggest that Fortran programmers, and certainly existing Fortran
! programs, disagree about the meaning of such invocations.
! 
!    The first version of `JCB002' didn't accommodate some compilers'
! treatment of `INT(I1-I2)' where `I1' and `I2' are `INTEGER*2'.  In such
! a case, these compilers apparently convert both operands to `INTEGER*4'
! and then do an `INTEGER*4' subtraction, instead of doing an `INTEGER*2'
! subtraction on the original values in `I1' and `I2'.
! 
!    However, the results of the careful analyses done on the outputs of
! programs compiled by these various compilers show that they all
! implement either `Interp 1' or `Interp 2' above.
! 
!    Specifically, it is believed that the new version of `JCB002' above
! will confirm that:
! 
!    * Digital Semiconductor ("DEC") Alpha OSF/1, HP-UX 10.0.1, AIX 3.2.5
!      `f77' compilers all implement `Interp 1'.
! 
!    * IRIX 5.3 `f77' compiler implements `Interp 2'.
! 
!    * Solaris 2.5, SunOS 4.1.3, DECstation ULTRIX 4.3, and IRIX 6.1
!      `f77' compilers all implement `Interp 3'.
! 
!    If you get different results than the above for the stated
! compilers, or have results for other compilers that might be worth
! adding to the above list, please let us know the details (compiler
! product, version, machine, results, and so on).
! 
! 
! File: g77.info,  Node: REAL() and AIMAG() of Complex,  Next: CMPLX() of DOUBLE PRECISION,  Prev: Generics and Specifics,  Up: Functions and Subroutines
! 
! `REAL()' and `AIMAG()' of Complex
! ---------------------------------
! 
!    The GNU Fortran language disallows `REAL(EXPR)' and `AIMAG(EXPR)',
! where EXPR is any `COMPLEX' type other than `COMPLEX(KIND=1)', except
! when they are used in the following way:
! 
!      REAL(REAL(EXPR))
!      REAL(AIMAG(EXPR))
! 
! The above forms explicitly specify that the desired effect is to
! convert the real or imaginary part of EXPR, which might be some `REAL'
! type other than `REAL(KIND=1)', to type `REAL(KIND=1)', and have that
! serve as the value of the expression.
! 
!    The GNU Fortran language offers clearly named intrinsics to extract
! the real and imaginary parts of a complex entity without any conversion:
! 
!      REALPART(EXPR)
!      IMAGPART(EXPR)
! 
!    To express the above using typical extended FORTRAN 77, use the
! following constructs (when EXPR is `COMPLEX(KIND=2)'):
! 
!      DBLE(EXPR)
!      DIMAG(EXPR)
! 
!    The FORTRAN 77 language offers no way to explicitly specify the real
! and imaginary parts of a complex expression of arbitrary type,
! apparently as a result of requiring support for only one `COMPLEX' type
! (`COMPLEX(KIND=1)').  The concepts of converting an expression to type
! `REAL(KIND=1)' and of extracting the real part of a complex expression
! were thus "smooshed" by FORTRAN 77 into a single intrinsic, since they
! happened to have the exact same effect in that language (due to having
! only one `COMPLEX' type).
! 
!    _Note:_ When `-ff90' is in effect, `g77' treats `REAL(EXPR)', where
! EXPR is of type `COMPLEX', as `REALPART(EXPR)', whereas with
! `-fugly-complex -fno-f90' in effect, it is treated as
! `REAL(REALPART(EXPR))'.
! 
!    *Note Ugly Complex Part Extraction::, for more information.
! 
! 
! File: g77.info,  Node: CMPLX() of DOUBLE PRECISION,  Next: MIL-STD 1753,  Prev: REAL() and AIMAG() of Complex,  Up: Functions and Subroutines
! 
! `CMPLX()' of `DOUBLE PRECISION'
! -------------------------------
! 
!    In accordance with Fortran 90 and at least some (perhaps all) other
! compilers, the GNU Fortran language defines `CMPLX()' as always
! returning a result that is type `COMPLEX(KIND=1)'.
! 
!    This means `CMPLX(D1,D2)', where `D1' and `D2' are `REAL(KIND=2)'
! (`DOUBLE PRECISION'), is treated as:
! 
!      CMPLX(SNGL(D1), SNGL(D2))
! 
!    (It was necessary for Fortran 90 to specify this behavior for
! `DOUBLE PRECISION' arguments, since that is the behavior mandated by
! FORTRAN 77.)
! 
!    The GNU Fortran language also provides the `DCMPLX()' intrinsic,
! which is provided by some FORTRAN 77 compilers to construct a `DOUBLE
! COMPLEX' entity from of `DOUBLE PRECISION' operands.  However, this
! solution does not scale well when more `COMPLEX' types (having various
! precisions and ranges) are offered by Fortran implementations.
! 
!    Fortran 90 extends the `CMPLX()' intrinsic by adding an extra
! argument used to specify the desired kind of complex result.  However,
! this solution is somewhat awkward to use, and `g77' currently does not
! support it.
! 
!    The GNU Fortran language provides a simple way to build a complex
! value out of two numbers, with the precise type of the value determined
! by the types of the two numbers (via the usual type-promotion
! mechanism):
! 
!      COMPLEX(REAL, IMAG)
! 
!    When REAL and IMAG are the same `REAL' types, `COMPLEX()' performs
! no conversion other than to put them together to form a complex result
! of the same (complex version of real) type.
! 
!    *Note Complex Intrinsic::, for more information.
! 
! 
! File: g77.info,  Node: MIL-STD 1753,  Next: f77/f2c Intrinsics,  Prev: CMPLX() of DOUBLE PRECISION,  Up: Functions and Subroutines
! 
! MIL-STD 1753 Support
! --------------------
! 
!    The GNU Fortran language includes the MIL-STD 1753 intrinsics
! `BTEST', `IAND', `IBCLR', `IBITS', `IBSET', `IEOR', `IOR', `ISHFT',
! `ISHFTC', `MVBITS', and `NOT'.
! 
! 
! File: g77.info,  Node: f77/f2c Intrinsics,  Next: Table of Intrinsic Functions,  Prev: MIL-STD 1753,  Up: Functions and Subroutines
! 
! `f77'/`f2c' Intrinsics
! ----------------------
! 
!    The bit-manipulation intrinsics supported by traditional `f77' and
! by `f2c' are available in the GNU Fortran language.  These include
! `AND', `LSHIFT', `OR', `RSHIFT', and `XOR'.
! 
!    Also supported are the intrinsics `CDABS', `CDCOS', `CDEXP',
! `CDLOG', `CDSIN', `CDSQRT', `DCMPLX', `DCONJG', `DFLOAT', `DIMAG',
! `DREAL', and `IMAG', `ZABS', `ZCOS', `ZEXP', `ZLOG', `ZSIN', and
! `ZSQRT'.
! 
! 
! File: g77.info,  Node: Table of Intrinsic Functions,  Prev: f77/f2c Intrinsics,  Up: Functions and Subroutines
! 
! Table of Intrinsic Functions
! ----------------------------
! 
!    (Corresponds to Section 15.10 of ANSI X3.9-1978 FORTRAN 77.)
! 
!    The GNU Fortran language adds various functions, subroutines, types,
! and arguments to the set of intrinsic functions in ANSI FORTRAN 77.
! The complete set of intrinsics supported by the GNU Fortran language is
! described below.
! 
!    Note that a name is not treated as that of an intrinsic if it is
! specified in an `EXTERNAL' statement in the same program unit; if a
! command-line option is used to disable the groups to which the
! intrinsic belongs; or if the intrinsic is not named in an `INTRINSIC'
! statement and a command-line option is used to hide the groups to which
! the intrinsic belongs.
! 
!    So, it is recommended that any reference in a program unit to an
! intrinsic procedure that is not a standard FORTRAN 77 intrinsic be
! accompanied by an appropriate `INTRINSIC' statement in that program
! unit.  This sort of defensive programming makes it more likely that an
! implementation will issue a diagnostic rather than generate incorrect
! code for such a reference.
! 
!    The terminology used below is based on that of the Fortran 90
! standard, so that the text may be more concise and accurate:
! 
!    * `OPTIONAL' means the argument may be omitted.
! 
!    * `A-1, A-2, ..., A-n' means more than one argument (generally named
!      `A') may be specified.
! 
!    * `scalar' means the argument must not be an array (must be a
!      variable or array element, or perhaps a constant if expressions
!      are permitted).
! 
!    * `DIMENSION(4)' means the argument must be an array having 4
!      elements.
! 
!    * `INTENT(IN)' means the argument must be an expression (such as a
!      constant or a variable that is defined upon invocation of the
!      intrinsic).
! 
!    * `INTENT(OUT)' means the argument must be definable by the
!      invocation of the intrinsic (that is, must not be a constant nor
!      an expression involving operators other than array reference and
!      substring reference).
! 
!    * `INTENT(INOUT)' means the argument must be defined prior to, and
!      definable by, invocation of the intrinsic (a combination of the
!      requirements of `INTENT(IN)' and `INTENT(OUT)'.
! 
!    * *Note Kind Notation::, for an explanation of `KIND'.
! 
!    (Note that the empty lines appearing in the menu below are not
! intentional--they result from a bug in the GNU `makeinfo' program...a
! program that, if it did not exist, would leave this document in far
! worse shape!)
! 
! * Menu:
! 
! 
! * Abort Intrinsic::     Abort the program.
! 
! * Abs Intrinsic::       Absolute value.
! 
! * Access Intrinsic::    Check file accessibility.
! 
! * AChar Intrinsic::     ASCII character from code.
! 
! * ACos Intrinsic::      Arc cosine.
! 
! * AdjustL Intrinsic::   (Reserved for future use.)
! * AdjustR Intrinsic::   (Reserved for future use.)
! 
! * AImag Intrinsic::     Convert/extract imaginary part of complex.
! 
! * AInt Intrinsic::      Truncate to whole number.
! 
! * Alarm Intrinsic::     Execute a routine after a given delay.
! 
! * All Intrinsic::       (Reserved for future use.)
! * Allocated Intrinsic:: (Reserved for future use.)
! 
! * ALog Intrinsic::      Natural logarithm (archaic).
! * ALog10 Intrinsic::    Common logarithm (archaic).
! * AMax0 Intrinsic::     Maximum value (archaic).
! * AMax1 Intrinsic::     Maximum value (archaic).
! * AMin0 Intrinsic::     Minimum value (archaic).
! * AMin1 Intrinsic::     Minimum value (archaic).
! * AMod Intrinsic::      Remainder (archaic).
! 
! * And Intrinsic::       Boolean AND.
! 
! * ANInt Intrinsic::     Round to nearest whole number.
! 
! * Any Intrinsic::       (Reserved for future use.)
! 
! * ASin Intrinsic::      Arc sine.
! 
! * Associated Intrinsic:: (Reserved for future use.)
! 
! * ATan Intrinsic::      Arc tangent.
! * ATan2 Intrinsic::     Arc tangent.
! 
! * BesJ0 Intrinsic::     Bessel function.
! * BesJ1 Intrinsic::     Bessel function.
! * BesJN Intrinsic::     Bessel function.
! * BesY0 Intrinsic::     Bessel function.
! * BesY1 Intrinsic::     Bessel function.
! * BesYN Intrinsic::     Bessel function.
! 
! * Bit_Size Intrinsic::  Number of bits in argument's type.
! 
! * BTest Intrinsic::     Test bit.
! 
! * CAbs Intrinsic::      Absolute value (archaic).
! * CCos Intrinsic::      Cosine (archaic).
! 
! * Ceiling Intrinsic::   (Reserved for future use.)
! 
! * CExp Intrinsic::      Exponential (archaic).
! * Char Intrinsic::      Character from code.
! 
! * ChDir Intrinsic (subroutine):: Change directory.
! 
! * ChMod Intrinsic (subroutine):: Change file modes.
! 
! * CLog Intrinsic::      Natural logarithm (archaic).
! * Cmplx Intrinsic::     Construct `COMPLEX(KIND=1)' value.
! 
! * Complex Intrinsic::   Build complex value from real and
!                          imaginary parts.
! 
! * Conjg Intrinsic::     Complex conjugate.
! * Cos Intrinsic::       Cosine.
! 
! * CosH Intrinsic::      Hyperbolic cosine.
! 
! * Count Intrinsic::     (Reserved for future use.)
! * CPU_Time Intrinsic::  Get current CPU time.
! * CShift Intrinsic::    (Reserved for future use.)
! 
! * CSin Intrinsic::      Sine (archaic).
! * CSqRt Intrinsic::     Square root (archaic).
! 
! * CTime Intrinsic (subroutine):: Convert time to Day Mon dd hh:mm:ss yyyy.
! * CTime Intrinsic (function):: Convert time to Day Mon dd hh:mm:ss yyyy.
! 
! * DAbs Intrinsic::      Absolute value (archaic).
! * DACos Intrinsic::     Arc cosine (archaic).
! 
! * DASin Intrinsic::     Arc sine (archaic).
! 
! * DATan Intrinsic::     Arc tangent (archaic).
! * DATan2 Intrinsic::    Arc tangent (archaic).
! 
! * Date_and_Time Intrinsic:: Get the current date and time.
! 
! * DbesJ0 Intrinsic::    Bessel function (archaic).
! * DbesJ1 Intrinsic::    Bessel function (archaic).
! * DbesJN Intrinsic::    Bessel function (archaic).
! * DbesY0 Intrinsic::    Bessel function (archaic).
! * DbesY1 Intrinsic::    Bessel function (archaic).
! * DbesYN Intrinsic::    Bessel function (archaic).
! 
! * Dble Intrinsic::      Convert to double precision.
! 
! * DCos Intrinsic::      Cosine (archaic).
! 
! * DCosH Intrinsic::     Hyperbolic cosine (archaic).
! * DDiM Intrinsic::      Difference magnitude (archaic).
! 
! * DErF Intrinsic::      Error function (archaic).
! * DErFC Intrinsic::     Complementary error function (archaic).
! 
! * DExp Intrinsic::      Exponential (archaic).
! 
! * Digits Intrinsic::    (Reserved for future use.)
! 
! * DiM Intrinsic::       Difference magnitude (non-negative subtract).
! 
! * DInt Intrinsic::      Truncate to whole number (archaic).
! * DLog Intrinsic::      Natural logarithm (archaic).
! * DLog10 Intrinsic::    Common logarithm (archaic).
! * DMax1 Intrinsic::     Maximum value (archaic).
! * DMin1 Intrinsic::     Minimum value (archaic).
! * DMod Intrinsic::      Remainder (archaic).
! * DNInt Intrinsic::     Round to nearest whole number (archaic).
! 
! * Dot_Product Intrinsic:: (Reserved for future use.)
! 
! * DProd Intrinsic::     Double-precision product.
! 
! * DSign Intrinsic::     Apply sign to magnitude (archaic).
! * DSin Intrinsic::      Sine (archaic).
! 
! * DSinH Intrinsic::     Hyperbolic sine (archaic).
! * DSqRt Intrinsic::     Square root (archaic).
! * DTan Intrinsic::      Tangent (archaic).
! 
! * DTanH Intrinsic::     Hyperbolic tangent (archaic).
! 
! * DTime Intrinsic (subroutine):: Get elapsed time since last time.
! 
! * EOShift Intrinsic::   (Reserved for future use.)
! * Epsilon Intrinsic::   (Reserved for future use.)
! 
! * ErF Intrinsic::       Error function.
! * ErFC Intrinsic::      Complementary error function.
! * ETime Intrinsic (subroutine):: Get elapsed time for process.
! * ETime Intrinsic (function):: Get elapsed time for process.
! * Exit Intrinsic::      Terminate the program.
! 
! * Exp Intrinsic::       Exponential.
! 
! * Exponent Intrinsic::  (Reserved for future use.)
! 
! * FDate Intrinsic (subroutine):: Get current time as Day Mon dd hh:mm:ss yyyy.
! * FDate Intrinsic (function):: Get current time as Day Mon dd hh:mm:ss yyyy.
! * FGet Intrinsic (subroutine):: Read a character from unit 5 stream-wise.
! 
! * FGetC Intrinsic (subroutine):: Read a character stream-wise.
! 
! * Float Intrinsic::     Conversion (archaic).
! 
! * Floor Intrinsic::     (Reserved for future use.)
! 
! * Flush Intrinsic::     Flush buffered output.
! * FNum Intrinsic::      Get file descriptor from Fortran unit number.
! * FPut Intrinsic (subroutine):: Write a character to unit 6 stream-wise.
! 
! * FPutC Intrinsic (subroutine):: Write a character stream-wise.
! 
! * Fraction Intrinsic::  (Reserved for future use.)
! 
! * FSeek Intrinsic::     Position file (low-level).
! * FStat Intrinsic (subroutine):: Get file information.
! * FStat Intrinsic (function):: Get file information.
! * FTell Intrinsic (subroutine):: Get file position (low-level).
! * FTell Intrinsic (function):: Get file position (low-level).
! * GError Intrinsic::    Get error message for last error.
! * GetArg Intrinsic::    Obtain command-line argument.
! * GetCWD Intrinsic (subroutine):: Get current working directory.
! * GetCWD Intrinsic (function):: Get current working directory.
! * GetEnv Intrinsic::    Get environment variable.
! * GetGId Intrinsic::    Get process group id.
! * GetLog Intrinsic::    Get login name.
! * GetPId Intrinsic::    Get process id.
! * GetUId Intrinsic::    Get process user id.
! * GMTime Intrinsic::    Convert time to GMT time info.
! * HostNm Intrinsic (subroutine):: Get host name.
! * HostNm Intrinsic (function):: Get host name.
! 
! * Huge Intrinsic::      (Reserved for future use.)
! 
! * IAbs Intrinsic::      Absolute value (archaic).
! 
! * IAChar Intrinsic::    ASCII code for character.
! 
! * IAnd Intrinsic::      Boolean AND.
! 
! * IArgC Intrinsic::     Obtain count of command-line arguments.
! 
! * IBClr Intrinsic::     Clear a bit.
! * IBits Intrinsic::     Extract a bit subfield of a variable.
! * IBSet Intrinsic::     Set a bit.
! 
! * IChar Intrinsic::     Code for character.
! 
! * IDate Intrinsic (UNIX):: Get local time info.
! 
! * IDiM Intrinsic::      Difference magnitude (archaic).
! * IDInt Intrinsic::     Convert to `INTEGER' value truncated
!                          to whole number (archaic).
! * IDNInt Intrinsic::    Convert to `INTEGER' value rounded
!                          to nearest whole number (archaic).
! 
! * IEOr Intrinsic::      Boolean XOR.
! 
! * IErrNo Intrinsic::    Get error number for last error.
! 
! * IFix Intrinsic::      Conversion (archaic).
! 
! * Imag Intrinsic::      Extract imaginary part of complex.
! 
! * ImagPart Intrinsic::  Extract imaginary part of complex.
! 
! * Index Intrinsic::     Locate a CHARACTER substring.
! 
! * Int Intrinsic::       Convert to `INTEGER' value truncated
!                          to whole number.
! 
! * Int2 Intrinsic::      Convert to `INTEGER(KIND=6)' value
!                          truncated to whole number.
! * Int8 Intrinsic::      Convert to `INTEGER(KIND=2)' value
!                          truncated to whole number.
! 
! * IOr Intrinsic::       Boolean OR.
! 
! * IRand Intrinsic::     Random number.
! * IsaTty Intrinsic::    Is unit connected to a terminal?
! 
! * IShft Intrinsic::     Logical bit shift.
! * IShftC Intrinsic::    Circular bit shift.
! 
! * ISign Intrinsic::     Apply sign to magnitude (archaic).
! 
! * ITime Intrinsic::     Get local time of day.
! 
! * Kill Intrinsic (subroutine):: Signal a process.
! 
! * Kind Intrinsic::      (Reserved for future use.)
! * LBound Intrinsic::    (Reserved for future use.)
! 
! * Len Intrinsic::       Length of character entity.
! 
! * Len_Trim Intrinsic::  Get last non-blank character in string.
! 
! * LGe Intrinsic::       Lexically greater than or equal.
! * LGt Intrinsic::       Lexically greater than.
! 
! * Link Intrinsic (subroutine):: Make hard link in file system.
! 
! * LLe Intrinsic::       Lexically less than or equal.
! * LLt Intrinsic::       Lexically less than.
! 
! * LnBlnk Intrinsic::    Get last non-blank character in string.
! * Loc Intrinsic::       Address of entity in core.
! 
! * Log Intrinsic::       Natural logarithm.
! * Log10 Intrinsic::     Common logarithm.
! 
! * Logical Intrinsic::   (Reserved for future use.)
! 
! * Long Intrinsic::      Conversion to `INTEGER(KIND=1)' (archaic).
! 
! * LShift Intrinsic::    Left-shift bits.
! 
! * LStat Intrinsic (subroutine):: Get file information.
! * LStat Intrinsic (function):: Get file information.
! * LTime Intrinsic::     Convert time to local time info.
! 
! * MatMul Intrinsic::    (Reserved for future use.)
! 
! * Max Intrinsic::       Maximum value.
! * Max0 Intrinsic::      Maximum value (archaic).
! * Max1 Intrinsic::      Maximum value (archaic).
! 
! * MaxExponent Intrinsic:: (Reserved for future use.)
! * MaxLoc Intrinsic::    (Reserved for future use.)
! * MaxVal Intrinsic::    (Reserved for future use.)
! 
! * MClock Intrinsic::    Get number of clock ticks for process.
! * MClock8 Intrinsic::   Get number of clock ticks for process.
! 
! * Merge Intrinsic::     (Reserved for future use.)
! 
! * Min Intrinsic::       Minimum value.
! * Min0 Intrinsic::      Minimum value (archaic).
! * Min1 Intrinsic::      Minimum value (archaic).
! 
! * MinExponent Intrinsic:: (Reserved for future use.)
! * MinLoc Intrinsic::    (Reserved for future use.)
! * MinVal Intrinsic::    (Reserved for future use.)
! 
! * Mod Intrinsic::       Remainder.
! 
! * Modulo Intrinsic::    (Reserved for future use.)
! 
! * MvBits Intrinsic::    Moving a bit field.
! 
! * Nearest Intrinsic::   (Reserved for future use.)
! 
! * NInt Intrinsic::      Convert to `INTEGER' value rounded
!                          to nearest whole number.
! 
! * Not Intrinsic::       Boolean NOT.
! 
! * Or Intrinsic::        Boolean OR.
! 
! * Pack Intrinsic::      (Reserved for future use.)
! 
! * PError Intrinsic::    Print error message for last error.
! 
! * Precision Intrinsic:: (Reserved for future use.)
! * Present Intrinsic::   (Reserved for future use.)
! * Product Intrinsic::   (Reserved for future use.)
! 
! * Radix Intrinsic::     (Reserved for future use.)
! 
! * Rand Intrinsic::      Random number.
! 
! * Random_Number Intrinsic:: (Reserved for future use.)
! * Random_Seed Intrinsic:: (Reserved for future use.)
! * Range Intrinsic::     (Reserved for future use.)
! 
! * Real Intrinsic::      Convert value to type `REAL(KIND=1)'.
! 
! * RealPart Intrinsic::  Extract real part of complex.
! 
! * Rename Intrinsic (subroutine):: Rename file.
! 
! * Repeat Intrinsic::    (Reserved for future use.)
! * Reshape Intrinsic::   (Reserved for future use.)
! * RRSpacing Intrinsic:: (Reserved for future use.)
! 
! * RShift Intrinsic::    Right-shift bits.
! 
! * Scale Intrinsic::     (Reserved for future use.)
! * Scan Intrinsic::      (Reserved for future use.)
! 
! * Second Intrinsic (function):: Get CPU time for process in seconds.
! * Second Intrinsic (subroutine):: Get CPU time for process
!                          in seconds.
! 
! * Selected_Int_Kind Intrinsic:: (Reserved for future use.)
! * Selected_Real_Kind Intrinsic:: (Reserved for future use.)
! * Set_Exponent Intrinsic:: (Reserved for future use.)
! * Shape Intrinsic::     (Reserved for future use.)
! 
! * Short Intrinsic::     Convert to `INTEGER(KIND=6)' value
!                          truncated to whole number.
! 
! * Sign Intrinsic::      Apply sign to magnitude.
! 
! * Signal Intrinsic (subroutine):: Muck with signal handling.
! 
! * Sin Intrinsic::       Sine.
! 
! * SinH Intrinsic::      Hyperbolic sine.
! 
! * Sleep Intrinsic::     Sleep for a specified time.
! 
! * Sngl Intrinsic::      Convert (archaic).
! 
! * Spacing Intrinsic::   (Reserved for future use.)
! * Spread Intrinsic::    (Reserved for future use.)
! 
! * SqRt Intrinsic::      Square root.
! 
! * SRand Intrinsic::     Random seed.
! * Stat Intrinsic (subroutine):: Get file information.
! * Stat Intrinsic (function):: Get file information.
! 
! * Sum Intrinsic::       (Reserved for future use.)
! 
! * SymLnk Intrinsic (subroutine):: Make symbolic link in file system.
! 
! * System Intrinsic (subroutine):: Invoke shell (system) command.
! 
! * System_Clock Intrinsic:: Get current system clock value.
! 
! * Tan Intrinsic::       Tangent.
! 
! * TanH Intrinsic::      Hyperbolic tangent.
! 
! * Time Intrinsic (UNIX):: Get current time as time value.
! 
! * Time8 Intrinsic::     Get current time as time value.
! 
! * Tiny Intrinsic::      (Reserved for future use.)
! * Transfer Intrinsic::  (Reserved for future use.)
! * Transpose Intrinsic:: (Reserved for future use.)
! * Trim Intrinsic::      (Reserved for future use.)
! 
! * TtyNam Intrinsic (subroutine):: Get name of terminal device for unit.
! * TtyNam Intrinsic (function):: Get name of terminal device for unit.
! 
! * UBound Intrinsic::    (Reserved for future use.)
! 
! * UMask Intrinsic (subroutine):: Set file creation permissions mask.
! 
! * Unlink Intrinsic (subroutine):: Unlink file.
! 
! * Unpack Intrinsic::    (Reserved for future use.)
! * Verify Intrinsic::    (Reserved for future use.)
! 
! * XOr Intrinsic::       Boolean XOR.
! * ZAbs Intrinsic::      Absolute value (archaic).
! * ZCos Intrinsic::      Cosine (archaic).
! * ZExp Intrinsic::      Exponential (archaic).
! 
! * ZLog Intrinsic::      Natural logarithm (archaic).
! * ZSin Intrinsic::      Sine (archaic).
! * ZSqRt Intrinsic::     Square root (archaic).
! 
! 
! File: g77.info,  Node: Abort Intrinsic,  Next: Abs Intrinsic,  Up: Table of Intrinsic Functions
! 
! Abort Intrinsic
! ...............
! 
!      CALL Abort()
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Prints a message and potentially causes a core dump via `abort(3)'.
! 
! 
! File: g77.info,  Node: Abs Intrinsic,  Next: Access Intrinsic,  Prev: Abort Intrinsic,  Up: Table of Intrinsic Functions
! 
! Abs Intrinsic
! .............
! 
!      Abs(A)
! 
! Abs: `INTEGER' or `REAL' function.  The exact type depends on that of
! argument A--if A is `COMPLEX', this function's type is `REAL' with the
! same `KIND=' value as the type of A.  Otherwise, this function's type
! is the same as that of A.
! 
! A: `INTEGER', `REAL', or `COMPLEX'; scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Returns the absolute value of A.
! 
!    If A is type `COMPLEX', the absolute value is computed as:
! 
!      SQRT(REALPART(A)**2+IMAGPART(A)**2)
! 
! Otherwise, it is computed by negating A if it is negative, or returning
! A.
! 
!    *Note Sign Intrinsic::, for how to explicitly compute the positive
! or negative form of the absolute value of an expression.
! 
! 
! File: g77.info,  Node: Access Intrinsic,  Next: AChar Intrinsic,  Prev: Abs Intrinsic,  Up: Table of Intrinsic Functions
! 
! Access Intrinsic
! ................
! 
!      Access(NAME, MODE)
! 
! Access: `INTEGER(KIND=1)' function.
! 
! NAME: `CHARACTER'; scalar; INTENT(IN).
! 
! MODE: `CHARACTER'; scalar; INTENT(IN).
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Checks file NAME for accessibility in the mode specified by MODE and
! returns 0 if the file is accessible in that mode, otherwise an error
! code if the file is inaccessible or MODE is invalid.  See `access(2)'.
! A null character (`CHAR(0)') marks the end of the name in
! NAME--otherwise, trailing blanks in NAME are ignored.  MODE may be a
! concatenation of any of the following characters:
! 
! `r'
!      Read permission
! 
! `w'
!      Write permission
! 
! `x'
!      Execute permission
! 
! `SPC'
!      Existence
! 
! 
! File: g77.info,  Node: AChar Intrinsic,  Next: ACos Intrinsic,  Prev: Access Intrinsic,  Up: Table of Intrinsic Functions
! 
! AChar Intrinsic
! ...............
! 
!      AChar(I)
! 
! AChar: `CHARACTER*1' function.
! 
! I: `INTEGER'; scalar; INTENT(IN).
! 
! Intrinsic groups: `f2c', `f90'.
! 
! Description:
! 
!    Returns the ASCII character corresponding to the code specified by I.
! 
!    *Note IAChar Intrinsic::, for the inverse of this function.
! 
!    *Note Char Intrinsic::, for the function corresponding to the
! system's native character set.
! 
! 
! File: g77.info,  Node: ACos Intrinsic,  Next: AdjustL Intrinsic,  Prev: AChar Intrinsic,  Up: Table of Intrinsic Functions
! 
! ACos Intrinsic
! ..............
! 
!      ACos(X)
! 
! ACos: `REAL' function, the `KIND=' value of the type being that of
! argument X.
! 
! X: `REAL'; scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Returns the arc-cosine (inverse cosine) of X in radians.
! 
!    *Note Cos Intrinsic::, for the inverse of this function.
! 
! 
! File: g77.info,  Node: AdjustL Intrinsic,  Next: AdjustR Intrinsic,  Prev: ACos Intrinsic,  Up: Table of Intrinsic Functions
! 
! AdjustL Intrinsic
! .................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL AdjustL' to use this name for
! an external procedure.
! 
! 
! File: g77.info,  Node: AdjustR Intrinsic,  Next: AImag Intrinsic,  Prev: AdjustL Intrinsic,  Up: Table of Intrinsic Functions
! 
! AdjustR Intrinsic
! .................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL AdjustR' to use this name for
! an external procedure.
! 
! 
! File: g77.info,  Node: AImag Intrinsic,  Next: AInt Intrinsic,  Prev: AdjustR Intrinsic,  Up: Table of Intrinsic Functions
! 
! AImag Intrinsic
! ...............
! 
!      AImag(Z)
! 
! AImag: `REAL' function.  This intrinsic is valid when argument Z is
! `COMPLEX(KIND=1)'.  When Z is any other `COMPLEX' type, this intrinsic
! is valid only when used as the argument to `REAL()', as explained below.
! 
! Z: `COMPLEX'; scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Returns the (possibly converted) imaginary part of Z.
! 
!    Use of `AIMAG()' with an argument of a type other than
! `COMPLEX(KIND=1)' is restricted to the following case:
! 
!      REAL(AIMAG(Z))
! 
! This expression converts the imaginary part of Z to `REAL(KIND=1)'.
! 
!    *Note REAL() and AIMAG() of Complex::, for more information.
! 
! 
! File: g77.info,  Node: AInt Intrinsic,  Next: Alarm Intrinsic,  Prev: AImag Intrinsic,  Up: Table of Intrinsic Functions
! 
! AInt Intrinsic
! ..............
! 
!      AInt(A)
! 
! AInt: `REAL' function, the `KIND=' value of the type being that of
! argument A.
! 
! A: `REAL'; scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Returns A with the fractional portion of its magnitude truncated and
! its sign preserved.  (Also called "truncation towards zero".)
! 
!    *Note ANInt Intrinsic::, for how to round to nearest whole number.
! 
!    *Note Int Intrinsic::, for how to truncate and then convert number
! to `INTEGER'.
! 
! 
! File: g77.info,  Node: Alarm Intrinsic,  Next: All Intrinsic,  Prev: AInt Intrinsic,  Up: Table of Intrinsic Functions
! 
! Alarm Intrinsic
! ...............
! 
!      CALL Alarm(SECONDS, HANDLER, STATUS)
! 
! SECONDS: `INTEGER'; scalar; INTENT(IN).
! 
! HANDLER: Signal handler (`INTEGER FUNCTION' or `SUBROUTINE') or
! dummy/global `INTEGER(KIND=1)' scalar.
! 
! STATUS: `INTEGER(KIND=1)'; OPTIONAL; scalar; INTENT(OUT).
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Causes external subroutine HANDLER to be executed after a delay of
! SECONDS seconds by using `alarm(1)' to set up a signal and `signal(2)'
! to catch it.  If STATUS is supplied, it will be returned with the
! number of seconds remaining until any previously scheduled alarm was
! due to be delivered, or zero if there was no previously scheduled alarm.
! *Note Signal Intrinsic (subroutine)::.
! 
! 
! File: g77.info,  Node: All Intrinsic,  Next: Allocated Intrinsic,  Prev: Alarm Intrinsic,  Up: Table of Intrinsic Functions
! 
! All Intrinsic
! .............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL All' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: Allocated Intrinsic,  Next: ALog Intrinsic,  Prev: All Intrinsic,  Up: Table of Intrinsic Functions
! 
! Allocated Intrinsic
! ...................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL Allocated' to use this name
! for an external procedure.
! 
! 
! File: g77.info,  Node: ALog Intrinsic,  Next: ALog10 Intrinsic,  Prev: Allocated Intrinsic,  Up: Table of Intrinsic Functions
! 
! ALog Intrinsic
! ..............
! 
!      ALog(X)
! 
! ALog: `REAL(KIND=1)' function.
! 
! X: `REAL(KIND=1)'; scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Archaic form of `LOG()' that is specific to one type for X.  *Note
! Log Intrinsic::.
! 
! 
! File: g77.info,  Node: ALog10 Intrinsic,  Next: AMax0 Intrinsic,  Prev: ALog Intrinsic,  Up: Table of Intrinsic Functions
! 
! ALog10 Intrinsic
! ................
! 
!      ALog10(X)
! 
! ALog10: `REAL(KIND=1)' function.
! 
! X: `REAL(KIND=1)'; scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Archaic form of `LOG10()' that is specific to one type for X.  *Note
! Log10 Intrinsic::.
! 
! 
! File: g77.info,  Node: AMax0 Intrinsic,  Next: AMax1 Intrinsic,  Prev: ALog10 Intrinsic,  Up: Table of Intrinsic Functions
! 
! AMax0 Intrinsic
! ...............
! 
!      AMax0(A-1, A-2, ..., A-n)
! 
! AMax0: `REAL(KIND=1)' function.
! 
! A: `INTEGER(KIND=1)'; at least two such arguments must be provided;
! scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Archaic form of `MAX()' that is specific to one type for A and a
! different return type.  *Note Max Intrinsic::.
! 
! 
! File: g77.info,  Node: AMax1 Intrinsic,  Next: AMin0 Intrinsic,  Prev: AMax0 Intrinsic,  Up: Table of Intrinsic Functions
! 
! AMax1 Intrinsic
! ...............
! 
!      AMax1(A-1, A-2, ..., A-n)
! 
! AMax1: `REAL(KIND=1)' function.
! 
! A: `REAL(KIND=1)'; at least two such arguments must be provided;
! scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Archaic form of `MAX()' that is specific to one type for A.  *Note
! Max Intrinsic::.
! 
! 
! File: g77.info,  Node: AMin0 Intrinsic,  Next: AMin1 Intrinsic,  Prev: AMax1 Intrinsic,  Up: Table of Intrinsic Functions
! 
! AMin0 Intrinsic
! ...............
! 
!      AMin0(A-1, A-2, ..., A-n)
! 
! AMin0: `REAL(KIND=1)' function.
! 
! A: `INTEGER(KIND=1)'; at least two such arguments must be provided;
! scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Archaic form of `MIN()' that is specific to one type for A and a
! different return type.  *Note Min Intrinsic::.
! 
! 
! File: g77.info,  Node: AMin1 Intrinsic,  Next: AMod Intrinsic,  Prev: AMin0 Intrinsic,  Up: Table of Intrinsic Functions
! 
! AMin1 Intrinsic
! ...............
! 
!      AMin1(A-1, A-2, ..., A-n)
! 
! AMin1: `REAL(KIND=1)' function.
! 
! A: `REAL(KIND=1)'; at least two such arguments must be provided;
! scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Archaic form of `MIN()' that is specific to one type for A.  *Note
! Min Intrinsic::.
! 
! 
! File: g77.info,  Node: AMod Intrinsic,  Next: And Intrinsic,  Prev: AMin1 Intrinsic,  Up: Table of Intrinsic Functions
! 
! AMod Intrinsic
! ..............
! 
!      AMod(A, P)
! 
! AMod: `REAL(KIND=1)' function.
! 
! A: `REAL(KIND=1)'; scalar; INTENT(IN).
! 
! P: `REAL(KIND=1)'; scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Archaic form of `MOD()' that is specific to one type for A.  *Note
! Mod Intrinsic::.
! 
! 
! File: g77.info,  Node: And Intrinsic,  Next: ANInt Intrinsic,  Prev: AMod Intrinsic,  Up: Table of Intrinsic Functions
! 
! And Intrinsic
! .............
! 
!      And(I, J)
! 
! And: `INTEGER' or `LOGICAL' function, the exact type being the result
! of cross-promoting the types of all the arguments.
! 
! I: `INTEGER' or `LOGICAL'; scalar; INTENT(IN).
! 
! J: `INTEGER' or `LOGICAL'; scalar; INTENT(IN).
! 
! Intrinsic groups: `f2c'.
! 
! Description:
! 
!    Returns value resulting from boolean AND of pair of bits in each of
! I and J.
! 
! 
! File: g77.info,  Node: ANInt Intrinsic,  Next: Any Intrinsic,  Prev: And Intrinsic,  Up: Table of Intrinsic Functions
! 
! ANInt Intrinsic
! ...............
! 
!      ANInt(A)
! 
! ANInt: `REAL' function, the `KIND=' value of the type being that of
! argument A.
! 
! A: `REAL'; scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Returns A with the fractional portion of its magnitude eliminated by
! rounding to the nearest whole number and with its sign preserved.
! 
!    A fractional portion exactly equal to `.5' is rounded to the whole
! number that is larger in magnitude.  (Also called "Fortran round".)
! 
!    *Note AInt Intrinsic::, for how to truncate to whole number.
! 
!    *Note NInt Intrinsic::, for how to round and then convert number to
! `INTEGER'.
! 
! 
! File: g77.info,  Node: Any Intrinsic,  Next: ASin Intrinsic,  Prev: ANInt Intrinsic,  Up: Table of Intrinsic Functions
! 
! Any Intrinsic
! .............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL Any' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: ASin Intrinsic,  Next: Associated Intrinsic,  Prev: Any Intrinsic,  Up: Table of Intrinsic Functions
! 
! ASin Intrinsic
! ..............
! 
!      ASin(X)
! 
! ASin: `REAL' function, the `KIND=' value of the type being that of
! argument X.
! 
! X: `REAL'; scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Returns the arc-sine (inverse sine) of X in radians.
! 
!    *Note Sin Intrinsic::, for the inverse of this function.
! 
! 
! File: g77.info,  Node: Associated Intrinsic,  Next: ATan Intrinsic,  Prev: ASin Intrinsic,  Up: Table of Intrinsic Functions
! 
! Associated Intrinsic
! ....................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL Associated' to use this name
! for an external procedure.
! 
! 
! File: g77.info,  Node: ATan Intrinsic,  Next: ATan2 Intrinsic,  Prev: Associated Intrinsic,  Up: Table of Intrinsic Functions
! 
! ATan Intrinsic
! ..............
! 
!      ATan(X)
! 
! ATan: `REAL' function, the `KIND=' value of the type being that of
! argument X.
! 
! X: `REAL'; scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Returns the arc-tangent (inverse tangent) of X in radians.
! 
!    *Note Tan Intrinsic::, for the inverse of this function.
! 
! 
! File: g77.info,  Node: ATan2 Intrinsic,  Next: BesJ0 Intrinsic,  Prev: ATan Intrinsic,  Up: Table of Intrinsic Functions
! 
! ATan2 Intrinsic
! ...............
! 
!      ATan2(Y, X)
! 
! ATan2: `REAL' function, the exact type being the result of
! cross-promoting the types of all the arguments.
! 
! Y: `REAL'; scalar; INTENT(IN).
! 
! X: `REAL'; scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Returns the arc-tangent (inverse tangent) of the complex number (Y,
! X) in radians.
! 
!    *Note Tan Intrinsic::, for the inverse of this function.
! 
! 
! File: g77.info,  Node: BesJ0 Intrinsic,  Next: BesJ1 Intrinsic,  Prev: ATan2 Intrinsic,  Up: Table of Intrinsic Functions
! 
! BesJ0 Intrinsic
! ...............
! 
!      BesJ0(X)
! 
! BesJ0: `REAL' function, the `KIND=' value of the type being that of
! argument X.
! 
! X: `REAL'; scalar; INTENT(IN).
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Calculates the Bessel function of the first kind of order 0 of X.
! See `bessel(3m)', on whose implementation the function depends.
! 
! 
! File: g77.info,  Node: BesJ1 Intrinsic,  Next: BesJN Intrinsic,  Prev: BesJ0 Intrinsic,  Up: Table of Intrinsic Functions
! 
! BesJ1 Intrinsic
! ...............
! 
!      BesJ1(X)
! 
! BesJ1: `REAL' function, the `KIND=' value of the type being that of
! argument X.
! 
! X: `REAL'; scalar; INTENT(IN).
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Calculates the Bessel function of the first kind of order 1 of X.
! See `bessel(3m)', on whose implementation the function depends.
! 
! 
! File: g77.info,  Node: BesJN Intrinsic,  Next: BesY0 Intrinsic,  Prev: BesJ1 Intrinsic,  Up: Table of Intrinsic Functions
! 
! BesJN Intrinsic
! ...............
! 
!      BesJN(N, X)
! 
! BesJN: `REAL' function, the `KIND=' value of the type being that of
! argument X.
! 
! N: `INTEGER' not wider than the default kind; scalar; INTENT(IN).
! 
! X: `REAL'; scalar; INTENT(IN).
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Calculates the Bessel function of the first kind of order N of X.
! See `bessel(3m)', on whose implementation the function depends.
! 
! 
! File: g77.info,  Node: BesY0 Intrinsic,  Next: BesY1 Intrinsic,  Prev: BesJN Intrinsic,  Up: Table of Intrinsic Functions
! 
! BesY0 Intrinsic
! ...............
! 
!      BesY0(X)
! 
! BesY0: `REAL' function, the `KIND=' value of the type being that of
! argument X.
! 
! X: `REAL'; scalar; INTENT(IN).
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Calculates the Bessel function of the second kind of order 0 of X.
! See `bessel(3m)', on whose implementation the function depends.
! 
! 
! File: g77.info,  Node: BesY1 Intrinsic,  Next: BesYN Intrinsic,  Prev: BesY0 Intrinsic,  Up: Table of Intrinsic Functions
! 
! BesY1 Intrinsic
! ...............
! 
!      BesY1(X)
! 
! BesY1: `REAL' function, the `KIND=' value of the type being that of
! argument X.
! 
! X: `REAL'; scalar; INTENT(IN).
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Calculates the Bessel function of the second kind of order 1 of X.
! See `bessel(3m)', on whose implementation the function depends.
! 
! 
! File: g77.info,  Node: BesYN Intrinsic,  Next: Bit_Size Intrinsic,  Prev: BesY1 Intrinsic,  Up: Table of Intrinsic Functions
! 
! BesYN Intrinsic
! ...............
! 
!      BesYN(N, X)
! 
! BesYN: `REAL' function, the `KIND=' value of the type being that of
! argument X.
! 
! N: `INTEGER' not wider than the default kind; scalar; INTENT(IN).
! 
! X: `REAL'; scalar; INTENT(IN).
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Calculates the Bessel function of the second kind of order N of X.
! See `bessel(3m)', on whose implementation the function depends.
! 
! 
! File: g77.info,  Node: Bit_Size Intrinsic,  Next: BTest Intrinsic,  Prev: BesYN Intrinsic,  Up: Table of Intrinsic Functions
! 
! Bit_Size Intrinsic
! ..................
! 
!      Bit_Size(I)
! 
! Bit_Size: `INTEGER' function, the `KIND=' value of the type being that
! of argument I.
! 
! I: `INTEGER'; scalar.
! 
! Intrinsic groups: `f90'.
! 
! Description:
! 
!    Returns the number of bits (integer precision plus sign bit)
! represented by the type for I.
! 
!    *Note BTest Intrinsic::, for how to test the value of a bit in a
! variable or array.
! 
!    *Note IBSet Intrinsic::, for how to set a bit in a variable to 1.
! 
!    *Note IBClr Intrinsic::, for how to set a bit in a variable to 0.
! 
! 
! File: g77.info,  Node: BTest Intrinsic,  Next: CAbs Intrinsic,  Prev: Bit_Size Intrinsic,  Up: Table of Intrinsic Functions
! 
! BTest Intrinsic
! ...............
! 
!      BTest(I, POS)
! 
! BTest: `LOGICAL(KIND=1)' function.
! 
! I: `INTEGER'; scalar; INTENT(IN).
! 
! POS: `INTEGER'; scalar; INTENT(IN).
! 
! Intrinsic groups: `mil', `f90', `vxt'.
! 
! Description:
! 
!    Returns `.TRUE.' if bit POS in I is 1, `.FALSE.' otherwise.
! 
!    (Bit 0 is the low-order (rightmost) bit, adding the value 2**0, or 1,
! to the number if set to 1; bit 1 is the next-higher-order bit, adding
! 2**1, or 2; bit 2 adds 2**2, or 4; and so on.)
! 
!    *Note Bit_Size Intrinsic::, for how to obtain the number of bits in
! a type.  The leftmost bit of I is `BIT_SIZE(I-1)'.
! 
! 
! File: g77.info,  Node: CAbs Intrinsic,  Next: CCos Intrinsic,  Prev: BTest Intrinsic,  Up: Table of Intrinsic Functions
! 
! CAbs Intrinsic
! ..............
! 
!      CAbs(A)
! 
! CAbs: `REAL(KIND=1)' function.
! 
! A: `COMPLEX(KIND=1)'; scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Archaic form of `ABS()' that is specific to one type for A.  *Note
! Abs Intrinsic::.
! 
! 
! File: g77.info,  Node: CCos Intrinsic,  Next: Ceiling Intrinsic,  Prev: CAbs Intrinsic,  Up: Table of Intrinsic Functions
! 
! CCos Intrinsic
! ..............
! 
!      CCos(X)
! 
! CCos: `COMPLEX(KIND=1)' function.
! 
! X: `COMPLEX(KIND=1)'; scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Archaic form of `COS()' that is specific to one type for X.  *Note
! Cos Intrinsic::.
! 
! 
! File: g77.info,  Node: Ceiling Intrinsic,  Next: CExp Intrinsic,  Prev: CCos Intrinsic,  Up: Table of Intrinsic Functions
! 
! Ceiling Intrinsic
! .................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL Ceiling' to use this name for
! an external procedure.
! 
! 
! File: g77.info,  Node: CExp Intrinsic,  Next: Char Intrinsic,  Prev: Ceiling Intrinsic,  Up: Table of Intrinsic Functions
! 
! CExp Intrinsic
! ..............
! 
!      CExp(X)
! 
! CExp: `COMPLEX(KIND=1)' function.
! 
! X: `COMPLEX(KIND=1)'; scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Archaic form of `EXP()' that is specific to one type for X.  *Note
! Exp Intrinsic::.
! 
! 
! File: g77.info,  Node: Char Intrinsic,  Next: ChDir Intrinsic (subroutine),  Prev: CExp Intrinsic,  Up: Table of Intrinsic Functions
! 
! Char Intrinsic
! ..............
! 
!      Char(I)
! 
! Char: `CHARACTER*1' function.
! 
! I: `INTEGER'; scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Returns the character corresponding to the code specified by I,
! using the system's native character set.
! 
!    Because the system's native character set is used, the
! correspondence between character and their codes is not necessarily the
! same between GNU Fortran implementations.
! 
!    Note that no intrinsic exists to convert a numerical value to a
! printable character string.  For example, there is no intrinsic that,
! given an `INTEGER' or `REAL' argument with the value `154', returns the
! `CHARACTER' result `'154''.
! 
!    Instead, you can use internal-file I/O to do this kind of conversion.
! For example:
! 
!      INTEGER VALUE
!      CHARACTER*10 STRING
!      VALUE = 154
!      WRITE (STRING, '(I10)'), VALUE
!      PRINT *, STRING
!      END
! 
!    The above program, when run, prints:
! 
!              154
! 
!    *Note IChar Intrinsic::, for the inverse of the `CHAR' function.
! 
!    *Note AChar Intrinsic::, for the function corresponding to the ASCII
! character set.
! 
! 
! File: g77.info,  Node: ChDir Intrinsic (subroutine),  Next: ChMod Intrinsic (subroutine),  Prev: Char Intrinsic,  Up: Table of Intrinsic Functions
! 
! ChDir Intrinsic (subroutine)
! ............................
! 
!      CALL ChDir(DIR, STATUS)
! 
! DIR: `CHARACTER'; scalar; INTENT(IN).
! 
! STATUS: `INTEGER(KIND=1)'; OPTIONAL; scalar; INTENT(OUT).
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Sets the current working directory to be DIR.  If the STATUS
! argument is supplied, it contains 0 on success or a nonzero error code
! otherwise upon return.  See `chdir(3)'.
! 
!    _Caution:_ Using this routine during I/O to a unit connected with a
! non-absolute file name can cause subsequent I/O on such a unit to fail
! because the I/O library might reopen files by name.
! 
!    Some non-GNU implementations of Fortran provide this intrinsic as
! only a function, not as a subroutine, or do not support the (optional)
! STATUS argument.
! 
!    For information on other intrinsics with the same name: *Note ChDir
! Intrinsic (function)::.
! 
! 
! File: g77.info,  Node: ChMod Intrinsic (subroutine),  Next: CLog Intrinsic,  Prev: ChDir Intrinsic (subroutine),  Up: Table of Intrinsic Functions
! 
! ChMod Intrinsic (subroutine)
! ............................
! 
!      CALL ChMod(NAME, MODE, STATUS)
! 
! NAME: `CHARACTER'; scalar; INTENT(IN).
! 
! MODE: `CHARACTER'; scalar; INTENT(IN).
! 
! STATUS: `INTEGER(KIND=1)'; OPTIONAL; scalar; INTENT(OUT).
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Changes the access mode of file NAME according to the specification
! MODE, which is given in the format of `chmod(1)'.  A null character
! (`CHAR(0)') marks the end of the name in NAME--otherwise, trailing
! blanks in NAME are ignored.  Currently, NAME must not contain the
! single quote character.
! 
!    If the STATUS argument is supplied, it contains 0 on success or a
! nonzero error code upon return.
! 
!    Note that this currently works by actually invoking `/bin/chmod' (or
! the `chmod' found when the library was configured) and so might fail in
! some circumstances and will, anyway, be slow.
! 
!    Some non-GNU implementations of Fortran provide this intrinsic as
! only a function, not as a subroutine, or do not support the (optional)
! STATUS argument.
! 
!    For information on other intrinsics with the same name: *Note ChMod
! Intrinsic (function)::.
! 
! 
! File: g77.info,  Node: CLog Intrinsic,  Next: Cmplx Intrinsic,  Prev: ChMod Intrinsic (subroutine),  Up: Table of Intrinsic Functions
! 
! CLog Intrinsic
! ..............
! 
!      CLog(X)
! 
! CLog: `COMPLEX(KIND=1)' function.
! 
! X: `COMPLEX(KIND=1)'; scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Archaic form of `LOG()' that is specific to one type for X.  *Note
! Log Intrinsic::.
! 
! 
! File: g77.info,  Node: Cmplx Intrinsic,  Next: Complex Intrinsic,  Prev: CLog Intrinsic,  Up: Table of Intrinsic Functions
! 
! Cmplx Intrinsic
! ...............
! 
!      Cmplx(X, Y)
! 
! Cmplx: `COMPLEX(KIND=1)' function.
! 
! X: `INTEGER', `REAL', or `COMPLEX'; scalar; INTENT(IN).
! 
! Y: `INTEGER' or `REAL'; OPTIONAL (must be omitted if X is `COMPLEX');
! scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    If X is not type `COMPLEX', constructs a value of type
! `COMPLEX(KIND=1)' from the real and imaginary values specified by X and
! Y, respectively.  If Y is omitted, `0.' is assumed.
! 
!    If X is type `COMPLEX', converts it to type `COMPLEX(KIND=1)'.
! 
!    *Note Complex Intrinsic::, for information on easily constructing a
! `COMPLEX' value of arbitrary precision from `REAL' arguments.
! 
! 
! File: g77.info,  Node: Complex Intrinsic,  Next: Conjg Intrinsic,  Prev: Cmplx Intrinsic,  Up: Table of Intrinsic Functions
! 
! Complex Intrinsic
! .................
! 
!      Complex(REAL, IMAG)
! 
! Complex: `COMPLEX' function, the exact type being the result of
! cross-promoting the types of all the arguments.
! 
! REAL: `INTEGER' or `REAL'; scalar; INTENT(IN).
! 
! IMAG: `INTEGER' or `REAL'; scalar; INTENT(IN).
! 
! Intrinsic groups: `gnu'.
! 
! Description:
! 
!    Returns a `COMPLEX' value that has `Real' and `Imag' as its real and
! imaginary parts, respectively.
! 
!    If REAL and IMAG are the same type, and that type is not `INTEGER',
! no data conversion is performed, and the type of the resulting value
! has the same kind value as the types of REAL and IMAG.
! 
!    If REAL and IMAG are not the same type, the usual type-promotion
! rules are applied to both, converting either or both to the appropriate
! `REAL' type.  The type of the resulting value has the same kind value
! as the type to which both REAL and IMAG were converted, in this case.
! 
!    If REAL and IMAG are both `INTEGER', they are both converted to
! `REAL(KIND=1)', and the result of the `COMPLEX()' invocation is type
! `COMPLEX(KIND=1)'.
! 
!    _Note:_ The way to do this in standard Fortran 90 is too hairy to
! describe here, but it is important to note that `CMPLX(D1,D2)' returns
! a `COMPLEX(KIND=1)' result even if `D1' and `D2' are type
! `REAL(KIND=2)'.  Hence the availability of `COMPLEX()' in GNU Fortran.
! 
! 
! File: g77.info,  Node: Conjg Intrinsic,  Next: Cos Intrinsic,  Prev: Complex Intrinsic,  Up: Table of Intrinsic Functions
! 
! Conjg Intrinsic
! ...............
! 
!      Conjg(Z)
! 
! Conjg: `COMPLEX' function, the `KIND=' value of the type being that of
! argument Z.
! 
! Z: `COMPLEX'; scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Returns the complex conjugate:
! 
!      COMPLEX(REALPART(Z), -IMAGPART(Z))
! 
! 
! File: g77.info,  Node: Cos Intrinsic,  Next: CosH Intrinsic,  Prev: Conjg Intrinsic,  Up: Table of Intrinsic Functions
! 
! Cos Intrinsic
! .............
! 
!      Cos(X)
! 
! Cos: `REAL' or `COMPLEX' function, the exact type being that of
! argument X.
! 
! X: `REAL' or `COMPLEX'; scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Returns the cosine of X, an angle measured in radians.
! 
!    *Note ACos Intrinsic::, for the inverse of this function.
! 
! 
! File: g77.info,  Node: CosH Intrinsic,  Next: Count Intrinsic,  Prev: Cos Intrinsic,  Up: Table of Intrinsic Functions
! 
! CosH Intrinsic
! ..............
! 
!      CosH(X)
! 
! CosH: `REAL' function, the `KIND=' value of the type being that of
! argument X.
! 
! X: `REAL'; scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Returns the hyperbolic cosine of X.
! 
! 
! File: g77.info,  Node: Count Intrinsic,  Next: CPU_Time Intrinsic,  Prev: CosH Intrinsic,  Up: Table of Intrinsic Functions
! 
! Count Intrinsic
! ...............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL Count' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: CPU_Time Intrinsic,  Next: CShift Intrinsic,  Prev: Count Intrinsic,  Up: Table of Intrinsic Functions
! 
! CPU_Time Intrinsic
! ..................
! 
!      CALL CPU_Time(SECONDS)
! 
! SECONDS: `REAL'; scalar; INTENT(OUT).
! 
! Intrinsic groups: `f90'.
! 
! Description:
! 
!    Returns in SECONDS the current value of the system time.  This
! implementation of the Fortran 95 intrinsic is just an alias for
! `second' *Note Second Intrinsic (subroutine)::.
! 
!    On some systems, the underlying timings are represented using types
! with sufficiently small limits that overflows (wraparounds) are
! possible, such as 32-bit types.  Therefore, the values returned by this
! intrinsic might be, or become, negative, or numerically less than
! previous values, during a single run of the compiled program.
! 
! 
! File: g77.info,  Node: CShift Intrinsic,  Next: CSin Intrinsic,  Prev: CPU_Time Intrinsic,  Up: Table of Intrinsic Functions
! 
! CShift Intrinsic
! ................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL CShift' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: CSin Intrinsic,  Next: CSqRt Intrinsic,  Prev: CShift Intrinsic,  Up: Table of Intrinsic Functions
! 
! CSin Intrinsic
! ..............
! 
!      CSin(X)
! 
! CSin: `COMPLEX(KIND=1)' function.
! 
! X: `COMPLEX(KIND=1)'; scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Archaic form of `SIN()' that is specific to one type for X.  *Note
! Sin Intrinsic::.
! 
! 
! File: g77.info,  Node: CSqRt Intrinsic,  Next: CTime Intrinsic (subroutine),  Prev: CSin Intrinsic,  Up: Table of Intrinsic Functions
! 
! CSqRt Intrinsic
! ...............
! 
!      CSqRt(X)
! 
! CSqRt: `COMPLEX(KIND=1)' function.
! 
! X: `COMPLEX(KIND=1)'; scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Archaic form of `SQRT()' that is specific to one type for X.  *Note
! SqRt Intrinsic::.
! 
! 
! File: g77.info,  Node: CTime Intrinsic (subroutine),  Next: CTime Intrinsic (function),  Prev: CSqRt Intrinsic,  Up: Table of Intrinsic Functions
! 
! CTime Intrinsic (subroutine)
! ............................
! 
!      CALL CTime(STIME, RESULT)
! 
! STIME: `INTEGER'; scalar; INTENT(IN).
! 
! RESULT: `CHARACTER'; scalar; INTENT(OUT).
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Converts STIME, a system time value, such as returned by `TIME8()',
! to a string of the form `Sat Aug 19 18:13:14 1995', and returns that
! string in RESULT.
! 
!    *Note Time8 Intrinsic::.
! 
!    Some non-GNU implementations of Fortran provide this intrinsic as
! only a function, not as a subroutine.
! 
!    For information on other intrinsics with the same name: *Note CTime
! Intrinsic (function)::.
! 
! 
! File: g77.info,  Node: CTime Intrinsic (function),  Next: DAbs Intrinsic,  Prev: CTime Intrinsic (subroutine),  Up: Table of Intrinsic Functions
! 
! CTime Intrinsic (function)
! ..........................
! 
!      CTime(STIME)
! 
! CTime: `CHARACTER*(*)' function.
! 
! STIME: `INTEGER'; scalar; INTENT(IN).
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Converts STIME, a system time value, such as returned by `TIME8()',
! to a string of the form `Sat Aug 19 18:13:14 1995', and returns that
! string as the function value.
! 
!    *Note Time8 Intrinsic::.
! 
!    For information on other intrinsics with the same name: *Note CTime
! Intrinsic (subroutine)::.
! 
! 
! File: g77.info,  Node: DAbs Intrinsic,  Next: DACos Intrinsic,  Prev: CTime Intrinsic (function),  Up: Table of Intrinsic Functions
! 
! DAbs Intrinsic
! ..............
! 
!      DAbs(A)
! 
! DAbs: `REAL(KIND=2)' function.
! 
! A: `REAL(KIND=2)'; scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Archaic form of `ABS()' that is specific to one type for A.  *Note
! Abs Intrinsic::.
! 
! 
! File: g77.info,  Node: DACos Intrinsic,  Next: DASin Intrinsic,  Prev: DAbs Intrinsic,  Up: Table of Intrinsic Functions
! 
! DACos Intrinsic
! ...............
! 
!      DACos(X)
! 
! DACos: `REAL(KIND=2)' function.
! 
! X: `REAL(KIND=2)'; scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Archaic form of `ACOS()' that is specific to one type for X.  *Note
! ACos Intrinsic::.
! 
! 
! File: g77.info,  Node: DASin Intrinsic,  Next: DATan Intrinsic,  Prev: DACos Intrinsic,  Up: Table of Intrinsic Functions
! 
! DASin Intrinsic
! ...............
! 
!      DASin(X)
! 
! DASin: `REAL(KIND=2)' function.
! 
! X: `REAL(KIND=2)'; scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Archaic form of `ASIN()' that is specific to one type for X.  *Note
! ASin Intrinsic::.
! 
! 
! File: g77.info,  Node: DATan Intrinsic,  Next: DATan2 Intrinsic,  Prev: DASin Intrinsic,  Up: Table of Intrinsic Functions
! 
! DATan Intrinsic
! ...............
! 
!      DATan(X)
! 
! DATan: `REAL(KIND=2)' function.
! 
! X: `REAL(KIND=2)'; scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Archaic form of `ATAN()' that is specific to one type for X.  *Note
! ATan Intrinsic::.
! 
! 
! File: g77.info,  Node: DATan2 Intrinsic,  Next: Date_and_Time Intrinsic,  Prev: DATan Intrinsic,  Up: Table of Intrinsic Functions
! 
! DATan2 Intrinsic
! ................
! 
!      DATan2(Y, X)
! 
! DATan2: `REAL(KIND=2)' function.
! 
! Y: `REAL(KIND=2)'; scalar; INTENT(IN).
! 
! X: `REAL(KIND=2)'; scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Archaic form of `ATAN2()' that is specific to one type for Y and X.
! *Note ATan2 Intrinsic::.
! 
! 
! File: g77.info,  Node: Date_and_Time Intrinsic,  Next: DbesJ0 Intrinsic,  Prev: DATan2 Intrinsic,  Up: Table of Intrinsic Functions
! 
! Date_and_Time Intrinsic
! .......................
! 
!      CALL Date_and_Time(DATE, TIME, ZONE, VALUES)
! 
! DATE: `CHARACTER'; scalar; INTENT(OUT).
! 
! TIME: `CHARACTER'; OPTIONAL; scalar; INTENT(OUT).
! 
! ZONE: `CHARACTER'; OPTIONAL; scalar; INTENT(OUT).
! 
! VALUES: `INTEGER(KIND=1)'; OPTIONAL; DIMENSION(8); INTENT(OUT).
! 
! Intrinsic groups: `f90'.
! 
! Description:
! 
!    Returns:
! DATE
!      The date in the form CCYYMMDD: century, year, month and day;
! 
! TIME
!      The time in the form `HHMMSS.SS': hours, minutes, seconds and
!      milliseconds;
! 
! ZONE
!      The difference between local time and UTC (GMT) in the form SHHMM:
!      sign, hours and minutes, e.g. `-0500' (winter in New York);
! 
! VALUES
!      The year, month of the year, day of the month, time difference in
!      minutes from UTC, hour of the day, minutes of the hour, seconds of
!      the minute, and milliseconds of the second in successive values of
!      the array.
! 
!    Programs making use of this intrinsic might not be Year 10000 (Y10K)
! compliant.  For example, the date might appear, to such programs, to
! wrap around (change from a larger value to a smaller one) as of the
! Year 10000.
! 
!    On systems where a millisecond timer isn't available, the millisecond
! value is returned as zero.
! 
! 
! File: g77.info,  Node: DbesJ0 Intrinsic,  Next: DbesJ1 Intrinsic,  Prev: Date_and_Time Intrinsic,  Up: Table of Intrinsic Functions
! 
! DbesJ0 Intrinsic
! ................
! 
!      DbesJ0(X)
! 
! DbesJ0: `REAL(KIND=2)' function.
! 
! X: `REAL(KIND=2)'; scalar; INTENT(IN).
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Archaic form of `BESJ0()' that is specific to one type for X.  *Note
! BesJ0 Intrinsic::.
! 
! 
! File: g77.info,  Node: DbesJ1 Intrinsic,  Next: DbesJN Intrinsic,  Prev: DbesJ0 Intrinsic,  Up: Table of Intrinsic Functions
! 
! DbesJ1 Intrinsic
! ................
! 
!      DbesJ1(X)
! 
! DbesJ1: `REAL(KIND=2)' function.
! 
! X: `REAL(KIND=2)'; scalar; INTENT(IN).
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Archaic form of `BESJ1()' that is specific to one type for X.  *Note
! BesJ1 Intrinsic::.
! 
! 
! File: g77.info,  Node: DbesJN Intrinsic,  Next: DbesY0 Intrinsic,  Prev: DbesJ1 Intrinsic,  Up: Table of Intrinsic Functions
! 
! DbesJN Intrinsic
! ................
! 
!      DbesJN(N, X)
! 
! DbesJN: `REAL(KIND=2)' function.
! 
! N: `INTEGER' not wider than the default kind; scalar; INTENT(IN).
! 
! X: `REAL(KIND=2)'; scalar; INTENT(IN).
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Archaic form of `BESJN()' that is specific to one type for X.  *Note
! BesJN Intrinsic::.
! 
! 
! File: g77.info,  Node: DbesY0 Intrinsic,  Next: DbesY1 Intrinsic,  Prev: DbesJN Intrinsic,  Up: Table of Intrinsic Functions
! 
! DbesY0 Intrinsic
! ................
! 
!      DbesY0(X)
! 
! DbesY0: `REAL(KIND=2)' function.
! 
! X: `REAL(KIND=2)'; scalar; INTENT(IN).
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Archaic form of `BESY0()' that is specific to one type for X.  *Note
! BesY0 Intrinsic::.
! 
! 
! File: g77.info,  Node: DbesY1 Intrinsic,  Next: DbesYN Intrinsic,  Prev: DbesY0 Intrinsic,  Up: Table of Intrinsic Functions
! 
! DbesY1 Intrinsic
! ................
! 
!      DbesY1(X)
! 
! DbesY1: `REAL(KIND=2)' function.
! 
! X: `REAL(KIND=2)'; scalar; INTENT(IN).
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Archaic form of `BESY1()' that is specific to one type for X.  *Note
! BesY1 Intrinsic::.
! 
! 
! File: g77.info,  Node: DbesYN Intrinsic,  Next: Dble Intrinsic,  Prev: DbesY1 Intrinsic,  Up: Table of Intrinsic Functions
! 
! DbesYN Intrinsic
! ................
! 
!      DbesYN(N, X)
! 
! DbesYN: `REAL(KIND=2)' function.
! 
! N: `INTEGER' not wider than the default kind; scalar; INTENT(IN).
! 
! X: `REAL(KIND=2)'; scalar; INTENT(IN).
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Archaic form of `BESYN()' that is specific to one type for X.  *Note
! BesYN Intrinsic::.
! 
! 
! File: g77.info,  Node: Dble Intrinsic,  Next: DCos Intrinsic,  Prev: DbesYN Intrinsic,  Up: Table of Intrinsic Functions
! 
! Dble Intrinsic
! ..............
! 
!      Dble(A)
! 
! Dble: `REAL(KIND=2)' function.
! 
! A: `INTEGER', `REAL', or `COMPLEX'; scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Returns A converted to double precision (`REAL(KIND=2)').  If A is
! `COMPLEX', the real part of A is used for the conversion and the
! imaginary part disregarded.
! 
!    *Note Sngl Intrinsic::, for the function that converts to single
! precision.
! 
!    *Note Int Intrinsic::, for the function that converts to `INTEGER'.
! 
!    *Note Complex Intrinsic::, for the function that converts to
! `COMPLEX'.
! 
! 
! File: g77.info,  Node: DCos Intrinsic,  Next: DCosH Intrinsic,  Prev: Dble Intrinsic,  Up: Table of Intrinsic Functions
! 
! DCos Intrinsic
! ..............
! 
!      DCos(X)
! 
! DCos: `REAL(KIND=2)' function.
! 
! X: `REAL(KIND=2)'; scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Archaic form of `COS()' that is specific to one type for X.  *Note
! Cos Intrinsic::.
! 
! 
! File: g77.info,  Node: DCosH Intrinsic,  Next: DDiM Intrinsic,  Prev: DCos Intrinsic,  Up: Table of Intrinsic Functions
! 
! DCosH Intrinsic
! ...............
! 
!      DCosH(X)
! 
! DCosH: `REAL(KIND=2)' function.
! 
! X: `REAL(KIND=2)'; scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Archaic form of `COSH()' that is specific to one type for X.  *Note
! CosH Intrinsic::.
! 
! 
! File: g77.info,  Node: DDiM Intrinsic,  Next: DErF Intrinsic,  Prev: DCosH Intrinsic,  Up: Table of Intrinsic Functions
! 
! DDiM Intrinsic
! ..............
! 
!      DDiM(X, Y)
! 
! DDiM: `REAL(KIND=2)' function.
! 
! X: `REAL(KIND=2)'; scalar; INTENT(IN).
! 
! Y: `REAL(KIND=2)'; scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Archaic form of `DIM()' that is specific to one type for X and Y.
! *Note DiM Intrinsic::.
! 
! 
! File: g77.info,  Node: DErF Intrinsic,  Next: DErFC Intrinsic,  Prev: DDiM Intrinsic,  Up: Table of Intrinsic Functions
! 
! DErF Intrinsic
! ..............
! 
!      DErF(X)
! 
! DErF: `REAL(KIND=2)' function.
! 
! X: `REAL(KIND=2)'; scalar; INTENT(IN).
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Archaic form of `ERF()' that is specific to one type for X.  *Note
! ErF Intrinsic::.
! 
! 
! File: g77.info,  Node: DErFC Intrinsic,  Next: DExp Intrinsic,  Prev: DErF Intrinsic,  Up: Table of Intrinsic Functions
! 
! DErFC Intrinsic
! ...............
! 
!      DErFC(X)
! 
! DErFC: `REAL(KIND=2)' function.
! 
! X: `REAL(KIND=2)'; scalar; INTENT(IN).
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Archaic form of `ERFC()' that is specific to one type for X.  *Note
! ErFC Intrinsic::.
! 
! 
! File: g77.info,  Node: DExp Intrinsic,  Next: Digits Intrinsic,  Prev: DErFC Intrinsic,  Up: Table of Intrinsic Functions
! 
! DExp Intrinsic
! ..............
! 
!      DExp(X)
! 
! DExp: `REAL(KIND=2)' function.
! 
! X: `REAL(KIND=2)'; scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Archaic form of `EXP()' that is specific to one type for X.  *Note
! Exp Intrinsic::.
! 
! 
! File: g77.info,  Node: Digits Intrinsic,  Next: DiM Intrinsic,  Prev: DExp Intrinsic,  Up: Table of Intrinsic Functions
! 
! Digits Intrinsic
! ................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL Digits' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: DiM Intrinsic,  Next: DInt Intrinsic,  Prev: Digits Intrinsic,  Up: Table of Intrinsic Functions
! 
! DiM Intrinsic
! .............
! 
!      DiM(X, Y)
! 
! DiM: `INTEGER' or `REAL' function, the exact type being the result of
! cross-promoting the types of all the arguments.
! 
! X: `INTEGER' or `REAL'; scalar; INTENT(IN).
! 
! Y: `INTEGER' or `REAL'; scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Returns `X-Y' if X is greater than Y; otherwise returns zero.
! 
! 
! File: g77.info,  Node: DInt Intrinsic,  Next: DLog Intrinsic,  Prev: DiM Intrinsic,  Up: Table of Intrinsic Functions
! 
! DInt Intrinsic
! ..............
! 
!      DInt(A)
! 
! DInt: `REAL(KIND=2)' function.
! 
! A: `REAL(KIND=2)'; scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Archaic form of `AINT()' that is specific to one type for A.  *Note
! AInt Intrinsic::.
! 
! 
! File: g77.info,  Node: DLog Intrinsic,  Next: DLog10 Intrinsic,  Prev: DInt Intrinsic,  Up: Table of Intrinsic Functions
! 
! DLog Intrinsic
! ..............
! 
!      DLog(X)
! 
! DLog: `REAL(KIND=2)' function.
! 
! X: `REAL(KIND=2)'; scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Archaic form of `LOG()' that is specific to one type for X.  *Note
! Log Intrinsic::.
! 
! 
! File: g77.info,  Node: DLog10 Intrinsic,  Next: DMax1 Intrinsic,  Prev: DLog Intrinsic,  Up: Table of Intrinsic Functions
! 
! DLog10 Intrinsic
! ................
! 
!      DLog10(X)
! 
! DLog10: `REAL(KIND=2)' function.
! 
! X: `REAL(KIND=2)'; scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Archaic form of `LOG10()' that is specific to one type for X.  *Note
! Log10 Intrinsic::.
! 
! 
! File: g77.info,  Node: DMax1 Intrinsic,  Next: DMin1 Intrinsic,  Prev: DLog10 Intrinsic,  Up: Table of Intrinsic Functions
! 
! DMax1 Intrinsic
! ...............
! 
!      DMax1(A-1, A-2, ..., A-n)
! 
! DMax1: `REAL(KIND=2)' function.
! 
! A: `REAL(KIND=2)'; at least two such arguments must be provided;
! scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Archaic form of `MAX()' that is specific to one type for A.  *Note
! Max Intrinsic::.
! 
! 
! File: g77.info,  Node: DMin1 Intrinsic,  Next: DMod Intrinsic,  Prev: DMax1 Intrinsic,  Up: Table of Intrinsic Functions
! 
! DMin1 Intrinsic
! ...............
! 
!      DMin1(A-1, A-2, ..., A-n)
! 
! DMin1: `REAL(KIND=2)' function.
! 
! A: `REAL(KIND=2)'; at least two such arguments must be provided;
! scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Archaic form of `MIN()' that is specific to one type for A.  *Note
! Min Intrinsic::.
! 
! 
! File: g77.info,  Node: DMod Intrinsic,  Next: DNInt Intrinsic,  Prev: DMin1 Intrinsic,  Up: Table of Intrinsic Functions
! 
! DMod Intrinsic
! ..............
! 
!      DMod(A, P)
! 
! DMod: `REAL(KIND=2)' function.
! 
! A: `REAL(KIND=2)'; scalar; INTENT(IN).
! 
! P: `REAL(KIND=2)'; scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Archaic form of `MOD()' that is specific to one type for A.  *Note
! Mod Intrinsic::.
! 
! 
! File: g77.info,  Node: DNInt Intrinsic,  Next: Dot_Product Intrinsic,  Prev: DMod Intrinsic,  Up: Table of Intrinsic Functions
! 
! DNInt Intrinsic
! ...............
! 
!      DNInt(A)
! 
! DNInt: `REAL(KIND=2)' function.
! 
! A: `REAL(KIND=2)'; scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Archaic form of `ANINT()' that is specific to one type for A.  *Note
! ANInt Intrinsic::.
! 
! 
! File: g77.info,  Node: Dot_Product Intrinsic,  Next: DProd Intrinsic,  Prev: DNInt Intrinsic,  Up: Table of Intrinsic Functions
! 
! Dot_Product Intrinsic
! .....................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL Dot_Product' to use this name
! for an external procedure.
! 
! 
! File: g77.info,  Node: DProd Intrinsic,  Next: DSign Intrinsic,  Prev: Dot_Product Intrinsic,  Up: Table of Intrinsic Functions
! 
! DProd Intrinsic
! ...............
! 
!      DProd(X, Y)
! 
! DProd: `REAL(KIND=2)' function.
! 
! X: `REAL(KIND=1)'; scalar; INTENT(IN).
! 
! Y: `REAL(KIND=1)'; scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Returns `DBLE(X)*DBLE(Y)'.
! 
! 
! File: g77.info,  Node: DSign Intrinsic,  Next: DSin Intrinsic,  Prev: DProd Intrinsic,  Up: Table of Intrinsic Functions
! 
! DSign Intrinsic
! ...............
! 
!      DSign(A, B)
! 
! DSign: `REAL(KIND=2)' function.
! 
! A: `REAL(KIND=2)'; scalar; INTENT(IN).
! 
! B: `REAL(KIND=2)'; scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Archaic form of `SIGN()' that is specific to one type for A and B.
! *Note Sign Intrinsic::.
! 
! 
! File: g77.info,  Node: DSin Intrinsic,  Next: DSinH Intrinsic,  Prev: DSign Intrinsic,  Up: Table of Intrinsic Functions
! 
! DSin Intrinsic
! ..............
! 
!      DSin(X)
! 
! DSin: `REAL(KIND=2)' function.
! 
! X: `REAL(KIND=2)'; scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Archaic form of `SIN()' that is specific to one type for X.  *Note
! Sin Intrinsic::.
! 
! 
! File: g77.info,  Node: DSinH Intrinsic,  Next: DSqRt Intrinsic,  Prev: DSin Intrinsic,  Up: Table of Intrinsic Functions
! 
! DSinH Intrinsic
! ...............
! 
!      DSinH(X)
! 
! DSinH: `REAL(KIND=2)' function.
! 
! X: `REAL(KIND=2)'; scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Archaic form of `SINH()' that is specific to one type for X.  *Note
! SinH Intrinsic::.
! 
! 
! File: g77.info,  Node: DSqRt Intrinsic,  Next: DTan Intrinsic,  Prev: DSinH Intrinsic,  Up: Table of Intrinsic Functions
! 
! DSqRt Intrinsic
! ...............
! 
!      DSqRt(X)
! 
! DSqRt: `REAL(KIND=2)' function.
! 
! X: `REAL(KIND=2)'; scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Archaic form of `SQRT()' that is specific to one type for X.  *Note
! SqRt Intrinsic::.
! 
! 
! File: g77.info,  Node: DTan Intrinsic,  Next: DTanH Intrinsic,  Prev: DSqRt Intrinsic,  Up: Table of Intrinsic Functions
! 
! DTan Intrinsic
! ..............
! 
!      DTan(X)
! 
! DTan: `REAL(KIND=2)' function.
! 
! X: `REAL(KIND=2)'; scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Archaic form of `TAN()' that is specific to one type for X.  *Note
! Tan Intrinsic::.
! 
! 
! File: g77.info,  Node: DTanH Intrinsic,  Next: DTime Intrinsic (subroutine),  Prev: DTan Intrinsic,  Up: Table of Intrinsic Functions
! 
! DTanH Intrinsic
! ...............
! 
!      DTanH(X)
! 
! DTanH: `REAL(KIND=2)' function.
! 
! X: `REAL(KIND=2)'; scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Archaic form of `TANH()' that is specific to one type for X.  *Note
! TanH Intrinsic::.
! 
! 
! File: g77.info,  Node: DTime Intrinsic (subroutine),  Next: EOShift Intrinsic,  Prev: DTanH Intrinsic,  Up: Table of Intrinsic Functions
! 
! DTime Intrinsic (subroutine)
! ............................
! 
!      CALL DTime(TARRAY, RESULT)
! 
! TARRAY: `REAL(KIND=1)'; DIMENSION(2); INTENT(OUT).
! 
! RESULT: `REAL(KIND=1)'; scalar; INTENT(OUT).
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Initially, return the number of seconds of runtime since the start
! of the process's execution in RESULT, and the user and system
! components of this in `TARRAY(1)' and `TARRAY(2)' respectively.  The
! value of RESULT is equal to `TARRAY(1) + TARRAY(2)'.
! 
!    Subsequent invocations of `DTIME()' set values based on accumulations
! since the previous invocation.
! 
!    On some systems, the underlying timings are represented using types
! with sufficiently small limits that overflows (wraparounds) are
! possible, such as 32-bit types.  Therefore, the values returned by this
! intrinsic might be, or become, negative, or numerically less than
! previous values, during a single run of the compiled program.
! 
!    Some non-GNU implementations of Fortran provide this intrinsic as
! only a function, not as a subroutine.
! 
!    For information on other intrinsics with the same name: *Note DTime
! Intrinsic (function)::.
! 
! 
! File: g77.info,  Node: EOShift Intrinsic,  Next: Epsilon Intrinsic,  Prev: DTime Intrinsic (subroutine),  Up: Table of Intrinsic Functions
! 
! EOShift Intrinsic
! .................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL EOShift' to use this name for
! an external procedure.
! 
! 
! File: g77.info,  Node: Epsilon Intrinsic,  Next: ErF Intrinsic,  Prev: EOShift Intrinsic,  Up: Table of Intrinsic Functions
! 
! Epsilon Intrinsic
! .................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL Epsilon' to use this name for
! an external procedure.
! 
! 
! File: g77.info,  Node: ErF Intrinsic,  Next: ErFC Intrinsic,  Prev: Epsilon Intrinsic,  Up: Table of Intrinsic Functions
! 
! ErF Intrinsic
! .............
! 
!      ErF(X)
! 
! ErF: `REAL' function, the `KIND=' value of the type being that of
! argument X.
! 
! X: `REAL'; scalar; INTENT(IN).
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Returns the error function of X.  See `erf(3m)', which provides the
! implementation.
! 
! 
! File: g77.info,  Node: ErFC Intrinsic,  Next: ETime Intrinsic (subroutine),  Prev: ErF Intrinsic,  Up: Table of Intrinsic Functions
! 
! ErFC Intrinsic
! ..............
! 
!      ErFC(X)
! 
! ErFC: `REAL' function, the `KIND=' value of the type being that of
! argument X.
! 
! X: `REAL'; scalar; INTENT(IN).
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Returns the complementary error function of X: `ERFC(R) = 1 -
! ERF(R)' (except that the result might be more accurate than explicitly
! evaluating that formulae would give).  See `erfc(3m)', which provides
! the implementation.
! 
! 
! File: g77.info,  Node: ETime Intrinsic (subroutine),  Next: ETime Intrinsic (function),  Prev: ErFC Intrinsic,  Up: Table of Intrinsic Functions
! 
! ETime Intrinsic (subroutine)
! ............................
! 
!      CALL ETime(TARRAY, RESULT)
! 
! TARRAY: `REAL(KIND=1)'; DIMENSION(2); INTENT(OUT).
! 
! RESULT: `REAL(KIND=1)'; scalar; INTENT(OUT).
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Return the number of seconds of runtime since the start of the
! process's execution in RESULT, and the user and system components of
! this in `TARRAY(1)' and `TARRAY(2)' respectively.  The value of RESULT
! is equal to `TARRAY(1) + TARRAY(2)'.
! 
!    On some systems, the underlying timings are represented using types
! with sufficiently small limits that overflows (wraparounds) are
! possible, such as 32-bit types.  Therefore, the values returned by this
! intrinsic might be, or become, negative, or numerically less than
! previous values, during a single run of the compiled program.
! 
!    Some non-GNU implementations of Fortran provide this intrinsic as
! only a function, not as a subroutine.
! 
!    For information on other intrinsics with the same name: *Note ETime
! Intrinsic (function)::.
! 
! 
! File: g77.info,  Node: ETime Intrinsic (function),  Next: Exit Intrinsic,  Prev: ETime Intrinsic (subroutine),  Up: Table of Intrinsic Functions
! 
! ETime Intrinsic (function)
! ..........................
! 
!      ETime(TARRAY)
! 
! ETime: `REAL(KIND=1)' function.
! 
! TARRAY: `REAL(KIND=1)'; DIMENSION(2); INTENT(OUT).
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Return the number of seconds of runtime since the start of the
! process's execution as the function value, and the user and system
! components of this in `TARRAY(1)' and `TARRAY(2)' respectively.  The
! functions' value is equal to `TARRAY(1) + TARRAY(2)'.
! 
!    On some systems, the underlying timings are represented using types
! with sufficiently small limits that overflows (wraparounds) are
! possible, such as 32-bit types.  Therefore, the values returned by this
! intrinsic might be, or become, negative, or numerically less than
! previous values, during a single run of the compiled program.
! 
!    For information on other intrinsics with the same name: *Note ETime
! Intrinsic (subroutine)::.
! 
! 
! File: g77.info,  Node: Exit Intrinsic,  Next: Exp Intrinsic,  Prev: ETime Intrinsic (function),  Up: Table of Intrinsic Functions
! 
! Exit Intrinsic
! ..............
! 
!      CALL Exit(STATUS)
! 
! STATUS: `INTEGER' not wider than the default kind; OPTIONAL; scalar;
! INTENT(IN).
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Exit the program with status STATUS after closing open Fortran I/O
! units and otherwise behaving as `exit(2)'.  If STATUS is omitted the
! canonical `success' value will be returned to the system.
! 
! 
! File: g77.info,  Node: Exp Intrinsic,  Next: Exponent Intrinsic,  Prev: Exit Intrinsic,  Up: Table of Intrinsic Functions
! 
! Exp Intrinsic
! .............
! 
!      Exp(X)
! 
! Exp: `REAL' or `COMPLEX' function, the exact type being that of
! argument X.
! 
! X: `REAL' or `COMPLEX'; scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Returns `E**X', where E is approximately 2.7182818.
! 
!    *Note Log Intrinsic::, for the inverse of this function.
! 
! 
! File: g77.info,  Node: Exponent Intrinsic,  Next: FDate Intrinsic (subroutine),  Prev: Exp Intrinsic,  Up: Table of Intrinsic Functions
! 
! Exponent Intrinsic
! ..................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL Exponent' to use this name for
! an external procedure.
! 
! 
! File: g77.info,  Node: FDate Intrinsic (subroutine),  Next: FDate Intrinsic (function),  Prev: Exponent Intrinsic,  Up: Table of Intrinsic Functions
! 
! FDate Intrinsic (subroutine)
! ............................
! 
!      CALL FDate(DATE)
! 
! DATE: `CHARACTER'; scalar; INTENT(OUT).
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Returns the current date (using the same format as `CTIME()') in
! DATE.
! 
!    Equivalent to:
! 
!      CALL CTIME(DATE, TIME8())
! 
!    Programs making use of this intrinsic might not be Year 10000 (Y10K)
! compliant.  For example, the date might appear, to such programs, to
! wrap around (change from a larger value to a smaller one) as of the
! Year 10000.
! 
!    *Note CTime Intrinsic (subroutine)::.
! 
!    Some non-GNU implementations of Fortran provide this intrinsic as
! only a function, not as a subroutine.
! 
!    For information on other intrinsics with the same name: *Note FDate
! Intrinsic (function)::.
! 
! 
! File: g77.info,  Node: FDate Intrinsic (function),  Next: FGet Intrinsic (subroutine),  Prev: FDate Intrinsic (subroutine),  Up: Table of Intrinsic Functions
! 
! FDate Intrinsic (function)
! ..........................
! 
!      FDate()
! 
! FDate: `CHARACTER*(*)' function.
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Returns the current date (using the same format as `CTIME()').
! 
!    Equivalent to:
! 
!      CTIME(TIME8())
! 
!    Programs making use of this intrinsic might not be Year 10000 (Y10K)
! compliant.  For example, the date might appear, to such programs, to
! wrap around (change from a larger value to a smaller one) as of the
! Year 10000.
! 
!    *Note CTime Intrinsic (function)::.
! 
!    For information on other intrinsics with the same name: *Note FDate
! Intrinsic (subroutine)::.
! 
! 
! File: g77.info,  Node: FGet Intrinsic (subroutine),  Next: FGetC Intrinsic (subroutine),  Prev: FDate Intrinsic (function),  Up: Table of Intrinsic Functions
! 
! FGet Intrinsic (subroutine)
! ...........................
! 
!      CALL FGet(C, STATUS)
! 
! C: `CHARACTER'; scalar; INTENT(OUT).
! 
! STATUS: `INTEGER(KIND=1)'; OPTIONAL; scalar; INTENT(OUT).
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Reads a single character into C in stream mode from unit 5
! (by-passing normal formatted output) using `getc(3)'.  Returns in
! STATUS 0 on success, -1 on end-of-file, and the error code from
! `ferror(3)' otherwise.
! 
!    Stream I/O should not be mixed with normal record-oriented
! (formatted or unformatted) I/O on the same unit; the results are
! unpredictable.
! 
!    For information on other intrinsics with the same name: *Note FGet
! Intrinsic (function)::.
! 
! 
! File: g77.info,  Node: FGetC Intrinsic (subroutine),  Next: Float Intrinsic,  Prev: FGet Intrinsic (subroutine),  Up: Table of Intrinsic Functions
! 
! FGetC Intrinsic (subroutine)
! ............................
! 
!      CALL FGetC(UNIT, C, STATUS)
! 
! UNIT: `INTEGER'; scalar; INTENT(IN).
! 
! C: `CHARACTER'; scalar; INTENT(OUT).
! 
! STATUS: `INTEGER(KIND=1)'; OPTIONAL; scalar; INTENT(OUT).
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Reads a single character into C in stream mode from unit UNIT
! (by-passing normal formatted output) using `getc(3)'.  Returns in
! STATUS 0 on success, -1 on end-of-file, and the error code from
! `ferror(3)' otherwise.
! 
!    Stream I/O should not be mixed with normal record-oriented
! (formatted or unformatted) I/O on the same unit; the results are
! unpredictable.
! 
!    For information on other intrinsics with the same name: *Note FGetC
! Intrinsic (function)::.
! 
! 
! File: g77.info,  Node: Float Intrinsic,  Next: Floor Intrinsic,  Prev: FGetC Intrinsic (subroutine),  Up: Table of Intrinsic Functions
! 
! Float Intrinsic
! ...............
! 
!      Float(A)
! 
! Float: `REAL(KIND=1)' function.
! 
! A: `INTEGER'; scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Archaic form of `REAL()' that is specific to one type for A.  *Note
! Real Intrinsic::.
! 
! 
! File: g77.info,  Node: Floor Intrinsic,  Next: Flush Intrinsic,  Prev: Float Intrinsic,  Up: Table of Intrinsic Functions
! 
! Floor Intrinsic
! ...............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL Floor' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: Flush Intrinsic,  Next: FNum Intrinsic,  Prev: Floor Intrinsic,  Up: Table of Intrinsic Functions
! 
! Flush Intrinsic
! ...............
! 
!      CALL Flush(UNIT)
! 
! UNIT: `INTEGER'; OPTIONAL; scalar; INTENT(IN).
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Flushes Fortran unit(s) currently open for output.  Without the
! optional argument, all such units are flushed, otherwise just the unit
! specified by UNIT.
! 
!    Some non-GNU implementations of Fortran provide this intrinsic as a
! library procedure that might or might not support the (optional) UNIT
! argument.
! 
! 
! File: g77.info,  Node: FNum Intrinsic,  Next: FPut Intrinsic (subroutine),  Prev: Flush Intrinsic,  Up: Table of Intrinsic Functions
! 
! FNum Intrinsic
! ..............
! 
!      FNum(UNIT)
! 
! FNum: `INTEGER(KIND=1)' function.
! 
! UNIT: `INTEGER'; scalar; INTENT(IN).
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Returns the Unix file descriptor number corresponding to the open
! Fortran I/O unit UNIT.  This could be passed to an interface to C I/O
! routines.
! 
! 
! File: g77.info,  Node: FPut Intrinsic (subroutine),  Next: FPutC Intrinsic (subroutine),  Prev: FNum Intrinsic,  Up: Table of Intrinsic Functions
! 
! FPut Intrinsic (subroutine)
! ...........................
! 
!      CALL FPut(C, STATUS)
! 
! C: `CHARACTER'; scalar; INTENT(IN).
! 
! STATUS: `INTEGER(KIND=1)'; OPTIONAL; scalar; INTENT(OUT).
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Writes the single character C in stream mode to unit 6 (by-passing
! normal formatted output) using `putc(3)'.  Returns in STATUS 0 on
! success, the error code from `ferror(3)' otherwise.
! 
!    Stream I/O should not be mixed with normal record-oriented
! (formatted or unformatted) I/O on the same unit; the results are
! unpredictable.
! 
!    For information on other intrinsics with the same name: *Note FPut
! Intrinsic (function)::.
! 
! 
! File: g77.info,  Node: FPutC Intrinsic (subroutine),  Next: Fraction Intrinsic,  Prev: FPut Intrinsic (subroutine),  Up: Table of Intrinsic Functions
! 
! FPutC Intrinsic (subroutine)
! ............................
! 
!      CALL FPutC(UNIT, C, STATUS)
! 
! UNIT: `INTEGER'; scalar; INTENT(IN).
! 
! C: `CHARACTER'; scalar; INTENT(IN).
! 
! STATUS: `INTEGER(KIND=1)'; OPTIONAL; scalar; INTENT(OUT).
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Writes the single character UNIT in stream mode to unit 6
! (by-passing normal formatted output) using `putc(3)'.  Returns in C 0
! on success, the error code from `ferror(3)' otherwise.
! 
!    Stream I/O should not be mixed with normal record-oriented
! (formatted or unformatted) I/O on the same unit; the results are
! unpredictable.
! 
!    For information on other intrinsics with the same name: *Note FPutC
! Intrinsic (function)::.
! 
! 
! File: g77.info,  Node: Fraction Intrinsic,  Next: FSeek Intrinsic,  Prev: FPutC Intrinsic (subroutine),  Up: Table of Intrinsic Functions
! 
! Fraction Intrinsic
! ..................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL Fraction' to use this name for
! an external procedure.
! 
! 
! File: g77.info,  Node: FSeek Intrinsic,  Next: FStat Intrinsic (subroutine),  Prev: Fraction Intrinsic,  Up: Table of Intrinsic Functions
! 
! FSeek Intrinsic
! ...............
! 
!      CALL FSeek(UNIT, OFFSET, WHENCE, ERRLAB)
! 
! UNIT: `INTEGER'; scalar; INTENT(IN).
! 
! OFFSET: `INTEGER'; scalar; INTENT(IN).
! 
! WHENCE: `INTEGER'; scalar; INTENT(IN).
! 
! ERRLAB: `*LABEL', where LABEL is the label of an executable statement;
! OPTIONAL.
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Attempts to move Fortran unit UNIT to the specified OFFSET: absolute
! offset if WHENCE=0; relative to the current offset if WHENCE=1;
! relative to the end of the file if WHENCE=2.  It branches to label
! ERRLAB if UNIT is not open or if the call otherwise fails.
! 
! 
! File: g77.info,  Node: FStat Intrinsic (subroutine),  Next: FStat Intrinsic (function),  Prev: FSeek Intrinsic,  Up: Table of Intrinsic Functions
! 
! FStat Intrinsic (subroutine)
! ............................
! 
!      CALL FStat(UNIT, SARRAY, STATUS)
! 
! UNIT: `INTEGER'; scalar; INTENT(IN).
! 
! SARRAY: `INTEGER(KIND=1)'; DIMENSION(13); INTENT(OUT).
! 
! STATUS: `INTEGER(KIND=1)'; OPTIONAL; scalar; INTENT(OUT).
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Obtains data about the file open on Fortran I/O unit UNIT and places
! them in the array SARRAY.  The values in this array are extracted from
! the `stat' structure as returned by `fstat(2)' q.v., as follows:
! 
!   1. Device ID
! 
!   2. Inode number
! 
!   3. File mode
! 
!   4. Number of links
! 
!   5. Owner's uid
! 
!   6. Owner's gid
! 
!   7. ID of device containing directory entry for file (0 if not
!      available)
! 
!   8. File size (bytes)
! 
!   9. Last access time
! 
!  10. Last modification time
! 
!  11. Last file status change time
! 
!  12. Preferred I/O block size (-1 if not available)
! 
!  13. Number of blocks allocated (-1 if not available)
! 
!    Not all these elements are relevant on all systems.  If an element
! is not relevant, it is returned as 0.
! 
!    If the STATUS argument is supplied, it contains 0 on success or a
! nonzero error code upon return.
! 
!    Some non-GNU implementations of Fortran provide this intrinsic as
! only a function, not as a subroutine, or do not support the (optional)
! STATUS argument.
! 
!    For information on other intrinsics with the same name: *Note FStat
! Intrinsic (function)::.
! 
! 
! File: g77.info,  Node: FStat Intrinsic (function),  Next: FTell Intrinsic (subroutine),  Prev: FStat Intrinsic (subroutine),  Up: Table of Intrinsic Functions
! 
! FStat Intrinsic (function)
! ..........................
! 
!      FStat(UNIT, SARRAY)
! 
! FStat: `INTEGER(KIND=1)' function.
! 
! UNIT: `INTEGER'; scalar; INTENT(IN).
! 
! SARRAY: `INTEGER(KIND=1)'; DIMENSION(13); INTENT(OUT).
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Obtains data about the file open on Fortran I/O unit UNIT and places
! them in the array SARRAY.  The values in this array are extracted from
! the `stat' structure as returned by `fstat(2)' q.v., as follows:
! 
!   1. Device ID
! 
!   2. Inode number
! 
!   3. File mode
! 
!   4. Number of links
! 
!   5. Owner's uid
! 
!   6. Owner's gid
! 
!   7. ID of device containing directory entry for file (0 if not
!      available)
! 
!   8. File size (bytes)
! 
!   9. Last access time
! 
!  10. Last modification time
! 
!  11. Last file status change time
! 
!  12. Preferred I/O block size (-1 if not available)
! 
!  13. Number of blocks allocated (-1 if not available)
! 
!    Not all these elements are relevant on all systems.  If an element
! is not relevant, it is returned as 0.
! 
!    Returns 0 on success or a nonzero error code.
! 
!    For information on other intrinsics with the same name: *Note FStat
! Intrinsic (subroutine)::.
! 
! 
! File: g77.info,  Node: FTell Intrinsic (subroutine),  Next: FTell Intrinsic (function),  Prev: FStat Intrinsic (function),  Up: Table of Intrinsic Functions
! 
! FTell Intrinsic (subroutine)
! ............................
! 
!      CALL FTell(UNIT, OFFSET)
! 
! UNIT: `INTEGER'; scalar; INTENT(IN).
! 
! OFFSET: `INTEGER(KIND=1)'; scalar; INTENT(OUT).
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Sets OFFSET to the current offset of Fortran unit UNIT (or to -1 if
! UNIT is not open).
! 
!    Some non-GNU implementations of Fortran provide this intrinsic as
! only a function, not as a subroutine.
! 
!    For information on other intrinsics with the same name: *Note FTell
! Intrinsic (function)::.
! 
! 
! File: g77.info,  Node: FTell Intrinsic (function),  Next: GError Intrinsic,  Prev: FTell Intrinsic (subroutine),  Up: Table of Intrinsic Functions
! 
! FTell Intrinsic (function)
! ..........................
! 
!      FTell(UNIT)
! 
! FTell: `INTEGER(KIND=1)' function.
! 
! UNIT: `INTEGER'; scalar; INTENT(IN).
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Returns the current offset of Fortran unit UNIT (or -1 if UNIT is
! not open).
! 
!    For information on other intrinsics with the same name: *Note FTell
! Intrinsic (subroutine)::.
! 
! 
! File: g77.info,  Node: GError Intrinsic,  Next: GetArg Intrinsic,  Prev: FTell Intrinsic (function),  Up: Table of Intrinsic Functions
! 
! GError Intrinsic
! ................
! 
!      CALL GError(MESSAGE)
! 
! MESSAGE: `CHARACTER'; scalar; INTENT(OUT).
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Returns the system error message corresponding to the last system
! error (C `errno').
! 
! 
! File: g77.info,  Node: GetArg Intrinsic,  Next: GetCWD Intrinsic (subroutine),  Prev: GError Intrinsic,  Up: Table of Intrinsic Functions
! 
! GetArg Intrinsic
! ................
! 
!      CALL GetArg(POS, VALUE)
! 
! POS: `INTEGER' not wider than the default kind; scalar; INTENT(IN).
! 
! VALUE: `CHARACTER'; scalar; INTENT(OUT).
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Sets VALUE to the POS-th command-line argument (or to all blanks if
! there are fewer than VALUE command-line arguments); `CALL GETARG(0,
! VALUE)' sets VALUE to the name of the program (on systems that support
! this feature).
! 
!    *Note IArgC Intrinsic::, for information on how to get the number of
! arguments.
! 
! 
! File: g77.info,  Node: GetCWD Intrinsic (subroutine),  Next: GetCWD Intrinsic (function),  Prev: GetArg Intrinsic,  Up: Table of Intrinsic Functions
! 
! GetCWD Intrinsic (subroutine)
! .............................
! 
!      CALL GetCWD(NAME, STATUS)
! 
! NAME: `CHARACTER'; scalar; INTENT(OUT).
! 
! STATUS: `INTEGER(KIND=1)'; OPTIONAL; scalar; INTENT(OUT).
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Places the current working directory in NAME.  If the STATUS
! argument is supplied, it contains 0 success or a nonzero error code
! upon return (`ENOSYS' if the system does not provide `getcwd(3)' or
! `getwd(3)').
! 
!    Some non-GNU implementations of Fortran provide this intrinsic as
! only a function, not as a subroutine, or do not support the (optional)
! STATUS argument.
! 
!    For information on other intrinsics with the same name: *Note GetCWD
! Intrinsic (function)::.
! 
! 
! File: g77.info,  Node: GetCWD Intrinsic (function),  Next: GetEnv Intrinsic,  Prev: GetCWD Intrinsic (subroutine),  Up: Table of Intrinsic Functions
! 
! GetCWD Intrinsic (function)
! ...........................
! 
!      GetCWD(NAME)
! 
! GetCWD: `INTEGER(KIND=1)' function.
! 
! NAME: `CHARACTER'; scalar; INTENT(OUT).
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Places the current working directory in NAME.  Returns 0 on success,
! otherwise a nonzero error code (`ENOSYS' if the system does not provide
! `getcwd(3)' or `getwd(3)').
! 
!    For information on other intrinsics with the same name: *Note GetCWD
! Intrinsic (subroutine)::.
! 
! 
! File: g77.info,  Node: GetEnv Intrinsic,  Next: GetGId Intrinsic,  Prev: GetCWD Intrinsic (function),  Up: Table of Intrinsic Functions
! 
! GetEnv Intrinsic
! ................
! 
!      CALL GetEnv(NAME, VALUE)
! 
! NAME: `CHARACTER'; scalar; INTENT(IN).
! 
! VALUE: `CHARACTER'; scalar; INTENT(OUT).
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Sets VALUE to the value of environment variable given by the value
! of NAME (`$name' in shell terms) or to blanks if `$name' has not been
! set.  A null character (`CHAR(0)') marks the end of the name in
! NAME--otherwise, trailing blanks in NAME are ignored.
! 
! 
! File: g77.info,  Node: GetGId Intrinsic,  Next: GetLog Intrinsic,  Prev: GetEnv Intrinsic,  Up: Table of Intrinsic Functions
! 
! GetGId Intrinsic
! ................
! 
!      GetGId()
! 
! GetGId: `INTEGER(KIND=1)' function.
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Returns the group id for the current process.
! 
! 
! File: g77.info,  Node: GetLog Intrinsic,  Next: GetPId Intrinsic,  Prev: GetGId Intrinsic,  Up: Table of Intrinsic Functions
! 
! GetLog Intrinsic
! ................
! 
!      CALL GetLog(LOGIN)
! 
! LOGIN: `CHARACTER'; scalar; INTENT(OUT).
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Returns the login name for the process in LOGIN.
! 
!    _Caution:_ On some systems, the `getlogin(3)' function, which this
! intrinsic calls at run time, is either not implemented or returns a
! null pointer.  In the latter case, this intrinsic returns blanks in
! LOGIN.
! 
! 
! File: g77.info,  Node: GetPId Intrinsic,  Next: GetUId Intrinsic,  Prev: GetLog Intrinsic,  Up: Table of Intrinsic Functions
! 
! GetPId Intrinsic
! ................
! 
!      GetPId()
! 
! GetPId: `INTEGER(KIND=1)' function.
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Returns the process id for the current process.
! 
! 
! File: g77.info,  Node: GetUId Intrinsic,  Next: GMTime Intrinsic,  Prev: GetPId Intrinsic,  Up: Table of Intrinsic Functions
! 
! GetUId Intrinsic
! ................
! 
!      GetUId()
! 
! GetUId: `INTEGER(KIND=1)' function.
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Returns the user id for the current process.
! 
! 
! File: g77.info,  Node: GMTime Intrinsic,  Next: HostNm Intrinsic (subroutine),  Prev: GetUId Intrinsic,  Up: Table of Intrinsic Functions
! 
! GMTime Intrinsic
! ................
! 
!      CALL GMTime(STIME, TARRAY)
! 
! STIME: `INTEGER(KIND=1)'; scalar; INTENT(IN).
! 
! TARRAY: `INTEGER(KIND=1)'; DIMENSION(9); INTENT(OUT).
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Given a system time value STIME, fills TARRAY with values extracted
! from it appropriate to the GMT time zone using `gmtime(3)'.
! 
!    The array elements are as follows:
! 
!   1. Seconds after the minute, range 0-59 or 0-61 to allow for leap
!      seconds
! 
!   2. Minutes after the hour, range 0-59
! 
!   3. Hours past midnight, range 0-23
! 
!   4. Day of month, range 0-31
! 
!   5. Number of months since January, range 0-12
! 
!   6. Years since 1900
! 
!   7. Number of days since Sunday, range 0-6
! 
!   8. Days since January 1
! 
!   9. Daylight savings indicator: positive if daylight savings is in
!      effect, zero if not, and negative if the information isn't
!      available.
! 
! 
! File: g77.info,  Node: HostNm Intrinsic (subroutine),  Next: HostNm Intrinsic (function),  Prev: GMTime Intrinsic,  Up: Table of Intrinsic Functions
! 
! HostNm Intrinsic (subroutine)
! .............................
! 
!      CALL HostNm(NAME, STATUS)
! 
! NAME: `CHARACTER'; scalar; INTENT(OUT).
! 
! STATUS: `INTEGER(KIND=1)'; OPTIONAL; scalar; INTENT(OUT).
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Fills NAME with the system's host name returned by `gethostname(2)'.
! If the STATUS argument is supplied, it contains 0 on success or a
! nonzero error code upon return (`ENOSYS' if the system does not provide
! `gethostname(2)').
! 
!    Some non-GNU implementations of Fortran provide this intrinsic as
! only a function, not as a subroutine, or do not support the (optional)
! STATUS argument.
! 
!    On some systems (specifically SCO) it might be necessary to link the
! "socket" library if you call this routine.  Typically this means adding
! `-lg2c -lsocket -lm' to the `g77' command line when linking the program.
! 
!    For information on other intrinsics with the same name: *Note HostNm
! Intrinsic (function)::.
! 
! 
! File: g77.info,  Node: HostNm Intrinsic (function),  Next: Huge Intrinsic,  Prev: HostNm Intrinsic (subroutine),  Up: Table of Intrinsic Functions
! 
! HostNm Intrinsic (function)
! ...........................
! 
!      HostNm(NAME)
! 
! HostNm: `INTEGER(KIND=1)' function.
! 
! NAME: `CHARACTER'; scalar; INTENT(OUT).
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Fills NAME with the system's host name returned by `gethostname(2)',
! returning 0 on success or a nonzero error code (`ENOSYS' if the system
! does not provide `gethostname(2)').
! 
!    On some systems (specifically SCO) it might be necessary to link the
! "socket" library if you call this routine.  Typically this means adding
! `-lg2c -lsocket -lm' to the `g77' command line when linking the program.
! 
!    For information on other intrinsics with the same name: *Note HostNm
! Intrinsic (subroutine)::.
! 
! 
! File: g77.info,  Node: Huge Intrinsic,  Next: IAbs Intrinsic,  Prev: HostNm Intrinsic (function),  Up: Table of Intrinsic Functions
! 
! Huge Intrinsic
! ..............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL Huge' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: IAbs Intrinsic,  Next: IAChar Intrinsic,  Prev: Huge Intrinsic,  Up: Table of Intrinsic Functions
! 
! IAbs Intrinsic
! ..............
! 
!      IAbs(A)
! 
! IAbs: `INTEGER(KIND=1)' function.
! 
! A: `INTEGER(KIND=1)'; scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Archaic form of `ABS()' that is specific to one type for A.  *Note
! Abs Intrinsic::.
! 
! 
! File: g77.info,  Node: IAChar Intrinsic,  Next: IAnd Intrinsic,  Prev: IAbs Intrinsic,  Up: Table of Intrinsic Functions
! 
! IAChar Intrinsic
! ................
! 
!      IAChar(C)
! 
! IAChar: `INTEGER(KIND=1)' function.
! 
! C: `CHARACTER'; scalar; INTENT(IN).
! 
! Intrinsic groups: `f2c', `f90'.
! 
! Description:
! 
!    Returns the code for the ASCII character in the first character
! position of C.
! 
!    *Note AChar Intrinsic::, for the inverse of this function.
! 
!    *Note IChar Intrinsic::, for the function corresponding to the
! system's native character set.
! 
! 
! File: g77.info,  Node: IAnd Intrinsic,  Next: IArgC Intrinsic,  Prev: IAChar Intrinsic,  Up: Table of Intrinsic Functions
! 
! IAnd Intrinsic
! ..............
! 
!      IAnd(I, J)
! 
! IAnd: `INTEGER' function, the exact type being the result of
! cross-promoting the types of all the arguments.
! 
! I: `INTEGER'; scalar; INTENT(IN).
! 
! J: `INTEGER'; scalar; INTENT(IN).
! 
! Intrinsic groups: `mil', `f90', `vxt'.
! 
! Description:
! 
!    Returns value resulting from boolean AND of pair of bits in each of
! I and J.
! 
! 
! File: g77.info,  Node: IArgC Intrinsic,  Next: IBClr Intrinsic,  Prev: IAnd Intrinsic,  Up: Table of Intrinsic Functions
! 
! IArgC Intrinsic
! ...............
! 
!      IArgC()
! 
! IArgC: `INTEGER(KIND=1)' function.
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Returns the number of command-line arguments.
! 
!    This count does not include the specification of the program name
! itself.
! 
! 
! File: g77.info,  Node: IBClr Intrinsic,  Next: IBits Intrinsic,  Prev: IArgC Intrinsic,  Up: Table of Intrinsic Functions
! 
! IBClr Intrinsic
! ...............
! 
!      IBClr(I, POS)
! 
! IBClr: `INTEGER' function, the `KIND=' value of the type being that of
! argument I.
! 
! I: `INTEGER'; scalar; INTENT(IN).
! 
! POS: `INTEGER'; scalar; INTENT(IN).
! 
! Intrinsic groups: `mil', `f90', `vxt'.
! 
! Description:
! 
!    Returns the value of I with bit POS cleared (set to zero).  *Note
! BTest Intrinsic::, for information on bit positions.
! 
! 
! File: g77.info,  Node: IBits Intrinsic,  Next: IBSet Intrinsic,  Prev: IBClr Intrinsic,  Up: Table of Intrinsic Functions
! 
! IBits Intrinsic
! ...............
! 
!      IBits(I, POS, LEN)
! 
! IBits: `INTEGER' function, the `KIND=' value of the type being that of
! argument I.
! 
! I: `INTEGER'; scalar; INTENT(IN).
! 
! POS: `INTEGER'; scalar; INTENT(IN).
! 
! LEN: `INTEGER'; scalar; INTENT(IN).
! 
! Intrinsic groups: `mil', `f90', `vxt'.
! 
! Description:
! 
!    Extracts a subfield of length LEN from I, starting from bit position
! POS and extending left for LEN bits.  The result is right-justified and
! the remaining bits are zeroed.  The value of `POS+LEN' must be less
! than or equal to the value `BIT_SIZE(I)'.  *Note Bit_Size Intrinsic::.
! 
! 
! File: g77.info,  Node: IBSet Intrinsic,  Next: IChar Intrinsic,  Prev: IBits Intrinsic,  Up: Table of Intrinsic Functions
! 
! IBSet Intrinsic
! ...............
! 
!      IBSet(I, POS)
! 
! IBSet: `INTEGER' function, the `KIND=' value of the type being that of
! argument I.
! 
! I: `INTEGER'; scalar; INTENT(IN).
! 
! POS: `INTEGER'; scalar; INTENT(IN).
! 
! Intrinsic groups: `mil', `f90', `vxt'.
! 
! Description:
! 
!    Returns the value of I with bit POS set (to one).  *Note BTest
! Intrinsic::, for information on bit positions.
! 
! 
! File: g77.info,  Node: IChar Intrinsic,  Next: IDate Intrinsic (UNIX),  Prev: IBSet Intrinsic,  Up: Table of Intrinsic Functions
! 
! IChar Intrinsic
! ...............
! 
!      IChar(C)
! 
! IChar: `INTEGER(KIND=1)' function.
! 
! C: `CHARACTER'; scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Returns the code for the character in the first character position
! of C.
! 
!    Because the system's native character set is used, the
! correspondence between character and their codes is not necessarily the
! same between GNU Fortran implementations.
! 
!    Note that no intrinsic exists to convert a printable character
! string to a numerical value.  For example, there is no intrinsic that,
! given the `CHARACTER' value `'154'', returns an `INTEGER' or `REAL'
! value with the value `154'.
! 
!    Instead, you can use internal-file I/O to do this kind of conversion.
! For example:
! 
!      INTEGER VALUE
!      CHARACTER*10 STRING
!      STRING = '154'
!      READ (STRING, '(I10)'), VALUE
!      PRINT *, VALUE
!      END
! 
!    The above program, when run, prints:
! 
!       154
! 
!    *Note Char Intrinsic::, for the inverse of the `ICHAR' function.
! 
!    *Note IAChar Intrinsic::, for the function corresponding to the
! ASCII character set.
! 
! 
! File: g77.info,  Node: IDate Intrinsic (UNIX),  Next: IDiM Intrinsic,  Prev: IChar Intrinsic,  Up: Table of Intrinsic Functions
! 
! IDate Intrinsic (UNIX)
! ......................
! 
!      CALL IDate(TARRAY)
! 
! TARRAY: `INTEGER(KIND=1)'; DIMENSION(3); INTENT(OUT).
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Fills TARRAY with the numerical values at the current local time of
! day, month (in the range 1-12), and year in elements 1, 2, and 3,
! respectively.  The year has four significant digits.
! 
!    Programs making use of this intrinsic might not be Year 10000 (Y10K)
! compliant.  For example, the date might appear, to such programs, to
! wrap around (change from a larger value to a smaller one) as of the
! Year 10000.
! 
!    For information on other intrinsics with the same name: *Note IDate
! Intrinsic (VXT)::.
! 
! 
! File: g77.info,  Node: IDiM Intrinsic,  Next: IDInt Intrinsic,  Prev: IDate Intrinsic (UNIX),  Up: Table of Intrinsic Functions
! 
! IDiM Intrinsic
! ..............
! 
!      IDiM(X, Y)
! 
! IDiM: `INTEGER(KIND=1)' function.
! 
! X: `INTEGER(KIND=1)'; scalar; INTENT(IN).
! 
! Y: `INTEGER(KIND=1)'; scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Archaic form of `DIM()' that is specific to one type for X and Y.
! *Note DiM Intrinsic::.
! 
! 
! File: g77.info,  Node: IDInt Intrinsic,  Next: IDNInt Intrinsic,  Prev: IDiM Intrinsic,  Up: Table of Intrinsic Functions
! 
! IDInt Intrinsic
! ...............
! 
!      IDInt(A)
! 
! IDInt: `INTEGER(KIND=1)' function.
! 
! A: `REAL(KIND=2)'; scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Archaic form of `INT()' that is specific to one type for A.  *Note
! Int Intrinsic::.
! 
! 
! File: g77.info,  Node: IDNInt Intrinsic,  Next: IEOr Intrinsic,  Prev: IDInt Intrinsic,  Up: Table of Intrinsic Functions
! 
! IDNInt Intrinsic
! ................
! 
!      IDNInt(A)
! 
! IDNInt: `INTEGER(KIND=1)' function.
! 
! A: `REAL(KIND=2)'; scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Archaic form of `NINT()' that is specific to one type for A.  *Note
! NInt Intrinsic::.
! 
! 
! File: g77.info,  Node: IEOr Intrinsic,  Next: IErrNo Intrinsic,  Prev: IDNInt Intrinsic,  Up: Table of Intrinsic Functions
! 
! IEOr Intrinsic
! ..............
! 
!      IEOr(I, J)
! 
! IEOr: `INTEGER' function, the exact type being the result of
! cross-promoting the types of all the arguments.
! 
! I: `INTEGER'; scalar; INTENT(IN).
! 
! J: `INTEGER'; scalar; INTENT(IN).
! 
! Intrinsic groups: `mil', `f90', `vxt'.
! 
! Description:
! 
!    Returns value resulting from boolean exclusive-OR of pair of bits in
! each of I and J.
! 
! 
! File: g77.info,  Node: IErrNo Intrinsic,  Next: IFix Intrinsic,  Prev: IEOr Intrinsic,  Up: Table of Intrinsic Functions
! 
! IErrNo Intrinsic
! ................
! 
!      IErrNo()
! 
! IErrNo: `INTEGER(KIND=1)' function.
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Returns the last system error number (corresponding to the C
! `errno').
! 
! 
! File: g77.info,  Node: IFix Intrinsic,  Next: Imag Intrinsic,  Prev: IErrNo Intrinsic,  Up: Table of Intrinsic Functions
! 
! IFix Intrinsic
! ..............
! 
!      IFix(A)
! 
! IFix: `INTEGER(KIND=1)' function.
! 
! A: `REAL(KIND=1)'; scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Archaic form of `INT()' that is specific to one type for A.  *Note
! Int Intrinsic::.
! 
! 
! File: g77.info,  Node: Imag Intrinsic,  Next: ImagPart Intrinsic,  Prev: IFix Intrinsic,  Up: Table of Intrinsic Functions
! 
! Imag Intrinsic
! ..............
! 
!      Imag(Z)
! 
! Imag: `REAL' function, the `KIND=' value of the type being that of
! argument Z.
! 
! Z: `COMPLEX'; scalar; INTENT(IN).
! 
! Intrinsic groups: `f2c'.
! 
! Description:
! 
!    The imaginary part of Z is returned, without conversion.
! 
!    _Note:_ The way to do this in standard Fortran 90 is `AIMAG(Z)'.
! However, when, for example, Z is `DOUBLE COMPLEX', `AIMAG(Z)' means
! something different for some compilers that are not true Fortran 90
! compilers but offer some extensions standardized by Fortran 90 (such as
! the `DOUBLE COMPLEX' type, also known as `COMPLEX(KIND=2)').
! 
!    The advantage of `IMAG()' is that, while not necessarily more or
! less portable than `AIMAG()', it is more likely to cause a compiler
! that doesn't support it to produce a diagnostic than generate incorrect
! code.
! 
!    *Note REAL() and AIMAG() of Complex::, for more information.
! 
! 
! File: g77.info,  Node: ImagPart Intrinsic,  Next: Index Intrinsic,  Prev: Imag Intrinsic,  Up: Table of Intrinsic Functions
! 
! ImagPart Intrinsic
! ..................
! 
!      ImagPart(Z)
! 
! ImagPart: `REAL' function, the `KIND=' value of the type being that of
! argument Z.
! 
! Z: `COMPLEX'; scalar; INTENT(IN).
! 
! Intrinsic groups: `gnu'.
! 
! Description:
! 
!    The imaginary part of Z is returned, without conversion.
! 
!    _Note:_ The way to do this in standard Fortran 90 is `AIMAG(Z)'.
! However, when, for example, Z is `DOUBLE COMPLEX', `AIMAG(Z)' means
! something different for some compilers that are not true Fortran 90
! compilers but offer some extensions standardized by Fortran 90 (such as
! the `DOUBLE COMPLEX' type, also known as `COMPLEX(KIND=2)').
! 
!    The advantage of `IMAGPART()' is that, while not necessarily more or
! less portable than `AIMAG()', it is more likely to cause a compiler
! that doesn't support it to produce a diagnostic than generate incorrect
! code.
! 
!    *Note REAL() and AIMAG() of Complex::, for more information.
! 
! 
! File: g77.info,  Node: Index Intrinsic,  Next: Int Intrinsic,  Prev: ImagPart Intrinsic,  Up: Table of Intrinsic Functions
! 
! Index Intrinsic
! ...............
! 
!      Index(STRING, SUBSTRING)
! 
! Index: `INTEGER(KIND=1)' function.
! 
! STRING: `CHARACTER'; scalar; INTENT(IN).
! 
! SUBSTRING: `CHARACTER'; scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Returns the position of the start of the first occurrence of string
! SUBSTRING as a substring in STRING, counting from one.  If SUBSTRING
! doesn't occur in STRING, zero is returned.
! 
! 
! File: g77.info,  Node: Int Intrinsic,  Next: Int2 Intrinsic,  Prev: Index Intrinsic,  Up: Table of Intrinsic Functions
! 
! Int Intrinsic
! .............
! 
!      Int(A)
! 
! Int: `INTEGER(KIND=1)' function.
! 
! A: `INTEGER', `REAL', or `COMPLEX'; scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Returns A with the fractional portion of its magnitude truncated and
! its sign preserved, converted to type `INTEGER(KIND=1)'.
! 
!    If A is type `COMPLEX', its real part is truncated and converted,
! and its imaginary part is disregarded.
! 
!    *Note NInt Intrinsic::, for how to convert, rounded to nearest whole
! number.
! 
!    *Note AInt Intrinsic::, for how to truncate to whole number without
! converting.
! 
! 
! File: g77.info,  Node: Int2 Intrinsic,  Next: Int8 Intrinsic,  Prev: Int Intrinsic,  Up: Table of Intrinsic Functions
! 
! Int2 Intrinsic
! ..............
! 
!      Int2(A)
! 
! Int2: `INTEGER(KIND=6)' function.
! 
! A: `INTEGER', `REAL', or `COMPLEX'; scalar; INTENT(IN).
! 
! Intrinsic groups: `gnu'.
! 
! Description:
! 
!    Returns A with the fractional portion of its magnitude truncated and
! its sign preserved, converted to type `INTEGER(KIND=6)'.
! 
!    If A is type `COMPLEX', its real part is truncated and converted,
! and its imaginary part is disregarded.
! 
!    *Note Int Intrinsic::.
! 
!    The precise meaning of this intrinsic might change in a future
! version of the GNU Fortran language, as more is learned about how it is
! used.
! 
! 
! File: g77.info,  Node: Int8 Intrinsic,  Next: IOr Intrinsic,  Prev: Int2 Intrinsic,  Up: Table of Intrinsic Functions
! 
! Int8 Intrinsic
! ..............
! 
!      Int8(A)
! 
! Int8: `INTEGER(KIND=2)' function.
! 
! A: `INTEGER', `REAL', or `COMPLEX'; scalar; INTENT(IN).
! 
! Intrinsic groups: `gnu'.
! 
! Description:
! 
!    Returns A with the fractional portion of its magnitude truncated and
! its sign preserved, converted to type `INTEGER(KIND=2)'.
! 
!    If A is type `COMPLEX', its real part is truncated and converted,
! and its imaginary part is disregarded.
! 
!    *Note Int Intrinsic::.
! 
!    The precise meaning of this intrinsic might change in a future
! version of the GNU Fortran language, as more is learned about how it is
! used.
! 
! 
! File: g77.info,  Node: IOr Intrinsic,  Next: IRand Intrinsic,  Prev: Int8 Intrinsic,  Up: Table of Intrinsic Functions
! 
! IOr Intrinsic
! .............
! 
!      IOr(I, J)
! 
! IOr: `INTEGER' function, the exact type being the result of
! cross-promoting the types of all the arguments.
! 
! I: `INTEGER'; scalar; INTENT(IN).
! 
! J: `INTEGER'; scalar; INTENT(IN).
! 
! Intrinsic groups: `mil', `f90', `vxt'.
! 
! Description:
! 
!    Returns value resulting from boolean OR of pair of bits in each of I
! and J.
! 
! 
! File: g77.info,  Node: IRand Intrinsic,  Next: IsaTty Intrinsic,  Prev: IOr Intrinsic,  Up: Table of Intrinsic Functions
! 
! IRand Intrinsic
! ...............
! 
!      IRand(FLAG)
! 
! IRand: `INTEGER(KIND=1)' function.
! 
! FLAG: `INTEGER'; OPTIONAL; scalar; INTENT(IN).
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Returns a uniform quasi-random number up to a system-dependent limit.
! If FLAG is 0, the next number in sequence is returned; if FLAG is 1,
! the generator is restarted by calling the UNIX function `srand(0)'; if
! FLAG has any other value, it is used as a new seed with `srand()'.
! 
!    *Note SRand Intrinsic::.
! 
!    _Note:_ As typically implemented (by the routine of the same name in
! the C library), this random number generator is a very poor one, though
! the BSD and GNU libraries provide a much better implementation than the
! `traditional' one.  On a different system you almost certainly want to
! use something better.
! 
! 
! File: g77.info,  Node: IsaTty Intrinsic,  Next: IShft Intrinsic,  Prev: IRand Intrinsic,  Up: Table of Intrinsic Functions
! 
! IsaTty Intrinsic
! ................
! 
!      IsaTty(UNIT)
! 
! IsaTty: `LOGICAL(KIND=1)' function.
! 
! UNIT: `INTEGER'; scalar; INTENT(IN).
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Returns `.TRUE.' if and only if the Fortran I/O unit specified by
! UNIT is connected to a terminal device.  See `isatty(3)'.
! 
! 
! File: g77.info,  Node: IShft Intrinsic,  Next: IShftC Intrinsic,  Prev: IsaTty Intrinsic,  Up: Table of Intrinsic Functions
! 
! IShft Intrinsic
! ...............
! 
!      IShft(I, SHIFT)
! 
! IShft: `INTEGER' function, the `KIND=' value of the type being that of
! argument I.
! 
! I: `INTEGER'; scalar; INTENT(IN).
! 
! SHIFT: `INTEGER'; scalar; INTENT(IN).
! 
! Intrinsic groups: `mil', `f90', `vxt'.
! 
! Description:
! 
!    All bits representing I are shifted SHIFT places.  `SHIFT.GT.0'
! indicates a left shift, `SHIFT.EQ.0' indicates no shift and
! `SHIFT.LT.0' indicates a right shift.  If the absolute value of the
! shift count is greater than `BIT_SIZE(I)', the result is undefined.
! Bits shifted out from the left end or the right end are lost.  Zeros
! are shifted in from the opposite end.
! 
!    *Note IShftC Intrinsic::, for the circular-shift equivalent.
! 
! 
! File: g77.info,  Node: IShftC Intrinsic,  Next: ISign Intrinsic,  Prev: IShft Intrinsic,  Up: Table of Intrinsic Functions
! 
! IShftC Intrinsic
! ................
! 
!      IShftC(I, SHIFT, SIZE)
! 
! IShftC: `INTEGER' function, the `KIND=' value of the type being that of
! argument I.
! 
! I: `INTEGER'; scalar; INTENT(IN).
! 
! SHIFT: `INTEGER'; scalar; INTENT(IN).
! 
! SIZE: `INTEGER'; scalar; INTENT(IN).
! 
! Intrinsic groups: `mil', `f90', `vxt'.
! 
! Description:
! 
!    The rightmost SIZE bits of the argument I are shifted circularly
! SHIFT places, i.e. the bits shifted out of one end are shifted into the
! opposite end.  No bits are lost.  The unshifted bits of the result are
! the same as the unshifted bits of I.  The  absolute value of the
! argument SHIFT must be less than or equal to SIZE.  The value of SIZE
! must be greater than or equal to one and less than or equal to
! `BIT_SIZE(I)'.
! 
!    *Note IShft Intrinsic::, for the logical shift equivalent.
! 
! 
! File: g77.info,  Node: ISign Intrinsic,  Next: ITime Intrinsic,  Prev: IShftC Intrinsic,  Up: Table of Intrinsic Functions
! 
! ISign Intrinsic
! ...............
! 
!      ISign(A, B)
! 
! ISign: `INTEGER(KIND=1)' function.
! 
! A: `INTEGER(KIND=1)'; scalar; INTENT(IN).
! 
! B: `INTEGER(KIND=1)'; scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Archaic form of `SIGN()' that is specific to one type for A and B.
! *Note Sign Intrinsic::.
! 
! 
! File: g77.info,  Node: ITime Intrinsic,  Next: Kill Intrinsic (subroutine),  Prev: ISign Intrinsic,  Up: Table of Intrinsic Functions
! 
! ITime Intrinsic
! ...............
! 
!      CALL ITime(TARRAY)
! 
! TARRAY: `INTEGER(KIND=1)'; DIMENSION(3); INTENT(OUT).
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Returns the current local time hour, minutes, and seconds in elements
! 1, 2, and 3 of TARRAY, respectively.
! 
! 
! File: g77.info,  Node: Kill Intrinsic (subroutine),  Next: Kind Intrinsic,  Prev: ITime Intrinsic,  Up: Table of Intrinsic Functions
! 
! Kill Intrinsic (subroutine)
! ...........................
! 
!      CALL Kill(PID, SIGNAL, STATUS)
! 
! PID: `INTEGER'; scalar; INTENT(IN).
! 
! SIGNAL: `INTEGER'; scalar; INTENT(IN).
! 
! STATUS: `INTEGER(KIND=1)'; OPTIONAL; scalar; INTENT(OUT).
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Sends the signal specified by SIGNAL to the process PID.  If the
! STATUS argument is supplied, it contains 0 on success or a nonzero
! error code upon return.  See `kill(2)'.
! 
!    Some non-GNU implementations of Fortran provide this intrinsic as
! only a function, not as a subroutine, or do not support the (optional)
! STATUS argument.
! 
!    For information on other intrinsics with the same name: *Note Kill
! Intrinsic (function)::.
! 
! 
! File: g77.info,  Node: Kind Intrinsic,  Next: LBound Intrinsic,  Prev: Kill Intrinsic (subroutine),  Up: Table of Intrinsic Functions
! 
! Kind Intrinsic
! ..............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL Kind' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: LBound Intrinsic,  Next: Len Intrinsic,  Prev: Kind Intrinsic,  Up: Table of Intrinsic Functions
! 
! LBound Intrinsic
! ................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL LBound' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: Len Intrinsic,  Next: Len_Trim Intrinsic,  Prev: LBound Intrinsic,  Up: Table of Intrinsic Functions
! 
! Len Intrinsic
! .............
! 
!      Len(STRING)
! 
! Len: `INTEGER(KIND=1)' function.
! 
! STRING: `CHARACTER'; scalar.
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Returns the length of STRING.
! 
!    If STRING is an array, the length of an element of STRING is
! returned.
! 
!    Note that STRING need not be defined when this intrinsic is invoked,
! since only the length, not the content, of STRING is needed.
! 
!    *Note Bit_Size Intrinsic::, for the function that determines the
! size of its argument in bits.
! 
! 
! File: g77.info,  Node: Len_Trim Intrinsic,  Next: LGe Intrinsic,  Prev: Len Intrinsic,  Up: Table of Intrinsic Functions
! 
! Len_Trim Intrinsic
! ..................
! 
!      Len_Trim(STRING)
! 
! Len_Trim: `INTEGER(KIND=1)' function.
! 
! STRING: `CHARACTER'; scalar; INTENT(IN).
! 
! Intrinsic groups: `f90'.
! 
! Description:
! 
!    Returns the index of the last non-blank character in STRING.
! `LNBLNK' and `LEN_TRIM' are equivalent.
! 
! 
! File: g77.info,  Node: LGe Intrinsic,  Next: LGt Intrinsic,  Prev: Len_Trim Intrinsic,  Up: Table of Intrinsic Functions
! 
! LGe Intrinsic
! .............
! 
!      LGe(STRING_A, STRING_B)
! 
! LGe: `LOGICAL(KIND=1)' function.
! 
! STRING_A: `CHARACTER'; scalar; INTENT(IN).
! 
! STRING_B: `CHARACTER'; scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Returns `.TRUE.' if `STRING_A.GE.STRING_B', `.FALSE.' otherwise.
! STRING_A and STRING_B are interpreted as containing ASCII character
! codes.  If either value contains a character not in the ASCII character
! set, the result is processor dependent.
! 
!    If the STRING_A and STRING_B are not the same length, the shorter is
! compared as if spaces were appended to it to form a value that has the
! same length as the longer.
! 
!    The lexical comparison intrinsics `LGe', `LGt', `LLe', and `LLt'
! differ from the corresponding intrinsic operators `.GE.', `.GT.',
! `.LE.', `.LT.'.  Because the ASCII collating sequence is assumed, the
! following expressions always return `.TRUE.':
! 
!      LGE ('0', ' ')
!      LGE ('A', '0')
!      LGE ('a', 'A')
! 
!    The following related expressions do _not_ always return `.TRUE.',
! as they are not necessarily evaluated assuming the arguments use ASCII
! encoding:
! 
!      '0' .GE. ' '
!      'A' .GE. '0'
!      'a' .GE. 'A'
! 
!    The same difference exists between `LGt' and `.GT.'; between `LLe'
! and `.LE.'; and between `LLt' and `.LT.'.
! 
! 
! File: g77.info,  Node: LGt Intrinsic,  Next: Link Intrinsic (subroutine),  Prev: LGe Intrinsic,  Up: Table of Intrinsic Functions
! 
! LGt Intrinsic
! .............
! 
!      LGt(STRING_A, STRING_B)
! 
! LGt: `LOGICAL(KIND=1)' function.
! 
! STRING_A: `CHARACTER'; scalar; INTENT(IN).
! 
! STRING_B: `CHARACTER'; scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Returns `.TRUE.' if `STRING_A.GT.STRING_B', `.FALSE.' otherwise.
! STRING_A and STRING_B are interpreted as containing ASCII character
! codes.  If either value contains a character not in the ASCII character
! set, the result is processor dependent.
! 
!    If the STRING_A and STRING_B are not the same length, the shorter is
! compared as if spaces were appended to it to form a value that has the
! same length as the longer.
! 
!    *Note LGe Intrinsic::, for information on the distinction between
! the `LGT' intrinsic and the `.GT.' operator.
! 
! 
! File: g77.info,  Node: Link Intrinsic (subroutine),  Next: LLe Intrinsic,  Prev: LGt Intrinsic,  Up: Table of Intrinsic Functions
! 
! Link Intrinsic (subroutine)
! ...........................
! 
!      CALL Link(PATH1, PATH2, STATUS)
! 
! PATH1: `CHARACTER'; scalar; INTENT(IN).
! 
! PATH2: `CHARACTER'; scalar; INTENT(IN).
! 
! STATUS: `INTEGER(KIND=1)'; OPTIONAL; scalar; INTENT(OUT).
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Makes a (hard) link from file PATH1 to PATH2.  A null character
! (`CHAR(0)') marks the end of the names in PATH1 and PATH2--otherwise,
! trailing blanks in PATH1 and PATH2 are ignored.  If the STATUS argument
! is supplied, it contains 0 on success or a nonzero error code upon
! return.  See `link(2)'.
! 
!    Some non-GNU implementations of Fortran provide this intrinsic as
! only a function, not as a subroutine, or do not support the (optional)
! STATUS argument.
! 
!    For information on other intrinsics with the same name: *Note Link
! Intrinsic (function)::.
! 
! 
! File: g77.info,  Node: LLe Intrinsic,  Next: LLt Intrinsic,  Prev: Link Intrinsic (subroutine),  Up: Table of Intrinsic Functions
! 
! LLe Intrinsic
! .............
! 
!      LLe(STRING_A, STRING_B)
! 
! LLe: `LOGICAL(KIND=1)' function.
! 
! STRING_A: `CHARACTER'; scalar; INTENT(IN).
! 
! STRING_B: `CHARACTER'; scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Returns `.TRUE.' if `STRING_A.LE.STRING_B', `.FALSE.' otherwise.
! STRING_A and STRING_B are interpreted as containing ASCII character
! codes.  If either value contains a character not in the ASCII character
! set, the result is processor dependent.
! 
!    If the STRING_A and STRING_B are not the same length, the shorter is
! compared as if spaces were appended to it to form a value that has the
! same length as the longer.
! 
!    *Note LGe Intrinsic::, for information on the distinction between
! the `LLE' intrinsic and the `.LE.' operator.
! 
! 
! File: g77.info,  Node: LLt Intrinsic,  Next: LnBlnk Intrinsic,  Prev: LLe Intrinsic,  Up: Table of Intrinsic Functions
! 
! LLt Intrinsic
! .............
! 
!      LLt(STRING_A, STRING_B)
! 
! LLt: `LOGICAL(KIND=1)' function.
! 
! STRING_A: `CHARACTER'; scalar; INTENT(IN).
! 
! STRING_B: `CHARACTER'; scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Returns `.TRUE.' if `STRING_A.LT.STRING_B', `.FALSE.' otherwise.
! STRING_A and STRING_B are interpreted as containing ASCII character
! codes.  If either value contains a character not in the ASCII character
! set, the result is processor dependent.
! 
!    If the STRING_A and STRING_B are not the same length, the shorter is
! compared as if spaces were appended to it to form a value that has the
! same length as the longer.
! 
!    *Note LGe Intrinsic::, for information on the distinction between
! the `LLT' intrinsic and the `.LT.' operator.
! 
! 
! File: g77.info,  Node: LnBlnk Intrinsic,  Next: Loc Intrinsic,  Prev: LLt Intrinsic,  Up: Table of Intrinsic Functions
! 
! LnBlnk Intrinsic
! ................
! 
!      LnBlnk(STRING)
! 
! LnBlnk: `INTEGER(KIND=1)' function.
! 
! STRING: `CHARACTER'; scalar; INTENT(IN).
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Returns the index of the last non-blank character in STRING.
! `LNBLNK' and `LEN_TRIM' are equivalent.
! 
! 
! File: g77.info,  Node: Loc Intrinsic,  Next: Log Intrinsic,  Prev: LnBlnk Intrinsic,  Up: Table of Intrinsic Functions
! 
! Loc Intrinsic
! .............
! 
!      Loc(ENTITY)
! 
! Loc: `INTEGER(KIND=7)' function.
! 
! ENTITY: Any type; cannot be a constant or expression.
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    The `LOC()' intrinsic works the same way as the `%LOC()' construct.
! *Note The `%LOC()' Construct: %LOC(), for more information.
! 
! 
! File: g77.info,  Node: Log Intrinsic,  Next: Log10 Intrinsic,  Prev: Loc Intrinsic,  Up: Table of Intrinsic Functions
! 
! Log Intrinsic
! .............
! 
!      Log(X)
! 
! Log: `REAL' or `COMPLEX' function, the exact type being that of
! argument X.
! 
! X: `REAL' or `COMPLEX'; scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Returns the natural logarithm of X, which must be greater than zero
! or, if type `COMPLEX', must not be zero.
! 
!    *Note Exp Intrinsic::, for the inverse of this function.
! 
!    *Note Log10 Intrinsic::, for the `common' (base-10) logarithm
! function.
! 
! 
! File: g77.info,  Node: Log10 Intrinsic,  Next: Logical Intrinsic,  Prev: Log Intrinsic,  Up: Table of Intrinsic Functions
! 
! Log10 Intrinsic
! ...............
! 
!      Log10(X)
! 
! Log10: `REAL' function, the `KIND=' value of the type being that of
! argument X.
! 
! X: `REAL'; scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Returns the common logarithm (base 10) of X, which must be greater
! than zero.
! 
!    The inverse of this function is `10. ** LOG10(X)'.
! 
!    *Note Log Intrinsic::, for the natural logarithm function.
! 
! 
! File: g77.info,  Node: Logical Intrinsic,  Next: Long Intrinsic,  Prev: Log10 Intrinsic,  Up: Table of Intrinsic Functions
! 
! Logical Intrinsic
! .................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL Logical' to use this name for
! an external procedure.
! 
! 
! File: g77.info,  Node: Long Intrinsic,  Next: LShift Intrinsic,  Prev: Logical Intrinsic,  Up: Table of Intrinsic Functions
! 
! Long Intrinsic
! ..............
! 
!      Long(A)
! 
! Long: `INTEGER(KIND=1)' function.
! 
! A: `INTEGER(KIND=6)'; scalar; INTENT(IN).
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Archaic form of `INT()' that is specific to one type for A.  *Note
! Int Intrinsic::.
! 
!    The precise meaning of this intrinsic might change in a future
! version of the GNU Fortran language, as more is learned about how it is
! used.
! 
! 
! File: g77.info,  Node: LShift Intrinsic,  Next: LStat Intrinsic (subroutine),  Prev: Long Intrinsic,  Up: Table of Intrinsic Functions
! 
! LShift Intrinsic
! ................
! 
!      LShift(I, SHIFT)
! 
! LShift: `INTEGER' function, the `KIND=' value of the type being that of
! argument I.
! 
! I: `INTEGER'; scalar; INTENT(IN).
! 
! SHIFT: `INTEGER'; scalar; INTENT(IN).
! 
! Intrinsic groups: `f2c'.
! 
! Description:
! 
!    Returns I shifted to the left SHIFT bits.
! 
!    Although similar to the expression `I*(2**SHIFT)', there are
! important differences.  For example, the sign of the result is not
! necessarily the same as the sign of I.
! 
!    Currently this intrinsic is defined assuming the underlying
! representation of I is as a two's-complement integer.  It is unclear at
! this point whether that definition will apply when a different
! representation is involved.
! 
!    *Note LShift Intrinsic::, for the inverse of this function.
! 
!    *Note IShft Intrinsic::, for information on a more widely available
! left-shifting intrinsic that is also more precisely defined.
! 
! 
! File: g77.info,  Node: LStat Intrinsic (subroutine),  Next: LStat Intrinsic (function),  Prev: LShift Intrinsic,  Up: Table of Intrinsic Functions
! 
! LStat Intrinsic (subroutine)
! ............................
! 
!      CALL LStat(FILE, SARRAY, STATUS)
! 
! FILE: `CHARACTER'; scalar; INTENT(IN).
! 
! SARRAY: `INTEGER(KIND=1)'; DIMENSION(13); INTENT(OUT).
! 
! STATUS: `INTEGER(KIND=1)'; OPTIONAL; scalar; INTENT(OUT).
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Obtains data about the given file FILE and places them in the array
! SARRAY.  A null character (`CHAR(0)') marks the end of the name in
! FILE--otherwise, trailing blanks in FILE are ignored.  If FILE is a
! symbolic link it returns data on the link itself, so the routine is
! available only on systems that support symbolic links.  The values in
! this array are extracted from the `stat' structure as returned by
! `fstat(2)' q.v., as follows:
! 
!   1. Device ID
! 
!   2. Inode number
! 
!   3. File mode
! 
!   4. Number of links
! 
!   5. Owner's uid
! 
!   6. Owner's gid
! 
!   7. ID of device containing directory entry for file (0 if not
!      available)
! 
!   8. File size (bytes)
! 
!   9. Last access time
! 
!  10. Last modification time
! 
!  11. Last file status change time
! 
!  12. Preferred I/O block size (-1 if not available)
! 
!  13. Number of blocks allocated (-1 if not available)
! 
!    Not all these elements are relevant on all systems.  If an element
! is not relevant, it is returned as 0.
! 
!    If the STATUS argument is supplied, it contains 0 on success or a
! nonzero error code upon return (`ENOSYS' if the system does not provide
! `lstat(2)').
! 
!    Some non-GNU implementations of Fortran provide this intrinsic as
! only a function, not as a subroutine, or do not support the (optional)
! STATUS argument.
! 
!    For information on other intrinsics with the same name: *Note LStat
! Intrinsic (function)::.
! 
! 
! File: g77.info,  Node: LStat Intrinsic (function),  Next: LTime Intrinsic,  Prev: LStat Intrinsic (subroutine),  Up: Table of Intrinsic Functions
! 
! LStat Intrinsic (function)
! ..........................
! 
!      LStat(FILE, SARRAY)
! 
! LStat: `INTEGER(KIND=1)' function.
! 
! FILE: `CHARACTER'; scalar; INTENT(IN).
! 
! SARRAY: `INTEGER(KIND=1)'; DIMENSION(13); INTENT(OUT).
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Obtains data about the given file FILE and places them in the array
! SARRAY.  A null character (`CHAR(0)') marks the end of the name in
! FILE--otherwise, trailing blanks in FILE are ignored.  If FILE is a
! symbolic link it returns data on the link itself, so the routine is
! available only on systems that support symbolic links.  The values in
! this array are extracted from the `stat' structure as returned by
! `fstat(2)' q.v., as follows:
! 
!   1. Device ID
! 
!   2. Inode number
! 
!   3. File mode
! 
!   4. Number of links
! 
!   5. Owner's uid
! 
!   6. Owner's gid
! 
!   7. ID of device containing directory entry for file (0 if not
!      available)
! 
!   8. File size (bytes)
! 
!   9. Last access time
! 
!  10. Last modification time
! 
!  11. Last file status change time
! 
!  12. Preferred I/O block size (-1 if not available)
! 
!  13. Number of blocks allocated (-1 if not available)
! 
!    Not all these elements are relevant on all systems.  If an element
! is not relevant, it is returned as 0.
! 
!    Returns 0 on success or a nonzero error code (`ENOSYS' if the system
! does not provide `lstat(2)').
! 
!    For information on other intrinsics with the same name: *Note LStat
! Intrinsic (subroutine)::.
! 
! 
! File: g77.info,  Node: LTime Intrinsic,  Next: MatMul Intrinsic,  Prev: LStat Intrinsic (function),  Up: Table of Intrinsic Functions
! 
! LTime Intrinsic
! ...............
! 
!      CALL LTime(STIME, TARRAY)
! 
! STIME: `INTEGER(KIND=1)'; scalar; INTENT(IN).
! 
! TARRAY: `INTEGER(KIND=1)'; DIMENSION(9); INTENT(OUT).
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Given a system time value STIME, fills TARRAY with values extracted
! from it appropriate to the GMT time zone using `localtime(3)'.
! 
!    The array elements are as follows:
! 
!   1. Seconds after the minute, range 0-59 or 0-61 to allow for leap
!      seconds
! 
!   2. Minutes after the hour, range 0-59
! 
!   3. Hours past midnight, range 0-23
! 
!   4. Day of month, range 0-31
! 
!   5. Number of months since January, range 0-12
! 
!   6. Years since 1900
! 
!   7. Number of days since Sunday, range 0-6
! 
!   8. Days since January 1
! 
!   9. Daylight savings indicator: positive if daylight savings is in
!      effect, zero if not, and negative if the information isn't
!      available.
! 
! 
! File: g77.info,  Node: MatMul Intrinsic,  Next: Max Intrinsic,  Prev: LTime Intrinsic,  Up: Table of Intrinsic Functions
! 
! MatMul Intrinsic
! ................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL MatMul' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: Max Intrinsic,  Next: Max0 Intrinsic,  Prev: MatMul Intrinsic,  Up: Table of Intrinsic Functions
! 
! Max Intrinsic
! .............
! 
!      Max(A-1, A-2, ..., A-n)
! 
! Max: `INTEGER' or `REAL' function, the exact type being the result of
! cross-promoting the types of all the arguments.
! 
! A: `INTEGER' or `REAL'; at least two such arguments must be provided;
! scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Returns the argument with the largest value.
! 
!    *Note Min Intrinsic::, for the opposite function.
! 
! 
! File: g77.info,  Node: Max0 Intrinsic,  Next: Max1 Intrinsic,  Prev: Max Intrinsic,  Up: Table of Intrinsic Functions
! 
! Max0 Intrinsic
! ..............
! 
!      Max0(A-1, A-2, ..., A-n)
! 
! Max0: `INTEGER(KIND=1)' function.
! 
! A: `INTEGER(KIND=1)'; at least two such arguments must be provided;
! scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Archaic form of `MAX()' that is specific to one type for A.  *Note
! Max Intrinsic::.
! 
! 
! File: g77.info,  Node: Max1 Intrinsic,  Next: MaxExponent Intrinsic,  Prev: Max0 Intrinsic,  Up: Table of Intrinsic Functions
! 
! Max1 Intrinsic
! ..............
! 
!      Max1(A-1, A-2, ..., A-n)
! 
! Max1: `INTEGER(KIND=1)' function.
! 
! A: `REAL(KIND=1)'; at least two such arguments must be provided;
! scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Archaic form of `MAX()' that is specific to one type for A and a
! different return type.  *Note Max Intrinsic::.
! 
! 
! File: g77.info,  Node: MaxExponent Intrinsic,  Next: MaxLoc Intrinsic,  Prev: Max1 Intrinsic,  Up: Table of Intrinsic Functions
! 
! MaxExponent Intrinsic
! .....................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL MaxExponent' to use this name
! for an external procedure.
! 
! 
! File: g77.info,  Node: MaxLoc Intrinsic,  Next: MaxVal Intrinsic,  Prev: MaxExponent Intrinsic,  Up: Table of Intrinsic Functions
! 
! MaxLoc Intrinsic
! ................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL MaxLoc' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: MaxVal Intrinsic,  Next: MClock Intrinsic,  Prev: MaxLoc Intrinsic,  Up: Table of Intrinsic Functions
! 
! MaxVal Intrinsic
! ................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL MaxVal' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: MClock Intrinsic,  Next: MClock8 Intrinsic,  Prev: MaxVal Intrinsic,  Up: Table of Intrinsic Functions
! 
! MClock Intrinsic
! ................
! 
!      MClock()
! 
! MClock: `INTEGER(KIND=1)' function.
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Returns the number of clock ticks since the start of the process.
! Supported on systems with `clock(3)' (q.v.).
! 
!    This intrinsic is not fully portable, such as to systems with 32-bit
! `INTEGER' types but supporting times wider than 32 bits.  Therefore,
! the values returned by this intrinsic might be, or become, negative, or
! numerically less than previous values, during a single run of the
! compiled program.
! 
!    *Note MClock8 Intrinsic::, for information on a similar intrinsic
! that might be portable to more GNU Fortran implementations, though to
! fewer Fortran compilers.
! 
!    If the system does not support `clock(3)', -1 is returned.
! 
! 
! File: g77.info,  Node: MClock8 Intrinsic,  Next: Merge Intrinsic,  Prev: MClock Intrinsic,  Up: Table of Intrinsic Functions
! 
! MClock8 Intrinsic
! .................
! 
!      MClock8()
! 
! MClock8: `INTEGER(KIND=2)' function.
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Returns the number of clock ticks since the start of the process.
! Supported on systems with `clock(3)' (q.v.).
! 
!    _Warning:_ this intrinsic does not increase the range of the timing
! values over that returned by `clock(3)'.  On a system with a 32-bit
! `clock(3)', `MCLOCK8' will return a 32-bit value, even though converted
! to an `INTEGER(KIND=2)' value.  That means overflows of the 32-bit
! value can still occur.  Therefore, the values returned by this intrinsic
! might be, or become, negative, or numerically less than previous values,
! during a single run of the compiled program.
! 
!    No Fortran implementations other than GNU Fortran are known to
! support this intrinsic at the time of this writing.  *Note MClock
! Intrinsic::, for information on a similar intrinsic that might be
! portable to more Fortran compilers, though to fewer GNU Fortran
! implementations.
! 
!    If the system does not support `clock(3)', -1 is returned.
! 
! 
! File: g77.info,  Node: Merge Intrinsic,  Next: Min Intrinsic,  Prev: MClock8 Intrinsic,  Up: Table of Intrinsic Functions
! 
! Merge Intrinsic
! ...............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL Merge' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: Min Intrinsic,  Next: Min0 Intrinsic,  Prev: Merge Intrinsic,  Up: Table of Intrinsic Functions
! 
! Min Intrinsic
! .............
! 
!      Min(A-1, A-2, ..., A-n)
! 
! Min: `INTEGER' or `REAL' function, the exact type being the result of
! cross-promoting the types of all the arguments.
! 
! A: `INTEGER' or `REAL'; at least two such arguments must be provided;
! scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Returns the argument with the smallest value.
! 
!    *Note Max Intrinsic::, for the opposite function.
! 
! 
! File: g77.info,  Node: Min0 Intrinsic,  Next: Min1 Intrinsic,  Prev: Min Intrinsic,  Up: Table of Intrinsic Functions
! 
! Min0 Intrinsic
! ..............
! 
!      Min0(A-1, A-2, ..., A-n)
! 
! Min0: `INTEGER(KIND=1)' function.
! 
! A: `INTEGER(KIND=1)'; at least two such arguments must be provided;
! scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Archaic form of `MIN()' that is specific to one type for A.  *Note
! Min Intrinsic::.
! 
! 
! File: g77.info,  Node: Min1 Intrinsic,  Next: MinExponent Intrinsic,  Prev: Min0 Intrinsic,  Up: Table of Intrinsic Functions
! 
! Min1 Intrinsic
! ..............
! 
!      Min1(A-1, A-2, ..., A-n)
! 
! Min1: `INTEGER(KIND=1)' function.
! 
! A: `REAL(KIND=1)'; at least two such arguments must be provided;
! scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Archaic form of `MIN()' that is specific to one type for A and a
! different return type.  *Note Min Intrinsic::.
! 
! 
! File: g77.info,  Node: MinExponent Intrinsic,  Next: MinLoc Intrinsic,  Prev: Min1 Intrinsic,  Up: Table of Intrinsic Functions
! 
! MinExponent Intrinsic
! .....................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL MinExponent' to use this name
! for an external procedure.
! 
! 
! File: g77.info,  Node: MinLoc Intrinsic,  Next: MinVal Intrinsic,  Prev: MinExponent Intrinsic,  Up: Table of Intrinsic Functions
! 
! MinLoc Intrinsic
! ................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL MinLoc' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: MinVal Intrinsic,  Next: Mod Intrinsic,  Prev: MinLoc Intrinsic,  Up: Table of Intrinsic Functions
! 
! MinVal Intrinsic
! ................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL MinVal' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: Mod Intrinsic,  Next: Modulo Intrinsic,  Prev: MinVal Intrinsic,  Up: Table of Intrinsic Functions
! 
! Mod Intrinsic
! .............
! 
!      Mod(A, P)
! 
! Mod: `INTEGER' or `REAL' function, the exact type being the result of
! cross-promoting the types of all the arguments.
! 
! A: `INTEGER' or `REAL'; scalar; INTENT(IN).
! 
! P: `INTEGER' or `REAL'; scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Returns remainder calculated as:
! 
!      A - (INT(A / P) * P)
! 
!    P must not be zero.
! 
! 
! File: g77.info,  Node: Modulo Intrinsic,  Next: MvBits Intrinsic,  Prev: Mod Intrinsic,  Up: Table of Intrinsic Functions
! 
! Modulo Intrinsic
! ................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL Modulo' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: MvBits Intrinsic,  Next: Nearest Intrinsic,  Prev: Modulo Intrinsic,  Up: Table of Intrinsic Functions
! 
! MvBits Intrinsic
! ................
! 
!      CALL MvBits(FROM, FROMPOS, LEN, TO, TOPOS)
! 
! FROM: `INTEGER'; scalar; INTENT(IN).
! 
! FROMPOS: `INTEGER'; scalar; INTENT(IN).
! 
! LEN: `INTEGER'; scalar; INTENT(IN).
! 
! TO: `INTEGER' with same `KIND=' value as for FROM; scalar;
! INTENT(INOUT).
! 
! TOPOS: `INTEGER'; scalar; INTENT(IN).
! 
! Intrinsic groups: `mil', `f90', `vxt'.
! 
! Description:
! 
!    Moves LEN bits from positions FROMPOS through `FROMPOS+LEN-1' of
! FROM to positions TOPOS through `FROMPOS+LEN-1' of TO.  The portion of
! argument TO not affected by the movement of bits is unchanged.
! Arguments FROM and TO are permitted to be the same numeric storage
! unit.  The values of `FROMPOS+LEN' and `TOPOS+LEN' must be less than or
! equal to `BIT_SIZE(FROM)'.
! 
! 
! File: g77.info,  Node: Nearest Intrinsic,  Next: NInt Intrinsic,  Prev: MvBits Intrinsic,  Up: Table of Intrinsic Functions
! 
! Nearest Intrinsic
! .................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL Nearest' to use this name for
! an external procedure.
! 
! 
! File: g77.info,  Node: NInt Intrinsic,  Next: Not Intrinsic,  Prev: Nearest Intrinsic,  Up: Table of Intrinsic Functions
! 
! NInt Intrinsic
! ..............
! 
!      NInt(A)
! 
! NInt: `INTEGER(KIND=1)' function.
! 
! A: `REAL'; scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Returns A with the fractional portion of its magnitude eliminated by
! rounding to the nearest whole number and with its sign preserved,
! converted to type `INTEGER(KIND=1)'.
! 
!    If A is type `COMPLEX', its real part is rounded and converted.
! 
!    A fractional portion exactly equal to `.5' is rounded to the whole
! number that is larger in magnitude.  (Also called "Fortran round".)
! 
!    *Note Int Intrinsic::, for how to convert, truncate to whole number.
! 
!    *Note ANInt Intrinsic::, for how to round to nearest whole number
! without converting.
! 
! 
! File: g77.info,  Node: Not Intrinsic,  Next: Or Intrinsic,  Prev: NInt Intrinsic,  Up: Table of Intrinsic Functions
! 
! Not Intrinsic
! .............
! 
!      Not(I)
! 
! Not: `INTEGER' function, the `KIND=' value of the type being that of
! argument I.
! 
! I: `INTEGER'; scalar; INTENT(IN).
! 
! Intrinsic groups: `mil', `f90', `vxt'.
! 
! Description:
! 
!    Returns value resulting from boolean NOT of each bit in I.
! 
! 
! File: g77.info,  Node: Or Intrinsic,  Next: Pack Intrinsic,  Prev: Not Intrinsic,  Up: Table of Intrinsic Functions
! 
! Or Intrinsic
! ............
! 
!      Or(I, J)
! 
! Or: `INTEGER' or `LOGICAL' function, the exact type being the result of
! cross-promoting the types of all the arguments.
! 
! I: `INTEGER' or `LOGICAL'; scalar; INTENT(IN).
! 
! J: `INTEGER' or `LOGICAL'; scalar; INTENT(IN).
! 
! Intrinsic groups: `f2c'.
! 
! Description:
! 
!    Returns value resulting from boolean OR of pair of bits in each of I
! and J.
! 
! 
! File: g77.info,  Node: Pack Intrinsic,  Next: PError Intrinsic,  Prev: Or Intrinsic,  Up: Table of Intrinsic Functions
! 
! Pack Intrinsic
! ..............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL Pack' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: PError Intrinsic,  Next: Precision Intrinsic,  Prev: Pack Intrinsic,  Up: Table of Intrinsic Functions
! 
! PError Intrinsic
! ................
! 
!      CALL PError(STRING)
! 
! STRING: `CHARACTER'; scalar; INTENT(IN).
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Prints (on the C `stderr' stream) a newline-terminated error message
! corresponding to the last system error.  This is prefixed by STRING, a
! colon and a space.  See `perror(3)'.
! 
! 
! File: g77.info,  Node: Precision Intrinsic,  Next: Present Intrinsic,  Prev: PError Intrinsic,  Up: Table of Intrinsic Functions
! 
! Precision Intrinsic
! ...................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL Precision' to use this name
! for an external procedure.
! 
! 
! File: g77.info,  Node: Present Intrinsic,  Next: Product Intrinsic,  Prev: Precision Intrinsic,  Up: Table of Intrinsic Functions
! 
! Present Intrinsic
! .................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL Present' to use this name for
! an external procedure.
! 
! 
! File: g77.info,  Node: Product Intrinsic,  Next: Radix Intrinsic,  Prev: Present Intrinsic,  Up: Table of Intrinsic Functions
! 
! Product Intrinsic
! .................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL Product' to use this name for
! an external procedure.
! 
! 
! File: g77.info,  Node: Radix Intrinsic,  Next: Rand Intrinsic,  Prev: Product Intrinsic,  Up: Table of Intrinsic Functions
! 
! Radix Intrinsic
! ...............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL Radix' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: Rand Intrinsic,  Next: Random_Number Intrinsic,  Prev: Radix Intrinsic,  Up: Table of Intrinsic Functions
! 
! Rand Intrinsic
! ..............
! 
!      Rand(FLAG)
! 
! Rand: `REAL(KIND=1)' function.
! 
! FLAG: `INTEGER'; OPTIONAL; scalar; INTENT(IN).
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Returns a uniform quasi-random number between 0 and 1.  If FLAG is
! 0, the next number in sequence is returned; if FLAG is 1, the generator
! is restarted by calling `srand(0)'; if FLAG has any other value, it is
! used as a new seed with `srand'.
! 
!    *Note SRand Intrinsic::.
! 
!    _Note:_ As typically implemented (by the routine of the same name in
! the C library), this random number generator is a very poor one, though
! the BSD and GNU libraries provide a much better implementation than the
! `traditional' one.  On a different system you almost certainly want to
! use something better.
! 
! 
! File: g77.info,  Node: Random_Number Intrinsic,  Next: Random_Seed Intrinsic,  Prev: Rand Intrinsic,  Up: Table of Intrinsic Functions
! 
! Random_Number Intrinsic
! .......................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL Random_Number' to use this
! name for an external procedure.
! 
! 
! File: g77.info,  Node: Random_Seed Intrinsic,  Next: Range Intrinsic,  Prev: Random_Number Intrinsic,  Up: Table of Intrinsic Functions
! 
! Random_Seed Intrinsic
! .....................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL Random_Seed' to use this name
! for an external procedure.
! 
! 
! File: g77.info,  Node: Range Intrinsic,  Next: Real Intrinsic,  Prev: Random_Seed Intrinsic,  Up: Table of Intrinsic Functions
! 
! Range Intrinsic
! ...............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL Range' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: Real Intrinsic,  Next: RealPart Intrinsic,  Prev: Range Intrinsic,  Up: Table of Intrinsic Functions
! 
! Real Intrinsic
! ..............
! 
!      Real(A)
! 
! Real: `REAL' function.  The exact type is `REAL(KIND=1)' when argument
! A is any type other than `COMPLEX', or when it is `COMPLEX(KIND=1)'.
! When A is any `COMPLEX' type other than `COMPLEX(KIND=1)', this
! intrinsic is valid only when used as the argument to `REAL()', as
! explained below.
! 
! A: `INTEGER', `REAL', or `COMPLEX'; scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Converts A to `REAL(KIND=1)'.
! 
!    Use of `REAL()' with a `COMPLEX' argument (other than
! `COMPLEX(KIND=1)') is restricted to the following case:
! 
!      REAL(REAL(A))
! 
! This expression converts the real part of A to `REAL(KIND=1)'.
! 
!    *Note RealPart Intrinsic::, for information on a GNU Fortran
! intrinsic that extracts the real part of an arbitrary `COMPLEX' value.
! 
!    *Note REAL() and AIMAG() of Complex::, for more information.
! 
! 
! File: g77.info,  Node: RealPart Intrinsic,  Next: Rename Intrinsic (subroutine),  Prev: Real Intrinsic,  Up: Table of Intrinsic Functions
! 
! RealPart Intrinsic
! ..................
! 
!      RealPart(Z)
! 
! RealPart: `REAL' function, the `KIND=' value of the type being that of
! argument Z.
! 
! Z: `COMPLEX'; scalar; INTENT(IN).
! 
! Intrinsic groups: `gnu'.
! 
! Description:
! 
!    The real part of Z is returned, without conversion.
! 
!    _Note:_ The way to do this in standard Fortran 90 is `REAL(Z)'.
! However, when, for example, Z is `COMPLEX(KIND=2)', `REAL(Z)' means
! something different for some compilers that are not true Fortran 90
! compilers but offer some extensions standardized by Fortran 90 (such as
! the `DOUBLE COMPLEX' type, also known as `COMPLEX(KIND=2)').
! 
!    The advantage of `REALPART()' is that, while not necessarily more or
! less portable than `REAL()', it is more likely to cause a compiler that
! doesn't support it to produce a diagnostic than generate incorrect code.
! 
!    *Note REAL() and AIMAG() of Complex::, for more information.
! 
! 
! File: g77.info,  Node: Rename Intrinsic (subroutine),  Next: Repeat Intrinsic,  Prev: RealPart Intrinsic,  Up: Table of Intrinsic Functions
! 
! Rename Intrinsic (subroutine)
! .............................
! 
!      CALL Rename(PATH1, PATH2, STATUS)
! 
! PATH1: `CHARACTER'; scalar; INTENT(IN).
! 
! PATH2: `CHARACTER'; scalar; INTENT(IN).
! 
! STATUS: `INTEGER(KIND=1)'; OPTIONAL; scalar; INTENT(OUT).
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Renames the file PATH1 to PATH2.  A null character (`CHAR(0)') marks
! the end of the names in PATH1 and PATH2--otherwise, trailing blanks in
! PATH1 and PATH2 are ignored.  See `rename(2)'.  If the STATUS argument
! is supplied, it contains 0 on success or a nonzero error code upon
! return.
! 
!    Some non-GNU implementations of Fortran provide this intrinsic as
! only a function, not as a subroutine, or do not support the (optional)
! STATUS argument.
! 
!    For information on other intrinsics with the same name: *Note Rename
! Intrinsic (function)::.
! 
! 
! File: g77.info,  Node: Repeat Intrinsic,  Next: Reshape Intrinsic,  Prev: Rename Intrinsic (subroutine),  Up: Table of Intrinsic Functions
! 
! Repeat Intrinsic
! ................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL Repeat' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: Reshape Intrinsic,  Next: RRSpacing Intrinsic,  Prev: Repeat Intrinsic,  Up: Table of Intrinsic Functions
! 
! Reshape Intrinsic
! .................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL Reshape' to use this name for
! an external procedure.
! 
! 
! File: g77.info,  Node: RRSpacing Intrinsic,  Next: RShift Intrinsic,  Prev: Reshape Intrinsic,  Up: Table of Intrinsic Functions
! 
! RRSpacing Intrinsic
! ...................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL RRSpacing' to use this name
! for an external procedure.
! 
! 
! File: g77.info,  Node: RShift Intrinsic,  Next: Scale Intrinsic,  Prev: RRSpacing Intrinsic,  Up: Table of Intrinsic Functions
! 
! RShift Intrinsic
! ................
! 
!      RShift(I, SHIFT)
! 
! RShift: `INTEGER' function, the `KIND=' value of the type being that of
! argument I.
! 
! I: `INTEGER'; scalar; INTENT(IN).
! 
! SHIFT: `INTEGER'; scalar; INTENT(IN).
! 
! Intrinsic groups: `f2c'.
! 
! Description:
! 
!    Returns I shifted to the right SHIFT bits.
! 
!    Although similar to the expression `I/(2**SHIFT)', there are
! important differences.  For example, the sign of the result is
! undefined.
! 
!    Currently this intrinsic is defined assuming the underlying
! representation of I is as a two's-complement integer.  It is unclear at
! this point whether that definition will apply when a different
! representation is involved.
! 
!    *Note RShift Intrinsic::, for the inverse of this function.
! 
!    *Note IShft Intrinsic::, for information on a more widely available
! right-shifting intrinsic that is also more precisely defined.
! 
! 
! File: g77.info,  Node: Scale Intrinsic,  Next: Scan Intrinsic,  Prev: RShift Intrinsic,  Up: Table of Intrinsic Functions
! 
! Scale Intrinsic
! ...............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL Scale' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: Scan Intrinsic,  Next: Second Intrinsic (function),  Prev: Scale Intrinsic,  Up: Table of Intrinsic Functions
! 
! Scan Intrinsic
! ..............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL Scan' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: Second Intrinsic (function),  Next: Second Intrinsic (subroutine),  Prev: Scan Intrinsic,  Up: Table of Intrinsic Functions
! 
! Second Intrinsic (function)
! ...........................
! 
!      Second()
! 
! Second: `REAL(KIND=1)' function.
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Returns the process's runtime in seconds--the same value as the UNIX
! function `etime' returns.
! 
!    On some systems, the underlying timings are represented using types
! with sufficiently small limits that overflows (wraparounds) are
! possible, such as 32-bit types.  Therefore, the values returned by this
! intrinsic might be, or become, negative, or numerically less than
! previous values, during a single run of the compiled program.
! 
!    For information on other intrinsics with the same name: *Note Second
! Intrinsic (subroutine)::.
! 
! 
! File: g77.info,  Node: Second Intrinsic (subroutine),  Next: Selected_Int_Kind Intrinsic,  Prev: Second Intrinsic (function),  Up: Table of Intrinsic Functions
! 
! Second Intrinsic (subroutine)
! .............................
! 
!      CALL Second(SECONDS)
! 
! SECONDS: `REAL'; scalar; INTENT(OUT).
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Returns the process's runtime in seconds in SECONDS--the same value
! as the UNIX function `etime' returns.
! 
!    On some systems, the underlying timings are represented using types
! with sufficiently small limits that overflows (wraparounds) are
! possible, such as 32-bit types.  Therefore, the values returned by this
! intrinsic might be, or become, negative, or numerically less than
! previous values, during a single run of the compiled program.
! 
!    This routine is known from Cray Fortran.  *Note CPU_Time Intrinsic::,
! for a standard equivalent.
! 
!    For information on other intrinsics with the same name: *Note Second
! Intrinsic (function)::.
! 
! 
! File: g77.info,  Node: Selected_Int_Kind Intrinsic,  Next: Selected_Real_Kind Intrinsic,  Prev: Second Intrinsic (subroutine),  Up: Table of Intrinsic Functions
! 
! Selected_Int_Kind Intrinsic
! ...........................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL Selected_Int_Kind' to use this
! name for an external procedure.
! 
! 
! File: g77.info,  Node: Selected_Real_Kind Intrinsic,  Next: Set_Exponent Intrinsic,  Prev: Selected_Int_Kind Intrinsic,  Up: Table of Intrinsic Functions
! 
! Selected_Real_Kind Intrinsic
! ............................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL Selected_Real_Kind' to use
! this name for an external procedure.
! 
! 
! File: g77.info,  Node: Set_Exponent Intrinsic,  Next: Shape Intrinsic,  Prev: Selected_Real_Kind Intrinsic,  Up: Table of Intrinsic Functions
! 
! Set_Exponent Intrinsic
! ......................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL Set_Exponent' to use this name
! for an external procedure.
! 
! 
! File: g77.info,  Node: Shape Intrinsic,  Next: Short Intrinsic,  Prev: Set_Exponent Intrinsic,  Up: Table of Intrinsic Functions
! 
! Shape Intrinsic
! ...............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL Shape' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: Short Intrinsic,  Next: Sign Intrinsic,  Prev: Shape Intrinsic,  Up: Table of Intrinsic Functions
! 
! Short Intrinsic
! ...............
! 
!      Short(A)
! 
! Short: `INTEGER(KIND=6)' function.
! 
! A: `INTEGER'; scalar; INTENT(IN).
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Returns A with the fractional portion of its magnitude truncated and
! its sign preserved, converted to type `INTEGER(KIND=6)'.
! 
!    If A is type `COMPLEX', its real part is truncated and converted,
! and its imaginary part is disregarded.
! 
!    *Note Int Intrinsic::.
! 
!    The precise meaning of this intrinsic might change in a future
! version of the GNU Fortran language, as more is learned about how it is
! used.
! 
! 
! File: g77.info,  Node: Sign Intrinsic,  Next: Signal Intrinsic (subroutine),  Prev: Short Intrinsic,  Up: Table of Intrinsic Functions
! 
! Sign Intrinsic
! ..............
! 
!      Sign(A, B)
! 
! Sign: `INTEGER' or `REAL' function, the exact type being the result of
! cross-promoting the types of all the arguments.
! 
! A: `INTEGER' or `REAL'; scalar; INTENT(IN).
! 
! B: `INTEGER' or `REAL'; scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Returns `ABS(A)*S', where S is +1 if `B.GE.0', -1 otherwise.
! 
!    *Note Abs Intrinsic::, for the function that returns the magnitude
! of a value.
! 
! 
! File: g77.info,  Node: Signal Intrinsic (subroutine),  Next: Sin Intrinsic,  Prev: Sign Intrinsic,  Up: Table of Intrinsic Functions
! 
! Signal Intrinsic (subroutine)
! .............................
! 
!      CALL Signal(NUMBER, HANDLER, STATUS)
! 
! NUMBER: `INTEGER'; scalar; INTENT(IN).
! 
! HANDLER: Signal handler (`INTEGER FUNCTION' or `SUBROUTINE') or
! dummy/global `INTEGER(KIND=1)' scalar.
! 
! STATUS: `INTEGER(KIND=7)'; OPTIONAL; scalar; INTENT(OUT).
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    If HANDLER is a an `EXTERNAL' routine, arranges for it to be invoked
! with a single integer argument (of system-dependent length) when signal
! NUMBER occurs.  If HANDLER is an integer, it can be used to turn off
! handling of signal NUMBER or revert to its default action.  See
! `signal(2)'.
! 
!    Note that HANDLER will be called using C conventions, so the value
! of its argument in Fortran terms Fortran terms is obtained by applying
! `%LOC()' (or LOC()) to it.
! 
!    The value returned by `signal(2)' is written to STATUS, if that
! argument is supplied.  Otherwise the return value is ignored.
! 
!    Some non-GNU implementations of Fortran provide this intrinsic as
! only a function, not as a subroutine, or do not support the (optional)
! STATUS argument.
! 
!    _Warning:_ Use of the `libf2c' run-time library function `signal_'
! directly (such as via `EXTERNAL SIGNAL') requires use of the `%VAL()'
! construct to pass an `INTEGER' value (such as `SIG_IGN' or `SIG_DFL')
! for the HANDLER argument.
! 
!    However, while `CALL SIGNAL(SIGNUM, %VAL(SIG_IGN))' works when
! `SIGNAL' is treated as an external procedure (and resolves, at link
! time, to `libf2c''s `signal_' routine), this construct is not valid
! when `SIGNAL' is recognized as the intrinsic of that name.
! 
!    Therefore, for maximum portability and reliability, code such
! references to the `SIGNAL' facility as follows:
! 
!      INTRINSIC SIGNAL
!      ...
!      CALL SIGNAL(SIGNUM, SIG_IGN)
! 
!    `g77' will compile such a call correctly, while other compilers will
! generally either do so as well or reject the `INTRINSIC SIGNAL'
! statement via a diagnostic, allowing you to take appropriate action.
! 
!    For information on other intrinsics with the same name: *Note Signal
! Intrinsic (function)::.
! 
! 
! File: g77.info,  Node: Sin Intrinsic,  Next: SinH Intrinsic,  Prev: Signal Intrinsic (subroutine),  Up: Table of Intrinsic Functions
! 
! Sin Intrinsic
! .............
! 
!      Sin(X)
! 
! Sin: `REAL' or `COMPLEX' function, the exact type being that of
! argument X.
! 
! X: `REAL' or `COMPLEX'; scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Returns the sine of X, an angle measured in radians.
! 
!    *Note ASin Intrinsic::, for the inverse of this function.
! 
! 
! File: g77.info,  Node: SinH Intrinsic,  Next: Sleep Intrinsic,  Prev: Sin Intrinsic,  Up: Table of Intrinsic Functions
! 
! SinH Intrinsic
! ..............
! 
!      SinH(X)
! 
! SinH: `REAL' function, the `KIND=' value of the type being that of
! argument X.
! 
! X: `REAL'; scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Returns the hyperbolic sine of X.
! 
! 
! File: g77.info,  Node: Sleep Intrinsic,  Next: Sngl Intrinsic,  Prev: SinH Intrinsic,  Up: Table of Intrinsic Functions
! 
! Sleep Intrinsic
! ...............
! 
!      CALL Sleep(SECONDS)
! 
! SECONDS: `INTEGER(KIND=1)'; scalar; INTENT(IN).
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Causes the process to pause for SECONDS seconds.  See `sleep(2)'.
! 
! 
! File: g77.info,  Node: Sngl Intrinsic,  Next: Spacing Intrinsic,  Prev: Sleep Intrinsic,  Up: Table of Intrinsic Functions
! 
! Sngl Intrinsic
! ..............
! 
!      Sngl(A)
! 
! Sngl: `REAL(KIND=1)' function.
! 
! A: `REAL(KIND=2)'; scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Archaic form of `REAL()' that is specific to one type for A.  *Note
! Real Intrinsic::.
! 
! 
! File: g77.info,  Node: Spacing Intrinsic,  Next: Spread Intrinsic,  Prev: Sngl Intrinsic,  Up: Table of Intrinsic Functions
! 
! Spacing Intrinsic
! .................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL Spacing' to use this name for
! an external procedure.
! 
! 
! File: g77.info,  Node: Spread Intrinsic,  Next: SqRt Intrinsic,  Prev: Spacing Intrinsic,  Up: Table of Intrinsic Functions
! 
! Spread Intrinsic
! ................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL Spread' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: SqRt Intrinsic,  Next: SRand Intrinsic,  Prev: Spread Intrinsic,  Up: Table of Intrinsic Functions
! 
! SqRt Intrinsic
! ..............
! 
!      SqRt(X)
! 
! SqRt: `REAL' or `COMPLEX' function, the exact type being that of
! argument X.
! 
! X: `REAL' or `COMPLEX'; scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Returns the square root of X, which must not be negative.
! 
!    To calculate and represent the square root of a negative number,
! complex arithmetic must be used.  For example, `SQRT(COMPLEX(X))'.
! 
!    The inverse of this function is `SQRT(X) * SQRT(X)'.
! 
! 
! File: g77.info,  Node: SRand Intrinsic,  Next: Stat Intrinsic (subroutine),  Prev: SqRt Intrinsic,  Up: Table of Intrinsic Functions
! 
! SRand Intrinsic
! ...............
! 
!      CALL SRand(SEED)
! 
! SEED: `INTEGER'; scalar; INTENT(IN).
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Reinitializes the generator with the seed in SEED.  *Note IRand
! Intrinsic::.  *Note Rand Intrinsic::.
! 
! 
! File: g77.info,  Node: Stat Intrinsic (subroutine),  Next: Stat Intrinsic (function),  Prev: SRand Intrinsic,  Up: Table of Intrinsic Functions
! 
! Stat Intrinsic (subroutine)
! ...........................
! 
!      CALL Stat(FILE, SARRAY, STATUS)
! 
! FILE: `CHARACTER'; scalar; INTENT(IN).
! 
! SARRAY: `INTEGER(KIND=1)'; DIMENSION(13); INTENT(OUT).
! 
! STATUS: `INTEGER(KIND=1)'; OPTIONAL; scalar; INTENT(OUT).
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Obtains data about the given file FILE and places them in the array
! SARRAY.  A null character (`CHAR(0)') marks the end of the name in
! FILE--otherwise, trailing blanks in FILE are ignored.  The values in
! this array are extracted from the `stat' structure as returned by
! `fstat(2)' q.v., as follows:
! 
!   1. Device ID
! 
!   2. Inode number
! 
!   3. File mode
! 
!   4. Number of links
! 
!   5. Owner's uid
! 
!   6. Owner's gid
! 
!   7. ID of device containing directory entry for file (0 if not
!      available)
! 
!   8. File size (bytes)
! 
!   9. Last access time
! 
!  10. Last modification time
! 
!  11. Last file status change time
! 
!  12. Preferred I/O block size (-1 if not available)
! 
!  13. Number of blocks allocated (-1 if not available)
! 
!    Not all these elements are relevant on all systems.  If an element
! is not relevant, it is returned as 0.
! 
!    If the STATUS argument is supplied, it contains 0 on success or a
! nonzero error code upon return.
! 
!    Some non-GNU implementations of Fortran provide this intrinsic as
! only a function, not as a subroutine, or do not support the (optional)
! STATUS argument.
! 
!    For information on other intrinsics with the same name: *Note Stat
! Intrinsic (function)::.
! 
! 
! File: g77.info,  Node: Stat Intrinsic (function),  Next: Sum Intrinsic,  Prev: Stat Intrinsic (subroutine),  Up: Table of Intrinsic Functions
! 
! Stat Intrinsic (function)
! .........................
! 
!      Stat(FILE, SARRAY)
! 
! Stat: `INTEGER(KIND=1)' function.
! 
! FILE: `CHARACTER'; scalar; INTENT(IN).
! 
! SARRAY: `INTEGER(KIND=1)'; DIMENSION(13); INTENT(OUT).
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Obtains data about the given file FILE and places them in the array
! SARRAY.  A null character (`CHAR(0)') marks the end of the name in
! FILE--otherwise, trailing blanks in FILE are ignored.  The values in
! this array are extracted from the `stat' structure as returned by
! `fstat(2)' q.v., as follows:
! 
!   1. Device ID
! 
!   2. Inode number
! 
!   3. File mode
! 
!   4. Number of links
! 
!   5. Owner's uid
! 
!   6. Owner's gid
! 
!   7. ID of device containing directory entry for file (0 if not
!      available)
! 
!   8. File size (bytes)
! 
!   9. Last access time
! 
!  10. Last modification time
! 
!  11. Last file status change time
! 
!  12. Preferred I/O block size (-1 if not available)
! 
!  13. Number of blocks allocated (-1 if not available)
! 
!    Not all these elements are relevant on all systems.  If an element
! is not relevant, it is returned as 0.
! 
!    Returns 0 on success or a nonzero error code.
! 
!    For information on other intrinsics with the same name: *Note Stat
! Intrinsic (subroutine)::.
! 
! 
! File: g77.info,  Node: Sum Intrinsic,  Next: SymLnk Intrinsic (subroutine),  Prev: Stat Intrinsic (function),  Up: Table of Intrinsic Functions
! 
! Sum Intrinsic
! .............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL Sum' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: SymLnk Intrinsic (subroutine),  Next: System Intrinsic (subroutine),  Prev: Sum Intrinsic,  Up: Table of Intrinsic Functions
! 
! SymLnk Intrinsic (subroutine)
! .............................
! 
!      CALL SymLnk(PATH1, PATH2, STATUS)
! 
! PATH1: `CHARACTER'; scalar; INTENT(IN).
! 
! PATH2: `CHARACTER'; scalar; INTENT(IN).
! 
! STATUS: `INTEGER(KIND=1)'; OPTIONAL; scalar; INTENT(OUT).
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Makes a symbolic link from file PATH1 to PATH2.  A null character
! (`CHAR(0)') marks the end of the names in PATH1 and PATH2--otherwise,
! trailing blanks in PATH1 and PATH2 are ignored.  If the STATUS argument
! is supplied, it contains 0 on success or a nonzero error code upon
! return (`ENOSYS' if the system does not provide `symlink(2)').
! 
!    Some non-GNU implementations of Fortran provide this intrinsic as
! only a function, not as a subroutine, or do not support the (optional)
! STATUS argument.
! 
!    For information on other intrinsics with the same name: *Note SymLnk
! Intrinsic (function)::.
! 
! 
! File: g77.info,  Node: System Intrinsic (subroutine),  Next: System_Clock Intrinsic,  Prev: SymLnk Intrinsic (subroutine),  Up: Table of Intrinsic Functions
! 
! System Intrinsic (subroutine)
! .............................
! 
!      CALL System(COMMAND, STATUS)
! 
! COMMAND: `CHARACTER'; scalar; INTENT(IN).
! 
! STATUS: `INTEGER(KIND=1)'; OPTIONAL; scalar; INTENT(OUT).
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Passes the command COMMAND to a shell (see `system(3)').  If
! argument STATUS is present, it contains the value returned by
! `system(3)', presumably 0 if the shell command succeeded.  Note that
! which shell is used to invoke the command is system-dependent and
! environment-dependent.
! 
!    Some non-GNU implementations of Fortran provide this intrinsic as
! only a function, not as a subroutine, or do not support the (optional)
! STATUS argument.
! 
!    For information on other intrinsics with the same name: *Note System
! Intrinsic (function)::.
! 
! 
! File: g77.info,  Node: System_Clock Intrinsic,  Next: Tan Intrinsic,  Prev: System Intrinsic (subroutine),  Up: Table of Intrinsic Functions
! 
! System_Clock Intrinsic
! ......................
! 
!      CALL System_Clock(COUNT, RATE, MAX)
! 
! COUNT: `INTEGER(KIND=1)'; scalar; INTENT(OUT).
! 
! RATE: `INTEGER(KIND=1)'; OPTIONAL; scalar; INTENT(OUT).
! 
! MAX: `INTEGER(KIND=1)'; OPTIONAL; scalar; INTENT(OUT).
! 
! Intrinsic groups: `f90'.
! 
! Description:
! 
!    Returns in COUNT the current value of the system clock; this is the
! value returned by the UNIX function `times(2)' in this implementation,
! but isn't in general.  RATE is the number of clock ticks per second and
! MAX is the maximum value this can take, which isn't very useful in this
! implementation since it's just the maximum C `unsigned int' value.
! 
!    On some systems, the underlying timings are represented using types
! with sufficiently small limits that overflows (wraparounds) are
! possible, such as 32-bit types.  Therefore, the values returned by this
! intrinsic might be, or become, negative, or numerically less than
! previous values, during a single run of the compiled program.
! 
! 
! File: g77.info,  Node: Tan Intrinsic,  Next: TanH Intrinsic,  Prev: System_Clock Intrinsic,  Up: Table of Intrinsic Functions
! 
! Tan Intrinsic
! .............
! 
!      Tan(X)
! 
! Tan: `REAL' function, the `KIND=' value of the type being that of
! argument X.
! 
! X: `REAL'; scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Returns the tangent of X, an angle measured in radians.
! 
!    *Note ATan Intrinsic::, for the inverse of this function.
! 
! 
! File: g77.info,  Node: TanH Intrinsic,  Next: Time Intrinsic (UNIX),  Prev: Tan Intrinsic,  Up: Table of Intrinsic Functions
! 
! TanH Intrinsic
! ..............
! 
!      TanH(X)
! 
! TanH: `REAL' function, the `KIND=' value of the type being that of
! argument X.
! 
! X: `REAL'; scalar; INTENT(IN).
! 
! Intrinsic groups: (standard FORTRAN 77).
! 
! Description:
! 
!    Returns the hyperbolic tangent of X.
! 
! 
! File: g77.info,  Node: Time Intrinsic (UNIX),  Next: Time8 Intrinsic,  Prev: TanH Intrinsic,  Up: Table of Intrinsic Functions
! 
! Time Intrinsic (UNIX)
! .....................
! 
!      Time()
! 
! Time: `INTEGER(KIND=1)' function.
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Returns the current time encoded as an integer (in the manner of the
! UNIX function `time(3)').  This value is suitable for passing to
! `CTIME', `GMTIME', and `LTIME'.
! 
!    This intrinsic is not fully portable, such as to systems with 32-bit
! `INTEGER' types but supporting times wider than 32 bits.  Therefore,
! the values returned by this intrinsic might be, or become, negative, or
! numerically less than previous values, during a single run of the
! compiled program.
! 
!    *Note Time8 Intrinsic::, for information on a similar intrinsic that
! might be portable to more GNU Fortran implementations, though to fewer
! Fortran compilers.
! 
!    For information on other intrinsics with the same name: *Note Time
! Intrinsic (VXT)::.
! 
! 
! File: g77.info,  Node: Time8 Intrinsic,  Next: Tiny Intrinsic,  Prev: Time Intrinsic (UNIX),  Up: Table of Intrinsic Functions
! 
! Time8 Intrinsic
! ...............
! 
!      Time8()
! 
! Time8: `INTEGER(KIND=2)' function.
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Returns the current time encoded as a long integer (in the manner of
! the UNIX function `time(3)').  This value is suitable for passing to
! `CTIME', `GMTIME', and `LTIME'.
! 
!    _Warning:_ this intrinsic does not increase the range of the timing
! values over that returned by `time(3)'.  On a system with a 32-bit
! `time(3)', `TIME8' will return a 32-bit value, even though converted to
! an `INTEGER(KIND=2)' value.  That means overflows of the 32-bit value
! can still occur.  Therefore, the values returned by this intrinsic
! might be, or become, negative, or numerically less than previous values,
! during a single run of the compiled program.
! 
!    No Fortran implementations other than GNU Fortran are known to
! support this intrinsic at the time of this writing.  *Note Time
! Intrinsic (UNIX)::, for information on a similar intrinsic that might
! be portable to more Fortran compilers, though to fewer GNU Fortran
! implementations.
! 
! 
! File: g77.info,  Node: Tiny Intrinsic,  Next: Transfer Intrinsic,  Prev: Time8 Intrinsic,  Up: Table of Intrinsic Functions
! 
! Tiny Intrinsic
! ..............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL Tiny' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: Transfer Intrinsic,  Next: Transpose Intrinsic,  Prev: Tiny Intrinsic,  Up: Table of Intrinsic Functions
! 
! Transfer Intrinsic
! ..................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL Transfer' to use this name for
! an external procedure.
! 
! 
! File: g77.info,  Node: Transpose Intrinsic,  Next: Trim Intrinsic,  Prev: Transfer Intrinsic,  Up: Table of Intrinsic Functions
! 
! Transpose Intrinsic
! ...................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL Transpose' to use this name
! for an external procedure.
! 
! 
! File: g77.info,  Node: Trim Intrinsic,  Next: TtyNam Intrinsic (subroutine),  Prev: Transpose Intrinsic,  Up: Table of Intrinsic Functions
! 
! Trim Intrinsic
! ..............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL Trim' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: TtyNam Intrinsic (subroutine),  Next: TtyNam Intrinsic (function),  Prev: Trim Intrinsic,  Up: Table of Intrinsic Functions
! 
! TtyNam Intrinsic (subroutine)
! .............................
! 
!      CALL TtyNam(UNIT, NAME)
! 
! UNIT: `INTEGER'; scalar; INTENT(IN).
! 
! NAME: `CHARACTER'; scalar; INTENT(OUT).
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Sets NAME to the name of the terminal device open on logical unit
! UNIT or to a blank string if UNIT is not connected to a terminal.
! 
!    Some non-GNU implementations of Fortran provide this intrinsic as
! only a function, not as a subroutine.
! 
!    For information on other intrinsics with the same name: *Note TtyNam
! Intrinsic (function)::.
! 
! 
! File: g77.info,  Node: TtyNam Intrinsic (function),  Next: UBound Intrinsic,  Prev: TtyNam Intrinsic (subroutine),  Up: Table of Intrinsic Functions
! 
! TtyNam Intrinsic (function)
! ...........................
! 
!      TtyNam(UNIT)
! 
! TtyNam: `CHARACTER*(*)' function.
! 
! UNIT: `INTEGER'; scalar; INTENT(IN).
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Returns the name of the terminal device open on logical unit UNIT or
! a blank string if UNIT is not connected to a terminal.
! 
!    For information on other intrinsics with the same name: *Note TtyNam
! Intrinsic (subroutine)::.
! 
! 
! File: g77.info,  Node: UBound Intrinsic,  Next: UMask Intrinsic (subroutine),  Prev: TtyNam Intrinsic (function),  Up: Table of Intrinsic Functions
! 
! UBound Intrinsic
! ................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL UBound' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: UMask Intrinsic (subroutine),  Next: Unlink Intrinsic (subroutine),  Prev: UBound Intrinsic,  Up: Table of Intrinsic Functions
! 
! UMask Intrinsic (subroutine)
! ............................
! 
!      CALL UMask(MASK, OLD)
! 
! MASK: `INTEGER'; scalar; INTENT(IN).
! 
! OLD: `INTEGER(KIND=1)'; OPTIONAL; scalar; INTENT(OUT).
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Sets the file creation mask to MASK and returns the old value in
! argument OLD if it is supplied.  See `umask(2)'.
! 
!    Some non-GNU implementations of Fortran provide this intrinsic as
! only a function, not as a subroutine.
! 
!    For information on other intrinsics with the same name: *Note UMask
! Intrinsic (function)::.
! 
! 
! File: g77.info,  Node: Unlink Intrinsic (subroutine),  Next: Unpack Intrinsic,  Prev: UMask Intrinsic (subroutine),  Up: Table of Intrinsic Functions
! 
! Unlink Intrinsic (subroutine)
! .............................
! 
!      CALL Unlink(FILE, STATUS)
! 
! FILE: `CHARACTER'; scalar; INTENT(IN).
! 
! STATUS: `INTEGER(KIND=1)'; OPTIONAL; scalar; INTENT(OUT).
! 
! Intrinsic groups: `unix'.
! 
! Description:
! 
!    Unlink the file FILE.  A null character (`CHAR(0)') marks the end of
! the name in FILE--otherwise, trailing blanks in FILE are ignored.  If
! the STATUS argument is supplied, it contains 0 on success or a nonzero
! error code upon return.  See `unlink(2)'.
! 
!    Some non-GNU implementations of Fortran provide this intrinsic as
! only a function, not as a subroutine, or do not support the (optional)
! STATUS argument.
! 
!    For information on other intrinsics with the same name: *Note Unlink
! Intrinsic (function)::.
! 
! 
! File: g77.info,  Node: Unpack Intrinsic,  Next: Verify Intrinsic,  Prev: Unlink Intrinsic (subroutine),  Up: Table of Intrinsic Functions
! 
! Unpack Intrinsic
! ................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL Unpack' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: Verify Intrinsic,  Next: XOr Intrinsic,  Prev: Unpack Intrinsic,  Up: Table of Intrinsic Functions
! 
! Verify Intrinsic
! ................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL Verify' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: XOr Intrinsic,  Next: ZAbs Intrinsic,  Prev: Verify Intrinsic,  Up: Table of Intrinsic Functions
! 
! XOr Intrinsic
! .............
! 
!      XOr(I, J)
! 
! XOr: `INTEGER' or `LOGICAL' function, the exact type being the result
! of cross-promoting the types of all the arguments.
! 
! I: `INTEGER' or `LOGICAL'; scalar; INTENT(IN).
! 
! J: `INTEGER' or `LOGICAL'; scalar; INTENT(IN).
! 
! Intrinsic groups: `f2c'.
! 
! Description:
! 
!    Returns value resulting from boolean exclusive-OR of pair of bits in
! each of I and J.
! 
! 
! File: g77.info,  Node: ZAbs Intrinsic,  Next: ZCos Intrinsic,  Prev: XOr Intrinsic,  Up: Table of Intrinsic Functions
! 
! ZAbs Intrinsic
! ..............
! 
!      ZAbs(A)
! 
! ZAbs: `REAL(KIND=2)' function.
! 
! A: `COMPLEX(KIND=2)'; scalar; INTENT(IN).
! 
! Intrinsic groups: `f2c'.
! 
! Description:
! 
!    Archaic form of `ABS()' that is specific to one type for A.  *Note
! Abs Intrinsic::.
! 
! 
! File: g77.info,  Node: ZCos Intrinsic,  Next: ZExp Intrinsic,  Prev: ZAbs Intrinsic,  Up: Table of Intrinsic Functions
! 
! ZCos Intrinsic
! ..............
! 
!      ZCos(X)
! 
! ZCos: `COMPLEX(KIND=2)' function.
! 
! X: `COMPLEX(KIND=2)'; scalar; INTENT(IN).
! 
! Intrinsic groups: `f2c'.
! 
! Description:
! 
!    Archaic form of `COS()' that is specific to one type for X.  *Note
! Cos Intrinsic::.
! 
! 
! File: g77.info,  Node: ZExp Intrinsic,  Next: ZLog Intrinsic,  Prev: ZCos Intrinsic,  Up: Table of Intrinsic Functions
! 
! ZExp Intrinsic
! ..............
! 
!      ZExp(X)
! 
! ZExp: `COMPLEX(KIND=2)' function.
! 
! X: `COMPLEX(KIND=2)'; scalar; INTENT(IN).
! 
! Intrinsic groups: `f2c'.
! 
! Description:
! 
!    Archaic form of `EXP()' that is specific to one type for X.  *Note
! Exp Intrinsic::.
! 
! 
! File: g77.info,  Node: ZLog Intrinsic,  Next: ZSin Intrinsic,  Prev: ZExp Intrinsic,  Up: Table of Intrinsic Functions
! 
! ZLog Intrinsic
! ..............
! 
!      ZLog(X)
! 
! ZLog: `COMPLEX(KIND=2)' function.
! 
! X: `COMPLEX(KIND=2)'; scalar; INTENT(IN).
! 
! Intrinsic groups: `f2c'.
! 
! Description:
! 
!    Archaic form of `LOG()' that is specific to one type for X.  *Note
! Log Intrinsic::.
! 
! 
! File: g77.info,  Node: ZSin Intrinsic,  Next: ZSqRt Intrinsic,  Prev: ZLog Intrinsic,  Up: Table of Intrinsic Functions
! 
! ZSin Intrinsic
! ..............
! 
!      ZSin(X)
! 
! ZSin: `COMPLEX(KIND=2)' function.
! 
! X: `COMPLEX(KIND=2)'; scalar; INTENT(IN).
! 
! Intrinsic groups: `f2c'.
! 
! Description:
! 
!    Archaic form of `SIN()' that is specific to one type for X.  *Note
! Sin Intrinsic::.
! 
! 
! File: g77.info,  Node: ZSqRt Intrinsic,  Prev: ZSin Intrinsic,  Up: Table of Intrinsic Functions
! 
! ZSqRt Intrinsic
! ...............
! 
!      ZSqRt(X)
! 
! ZSqRt: `COMPLEX(KIND=2)' function.
! 
! X: `COMPLEX(KIND=2)'; scalar; INTENT(IN).
! 
! Intrinsic groups: `f2c'.
! 
! Description:
! 
!    Archaic form of `SQRT()' that is specific to one type for X.  *Note
! SqRt Intrinsic::.
! 
! 
! File: g77.info,  Node: Scope and Classes of Names,  Next: I/O,  Prev: Functions and Subroutines,  Up: Language
! 
! Scope and Classes of Symbolic Names
! ===================================
! 
!    (The following information augments or overrides the information in
! Chapter 18 of ANSI X3.9-1978 FORTRAN 77 in specifying the GNU Fortran
! language.  Chapter 18 of that document otherwise serves as the basis
! for the relevant aspects of GNU Fortran.)
! 
! * Menu:
! 
! * Underscores in Symbol Names::
! 
! 
! File: g77.info,  Node: Underscores in Symbol Names,  Up: Scope and Classes of Names
! 
! Underscores in Symbol Names
! ---------------------------
! 
!    Underscores (`_') are accepted in symbol names after the first
! character (which must be a letter).
! 
! 
! File: g77.info,  Node: I/O,  Next: Fortran 90 Features,  Prev: Scope and Classes of Names,  Up: Language
! 
! I/O
! ===
! 
!    A dollar sign at the end of an output format specification suppresses
! the newline at the end of the output.
! 
!    Edit descriptors in `FORMAT' statements may contain compile-time
! `INTEGER' constant expressions in angle brackets, such as
!      10    FORMAT (I<WIDTH>)
! 
!    The `OPEN' specifier `NAME=' is equivalent to `FILE='.
! 
!    These Fortran 90 features are supported:
!    * The `O' and `Z' edit descriptors are supported for I/O of integers
!      in octal and hexadecimal formats, respectively.
! 
!    * The `FILE=' specifier may be omitted in an `OPEN' statement if
!      `STATUS='SCRATCH'' is supplied.  The `STATUS='REPLACE'' specifier
!      is supported.
! 
! 
! File: g77.info,  Node: Fortran 90 Features,  Prev: I/O,  Up: Language
! 
! Fortran 90 Features
! ===================
! 
!    For convenience this section collects a list (probably incomplete) of
! the Fortran 90 features supported by the GNU Fortran language, even if
! they are documented elsewhere.  *Note Characters, Lines, and Execution
! Sequence: Characters Lines Sequence, for information on additional
! fixed source form lexical issues.  Further, the free source form is
! supported through the `-ffree-form' option.  Other Fortran 90 features
! can be turned on by the `-ff90' option; see *Note Fortran 90::.  For
! information on the Fortran 90 intrinsics available, see *Note Table of
! Intrinsic Functions::.
! 
! Automatic arrays in procedures
! 
! Character assignments
!      In character assignments, the variable being assigned may occur on
!      the right hand side of the assignment.
! 
! Character strings
!      Strings may have zero length and substrings of character constants
!      are permitted.  Character constants may be enclosed in double
!      quotes (`"') as well as single quotes.  *Note Character Type::.
! 
! Construct names
!      (Symbolic tags on blocks.)  *Note Construct Names::.
! 
! `CYCLE' and `EXIT'
!      *Note The `CYCLE' and `EXIT' Statements: CYCLE and EXIT.
! 
! `DOUBLE COMPLEX'
!      *Note `DOUBLE COMPLEX' Statement: DOUBLE COMPLEX.
! 
! `DO WHILE'
!      *Note DO WHILE::.
! 
! `END' decoration
!      *Note Statements::.
! 
! `END DO'
!      *Note END DO::.
! 
! `KIND'
! 
! `IMPLICIT NONE'
! 
! `INCLUDE' statements
!      *Note INCLUDE::.
! 
! List-directed and namelist I/O on internal files
! 
! Binary, octal and hexadecimal constants
!      These are supported more generally than required by Fortran 90.
!      *Note Integer Type::.
! 
! `O' and `Z' edit descriptors
! 
! `NAMELIST'
!      *Note NAMELIST::.
! 
! `OPEN' specifiers
!      `STATUS='REPLACE'' is supported.  The `FILE=' specifier may be
!      omitted in an `OPEN' statement if `STATUS='SCRATCH'' is supplied.
! 
! `FORMAT' edit descriptors
!      The `Z' edit descriptor is supported.
! 
! Relational operators
!      The operators `<', `<=', `==', `/=', `>' and `>=' may be used
!      instead of `.LT.', `.LE.', `.EQ.', `.NE.', `.GT.' and `.GE.'
!      respectively.
! 
! `SELECT CASE'
!      Not fully implemented.  *Note `SELECT CASE' on `CHARACTER' Type:
!      SELECT CASE on CHARACTER Type.
! 
! Specification statements
!      A limited subset of the Fortran 90 syntax and semantics for
!      variable declarations is supported, including `KIND'.  *Note Kind
!      Notation::.  (`KIND' is of limited usefulness in the absence of the
!      `KIND'-related intrinsics, since these intrinsics permit writing
!      more widely portable code.)  An example of supported `KIND' usage
!      is:
!           INTEGER (KIND=1) :: FOO=1, BAR=2
!           CHARACTER (LEN=3) FOO
!      `PARAMETER' and `DIMENSION' attributes aren't supported.
! 
! 
! File: g77.info,  Node: Other Dialects,  Next: Other Compilers,  Prev: Compiler,  Up: Top
! 
! Other Dialects
! **************
! 
!    GNU Fortran supports a variety of features that are not considered
! part of the GNU Fortran language itself, but are representative of
! various dialects of Fortran that `g77' supports in whole or in part.
! 
!    Any of the features listed below might be disallowed by `g77' unless
! some command-line option is specified.  Currently, some of the features
! are accepted using the default invocation of `g77', but that might
! change in the future.
! 
!    _Note: This portion of the documentation definitely needs a lot of
! work!_
! 
! * Menu:
! 
! * Source Form::       Details of fixed-form and free-form source.
! * Trailing Comment::  Use of `/*' to start a comment.
! * Debug Line::        Use of `D' in column 1.
! * Dollar Signs::      Use of `$' in symbolic names.
! * Case Sensitivity::  Uppercase and lowercase in source files.
! * VXT Fortran::       ...versus the GNU Fortran language.
! * Fortran 90::        ...versus the GNU Fortran language.
! * Pedantic Compilation::  Enforcing the standard.
! * Distensions::       Misfeatures supported by GNU Fortran.
! 
! 
! File: g77.info,  Node: Source Form,  Next: Trailing Comment,  Up: Other Dialects
! 
! Source Form
! ===========
! 
!    GNU Fortran accepts programs written in either fixed form or free
! form.
! 
!    Fixed form corresponds to ANSI FORTRAN 77 (plus popular extensions,
! such as allowing tabs) and Fortran 90's fixed form.
! 
!    Free form corresponds to Fortran 90's free form (though possibly not
! entirely up-to-date, and without complaining about some things that for
! which Fortran 90 requires diagnostics, such as the spaces in the
! constant in `R = 3 . 1').
! 
!    The way a Fortran compiler views source files depends entirely on the
! implementation choices made for the compiler, since those choices are
! explicitly left to the implementation by the published Fortran
! standards.  GNU Fortran currently tries to be somewhat like a few
! popular compilers (`f2c', Digital ("DEC") Fortran, and so on).
! 
!    This section describes how `g77' interprets source lines.
! 
! * Menu:
! 
! * Carriage Returns::  Carriage returns ignored.
! * Tabs::              Tabs converted to spaces.
! * Short Lines::       Short lines padded with spaces (fixed-form only).
! * Long Lines::        Long lines truncated.
! * Ampersands::        Special Continuation Lines.
! 
! 
! File: g77.info,  Node: Carriage Returns,  Next: Tabs,  Up: Source Form
! 
! Carriage Returns
! ----------------
! 
!    Carriage returns (`\r') in source lines are ignored.  This is
! somewhat different from `f2c', which seems to treat them as spaces
! outside character/Hollerith constants, and encodes them as `\r' inside
! such constants.
! 
! 
! File: g77.info,  Node: Tabs,  Next: Short Lines,  Prev: Carriage Returns,  Up: Source Form
! 
! Tabs
! ----
! 
!    A source line with a <TAB> character anywhere in it is treated as
! entirely significant--however long it is--instead of ending in column
! 72 (for fixed-form source) or 132 (for free-form source).  This also is
! different from `f2c', which encodes tabs as `\t' (the ASCII <TAB>
! character) inside character and Hollerith constants, but nevertheless
! seems to treat the column position as if it had been affected by the
! canonical tab positioning.
! 
!    `g77' effectively translates tabs to the appropriate number of
! spaces (a la the default for the UNIX `expand' command) before doing
! any other processing, other than (currently) noting whether a tab was
! found on a line and using this information to decide how to interpret
! the length of the line and continued constants.
! 
! 
! File: g77.info,  Node: Short Lines,  Next: Long Lines,  Prev: Tabs,  Up: Source Form
! 
! Short Lines
! -----------
! 
!    Source lines shorter than the applicable fixed-form length are
! treated as if they were padded with spaces to that length.  (None of
! this is relevant to source files written in free form.)
! 
!    This affects only continued character and Hollerith constants, and
! is a different interpretation than provided by some other popular
! compilers (although a bit more consistent with the traditional
! punched-card basis of Fortran and the way the Fortran standard
! expressed fixed source form).
! 
!    `g77' might someday offer an option to warn about cases where
! differences might be seen as a result of this treatment, and perhaps an
! option to specify the alternate behavior as well.
! 
!    Note that this padding cannot apply to lines that are effectively of
! infinite length--such lines are specified using command-line options
! like `-ffixed-line-length-none', for example.
! 
! 
! File: g77.info,  Node: Long Lines,  Next: Ampersands,  Prev: Short Lines,  Up: Source Form
! 
! Long Lines
! ----------
! 
!    Source lines longer than the applicable length are truncated to that
! length.  Currently, `g77' does not warn if the truncated characters are
! not spaces, to accommodate existing code written for systems that
! treated truncated text as commentary (especially in columns 73 through
! 80).
! 
!    *Note Options Controlling Fortran Dialect: Fortran Dialect Options,
! for information on the `-ffixed-line-length-N' option, which can be
! used to set the line length applicable to fixed-form source files.
! 
! 
! File: g77.info,  Node: Ampersands,  Prev: Long Lines,  Up: Source Form
! 
! Ampersand Continuation Line
! ---------------------------
! 
!    A `&' in column 1 of fixed-form source denotes an arbitrary-length
! continuation line, imitating the behavior of `f2c'.
! 
! 
! File: g77.info,  Node: Trailing Comment,  Next: Debug Line,  Prev: Source Form,  Up: Other Dialects
! 
! Trailing Comment
! ================
! 
!    `g77' supports use of `/*' to start a trailing comment.  In the GNU
! Fortran language, `!' is used for this purpose.
! 
!    `/*' is not in the GNU Fortran language because the use of `/*' in a
! program might suggest to some readers that a block, not trailing,
! comment is started (and thus ended by `*/', not end of line), since
! that is the meaning of `/*' in C.
! 
!    Also, such readers might think they can use `//' to start a trailing
! comment as an alternative to `/*', but `//' already denotes
! concatenation, and such a "comment" might actually result in a program
! that compiles without error (though it would likely behave incorrectly).
! 
! 
! File: g77.info,  Node: Debug Line,  Next: Dollar Signs,  Prev: Trailing Comment,  Up: Other Dialects
! 
! Debug Line
! ==========
! 
!    Use of `D' or `d' as the first character (column 1) of a source line
! denotes a debug line.
! 
!    In turn, a debug line is treated as either a comment line or a
! normal line, depending on whether debug lines are enabled.
! 
!    When treated as a comment line, a line beginning with `D' or `d' is
! treated as if it the first character was `C' or `c', respectively.
! When treated as a normal line, such a line is treated as if the first
! character was <SPC> (space).
! 
!    (Currently, `g77' provides no means for treating debug lines as
! normal lines.)
! 
! 
! File: g77.info,  Node: Dollar Signs,  Next: Case Sensitivity,  Prev: Debug Line,  Up: Other Dialects
! 
! Dollar Signs in Symbol Names
! ============================
! 
!    Dollar signs (`$') are allowed in symbol names (after the first
! character) when the `-fdollar-ok' option is specified.
! 
! 
! File: g77.info,  Node: Case Sensitivity,  Next: VXT Fortran,  Prev: Dollar Signs,  Up: Other Dialects
! 
! Case Sensitivity
! ================
! 
!    GNU Fortran offers the programmer way too much flexibility in
! deciding how source files are to be treated vis-a-vis uppercase and
! lowercase characters.  There are 66 useful settings that affect case
! sensitivity, plus 10 settings that are nearly useless, with the
! remaining 116 settings being either redundant or useless.
! 
!    None of these settings have any effect on the contents of comments
! (the text after a `c' or `C' in Column 1, for example) or of character
! or Hollerith constants.  Note that things like the `E' in the statement
! `CALL FOO(3.2E10)' and the `TO' in `ASSIGN 10 TO LAB' are considered
! built-in keywords, and so are affected by these settings.
! 
!    Low-level switches are identified in this section as follows:
! 
!      A Source Case Conversion:
! 
!           0 Preserve (see Note 1)
! 
!           1 Convert to Upper Case
! 
!           2 Convert to Lower Case
! 
!      B Built-in Keyword Matching:
! 
!           0 Match Any Case (per-character basis)
! 
!           1 Match Upper Case Only
! 
!           2 Match Lower Case Only
! 
!           3 Match InitialCaps Only (see tables for spellings)
! 
!      C Built-in Intrinsic Matching:
! 
!           0 Match Any Case (per-character basis)
! 
!           1 Match Upper Case Only
! 
!           2 Match Lower Case Only
! 
!           3 Match InitialCaps Only (see tables for spellings)
! 
!      D User-defined Symbol Possibilities (warnings only):
! 
!           0 Allow Any Case (per-character basis)
! 
!           1 Allow Upper Case Only
! 
!           2 Allow Lower Case Only
! 
!           3 Allow InitialCaps Only (see Note 2)
! 
!    Note 1: `g77' eventually will support `NAMELIST' in a manner that is
! consistent with these source switches--in the sense that input will be
! expected to meet the same requirements as source code in terms of
! matching symbol names and keywords (for the exponent letters).
! 
!    Currently, however, `NAMELIST' is supported by `libg2c', which
! uppercases `NAMELIST' input and symbol names for matching.  This means
! not only that `NAMELIST' output currently shows symbol (and keyword)
! names in uppercase even if lower-case source conversion (option A2) is
! selected, but that `NAMELIST' cannot be adequately supported when
! source case preservation (option A0) is selected.
! 
!    If A0 is selected, a warning message will be output for each
! `NAMELIST' statement to this effect.  The behavior of the program is
! undefined at run time if two or more symbol names appear in a given
! `NAMELIST' such that the names are identical when converted to upper
! case (e.g. `NAMELIST /X/ VAR, Var, var').  For complete and total
! elegance, perhaps there should be a warning when option A2 is selected,
! since the output of NAMELIST is currently in uppercase but will someday
! be lowercase (when a `libg77' is written), but that seems to be
! overkill for a product in beta test.
! 
!    Note 2: Rules for InitialCaps names are:
! 
!    - Must be a single uppercase letter, *or*
! 
!    - Must start with an uppercase letter and contain at least one
!      lowercase letter.
! 
!    So `A', `Ab', `ABc', `AbC', and `Abc' are valid InitialCaps names,
! but `AB', `A2', and `ABC' are not.  Note that most, but not all,
! built-in names meet these requirements--the exceptions are some of the
! two-letter format specifiers, such as `BN' and `BZ'.
! 
!    Here are the names of the corresponding command-line options:
! 
!      A0: -fsource-case-preserve
!      A1: -fsource-case-upper
!      A2: -fsource-case-lower
!      
!      B0: -fmatch-case-any
!      B1: -fmatch-case-upper
!      B2: -fmatch-case-lower
!      B3: -fmatch-case-initcap
!      
!      C0: -fintrin-case-any
!      C1: -fintrin-case-upper
!      C2: -fintrin-case-lower
!      C3: -fintrin-case-initcap
!      
!      D0: -fsymbol-case-any
!      D1: -fsymbol-case-upper
!      D2: -fsymbol-case-lower
!      D3: -fsymbol-case-initcap
! 
!    Useful combinations of the above settings, along with abbreviated
! option names that set some of these combinations all at once:
! 
!       1: A0--  B0---  C0---  D0---    -fcase-preserve
!       2: A0--  B0---  C0---  D-1--
!       3: A0--  B0---  C0---  D--2-
!       4: A0--  B0---  C0---  D---3
!       5: A0--  B0---  C-1--  D0---
!       6: A0--  B0---  C-1--  D-1--
!       7: A0--  B0---  C-1--  D--2-
!       8: A0--  B0---  C-1--  D---3
!       9: A0--  B0---  C--2-  D0---
!      10: A0--  B0---  C--2-  D-1--
!      11: A0--  B0---  C--2-  D--2-
!      12: A0--  B0---  C--2-  D---3
!      13: A0--  B0---  C---3  D0---
!      14: A0--  B0---  C---3  D-1--
!      15: A0--  B0---  C---3  D--2-
!      16: A0--  B0---  C---3  D---3
!      17: A0--  B-1--  C0---  D0---
!      18: A0--  B-1--  C0---  D-1--
!      19: A0--  B-1--  C0---  D--2-
!      20: A0--  B-1--  C0---  D---3
!      21: A0--  B-1--  C-1--  D0---
!      22: A0--  B-1--  C-1--  D-1--    -fcase-strict-upper
!      23: A0--  B-1--  C-1--  D--2-
!      24: A0--  B-1--  C-1--  D---3
!      25: A0--  B-1--  C--2-  D0---
!      26: A0--  B-1--  C--2-  D-1--
!      27: A0--  B-1--  C--2-  D--2-
!      28: A0--  B-1--  C--2-  D---3
!      29: A0--  B-1--  C---3  D0---
!      30: A0--  B-1--  C---3  D-1--
!      31: A0--  B-1--  C---3  D--2-
!      32: A0--  B-1--  C---3  D---3
!      33: A0--  B--2-  C0---  D0---
!      34: A0--  B--2-  C0---  D-1--
!      35: A0--  B--2-  C0---  D--2-
!      36: A0--  B--2-  C0---  D---3
!      37: A0--  B--2-  C-1--  D0---
!      38: A0--  B--2-  C-1--  D-1--
!      39: A0--  B--2-  C-1--  D--2-
!      40: A0--  B--2-  C-1--  D---3
!      41: A0--  B--2-  C--2-  D0---
!      42: A0--  B--2-  C--2-  D-1--
!      43: A0--  B--2-  C--2-  D--2-    -fcase-strict-lower
!      44: A0--  B--2-  C--2-  D---3
!      45: A0--  B--2-  C---3  D0---
!      46: A0--  B--2-  C---3  D-1--
!      47: A0--  B--2-  C---3  D--2-
!      48: A0--  B--2-  C---3  D---3
!      49: A0--  B---3  C0---  D0---
!      50: A0--  B---3  C0---  D-1--
!      51: A0--  B---3  C0---  D--2-
!      52: A0--  B---3  C0---  D---3
!      53: A0--  B---3  C-1--  D0---
!      54: A0--  B---3  C-1--  D-1--
!      55: A0--  B---3  C-1--  D--2-
!      56: A0--  B---3  C-1--  D---3
!      57: A0--  B---3  C--2-  D0---
!      58: A0--  B---3  C--2-  D-1--
!      59: A0--  B---3  C--2-  D--2-
!      60: A0--  B---3  C--2-  D---3
!      61: A0--  B---3  C---3  D0---
!      62: A0--  B---3  C---3  D-1--
!      63: A0--  B---3  C---3  D--2-
!      64: A0--  B---3  C---3  D---3    -fcase-initcap
!      65: A-1-  B01--  C01--  D01--    -fcase-upper
!      66: A--2  B0-2-  C0-2-  D0-2-    -fcase-lower
! 
!    Number 22 is the "strict" ANSI FORTRAN 77 model wherein all input
! (except comments, character constants, and Hollerith strings) must be
! entered in uppercase.  Use `-fcase-strict-upper' to specify this
! combination.
! 
!    Number 43 is like Number 22 except all input must be lowercase.  Use
! `-fcase-strict-lower' to specify this combination.
! 
!    Number 65 is the "classic" ANSI FORTRAN 77 model as implemented on
! many non-UNIX machines whereby all the source is translated to
! uppercase.  Use `-fcase-upper' to specify this combination.
! 
!    Number 66 is the "canonical" UNIX model whereby all the source is
! translated to lowercase.  Use `-fcase-lower' to specify this
! combination.
! 
!    There are a few nearly useless combinations:
! 
!      67: A-1-  B01--  C01--  D--2-
!      68: A-1-  B01--  C01--  D---3
!      69: A-1-  B01--  C--23  D01--
!      70: A-1-  B01--  C--23  D--2-
!      71: A-1-  B01--  C--23  D---3
!      72: A--2  B01--  C0-2-  D-1--
!      73: A--2  B01--  C0-2-  D---3
!      74: A--2  B01--  C-1-3  D0-2-
!      75: A--2  B01--  C-1-3  D-1--
!      76: A--2  B01--  C-1-3  D---3
! 
!    The above allow some programs to be compiled but with restrictions
! that make most useful programs impossible: Numbers 67 and 72 warn about
! _any_ user-defined symbol names (such as `SUBROUTINE FOO'); Numbers 68
! and 73 warn about any user-defined symbol names longer than one
! character that don't have at least one non-alphabetic character after
! the first; Numbers 69 and 74 disallow any references to intrinsics; and
! Numbers 70, 71, 75, and 76 are combinations of the restrictions in
! 67+69, 68+69, 72+74, and 73+74, respectively.
! 
!    All redundant combinations are shown in the above tables anyplace
! where more than one setting is shown for a low-level switch.  For
! example, `B0-2-' means either setting 0 or 2 is valid for switch B.
! The "proper" setting in such a case is the one that copies the setting
! of switch A--any other setting might slightly reduce the speed of the
! compiler, though possibly to an unmeasurable extent.
! 
!    All remaining combinations are useless in that they prevent
! successful compilation of non-null source files (source files with
! something other than comments).
! 
! 
! File: g77.info,  Node: VXT Fortran,  Next: Fortran 90,  Prev: Case Sensitivity,  Up: Other Dialects
! 
! VXT Fortran
! ===========
! 
!    `g77' supports certain constructs that have different meanings in
! VXT Fortran than they do in the GNU Fortran language.
! 
!    Generally, this manual uses the invented term VXT Fortran to refer
! VAX FORTRAN (circa v4).  That compiler offered many popular features,
! though not necessarily those that are specific to the VAX processor
! architecture, the VMS operating system, or Digital Equipment
! Corporation's Fortran product line.  (VAX and VMS probably are
! trademarks of Digital Equipment Corporation.)
! 
!    An extension offered by a Digital Fortran product that also is
! offered by several other Fortran products for different kinds of
! systems is probably going to be considered for inclusion in `g77'
! someday, and is considered a VXT Fortran feature.
! 
!    The `-fvxt' option generally specifies that, where the meaning of a
! construct is ambiguous (means one thing in GNU Fortran and another in
! VXT Fortran), the VXT Fortran meaning is to be assumed.
! 
! * Menu:
! 
! * Double Quote Meaning::  `"2000' as octal constant.
! * Exclamation Point::     `!' in column 6.
! 
! 
! File: g77.info,  Node: Double Quote Meaning,  Next: Exclamation Point,  Up: VXT Fortran
! 
! Meaning of Double Quote
! -----------------------
! 
!    `g77' treats double-quote (`"') as beginning an octal constant of
! `INTEGER(KIND=1)' type when the `-fvxt' option is specified.  The form
! of this octal constant is
! 
!      "OCTAL-DIGITS
! 
! where OCTAL-DIGITS is a nonempty string of characters in the set
! `01234567'.
! 
!    For example, the `-fvxt' option permits this:
! 
!      PRINT *, "20
!      END
! 
! The above program would print the value `16'.
! 
!    *Note Integer Type::, for information on the preferred construct for
! integer constants specified using GNU Fortran's octal notation.
! 
!    (In the GNU Fortran language, the double-quote character (`"')
! delimits a character constant just as does apostrophe (`'').  There is
! no way to allow both constructs in the general case, since statements
! like `PRINT *,"2000 !comment?"' would be ambiguous.)
! 
! 
! File: g77.info,  Node: Exclamation Point,  Prev: Double Quote Meaning,  Up: VXT Fortran
! 
! Meaning of Exclamation Point in Column 6
! ----------------------------------------
! 
!    `g77' treats an exclamation point (`!') in column 6 of a fixed-form
! source file as a continuation character rather than as the beginning of
! a comment (as it does in any other column) when the `-fvxt' option is
! specified.
! 
!    The following program, when run, prints a message indicating whether
! it is interpreted according to GNU Fortran (and Fortran 90) rules or
! VXT Fortran rules:
! 
!      C234567  (This line begins in column 1.)
!            I = 0
!           !1
!            IF (I.EQ.0) PRINT *, ' I am a VXT Fortran program'
!            IF (I.EQ.1) PRINT *, ' I am a Fortran 90 program'
!            IF (I.LT.0 .OR. I.GT.1) PRINT *, ' I am a HAL 9000 computer'
!            END
! 
!    (In the GNU Fortran and Fortran 90 languages, exclamation point is a
! valid character and, unlike space (<SPC>) or zero (`0'), marks a line
! as a continuation line when it appears in column 6.)
! 
! 
! File: g77.info,  Node: Fortran 90,  Next: Pedantic Compilation,  Prev: VXT Fortran,  Up: Other Dialects
! 
! Fortran 90
! ==========
! 
!    The GNU Fortran language includes a number of features that are part
! of Fortran 90, even when the `-ff90' option is not specified.  The
! features enabled by `-ff90' are intended to be those that, when `-ff90'
! is not specified, would have another meaning to `g77'--usually meaning
! something invalid in the GNU Fortran language.
! 
!    So, the purpose of `-ff90' is not to specify whether `g77' is to
! gratuitously reject Fortran 90 constructs.  The `-pedantic' option
! specified with `-fno-f90' is intended to do that, although its
! implementation is certainly incomplete at this point.
! 
!    When `-ff90' is specified:
! 
!    * The type of `REAL(EXPR)' and `AIMAG(EXPR)', where EXPR is
!      `COMPLEX' type, is the same type as the real part of EXPR.
! 
!      For example, assuming `Z' is type `COMPLEX(KIND=2)', `REAL(Z)'
!      would return a value of type `REAL(KIND=2)', not of type
!      `REAL(KIND=1)', since `-ff90' is specified.
! 
! 
! File: g77.info,  Node: Pedantic Compilation,  Next: Distensions,  Prev: Fortran 90,  Up: Other Dialects
! 
! Pedantic Compilation
! ====================
! 
!    The `-fpedantic' command-line option specifies that `g77' is to warn
! about code that is not standard-conforming.  This is useful for finding
! some extensions `g77' accepts that other compilers might not accept.
! (Note that the `-pedantic' and `-pedantic-errors' options always imply
! `-fpedantic'.)
! 
!    With `-fno-f90' in force, ANSI FORTRAN 77 is used as the standard
! for conforming code.  With `-ff90' in force, Fortran 90 is used.
! 
!    The constructs for which `g77' issues diagnostics when `-fpedantic'
! and `-fno-f90' are in force are:
! 
!    * Automatic arrays, as in
! 
!           SUBROUTINE X(N)
!           REAL A(N)
!           ...
! 
!      where `A' is not listed in any `ENTRY' statement, and thus is not
!      a dummy argument.
! 
!    * The commas in `READ (5), I' and `WRITE (10), J'.
! 
!      These commas are disallowed by FORTRAN 77, but, while strictly
!      superfluous, are syntactically elegant, especially given that
!      commas are required in statements such as `READ 99, I' and `PRINT
!      *, J'.  Many compilers permit the superfluous commas for this
!      reason.
! 
!    * `DOUBLE COMPLEX', either explicitly or implicitly.
! 
!      An explicit use of this type is via a `DOUBLE COMPLEX' or
!      `IMPLICIT DOUBLE COMPLEX' statement, for examples.
! 
!      An example of an implicit use is the expression `C*D', where `C'
!      is `COMPLEX(KIND=1)' and `D' is `DOUBLE PRECISION'.  This
!      expression is prohibited by ANSI FORTRAN 77 because the rules of
!      promotion would suggest that it produce a `DOUBLE COMPLEX'
!      result--a type not provided for by that standard.
! 
!    * Automatic conversion of numeric expressions to `INTEGER(KIND=1)'
!      in contexts such as:
! 
!         - Array-reference indexes.
! 
!         - Alternate-return values.
! 
!         - Computed `GOTO'.
! 
!         - `FORMAT' run-time expressions (not yet supported).
! 
!         - Dimension lists in specification statements.
! 
!         - Numbers for I/O statements (such as `READ (UNIT=3.2), I')
! 
!         - Sizes of `CHARACTER' entities in specification statements.
! 
!         - Kind types in specification entities (a Fortran 90 feature).
! 
!         - Initial, terminal, and incrementation parameters for
!           implied-`DO' constructs in `DATA' statements.
! 
!    * Automatic conversion of `LOGICAL' expressions to `INTEGER' in
!      contexts such as arithmetic `IF' (where `COMPLEX' expressions are
!      disallowed anyway).
! 
!    * Zero-size array dimensions, as in:
! 
!           INTEGER I(10,20,4:2)
! 
!    * Zero-length `CHARACTER' entities, as in:
! 
!           PRINT *, ''
! 
!    * Substring operators applied to character constants and named
!      constants, as in:
! 
!           PRINT *, 'hello'(3:5)
! 
!    * Null arguments passed to statement function, as in:
! 
!           PRINT *, FOO(,3)
! 
!    * Disagreement among program units regarding whether a given `COMMON'
!      area is `SAVE'd (for targets where program units in a single source
!      file are "glued" together as they typically are for UNIX
!      development environments).
! 
!    * Disagreement among program units regarding the size of a named
!      `COMMON' block.
! 
!    * Specification statements following first `DATA' statement.
! 
!      (In the GNU Fortran language, `DATA I/1/' may be followed by
!      `INTEGER J', but not `INTEGER I'.  The `-fpedantic' option
!      disallows both of these.)
! 
!    * Semicolon as statement separator, as in:
! 
!           CALL FOO; CALL BAR
! 
!    * Use of `&' in column 1 of fixed-form source (to indicate
!      continuation).
! 
!    * Use of `CHARACTER' constants to initialize numeric entities, and
!      vice versa.
! 
!    * Expressions having two arithmetic operators in a row, such as
!      `X*-Y'.
! 
!    If `-fpedantic' is specified along with `-ff90', the following
! constructs result in diagnostics:
! 
!    * Use of semicolon as a statement separator on a line that has an
!      `INCLUDE' directive.
! 
! 
! File: g77.info,  Node: Distensions,  Prev: Pedantic Compilation,  Up: Other Dialects
! 
! Distensions
! ===========
! 
!    The `-fugly-*' command-line options determine whether certain
! features supported by VAX FORTRAN and other such compilers, but
! considered too ugly to be in code that can be changed to use safer
! and/or more portable constructs, are accepted.  These are humorously
! referred to as "distensions", extensions that just plain look ugly in
! the harsh light of day.
! 
! * Menu:
! 
! * Ugly Implicit Argument Conversion::  Disabled via `-fno-ugly-args'.
! * Ugly Assumed-Size Arrays::           Enabled via `-fugly-assumed'.
! * Ugly Null Arguments::                Enabled via `-fugly-comma'.
! * Ugly Complex Part Extraction::       Enabled via `-fugly-complex'.
! * Ugly Conversion of Initializers::    Disabled via `-fno-ugly-init'.
! * Ugly Integer Conversions::           Enabled via `-fugly-logint'.
! * Ugly Assigned Labels::               Enabled via `-fugly-assign'.
! 
! 
! File: g77.info,  Node: Ugly Implicit Argument Conversion,  Next: Ugly Assumed-Size Arrays,  Up: Distensions
! 
! Implicit Argument Conversion
! ----------------------------
! 
!    The `-fno-ugly-args' option disables passing typeless and Hollerith
! constants as actual arguments in procedure invocations.  For example:
! 
!      CALL FOO(4HABCD)
!      CALL BAR('123'O)
! 
! These constructs can be too easily used to create non-portable code,
! but are not considered as "ugly" as others.  Further, they are widely
! used in existing Fortran source code in ways that often are quite
! portable.  Therefore, they are enabled by default.
! 
! 
! File: g77.info,  Node: Ugly Assumed-Size Arrays,  Next: Ugly Null Arguments,  Prev: Ugly Implicit Argument Conversion,  Up: Distensions
! 
! Ugly Assumed-Size Arrays
! ------------------------
! 
!    The `-fugly-assumed' option enables the treatment of any array with
! a final dimension specified as `1' as an assumed-size array, as if `*'
! had been specified instead.
! 
!    For example, `DIMENSION X(1)' is treated as if it had read
! `DIMENSION X(*)' if `X' is listed as a dummy argument in a preceding
! `SUBROUTINE', `FUNCTION', or `ENTRY' statement in the same program unit.
! 
!    Use an explicit lower bound to avoid this interpretation.  For
! example, `DIMENSION X(1:1)' is never treated as if it had read
! `DIMENSION X(*)' or `DIMENSION X(1:*)'.  Nor is `DIMENSION X(2-1)'
! affected by this option, since that kind of expression is unlikely to
! have been intended to designate an assumed-size array.
! 
!    This option is used to prevent warnings being issued about apparent
! out-of-bounds reference such as `X(2) = 99'.
! 
!    It also prevents the array from being used in contexts that disallow
! assumed-size arrays, such as `PRINT *,X'.  In such cases, a diagnostic
! is generated and the source file is not compiled.
! 
!    The construct affected by this option is used only in old code that
! pre-exists the widespread acceptance of adjustable and assumed-size
! arrays in the Fortran community.
! 
!    _Note:_ This option does not affect how `DIMENSION X(1)' is treated
! if `X' is listed as a dummy argument only _after_ the `DIMENSION'
! statement (presumably in an `ENTRY' statement).  For example,
! `-fugly-assumed' has no effect on the following program unit:
! 
!      SUBROUTINE X
!      REAL A(1)
!      RETURN
!      ENTRY Y(A)
!      PRINT *, A
!      END
! 
! 
! File: g77.info,  Node: Ugly Complex Part Extraction,  Next: Ugly Conversion of Initializers,  Prev: Ugly Null Arguments,  Up: Distensions
! 
! Ugly Complex Part Extraction
! ----------------------------
! 
!    The `-fugly-complex' option enables use of the `REAL()' and `AIMAG()'
! intrinsics with arguments that are `COMPLEX' types other than
! `COMPLEX(KIND=1)'.
! 
!    With `-ff90' in effect, these intrinsics return the unconverted real
! and imaginary parts (respectively) of their argument.
! 
!    With `-fno-f90' in effect, these intrinsics convert the real and
! imaginary parts to `REAL(KIND=1)', and return the result of that
! conversion.
! 
!    Due to this ambiguity, the GNU Fortran language defines these
! constructs as invalid, except in the specific case where they are
! entirely and solely passed as an argument to an invocation of the
! `REAL()' intrinsic.  For example,
! 
!      REAL(REAL(Z))
! 
! is permitted even when `Z' is `COMPLEX(KIND=2)' and `-fno-ugly-complex'
! is in effect, because the meaning is clear.
! 
!    `g77' enforces this restriction, unless `-fugly-complex' is
! specified, in which case the appropriate interpretation is chosen and
! no diagnostic is issued.
! 
!    *Note CMPAMBIG::, for information on how to cope with existing code
! with unclear expectations of `REAL()' and `AIMAG()' with
! `COMPLEX(KIND=2)' arguments.
! 
!    *Note RealPart Intrinsic::, for information on the `REALPART()'
! intrinsic, used to extract the real part of a complex expression
! without conversion.  *Note ImagPart Intrinsic::, for information on the
! `IMAGPART()' intrinsic, used to extract the imaginary part of a complex
! expression without conversion.
! 
! 
! File: g77.info,  Node: Ugly Null Arguments,  Next: Ugly Complex Part Extraction,  Prev: Ugly Assumed-Size Arrays,  Up: Distensions
! 
! Ugly Null Arguments
! -------------------
! 
!    The `-fugly-comma' option enables use of a single trailing comma to
! mean "pass an extra trailing null argument" in a list of actual
! arguments to an external procedure, and use of an empty list of
! arguments to such a procedure to mean "pass a single null argument".
! 
!    (Null arguments often are used in some procedure-calling schemes to
! indicate omitted arguments.)
! 
!    For example, `CALL FOO(,)' means "pass two null arguments", rather
! than "pass one null argument".  Also, `CALL BAR()' means "pass one null
! argument".
! 
!    This construct is considered "ugly" because it does not provide an
! elegant way to pass a single null argument that is syntactically
! distinct from passing no arguments.  That is, this construct changes
! the meaning of code that makes no use of the construct.
! 
!    So, with `-fugly-comma' in force, `CALL FOO()' and `I = JFUNC()'
! pass a single null argument, instead of passing no arguments as
! required by the Fortran 77 and 90 standards.
! 
!    _Note:_ Many systems gracefully allow the case where a procedure
! call passes one extra argument that the called procedure does not
! expect.
! 
!    So, in practice, there might be no difference in the behavior of a
! program that does `CALL FOO()' or `I = JFUNC()' and is compiled with
! `-fugly-comma' in force as compared to its behavior when compiled with
! the default, `-fno-ugly-comma', in force, assuming `FOO' and `JFUNC' do
! not expect any arguments to be passed.
! 
! 
! File: g77.info,  Node: Ugly Conversion of Initializers,  Next: Ugly Integer Conversions,  Prev: Ugly Complex Part Extraction,  Up: Distensions
! 
! Ugly Conversion of Initializers
! -------------------------------
! 
!    The constructs disabled by `-fno-ugly-init' are:
! 
!    * Use of Hollerith and typeless constants in contexts where they set
!      initial (compile-time) values for variables, arrays, and named
!      constants--that is, `DATA' and `PARAMETER' statements, plus
!      type-declaration statements specifying initial values.
! 
!      Here are some sample initializations that are disabled by the
!      `-fno-ugly-init' option:
! 
!           PARAMETER (VAL='9A304FFE'X)
!           REAL*8 STRING/8HOUTPUT00/
!           DATA VAR/4HABCD/
! 
!    * In the same contexts as above, use of character constants to
!      initialize numeric items and vice versa (one constant per item).
! 
!      Here are more sample initializations that are disabled by the
!      `-fno-ugly-init' option:
! 
!           INTEGER IA
!           CHARACTER BELL
!           PARAMETER (IA = 'A')
!           PARAMETER (BELL = 7)
! 
!    * Use of Hollerith and typeless constants on the right-hand side of
!      assignment statements to numeric types, and in other contexts
!      (such as passing arguments in invocations of intrinsic procedures
!      and statement functions) that are treated as assignments to known
!      types (the dummy arguments, in these cases).
! 
!      Here are sample statements that are disabled by the
!      `-fno-ugly-init' option:
! 
!           IVAR = 4HABCD
!           PRINT *, IMAX0(2HAB, 2HBA)
! 
!    The above constructs, when used, can tend to result in non-portable
! code.  But, they are widely used in existing Fortran code in ways that
! often are quite portable.  Therefore, they are enabled by default.
! 
! 
! File: g77.info,  Node: Ugly Integer Conversions,  Next: Ugly Assigned Labels,  Prev: Ugly Conversion of Initializers,  Up: Distensions
! 
! Ugly Integer Conversions
! ------------------------
! 
!    The constructs enabled via `-fugly-logint' are:
! 
!    * Automatic conversion between `INTEGER' and `LOGICAL' as dictated by
!      context (typically implies nonportable dependencies on how a
!      particular implementation encodes `.TRUE.' and `.FALSE.').
! 
!    * Use of a `LOGICAL' variable in `ASSIGN' and assigned-`GOTO'
!      statements.
! 
!    The above constructs are disabled by default because use of them
! tends to lead to non-portable code.  Even existing Fortran code that
! uses that often turns out to be non-portable, if not outright buggy.
! 
!    Some of this is due to differences among implementations as far as
! how `.TRUE.' and `.FALSE.' are encoded as `INTEGER' values--Fortran
! code that assumes a particular coding is likely to use one of the above
! constructs, and is also likely to not work correctly on implementations
! using different encodings.
! 
!    *Note Equivalence Versus Equality::, for more information.
! 
! 
! File: g77.info,  Node: Ugly Assigned Labels,  Prev: Ugly Integer Conversions,  Up: Distensions
! 
! Ugly Assigned Labels
! --------------------
! 
!    The `-fugly-assign' option forces `g77' to use the same storage for
! assigned labels as it would for a normal assignment to the same
! variable.
! 
!    For example, consider the following code fragment:
! 
!      I = 3
!      ASSIGN 10 TO I
! 
! Normally, for portability and improved diagnostics, `g77' reserves
! distinct storage for a "sibling" of `I', used only for `ASSIGN'
! statements to that variable (along with the corresponding
! assigned-`GOTO' and assigned-`FORMAT'-I/O statements that reference the
! variable).
! 
!    However, some code (that violates the ANSI FORTRAN 77 standard)
! attempts to copy assigned labels among variables involved with `ASSIGN'
! statements, as in:
! 
!      ASSIGN 10 TO I
!      ISTATE(5) = I
!      ...
!      J = ISTATE(ICUR)
!      GOTO J
! 
! Such code doesn't work under `g77' unless `-fugly-assign' is specified
! on the command-line, ensuring that the value of `I' referenced in the
! second line is whatever value `g77' uses to designate statement label
! `10', so the value may be copied into the `ISTATE' array, later
! retrieved into a variable of the appropriate type (`J'), and used as
! the target of an assigned-`GOTO' statement.
! 
!    _Note:_ To avoid subtle program bugs, when `-fugly-assign' is
! specified, `g77' requires the type of variables specified in
! assigned-label contexts _must_ be the same type returned by `%LOC()'.
! On many systems, this type is effectively the same as
! `INTEGER(KIND=1)', while, on others, it is effectively the same as
! `INTEGER(KIND=2)'.
! 
!    Do _not_ depend on `g77' actually writing valid pointers to these
! variables, however.  While `g77' currently chooses that implementation,
! it might be changed in the future.
! 
!    *Note Assigned Statement Labels (ASSIGN and GOTO): Assigned
! Statement Labels, for implementation details on assigned-statement
! labels.
! 
! 
! File: g77.info,  Node: Compiler,  Next: Other Dialects,  Prev: Language,  Up: Top
! 
! The GNU Fortran Compiler
! ************************
! 
!    The GNU Fortran compiler, `g77', supports programs written in the
! GNU Fortran language and in some other dialects of Fortran.
! 
!    Some aspects of how `g77' works are universal regardless of dialect,
! and yet are not properly part of the GNU Fortran language itself.
! These are described below.
! 
!    _Note: This portion of the documentation definitely needs a lot of
! work!_
! 
! * Menu:
! 
! * Compiler Limits::
! * Run-time Environment Limits::
! * Compiler Types::
! * Compiler Constants::
! * Compiler Intrinsics::
! 
! 
! File: g77.info,  Node: Compiler Limits,  Next: Run-time Environment Limits,  Up: Compiler
! 
! Compiler Limits
! ===============
! 
!    `g77', as with GNU tools in general, imposes few arbitrary
! restrictions on lengths of identifiers, number of continuation lines,
! number of external symbols in a program, and so on.
! 
!    For example, some other Fortran compiler have an option (such as
! `-NlX') to increase the limit on the number of continuation lines.
! Also, some Fortran compilation systems have an option (such as `-NxX')
! to increase the limit on the number of external symbols.
! 
!    `g77', `gcc', and GNU `ld' (the GNU linker) have no equivalent
! options, since they do not impose arbitrary limits in these areas.
! 
!    `g77' does currently limit the number of dimensions in an array to
! the same degree as do the Fortran standards--seven (7).  This
! restriction might be lifted in a future version.
! 
! 
! File: g77.info,  Node: Run-time Environment Limits,  Next: Compiler Types,  Prev: Compiler Limits,  Up: Compiler
! 
! Run-time Environment Limits
! ===========================
! 
!    As a portable Fortran implementation, `g77' offers its users direct
! access to, and otherwise depends upon, the underlying facilities of the
! system used to build `g77', the system on which `g77' itself is used to
! compile programs, and the system on which the `g77'-compiled program is
! actually run.  (For most users, the three systems are of the same
! type--combination of operating environment and hardware--often the same
! physical system.)
! 
!    The run-time environment for a particular system inevitably imposes
! some limits on a program's use of various system facilities.  These
! limits vary from system to system.
! 
!    Even when such limits might be well beyond the possibility of being
! encountered on a particular system, the `g77' run-time environment has
! certain built-in limits, usually, but not always, stemming from
! intrinsics with inherently limited interfaces.
! 
!    Currently, the `g77' run-time environment does not generally offer a
! less-limiting environment by augmenting the underlying system's own
! environment.
! 
!    Therefore, code written in the GNU Fortran language, while
! syntactically and semantically portable, might nevertheless make
! non-portable assumptions about the run-time environment--assumptions
! that prove to be false for some particular environments.
! 
!    The GNU Fortran language, the `g77' compiler and run-time
! environment, and the `g77' documentation do not yet offer comprehensive
! portable work-arounds for such limits, though programmers should be
! able to find their own in specific instances.
! 
!    Not all of the limitations are described in this document.  Some of
! the known limitations include:
! 
! * Menu:
! 
! * Timer Wraparounds::
! * Year 2000 (Y2K) Problems::
! * Array Size::
! * Character-variable Length::
! * Year 10000 (Y10K) Problems::
! 
! 
! File: g77.info,  Node: Timer Wraparounds,  Next: Year 2000 (Y2K) Problems,  Up: Run-time Environment Limits
! 
! Timer Wraparounds
! -----------------
! 
!    Intrinsics that return values computed from system timers, whether
! elapsed (wall-clock) timers, process CPU timers, or other kinds of
! timers, are prone to experiencing wrap-around errors (or returning
! wrapped-around values from successive calls) due to insufficient ranges
! offered by the underlying system's timers.
! 
!    Some of the symptoms of such behaviors include apparently negative
! time being computed for a duration, an extremely short amount of time
! being computed for a long duration, and an extremely long amount of
! time being computed for a short duration.
! 
!    See the following for intrinsics known to have potential problems in
! these areas on at least some systems: *Note CPU_Time Intrinsic::, *Note
! DTime Intrinsic (function)::, *Note DTime Intrinsic (subroutine)::,
! *Note ETime Intrinsic (function)::, *Note ETime Intrinsic
! (subroutine)::, *Note MClock Intrinsic::, *Note MClock8 Intrinsic::,
! *Note Secnds Intrinsic::, *Note Second Intrinsic (function)::, *Note
! Second Intrinsic (subroutine)::, *Note System_Clock Intrinsic::, *Note
! Time Intrinsic (UNIX)::, *Note Time Intrinsic (VXT)::, *Note Time8
! Intrinsic::.
! 
! 
! File: g77.info,  Node: Year 2000 (Y2K) Problems,  Next: Array Size,  Prev: Timer Wraparounds,  Up: Run-time Environment Limits
! 
! Year 2000 (Y2K) Problems
! ------------------------
! 
!    While the `g77' compiler itself is believed to be Year-2000 (Y2K)
! compliant, some intrinsics are not, and, potentially, some underlying
! systems are not, perhaps rendering some Y2K-compliant intrinsics
! non-compliant when used on those particular systems.
! 
!    Fortran code that uses non-Y2K-compliant intrinsics (listed below)
! is, itself, almost certainly not compliant, and should be modified to
! use Y2K-compliant intrinsics instead.
! 
!    Fortran code that uses no non-Y2K-compliant intrinsics, but which
! currently is running on a non-Y2K-compliant system, can be made more
! Y2K compliant by compiling and linking it for use on a new
! Y2K-compliant system, such as a new version of an old,
! non-Y2K-compliant, system.
! 
!    Currently, information on Y2K and related issues is being maintained
! at `http://www.gnu.org/software/year2000-list.html'.
! 
!    See the following for intrinsics known to have potential problems in
! these areas on at least some systems: *Note Date Intrinsic::, *Note
! IDate Intrinsic (VXT)::.
! 
!    The `libg2c' library shipped with any `g77' that warns about
! invocation of a non-Y2K-compliant intrinsic has renamed the `EXTERNAL'
! procedure names of those intrinsics.  This is done so that the `libg2c'
! implementations of these intrinsics cannot be directly linked to as
! `EXTERNAL' names (which normally would avoid the non-Y2K-intrinsic
! warning).
! 
!    The renamed forms of the `EXTERNAL' names of these renamed procedures
! may be linked to by appending the string `_y2kbug' to the name of the
! procedure in the source code.  For example:
! 
!      CHARACTER*20 STR
!      INTEGER YY, MM, DD
!      EXTERNAL DATE_Y2KBUG, VXTIDATE_Y2KBUG
!      CALL DATE_Y2KBUG (STR)
!      CALL VXTIDATE_Y2KBUG (MM, DD, YY)
! 
!    (Note that the `EXTERNAL' statement is not actually required, since
! the modified names are not recognized as intrinsics by the current
! version of `g77'.  But it is shown in this specific case, for purposes
! of illustration.)
! 
!    The renaming of `EXTERNAL' procedure names of these intrinsics
! causes unresolved references at link time.  For example, `EXTERNAL
! DATE; CALL DATE(STR)' is normally compiled by `g77' as, in C,
! `date_(&str, 20);'.  This, in turn, links to the `date_' procedure in
! the `libE77' portion of `libg2c', which purposely calls a nonexistent
! procedure named `G77_date_y2kbuggy_0'.  The resulting link-time error
! is designed, via this name, to encourage the programmer to look up the
! index entries to this portion of the `g77' documentation.
! 
!    Generally, we recommend that the `EXTERNAL' method of invoking
! procedures in `libg2c' _not_ be used.  When used, some of the
! correctness checking normally performed by `g77' is skipped.
! 
!    In particular, it is probably better to use the `INTRINSIC' method
! of invoking non-Y2K-compliant procedures, so anyone compiling the code
! can quickly notice the potential Y2K problems (via the warnings
! printing by `g77') without having to even look at the code itself.
! 
!    If there are problems linking `libg2c' to code compiled by `g77'
! that involve the string `y2kbug', and these are not explained above,
! that probably indicates that a version of `libg2c' older than `g77' is
! being linked to, or that the new library is being linked to code
! compiled by an older version of `g77'.
! 
!    That's because, as of the version that warns about non-Y2K-compliant
! intrinsic invocation, `g77' references the `libg2c' implementations of
! those intrinsics using new names, containing the string `y2kbug'.
! 
!    So, linking newly-compiled code (invoking one of the intrinsics in
! question) to an old library might yield an unresolved reference to
! `G77_date_y2kbug_0'.  (The old library calls it `G77_date_0'.)
! 
!    Similarly, linking previously-compiled code to a new library might
! yield an unresolved reference to `G77_vxtidate_0'.  (The new library
! calls it `G77_vxtidate_y2kbug_0'.)
! 
!    The proper fix for the above problems is to obtain the latest
! release of `g77' and related products (including `libg2c') and install
! them on all systems, then recompile, relink, and install (as
! appropriate) all existing Fortran programs.
! 
!    (Normally, this sort of renaming is steadfastly avoided.  In this
! case, however, it seems more important to highlight potential Y2K
! problems than to ease the transition of potentially non-Y2K-compliant
! code to new versions of `g77' and `libg2c'.)
! 
! 
! File: g77.info,  Node: Array Size,  Next: Character-variable Length,  Prev: Year 2000 (Y2K) Problems,  Up: Run-time Environment Limits
! 
! Array Size
! ----------
! 
!    Currently, `g77' uses the default `INTEGER' type for array indexes,
! which limits the sizes of single-dimension arrays on systems offering a
! larger address space than can be addressed by that type.  (That `g77'
! puts all arrays in memory could be considered another limitation--it
! could use large temporary files--but that decision is left to the
! programmer as an implementation choice by most Fortran implementations.)
! 
!    It is not yet clear whether this limitation never, sometimes, or
! always applies to the sizes of multiple-dimension arrays as a whole.
! 
!    For example, on a system with 64-bit addresses and 32-bit default
! `INTEGER', an array with a size greater than can be addressed by a
! 32-bit offset can be declared using multiple dimensions.  Such an array
! is therefore larger than a single-dimension array can be, on the same
! system.
! 
!    Whether large multiple-dimension arrays are reliably supported
! depends mostly on the `gcc' back end (code generator) used by `g77',
! and has not yet been fully investigated.
! 
! 
! File: g77.info,  Node: Character-variable Length,  Next: Year 10000 (Y10K) Problems,  Prev: Array Size,  Up: Run-time Environment Limits
! 
! Character-variable Length
! -------------------------
! 
!    Currently, `g77' uses the default `INTEGER' type for the lengths of
! `CHARACTER' variables and array elements.
! 
!    This means that, for example, a system with a 64-bit address space
! and a 32-bit default `INTEGER' type does not, under `g77', support a
! `CHARACTER*N' declaration where N is greater than 2147483647.
! 
! 
! File: g77.info,  Node: Year 10000 (Y10K) Problems,  Prev: Character-variable Length,  Up: Run-time Environment Limits
! 
! Year 10000 (Y10K) Problems
! --------------------------
! 
!    Most intrinsics returning, or computing values based on, date
! information are prone to Year-10000 (Y10K) problems, due to supporting
! only 4 digits for the year.
! 
!    See the following for examples: *Note FDate Intrinsic (function)::,
! *Note FDate Intrinsic (subroutine)::, *Note IDate Intrinsic (UNIX)::,
! *Note Time Intrinsic (VXT)::, *Note Date_and_Time Intrinsic::.
! 
! 
! File: g77.info,  Node: Compiler Types,  Next: Compiler Constants,  Prev: Run-time Environment Limits,  Up: Compiler
! 
! Compiler Types
! ==============
! 
!    Fortran implementations have a fair amount of freedom given them by
! the standard as far as how much storage space is used and how much
! precision and range is offered by the various types such as
! `LOGICAL(KIND=1)', `INTEGER(KIND=1)', `REAL(KIND=1)', `REAL(KIND=2)',
! `COMPLEX(KIND=1)', and `CHARACTER'.  Further, many compilers offer
! so-called `*N' notation, but the interpretation of N varies across
! compilers and target architectures.
! 
!    The standard requires that `LOGICAL(KIND=1)', `INTEGER(KIND=1)', and
! `REAL(KIND=1)' occupy the same amount of storage space, and that
! `COMPLEX(KIND=1)' and `REAL(KIND=2)' take twice as much storage space
! as `REAL(KIND=1)'.  Further, it requires that `COMPLEX(KIND=1)'
! entities be ordered such that when a `COMPLEX(KIND=1)' variable is
! storage-associated (such as via `EQUIVALENCE') with a two-element
! `REAL(KIND=1)' array named `R', `R(1)' corresponds to the real element
! and `R(2)' to the imaginary element of the `COMPLEX(KIND=1)' variable.
! 
!    (Few requirements as to precision or ranges of any of these are
! placed on the implementation, nor is the relationship of storage sizes
! of these types to the `CHARACTER' type specified, by the standard.)
! 
!    `g77' follows the above requirements, warning when compiling a
! program requires placement of items in memory that contradict the
! requirements of the target architecture.  (For example, a program can
! require placement of a `REAL(KIND=2)' on a boundary that is not an even
! multiple of its size, but still an even multiple of the size of a
! `REAL(KIND=1)' variable.  On some target architectures, using the
! canonical mapping of Fortran types to underlying architectural types,
! such placement is prohibited by the machine definition or the
! Application Binary Interface (ABI) in force for the configuration
! defined for building `gcc' and `g77'.  `g77' warns about such
! situations when it encounters them.)
! 
!    `g77' follows consistent rules for configuring the mapping between
! Fortran types, including the `*N' notation, and the underlying
! architectural types as accessed by a similarly-configured applicable
! version of the `gcc' compiler.  These rules offer a widely portable,
! consistent Fortran/C environment, although they might well conflict
! with the expectations of users of Fortran compilers designed and
! written for particular architectures.
! 
!    These rules are based on the configuration that is in force for the
! version of `gcc' built in the same release as `g77' (and which was
! therefore used to build both the `g77' compiler components and the
! `libg2c' run-time library):
! 
! `REAL(KIND=1)'
!      Same as `float' type.
! 
! `REAL(KIND=2)'
!      Same as whatever floating-point type that is twice the size of a
!      `float'--usually, this is a `double'.
! 
! `INTEGER(KIND=1)'
!      Same as an integral type that is occupies the same amount of
!      memory storage as `float'--usually, this is either an `int' or a
!      `long int'.
! 
! `LOGICAL(KIND=1)'
!      Same `gcc' type as `INTEGER(KIND=1)'.
! 
! `INTEGER(KIND=2)'
!      Twice the size, and usually nearly twice the range, as
!      `INTEGER(KIND=1)'--usually, this is either a `long int' or a `long
!      long int'.
! 
! `LOGICAL(KIND=2)'
!      Same `gcc' type as `INTEGER(KIND=2)'.
! 
! `INTEGER(KIND=3)'
!      Same `gcc' type as signed `char'.
! 
! `LOGICAL(KIND=3)'
!      Same `gcc' type as `INTEGER(KIND=3)'.
! 
! `INTEGER(KIND=6)'
!      Twice the size, and usually nearly twice the range, as
!      `INTEGER(KIND=3)'--usually, this is a `short'.
! 
! `LOGICAL(KIND=6)'
!      Same `gcc' type as `INTEGER(KIND=6)'.
! 
! `COMPLEX(KIND=1)'
!      Two `REAL(KIND=1)' scalars (one for the real part followed by one
!      for the imaginary part).
! 
! `COMPLEX(KIND=2)'
!      Two `REAL(KIND=2)' scalars.
! 
! `NUMERIC-TYPE*N'
!      (Where NUMERIC-TYPE is any type other than `CHARACTER'.)  Same as
!      whatever `gcc' type occupies N times the storage space of a `gcc'
!      `char' item.
! 
! `DOUBLE PRECISION'
!      Same as `REAL(KIND=2)'.
! 
! `DOUBLE COMPLEX'
!      Same as `COMPLEX(KIND=2)'.
! 
!    Note that the above are proposed correspondences and might change in
! future versions of `g77'--avoid writing code depending on them.
! 
!    Other types supported by `g77' are derived from gcc types such as
! `char', `short', `int', `long int', `long long int', `long double', and
! so on.  That is, whatever types `gcc' already supports, `g77' supports
! now or probably will support in a future version.  The rules for the
! `NUMERIC-TYPE*N' notation apply to these types, and new values for
! `NUMERIC-TYPE(KIND=N)' will be assigned in a way that encourages
! clarity, consistency, and portability.
! 
! 
! File: g77.info,  Node: Compiler Constants,  Next: Compiler Intrinsics,  Prev: Compiler Types,  Up: Compiler
! 
! Compiler Constants
! ==================
! 
!    `g77' strictly assigns types to _all_ constants not documented as
! "typeless" (typeless constants including `'1'Z', for example).  Many
! other Fortran compilers attempt to assign types to typed constants
! based on their context.  This results in hard-to-find bugs, nonportable
! code, and is not in the spirit (though it strictly follows the letter)
! of the 77 and 90 standards.
! 
!    `g77' might offer, in a future release, explicit constructs by which
! a wider variety of typeless constants may be specified, and/or
! user-requested warnings indicating places where `g77' might differ from
! how other compilers assign types to constants.
! 
!    *Note Context-Sensitive Constants::, for more information on this
! issue.
! 
! 
! File: g77.info,  Node: Compiler Intrinsics,  Prev: Compiler Constants,  Up: Compiler
! 
! Compiler Intrinsics
! ===================
! 
!    `g77' offers an ever-widening set of intrinsics.  Currently these
! all are procedures (functions and subroutines).
! 
!    Some of these intrinsics are unimplemented, but their names reserved
! to reduce future problems with existing code as they are implemented.
! Others are implemented as part of the GNU Fortran language, while yet
! others are provided for compatibility with other dialects of Fortran
! but are not part of the GNU Fortran language.
! 
!    To manage these distinctions, `g77' provides intrinsic _groups_, a
! facility that is simply an extension of the intrinsic groups provided
! by the GNU Fortran language.
! 
! * Menu:
! 
! * Intrinsic Groups::  How intrinsics are grouped for easy management.
! * Other Intrinsics::  Intrinsics other than those in the GNU
!                        Fortran language.
! 
! 
! File: g77.info,  Node: Intrinsic Groups,  Next: Other Intrinsics,  Up: Compiler Intrinsics
! 
! Intrinsic Groups
! ----------------
! 
!    A given specific intrinsic belongs in one or more groups.  Each
! group is deleted, disabled, hidden, or enabled by default or a
! command-line option.  The meaning of each term follows.
! 
! Deleted
!      No intrinsics are recognized as belonging to that group.
! 
! Disabled
!      Intrinsics are recognized as belonging to the group, but
!      references to them (other than via the `INTRINSIC' statement) are
!      disallowed through that group.
! 
! Hidden
!      Intrinsics in that group are recognized and enabled (if
!      implemented) _only_ if the first mention of the actual name of an
!      intrinsic in a program unit is in an `INTRINSIC' statement.
! 
! Enabled
!      Intrinsics in that group are recognized and enabled (if
!      implemented).
! 
!    The distinction between deleting and disabling a group is illustrated
! by the following example.  Assume intrinsic `FOO' belongs only to group
! `FGR'.  If group `FGR' is deleted, the following program unit will
! successfully compile, because `FOO()' will be seen as a reference to an
! external function named `FOO':
! 
!      PRINT *, FOO()
!      END
! 
! If group `FGR' is disabled, compiling the above program will produce
! diagnostics, either because the `FOO' intrinsic is improperly invoked
! or, if properly invoked, it is not enabled.  To change the above
! program so it references an external function `FOO' instead of the
! disabled `FOO' intrinsic, add the following line to the top:
! 
!      EXTERNAL FOO
! 
! So, deleting a group tells `g77' to pretend as though the intrinsics in
! that group do not exist at all, whereas disabling it tells `g77' to
! recognize them as (disabled) intrinsics in intrinsic-like contexts.
! 
!    Hiding a group is like enabling it, but the intrinsic must be first
! named in an `INTRINSIC' statement to be considered a reference to the
! intrinsic rather than to an external procedure.  This might be the
! "safest" way to treat a new group of intrinsics when compiling old
! code, because it allows the old code to be generally written as if
! those new intrinsics never existed, but to be changed to use them by
! inserting `INTRINSIC' statements in the appropriate places.  However,
! it should be the goal of development to use `EXTERNAL' for all names of
! external procedures that might be intrinsic names.
! 
!    If an intrinsic is in more than one group, it is enabled if any of
! its containing groups are enabled; if not so enabled, it is hidden if
! any of its containing groups are hidden; if not so hidden, it is
! disabled if any of its containing groups are disabled; if not so
! disabled, it is deleted.  This extra complication is necessary because
! some intrinsics, such as `IBITS', belong to more than one group, and
! hence should be enabled if any of the groups to which they belong are
! enabled, and so on.
! 
!    The groups are:
! 
! `badu77'
!      UNIX intrinsics having inappropriate forms (usually functions that
!      have intended side effects).
! 
! `gnu'
!      Intrinsics the GNU Fortran language supports that are extensions to
!      the Fortran standards (77 and 90).
! 
! `f2c'
!      Intrinsics supported by AT&T's `f2c' converter and/or `libf2c'.
! 
! `f90'
!      Fortran 90 intrinsics.
! 
! `mil'
!      MIL-STD 1753 intrinsics (`MVBITS', `IAND', `BTEST', and so on).
! 
! `unix'
!      UNIX intrinsics (`IARGC', `EXIT', `ERF', and so on).
! 
! `vxt'
!      VAX/VMS FORTRAN (current as of v4) intrinsics.
! 
! 
! File: g77.info,  Node: Other Intrinsics,  Prev: Intrinsic Groups,  Up: Compiler Intrinsics
! 
! Other Intrinsics
! ----------------
! 
!    `g77' supports intrinsics other than those in the GNU Fortran
! language proper.  This set of intrinsics is described below.
! 
!    (Note that the empty lines appearing in the menu below are not
! intentional--they result from a bug in the `makeinfo' program.)
! 
! * Menu:
! 
! 
! * ACosD Intrinsic::     (Reserved for future use.)
! 
! * AIMax0 Intrinsic::    (Reserved for future use.)
! * AIMin0 Intrinsic::    (Reserved for future use.)
! 
! * AJMax0 Intrinsic::    (Reserved for future use.)
! * AJMin0 Intrinsic::    (Reserved for future use.)
! 
! * ASinD Intrinsic::     (Reserved for future use.)
! 
! * ATan2D Intrinsic::    (Reserved for future use.)
! * ATanD Intrinsic::     (Reserved for future use.)
! 
! * BITest Intrinsic::    (Reserved for future use.)
! 
! * BJTest Intrinsic::    (Reserved for future use.)
! 
! * CDAbs Intrinsic::     Absolute value (archaic).
! * CDCos Intrinsic::     Cosine (archaic).
! * CDExp Intrinsic::     Exponential (archaic).
! * CDLog Intrinsic::     Natural logarithm (archaic).
! * CDSin Intrinsic::     Sine (archaic).
! * CDSqRt Intrinsic::    Square root (archaic).
! 
! * ChDir Intrinsic (function):: Change directory.
! 
! * ChMod Intrinsic (function):: Change file modes.
! 
! * CosD Intrinsic::      (Reserved for future use.)
! 
! * DACosD Intrinsic::    (Reserved for future use.)
! 
! * DASinD Intrinsic::    (Reserved for future use.)
! 
! * DATan2D Intrinsic::   (Reserved for future use.)
! * DATanD Intrinsic::    (Reserved for future use.)
! * Date Intrinsic::      Get current date as dd-Mon-yy.
! 
! * DbleQ Intrinsic::     (Reserved for future use.)
! 
! * DCmplx Intrinsic::    Construct `COMPLEX(KIND=2)' value.
! * DConjg Intrinsic::    Complex conjugate (archaic).
! 
! * DCosD Intrinsic::     (Reserved for future use.)
! 
! * DFloat Intrinsic::    Conversion (archaic).
! 
! * DFlotI Intrinsic::    (Reserved for future use.)
! * DFlotJ Intrinsic::    (Reserved for future use.)
! 
! * DImag Intrinsic::     Convert/extract imaginary part of complex (archaic).
! 
! * DReal Intrinsic::     Convert value to type `REAL(KIND=2)'.
! 
! * DSinD Intrinsic::     (Reserved for future use.)
! 
! * DTanD Intrinsic::     (Reserved for future use.)
! 
! * DTime Intrinsic (function):: Get elapsed time since last time.
! 
! * FGet Intrinsic (function):: Read a character from unit 5 stream-wise.
! 
! * FGetC Intrinsic (function):: Read a character stream-wise.
! 
! * FloatI Intrinsic::    (Reserved for future use.)
! * FloatJ Intrinsic::    (Reserved for future use.)
! 
! * FPut Intrinsic (function):: Write a character to unit 6 stream-wise.
! 
! * FPutC Intrinsic (function):: Write a character stream-wise.
! 
! * IDate Intrinsic (VXT):: Get local time info (VAX/VMS).
! 
! * IIAbs Intrinsic::     (Reserved for future use.)
! * IIAnd Intrinsic::     (Reserved for future use.)
! * IIBClr Intrinsic::    (Reserved for future use.)
! * IIBits Intrinsic::    (Reserved for future use.)
! * IIBSet Intrinsic::    (Reserved for future use.)
! * IIDiM Intrinsic::     (Reserved for future use.)
! * IIDInt Intrinsic::    (Reserved for future use.)
! * IIDNnt Intrinsic::    (Reserved for future use.)
! * IIEOr Intrinsic::     (Reserved for future use.)
! * IIFix Intrinsic::     (Reserved for future use.)
! * IInt Intrinsic::      (Reserved for future use.)
! * IIOr Intrinsic::      (Reserved for future use.)
! * IIQint Intrinsic::    (Reserved for future use.)
! * IIQNnt Intrinsic::    (Reserved for future use.)
! * IIShftC Intrinsic::   (Reserved for future use.)
! * IISign Intrinsic::    (Reserved for future use.)
! 
! * IMax0 Intrinsic::     (Reserved for future use.)
! * IMax1 Intrinsic::     (Reserved for future use.)
! * IMin0 Intrinsic::     (Reserved for future use.)
! * IMin1 Intrinsic::     (Reserved for future use.)
! * IMod Intrinsic::      (Reserved for future use.)
! 
! * INInt Intrinsic::     (Reserved for future use.)
! * INot Intrinsic::      (Reserved for future use.)
! 
! * IZExt Intrinsic::     (Reserved for future use.)
! * JIAbs Intrinsic::     (Reserved for future use.)
! * JIAnd Intrinsic::     (Reserved for future use.)
! * JIBClr Intrinsic::    (Reserved for future use.)
! * JIBits Intrinsic::    (Reserved for future use.)
! * JIBSet Intrinsic::    (Reserved for future use.)
! * JIDiM Intrinsic::     (Reserved for future use.)
! * JIDInt Intrinsic::    (Reserved for future use.)
! * JIDNnt Intrinsic::    (Reserved for future use.)
! * JIEOr Intrinsic::     (Reserved for future use.)
! * JIFix Intrinsic::     (Reserved for future use.)
! * JInt Intrinsic::      (Reserved for future use.)
! * JIOr Intrinsic::      (Reserved for future use.)
! * JIQint Intrinsic::    (Reserved for future use.)
! * JIQNnt Intrinsic::    (Reserved for future use.)
! * JIShft Intrinsic::    (Reserved for future use.)
! * JIShftC Intrinsic::   (Reserved for future use.)
! * JISign Intrinsic::    (Reserved for future use.)
! * JMax0 Intrinsic::     (Reserved for future use.)
! * JMax1 Intrinsic::     (Reserved for future use.)
! * JMin0 Intrinsic::     (Reserved for future use.)
! * JMin1 Intrinsic::     (Reserved for future use.)
! * JMod Intrinsic::      (Reserved for future use.)
! * JNInt Intrinsic::     (Reserved for future use.)
! * JNot Intrinsic::      (Reserved for future use.)
! * JZExt Intrinsic::     (Reserved for future use.)
! 
! * Kill Intrinsic (function):: Signal a process.
! 
! * Link Intrinsic (function):: Make hard link in file system.
! 
! * QAbs Intrinsic::      (Reserved for future use.)
! * QACos Intrinsic::     (Reserved for future use.)
! * QACosD Intrinsic::    (Reserved for future use.)
! * QASin Intrinsic::     (Reserved for future use.)
! * QASinD Intrinsic::    (Reserved for future use.)
! * QATan Intrinsic::     (Reserved for future use.)
! * QATan2 Intrinsic::    (Reserved for future use.)
! * QATan2D Intrinsic::   (Reserved for future use.)
! * QATanD Intrinsic::    (Reserved for future use.)
! * QCos Intrinsic::      (Reserved for future use.)
! * QCosD Intrinsic::     (Reserved for future use.)
! * QCosH Intrinsic::     (Reserved for future use.)
! * QDiM Intrinsic::      (Reserved for future use.)
! * QExp Intrinsic::      (Reserved for future use.)
! * QExt Intrinsic::      (Reserved for future use.)
! * QExtD Intrinsic::     (Reserved for future use.)
! * QFloat Intrinsic::    (Reserved for future use.)
! * QInt Intrinsic::      (Reserved for future use.)
! * QLog Intrinsic::      (Reserved for future use.)
! * QLog10 Intrinsic::    (Reserved for future use.)
! * QMax1 Intrinsic::     (Reserved for future use.)
! * QMin1 Intrinsic::     (Reserved for future use.)
! * QMod Intrinsic::      (Reserved for future use.)
! * QNInt Intrinsic::     (Reserved for future use.)
! * QSin Intrinsic::      (Reserved for future use.)
! * QSinD Intrinsic::     (Reserved for future use.)
! * QSinH Intrinsic::     (Reserved for future use.)
! * QSqRt Intrinsic::     (Reserved for future use.)
! * QTan Intrinsic::      (Reserved for future use.)
! * QTanD Intrinsic::     (Reserved for future use.)
! * QTanH Intrinsic::     (Reserved for future use.)
! 
! * Rename Intrinsic (function):: Rename file.
! 
! * Secnds Intrinsic::    Get local time offset since midnight.
! 
! * Signal Intrinsic (function):: Muck with signal handling.
! 
! * SinD Intrinsic::      (Reserved for future use.)
! 
! * SnglQ Intrinsic::     (Reserved for future use.)
! 
! * SymLnk Intrinsic (function):: Make symbolic link in file system.
! 
! * System Intrinsic (function):: Invoke shell (system) command.
! 
! * TanD Intrinsic::      (Reserved for future use.)
! 
! * Time Intrinsic (VXT):: Get the time as a character value.
! 
! * UMask Intrinsic (function):: Set file creation permissions mask.
! 
! * Unlink Intrinsic (function):: Unlink file.
! 
! * ZExt Intrinsic::      (Reserved for future use.)
! 
! 
! File: g77.info,  Node: ACosD Intrinsic,  Next: AIMax0 Intrinsic,  Up: Other Intrinsics
! 
! ACosD Intrinsic
! ...............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL ACosD' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: AIMax0 Intrinsic,  Next: AIMin0 Intrinsic,  Prev: ACosD Intrinsic,  Up: Other Intrinsics
! 
! AIMax0 Intrinsic
! ................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL AIMax0' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: AIMin0 Intrinsic,  Next: AJMax0 Intrinsic,  Prev: AIMax0 Intrinsic,  Up: Other Intrinsics
! 
! AIMin0 Intrinsic
! ................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL AIMin0' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: AJMax0 Intrinsic,  Next: AJMin0 Intrinsic,  Prev: AIMin0 Intrinsic,  Up: Other Intrinsics
! 
! AJMax0 Intrinsic
! ................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL AJMax0' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: AJMin0 Intrinsic,  Next: ASinD Intrinsic,  Prev: AJMax0 Intrinsic,  Up: Other Intrinsics
! 
! AJMin0 Intrinsic
! ................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL AJMin0' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: ASinD Intrinsic,  Next: ATan2D Intrinsic,  Prev: AJMin0 Intrinsic,  Up: Other Intrinsics
! 
! ASinD Intrinsic
! ...............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL ASinD' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: ATan2D Intrinsic,  Next: ATanD Intrinsic,  Prev: ASinD Intrinsic,  Up: Other Intrinsics
! 
! ATan2D Intrinsic
! ................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL ATan2D' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: ATanD Intrinsic,  Next: BITest Intrinsic,  Prev: ATan2D Intrinsic,  Up: Other Intrinsics
! 
! ATanD Intrinsic
! ...............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL ATanD' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: BITest Intrinsic,  Next: BJTest Intrinsic,  Prev: ATanD Intrinsic,  Up: Other Intrinsics
! 
! BITest Intrinsic
! ................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL BITest' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: BJTest Intrinsic,  Next: CDAbs Intrinsic,  Prev: BITest Intrinsic,  Up: Other Intrinsics
! 
! BJTest Intrinsic
! ................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL BJTest' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: CDAbs Intrinsic,  Next: CDCos Intrinsic,  Prev: BJTest Intrinsic,  Up: Other Intrinsics
! 
! CDAbs Intrinsic
! ...............
! 
!      CDAbs(A)
! 
! CDAbs: `REAL(KIND=2)' function.
! 
! A: `COMPLEX(KIND=2)'; scalar; INTENT(IN).
! 
! Intrinsic groups: `f2c', `vxt'.
! 
! Description:
! 
!    Archaic form of `ABS()' that is specific to one type for A.  *Note
! Abs Intrinsic::.
! 
! 
! File: g77.info,  Node: CDCos Intrinsic,  Next: CDExp Intrinsic,  Prev: CDAbs Intrinsic,  Up: Other Intrinsics
! 
! CDCos Intrinsic
! ...............
! 
!      CDCos(X)
! 
! CDCos: `COMPLEX(KIND=2)' function.
! 
! X: `COMPLEX(KIND=2)'; scalar; INTENT(IN).
! 
! Intrinsic groups: `f2c', `vxt'.
! 
! Description:
! 
!    Archaic form of `COS()' that is specific to one type for X.  *Note
! Cos Intrinsic::.
! 
! 
! File: g77.info,  Node: CDExp Intrinsic,  Next: CDLog Intrinsic,  Prev: CDCos Intrinsic,  Up: Other Intrinsics
! 
! CDExp Intrinsic
! ...............
! 
!      CDExp(X)
! 
! CDExp: `COMPLEX(KIND=2)' function.
! 
! X: `COMPLEX(KIND=2)'; scalar; INTENT(IN).
! 
! Intrinsic groups: `f2c', `vxt'.
! 
! Description:
! 
!    Archaic form of `EXP()' that is specific to one type for X.  *Note
! Exp Intrinsic::.
! 
! 
! File: g77.info,  Node: CDLog Intrinsic,  Next: CDSin Intrinsic,  Prev: CDExp Intrinsic,  Up: Other Intrinsics
! 
! CDLog Intrinsic
! ...............
! 
!      CDLog(X)
! 
! CDLog: `COMPLEX(KIND=2)' function.
! 
! X: `COMPLEX(KIND=2)'; scalar; INTENT(IN).
! 
! Intrinsic groups: `f2c', `vxt'.
! 
! Description:
! 
!    Archaic form of `LOG()' that is specific to one type for X.  *Note
! Log Intrinsic::.
! 
! 
! File: g77.info,  Node: CDSin Intrinsic,  Next: CDSqRt Intrinsic,  Prev: CDLog Intrinsic,  Up: Other Intrinsics
! 
! CDSin Intrinsic
! ...............
! 
!      CDSin(X)
! 
! CDSin: `COMPLEX(KIND=2)' function.
! 
! X: `COMPLEX(KIND=2)'; scalar; INTENT(IN).
! 
! Intrinsic groups: `f2c', `vxt'.
! 
! Description:
! 
!    Archaic form of `SIN()' that is specific to one type for X.  *Note
! Sin Intrinsic::.
! 
! 
! File: g77.info,  Node: CDSqRt Intrinsic,  Next: ChDir Intrinsic (function),  Prev: CDSin Intrinsic,  Up: Other Intrinsics
! 
! CDSqRt Intrinsic
! ................
! 
!      CDSqRt(X)
! 
! CDSqRt: `COMPLEX(KIND=2)' function.
! 
! X: `COMPLEX(KIND=2)'; scalar; INTENT(IN).
! 
! Intrinsic groups: `f2c', `vxt'.
! 
! Description:
! 
!    Archaic form of `SQRT()' that is specific to one type for X.  *Note
! SqRt Intrinsic::.
! 
! 
! File: g77.info,  Node: ChDir Intrinsic (function),  Next: ChMod Intrinsic (function),  Prev: CDSqRt Intrinsic,  Up: Other Intrinsics
! 
! ChDir Intrinsic (function)
! ..........................
! 
!      ChDir(DIR)
! 
! ChDir: `INTEGER(KIND=1)' function.
! 
! DIR: `CHARACTER'; scalar; INTENT(IN).
! 
! Intrinsic groups: `badu77'.
! 
! Description:
! 
!    Sets the current working directory to be DIR.  Returns 0 on success
! or a nonzero error code.  See `chdir(3)'.
! 
!    _Caution:_ Using this routine during I/O to a unit connected with a
! non-absolute file name can cause subsequent I/O on such a unit to fail
! because the I/O library might reopen files by name.
! 
!    Due to the side effects performed by this intrinsic, the function
! form is not recommended.
! 
!    For information on other intrinsics with the same name: *Note ChDir
! Intrinsic (subroutine)::.
! 
! 
! File: g77.info,  Node: ChMod Intrinsic (function),  Next: CosD Intrinsic,  Prev: ChDir Intrinsic (function),  Up: Other Intrinsics
! 
! ChMod Intrinsic (function)
! ..........................
! 
!      ChMod(NAME, MODE)
! 
! ChMod: `INTEGER(KIND=1)' function.
! 
! NAME: `CHARACTER'; scalar; INTENT(IN).
! 
! MODE: `CHARACTER'; scalar; INTENT(IN).
! 
! Intrinsic groups: `badu77'.
! 
! Description:
! 
!    Changes the access mode of file NAME according to the specification
! MODE, which is given in the format of `chmod(1)'.  A null character
! (`CHAR(0)') marks the end of the name in NAME--otherwise, trailing
! blanks in NAME are ignored.  Currently, NAME must not contain the
! single quote character.
! 
!    Returns 0 on success or a nonzero error code otherwise.
! 
!    Note that this currently works by actually invoking `/bin/chmod' (or
! the `chmod' found when the library was configured) and so might fail in
! some circumstances and will, anyway, be slow.
! 
!    Due to the side effects performed by this intrinsic, the function
! form is not recommended.
! 
!    For information on other intrinsics with the same name: *Note ChMod
! Intrinsic (subroutine)::.
! 
! 
! File: g77.info,  Node: CosD Intrinsic,  Next: DACosD Intrinsic,  Prev: ChMod Intrinsic (function),  Up: Other Intrinsics
! 
! CosD Intrinsic
! ..............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL CosD' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: DACosD Intrinsic,  Next: DASinD Intrinsic,  Prev: CosD Intrinsic,  Up: Other Intrinsics
! 
! DACosD Intrinsic
! ................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL DACosD' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: DASinD Intrinsic,  Next: DATan2D Intrinsic,  Prev: DACosD Intrinsic,  Up: Other Intrinsics
! 
! DASinD Intrinsic
! ................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL DASinD' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: DATan2D Intrinsic,  Next: DATanD Intrinsic,  Prev: DASinD Intrinsic,  Up: Other Intrinsics
! 
! DATan2D Intrinsic
! .................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL DATan2D' to use this name for
! an external procedure.
! 
! 
! File: g77.info,  Node: DATanD Intrinsic,  Next: Date Intrinsic,  Prev: DATan2D Intrinsic,  Up: Other Intrinsics
! 
! DATanD Intrinsic
! ................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL DATanD' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: Date Intrinsic,  Next: DbleQ Intrinsic,  Prev: DATanD Intrinsic,  Up: Other Intrinsics
! 
! Date Intrinsic
! ..............
! 
!      CALL Date(DATE)
! 
! DATE: `CHARACTER'; scalar; INTENT(OUT).
! 
! Intrinsic groups: `vxt'.
! 
! Description:
! 
!    Returns DATE in the form `DD-MMM-YY', representing the numeric day
! of the month DD, a three-character abbreviation of the month name MMM
! and the last two digits of the year YY, e.g. `25-Nov-96'.
! 
!    This intrinsic is not recommended, due to the year 2000 approaching.
! Therefore, programs making use of this intrinsic might not be Year 2000
! (Y2K) compliant.  *Note CTime Intrinsic (subroutine)::, for information
! on obtaining more digits for the current (or any) date.
! 
! 
! File: g77.info,  Node: DbleQ Intrinsic,  Next: DCmplx Intrinsic,  Prev: Date Intrinsic,  Up: Other Intrinsics
! 
! DbleQ Intrinsic
! ...............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL DbleQ' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: DCmplx Intrinsic,  Next: DConjg Intrinsic,  Prev: DbleQ Intrinsic,  Up: Other Intrinsics
! 
! DCmplx Intrinsic
! ................
! 
!      DCmplx(X, Y)
! 
! DCmplx: `COMPLEX(KIND=2)' function.
! 
! X: `INTEGER', `REAL', or `COMPLEX'; scalar; INTENT(IN).
! 
! Y: `INTEGER' or `REAL'; OPTIONAL (must be omitted if X is `COMPLEX');
! scalar; INTENT(IN).
! 
! Intrinsic groups: `f2c', `vxt'.
! 
! Description:
! 
!    If X is not type `COMPLEX', constructs a value of type
! `COMPLEX(KIND=2)' from the real and imaginary values specified by X and
! Y, respectively.  If Y is omitted, `0D0' is assumed.
! 
!    If X is type `COMPLEX', converts it to type `COMPLEX(KIND=2)'.
! 
!    Although this intrinsic is not standard Fortran, it is a popular
! extension offered by many compilers that support `DOUBLE COMPLEX',
! since it offers the easiest way to convert to `DOUBLE COMPLEX' without
! using Fortran 90 features (such as the `KIND=' argument to the
! `CMPLX()' intrinsic).
! 
!    (`CMPLX(0D0, 0D0)' returns a single-precision `COMPLEX' result, as
! required by standard FORTRAN 77.  That's why so many compilers provide
! `DCMPLX()', since `DCMPLX(0D0, 0D0)' returns a `DOUBLE COMPLEX' result.
! Still, `DCMPLX()' converts even `REAL*16' arguments to their `REAL*8'
! equivalents in most dialects of Fortran, so neither it nor `CMPLX()'
! allow easy construction of arbitrary-precision values without
! potentially forcing a conversion involving extending or reducing
! precision.  GNU Fortran provides such an intrinsic, called `COMPLEX()'.)
! 
!    *Note Complex Intrinsic::, for information on easily constructing a
! `COMPLEX' value of arbitrary precision from `REAL' arguments.
! 
! 
! File: g77.info,  Node: DConjg Intrinsic,  Next: DCosD Intrinsic,  Prev: DCmplx Intrinsic,  Up: Other Intrinsics
! 
! DConjg Intrinsic
! ................
! 
!      DConjg(Z)
! 
! DConjg: `COMPLEX(KIND=2)' function.
! 
! Z: `COMPLEX(KIND=2)'; scalar; INTENT(IN).
! 
! Intrinsic groups: `f2c', `vxt'.
! 
! Description:
! 
!    Archaic form of `CONJG()' that is specific to one type for Z.  *Note
! Conjg Intrinsic::.
! 
! 
! File: g77.info,  Node: DCosD Intrinsic,  Next: DFloat Intrinsic,  Prev: DConjg Intrinsic,  Up: Other Intrinsics
! 
! DCosD Intrinsic
! ...............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL DCosD' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: DFloat Intrinsic,  Next: DFlotI Intrinsic,  Prev: DCosD Intrinsic,  Up: Other Intrinsics
! 
! DFloat Intrinsic
! ................
! 
!      DFloat(A)
! 
! DFloat: `REAL(KIND=2)' function.
! 
! A: `INTEGER'; scalar; INTENT(IN).
! 
! Intrinsic groups: `f2c', `vxt'.
! 
! Description:
! 
!    Archaic form of `REAL()' that is specific to one type for A.  *Note
! Real Intrinsic::.
! 
! 
! File: g77.info,  Node: DFlotI Intrinsic,  Next: DFlotJ Intrinsic,  Prev: DFloat Intrinsic,  Up: Other Intrinsics
! 
! DFlotI Intrinsic
! ................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL DFlotI' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: DFlotJ Intrinsic,  Next: DImag Intrinsic,  Prev: DFlotI Intrinsic,  Up: Other Intrinsics
! 
! DFlotJ Intrinsic
! ................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL DFlotJ' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: DImag Intrinsic,  Next: DReal Intrinsic,  Prev: DFlotJ Intrinsic,  Up: Other Intrinsics
! 
! DImag Intrinsic
! ...............
! 
!      DImag(Z)
! 
! DImag: `REAL(KIND=2)' function.
! 
! Z: `COMPLEX(KIND=2)'; scalar; INTENT(IN).
! 
! Intrinsic groups: `f2c', `vxt'.
! 
! Description:
! 
!    Archaic form of `AIMAG()' that is specific to one type for Z.  *Note
! AImag Intrinsic::.
! 
! 
! File: g77.info,  Node: DReal Intrinsic,  Next: DSinD Intrinsic,  Prev: DImag Intrinsic,  Up: Other Intrinsics
! 
! DReal Intrinsic
! ...............
! 
!      DReal(A)
! 
! DReal: `REAL(KIND=2)' function.
! 
! A: `INTEGER', `REAL', or `COMPLEX'; scalar; INTENT(IN).
! 
! Intrinsic groups: `vxt'.
! 
! Description:
! 
!    Converts A to `REAL(KIND=2)'.
! 
!    If A is type `COMPLEX', its real part is converted (if necessary) to
! `REAL(KIND=2)', and its imaginary part is disregarded.
! 
!    Although this intrinsic is not standard Fortran, it is a popular
! extension offered by many compilers that support `DOUBLE COMPLEX',
! since it offers the easiest way to extract the real part of a `DOUBLE
! COMPLEX' value without using the Fortran 90 `REAL()' intrinsic in a way
! that produces a return value inconsistent with the way many FORTRAN 77
! compilers handle `REAL()' of a `DOUBLE COMPLEX' value.
! 
!    *Note RealPart Intrinsic::, for information on a GNU Fortran
! intrinsic that avoids these areas of confusion.
! 
!    *Note Dble Intrinsic::, for information on the standard FORTRAN 77
! replacement for `DREAL()'.
! 
!    *Note REAL() and AIMAG() of Complex::, for more information on this
! issue.
! 
! 
! File: g77.info,  Node: DSinD Intrinsic,  Next: DTanD Intrinsic,  Prev: DReal Intrinsic,  Up: Other Intrinsics
! 
! DSinD Intrinsic
! ...............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL DSinD' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: DTanD Intrinsic,  Next: DTime Intrinsic (function),  Prev: DSinD Intrinsic,  Up: Other Intrinsics
! 
! DTanD Intrinsic
! ...............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL DTanD' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: DTime Intrinsic (function),  Next: FGet Intrinsic (function),  Prev: DTanD Intrinsic,  Up: Other Intrinsics
! 
! DTime Intrinsic (function)
! ..........................
! 
!      DTime(TARRAY)
! 
! DTime: `REAL(KIND=1)' function.
! 
! TARRAY: `REAL(KIND=1)'; DIMENSION(2); INTENT(OUT).
! 
! Intrinsic groups: `badu77'.
! 
! Description:
! 
!    Initially, return the number of seconds of runtime since the start
! of the process's execution as the function value, and the user and
! system components of this in `TARRAY(1)' and `TARRAY(2)' respectively.
! The functions' value is equal to `TARRAY(1) + TARRAY(2)'.
! 
!    Subsequent invocations of `DTIME()' return values accumulated since
! the previous invocation.
! 
!    On some systems, the underlying timings are represented using types
! with sufficiently small limits that overflows (wraparounds) are
! possible, such as 32-bit types.  Therefore, the values returned by this
! intrinsic might be, or become, negative, or numerically less than
! previous values, during a single run of the compiled program.
! 
!    Due to the side effects performed by this intrinsic, the function
! form is not recommended.
! 
!    For information on other intrinsics with the same name: *Note DTime
! Intrinsic (subroutine)::.
! 
! 
! File: g77.info,  Node: FGet Intrinsic (function),  Next: FGetC Intrinsic (function),  Prev: DTime Intrinsic (function),  Up: Other Intrinsics
! 
! FGet Intrinsic (function)
! .........................
! 
!      FGet(C)
! 
! FGet: `INTEGER(KIND=1)' function.
! 
! C: `CHARACTER'; scalar; INTENT(OUT).
! 
! Intrinsic groups: `badu77'.
! 
! Description:
! 
!    Reads a single character into C in stream mode from unit 5
! (by-passing normal formatted input) using `getc(3)'.  Returns 0 on
! success, -1 on end-of-file, and the error code from `ferror(3)'
! otherwise.
! 
!    Stream I/O should not be mixed with normal record-oriented
! (formatted or unformatted) I/O on the same unit; the results are
! unpredictable.
! 
!    For information on other intrinsics with the same name: *Note FGet
! Intrinsic (subroutine)::.
! 
! 
! File: g77.info,  Node: FGetC Intrinsic (function),  Next: FloatI Intrinsic,  Prev: FGet Intrinsic (function),  Up: Other Intrinsics
! 
! FGetC Intrinsic (function)
! ..........................
! 
!      FGetC(UNIT, C)
! 
! FGetC: `INTEGER(KIND=1)' function.
! 
! UNIT: `INTEGER'; scalar; INTENT(IN).
! 
! C: `CHARACTER'; scalar; INTENT(OUT).
! 
! Intrinsic groups: `badu77'.
! 
! Description:
! 
!    Reads a single character into C in stream mode from unit UNIT
! (by-passing normal formatted output) using `getc(3)'.  Returns 0 on
! success, -1 on end-of-file, and the error code from `ferror(3)'
! otherwise.
! 
!    Stream I/O should not be mixed with normal record-oriented
! (formatted or unformatted) I/O on the same unit; the results are
! unpredictable.
! 
!    For information on other intrinsics with the same name: *Note FGetC
! Intrinsic (subroutine)::.
! 
! 
! File: g77.info,  Node: FloatI Intrinsic,  Next: FloatJ Intrinsic,  Prev: FGetC Intrinsic (function),  Up: Other Intrinsics
! 
! FloatI Intrinsic
! ................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL FloatI' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: FloatJ Intrinsic,  Next: FPut Intrinsic (function),  Prev: FloatI Intrinsic,  Up: Other Intrinsics
! 
! FloatJ Intrinsic
! ................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL FloatJ' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: FPut Intrinsic (function),  Next: FPutC Intrinsic (function),  Prev: FloatJ Intrinsic,  Up: Other Intrinsics
! 
! FPut Intrinsic (function)
! .........................
! 
!      FPut(C)
! 
! FPut: `INTEGER(KIND=1)' function.
! 
! C: `CHARACTER'; scalar; INTENT(IN).
! 
! Intrinsic groups: `badu77'.
! 
! Description:
! 
!    Writes the single character C in stream mode to unit 6 (by-passing
! normal formatted output) using `getc(3)'.  Returns 0 on success, the
! error code from `ferror(3)' otherwise.
! 
!    Stream I/O should not be mixed with normal record-oriented
! (formatted or unformatted) I/O on the same unit; the results are
! unpredictable.
! 
!    For information on other intrinsics with the same name: *Note FPut
! Intrinsic (subroutine)::.
! 
! 
! File: g77.info,  Node: FPutC Intrinsic (function),  Next: IDate Intrinsic (VXT),  Prev: FPut Intrinsic (function),  Up: Other Intrinsics
! 
! FPutC Intrinsic (function)
! ..........................
! 
!      FPutC(UNIT, C)
! 
! FPutC: `INTEGER(KIND=1)' function.
! 
! UNIT: `INTEGER'; scalar; INTENT(IN).
! 
! C: `CHARACTER'; scalar; INTENT(IN).
! 
! Intrinsic groups: `badu77'.
! 
! Description:
! 
!    Writes the single character C in stream mode to unit UNIT
! (by-passing normal formatted output) using `putc(3)'.  Returns 0 on
! success, the error code from `ferror(3)' otherwise.
! 
!    Stream I/O should not be mixed with normal record-oriented
! (formatted or unformatted) I/O on the same unit; the results are
! unpredictable.
! 
!    For information on other intrinsics with the same name: *Note FPutC
! Intrinsic (subroutine)::.
! 
! 
! File: g77.info,  Node: IDate Intrinsic (VXT),  Next: IIAbs Intrinsic,  Prev: FPutC Intrinsic (function),  Up: Other Intrinsics
! 
! IDate Intrinsic (VXT)
! .....................
! 
!      CALL IDate(M, D, Y)
! 
! M: `INTEGER(KIND=1)'; scalar; INTENT(OUT).
! 
! D: `INTEGER(KIND=1)'; scalar; INTENT(OUT).
! 
! Y: `INTEGER(KIND=1)'; scalar; INTENT(OUT).
! 
! Intrinsic groups: `vxt'.
! 
! Description:
! 
!    Returns the numerical values of the current local time.  The month
! (in the range 1-12) is returned in M, the day (in the range 1-7) in D,
! and the year in Y (in the range 0-99).
! 
!    This intrinsic is not recommended, due to the year 2000 approaching.
! Therefore, programs making use of this intrinsic might not be Year 2000
! (Y2K) compliant.  For example, the date might appear, to such programs,
! to wrap around (change from a larger value to a smaller one) as of the
! Year 2000.
! 
!    *Note IDate Intrinsic (UNIX)::, for information on obtaining more
! digits for the current date.
! 
!    For information on other intrinsics with the same name: *Note IDate
! Intrinsic (UNIX)::.
! 
! 
! File: g77.info,  Node: IIAbs Intrinsic,  Next: IIAnd Intrinsic,  Prev: IDate Intrinsic (VXT),  Up: Other Intrinsics
! 
! IIAbs Intrinsic
! ...............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL IIAbs' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: IIAnd Intrinsic,  Next: IIBClr Intrinsic,  Prev: IIAbs Intrinsic,  Up: Other Intrinsics
! 
! IIAnd Intrinsic
! ...............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL IIAnd' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: IIBClr Intrinsic,  Next: IIBits Intrinsic,  Prev: IIAnd Intrinsic,  Up: Other Intrinsics
! 
! IIBClr Intrinsic
! ................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL IIBClr' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: IIBits Intrinsic,  Next: IIBSet Intrinsic,  Prev: IIBClr Intrinsic,  Up: Other Intrinsics
! 
! IIBits Intrinsic
! ................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL IIBits' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: IIBSet Intrinsic,  Next: IIDiM Intrinsic,  Prev: IIBits Intrinsic,  Up: Other Intrinsics
! 
! IIBSet Intrinsic
! ................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL IIBSet' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: IIDiM Intrinsic,  Next: IIDInt Intrinsic,  Prev: IIBSet Intrinsic,  Up: Other Intrinsics
! 
! IIDiM Intrinsic
! ...............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL IIDiM' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: IIDInt Intrinsic,  Next: IIDNnt Intrinsic,  Prev: IIDiM Intrinsic,  Up: Other Intrinsics
! 
! IIDInt Intrinsic
! ................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL IIDInt' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: IIDNnt Intrinsic,  Next: IIEOr Intrinsic,  Prev: IIDInt Intrinsic,  Up: Other Intrinsics
! 
! IIDNnt Intrinsic
! ................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL IIDNnt' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: IIEOr Intrinsic,  Next: IIFix Intrinsic,  Prev: IIDNnt Intrinsic,  Up: Other Intrinsics
! 
! IIEOr Intrinsic
! ...............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL IIEOr' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: IIFix Intrinsic,  Next: IInt Intrinsic,  Prev: IIEOr Intrinsic,  Up: Other Intrinsics
! 
! IIFix Intrinsic
! ...............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL IIFix' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: IInt Intrinsic,  Next: IIOr Intrinsic,  Prev: IIFix Intrinsic,  Up: Other Intrinsics
! 
! IInt Intrinsic
! ..............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL IInt' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: IIOr Intrinsic,  Next: IIQint Intrinsic,  Prev: IInt Intrinsic,  Up: Other Intrinsics
! 
! IIOr Intrinsic
! ..............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL IIOr' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: IIQint Intrinsic,  Next: IIQNnt Intrinsic,  Prev: IIOr Intrinsic,  Up: Other Intrinsics
! 
! IIQint Intrinsic
! ................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL IIQint' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: IIQNnt Intrinsic,  Next: IIShftC Intrinsic,  Prev: IIQint Intrinsic,  Up: Other Intrinsics
! 
! IIQNnt Intrinsic
! ................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL IIQNnt' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: IIShftC Intrinsic,  Next: IISign Intrinsic,  Prev: IIQNnt Intrinsic,  Up: Other Intrinsics
! 
! IIShftC Intrinsic
! .................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL IIShftC' to use this name for
! an external procedure.
! 
! 
! File: g77.info,  Node: IISign Intrinsic,  Next: IMax0 Intrinsic,  Prev: IIShftC Intrinsic,  Up: Other Intrinsics
! 
! IISign Intrinsic
! ................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL IISign' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: IMax0 Intrinsic,  Next: IMax1 Intrinsic,  Prev: IISign Intrinsic,  Up: Other Intrinsics
! 
! IMax0 Intrinsic
! ...............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL IMax0' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: IMax1 Intrinsic,  Next: IMin0 Intrinsic,  Prev: IMax0 Intrinsic,  Up: Other Intrinsics
! 
! IMax1 Intrinsic
! ...............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL IMax1' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: IMin0 Intrinsic,  Next: IMin1 Intrinsic,  Prev: IMax1 Intrinsic,  Up: Other Intrinsics
! 
! IMin0 Intrinsic
! ...............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL IMin0' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: IMin1 Intrinsic,  Next: IMod Intrinsic,  Prev: IMin0 Intrinsic,  Up: Other Intrinsics
! 
! IMin1 Intrinsic
! ...............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL IMin1' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: IMod Intrinsic,  Next: INInt Intrinsic,  Prev: IMin1 Intrinsic,  Up: Other Intrinsics
! 
! IMod Intrinsic
! ..............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL IMod' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: INInt Intrinsic,  Next: INot Intrinsic,  Prev: IMod Intrinsic,  Up: Other Intrinsics
! 
! INInt Intrinsic
! ...............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL INInt' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: INot Intrinsic,  Next: IZExt Intrinsic,  Prev: INInt Intrinsic,  Up: Other Intrinsics
! 
! INot Intrinsic
! ..............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL INot' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: IZExt Intrinsic,  Next: JIAbs Intrinsic,  Prev: INot Intrinsic,  Up: Other Intrinsics
! 
! IZExt Intrinsic
! ...............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL IZExt' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: JIAbs Intrinsic,  Next: JIAnd Intrinsic,  Prev: IZExt Intrinsic,  Up: Other Intrinsics
! 
! JIAbs Intrinsic
! ...............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL JIAbs' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: JIAnd Intrinsic,  Next: JIBClr Intrinsic,  Prev: JIAbs Intrinsic,  Up: Other Intrinsics
! 
! JIAnd Intrinsic
! ...............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL JIAnd' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: JIBClr Intrinsic,  Next: JIBits Intrinsic,  Prev: JIAnd Intrinsic,  Up: Other Intrinsics
! 
! JIBClr Intrinsic
! ................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL JIBClr' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: JIBits Intrinsic,  Next: JIBSet Intrinsic,  Prev: JIBClr Intrinsic,  Up: Other Intrinsics
! 
! JIBits Intrinsic
! ................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL JIBits' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: JIBSet Intrinsic,  Next: JIDiM Intrinsic,  Prev: JIBits Intrinsic,  Up: Other Intrinsics
! 
! JIBSet Intrinsic
! ................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL JIBSet' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: JIDiM Intrinsic,  Next: JIDInt Intrinsic,  Prev: JIBSet Intrinsic,  Up: Other Intrinsics
! 
! JIDiM Intrinsic
! ...............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL JIDiM' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: JIDInt Intrinsic,  Next: JIDNnt Intrinsic,  Prev: JIDiM Intrinsic,  Up: Other Intrinsics
! 
! JIDInt Intrinsic
! ................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL JIDInt' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: JIDNnt Intrinsic,  Next: JIEOr Intrinsic,  Prev: JIDInt Intrinsic,  Up: Other Intrinsics
! 
! JIDNnt Intrinsic
! ................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL JIDNnt' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: JIEOr Intrinsic,  Next: JIFix Intrinsic,  Prev: JIDNnt Intrinsic,  Up: Other Intrinsics
! 
! JIEOr Intrinsic
! ...............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL JIEOr' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: JIFix Intrinsic,  Next: JInt Intrinsic,  Prev: JIEOr Intrinsic,  Up: Other Intrinsics
! 
! JIFix Intrinsic
! ...............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL JIFix' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: JInt Intrinsic,  Next: JIOr Intrinsic,  Prev: JIFix Intrinsic,  Up: Other Intrinsics
! 
! JInt Intrinsic
! ..............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL JInt' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: JIOr Intrinsic,  Next: JIQint Intrinsic,  Prev: JInt Intrinsic,  Up: Other Intrinsics
! 
! JIOr Intrinsic
! ..............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL JIOr' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: JIQint Intrinsic,  Next: JIQNnt Intrinsic,  Prev: JIOr Intrinsic,  Up: Other Intrinsics
! 
! JIQint Intrinsic
! ................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL JIQint' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: JIQNnt Intrinsic,  Next: JIShft Intrinsic,  Prev: JIQint Intrinsic,  Up: Other Intrinsics
! 
! JIQNnt Intrinsic
! ................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL JIQNnt' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: JIShft Intrinsic,  Next: JIShftC Intrinsic,  Prev: JIQNnt Intrinsic,  Up: Other Intrinsics
! 
! JIShft Intrinsic
! ................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL JIShft' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: JIShftC Intrinsic,  Next: JISign Intrinsic,  Prev: JIShft Intrinsic,  Up: Other Intrinsics
! 
! JIShftC Intrinsic
! .................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL JIShftC' to use this name for
! an external procedure.
! 
! 
! File: g77.info,  Node: JISign Intrinsic,  Next: JMax0 Intrinsic,  Prev: JIShftC Intrinsic,  Up: Other Intrinsics
! 
! JISign Intrinsic
! ................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL JISign' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: JMax0 Intrinsic,  Next: JMax1 Intrinsic,  Prev: JISign Intrinsic,  Up: Other Intrinsics
! 
! JMax0 Intrinsic
! ...............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL JMax0' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: JMax1 Intrinsic,  Next: JMin0 Intrinsic,  Prev: JMax0 Intrinsic,  Up: Other Intrinsics
! 
! JMax1 Intrinsic
! ...............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL JMax1' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: JMin0 Intrinsic,  Next: JMin1 Intrinsic,  Prev: JMax1 Intrinsic,  Up: Other Intrinsics
! 
! JMin0 Intrinsic
! ...............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL JMin0' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: JMin1 Intrinsic,  Next: JMod Intrinsic,  Prev: JMin0 Intrinsic,  Up: Other Intrinsics
! 
! JMin1 Intrinsic
! ...............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL JMin1' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: JMod Intrinsic,  Next: JNInt Intrinsic,  Prev: JMin1 Intrinsic,  Up: Other Intrinsics
! 
! JMod Intrinsic
! ..............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL JMod' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: JNInt Intrinsic,  Next: JNot Intrinsic,  Prev: JMod Intrinsic,  Up: Other Intrinsics
! 
! JNInt Intrinsic
! ...............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL JNInt' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: JNot Intrinsic,  Next: JZExt Intrinsic,  Prev: JNInt Intrinsic,  Up: Other Intrinsics
! 
! JNot Intrinsic
! ..............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL JNot' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: JZExt Intrinsic,  Next: Kill Intrinsic (function),  Prev: JNot Intrinsic,  Up: Other Intrinsics
! 
! JZExt Intrinsic
! ...............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL JZExt' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: Kill Intrinsic (function),  Next: Link Intrinsic (function),  Prev: JZExt Intrinsic,  Up: Other Intrinsics
! 
! Kill Intrinsic (function)
! .........................
! 
!      Kill(PID, SIGNAL)
! 
! Kill: `INTEGER(KIND=1)' function.
! 
! PID: `INTEGER'; scalar; INTENT(IN).
! 
! SIGNAL: `INTEGER'; scalar; INTENT(IN).
! 
! Intrinsic groups: `badu77'.
! 
! Description:
! 
!    Sends the signal specified by SIGNAL to the process PID.  Returns 0
! on success or a nonzero error code.  See `kill(2)'.
! 
!    Due to the side effects performed by this intrinsic, the function
! form is not recommended.
! 
!    For information on other intrinsics with the same name: *Note Kill
! Intrinsic (subroutine)::.
! 
! 
! File: g77.info,  Node: Link Intrinsic (function),  Next: QAbs Intrinsic,  Prev: Kill Intrinsic (function),  Up: Other Intrinsics
! 
! Link Intrinsic (function)
! .........................
! 
!      Link(PATH1, PATH2)
! 
! Link: `INTEGER(KIND=1)' function.
! 
! PATH1: `CHARACTER'; scalar; INTENT(IN).
! 
! PATH2: `CHARACTER'; scalar; INTENT(IN).
! 
! Intrinsic groups: `badu77'.
! 
! Description:
! 
!    Makes a (hard) link from file PATH1 to PATH2.  A null character
! (`CHAR(0)') marks the end of the names in PATH1 and PATH2--otherwise,
! trailing blanks in PATH1 and PATH2 are ignored.  Returns 0 on success
! or a nonzero error code.  See `link(2)'.
! 
!    Due to the side effects performed by this intrinsic, the function
! form is not recommended.
! 
!    For information on other intrinsics with the same name: *Note Link
! Intrinsic (subroutine)::.
! 
! 
! File: g77.info,  Node: QAbs Intrinsic,  Next: QACos Intrinsic,  Prev: Link Intrinsic (function),  Up: Other Intrinsics
! 
! QAbs Intrinsic
! ..............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL QAbs' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: QACos Intrinsic,  Next: QACosD Intrinsic,  Prev: QAbs Intrinsic,  Up: Other Intrinsics
! 
! QACos Intrinsic
! ...............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL QACos' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: QACosD Intrinsic,  Next: QASin Intrinsic,  Prev: QACos Intrinsic,  Up: Other Intrinsics
! 
! QACosD Intrinsic
! ................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL QACosD' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: QASin Intrinsic,  Next: QASinD Intrinsic,  Prev: QACosD Intrinsic,  Up: Other Intrinsics
! 
! QASin Intrinsic
! ...............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL QASin' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: QASinD Intrinsic,  Next: QATan Intrinsic,  Prev: QASin Intrinsic,  Up: Other Intrinsics
! 
! QASinD Intrinsic
! ................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL QASinD' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: QATan Intrinsic,  Next: QATan2 Intrinsic,  Prev: QASinD Intrinsic,  Up: Other Intrinsics
! 
! QATan Intrinsic
! ...............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL QATan' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: QATan2 Intrinsic,  Next: QATan2D Intrinsic,  Prev: QATan Intrinsic,  Up: Other Intrinsics
! 
! QATan2 Intrinsic
! ................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL QATan2' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: QATan2D Intrinsic,  Next: QATanD Intrinsic,  Prev: QATan2 Intrinsic,  Up: Other Intrinsics
! 
! QATan2D Intrinsic
! .................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL QATan2D' to use this name for
! an external procedure.
! 
! 
! File: g77.info,  Node: QATanD Intrinsic,  Next: QCos Intrinsic,  Prev: QATan2D Intrinsic,  Up: Other Intrinsics
! 
! QATanD Intrinsic
! ................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL QATanD' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: QCos Intrinsic,  Next: QCosD Intrinsic,  Prev: QATanD Intrinsic,  Up: Other Intrinsics
! 
! QCos Intrinsic
! ..............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL QCos' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: QCosD Intrinsic,  Next: QCosH Intrinsic,  Prev: QCos Intrinsic,  Up: Other Intrinsics
! 
! QCosD Intrinsic
! ...............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL QCosD' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: QCosH Intrinsic,  Next: QDiM Intrinsic,  Prev: QCosD Intrinsic,  Up: Other Intrinsics
! 
! QCosH Intrinsic
! ...............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL QCosH' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: QDiM Intrinsic,  Next: QExp Intrinsic,  Prev: QCosH Intrinsic,  Up: Other Intrinsics
! 
! QDiM Intrinsic
! ..............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL QDiM' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: QExp Intrinsic,  Next: QExt Intrinsic,  Prev: QDiM Intrinsic,  Up: Other Intrinsics
! 
! QExp Intrinsic
! ..............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL QExp' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: QExt Intrinsic,  Next: QExtD Intrinsic,  Prev: QExp Intrinsic,  Up: Other Intrinsics
! 
! QExt Intrinsic
! ..............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL QExt' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: QExtD Intrinsic,  Next: QFloat Intrinsic,  Prev: QExt Intrinsic,  Up: Other Intrinsics
! 
! QExtD Intrinsic
! ...............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL QExtD' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: QFloat Intrinsic,  Next: QInt Intrinsic,  Prev: QExtD Intrinsic,  Up: Other Intrinsics
! 
! QFloat Intrinsic
! ................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL QFloat' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: QInt Intrinsic,  Next: QLog Intrinsic,  Prev: QFloat Intrinsic,  Up: Other Intrinsics
! 
! QInt Intrinsic
! ..............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL QInt' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: QLog Intrinsic,  Next: QLog10 Intrinsic,  Prev: QInt Intrinsic,  Up: Other Intrinsics
! 
! QLog Intrinsic
! ..............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL QLog' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: QLog10 Intrinsic,  Next: QMax1 Intrinsic,  Prev: QLog Intrinsic,  Up: Other Intrinsics
! 
! QLog10 Intrinsic
! ................
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL QLog10' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: QMax1 Intrinsic,  Next: QMin1 Intrinsic,  Prev: QLog10 Intrinsic,  Up: Other Intrinsics
! 
! QMax1 Intrinsic
! ...............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL QMax1' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: QMin1 Intrinsic,  Next: QMod Intrinsic,  Prev: QMax1 Intrinsic,  Up: Other Intrinsics
! 
! QMin1 Intrinsic
! ...............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL QMin1' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: QMod Intrinsic,  Next: QNInt Intrinsic,  Prev: QMin1 Intrinsic,  Up: Other Intrinsics
! 
! QMod Intrinsic
! ..............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL QMod' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: QNInt Intrinsic,  Next: QSin Intrinsic,  Prev: QMod Intrinsic,  Up: Other Intrinsics
! 
! QNInt Intrinsic
! ...............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL QNInt' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: QSin Intrinsic,  Next: QSinD Intrinsic,  Prev: QNInt Intrinsic,  Up: Other Intrinsics
! 
! QSin Intrinsic
! ..............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL QSin' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: QSinD Intrinsic,  Next: QSinH Intrinsic,  Prev: QSin Intrinsic,  Up: Other Intrinsics
! 
! QSinD Intrinsic
! ...............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL QSinD' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: QSinH Intrinsic,  Next: QSqRt Intrinsic,  Prev: QSinD Intrinsic,  Up: Other Intrinsics
! 
! QSinH Intrinsic
! ...............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL QSinH' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: QSqRt Intrinsic,  Next: QTan Intrinsic,  Prev: QSinH Intrinsic,  Up: Other Intrinsics
! 
! QSqRt Intrinsic
! ...............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL QSqRt' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: QTan Intrinsic,  Next: QTanD Intrinsic,  Prev: QSqRt Intrinsic,  Up: Other Intrinsics
! 
! QTan Intrinsic
! ..............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL QTan' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: QTanD Intrinsic,  Next: QTanH Intrinsic,  Prev: QTan Intrinsic,  Up: Other Intrinsics
! 
! QTanD Intrinsic
! ...............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL QTanD' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: QTanH Intrinsic,  Next: Rename Intrinsic (function),  Prev: QTanD Intrinsic,  Up: Other Intrinsics
! 
! QTanH Intrinsic
! ...............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL QTanH' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: Rename Intrinsic (function),  Next: Secnds Intrinsic,  Prev: QTanH Intrinsic,  Up: Other Intrinsics
! 
! Rename Intrinsic (function)
! ...........................
! 
!      Rename(PATH1, PATH2)
! 
! Rename: `INTEGER(KIND=1)' function.
! 
! PATH1: `CHARACTER'; scalar; INTENT(IN).
! 
! PATH2: `CHARACTER'; scalar; INTENT(IN).
! 
! Intrinsic groups: `badu77'.
! 
! Description:
! 
!    Renames the file PATH1 to PATH2.  A null character (`CHAR(0)') marks
! the end of the names in PATH1 and PATH2--otherwise, trailing blanks in
! PATH1 and PATH2 are ignored.  See `rename(2)'.  Returns 0 on success or
! a nonzero error code.
! 
!    Due to the side effects performed by this intrinsic, the function
! form is not recommended.
! 
!    For information on other intrinsics with the same name: *Note Rename
! Intrinsic (subroutine)::.
! 
! 
! File: g77.info,  Node: Secnds Intrinsic,  Next: Signal Intrinsic (function),  Prev: Rename Intrinsic (function),  Up: Other Intrinsics
! 
! Secnds Intrinsic
! ................
! 
!      Secnds(T)
! 
! Secnds: `REAL(KIND=1)' function.
! 
! T: `REAL(KIND=1)'; scalar; INTENT(IN).
! 
! Intrinsic groups: `vxt'.
! 
! Description:
! 
!    Returns the local time in seconds since midnight minus the value T.
! 
!    This values returned by this intrinsic become numerically less than
! previous values (they wrap around) during a single run of the compiler
! program, under normal circumstances (such as running through the
! midnight hour).
! 
! 
! File: g77.info,  Node: Signal Intrinsic (function),  Next: SinD Intrinsic,  Prev: Secnds Intrinsic,  Up: Other Intrinsics
! 
! Signal Intrinsic (function)
! ...........................
! 
!      Signal(NUMBER, HANDLER)
! 
! Signal: `INTEGER(KIND=7)' function.
! 
! NUMBER: `INTEGER'; scalar; INTENT(IN).
! 
! HANDLER: Signal handler (`INTEGER FUNCTION' or `SUBROUTINE') or
! dummy/global `INTEGER(KIND=1)' scalar.
! 
! Intrinsic groups: `badu77'.
! 
! Description:
! 
!    If HANDLER is a an `EXTERNAL' routine, arranges for it to be invoked
! with a single integer argument (of system-dependent length) when signal
! NUMBER occurs.  If HANDLER is an integer, it can be used to turn off
! handling of signal NUMBER or revert to its default action.  See
! `signal(2)'.
! 
!    Note that HANDLER will be called using C conventions, so the value
! of its argument in Fortran terms is obtained by applying `%LOC()' (or
! LOC()) to it.
! 
!    The value returned by `signal(2)' is returned.
! 
!    Due to the side effects performed by this intrinsic, the function
! form is not recommended.
! 
!    _Warning:_ If the returned value is stored in an `INTEGER(KIND=1)'
! (default `INTEGER') argument, truncation of the original return value
! occurs on some systems (such as Alphas, which have 64-bit pointers but
! 32-bit default integers), with no warning issued by `g77' under normal
! circumstances.
! 
!    Therefore, the following code fragment might silently fail on some
! systems:
! 
!      INTEGER RTN
!      EXTERNAL MYHNDL
!      RTN = SIGNAL(SIGNUM, MYHNDL)
!      ...
!      ! Restore original handler:
!      RTN = SIGNAL(SIGNUM, RTN)
! 
!    The reason for the failure is that `RTN' might not hold all the
! information on the original handler for the signal, thus restoring an
! invalid handler.  This bug could manifest itself as a spurious run-time
! failure at an arbitrary point later during the program's execution, for
! example.
! 
!    _Warning:_ Use of the `libf2c' run-time library function `signal_'
! directly (such as via `EXTERNAL SIGNAL') requires use of the `%VAL()'
! construct to pass an `INTEGER' value (such as `SIG_IGN' or `SIG_DFL')
! for the HANDLER argument.
! 
!    However, while `RTN = SIGNAL(SIGNUM, %VAL(SIG_IGN))' works when
! `SIGNAL' is treated as an external procedure (and resolves, at link
! time, to `libf2c''s `signal_' routine), this construct is not valid
! when `SIGNAL' is recognized as the intrinsic of that name.
! 
!    Therefore, for maximum portability and reliability, code such
! references to the `SIGNAL' facility as follows:
! 
!      INTRINSIC SIGNAL
!      ...
!      RTN = SIGNAL(SIGNUM, SIG_IGN)
! 
!    `g77' will compile such a call correctly, while other compilers will
! generally either do so as well or reject the `INTRINSIC SIGNAL'
! statement via a diagnostic, allowing you to take appropriate action.
! 
!    For information on other intrinsics with the same name: *Note Signal
! Intrinsic (subroutine)::.
! 
! 
! File: g77.info,  Node: SinD Intrinsic,  Next: SnglQ Intrinsic,  Prev: Signal Intrinsic (function),  Up: Other Intrinsics
! 
! SinD Intrinsic
! ..............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL SinD' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: SnglQ Intrinsic,  Next: SymLnk Intrinsic (function),  Prev: SinD Intrinsic,  Up: Other Intrinsics
! 
! SnglQ Intrinsic
! ...............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL SnglQ' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: SymLnk Intrinsic (function),  Next: System Intrinsic (function),  Prev: SnglQ Intrinsic,  Up: Other Intrinsics
! 
! SymLnk Intrinsic (function)
! ...........................
! 
!      SymLnk(PATH1, PATH2)
! 
! SymLnk: `INTEGER(KIND=1)' function.
! 
! PATH1: `CHARACTER'; scalar; INTENT(IN).
! 
! PATH2: `CHARACTER'; scalar; INTENT(IN).
! 
! Intrinsic groups: `badu77'.
! 
! Description:
! 
!    Makes a symbolic link from file PATH1 to PATH2.  A null character
! (`CHAR(0)') marks the end of the names in PATH1 and PATH2--otherwise,
! trailing blanks in PATH1 and PATH2 are ignored.  Returns 0 on success
! or a nonzero error code (`ENOSYS' if the system does not provide
! `symlink(2)').
! 
!    Due to the side effects performed by this intrinsic, the function
! form is not recommended.
! 
!    For information on other intrinsics with the same name: *Note SymLnk
! Intrinsic (subroutine)::.
! 
! 
! File: g77.info,  Node: System Intrinsic (function),  Next: TanD Intrinsic,  Prev: SymLnk Intrinsic (function),  Up: Other Intrinsics
! 
! System Intrinsic (function)
! ...........................
! 
!      System(COMMAND)
! 
! System: `INTEGER(KIND=1)' function.
! 
! COMMAND: `CHARACTER'; scalar; INTENT(IN).
! 
! Intrinsic groups: `badu77'.
! 
! Description:
! 
!    Passes the command COMMAND to a shell (see `system(3)').  Returns
! the value returned by `system(3)', presumably 0 if the shell command
! succeeded.  Note that which shell is used to invoke the command is
! system-dependent and environment-dependent.
! 
!    Due to the side effects performed by this intrinsic, the function
! form is not recommended.  However, the function form can be valid in
! cases where the actual side effects performed by the call are
! unimportant to the application.
! 
!    For example, on a UNIX system, `SAME = SYSTEM('cmp a b')' does not
! perform any side effects likely to be important to the program, so the
! programmer would not care if the actual system call (and invocation of
! `cmp') was optimized away in a situation where the return value could
! be determined otherwise, or was not actually needed (`SAME' not
! actually referenced after the sample assignment statement).
! 
!    For information on other intrinsics with the same name: *Note System
! Intrinsic (subroutine)::.
! 
! 
! File: g77.info,  Node: TanD Intrinsic,  Next: Time Intrinsic (VXT),  Prev: System Intrinsic (function),  Up: Other Intrinsics
! 
! TanD Intrinsic
! ..............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL TanD' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: Time Intrinsic (VXT),  Next: UMask Intrinsic (function),  Prev: TanD Intrinsic,  Up: Other Intrinsics
! 
! Time Intrinsic (VXT)
! ....................
! 
!      CALL Time(TIME)
! 
! TIME: `CHARACTER*8'; scalar; INTENT(OUT).
! 
! Intrinsic groups: `vxt'.
! 
! Description:
! 
!    Returns in TIME a character representation of the current time as
! obtained from `ctime(3)'.
! 
!    Programs making use of this intrinsic might not be Year 10000 (Y10K)
! compliant.  For example, the date might appear, to such programs, to
! wrap around (change from a larger value to a smaller one) as of the
! Year 10000.
! 
!    *Note FDate Intrinsic (subroutine)::, for an equivalent routine.
! 
!    For information on other intrinsics with the same name: *Note Time
! Intrinsic (UNIX)::.
! 
! 
! File: g77.info,  Node: UMask Intrinsic (function),  Next: Unlink Intrinsic (function),  Prev: Time Intrinsic (VXT),  Up: Other Intrinsics
! 
! UMask Intrinsic (function)
! ..........................
! 
!      UMask(MASK)
! 
! UMask: `INTEGER(KIND=1)' function.
! 
! MASK: `INTEGER'; scalar; INTENT(IN).
! 
! Intrinsic groups: `badu77'.
! 
! Description:
! 
!    Sets the file creation mask to MASK and returns the old value.  See
! `umask(2)'.
! 
!    Due to the side effects performed by this intrinsic, the function
! form is not recommended.
! 
!    For information on other intrinsics with the same name: *Note UMask
! Intrinsic (subroutine)::.
! 
! 
! File: g77.info,  Node: Unlink Intrinsic (function),  Next: ZExt Intrinsic,  Prev: UMask Intrinsic (function),  Up: Other Intrinsics
! 
! Unlink Intrinsic (function)
! ...........................
! 
!      Unlink(FILE)
! 
! Unlink: `INTEGER(KIND=1)' function.
! 
! FILE: `CHARACTER'; scalar; INTENT(IN).
! 
! Intrinsic groups: `badu77'.
! 
! Description:
! 
!    Unlink the file FILE.  A null character (`CHAR(0)') marks the end of
! the name in FILE--otherwise, trailing blanks in FILE are ignored.
! Returns 0 on success or a nonzero error code.  See `unlink(2)'.
! 
!    Due to the side effects performed by this intrinsic, the function
! form is not recommended.
! 
!    For information on other intrinsics with the same name: *Note Unlink
! Intrinsic (subroutine)::.
! 
! 
! File: g77.info,  Node: ZExt Intrinsic,  Prev: Unlink Intrinsic (function),  Up: Other Intrinsics
! 
! ZExt Intrinsic
! ..............
! 
!    This intrinsic is not yet implemented.  The name is, however,
! reserved as an intrinsic.  Use `EXTERNAL ZExt' to use this name for an
! external procedure.
! 
! 
! File: g77.info,  Node: Other Compilers,  Next: Other Languages,  Prev: Other Dialects,  Up: Top
! 
! Other Compilers
! ***************
! 
!    An individual Fortran source file can be compiled to an object
! (`*.o') file instead of to the final program executable.  This allows
! several portions of a program to be compiled at different times and
! linked together whenever a new version of the program is needed.
! However, it introduces the issue of "object compatibility" across the
! various object files (and libraries, or `*.a' files) that are linked
! together to produce any particular executable file.
! 
!    Object compatibility is an issue when combining, in one program,
! Fortran code compiled by more than one compiler (or more than one
! configuration of a compiler).  If the compilers disagree on how to
! transform the names of procedures, there will normally be errors when
! linking such programs.  Worse, if the compilers agree on naming, but
! disagree on issues like how to pass parameters, return arguments, and
! lay out `COMMON' areas, the earliest detected errors might be the
! incorrect results produced by the program (and that assumes these
! errors are detected, which is not always the case).
! 
!    Normally, `g77' generates code that is object-compatible with code
! generated by a version of `f2c' configured (with, for example, `f2c.h'
! definitions) to be generally compatible with `g77' as built by `gcc'.
! (Normally, `f2c' will, by default, conform to the appropriate
! configuration, but it is possible that older or perhaps even newer
! versions of `f2c', or versions having certain configuration changes to
! `f2c' internals, will produce object files that are incompatible with
! `g77'.)
! 
!    For example, a Fortran string subroutine argument will become two
! arguments on the C side: a `char *' and an `int' length.
! 
!    Much of this compatibility results from the fact that `g77' uses the
! same run-time library, `libf2c', used by `f2c', though `g77' gives its
! version the name `libg2c' so as to avoid conflicts when linking,
! installing them in the same directories, and so on.
! 
!    Other compilers might or might not generate code that is
! object-compatible with `libg2c' and current `g77', and some might offer
! such compatibility only when explicitly selected via a command-line
! option to the compiler.
! 
!    _Note: This portion of the documentation definitely needs a lot of
! work!_
! 
! * Menu:
! 
! * Dropping f2c Compatibility::  When speed is more important.
! * Compilers Other Than f2c::    Interoperation with code from other compilers.
! 
! 
! File: g77.info,  Node: Dropping f2c Compatibility,  Next: Compilers Other Than f2c,  Up: Other Compilers
! 
! Dropping `f2c' Compatibility
! ============================
! 
!    Specifying `-fno-f2c' allows `g77' to generate, in some cases,
! faster code, by not needing to allow to the possibility of linking with
! code compiled by `f2c'.
! 
!    For example, this affects how `REAL(KIND=1)', `COMPLEX(KIND=1)', and
! `COMPLEX(KIND=2)' functions are called.  With `-fno-f2c', they are
! compiled as returning the appropriate `gcc' type (`float', `__complex__
! float', `__complex__ double', in many configurations).
! 
!    With `-ff2c' in force, they are compiled differently (with perhaps
! slower run-time performance) to accommodate the restrictions inherent
! in `f2c''s use of K&R C as an intermediate language--`REAL(KIND=1)'
! functions return C's `double' type, while `COMPLEX' functions return
! `void' and use an extra argument pointing to a place for the functions
! to return their values.
! 
!    It is possible that, in some cases, leaving `-ff2c' in force might
! produce faster code than using `-fno-f2c'.  Feel free to experiment,
! but remember to experiment with changing the way _entire programs and
! their Fortran libraries are compiled_ at a time, since this sort of
! experimentation affects the interface of code generated for a Fortran
! source file--that is, it affects object compatibility.
! 
!    Note that `f2c' compatibility is a fairly static target to achieve,
! though not necessarily perfectly so, since, like `g77', it is still
! being improved.  However, specifying `-fno-f2c' causes `g77' to
! generate code that will probably be incompatible with code generated by
! future versions of `g77' when the same option is in force.  You should
! make sure you are always able to recompile complete programs from
! source code when upgrading to new versions of `g77' or `f2c',
! especially when using options such as `-fno-f2c'.
! 
!    Therefore, if you are using `g77' to compile libraries and other
! object files for possible future use and you don't want to require
! recompilation for future use with subsequent versions of `g77', you
! might want to stick with `f2c' compatibility for now, and carefully
! watch for any announcements about changes to the `f2c'/`libf2c'
! interface that might affect existing programs (thus requiring
! recompilation).
! 
!    It is probable that a future version of `g77' will not, by default,
! generate object files compatible with `f2c', and that version probably
! would no longer use `libf2c'.  If you expect to depend on this
! compatibility in the long term, use the options `-ff2c -ff2c-library'
! when compiling all of the applicable code.  This should cause future
! versions of `g77' either to produce compatible code (at the expense of
! the availability of some features and performance), or at the very
! least, to produce diagnostics.
! 
!    (The library `g77' produces will no longer be named `libg2c' when it
! is no longer generally compatible with `libf2c'.  It will likely be
! referred to, and, if installed as a distinct library, named `libg77',
! or some other as-yet-unused name.)
! 
! 
! File: g77.info,  Node: Compilers Other Than f2c,  Prev: Dropping f2c Compatibility,  Up: Other Compilers
! 
! Compilers Other Than `f2c'
! ==========================
! 
!    On systems with Fortran compilers other than `f2c' and `g77', code
! compiled by `g77' is not expected to work well with code compiled by
! the native compiler.  (This is true for `f2c'-compiled objects as well.)
! Libraries compiled with the native compiler probably will have to be
! recompiled with `g77' to be used with `g77'-compiled code.
! 
!    Reasons for such incompatibilities include:
! 
!    * There might be differences in the way names of Fortran procedures
!      are translated for use in the system's object-file format.  For
!      example, the statement `CALL FOO' might be compiled by `g77' to
!      call a procedure the linker `ld' sees given the name `_foo_',
!      while the apparently corresponding statement `SUBROUTINE FOO'
!      might be compiled by the native compiler to define the
!      linker-visible name `_foo', or `_FOO_', and so on.
! 
!    * There might be subtle type mismatches which cause subroutine
!      arguments and function return values to get corrupted.
! 
!      This is why simply getting `g77' to transform procedure names the
!      same way a native compiler does is not usually a good idea--unless
!      some effort has been made to ensure that, aside from the way the
!      two compilers transform procedure names, everything else about the
!      way they generate code for procedure interfaces is identical.
! 
!    * Native compilers use libraries of private I/O routines which will
!      not be available at link time unless you have the native
!      compiler--and you would have to explicitly ask for them.
! 
!      For example, on the Sun you would have to add `-L/usr/lang/SCx.x
!      -lF77 -lV77' to the link command.
! 
! 
! File: g77.info,  Node: Other Languages,  Next: Debugging and Interfacing,  Prev: Other Compilers,  Up: Top
! 
! Other Languages
! ***************
! 
!    _Note: This portion of the documentation definitely needs a lot of
! work!_
! 
! * Menu:
! 
! * Interoperating with C and C++::
! 
! 
! File: g77.info,  Node: Interoperating with C and C++,  Up: Other Languages
! 
! Tools and advice for interoperating with C and C++
! ==================================================
! 
!    The following discussion assumes that you are running `g77' in `f2c'
! compatibility mode, i.e. not using `-fno-f2c'.  It provides some advice
! about quick and simple techniques for linking Fortran and C (or C++),
! the most common requirement.  For the full story consult the
! description of code generation.  *Note Debugging and Interfacing::.
! 
!    When linking Fortran and C, it's usually best to use `g77' to do the
! linking so that the correct libraries are included (including the maths
! one).  If you're linking with C++ you will want to add `-lstdc++',
! `-lg++' or whatever.  If you need to use another driver program (or
! `ld' directly), you can find out what linkage options `g77' passes by
! running `g77 -v'.
! 
! * Menu:
! 
! * C Interfacing Tools::
! * C Access to Type Information::
! * f2c Skeletons and Prototypes::
! * C++ Considerations::
! * Startup Code::
! 
! 
! File: g77.info,  Node: C Interfacing Tools,  Next: C Access to Type Information,  Up: Interoperating with C and C++
! 
! C Interfacing Tools
! -------------------
! 
!    Even if you don't actually use it as a compiler, `f2c' from
! `ftp://ftp.netlib.org/f2c/src', can be a useful tool when you're
! interfacing (linking) Fortran and C.  *Note Generating Skeletons and
! Prototypes with `f2c': f2c Skeletons and Prototypes.
! 
!    To use `f2c' for this purpose you only need retrieve and build the
! `src' directory from the distribution, consult the `README'
! instructions there for machine-specifics, and install the `f2c' program
! on your path.
! 
!    Something else that might be useful is `cfortran.h' from
! `ftp://zebra.desy.de/cfortran'.  This is a fairly general tool which
! can be used to generate interfaces for calling in both directions
! between Fortran and C.  It can be used in `f2c' mode with
! `g77'--consult its documentation for details.
! 
! 
! File: g77.info,  Node: C Access to Type Information,  Next: f2c Skeletons and Prototypes,  Prev: C Interfacing Tools,  Up: Interoperating with C and C++
! 
! Accessing Type Information in C
! -------------------------------
! 
!    Generally, C code written to link with `g77' code--calling and/or
! being called from Fortran--should `#include <g2c.h>' to define the C
! versions of the Fortran types.  Don't assume Fortran `INTEGER' types
! correspond to C `int's, for instance; instead, declare them as
! `integer', a type defined by `g2c.h'.  `g2c.h' is installed where `gcc'
! will find it by default, assuming you use a copy of `gcc' compatible
! with `g77', probably built at the same time as `g77'.
! 
! 
! File: g77.info,  Node: f2c Skeletons and Prototypes,  Next: C++ Considerations,  Prev: C Access to Type Information,  Up: Interoperating with C and C++
! 
! Generating Skeletons and Prototypes with `f2c'
! ----------------------------------------------
! 
!    A simple and foolproof way to write `g77'-callable C routines--e.g.
! to interface with an existing library--is to write a file (named, for
! example, `fred.f') of dummy Fortran skeletons comprising just the
! declaration of the routine(s) and dummy arguments plus `END' statements.
! Then run `f2c' on file `fred.f' to produce `fred.c' into which you can
! edit useful code, confident the calling sequence is correct, at least.
! (There are some errors otherwise commonly made in generating C
! interfaces with `f2c' conventions, such as not using `doublereal' as
! the return type of a `REAL' `FUNCTION'.)
! 
!    `f2c' also can help with calling Fortran from C, using its `-P'
! option to generate C prototypes appropriate for calling the Fortran.(1)
! If the Fortran code containing any routines to be called from C is in
! file `joe.f', use the command `f2c -P joe.f' to generate the file
! `joe.P' containing prototype information.  `#include' this in the C
! which has to call the Fortran routines to make sure you get it right.
! 
!    *Note Arrays (DIMENSION): Arrays, for information on the differences
! between the way Fortran (including compilers like `g77') and C handle
! arrays.
! 
!    ---------- Footnotes ----------
! 
!    (1) The files generated like this can also be used for inter-unit
! consistency checking of dummy and actual arguments, although the
! `ftnchek' tool from `ftp://ftp.netlib.org/fortran' or
! `ftp://ftp.dsm.fordham.edu' is probably better for this purpose.
! 
! 
! File: g77.info,  Node: C++ Considerations,  Next: Startup Code,  Prev: f2c Skeletons and Prototypes,  Up: Interoperating with C and C++
! 
! C++ Considerations
! ------------------
! 
!    `f2c' can be used to generate suitable code for compilation with a
! C++ system using the `-C++' option.  The important thing about linking
! `g77'-compiled code with C++ is that the prototypes for the `g77'
! routines must specify C linkage to avoid name mangling.  So, use an
! `extern "C"' declaration.  `f2c''s `-C++' option will not take care of
! this when generating skeletons or prototype files as above, however, it
! will avoid clashes with C++ reserved words in addition to those in C.
! 
! 
! File: g77.info,  Node: Startup Code,  Prev: C++ Considerations,  Up: Interoperating with C and C++
! 
! Startup Code
! ------------
! 
!    Unlike with some runtime systems, it shouldn't be necessary (unless
! there are bugs) to use a Fortran main program unit to ensure the
! runtime--specifically the I/O system--is initialized.
! 
!    However, to use the `g77' intrinsics `GETARG' and `IARGC', either
! the `main' routine from the `libg2c' library must be used, or the
! `f_setarg' routine (new as of `egcs' version 1.1 and `g77' version
! 0.5.23) must be called with the appropriate `argc' and `argv' arguments
! prior to the program calling `GETARG' or `IARGC'.
! 
!    To provide more flexibility for mixed-language programming involving
! `g77' while allowing for shared libraries, as of `egcs' version 1.1 and
! `g77' version 0.5.23, `g77''s `main' routine in `libg2c' does the
! following, in order:
! 
!   1. Calls `f_setarg' with the incoming `argc' and `argv' arguments, in
!      the same order as for `main' itself.
! 
!      This sets up the command-line environment for `GETARG' and `IARGC'.
! 
!   2. Calls `f_setsig' (with no arguments).
! 
!      This sets up the signaling and exception environment.
! 
!   3. Calls `f_init' (with no arguments).
! 
!      This initializes the I/O environment, though that should not be
!      necessary, as all I/O functions in `libf2c' are believed to call
!      `f_init' automatically, if necessary.
! 
!      (A future version of `g77' might skip this explicit step, to speed
!      up normal exit of a program.)
! 
!   4. Arranges for `f_exit' to be called (with no arguments) when the
!      program exits.
! 
!      This ensures that the I/O environment is properly shut down before
!      the program exits normally.  Otherwise, output buffers might not
!      be fully flushed, scratch files might not be deleted, and so on.
! 
!      The simple way `main' does this is to call `f_exit' itself after
!      calling `MAIN__' (in the next step).
! 
!      However, this does not catch the cases where the program might
!      call `exit' directly, instead of using the `EXIT' intrinsic
!      (implemented as `exit_' in `libf2c').
! 
!      So, `main' attempts to use the operating environment's `onexit' or
!      `atexit' facility, if available, to cause `f_exit' to be called
!      automatically upon any invocation of `exit'.
! 
!   5. Calls `MAIN__' (with no arguments).
! 
!      This starts executing the Fortran main program unit for the
!      application.  (Both `g77' and `f2c' currently compile a main
!      program unit so that its global name is `MAIN__'.)
! 
!   6. If no `onexit' or `atexit' is provided by the system, calls
!      `f_exit'.
! 
!   7. Calls `exit' with a zero argument, to signal a successful program
!      termination.
! 
!   8. Returns a zero value to the caller, to signal a successful program
!      termination, in case `exit' doesn't exit on the system.
! 
!    All of the above names are C `extern' names, i.e. not mangled.
! 
!    When using the `main' procedure provided by `g77' without a Fortran
! main program unit, you need to provide `MAIN__' as the entry point for
! your C code.  (Make sure you link the object file that defines that
! entry point with the rest of your program.)
! 
!    To provide your own `main' procedure in place of `g77''s, make sure
! you specify the object file defining that procedure _before_ `-lg2c' on
! the `g77' command line.  Since the `-lg2c' option is implicitly
! provided, this is usually straightforward.  (Use the `--verbose' option
! to see how and where `g77' implicitly adds `-lg2c' in a command line
! that will link the program.  Feel free to specify `-lg2c' explicitly,
! as appropriate.)
! 
!    However, when providing your own `main', make sure you perform the
! appropriate tasks in the appropriate order.  For example, if your
! `main' does not call `f_setarg', make sure the rest of your application
! does not call `GETARG' or `IARGC'.
! 
!    And, if your `main' fails to ensure that `f_exit' is called upon
! program exit, some files might end up incompletely written, some
! scratch files might be left lying around, and some existing files being
! written might be left with old data not properly truncated at the end.
! 
!    Note that, generally, the `g77' operating environment does not
! depend on a procedure named `MAIN__' actually being called prior to any
! other `g77'-compiled code.  That is, `MAIN__' does not, itself, set up
! any important operating-environment characteristics upon which other
! code might depend.  This might change in future versions of `g77', with
! appropriate notification in the release notes.
! 
!    For more information, consult the source code for the above routines.
! These are in `gcc/libf2c/libF77/', named `main.c', `setarg.c',
! `setsig.c', `getarg_.c', and `iargc_.c'.
! 
!    Also, the file `gcc/gcc/f/com.c' contains the code `g77' uses to
! open-code (inline) references to `IARGC'.
! 
! 
! File: g77.info,  Node: Debugging and Interfacing,  Next: Collected Fortran Wisdom,  Prev: Other Languages,  Up: Top
! 
! Debugging and Interfacing
! *************************
! 
!    GNU Fortran currently generates code that is object-compatible with
! the `f2c' converter.  Also, it avoids limitations in the current GBE,
! such as the inability to generate a procedure with multiple entry
! points, by generating code that is structured differently (in terms of
! procedure names, scopes, arguments, and so on) than might be expected.
! 
!    As a result, writing code in other languages that calls on, is
! called by, or shares in-memory data with `g77'-compiled code generally
! requires some understanding of the way `g77' compiles code for various
! constructs.
! 
!    Similarly, using a debugger to debug `g77'-compiled code, even if
! that debugger supports native Fortran debugging, generally requires
! this sort of information.
! 
!    This section describes some of the basic information on how `g77'
! compiles code for constructs involving interfaces to other languages
! and to debuggers.
! 
!    _Caution:_ Much or all of this information pertains to only the
! current release of `g77', sometimes even to using certain compiler
! options with `g77' (such as `-fno-f2c').  Do not write code that
! depends on this information without clearly marking said code as
! nonportable and subject to review for every new release of `g77'.  This
! information is provided primarily to make debugging of code generated
! by this particular release of `g77' easier for the user, and partly to
! make writing (generally nonportable) interface code easier.  Both of
! these activities require tracking changes in new version of `g77' as
! they are installed, because new versions can change the behaviors
! described in this section.
! 
! * Menu:
! 
! * Main Program Unit::  How `g77' compiles a main program unit.
! * Procedures::         How `g77' constructs parameter lists
!                        for procedures.
! * Functions::          Functions returning floating-point or character data.
! * Names::              Naming of user-defined variables, procedures, etc.
! * Common Blocks::      Accessing common variables while debugging.
! * Local Equivalence Areas::  Accessing `EQUIVALENCE' while debugging.
! * Complex Variables::  How `g77' performs complex arithmetic.
! * Arrays::             Dealing with (possibly multi-dimensional) arrays.
! * Adjustable Arrays::  Special consideration for adjustable arrays.
! * Alternate Entry Points::  How `g77' implements alternate `ENTRY'.
! * Alternate Returns::  How `g77' handles alternate returns.
! * Assigned Statement Labels::  How `g77' handles `ASSIGN'.
! * Run-time Library Errors::  Meanings of some `IOSTAT=' values.
! 
! 
! File: g77.info,  Node: Main Program Unit,  Next: Procedures,  Up: Debugging and Interfacing
! 
! Main Program Unit (PROGRAM)
! ===========================
! 
!    When `g77' compiles a main program unit, it gives it the public
! procedure name `MAIN__'.  The `libg2c' library has the actual `main()'
! procedure as is typical of C-based environments, and it is this
! procedure that performs some initial start-up activity and then calls
! `MAIN__'.
! 
!    Generally, `g77' and `libg2c' are designed so that you need not
! include a main program unit written in Fortran in your program--it can
! be written in C or some other language.  Especially for I/O handling,
! this is the case, although `g77' version 0.5.16 includes a bug fix for
! `libg2c' that solved a problem with using the `OPEN' statement as the
! first Fortran I/O activity in a program without a Fortran main program
! unit.
! 
!    However, if you don't intend to use `g77' (or `f2c') to compile your
! main program unit--that is, if you intend to compile a `main()'
! procedure using some other language--you should carefully examine the
! code for `main()' in `libg2c', found in the source file
! `gcc/libf2c/libF77/main.c', to see what kinds of things might need to
! be done by your `main()' in order to provide the Fortran environment
! your Fortran code is expecting.
! 
!    For example, `libg2c''s `main()' sets up the information used by the
! `IARGC' and `GETARG' intrinsics.  Bypassing `libg2c''s `main()' without
! providing a substitute for this activity would mean that invoking
! `IARGC' and `GETARG' would produce undefined results.
! 
!    When debugging, one implication of the fact that `main()', which is
! the place where the debugged program "starts" from the debugger's point
! of view, is in `libg2c' is that you won't be starting your Fortran
! program at a point you recognize as your Fortran code.
! 
!    The standard way to get around this problem is to set a break point
! (a one-time, or temporary, break point will do) at the entrance to
! `MAIN__', and then run the program.  A convenient way to do so is to
! add the `gdb' command
! 
!      tbreak MAIN__
! 
! to the file `.gdbinit' in the directory in which you're debugging
! (using `gdb').
! 
!    After doing this, the debugger will see the current execution point
! of the program as at the beginning of the main program unit of your
! program.
! 
!    Of course, if you really want to set a break point at some other
! place in your program and just start the program running, without first
! breaking at `MAIN__', that should work fine.
! 
! 
! File: g77.info,  Node: Procedures,  Next: Functions,  Prev: Main Program Unit,  Up: Debugging and Interfacing
! 
! Procedures (SUBROUTINE and FUNCTION)
! ====================================
! 
!    Currently, `g77' passes arguments via reference--specifically, by
! passing a pointer to the location in memory of a variable, array, array
! element, a temporary location that holds the result of evaluating an
! expression, or a temporary or permanent location that holds the value
! of a constant.
! 
!    Procedures that accept `CHARACTER' arguments are implemented by
! `g77' so that each `CHARACTER' argument has two actual arguments.
! 
!    The first argument occupies the expected position in the argument
! list and has the user-specified name.  This argument is a pointer to an
! array of characters, passed by the caller.
! 
!    The second argument is appended to the end of the user-specified
! calling sequence and is named `__g77_length_X', where X is the
! user-specified name.  This argument is of the C type `ftnlen' (see
! `gcc/libf2c/g2c.h.in' for information on that type) and is the number
! of characters the caller has allocated in the array pointed to by the
! first argument.
! 
!    A procedure will ignore the length argument if `X' is not declared
! `CHARACTER*(*)', because for other declarations, it knows the length.
! Not all callers necessarily "know" this, however, which is why they all
! pass the extra argument.
! 
!    The contents of the `CHARACTER' argument are specified by the
! address passed in the first argument (named after it).  The procedure
! can read or write these contents as appropriate.
! 
!    When more than one `CHARACTER' argument is present in the argument
! list, the length arguments are appended in the order the original
! arguments appear.  So `CALL FOO('HI','THERE')' is implemented in C as
! `foo("hi","there",2,5);', ignoring the fact that `g77' does not provide
! the trailing null bytes on the constant strings (`f2c' does provide
! them, but they are unnecessary in a Fortran environment, and you should
! not expect them to be there).
! 
!    Note that the above information applies to `CHARACTER' variables and
! arrays *only*.  It does *not* apply to external `CHARACTER' functions
! or to intrinsic `CHARACTER' functions.  That is, no second length
! argument is passed to `FOO' in this case:
! 
!      CHARACTER X
!      EXTERNAL X
!      CALL FOO(X)
! 
! Nor does `FOO' expect such an argument in this case:
! 
!      SUBROUTINE FOO(X)
!      CHARACTER X
!      EXTERNAL X
! 
!    Because of this implementation detail, if a program has a bug such
! that there is disagreement as to whether an argument is a procedure,
! and the type of the argument is `CHARACTER', subtle symptoms might
! appear.
! 
! 
! File: g77.info,  Node: Functions,  Next: Names,  Prev: Procedures,  Up: Debugging and Interfacing
! 
! Functions (FUNCTION and RETURN)
! ===============================
! 
!    `g77' handles in a special way functions that return the following
! types:
! 
!    * `CHARACTER'
! 
!    * `COMPLEX'
! 
!    * `REAL(KIND=1)'
! 
!    For `CHARACTER', `g77' implements a subroutine (a C function
! returning `void') with two arguments prepended: `__g77_result', which
! the caller passes as a pointer to a `char' array expected to hold the
! return value, and `__g77_length', which the caller passes as an
! `ftnlen' value specifying the length of the return value as declared in
! the calling program.  For `CHARACTER*(*)', the called function uses
! `__g77_length' to determine the size of the array that `__g77_result'
! points to; otherwise, it ignores that argument.
! 
!    For `COMPLEX', when `-ff2c' is in force, `g77' implements a
! subroutine with one argument prepended: `__g77_result', which the
! caller passes as a pointer to a variable of the type of the function.
! The called function writes the return value into this variable instead
! of returning it as a function value.  When `-fno-f2c' is in force,
! `g77' implements a `COMPLEX' function as `gcc''s `__complex__ float' or
! `__complex__ double' function (or an emulation thereof, when
! `-femulate-complex' is in effect), returning the result of the function
! in the same way as `gcc' would.
! 
!    For `REAL(KIND=1)', when `-ff2c' is in force, `g77' implements a
! function that actually returns `REAL(KIND=2)' (typically C's `double'
! type).  When `-fno-f2c' is in force, `REAL(KIND=1)' functions return
! `float'.
! 
! 
! File: g77.info,  Node: Names,  Next: Common Blocks,  Prev: Functions,  Up: Debugging and Interfacing
! 
! Names
! =====
! 
!    Fortran permits each implementation to decide how to represent names
! as far as how they're seen in other contexts, such as debuggers and
! when interfacing to other languages, and especially as far as how
! casing is handled.
! 
!    External names--names of entities that are public, or "accessible",
! to all modules in a program--normally have an underscore (`_') appended
! by `g77', to generate code that is compatible with `f2c'.  External
! names include names of Fortran things like common blocks, external
! procedures (subroutines and functions, but not including statement
! functions, which are internal procedures), and entry point names.
! 
!    However, use of the `-fno-underscoring' option disables this kind of
! transformation of external names (though inhibiting the transformation
! certainly improves the chances of colliding with incompatible externals
! written in other languages--but that might be intentional.
! 
!    When `-funderscoring' is in force, any name (external or local) that
! already has at least one underscore in it is implemented by `g77' by
! appending two underscores.  (This second underscore can be disabled via
! the `-fno-second-underscore' option.)  External names are changed this
! way for `f2c' compatibility.  Local names are changed this way to avoid
! collisions with external names that are different in the source
! code--`f2c' does the same thing, but there's no compatibility issue
! there except for user expectations while debugging.
! 
!    For example:
! 
!      Max_Cost = 0
! 
! Here, a user would, in the debugger, refer to this variable using the
! name `max_cost__' (or `MAX_COST__' or `Max_Cost__', as described below).
! (We hope to improve `g77' in this regard in the future--don't write
! scripts depending on this behavior!  Also, consider experimenting with
! the `-fno-underscoring' option to try out debugging without having to
! massage names by hand like this.)
! 
!    `g77' provides a number of command-line options that allow the user
! to control how case mapping is handled for source files.  The default
! is the traditional UNIX model for Fortran compilers--names are mapped
! to lower case.  Other command-line options can be specified to map
! names to upper case, or to leave them exactly as written in the source
! file.
! 
!    For example:
! 
!      Foo = 9.436
! 
! Here, it is normally the case that the variable assigned will be named
! `foo'.  This would be the name to enter when using a debugger to access
! the variable.
! 
!    However, depending on the command-line options specified, the name
! implemented by `g77' might instead be `FOO' or even `Foo', thus
! affecting how debugging is done.
! 
!    Also:
! 
!      Call Foo
! 
! This would normally call a procedure that, if it were in a separate C
! program, be defined starting with the line:
! 
!      void foo_()
! 
! However, `g77' command-line options could be used to change the casing
! of names, resulting in the name `FOO_' or `Foo_' being given to the
! procedure instead of `foo_', and the `-fno-underscoring' option could
! be used to inhibit the appending of the underscore to the name.
! 
! 
! File: g77.info,  Node: Common Blocks,  Next: Local Equivalence Areas,  Prev: Names,  Up: Debugging and Interfacing
! 
! Common Blocks (COMMON)
! ======================
! 
!    `g77' names and lays out `COMMON' areas the same way `f2c' does, for
! compatibility with `f2c'.
! 
! 
! File: g77.info,  Node: Local Equivalence Areas,  Next: Complex Variables,  Prev: Common Blocks,  Up: Debugging and Interfacing
! 
! Local Equivalence Areas (EQUIVALENCE)
! =====================================
! 
!    `g77' treats storage-associated areas involving a `COMMON' block as
! explained in the section on common blocks.
! 
!    A local `EQUIVALENCE' area is a collection of variables and arrays
! connected to each other in any way via `EQUIVALENCE', none of which are
! listed in a `COMMON' statement.
! 
!    (_Note:_ `g77' version 0.5.18 and earlier chose the name for X using
! a different method when more than one name was in the list of names of
! entities placed at the beginning of the array.  Though the
! documentation specified that the first name listed in the `EQUIVALENCE'
! statements was chosen for X, `g77' in fact chose the name using a
! method that was so complicated, it seemed easier to change it to an
! alphabetical sort than to describe the previous method in the
! documentation.)
! 
! 
! File: g77.info,  Node: Complex Variables,  Next: Arrays,  Prev: Local Equivalence Areas,  Up: Debugging and Interfacing
! 
! Complex Variables (COMPLEX)
! ===========================
! 
!    As of 0.5.20, `g77' defaults to handling `COMPLEX' types (and
! related intrinsics, constants, functions, and so on) in a manner that
! makes direct debugging involving these types in Fortran language mode
! difficult.
! 
!    Essentially, `g77' implements these types using an internal
! construct similar to C's `struct', at least as seen by the `gcc' back
! end.
! 
!    Currently, the back end, when outputting debugging info with the
! compiled code for the assembler to digest, does not detect these
! `struct' types as being substitutes for Fortran complex.  As a result,
! the Fortran language modes of debuggers such as `gdb' see these types
! as C `struct' types, which they might or might not support.
! 
!    Until this is fixed, switch to C language mode to work with entities
! of `COMPLEX' type and then switch back to Fortran language mode
! afterward.  (In `gdb', this is accomplished via `set lang c' and either
! `set lang fortran' or `set lang auto'.)
! 
! 
! File: g77.info,  Node: Arrays,  Next: Adjustable Arrays,  Prev: Complex Variables,  Up: Debugging and Interfacing
! 
! Arrays (DIMENSION)
! ==================
! 
!    Fortran uses "column-major ordering" in its arrays.  This differs
! from other languages, such as C, which use "row-major ordering".  The
! difference is that, with Fortran, array elements adjacent to each other
! in memory differ in the _first_ subscript instead of the last;
! `A(5,10,20)' immediately follows `A(4,10,20)', whereas with row-major
! ordering it would follow `A(5,10,19)'.
! 
!    This consideration affects not only interfacing with and debugging
! Fortran code, it can greatly affect how code is designed and written,
! especially when code speed and size is a concern.
! 
!    Fortran also differs from C, a popular language for interfacing and
! to support directly in debuggers, in the way arrays are treated.  In C,
! arrays are single-dimensional and have interesting relationships to
! pointers, neither of which is true for Fortran.  As a result, dealing
! with Fortran arrays from within an environment limited to C concepts
! can be challenging.
! 
!    For example, accessing the array element `A(5,10,20)' is easy enough
! in Fortran (use `A(5,10,20)'), but in C some difficult machinations are
! needed.  First, C would treat the A array as a single-dimension array.
! Second, C does not understand low bounds for arrays as does Fortran.
! Third, C assumes a low bound of zero (0), while Fortran defaults to a
! low bound of one (1) and can supports an arbitrary low bound.
! Therefore, calculations must be done to determine what the C equivalent
! of `A(5,10,20)' would be, and these calculations require knowing the
! dimensions of `A'.
! 
!    For `DIMENSION A(2:11,21,0:29)', the calculation of the offset of
! `A(5,10,20)' would be:
! 
!        (5-2)
!      + (10-1)*(11-2+1)
!      + (20-0)*(11-2+1)*(21-1+1)
!      = 4293
! 
! So the C equivalent in this case would be `a[4293]'.
! 
!    When using a debugger directly on Fortran code, the C equivalent
! might not work, because some debuggers cannot understand the notion of
! low bounds other than zero.  However, unlike `f2c', `g77' does inform
! the GBE that a multi-dimensional array (like `A' in the above example)
! is really multi-dimensional, rather than a single-dimensional array, so
! at least the dimensionality of the array is preserved.
! 
!    Debuggers that understand Fortran should have no trouble with
! nonzero low bounds, but for non-Fortran debuggers, especially C
! debuggers, the above example might have a C equivalent of `a[4305]'.
! This calculation is arrived at by eliminating the subtraction of the
! lower bound in the first parenthesized expression on each line--that
! is, for `(5-2)' substitute `(5)', for `(10-1)' substitute `(10)', and
! for `(20-0)' substitute `(20)'.  Actually, the implication of this can
! be that the expression `*(&a[2][1][0] + 4293)' works fine, but that
! `a[20][10][5]' produces the equivalent of `*(&a[0][0][0] + 4305)'
! because of the missing lower bounds.
! 
!    Come to think of it, perhaps the behavior is due to the debugger
! internally compensating for the lower bounds by offsetting the base
! address of `a', leaving `&a' set lower, in this case, than
! `&a[2][1][0]' (the address of its first element as identified by
! subscripts equal to the corresponding lower bounds).
! 
!    You know, maybe nobody really needs to use arrays.
! 
! 
! File: g77.info,  Node: Adjustable Arrays,  Next: Alternate Entry Points,  Prev: Arrays,  Up: Debugging and Interfacing
! 
! Adjustable Arrays (DIMENSION)
! =============================
! 
!    Adjustable and automatic arrays in Fortran require the implementation
! (in this case, the `g77' compiler) to "memorize" the expressions that
! dimension the arrays each time the procedure is invoked.  This is so
! that subsequent changes to variables used in those expressions, made
! during execution of the procedure, do not have any effect on the
! dimensions of those arrays.
! 
!    For example:
! 
!      REAL ARRAY(5)
!      DATA ARRAY/5*2/
!      CALL X(ARRAY, 5)
!      END
!      SUBROUTINE X(A, N)
!      DIMENSION A(N)
!      N = 20
!      PRINT *, N, A
!      END
! 
! Here, the implementation should, when running the program, print
! something like:
! 
!      20   2.  2.  2.  2.  2.
! 
! Note that this shows that while the value of `N' was successfully
! changed, the size of the `A' array remained at 5 elements.
! 
!    To support this, `g77' generates code that executes before any user
! code (and before the internally generated computed `GOTO' to handle
! alternate entry points, as described below) that evaluates each
! (nonconstant) expression in the list of subscripts for an array, and
! saves the result of each such evaluation to be used when determining
! the size of the array (instead of re-evaluating the expressions).
! 
!    So, in the above example, when `X' is first invoked, code is
! executed that copies the value of `N' to a temporary.  And that same
! temporary serves as the actual high bound for the single dimension of
! the `A' array (the low bound being the constant 1).  Since the user
! program cannot (legitimately) change the value of the temporary during
! execution of the procedure, the size of the array remains constant
! during each invocation.
! 
!    For alternate entry points, the code `g77' generates takes into
! account the possibility that a dummy adjustable array is not actually
! passed to the actual entry point being invoked at that time.  In that
! case, the public procedure implementing the entry point passes to the
! master private procedure implementing all the code for the entry points
! a `NULL' pointer where a pointer to that adjustable array would be
! expected.  The `g77'-generated code doesn't attempt to evaluate any of
! the expressions in the subscripts for an array if the pointer to that
! array is `NULL' at run time in such cases.  (Don't depend on this
! particular implementation by writing code that purposely passes `NULL'
! pointers where the callee expects adjustable arrays, even if you know
! the callee won't reference the arrays--nor should you pass `NULL'
! pointers for any dummy arguments used in calculating the bounds of such
! arrays or leave undefined any values used for that purpose in
! COMMON--because the way `g77' implements these things might change in
! the future!)
! 
! 
! File: g77.info,  Node: Alternate Entry Points,  Next: Alternate Returns,  Prev: Adjustable Arrays,  Up: Debugging and Interfacing
! 
! Alternate Entry Points (ENTRY)
! ==============================
! 
!    The GBE does not understand the general concept of alternate entry
! points as Fortran provides via the ENTRY statement.  `g77' gets around
! this by using an approach to compiling procedures having at least one
! `ENTRY' statement that is almost identical to the approach used by
! `f2c'.  (An alternate approach could be used that would probably
! generate faster, but larger, code that would also be a bit easier to
! debug.)
! 
!    Information on how `g77' implements `ENTRY' is provided for those
! trying to debug such code.  The choice of implementation seems unlikely
! to affect code (compiled in other languages) that interfaces to such
! code.
! 
!    `g77' compiles exactly one public procedure for the primary entry
! point of a procedure plus each `ENTRY' point it specifies, as usual.
! That is, in terms of the public interface, there is no difference
! between
! 
!      SUBROUTINE X
!      END
!      SUBROUTINE Y
!      END
! 
! and:
! 
!      SUBROUTINE X
!      ENTRY Y
!      END
! 
!    The difference between the above two cases lies in the code compiled
! for the `X' and `Y' procedures themselves, plus the fact that, for the
! second case, an extra internal procedure is compiled.
! 
!    For every Fortran procedure with at least one `ENTRY' statement,
! `g77' compiles an extra procedure named `__g77_masterfun_X', where X is
! the name of the primary entry point (which, in the above case, using
! the standard compiler options, would be `x_' in C).
! 
!    This extra procedure is compiled as a private procedure--that is, a
! procedure not accessible by name to separately compiled modules.  It
! contains all the code in the program unit, including the code for the
! primary entry point plus for every entry point.  (The code for each
! public procedure is quite short, and explained later.)
! 
!    The extra procedure has some other interesting characteristics.
! 
!    The argument list for this procedure is invented by `g77'.  It
! contains a single integer argument named `__g77_which_entrypoint',
! passed by value (as in Fortran's `%VAL()' intrinsic), specifying the
! entry point index--0 for the primary entry point, 1 for the first entry
! point (the first `ENTRY' statement encountered), 2 for the second entry
! point, and so on.
! 
!    It also contains, for functions returning `CHARACTER' and (when
! `-ff2c' is in effect) `COMPLEX' functions, and for functions returning
! different types among the `ENTRY' statements (e.g. `REAL FUNCTION R()'
! containing `ENTRY I()'), an argument named `__g77_result' that is
! expected at run time to contain a pointer to where to store the result
! of the entry point.  For `CHARACTER' functions, this storage area is an
! array of the appropriate number of characters; for `COMPLEX' functions,
! it is the appropriate area for the return type; for
! multiple-return-type functions, it is a union of all the supported
! return types (which cannot include `CHARACTER', since combining
! `CHARACTER' and non-`CHARACTER' return types via `ENTRY' in a single
! function is not supported by `g77').
! 
!    For `CHARACTER' functions, the `__g77_result' argument is followed
! by yet another argument named `__g77_length' that, at run time,
! specifies the caller's expected length of the returned value.  Note
! that only `CHARACTER*(*)' functions and entry points actually make use
! of this argument, even though it is always passed by all callers of
! public `CHARACTER' functions (since the caller does not generally know
! whether such a function is `CHARACTER*(*)' or whether there are any
! other callers that don't have that information).
! 
!    The rest of the argument list is the union of all the arguments
! specified for all the entry points (in their usual forms, e.g.
! `CHARACTER' arguments have extra length arguments, all appended at the
! end of this list).  This is considered the "master list" of arguments.
! 
!    The code for this procedure has, before the code for the first
! executable statement, code much like that for the following Fortran
! statement:
! 
!             GOTO (100000,100001,100002), __g77_which_entrypoint
!      100000 ...code for primary entry point...
!      100001 ...code immediately following first ENTRY statement...
!      100002 ...code immediately following second ENTRY statement...
! 
! (Note that invalid Fortran statement labels and variable names are used
! in the above example to highlight the fact that it represents code
! generated by the `g77' internals, not code to be written by the user.)
! 
!    It is this code that, when the procedure is called, picks which
! entry point to start executing.
! 
!    Getting back to the public procedures (`x' and `Y' in the original
! example), those procedures are fairly simple.  Their interfaces are
! just like they would be if they were self-contained procedures (without
! `ENTRY'), of course, since that is what the callers expect.  Their code
! consists of simply calling the private procedure, described above, with
! the appropriate extra arguments (the entry point index, and perhaps a
! pointer to a multiple-type- return variable, local to the public
! procedure, that contains all the supported returnable non-character
! types).  For arguments that are not listed for a given entry point that
! are listed for other entry points, and therefore that are in the
! "master list" for the private procedure, null pointers (in C, the
! `NULL' macro) are passed.  Also, for entry points that are part of a
! multiple-type- returning function, code is compiled after the call of
! the private procedure to extract from the multi-type union the
! appropriate result, depending on the type of the entry point in
! question, returning that result to the original caller.
! 
!    When debugging a procedure containing alternate entry points, you
! can either set a break point on the public procedure itself (e.g.  a
! break point on `X' or `Y') or on the private procedure that contains
! most of the pertinent code (e.g. `__g77_masterfun_X').  If you do the
! former, you should use the debugger's command to "step into" the called
! procedure to get to the actual code; with the latter approach, the
! break point leaves you right at the actual code, skipping over the
! public entry point and its call to the private procedure (unless you
! have set a break point there as well, of course).
! 
!    Further, the list of dummy arguments that is visible when the
! private procedure is active is going to be the expanded version of the
! list for whichever particular entry point is active, as explained
! above, and the way in which return values are handled might well be
! different from how they would be handled for an equivalent single-entry
! function.
! 
! 
! File: g77.info,  Node: Alternate Returns,  Next: Assigned Statement Labels,  Prev: Alternate Entry Points,  Up: Debugging and Interfacing
! 
! Alternate Returns (SUBROUTINE and RETURN)
! =========================================
! 
!    Subroutines with alternate returns (e.g. `SUBROUTINE X(*)' and `CALL
! X(*50)') are implemented by `g77' as functions returning the C `int'
! type.  The actual alternate-return arguments are omitted from the
! calling sequence.  Instead, the caller uses the return value to do a
! rough equivalent of the Fortran computed-`GOTO' statement, as in `GOTO
! (50), X()' in the example above (where `X' is quietly declared as an
! `INTEGER(KIND=1)' function), and the callee just returns whatever
! integer is specified in the `RETURN' statement for the subroutine For
! example, `RETURN 1' is implemented as `X = 1' followed by `RETURN' in
! C, and `RETURN' by itself is `X = 0' and `RETURN').
! 
! 
! File: g77.info,  Node: Assigned Statement Labels,  Next: Run-time Library Errors,  Prev: Alternate Returns,  Up: Debugging and Interfacing
! 
! Assigned Statement Labels (ASSIGN and GOTO)
! ===========================================
! 
!    For portability to machines where a pointer (such as to a label,
! which is how `g77' implements `ASSIGN' and its relatives, the
! assigned-`GOTO' and assigned-`FORMAT'-I/O statements) is wider
! (bitwise) than an `INTEGER(KIND=1)', `g77' uses a different memory
! location to hold the `ASSIGN'ed value of a variable than it does the
! numerical value in that variable, unless the variable is wide enough
! (can hold enough bits).
! 
!    In particular, while `g77' implements
! 
!      I = 10
! 
! as, in C notation, `i = 10;', it implements
! 
!      ASSIGN 10 TO I
! 
! as, in GNU's extended C notation (for the label syntax),
! `__g77_ASSIGN_I = &&L10;' (where `L10' is just a massaging of the
! Fortran label `10' to make the syntax C-like; `g77' doesn't actually
! generate the name `L10' or any other name like that, since debuggers
! cannot access labels anyway).
! 
!    While this currently means that an `ASSIGN' statement does not
! overwrite the numeric contents of its target variable, _do not_ write
! any code depending on this feature.  `g77' has already changed this
! implementation across versions and might do so in the future.  This
! information is provided only to make debugging Fortran programs
! compiled with the current version of `g77' somewhat easier.  If there's
! no debugger-visible variable named `__g77_ASSIGN_I' in a program unit
! that does `ASSIGN 10 TO I', that probably means `g77' has decided it
! can store the pointer to the label directly into `I' itself.
! 
!    *Note Ugly Assigned Labels::, for information on a command-line
! option to force `g77' to use the same storage for both normal and
! assigned-label uses of a variable.
! 
! 
! File: g77.info,  Node: Run-time Library Errors,  Prev: Assigned Statement Labels,  Up: Debugging and Interfacing
! 
! Run-time Library Errors
! =======================
! 
!    The `libg2c' library currently has the following table to relate
! error code numbers, returned in `IOSTAT=' variables, to messages.  This
! information should, in future versions of this document, be expanded
! upon to include detailed descriptions of each message.
! 
!    In line with good coding practices, any of the numbers in the list
! below should _not_ be directly written into Fortran code you write.
! Instead, make a separate `INCLUDE' file that defines `PARAMETER' names
! for them, and use those in your code, so you can more easily change the
! actual numbers in the future.
! 
!    The information below is culled from the definition of `F_err' in
! `f/runtime/libI77/err.c' in the `g77' source tree.
! 
!      100: "error in format"
!      101: "illegal unit number"
!      102: "formatted io not allowed"
!      103: "unformatted io not allowed"
!      104: "direct io not allowed"
!      105: "sequential io not allowed"
!      106: "can't backspace file"
!      107: "null file name"
!      108: "can't stat file"
!      109: "unit not connected"
!      110: "off end of record"
!      111: "truncation failed in endfile"
!      112: "incomprehensible list input"
!      113: "out of free space"
!      114: "unit not connected"
!      115: "read unexpected character"
!      116: "bad logical input field"
!      117: "bad variable type"
!      118: "bad namelist name"
!      119: "variable not in namelist"
!      120: "no end record"
!      121: "variable count incorrect"
!      122: "subscript for scalar variable"
!      123: "invalid array section"
!      124: "substring out of bounds"
!      125: "subscript out of bounds"
!      126: "can't read file"
!      127: "can't write file"
!      128: "'new' file exists"
!      129: "can't append to file"
!      130: "non-positive record number"
!      131: "I/O started while already doing I/O"
! 
! 
! File: g77.info,  Node: Collected Fortran Wisdom,  Next: Trouble,  Prev: Debugging and Interfacing,  Up: Top
! 
! Collected Fortran Wisdom
! ************************
! 
!    Most users of `g77' can be divided into two camps:
! 
!    * Those writing new Fortran code to be compiled by `g77'.
! 
!    * Those using `g77' to compile existing, "legacy" code.
! 
!    Users writing new code generally understand most of the necessary
! aspects of Fortran to write "mainstream" code, but often need help
! deciding how to handle problems, such as the construction of libraries
! containing `BLOCK DATA'.
! 
!    Users dealing with "legacy" code sometimes don't have much
! experience with Fortran, but believe that the code they're compiling
! already works when compiled by other compilers (and might not
! understand why, as is sometimes the case, it doesn't work when compiled
! by `g77').
! 
!    The following information is designed to help users do a better job
! coping with existing, "legacy" Fortran code, and with writing new code
! as well.
! 
! * Menu:
! 
! * Advantages Over f2c::        If `f2c' is so great, why `g77'?
! * Block Data and Libraries::   How `g77' solves a common problem.
! * Loops::                      Fortran `DO' loops surprise many people.
! * Working Programs::           Getting programs to work should be done first.
! * Overly Convenient Options::  Temptations to avoid, habits to not form.
! * Faster Programs::            Everybody wants these, but at what cost?
! 
! 
! File: g77.info,  Node: Advantages Over f2c,  Next: Block Data and Libraries,  Up: Collected Fortran Wisdom
! 
! Advantages Over f2c
! ===================
! 
!    Without `f2c', `g77' would have taken much longer to do and probably
! not been as good for quite a while.  Sometimes people who notice how
! much `g77' depends on, and documents encouragement to use, `f2c' ask
! why `g77' was created if `f2c' already existed.
! 
!    This section gives some basic answers to these questions, though it
! is not intended to be comprehensive.
! 
! * Menu:
! 
! * Language Extensions::  Features used by Fortran code.
! * Diagnostic Abilities:: Abilities to spot problems early.
! * Compiler Options::     Features helpful to accommodate legacy code, etc.
! * Compiler Speed::       Speed of the compilation process.
! * Program Speed::        Speed of the generated, optimized code.
! * Ease of Debugging::    Debugging ease-of-use at the source level.
! * Character and Hollerith Constants::  A byte saved is a byte earned.
! 
! 
! File: g77.info,  Node: Language Extensions,  Next: Diagnostic Abilities,  Up: Advantages Over f2c
! 
! Language Extensions
! -------------------
! 
!    `g77' offers several extensions to FORTRAN 77 language that `f2c'
! doesn't:
! 
!    * Automatic arrays
! 
!    * `CYCLE' and `EXIT'
! 
!    * Construct names
! 
!    * `SELECT CASE'
! 
!    * `KIND=' and `LEN=' notation
! 
!    * Semicolon as statement separator
! 
!    * Constant expressions in `FORMAT' statements (such as
!      `FORMAT(I<J>)', where `J' is a `PARAMETER' named constant)
! 
!    * `MvBits' intrinsic
! 
!    * `libU77' (Unix-compatibility) library, with routines known to
!      compiler as intrinsics (so they work even when compiler options
!      are used to change the interfaces used by Fortran routines)
! 
!    `g77' also implements iterative `DO' loops so that they work even in
! the presence of certain "extreme" inputs, unlike `f2c'.  *Note Loops::.
! 
!    However, `f2c' offers a few that `g77' doesn't, such as:
! 
!    * Intrinsics in `PARAMETER' statements
! 
!    * Array bounds expressions (such as `REAL M(N(2))')
! 
!    * `AUTOMATIC' statement
! 
!    It is expected that `g77' will offer some or all of these missing
! features at some time in the future.
! 
! 
! File: g77.info,  Node: Diagnostic Abilities,  Next: Compiler Options,  Prev: Language Extensions,  Up: Advantages Over f2c
! 
! Diagnostic Abilities
! --------------------
! 
!    `g77' offers better diagnosis of problems in `FORMAT' statements.
! `f2c' doesn't, for example, emit any diagnostic for
! `FORMAT(XZFAJG10324)', leaving that to be diagnosed, at run time, by
! the `libf2c' run-time library.
! 
! 
! File: g77.info,  Node: Compiler Options,  Next: Compiler Speed,  Prev: Diagnostic Abilities,  Up: Advantages Over f2c
! 
! Compiler Options
! ----------------
! 
!    `g77' offers compiler options that `f2c' doesn't, most of which are
! designed to more easily accommodate legacy code:
! 
!    * Two that control the automatic appending of extra underscores to
!      external names
! 
!    * One that allows dollar signs (`$') in symbol names
! 
!    * A variety that control acceptance of various "ugly" constructs
! 
!    * Several that specify acceptable use of upper and lower case in the
!      source code
! 
!    * Many that enable, disable, delete, or hide groups of intrinsics
! 
!    * One to specify the length of fixed-form source lines (normally 72)
! 
!    * One to specify the the source code is written in Fortran-90-style
!      free-form
! 
!    However, `f2c' offers a few that `g77' doesn't, like an option to
! have `REAL' default to `REAL*8'.  It is expected that `g77' will offer
! all of the missing options pertinent to being a Fortran compiler at
! some time in the future.
! 
! 
! File: g77.info,  Node: Compiler Speed,  Next: Program Speed,  Prev: Compiler Options,  Up: Advantages Over f2c
! 
! Compiler Speed
! --------------
! 
!    Saving the steps of writing and then rereading C code is a big reason
! why `g77' should be able to compile code much faster than using `f2c'
! in conjunction with the equivalent invocation of `gcc'.
! 
!    However, due to `g77''s youth, lots of self-checking is still being
! performed.  As a result, this improvement is as yet unrealized (though
! the potential seems to be there for quite a big speedup in the future).
! It is possible that, as of version 0.5.18, `g77' is noticeably faster
! compiling many Fortran source files than using `f2c' in conjunction
! with `gcc'.
! 
! 
! File: g77.info,  Node: Program Speed,  Next: Ease of Debugging,  Prev: Compiler Speed,  Up: Advantages Over f2c
! 
! Program Speed
! -------------
! 
!    `g77' has the potential to better optimize code than `f2c', even
! when `gcc' is used to compile the output of `f2c', because `f2c' must
! necessarily translate Fortran into a somewhat lower-level language (C)
! that cannot preserve all the information that is potentially useful for
! optimization, while `g77' can gather, preserve, and transmit that
! information directly to the GBE.
! 
!    For example, `g77' implements `ASSIGN' and assigned `GOTO' using
! direct assignment of pointers to labels and direct jumps to labels,
! whereas `f2c' maps the assigned labels to integer values and then uses
! a C `switch' statement to encode the assigned `GOTO' statements.
! 
!    However, as is typical, theory and reality don't quite match, at
! least not in all cases, so it is still the case that `f2c' plus `gcc'
! can generate code that is faster than `g77'.
! 
!    Version 0.5.18 of `g77' offered default settings and options, via
! patches to the `gcc' back end, that allow for better program speed,
! though some of these improvements also affected the performance of
! programs translated by `f2c' and then compiled by `g77''s version of
! `gcc'.
! 
!    Version 0.5.20 of `g77' offers further performance improvements, at
! least one of which (alias analysis) is not generally applicable to
! `f2c' (though `f2c' could presumably be changed to also take advantage
! of this new capability of the `gcc' back end, assuming this is made
! available in an upcoming release of `gcc').
! 
! 
! File: g77.info,  Node: Ease of Debugging,  Next: Character and Hollerith Constants,  Prev: Program Speed,  Up: Advantages Over f2c
! 
! Ease of Debugging
! -----------------
! 
!    Because `g77' compiles directly to assembler code like `gcc',
! instead of translating to an intermediate language (C) as does `f2c',
! support for debugging can be better for `g77' than `f2c'.
! 
!    However, although `g77' might be somewhat more "native" in terms of
! debugging support than `f2c' plus `gcc', there still are a lot of
! things "not quite right".  Many of the important ones should be
! resolved in the near future.
! 
!    For example, `g77' doesn't have to worry about reserved names like
! `f2c' does.  Given `FOR = WHILE', `f2c' must necessarily translate this
! to something _other_ than `for = while;', because C reserves those
! words.
! 
!    However, `g77' does still uses things like an extra level of
! indirection for `ENTRY'-laden procedures--in this case, because the
! back end doesn't yet support multiple entry points.
! 
!    Another example is that, given
! 
!      COMMON A, B
!      EQUIVALENCE (B, C)
! 
! the `g77' user should be able to access the variables directly, by name,
! without having to traverse C-like structures and unions, while `f2c' is
! unlikely to ever offer this ability (due to limitations in the C
! language).
! 
!    However, due to apparent bugs in the back end, `g77' currently
! doesn't take advantage of this facility at all--it doesn't emit any
! debugging information for `COMMON' and `EQUIVALENCE' areas, other than
! information on the array of `char' it creates (and, in the case of
! local `EQUIVALENCE', names) for each such area.
! 
!    Yet another example is arrays.  `g77' represents them to the debugger
! using the same "dimensionality" as in the source code, while `f2c' must
! necessarily convert them all to one-dimensional arrays to fit into the
! confines of the C language.  However, the level of support offered by
! debuggers for interactive Fortran-style access to arrays as compiled by
! `g77' can vary widely.  In some cases, it can actually be an advantage
! that `f2c' converts everything to widely supported C semantics.
! 
!    In fairness, `g77' could do many of the things `f2c' does to get
! things working at least as well as `f2c'--for now, the developers
! prefer making `g77' work the way they think it is supposed to, and
! finding help improving the other products (the back end of `gcc';
! `gdb'; and so on) to get things working properly.
! 
! 
! File: g77.info,  Node: Character and Hollerith Constants,  Prev: Ease of Debugging,  Up: Advantages Over f2c
! 
! Character and Hollerith Constants
! ---------------------------------
! 
!    To avoid the extensive hassle that would be needed to avoid this,
! `f2c' uses C character constants to encode character and Hollerith
! constants.  That means a constant like `'HELLO'' is translated to
! `"hello"' in C, which further means that an extra null byte is present
! at the end of the constant.  This null byte is superfluous.
! 
!    `g77' does not generate such null bytes.  This represents significant
! savings of resources, such as on systems where `/dev/null' or
! `/dev/zero' represent bottlenecks in the systems' performance, because
! `g77' simply asks for fewer zeros from the operating system than `f2c'.
! (Avoiding spurious use of zero bytes, each byte typically have eight
! zero bits, also reduces the liabilities in case Microsoft's rumored
! patent on the digits 0 and 1 is upheld.)
! 
! 
! File: g77.info,  Node: Block Data and Libraries,  Next: Loops,  Prev: Advantages Over f2c,  Up: Collected Fortran Wisdom
! 
! Block Data and Libraries
! ========================
! 
!    To ensure that block data program units are linked, especially a
! concern when they are put into libraries, give each one a name (as in
! `BLOCK DATA FOO') and make sure there is an `EXTERNAL FOO' statement in
! every program unit that uses any common block initialized by the
! corresponding `BLOCK DATA'.  `g77' currently compiles a `BLOCK DATA' as
! if it were a `SUBROUTINE', that is, it generates an actual procedure
! having the appropriate name.  The procedure does nothing but return
! immediately if it happens to be called.  For `EXTERNAL FOO', where
! `FOO' is not otherwise referenced in the same program unit, `g77'
! assumes there exists a `BLOCK DATA FOO' in the program and ensures that
! by generating a reference to it so the linker will make sure it is
! present.  (Specifically, `g77' outputs in the data section a static
! pointer to the external name `FOO'.)
! 
!    The implementation `g77' currently uses to make this work is one of
! the few things not compatible with `f2c' as currently shipped.  `f2c'
! currently does nothing with `EXTERNAL FOO' except issue a warning that
! `FOO' is not otherwise referenced, and, for `BLOCK DATA FOO', `f2c'
! doesn't generate a dummy procedure with the name `FOO'.  The upshot is
! that you shouldn't mix `f2c' and `g77' in this particular case.  If you
! use `f2c' to compile `BLOCK DATA FOO', then any `g77'-compiled program
! unit that says `EXTERNAL FOO' will result in an unresolved reference
! when linked.  If you do the opposite, then `FOO' might not be linked in
! under various circumstances (such as when `FOO' is in a library, or
! you're using a "clever" linker--so clever, it produces a broken program
! with little or no warning by omitting initializations of global data
! because they are contained in unreferenced procedures).
! 
!    The changes you make to your code to make `g77' handle this
! situation, however, appear to be a widely portable way to handle it.
! That is, many systems permit it (as they should, since the FORTRAN 77
! standard permits `EXTERNAL FOO' when `FOO' is a block data program
! unit), and of the ones that might not link `BLOCK DATA FOO' under some
! circumstances, most of them appear to do so once `EXTERNAL FOO' is
! present in the appropriate program units.
! 
!    Here is the recommended approach to modifying a program containing a
! program unit such as the following:
! 
!      BLOCK DATA FOO
!      COMMON /VARS/ X, Y, Z
!      DATA X, Y, Z / 3., 4., 5. /
!      END
! 
! If the above program unit might be placed in a library module, then
! ensure that every program unit in every program that references that
! particular `COMMON' area uses the `EXTERNAL' statement to force the
! area to be initialized.
! 
!    For example, change a program unit that starts with
! 
!      INTEGER FUNCTION CURX()
!      COMMON /VARS/ X, Y, Z
!      CURX = X
!      END
! 
! so that it uses the `EXTERNAL' statement, as in:
! 
!      INTEGER FUNCTION CURX()
!      COMMON /VARS/ X, Y, Z
!      EXTERNAL FOO
!      CURX = X
!      END
! 
! That way, `CURX' is compiled by `g77' (and many other compilers) so
! that the linker knows it must include `FOO', the `BLOCK DATA' program
! unit that sets the initial values for the variables in `VAR', in the
! executable program.
! 
! 
! File: g77.info,  Node: Loops,  Next: Working Programs,  Prev: Block Data and Libraries,  Up: Collected Fortran Wisdom
! 
! Loops
! =====
! 
!    The meaning of a `DO' loop in Fortran is precisely specified in the
! Fortran standard...and is quite different from what many programmers
! might expect.
! 
!    In particular, Fortran iterative `DO' loops are implemented as if
! the number of trips through the loop is calculated _before_ the loop is
! entered.
! 
!    The number of trips for a loop is calculated from the START, END,
! and INCREMENT values specified in a statement such as:
! 
!      DO ITER = START, END, INCREMENT
! 
! The trip count is evaluated using a fairly simple formula based on the
! three values following the `=' in the statement, and it is that trip
! count that is effectively decremented during each iteration of the loop.
! If, at the beginning of an iteration of the loop, the trip count is
! zero or negative, the loop terminates.  The per-loop-iteration
! modifications to ITER are not related to determining whether to
! terminate the loop.
! 
!    There are two important things to remember about the trip count:
! 
!    * It can be _negative_, in which case it is treated as if it was
!      zero--meaning the loop is not executed at all.
! 
!    * The type used to _calculate_ the trip count is the same type as
!      ITER, but the final calculation, and thus the type of the trip
!      count itself, always is `INTEGER(KIND=1)'.
! 
!    These two items mean that there are loops that cannot be written in
! straightforward fashion using the Fortran `DO'.
! 
!    For example, on a system with the canonical 32-bit two's-complement
! implementation of `INTEGER(KIND=1)', the following loop will not work:
! 
!      DO I = -2000000000, 2000000000
! 
! Although the START and END values are well within the range of
! `INTEGER(KIND=1)', the _trip count_ is not.  The expected trip count is
! 40000000001, which is outside the range of `INTEGER(KIND=1)' on many
! systems.
! 
!    Instead, the above loop should be constructed this way:
! 
!      I = -2000000000
!      DO
!        IF (I .GT. 2000000000) EXIT
!        ...
!        I = I + 1
!      END DO
! 
! The simple `DO' construct and the `EXIT' statement (used to leave the
! innermost loop) are F90 features that `g77' supports.
! 
!    Some Fortran compilers have buggy implementations of `DO', in that
! they don't follow the standard.  They implement `DO' as a
! straightforward translation to what, in C, would be a `for' statement.
! Instead of creating a temporary variable to hold the trip count as
! calculated at run time, these compilers use the iteration variable ITER
! to control whether the loop continues at each iteration.
! 
!    The bug in such an implementation shows up when the trip count is
! within the range of the type of ITER, but the magnitude of `ABS(END) +
! ABS(INCR)' exceeds that range.  For example:
! 
!      DO I = 2147483600, 2147483647
! 
! A loop started by the above statement will work as implemented by
! `g77', but the use, by some compilers, of a more C-like implementation
! akin to
! 
!      for (i = 2147483600; i <= 2147483647; ++i)
! 
! produces a loop that does not terminate, because `i' can never be
! greater than 2147483647, since incrementing it beyond that value
! overflows `i', setting it to -2147483648.  This is a large, negative
! number that still is less than 2147483647.
! 
!    Another example of unexpected behavior of `DO' involves using a
! nonintegral iteration variable ITER, that is, a `REAL' variable.
! Consider the following program:
! 
!            DATA BEGIN, END, STEP /.1, .31, .007/
!            DO 10 R = BEGIN, END, STEP
!               IF (R .GT. END) PRINT *, R, ' .GT. ', END, '!!'
!               PRINT *,R
!      10    CONTINUE
!            PRINT *,'LAST = ',R
!            IF (R .LE. END) PRINT *, R, ' .LE. ', END, '!!'
!            END
! 
! A C-like view of `DO' would hold that the two "exclamatory" `PRINT'
! statements are never executed.  However, this is the output of running
! the above program as compiled by `g77' on a GNU/Linux ix86 system:
! 
!       .100000001
!       .107000001
!       .114
!       .120999999
!       ...
!       .289000005
!       .296000004
!       .303000003
!      LAST =   .310000002
!       .310000002 .LE.   .310000002!!
! 
!    Note that one of the two checks in the program turned up an apparent
! violation of the programmer's expectation--yet, the loop is correctly
! implemented by `g77', in that it has 30 iterations.  This trip count of
! 30 is correct when evaluated using the floating-point representations
! for the BEGIN, END, and INCR values (.1, .31, .007) on GNU/Linux ix86
! are used.  On other systems, an apparently more accurate trip count of
! 31 might result, but, nevertheless, `g77' is faithfully following the
! Fortran standard, and the result is not what the author of the sample
! program above apparently expected.  (Such other systems might, for
! different values in the `DATA' statement, violate the other
! programmer's expectation, for example.)
! 
!    Due to this combination of imprecise representation of
! floating-point values and the often-misunderstood interpretation of
! `DO' by standard-conforming compilers such as `g77', use of `DO' loops
! with `REAL' iteration variables is not recommended.  Such use can be
! caught by specifying `-Wsurprising'.  *Note Warning Options::, for more
! information on this option.
! 
! 
! File: g77.info,  Node: Working Programs,  Next: Overly Convenient Options,  Prev: Loops,  Up: Collected Fortran Wisdom
! 
! Working Programs
! ================
! 
!    Getting Fortran programs to work in the first place can be quite a
! challenge--even when the programs already work on other systems, or
! when using other compilers.
! 
!    `g77' offers some facilities that might be useful for tracking down
! bugs in such programs.
! 
! * Menu:
! 
! * Not My Type::
! * Variables Assumed To Be Zero::
! * Variables Assumed To Be Saved::
! * Unwanted Variables::
! * Unused Arguments::
! * Surprising Interpretations of Code::
! * Aliasing Assumed To Work::
! * Output Assumed To Flush::
! * Large File Unit Numbers::
! * Floating-point precision::
! * Inconsistent Calling Sequences::
! 
! 
! File: g77.info,  Node: Not My Type,  Next: Variables Assumed To Be Zero,  Up: Working Programs
! 
! Not My Type
! -----------
! 
!    A fruitful source of bugs in Fortran source code is use, or mis-use,
! of Fortran's implicit-typing feature, whereby the type of a variable,
! array, or function is determined by the first character of its name.
! 
!    Simple cases of this include statements like `LOGX=9.227', without a
! statement such as `REAL LOGX'.  In this case, `LOGX' is implicitly
! given `INTEGER(KIND=1)' type, with the result of the assignment being
! that it is given the value `9'.
! 
!    More involved cases include a function that is defined starting with
! a statement like `DOUBLE PRECISION FUNCTION IPS(...)'.  Any caller of
! this function that does not also declare `IPS' as type `DOUBLE
! PRECISION' (or, in GNU Fortran, `REAL(KIND=2)') is likely to assume it
! returns `INTEGER', or some other type, leading to invalid results or
! even program crashes.
! 
!    The `-Wimplicit' option might catch failures to properly specify the
! types of variables, arrays, and functions in the code.
! 
!    However, in code that makes heavy use of Fortran's implicit-typing
! facility, this option might produce so many warnings about cases that
! are working, it would be hard to find the one or two that represent
! bugs.  This is why so many experienced Fortran programmers strongly
! recommend widespread use of the `IMPLICIT NONE' statement, despite it
! not being standard FORTRAN 77, to completely turn off implicit typing.
! (`g77' supports `IMPLICIT NONE', as do almost all FORTRAN 77 compilers.)
! 
!    Note that `-Wimplicit' catches only implicit typing of _names_.  It
! does not catch implicit typing of expressions such as `X**(2/3)'.  Such
! expressions can be buggy as well--in fact, `X**(2/3)' is equivalent to
! `X**0', due to the way Fortran expressions are given types and then
! evaluated.  (In this particular case, the programmer probably wanted
! `X**(2./3.)'.)
! 
! 
! File: g77.info,  Node: Variables Assumed To Be Zero,  Next: Variables Assumed To Be Saved,  Prev: Not My Type,  Up: Working Programs
! 
! Variables Assumed To Be Zero
! ----------------------------
! 
!    Many Fortran programs were developed on systems that provided
! automatic initialization of all, or some, variables and arrays to zero.
! As a result, many of these programs depend, sometimes inadvertently, on
! this behavior, though to do so violates the Fortran standards.
! 
!    You can ask `g77' for this behavior by specifying the
! `-finit-local-zero' option when compiling Fortran code.  (You might
! want to specify `-fno-automatic' as well, to avoid code-size inflation
! for non-optimized compilations.)
! 
!    Note that a program that works better when compiled with the
! `-finit-local-zero' option is almost certainly depending on a
! particular system's, or compiler's, tendency to initialize some
! variables to zero.  It might be worthwhile finding such cases and
! fixing them, using techniques such as compiling with the `-O
! -Wuninitialized' options using `g77'.
! 
! 
! File: g77.info,  Node: Variables Assumed To Be Saved,  Next: Unwanted Variables,  Prev: Variables Assumed To Be Zero,  Up: Working Programs
! 
! Variables Assumed To Be Saved
! -----------------------------
! 
!    Many Fortran programs were developed on systems that saved the
! values of all, or some, variables and arrays across procedure calls.
! As a result, many of these programs depend, sometimes inadvertently, on
! being able to assign a value to a variable, perform a `RETURN' to a
! calling procedure, and, upon subsequent invocation, reference the
! previously assigned variable to obtain the value.
! 
!    They expect this despite not using the `SAVE' statement to specify
! that the value in a variable is expected to survive procedure returns
! and calls.  Depending on variables and arrays to retain values across
! procedure calls without using `SAVE' to require it violates the Fortran
! standards.
! 
!    You can ask `g77' to assume `SAVE' is specified for all relevant
! (local) variables and arrays by using the `-fno-automatic' option.
! 
!    Note that a program that works better when compiled with the
! `-fno-automatic' option is almost certainly depending on not having to
! use the `SAVE' statement as required by the Fortran standard.  It might
! be worthwhile finding such cases and fixing them, using techniques such
! as compiling with the `-O -Wuninitialized' options using `g77'.
! 
! 
! File: g77.info,  Node: Unwanted Variables,  Next: Unused Arguments,  Prev: Variables Assumed To Be Saved,  Up: Working Programs
! 
! Unwanted Variables
! ------------------
! 
!    The `-Wunused' option can find bugs involving implicit typing,
! sometimes more easily than using `-Wimplicit' in code that makes heavy
! use of implicit typing.  An unused variable or array might indicate
! that the spelling for its declaration is different from that of its
! intended uses.
! 
!    Other than cases involving typos, unused variables rarely indicate
! actual bugs in a program.  However, investigating such cases thoroughly
! has, on occasion, led to the discovery of code that had not been
! completely written--where the programmer wrote declarations as needed
! for the whole algorithm, wrote some or even most of the code for that
! algorithm, then got distracted and forgot that the job was not complete.
! 
! 
! File: g77.info,  Node: Unused Arguments,  Next: Surprising Interpretations of Code,  Prev: Unwanted Variables,  Up: Working Programs
! 
! Unused Arguments
! ----------------
! 
!    As with unused variables, It is possible that unused arguments to a
! procedure might indicate a bug.  Compile with `-W -Wunused' option to
! catch cases of unused arguments.
! 
!    Note that `-W' also enables warnings regarding overflow of
! floating-point constants under certain circumstances.
! 
! 
! File: g77.info,  Node: Surprising Interpretations of Code,  Next: Aliasing Assumed To Work,  Prev: Unused Arguments,  Up: Working Programs
! 
! Surprising Interpretations of Code
! ----------------------------------
! 
!    The `-Wsurprising' option can help find bugs involving expression
! evaluation or in the way `DO' loops with non-integral iteration
! variables are handled.  Cases found by this option might indicate a
! difference of interpretation between the author of the code involved,
! and a standard-conforming compiler such as `g77'.  Such a difference
! might produce actual bugs.
! 
!    In any case, changing the code to explicitly do what the programmer
! might have expected it to do, so `g77' and other compilers are more
! likely to follow the programmer's expectations, might be worthwhile,
! especially if such changes make the program work better.
! 
! 
! File: g77.info,  Node: Aliasing Assumed To Work,  Next: Output Assumed To Flush,  Prev: Surprising Interpretations of Code,  Up: Working Programs
! 
! Aliasing Assumed To Work
! ------------------------
! 
!    The `-falias-check', `-fargument-alias', `-fargument-noalias', and
! `-fno-argument-noalias-global' options, introduced in version 0.5.20 and
! `g77''s version 2.7.2.2.f.2 of `gcc', were withdrawn as of `g77'
! version 0.5.23 due to their not being supported by `gcc' version 2.8.
! 
!    These options control the assumptions regarding aliasing
! (overlapping) of writes and reads to main memory (core) made by the
! `gcc' back end.
! 
!    The information below still is useful, but applies to only those
! versions of `g77' that support the alias analysis implied by support
! for these options.
! 
!    These options are effective only when compiling with `-O'
! (specifying any level other than `-O0') or with `-falias-check'.
! 
!    The default for Fortran code is `-fargument-noalias-global'.  (The
! default for C code and code written in other C-based languages is
! `-fargument-alias'.  These defaults apply regardless of whether you use
! `g77' or `gcc' to compile your code.)
! 
!    Note that, on some systems, compiling with `-fforce-addr' in effect
! can produce more optimal code when the default aliasing options are in
! effect (and when optimization is enabled).
! 
!    If your program is not working when compiled with optimization, it
! is possible it is violating the Fortran standards (77 and 90) by
! relying on the ability to "safely" modify variables and arrays that are
! aliased, via procedure calls, to other variables and arrays, without
! using `EQUIVALENCE' to explicitly set up this kind of aliasing.
! 
!    (The FORTRAN 77 standard's prohibition of this sort of overlap,
! generally referred to therein as "storage association", appears in
! Sections 15.9.3.6.  This prohibition allows implementations, such as
! `g77', to, for example, implement the passing of procedures and even
! values in `COMMON' via copy operations into local, perhaps more
! efficiently accessed temporaries at entry to a procedure, and, where
! appropriate, via copy operations back out to their original locations
! in memory at exit from that procedure, without having to take into
! consideration the order in which the local copies are updated by the
! code, among other things.)
! 
!    To test this hypothesis, try compiling your program with the
! `-fargument-alias' option, which causes the compiler to revert to
! assumptions essentially the same as made by versions of `g77' prior to
! 0.5.20.
! 
!    If the program works using this option, that strongly suggests that
! the bug is in your program.  Finding and fixing the bug(s) should
! result in a program that is more standard-conforming and that can be
! compiled by `g77' in a way that results in a faster executable.
! 
!    (You might want to try compiling with `-fargument-noalias', a kind
! of half-way point, to see if the problem is limited to aliasing between
! dummy arguments and `COMMON' variables--this option assumes that such
! aliasing is not done, while still allowing aliasing among dummy
! arguments.)
! 
!    An example of aliasing that is invalid according to the standards is
! shown in the following program, which might _not_ produce the expected
! results when executed:
! 
!      I = 1
!      CALL FOO(I, I)
!      PRINT *, I
!      END
!      
!      SUBROUTINE FOO(J, K)
!      J = J + K
!      K = J * K
!      PRINT *, J, K
!      END
! 
!    The above program attempts to use the temporary aliasing of the `J'
! and `K' arguments in `FOO' to effect a pathological behavior--the
! simultaneous changing of the values of _both_ `J' and `K' when either
! one of them is written.
! 
!    The programmer likely expects the program to print these values:
! 
!      2  4
!      4
! 
!    However, since the program is not standard-conforming, an
! implementation's behavior when running it is undefined, because
! subroutine `FOO' modifies at least one of the arguments, and they are
! aliased with each other.  (Even if one of the assignment statements was
! deleted, the program would still violate these rules.  This kind of
! on-the-fly aliasing is permitted by the standard only when none of the
! aliased items are defined, or written, while the aliasing is in effect.)
! 
!    As a practical example, an optimizing compiler might schedule the `J
! =' part of the second line of `FOO' _after_ the reading of `J' and `K'
! for the `J * K' expression, resulting in the following output:
! 
!      2  2
!      2
! 
!    Essentially, compilers are promised (by the standard and, therefore,
! by programmers who write code they claim to be standard-conforming)
! that if they cannot detect aliasing via static analysis of a single
! program unit's `EQUIVALENCE' and `COMMON' statements, no such aliasing
! exists.  In such cases, compilers are free to assume that an assignment
! to one variable will not change the value of another variable, allowing
! it to avoid generating code to re-read the value of the other variable,
! to re-schedule reads and writes, and so on, to produce a faster
! executable.
! 
!    The same promise holds true for arrays (as seen by the called
! procedure)--an element of one dummy array cannot be aliased with, or
! overlap, any element of another dummy array or be in a `COMMON' area
! known to the procedure.
! 
!    (These restrictions apply only when the procedure defines, or writes
! to, one of the aliased variables or arrays.)
! 
!    Unfortunately, there is no way to find _all_ possible cases of
! violations of the prohibitions against aliasing in Fortran code.
! Static analysis is certainly imperfect, as is run-time analysis, since
! neither can catch all violations.  (Static analysis can catch all
! likely violations, and some that might never actually happen, while
! run-time analysis can catch only those violations that actually happen
! during a particular run.  Neither approach can cope with programs
! mixing Fortran code with routines written in other languages, however.)
! 
!    Currently, `g77' provides neither static nor run-time facilities to
! detect any cases of this problem, although other products might.
! Run-time facilities are more likely to be offered by future versions of
! `g77', though patches improving `g77' so that it provides either form
! of detection are welcome.
! 
! 
! File: g77.info,  Node: Output Assumed To Flush,  Next: Large File Unit Numbers,  Prev: Aliasing Assumed To Work,  Up: Working Programs
! 
! Output Assumed To Flush
! -----------------------
! 
!    For several versions prior to 0.5.20, `g77' configured its version
! of the `libf2c' run-time library so that one of its configuration
! macros, `ALWAYS_FLUSH', was defined.
! 
!    This was done as a result of a belief that many programs expected
! output to be flushed to the operating system (under UNIX, via the
! `fflush()' library call) with the result that errors, such as disk
! full, would be immediately flagged via the relevant `ERR=' and
! `IOSTAT=' mechanism.
! 
!    Because of the adverse effects this approach had on the performance
! of many programs, `g77' no longer configures `libf2c' (now named
! `libg2c' in its `g77' incarnation) to always flush output.
! 
!    If your program depends on this behavior, either insert the
! appropriate `CALL FLUSH' statements, or modify the sources to the
! `libg2c', rebuild and reinstall `g77', and relink your programs with
! the modified library.
! 
!    (Ideally, `libg2c' would offer the choice at run-time, so that a
! compile-time option to `g77' or `f2c' could result in generating the
! appropriate calls to flushing or non-flushing library routines.)
! 
!    Some Fortran programs require output (writes) to be flushed to the
! operating system (under UNIX, via the `fflush()' library call) so that
! errors, such as disk full, are immediately flagged via the relevant
! `ERR=' and `IOSTAT=' mechanism, instead of such errors being flagged
! later as subsequent writes occur, forcing the previously written data
! to disk, or when the file is closed.
! 
!    Essentially, the difference can be viewed as synchronous error
! reporting (immediate flagging of errors during writes) versus
! asynchronous, or, more precisely, buffered error reporting (detection
! of errors might be delayed).
! 
!    `libg2c' supports flagging write errors immediately when it is built
! with the `ALWAYS_FLUSH' macro defined.  This results in a `libg2c' that
! runs slower, sometimes quite a bit slower, under certain
! circumstances--for example, accessing files via the networked file
! system NFS--but the effect can be more reliable, robust file I/O.
! 
!    If you know that Fortran programs requiring this level of precision
! of error reporting are to be compiled using the version of `g77' you
! are building, you might wish to modify the `g77' source tree so that
! the version of `libg2c' is built with the `ALWAYS_FLUSH' macro defined,
! enabling this behavior.
! 
!    To do this, find this line in `gcc/libf2c/f2c.h' in your `g77'
! source tree:
! 
!      /* #define ALWAYS_FLUSH */
! 
!    Remove the leading `/* ', so the line begins with `#define', and the
! trailing ` */'.
! 
!    Then build or rebuild `g77' as appropriate.
! 
! 
! File: g77.info,  Node: Large File Unit Numbers,  Next: Floating-point precision,  Prev: Output Assumed To Flush,  Up: Working Programs
! 
! Large File Unit Numbers
! -----------------------
! 
!    If your program crashes at run time with a message including the
! text `illegal unit number', that probably is a message from the
! run-time library, `libg2c'.
! 
!    The message means that your program has attempted to use a file unit
! number that is out of the range accepted by `libg2c'.  Normally, this
! range is 0 through 99, and the high end of the range is controlled by a
! `libg2c' source-file macro named `MXUNIT'.
! 
!    If you can easily change your program to use unit numbers in the
! range 0 through 99, you should do so.
! 
!    As distributed, whether as part of `f2c' or `g77', `libf2c' accepts
! file unit numbers only in the range 0 through 99.  For example, a
! statement such as `WRITE (UNIT=100)' causes a run-time crash in
! `libf2c', because the unit number, 100, is out of range.
! 
!    If you know that Fortran programs at your installation require the
! use of unit numbers higher than 99, you can change the value of the
! `MXUNIT' macro, which represents the maximum unit number, to an
! appropriately higher value.
! 
!    To do this, edit the file `gcc/libf2c/libI77/fio.h' in your `g77'
! source tree, changing the following line:
! 
!      #define MXUNIT 100
! 
!    Change the line so that the value of `MXUNIT' is defined to be at
! least one _greater_ than the maximum unit number used by the Fortran
! programs on your system.
! 
!    (For example, a program that does `WRITE (UNIT=255)' would require
! `MXUNIT' set to at least 256 to avoid crashing.)
! 
!    Then build or rebuild `g77' as appropriate.
! 
!    _Note:_ Changing this macro has _no_ effect on other limits your
! system might place on the number of files open at the same time.  That
! is, the macro might allow a program to do `WRITE (UNIT=100)', but the
! library and operating system underlying `libf2c' might disallow it if
! many other files have already been opened (via `OPEN' or implicitly via
! `READ', `WRITE', and so on).  Information on how to increase these
! other limits should be found in your system's documentation.
! 
! 
! File: g77.info,  Node: Floating-point precision,  Next: Inconsistent Calling Sequences,  Prev: Large File Unit Numbers,  Up: Working Programs
! 
! Floating-point precision
! ------------------------
! 
!    If your program depends on exact IEEE 754 floating-point handling it
! may help on some systems--specifically x86 or m68k hardware--to use the
! `-ffloat-store' option or to reset the precision flag on the
! floating-point unit.  *Note Optimize Options::.
! 
!    However, it might be better simply to put the FPU into double
! precision mode and not take the performance hit of `-ffloat-store'.  On
! x86 and m68k GNU systems you can do this with a technique similar to
! that for turning on floating-point exceptions (*note Floating-point
! Exception Handling::).  The control word could be set to double
! precision by some code like this one:
!      #include <fpu_control.h>
!      {
!        fpu_control_t cw = (_FPU_DEFAULT & ~_FPU_EXTENDED) | _FPU_DOUBLE;
!        _FPU_SETCW(cw);
!      }
!    (It is not clear whether this has any effect on the operation of the
! GNU maths library, but we have no evidence of it causing trouble.)
! 
!    Some targets (such as the Alpha) may need special options for full
! IEEE conformance.  *Note Hardware Models and Configurations:
! (gcc)Submodel Options.
! 
! 
! File: g77.info,  Node: Inconsistent Calling Sequences,  Prev: Floating-point precision,  Up: Working Programs
! 
! Inconsistent Calling Sequences
! ------------------------------
! 
!    Code containing inconsistent calling sequences in the same file is
! normally rejected--see *Note GLOBALS::.  (Use, say, `ftnchek' to ensure
! consistency across source files.  *Note Generating Skeletons and
! Prototypes with `f2c': f2c Skeletons and Prototypes.)
! 
!    Mysterious errors, which may appear to be code generation problems,
! can appear specifically on the x86 architecture with some such
! inconsistencies.  On x86 hardware, floating-point return values of
! functions are placed on the floating-point unit's register stack, not
! the normal stack.  Thus calling a `REAL' or `DOUBLE PRECISION'
! `FUNCTION' as some other sort of procedure, or vice versa, scrambles
! the floating-point stack.  This may break unrelated code executed
! later.  Similarly if, say, external C routines are written incorrectly.
! 
! 
! File: g77.info,  Node: Overly Convenient Options,  Next: Faster Programs,  Prev: Working Programs,  Up: Collected Fortran Wisdom
! 
! Overly Convenient Command-line Options
! ======================================
! 
!    These options should be used only as a quick-and-dirty way to
! determine how well your program will run under different compilation
! models without having to change the source.  Some are more problematic
! than others, depending on how portable and maintainable you want the
! program to be (and, of course, whether you are allowed to change it at
! all is crucial).
! 
!    You should not continue to use these command-line options to compile
! a given program, but rather should make changes to the source code:
! 
! `-finit-local-zero'
!      (This option specifies that any uninitialized local variables and
!      arrays have default initialization to binary zeros.)
! 
!      Many other compilers do this automatically, which means lots of
!      Fortran code developed with those compilers depends on it.
! 
!      It is safer (and probably would produce a faster program) to find
!      the variables and arrays that need such initialization and provide
!      it explicitly via `DATA', so that `-finit-local-zero' is not
!      needed.
! 
!      Consider using `-Wuninitialized' (which requires `-O') to find
!      likely candidates, but do not specify `-finit-local-zero' or
!      `-fno-automatic', or this technique won't work.
! 
! `-fno-automatic'
!      (This option specifies that all local variables and arrays are to
!      be treated as if they were named in `SAVE' statements.)
! 
!      Many other compilers do this automatically, which means lots of
!      Fortran code developed with those compilers depends on it.
! 
!      The effect of this is that all non-automatic variables and arrays
!      are made static, that is, not placed on the stack or in heap
!      storage.  This might cause a buggy program to appear to work
!      better.  If so, rather than relying on this command-line option
!      (and hoping all compilers provide the equivalent one), add `SAVE'
!      statements to some or all program unit sources, as appropriate.
!      Consider using `-Wuninitialized' (which requires `-O') to find
!      likely candidates, but do not specify `-finit-local-zero' or
!      `-fno-automatic', or this technique won't work.
! 
!      The default is `-fautomatic', which tells `g77' to try and put
!      variables and arrays on the stack (or in fast registers) where
!      possible and reasonable.  This tends to make programs faster.
! 
!      _Note:_ Automatic variables and arrays are not affected by this
!      option.  These are variables and arrays that are _necessarily_
!      automatic, either due to explicit statements, or due to the way
!      they are declared.  Examples include local variables and arrays
!      not given the `SAVE' attribute in procedures declared `RECURSIVE',
!      and local arrays declared with non-constant bounds (automatic
!      arrays).  Currently, `g77' supports only automatic arrays, not
!      `RECURSIVE' procedures or other means of explicitly specifying
!      that variables or arrays are automatic.
! 
! `-fGROUP-intrinsics-hide'
!      Change the source code to use `EXTERNAL' for any external procedure
!      that might be the name of an intrinsic.  It is easy to find these
!      using `-fGROUP-intrinsics-disable'.
! 
! 
! File: g77.info,  Node: Faster Programs,  Prev: Overly Convenient Options,  Up: Collected Fortran Wisdom
! 
! Faster Programs
! ===============
! 
!    Aside from the usual `gcc' options, such as `-O', `-ffast-math', and
! so on, consider trying some of the following approaches to speed up
! your program (once you get it working).
! 
! * Menu:
! 
! * Aligned Data::
! * Prefer Automatic Uninitialized Variables::
! * Avoid f2c Compatibility::
! * Use Submodel Options::
! 
! 
! File: g77.info,  Node: Aligned Data,  Next: Prefer Automatic Uninitialized Variables,  Up: Faster Programs
! 
! Aligned Data
! ------------
! 
!    On some systems, such as those with Pentium Pro CPUs, programs that
! make heavy use of `REAL(KIND=2)' (`DOUBLE PRECISION') might run much
! slower than possible due to the compiler not aligning these 64-bit
! values to 64-bit boundaries in memory.  (The effect also is present,
! though to a lesser extent, on the 586 (Pentium) architecture.)
! 
!    The Intel x86 architecture generally ensures that these programs will
! work on all its implementations, but particular implementations (such
! as Pentium Pro) perform better with more strict alignment.  (Such
! behavior isn't unique to the Intel x86 architecture.)  Other
! architectures might _demand_ 64-bit alignment of 64-bit data.
! 
!    There are a variety of approaches to use to address this problem:
! 
!    * Order your `COMMON' and `EQUIVALENCE' areas such that the
!      variables and arrays with the widest alignment guidelines come
!      first.
! 
!      For example, on most systems, this would mean placing
!      `COMPLEX(KIND=2)', `REAL(KIND=2)', and `INTEGER(KIND=2)' entities
!      first, followed by `REAL(KIND=1)', `INTEGER(KIND=1)', and
!      `LOGICAL(KIND=1)' entities, then `INTEGER(KIND=6)' entities, and
!      finally `CHARACTER' and `INTEGER(KIND=3)' entities.
! 
!      The reason to use such placement is it makes it more likely that
!      your data will be aligned properly, without requiring you to do
!      detailed analysis of each aggregate (`COMMON' and `EQUIVALENCE')
!      area.
! 
!      Specifically, on systems where the above guidelines are
!      appropriate, placing `CHARACTER' entities before `REAL(KIND=2)'
!      entities can work just as well, but only if the number of bytes
!      occupied by the `CHARACTER' entities is divisible by the
!      recommended alignment for `REAL(KIND=2)'.
! 
!      By ordering the placement of entities in aggregate areas according
!      to the simple guidelines above, you avoid having to carefully
!      count the number of bytes occupied by each entity to determine
!      whether the actual alignment of each subsequent entity meets the
!      alignment guidelines for the type of that entity.
! 
!      If you don't ensure correct alignment of `COMMON' elements, the
!      compiler may be forced by some systems to violate the Fortran
!      semantics by adding padding to get `DOUBLE PRECISION' data
!      properly aligned.  If the unfortunate practice is employed of
!      overlaying different types of data in the `COMMON' block, the
!      different variants of this block may become misaligned with
!      respect to each other.  Even if your platform doesn't require
!      strict alignment, `COMMON' should be laid out as above for
!      portability.  (Unfortunately the FORTRAN 77 standard didn't
!      anticipate this possible requirement, which is
!      compiler-independent on a given platform.)
! 
!    * Use the (x86-specific) `-malign-double' option when compiling
!      programs for the Pentium and Pentium Pro architectures (called 586
!      and 686 in the `gcc' configuration subsystem).  The warning about
!      this in the `gcc' manual isn't generally relevant to Fortran, but
!      using it will force `COMMON' to be padded if necessary to align
!      `DOUBLE PRECISION' data.
! 
!      When `DOUBLE PRECISION' data is forcibly aligned in `COMMON' by
!      `g77' due to specifying `-malign-double', `g77' issues a warning
!      about the need to insert padding.
! 
!      In this case, each and every program unit that uses the same
!      `COMMON' area must specify the same layout of variables and their
!      types for that area and be compiled with `-malign-double' as well.
!      `g77' will issue warnings in each case, but as long as every
!      program unit using that area is compiled with the same warnings,
!      the resulting object files should work when linked together unless
!      the program makes additional assumptions about `COMMON' area
!      layouts that are outside the scope of the FORTRAN 77 standard, or
!      uses `EQUIVALENCE' or different layouts in ways that assume no
!      padding is ever inserted by the compiler.
! 
!    * Ensure that `crt0.o' or `crt1.o' on your system guarantees a 64-bit
!      aligned stack for `main()'.  The recent one from GNU (`glibc2')
!      will do this on x86 systems, but we don't know of any other x86
!      setups where it will be right.  Read your system's documentation
!      to determine if it is appropriate to upgrade to a more recent
!      version to obtain the optimal alignment.
! 
!    Progress is being made on making this work "out of the box" on
! future versions of `g77', `gcc', and some of the relevant operating
! systems (such as GNU/Linux).
! 
!    A package that tests the degree to which a Fortran compiler (such as
! `g77') aligns 64-bit floating-point variables and arrays is available
! at `ftp://alpha.gnu.org/gnu/g77/align/'.
! 
! 
! File: g77.info,  Node: Prefer Automatic Uninitialized Variables,  Next: Avoid f2c Compatibility,  Prev: Aligned Data,  Up: Faster Programs
! 
! Prefer Automatic Uninitialized Variables
! ----------------------------------------
! 
!    If you're using `-fno-automatic' already, you probably should change
! your code to allow compilation with `-fautomatic' (the default), to
! allow the program to run faster.
! 
!    Similarly, you should be able to use `-fno-init-local-zero' (the
! default) instead of `-finit-local-zero'.  This is because it is rare
! that every variable affected by these options in a given program
! actually needs to be so affected.
! 
!    For example, `-fno-automatic', which effectively `SAVE's every local
! non-automatic variable and array, affects even things like `DO'
! iteration variables, which rarely need to be `SAVE'd, and this often
! reduces run-time performances.  Similarly, `-fno-init-local-zero'
! forces such variables to be initialized to zero--when `SAVE'd (such as
! when `-fno-automatic'), this by itself generally affects only startup
! time for a program, but when not `SAVE'd, it can slow down the
! procedure every time it is called.
! 
!    *Note Overly Convenient Command-Line Options: Overly Convenient
! Options, for information on the `-fno-automatic' and
! `-finit-local-zero' options and how to convert their use into selective
! changes in your own code.
! 
! 
! File: g77.info,  Node: Avoid f2c Compatibility,  Next: Use Submodel Options,  Prev: Prefer Automatic Uninitialized Variables,  Up: Faster Programs
! 
! Avoid f2c Compatibility
! -----------------------
! 
!    If you aren't linking with any code compiled using `f2c', try using
! the `-fno-f2c' option when compiling _all_ the code in your program.
! (Note that `libf2c' is _not_ an example of code that is compiled using
! `f2c'--it is compiled by a C compiler, typically `gcc'.)
! 
! 
! File: g77.info,  Node: Use Submodel Options,  Prev: Avoid f2c Compatibility,  Up: Faster Programs
! 
! Use Submodel Options
! --------------------
! 
!    Using an appropriate `-m' option to generate specific code for your
! CPU may be worthwhile, though it may mean the executable won't run on
! other versions of the CPU that don't support the same instruction set.
! *Note Hardware Models and Configurations: (gcc)Submodel Options.  For
! instance on an x86 system the compiler might have been built--as shown
! by `g77 -v'--for the target `i386-pc-linux-gnu', i.e. an `i386' CPU.
! In that case to generate code best optimized for a Pentium you could
! use the option `-march=pentium'.
! 
!    For recent CPUs that don't have explicit support in the released
! version of `gcc', it _might_ still be possible to get improvements with
! certain `-m' options.
! 
!    `-fomit-frame-pointer' can help performance on x86 systems and
! others.  It will, however, inhibit debugging on the systems on which it
! is not turned on anyway by `-O'.
! 
! 
! File: g77.info,  Node: Trouble,  Next: Open Questions,  Prev: Collected Fortran Wisdom,  Up: Top
! 
! Known Causes of Trouble with GNU Fortran
! ****************************************
! 
!    This section describes known problems that affect users of GNU
! Fortran.  Most of these are not GNU Fortran bugs per se--if they were,
! we would fix them.  But the result for a user might be like the result
! of a bug.
! 
!    Some of these problems are due to bugs in other software, some are
! missing features that are too much work to add, and some are places
! where people's opinions differ as to what is best.
! 
!    To find out about major bugs discovered in the current release and
! possible workarounds for them, see `ftp://alpha.gnu.org/g77.plan'.
! 
!    (Note that some of this portion of the manual is lifted directly
! from the `gcc' manual, with minor modifications to tailor it to users
! of `g77'.  Anytime a bug seems to have more to do with the `gcc'
! portion of `g77', see *Note Known Causes of Trouble with GCC:
! (gcc)Trouble.)
! 
! * Menu:
! 
! * But-bugs::         Bugs really in other programs or elsewhere.
! * Known Bugs::       Bugs known to be in this version of `g77'.
! * Missing Features:: Features we already know we want to add later.
! * Disappointments::  Regrettable things we can't change.
! * Non-bugs::         Things we think are right, but some others disagree.
! * Warnings and Errors::  Which problems in your code get warnings,
!                         and which get errors.
! 
! 
! File: g77.info,  Node: But-bugs,  Next: Known Bugs,  Up: Trouble
! 
! Bugs Not In GNU Fortran
! =======================
! 
!    These are bugs to which the maintainers often have to reply, "but
! that isn't a bug in `g77'...".  Some of these already are fixed in new
! versions of other software; some still need to be fixed; some are
! problems with how `g77' is installed or is being used; some are the
! result of bad hardware that causes software to misbehave in sometimes
! bizarre ways; some just cannot be addressed at this time until more is
! known about the problem.
! 
!    Please don't re-report these bugs to the `g77' maintainers--if you
! must remind someone how important it is to you that the problem be
! fixed, talk to the people responsible for the other products identified
! below, but preferably only after you've tried the latest versions of
! those products.  The `g77' maintainers have their hands full working on
! just fixing and improving `g77', without serving as a clearinghouse for
! all bugs that happen to affect `g77' users.
! 
!    *Note Collected Fortran Wisdom::, for information on behavior of
! Fortran programs, and the programs that compile them, that might be
! _thought_ to indicate bugs.
! 
! * Menu:
! 
! * Signal 11 and Friends::  Strange behavior by any software.
! * Cannot Link Fortran Programs::  Unresolved references.
! * Large Common Blocks::    Problems on older GNU/Linux systems.
! * Debugger Problems::      When the debugger crashes.
! * NeXTStep Problems::      Misbehaving executables.
! * Stack Overflow::         More misbehaving executables.
! * Nothing Happens::        Less behaving executables.
! * Strange Behavior at Run Time::  Executables misbehaving due to
!                             bugs in your program.
! * Floating-point Errors::  The results look wrong, but....
! 
! 
! File: g77.info,  Node: Signal 11 and Friends,  Next: Cannot Link Fortran Programs,  Up: But-bugs
! 
! Signal 11 and Friends
! ---------------------
! 
!    A whole variety of strange behaviors can occur when the software, or
! the way you are using the software, stresses the hardware in a way that
! triggers hardware bugs.  This might seem hard to believe, but it
! happens frequently enough that there exist documents explaining in
! detail what the various causes of the problems are, what typical
! symptoms look like, and so on.
! 
!    Generally these problems are referred to in this document as "signal
! 11" crashes, because the Linux kernel, running on the most popular
! hardware (the Intel x86 line), often stresses the hardware more than
! other popular operating systems.  When hardware problems do occur under
! GNU/Linux on x86 systems, these often manifest themselves as "signal 11"
! problems, as illustrated by the following diagnostic:
! 
!      sh# g77 myprog.f
!      gcc: Internal compiler error: program f771 got fatal signal 11
!      sh#
! 
!    It is _very_ important to remember that the above message is _not_
! the only one that indicates a hardware problem, nor does it always
! indicate a hardware problem.
! 
!    In particular, on systems other than those running the Linux kernel,
! the message might appear somewhat or very different, as it will if the
! error manifests itself while running a program other than the `g77'
! compiler.  For example, it will appear somewhat different when running
! your program, when running Emacs, and so on.
! 
!    How to cope with such problems is well beyond the scope of this
! manual.
! 
!    However, users of Linux-based systems (such as GNU/Linux) should
! review `http://www.bitwizard.nl/sig11/', a source of detailed
! information on diagnosing hardware problems, by recognizing their
! common symptoms.
! 
!    Users of other operating systems and hardware might find this
! reference useful as well.  If you know of similar material for another
! hardware/software combination, please let us know so we can consider
! including a reference to it in future versions of this manual.
! 
! 
! File: g77.info,  Node: Cannot Link Fortran Programs,  Next: Large Common Blocks,  Prev: Signal 11 and Friends,  Up: But-bugs
! 
! Cannot Link Fortran Programs
! ----------------------------
! 
!    On some systems, perhaps just those with out-of-date (shared?)
! libraries, unresolved-reference errors happen when linking
! `g77'-compiled programs (which should be done using `g77').
! 
!    If this happens to you, try appending `-lc' to the command you use
! to link the program, e.g. `g77 foo.f -lc'.  `g77' already specifies
! `-lg2c -lm' when it calls the linker, but it cannot also specify `-lc'
! because not all systems have a file named `libc.a'.
! 
!    It is unclear at this point whether there are legitimately installed
! systems where `-lg2c -lm' is insufficient to resolve code produced by
! `g77'.
! 
!    If your program doesn't link due to unresolved references to names
! like `_main', make sure you're using the `g77' command to do the link,
! since this command ensures that the necessary libraries are loaded by
! specifying `-lg2c -lm' when it invokes the `gcc' command to do the
! actual link.  (Use the `-v' option to discover more about what actually
! happens when you use the `g77' and `gcc' commands.)
! 
!    Also, try specifying `-lc' as the last item on the `g77' command
! line, in case that helps.
! 
! 
! File: g77.info,  Node: Large Common Blocks,  Next: Debugger Problems,  Prev: Cannot Link Fortran Programs,  Up: But-bugs
! 
! Large Common Blocks
! -------------------
! 
!    On some older GNU/Linux systems, programs with common blocks larger
! than 16MB cannot be linked without some kind of error message being
! produced.
! 
!    This is a bug in older versions of `ld', fixed in more recent
! versions of `binutils', such as version 2.6.
! 
! 
! File: g77.info,  Node: Debugger Problems,  Next: NeXTStep Problems,  Prev: Large Common Blocks,  Up: But-bugs
! 
! Debugger Problems
! -----------------
! 
!    There are some known problems when using `gdb' on code compiled by
! `g77'.  Inadequate investigation as of the release of 0.5.16 results in
! not knowing which products are the culprit, but `gdb-4.14' definitely
! crashes when, for example, an attempt is made to print the contents of
! a `COMPLEX(KIND=2)' dummy array, on at least some GNU/Linux machines,
! plus some others.  Attempts to access assumed-size arrays are also
! known to crash recent versions of `gdb'.  (`gdb''s Fortran support was
! done for a different compiler and isn't properly compatible with `g77'.)
! 
! 
! File: g77.info,  Node: NeXTStep Problems,  Next: Stack Overflow,  Prev: Debugger Problems,  Up: But-bugs
! 
! NeXTStep Problems
! -----------------
! 
!    Developers of Fortran code on NeXTStep (all architectures) have to
! watch out for the following problem when writing programs with large,
! statically allocated (i.e. non-stack based) data structures (common
! blocks, saved arrays).
! 
!    Due to the way the native loader (`/bin/ld') lays out data
! structures in virtual memory, it is very easy to create an executable
! wherein the `__DATA' segment overlaps (has addresses in common) with
! the `UNIX STACK' segment.
! 
!    This leads to all sorts of trouble, from the executable simply not
! executing, to bus errors.  The NeXTStep command line tool `ebadexec'
! points to the problem as follows:
! 
!      % /bin/ebadexec a.out
!      /bin/ebadexec: __LINKEDIT segment (truncated address = 0x3de000
!      rounded size = 0x2a000) of executable file: a.out overlaps with UNIX
!      STACK segment (truncated address = 0x400000 rounded size =
!      0x3c00000) of executable file: a.out
! 
!    (In the above case, it is the `__LINKEDIT' segment that overlaps the
! stack segment.)
! 
!    This can be cured by assigning the `__DATA' segment (virtual)
! addresses beyond the stack segment.  A conservative estimate for this
! is from address 6000000 (hexadecimal) onwards--this has always worked
! for me [Toon Moene]:
! 
!      % g77 -segaddr __DATA 6000000 test.f
!      % ebadexec a.out
!      ebadexec: file: a.out appears to be executable
!      %
! 
!    Browsing through `gcc/gcc/f/Makefile.in', you will find that the
! `f771' program itself also has to be linked with these flags--it has
! large statically allocated data structures.  (Version 0.5.18 reduces
! this somewhat, but probably not enough.)
! 
!    (The above item was contributed by Toon Moene
! (<toon@moene.indiv.nluug.nl>).)
! 
! 
! File: g77.info,  Node: Stack Overflow,  Next: Nothing Happens,  Prev: NeXTStep Problems,  Up: But-bugs
! 
! Stack Overflow
! --------------
! 
!    `g77' code might fail at runtime (probably with a "segmentation
! violation") due to overflowing the stack.  This happens most often on
! systems with an environment that provides substantially more heap space
! (for use when arbitrarily allocating and freeing memory) than stack
! space.
! 
!    Often this can be cured by increasing or removing your shell's limit
! on stack usage, typically using `limit stacksize' (in `csh' and
! derivatives) or `ulimit -s' (in `sh' and derivatives).
! 
!    Increasing the allowed stack size might, however, require changing
! some operating system or system configuration parameters.
! 
!    You might be able to work around the problem by compiling with the
! `-fno-automatic' option to reduce stack usage, probably at the expense
! of speed.
! 
!    `g77', on most machines, puts many variables and arrays on the stack
! where possible, and can be configured (by changing
! `FFECOM_sizeMAXSTACKITEM' in `gcc/gcc/f/com.c') to force smaller-sized
! entities into static storage (saving on stack space) or permit
! larger-sized entities to be put on the stack (which can improve
! run-time performance, as it presents more opportunities for the GBE to
! optimize the generated code).
! 
!    _Note:_ Putting more variables and arrays on the stack might cause
! problems due to system-dependent limits on stack size.  Also, the value
! of `FFECOM_sizeMAXSTACKITEM' has no effect on automatic variables and
! arrays.  *Note But-bugs::, for more information.  _Note:_ While
! `libg2c' places a limit on the range of Fortran file-unit numbers, the
! underlying library and operating system might impose different kinds of
! limits.  For example, some systems limit the number of files
! simultaneously open by a running program.  Information on how to
! increase these limits should be found in your system's documentation.
! 
!    However, if your program uses large automatic arrays (for example,
! has declarations like `REAL A(N)' where `A' is a local array and `N' is
! a dummy or `COMMON' variable that can have a large value), neither use
! of `-fno-automatic', nor changing the cut-off point for `g77' for using
! the stack, will solve the problem by changing the placement of these
! large arrays, as they are _necessarily_ automatic.
! 
!    `g77' currently provides no means to specify that automatic arrays
! are to be allocated on the heap instead of the stack.  So, other than
! increasing the stack size, your best bet is to change your source code
! to avoid large automatic arrays.  Methods for doing this currently are
! outside the scope of this document.
! 
!    (_Note:_ If your system puts stack and heap space in the same memory
! area, such that they are effectively combined, then a stack overflow
! probably indicates a program that is either simply too large for the
! system, or buggy.)
! 
! 
! File: g77.info,  Node: Nothing Happens,  Next: Strange Behavior at Run Time,  Prev: Stack Overflow,  Up: But-bugs
! 
! Nothing Happens
! ---------------
! 
!    It is occasionally reported that a "simple" program, such as a
! "Hello, World!" program, does nothing when it is run, even though the
! compiler reported no errors, despite the program containing nothing
! other than a simple `PRINT' statement.
! 
!    This most often happens because the program has been compiled and
! linked on a UNIX system and named `test', though other names can lead
! to similarly unexpected run-time behavior on various systems.
! 
!    Essentially this problem boils down to giving your program a name
! that is already known to the shell you are using to identify some other
! program, which the shell continues to execute instead of your program
! when you invoke it via, for example:
! 
!      sh# test
!      sh#
! 
!    Under UNIX and many other system, a simple command name invokes a
! searching mechanism that might well not choose the program located in
! the current working directory if there is another alternative (such as
! the `test' command commonly installed on UNIX systems).
! 
!    The reliable way to invoke a program you just linked in the current
! directory under UNIX is to specify it using an explicit pathname, as in:
! 
!      sh# ./test
!       Hello, World!
!      sh#
! 
!    Users who encounter this problem should take the time to read up on
! how their shell searches for commands, how to set their search path,
! and so on.  The relevant UNIX commands to learn about include `man',
! `info' (on GNU systems), `setenv' (or `set' and `env'), `which', and
! `find'.
! 
! 
! File: g77.info,  Node: Strange Behavior at Run Time,  Next: Floating-point Errors,  Prev: Nothing Happens,  Up: But-bugs
! 
! Strange Behavior at Run Time
! ----------------------------
! 
!    `g77' code might fail at runtime with "segmentation violation", "bus
! error", or even something as subtle as a procedure call overwriting a
! variable or array element that it is not supposed to touch.
! 
!    These can be symptoms of a wide variety of actual bugs that occurred
! earlier during the program's run, but manifested themselves as
! _visible_ problems some time later.
! 
!    Overflowing the bounds of an array--usually by writing beyond the
! end of it--is one of two kinds of bug that often occurs in Fortran code.
! (Compile your code with the `-fbounds-check' option to catch many of
! these kinds of errors at program run time.)
! 
!    The other kind of bug is a mismatch between the actual arguments
! passed to a procedure and the dummy arguments as declared by that
! procedure.
! 
!    Both of these kinds of bugs, and some others as well, can be
! difficult to track down, because the bug can change its behavior, or
! even appear to not occur, when using a debugger.
! 
!    That is, these bugs can be quite sensitive to data, including data
! representing the placement of other data in memory (that is, pointers,
! such as the placement of stack frames in memory).
! 
!    `g77' now offers the ability to catch and report some of these
! problems at compile, link, or run time, such as by generating code to
! detect references to beyond the bounds of most arrays (except
! assumed-size arrays), and checking for agreement between calling and
! called procedures.  Future improvements are likely to be made in the
! procedure-mismatch area, at least.
! 
!    In the meantime, finding and fixing the programming bugs that lead
! to these behaviors is, ultimately, the user's responsibility, as
! difficult as that task can sometimes be.
! 
!    One runtime problem that has been observed might have a simple
! solution.  If a formatted `WRITE' produces an endless stream of spaces,
! check that your program is linked against the correct version of the C
! library.  The configuration process takes care to account for your
! system's normal `libc' not being ANSI-standard, which will otherwise
! cause this behavior.  If your system's default library is ANSI-standard
! and you subsequently link against a non-ANSI one, there might be
! problems such as this one.
! 
!    Specifically, on Solaris2 systems, avoid picking up the `BSD'
! library from `/usr/ucblib'.
! 
! 
! File: g77.info,  Node: Floating-point Errors,  Prev: Strange Behavior at Run Time,  Up: But-bugs
! 
! Floating-point Errors
! ---------------------
! 
!    Some programs appear to produce inconsistent floating-point results
! compiled by `g77' versus by other compilers.
! 
!    Often the reason for this behavior is the fact that floating-point
! values are represented on almost all Fortran systems by
! _approximations_, and these approximations are inexact even for
! apparently simple values like 0.1, 0.2, 0.3, 0.4, 0.6, 0.7, 0.8, 0.9,
! 1.1, and so on.  Most Fortran systems, including all current ports of
! `g77', use binary arithmetic to represent these approximations.
! 
!    Therefore, the exact value of any floating-point approximation as
! manipulated by `g77'-compiled code is representable by adding some
! combination of the values 1.0, 0.5, 0.25, 0.125, and so on (just keep
! dividing by two) through the precision of the fraction (typically
! around 23 bits for `REAL(KIND=1)', 52 for `REAL(KIND=2)'), then
! multiplying the sum by a integral power of two (in Fortran, by `2**N')
! that typically is between -127 and +128 for `REAL(KIND=1)' and -1023
! and +1024 for `REAL(KIND=2)', then multiplying by -1 if the number is
! negative.
! 
!    So, a value like 0.2 is exactly represented in decimal--since it is
! a fraction, `2/10', with a denominator that is compatible with the base
! of the number system (base 10).  However, `2/10' cannot be represented
! by any finite number of sums of any of 1.0, 0.5, 0.25, and so on, so
! 0.2 cannot be exactly represented in binary notation.
! 
!    (On the other hand, decimal notation can represent any binary number
! in a finite number of digits.  Decimal notation cannot do so with
! ternary, or base-3, notation, which would represent floating-point
! numbers as sums of any of `1/1', `1/3', `1/9', and so on.  After all,
! no finite number of decimal digits can exactly represent `1/3'.
! Fortunately, few systems use ternary notation.)
! 
!    Moreover, differences in the way run-time I/O libraries convert
! between these approximations and the decimal representation often used
! by programmers and the programs they write can result in apparent
! differences between results that do not actually exist, or exist to
! such a small degree that they usually are not worth worrying about.
! 
!    For example, consider the following program:
! 
!      PRINT *, 0.2
!      END
! 
!    When compiled by `g77', the above program might output `0.20000003',
! while another compiler might produce a executable that outputs `0.2'.
! 
!    This particular difference is due to the fact that, currently,
! conversion of floating-point values by the `libg2c' library, used by
! `g77', handles only double-precision values.
! 
!    Since `0.2' in the program is a single-precision value, it is
! converted to double precision (still in binary notation) before being
! converted back to decimal.  The conversion to binary appends _binary_
! zero digits to the original value--which, again, is an inexact
! approximation of 0.2--resulting in an approximation that is much less
! exact than is connoted by the use of double precision.
! 
!    (The appending of binary zero digits has essentially the same effect
! as taking a particular decimal approximation of `1/3', such as
! `0.3333333', and appending decimal zeros to it, producing
! `0.33333330000000000'.  Treating the resulting decimal approximation as
! if it really had 18 or so digits of valid precision would make it seem
! a very poor approximation of `1/3'.)
! 
!    As a result of converting the single-precision approximation to
! double precision by appending binary zeros, the conversion of the
! resulting double-precision value to decimal produces what looks like an
! incorrect result, when in fact the result is _inexact_, and is probably
! no less inaccurate or imprecise an approximation of 0.2 than is
! produced by other compilers that happen to output the converted value
! as "exactly" `0.2'.  (Some compilers behave in a way that can make them
! appear to retain more accuracy across a conversion of a single-precision
! constant to double precision.  *Note Context-Sensitive Constants::, to
! see why this practice is illusory and even dangerous.)
! 
!    Note that a more exact approximation of the constant is computed
! when the program is changed to specify a double-precision constant:
! 
!      PRINT *, 0.2D0
!      END
! 
!    Future versions of `g77' and/or `libg2c' might convert
! single-precision values directly to decimal, instead of converting them
! to double precision first.  This would tend to result in output that is
! more consistent with that produced by some other Fortran
! implementations.
! 
!    A useful source of information on floating-point computation is David
! Goldberg, `What Every Computer Scientist Should Know About
! Floating-Point Arithmetic', Computing Surveys, 23, March 1991, pp.
! 5-48.  An online version is available at `http://docs.sun.com/', and
! there is a supplemented version, in PostScript form, at
! `http://www.validgh.com/goldberg/paper.ps'.
! 
!    Information related to the IEEE 754 floating-point standard by a
! leading light can be found at
! `http://http.cs.berkeley.edu/%7Ewkahan/ieee754status/'; see also slides
! from the short course referenced from
! `http://http.cs.berkeley.edu/%7Efateman/'.
! `http://www.linuxsupportline.com/%7Ebillm/' has a brief guide to IEEE
! 754, a somewhat x86-GNU/Linux-specific FAQ, and library code for
! GNU/Linux x86 systems.
! 
!    The supplement to the PostScript-formatted Goldberg document,
! referenced above, is available in HTML format.  See `Differences Among
! IEEE 754 Implementations' by Doug Priest, available online at
! `http://www.validgh.com/goldberg/addendum.html'.  This document
! explores some of the issues surrounding computing of extended (80-bit)
! results on processors such as the x86, especially when those results
! are arbitrarily truncated to 32-bit or 64-bit values by the compiler as
! "spills".
! 
!    (_Note:_ `g77' specifically, and `gcc' generally, does arbitrarily
! truncate 80-bit results during spills as of this writing.  It is not
! yet clear whether a future version of the GNU compiler suite will offer
! 80-bit spills as an option, or perhaps even as the default behavior.)
! 
!    The GNU C library provides routines for controlling the FPU, and
! other documentation about this.
! 
!    *Note Floating-point precision::, regarding IEEE 754 conformance.
! 
! 
! File: g77.info,  Node: Known Bugs,  Next: Missing Features,  Prev: But-bugs,  Up: Trouble
! 
! Known Bugs In GNU Fortran
! =========================
! 
!    This section identifies bugs that `g77' _users_ might run into in
! the GCC-3.3 version of `g77'.  This includes bugs that are actually in
! the `gcc' back end (GBE) or in `libf2c', because those sets of code are
! at least somewhat under the control of (and necessarily intertwined
! with) `g77', so it isn't worth separating them out.
! 
!    For information on bugs in _other_ versions of `g77', see *Note News
! About GNU Fortran: News.  There, lists of bugs fixed in various
! versions of `g77' can help determine what bugs existed in prior
! versions.
! 
!    An online, "live" version of this document (derived directly from
! the mainline, development version of `g77' within `gcc') is available
! via `http://gcc.gnu.org/onlinedocs/g77/Trouble.html'.  Follow the
! "Known Bugs" link.
! 
!    The following information was last updated on 2002-02-01:
! 
!    * `g77' fails to warn about use of a "live" iterative-DO variable as
!      an implied-DO variable in a `WRITE' or `PRINT' statement (although
!      it does warn about this in a `READ' statement).
! 
!    * Something about `g77''s straightforward handling of label
!      references and definitions sometimes prevents the GBE from
!      unrolling loops.  Until this is solved, try inserting or removing
!      `CONTINUE' statements as the terminal statement, using the `END DO'
!      form instead, and so on.
! 
!    * Some confusion in diagnostics concerning failing `INCLUDE'
!      statements from within `INCLUDE''d or `#include''d files.
! 
!    * `g77' assumes that `INTEGER(KIND=1)' constants range from `-2**31'
!      to `2**31-1' (the range for two's-complement 32-bit values),
!      instead of determining their range from the actual range of the
!      type for the configuration (and, someday, for the constant).
! 
!      Further, it generally doesn't implement the handling of constants
!      very well in that it makes assumptions about the configuration
!      that it no longer makes regarding variables (types).
! 
!      Included with this item is the fact that `g77' doesn't recognize
!      that, on IEEE-754/854-compliant systems, `0./0.' should produce a
!      NaN and no warning instead of the value `0.' and a warning.
! 
!    * `g77' uses way too much memory and CPU time to process large
!      aggregate areas having any initialized elements.
! 
!      For example, `REAL A(1000000)' followed by `DATA A(1)/1/' takes up
!      way too much time and space, including the size of the generated
!      assembler file.
! 
!      Version 0.5.18 improves cases like this--specifically, cases of
!      _sparse_ initialization that leave large, contiguous areas
!      uninitialized--significantly.  However, even with the
!      improvements, these cases still require too much memory and CPU
!      time.
! 
!      (Version 0.5.18 also improves cases where the initial values are
!      zero to a much greater degree, so if the above example ends with
!      `DATA A(1)/0/', the compile-time performance will be about as good
!      as it will ever get, aside from unrelated improvements to the
!      compiler.)
! 
!      Note that `g77' does display a warning message to notify the user
!      before the compiler appears to hang.  A warning message is issued
!      when `g77' sees code that provides initial values (e.g. via
!      `DATA') to an aggregate area (`COMMON' or `EQUIVALENCE', or even a
!      large enough array or `CHARACTER' variable) that is large enough
!      to increase `g77''s compile time by roughly a factor of 10.
! 
!      This size currently is quite small, since `g77' currently has a
!      known bug requiring too much memory and time to handle such cases.
!      In `gcc/gcc/f/data.c', the macro `FFEDATA_sizeTOO_BIG_INIT_' is
!      defined to the minimum size for the warning to appear.  The size
!      is specified in storage units, which can be bytes, words, or
!      whatever, on a case-by-case basis.
! 
!      After changing this macro definition, you must (of course) rebuild
!      and reinstall `g77' for the change to take effect.
! 
!      Note that, as of version 0.5.18, improvements have reduced the
!      scope of the problem for _sparse_ initialization of large arrays,
!      especially those with large, contiguous uninitialized areas.
!      However, the warning is issued at a point prior to when `g77'
!      knows whether the initialization is sparse, and delaying the
!      warning could mean it is produced too late to be helpful.
! 
!      Therefore, the macro definition should not be adjusted to reflect
!      sparse cases.  Instead, adjust it to generate the warning when
!      densely initialized arrays begin to cause responses noticeably
!      slower than linear performance would suggest.
! 
!    * When debugging, after starting up the debugger but before being
!      able to see the source code for the main program unit, the user
!      must currently set a breakpoint at `MAIN__' (or `MAIN___' or
!      `MAIN_' if `MAIN__' doesn't exist) and run the program until it
!      hits the breakpoint.  At that point, the main program unit is
!      activated and about to execute its first executable statement, but
!      that's the state in which the debugger should start up, as is the
!      case for languages like C.
! 
!    * Debugging `g77'-compiled code using debuggers other than `gdb' is
!      likely not to work.
! 
!      Getting `g77' and `gdb' to work together is a known
!      problem--getting `g77' to work properly with other debuggers, for
!      which source code often is unavailable to `g77' developers, seems
!      like a much larger, unknown problem, and is a lower priority than
!      making `g77' and `gdb' work together properly.
! 
!      On the other hand, information about problems other debuggers have
!      with `g77' output might make it easier to properly fix `g77', and
!      perhaps even improve `gdb', so it is definitely welcome.  Such
!      information might even lead to all relevant products working
!      together properly sooner.
! 
!    * `g77' doesn't work perfectly on 64-bit configurations such as the
!      Digital Semiconductor ("DEC") Alpha.
! 
!      This problem is largely resolved as of version 0.5.23.
! 
!    * `g77' currently inserts needless padding for things like `COMMON
!      A,IPAD' where `A' is `CHARACTER*1' and `IPAD' is `INTEGER(KIND=1)'
!      on machines like x86, because the back end insists that `IPAD' be
!      aligned to a 4-byte boundary, but the processor has no such
!      requirement (though it is usually good for performance).
! 
!      The `gcc' back end needs to provide a wider array of
!      specifications of alignment requirements and preferences for
!      targets, and front ends like `g77' should take advantage of this
!      when it becomes available.
! 
!    * The `libf2c' routines that perform some run-time arithmetic on
!      `COMPLEX' operands were modified circa version 0.5.20 of `g77' to
!      work properly even in the presence of aliased operands.
! 
!      While the `g77' and `netlib' versions of `libf2c' differ on how
!      this is accomplished, the main differences are that we believe the
!      `g77' version works properly even in the presence of _partially_
!      aliased operands.
! 
!      However, these modifications have reduced performance on targets
!      such as x86, due to the extra copies of operands involved.
! 
! 
! File: g77.info,  Node: Missing Features,  Next: Disappointments,  Prev: Known Bugs,  Up: Trouble
! 
! Missing Features
! ================
! 
!    This section lists features we know are missing from `g77', and
! which we want to add someday.  (There is no priority implied in the
! ordering below.)
! 
! * Menu:
! 
! GNU Fortran language:
! * Better Source Model::
! * Fortran 90 Support::
! * Intrinsics in PARAMETER Statements::
! * Arbitrary Concatenation::
! * SELECT CASE on CHARACTER Type::
! * RECURSIVE Keyword::
! * Popular Non-standard Types::
! * Full Support for Compiler Types::
! * Array Bounds Expressions::
! * POINTER Statements::
! * Sensible Non-standard Constructs::
! * READONLY Keyword::
! * FLUSH Statement::
! * Expressions in FORMAT Statements::
! * Explicit Assembler Code::
! * Q Edit Descriptor::
! 
! GNU Fortran dialects:
! * Old-style PARAMETER Statements::
! * TYPE and ACCEPT I/O Statements::
! * STRUCTURE UNION RECORD MAP::
! * OPEN CLOSE and INQUIRE Keywords::
! * ENCODE and DECODE::
! * AUTOMATIC Statement::
! * Suppressing Space Padding::
! * Fortran Preprocessor::
! * Bit Operations on Floating-point Data::
! * Really Ugly Character Assignments::
! 
! New facilities:
! * POSIX Standard::
! * Floating-point Exception Handling::
! * Nonportable Conversions::
! * Large Automatic Arrays::
! * Support for Threads::
! * Increasing Precision/Range::
! * Enabling Debug Lines::
! 
! Better diagnostics:
! * Better Warnings::
! * Gracefully Handle Sensible Bad Code::
! * Non-standard Conversions::
! * Non-standard Intrinsics::
! * Modifying DO Variable::
! * Better Pedantic Compilation::
! * Warn About Implicit Conversions::
! * Invalid Use of Hollerith Constant::
! * Dummy Array Without Dimensioning Dummy::
! * Invalid FORMAT Specifiers::
! * Ambiguous Dialects::
! * Unused Labels::
! * Informational Messages::
! 
! Run-time facilities:
! * Uninitialized Variables at Run Time::
! * Portable Unformatted Files::
! * Better List-directed I/O::
! * Default to Console I/O::
! 
! Debugging:
! * Labels Visible to Debugger::
! 
! 
! File: g77.info,  Node: Better Source Model,  Next: Fortran 90 Support,  Up: Missing Features
! 
! Better Source Model
! -------------------
! 
!    `g77' needs to provide, as the default source-line model, a "pure
! visual" mode, where the interpretation of a source program in this mode
! can be accurately determined by a user looking at a traditionally
! displayed rendition of the program (assuming the user knows whether the
! program is fixed or free form).
! 
!    The design should assume the user cannot tell tabs from spaces and
! cannot see trailing spaces on lines, but has canonical tab stops and,
! for fixed-form source, has the ability to always know exactly where
! column 72 is (since the Fortran standard itself requires this for
! fixed-form source).
! 
!    This would change the default treatment of fixed-form source to not
! treat lines with tabs as if they were infinitely long--instead, they
! would end at column 72 just as if the tabs were replaced by spaces in
! the canonical way.
! 
!    As part of this, provide common alternate models (Digital, `f2c',
! and so on) via command-line options.  This includes allowing
! arbitrarily long lines for free-form source as well as fixed-form
! source and providing various limits and diagnostics as appropriate.
! 
!    Also, `g77' should offer, perhaps even default to, warnings when
! characters beyond the last valid column are anything other than spaces.
! This would mean code with "sequence numbers" in columns 73 through 80
! would be rejected, and there's a lot of that kind of code around, but
! one of the most frequent bugs encountered by new users is accidentally
! writing fixed-form source code into and beyond column 73.  So, maybe
! the users of old code would be able to more easily handle having to
! specify, say, a `-Wno-col73to80' option.
! 
! 
! File: g77.info,  Node: Fortran 90 Support,  Next: Intrinsics in PARAMETER Statements,  Prev: Better Source Model,  Up: Missing Features
! 
! Fortran 90 Support
! ------------------
! 
!    `g77' does not support many of the features that distinguish Fortran
! 90 (and, now, Fortran 95) from ANSI FORTRAN 77.
! 
!    Some Fortran 90 features are supported, because they make sense to
! offer even to die-hard users of F77.  For example, many of them codify
! various ways F77 has been extended to meet users' needs during its
! tenure, so `g77' might as well offer them as the primary way to meet
! those same needs, even if it offers compatibility with one or more of
! the ways those needs were met by other F77 compilers in the industry.
! 
!    Still, many important F90 features are not supported, because no
! attempt has been made to research each and every feature and assess its
! viability in `g77'.  In the meantime, users who need those features must
! use Fortran 90 compilers anyway, and the best approach to adding some
! F90 features to GNU Fortran might well be to fund a comprehensive
! project to create GNU Fortran 95.
! 
! 
! File: g77.info,  Node: Intrinsics in PARAMETER Statements,  Next: Arbitrary Concatenation,  Prev: Fortran 90 Support,  Up: Missing Features
! 
! Intrinsics in `PARAMETER' Statements
! ------------------------------------
! 
!    `g77' doesn't allow intrinsics in `PARAMETER' statements.
! 
!    Related to this, `g77' doesn't allow non-integral exponentiation in
! `PARAMETER' statements, such as `PARAMETER (R=2**.25)'.  It is unlikely
! `g77' will ever support this feature, as doing it properly requires
! complete emulation of a target computer's floating-point facilities when
! building `g77' as a cross-compiler.  But, if the `gcc' back end is
! enhanced to provide such a facility, `g77' will likely use that facility
! in implementing this feature soon afterwards.
! 
! 
! File: g77.info,  Node: Arbitrary Concatenation,  Next: SELECT CASE on CHARACTER Type,  Prev: Intrinsics in PARAMETER Statements,  Up: Missing Features
! 
! Arbitrary Concatenation
! -----------------------
! 
!    `g77' doesn't support arbitrary operands for concatenation in
! contexts where run-time allocation is required.  For example:
! 
!      SUBROUTINE X(A)
!      CHARACTER*(*) A
!      CALL FOO(A // 'suffix')
! 
! 
! File: g77.info,  Node: SELECT CASE on CHARACTER Type,  Next: RECURSIVE Keyword,  Prev: Arbitrary Concatenation,  Up: Missing Features
! 
! `SELECT CASE' on `CHARACTER' Type
! ---------------------------------
! 
!    Character-type selector/cases for `SELECT CASE' currently are not
! supported.
! 
! 
! File: g77.info,  Node: RECURSIVE Keyword,  Next: Popular Non-standard Types,  Prev: SELECT CASE on CHARACTER Type,  Up: Missing Features
! 
! `RECURSIVE' Keyword
! -------------------
! 
!    `g77' doesn't support the `RECURSIVE' keyword that F90 compilers do.
! Nor does it provide any means for compiling procedures designed to do
! recursion.
! 
!    All recursive code can be rewritten to not use recursion, but the
! result is not pretty.
! 
! 
! File: g77.info,  Node: Increasing Precision/Range,  Next: Enabling Debug Lines,  Prev: Support for Threads,  Up: Missing Features
! 
! Increasing Precision/Range
! --------------------------
! 
!    Some compilers, such as `f2c', have an option (`-r8', `-qrealsize=8'
! or similar) that provides automatic treatment of `REAL' entities such
! that they have twice the storage size, and a corresponding increase in
! the range and precision, of what would normally be the `REAL(KIND=1)'
! (default `REAL') type.  (This affects `COMPLEX' the same way.)
! 
!    They also typically offer another option (`-i8') to increase
! `INTEGER' entities so they are twice as large (with roughly twice as
! much range).
! 
!    (There are potential pitfalls in using these options.)
! 
!    `g77' does not yet offer any option that performs these kinds of
! transformations.  Part of the problem is the lack of detailed
! specifications regarding exactly how these options affect the
! interpretation of constants, intrinsics, and so on.
! 
!    Until `g77' addresses this need, programmers could improve the
! portability of their code by modifying it to not require compile-time
! options to produce correct results.  Some free tools are available
! which may help, specifically in Toolpack (which one would expect to be
! sound) and the `fortran' section of the Netlib repository.
! 
!    Use of preprocessors can provide a fairly portable means to work
! around the lack of widely portable methods in the Fortran language
! itself (though increasing acceptance of Fortran 90 would alleviate this
! problem).
! 
! 
! File: g77.info,  Node: Popular Non-standard Types,  Next: Full Support for Compiler Types,  Prev: RECURSIVE Keyword,  Up: Missing Features
! 
! Popular Non-standard Types
! --------------------------
! 
!    `g77' doesn't fully support `INTEGER*2', `LOGICAL*1', and similar.
! In the meantime, version 0.5.18 provides rudimentary support for them.
! 
! 
! File: g77.info,  Node: Full Support for Compiler Types,  Next: Array Bounds Expressions,  Prev: Popular Non-standard Types,  Up: Missing Features
! 
! Full Support for Compiler Types
! -------------------------------
! 
!    `g77' doesn't support `INTEGER', `REAL', and `COMPLEX' equivalents
! for _all_ applicable back-end-supported types (`char', `short int',
! `int', `long int', `long long int', and `long double').  This means
! providing intrinsic support, and maybe constant support (using F90
! syntax) as well, and, for most machines will result in automatic
! support of `INTEGER*1', `INTEGER*2', `INTEGER*8', maybe even `REAL*16',
! and so on.
! 
! 
! File: g77.info,  Node: Array Bounds Expressions,  Next: POINTER Statements,  Prev: Full Support for Compiler Types,  Up: Missing Features
! 
! Array Bounds Expressions
! ------------------------
! 
!    `g77' doesn't support more general expressions to dimension arrays,
! such as array element references, function references, etc.
! 
!    For example, `g77' currently does not accept the following:
! 
!      SUBROUTINE X(M, N)
!      INTEGER N(10), M(N(2), N(1))
! 
! 
! File: g77.info,  Node: POINTER Statements,  Next: Sensible Non-standard Constructs,  Prev: Array Bounds Expressions,  Up: Missing Features
! 
! POINTER Statements
! ------------------
! 
!    `g77' doesn't support pointers or allocatable objects (other than
! automatic arrays).  This set of features is probably considered just
! behind intrinsics in `PARAMETER' statements on the list of large,
! important things to add to `g77'.
! 
!    In the meantime, consider using the `INTEGER(KIND=7)' declaration to
! specify that a variable must be able to hold a pointer.  This construct
! is not portable to other non-GNU compilers, but it is portable to all
! machines GNU Fortran supports when `g77' is used.
! 
!    *Note Functions and Subroutines::, for information on `%VAL()',
! `%REF()', and `%DESCR()' constructs, which are useful for passing
! pointers to procedures written in languages other than Fortran.
! 
! 
! File: g77.info,  Node: Sensible Non-standard Constructs,  Next: READONLY Keyword,  Prev: POINTER Statements,  Up: Missing Features
! 
! Sensible Non-standard Constructs
! --------------------------------
! 
!    `g77' rejects things other compilers accept, like `INTRINSIC
! SQRT,SQRT'.  As time permits in the future, some of these things that
! are easy for humans to read and write and unlikely to be intended to
! mean something else will be accepted by `g77' (though `-fpedantic'
! should trigger warnings about such non-standard constructs).
! 
!    Until `g77' no longer gratuitously rejects sensible code, you might
! as well fix your code to be more standard-conforming and portable.
! 
!    The kind of case that is important to except from the recommendation
! to change your code is one where following good coding rules would
! force you to write non-standard code that nevertheless has a clear
! meaning.
! 
!    For example, when writing an `INCLUDE' file that defines a common
! block, it might be appropriate to include a `SAVE' statement for the
! common block (such as `SAVE /CBLOCK/'), so that variables defined in
! the common block retain their values even when all procedures declaring
! the common block become inactive (return to their callers).
! 
!    However, putting `SAVE' statements in an `INCLUDE' file would
! prevent otherwise standard-conforming code from also specifying the
! `SAVE' statement, by itself, to indicate that all local variables and
! arrays are to have the `SAVE' attribute.
! 
!    For this reason, `g77' already has been changed to allow this
! combination, because although the general problem of gratuitously
! rejecting unambiguous and "safe" constructs still exists in `g77', this
! particular construct was deemed useful enough that it was worth fixing
! `g77' for just this case.
! 
!    So, while there is no need to change your code to avoid using this
! particular construct, there might be other, equally appropriate but
! non-standard constructs, that you shouldn't have to stop using just
! because `g77' (or any other compiler) gratuitously rejects it.
! 
!    Until the general problem is solved, if you have any such construct
! you believe is worthwhile using (e.g. not just an arbitrary, redundant
! specification of an attribute), please submit a bug report with an
! explanation, so we can consider fixing `g77' just for cases like yours.
! 
! 
! File: g77.info,  Node: READONLY Keyword,  Next: FLUSH Statement,  Prev: Sensible Non-standard Constructs,  Up: Missing Features
! 
! `READONLY' Keyword
! ------------------
! 
!    Support for `READONLY', in `OPEN' statements, requires `libg2c'
! support, to make sure that `CLOSE(...,STATUS='DELETE')' does not delete
! a file opened on a unit with the `READONLY' keyword, and perhaps to
! trigger a fatal diagnostic if a `WRITE' or `PRINT' to such a unit is
! attempted.
! 
!    _Note:_ It is not sufficient for `g77' and `libg2c' (its version of
! `libf2c') to assume that `READONLY' does not need some kind of explicit
! support at run time, due to UNIX systems not (generally) needing it.
! `g77' is not just a UNIX-based compiler!
! 
!    Further, mounting of non-UNIX filesystems on UNIX systems (such as
! via NFS) might require proper `READONLY' support.
! 
!    (Similar issues might be involved with supporting the `SHARED'
! keyword.)
! 
! 
! File: g77.info,  Node: FLUSH Statement,  Next: Expressions in FORMAT Statements,  Prev: READONLY Keyword,  Up: Missing Features
! 
! `FLUSH' Statement
! -----------------
! 
!    `g77' could perhaps use a `FLUSH' statement that does what `CALL
! FLUSH' does, but that supports `*' as the unit designator (same unit as
! for `PRINT') and accepts `ERR=' and/or `IOSTAT=' specifiers.
! 
! 
! File: g77.info,  Node: Expressions in FORMAT Statements,  Next: Explicit Assembler Code,  Prev: FLUSH Statement,  Up: Missing Features
! 
! Expressions in `FORMAT' Statements
! ----------------------------------
! 
!    `g77' doesn't support `FORMAT(I<J>)' and the like.  Supporting this
! requires a significant redesign or replacement of `libg2c'.
! 
!    However, `g77' does support this construct when the expression is
! constant (as of version 0.5.22).  For example:
! 
!            PARAMETER (IWIDTH = 12)
!      10    FORMAT (I<IWIDTH>)
! 
!    Otherwise, at least for output (`PRINT' and `WRITE'), Fortran code
! making use of this feature can be rewritten to avoid it by constructing
! the `FORMAT' string in a `CHARACTER' variable or array, then using that
! variable or array in place of the `FORMAT' statement label to do the
! original `PRINT' or `WRITE'.
! 
!    Many uses of this feature on input can be rewritten this way as
! well, but not all can.  For example, this can be rewritten:
! 
!            READ 20, I
!      20    FORMAT (I<J>)
! 
!    However, this cannot, in general, be rewritten, especially when
! `ERR=' and `END=' constructs are employed:
! 
!            READ 30, J, I
!      30    FORMAT (I<J>)
! 
! 
! File: g77.info,  Node: Explicit Assembler Code,  Next: Q Edit Descriptor,  Prev: Expressions in FORMAT Statements,  Up: Missing Features
! 
! Explicit Assembler Code
! -----------------------
! 
!    `g77' needs to provide some way, a la `gcc', for `g77' code to
! specify explicit assembler code.
! 
! 
! File: g77.info,  Node: Q Edit Descriptor,  Next: Old-style PARAMETER Statements,  Prev: Explicit Assembler Code,  Up: Missing Features
! 
! Q Edit Descriptor
! -----------------
! 
!    The `Q' edit descriptor in `FORMAT's isn't supported.  (This is
! meant to get the number of characters remaining in an input record.)
! Supporting this requires a significant redesign or replacement of
! `libg2c'.
! 
!    A workaround might be using internal I/O or the stream-based
! intrinsics.  *Note FGetC Intrinsic (subroutine)::.
! 
! 
! File: g77.info,  Node: Old-style PARAMETER Statements,  Next: TYPE and ACCEPT I/O Statements,  Prev: Q Edit Descriptor,  Up: Missing Features
! 
! Old-style PARAMETER Statements
! ------------------------------
! 
!    `g77' doesn't accept `PARAMETER I=1'.  Supporting this obsolete form
! of the `PARAMETER' statement would not be particularly hard, as most of
! the parsing code is already in place and working.
! 
!    Until time/money is spent implementing it, you might as well fix
! your code to use the standard form, `PARAMETER (I=1)' (possibly needing
! `INTEGER I' preceding the `PARAMETER' statement as well, otherwise, in
! the obsolete form of `PARAMETER', the type of the variable is set from
! the type of the constant being assigned to it).
! 
! 
! File: g77.info,  Node: TYPE and ACCEPT I/O Statements,  Next: STRUCTURE UNION RECORD MAP,  Prev: Old-style PARAMETER Statements,  Up: Missing Features
! 
! `TYPE' and `ACCEPT' I/O Statements
! ----------------------------------
! 
!    `g77' doesn't support the I/O statements `TYPE' and `ACCEPT'.  These
! are common extensions that should be easy to support, but also are
! fairly easy to work around in user code.
! 
!    Generally, any `TYPE fmt,list' I/O statement can be replaced by
! `PRINT fmt,list'.  And, any `ACCEPT fmt,list' statement can be replaced
! by `READ fmt,list'.
! 
! 
! File: g77.info,  Node: STRUCTURE UNION RECORD MAP,  Next: OPEN CLOSE and INQUIRE Keywords,  Prev: TYPE and ACCEPT I/O Statements,  Up: Missing Features
! 
! `STRUCTURE', `UNION', `RECORD', `MAP'
! -------------------------------------
! 
!    `g77' doesn't support `STRUCTURE', `UNION', `RECORD', `MAP'.  This
! set of extensions is quite a bit lower on the list of large, important
! things to add to `g77', partly because it requires a great deal of work
! either upgrading or replacing `libg2c'.
! 
! 
! File: g77.info,  Node: OPEN CLOSE and INQUIRE Keywords,  Next: ENCODE and DECODE,  Prev: STRUCTURE UNION RECORD MAP,  Up: Missing Features
! 
! `OPEN', `CLOSE', and `INQUIRE' Keywords
! ---------------------------------------
! 
!    `g77' doesn't have support for keywords such as `DISP='DELETE'' in
! the `OPEN', `CLOSE', and `INQUIRE' statements.  These extensions are
! easy to add to `g77' itself, but require much more work on `libg2c'.
! 
!    `g77' doesn't support `FORM='PRINT'' or an equivalent to translate
! the traditional `carriage control' characters in column 1 of output to
! use backspaces, carriage returns and the like.  However programs exist
! to translate them in output files (or standard output).  These are
! typically called either `fpr' or `asa'.  You can get a version of `asa'
! from `ftp://sunsite.unc.edu/pub/Linux/devel/lang/fortran' for GNU
! systems which will probably build easily on other systems.
! Alternatively, `fpr' is in BSD distributions in various archive sites.
! 
! 
! File: g77.info,  Node: ENCODE and DECODE,  Next: AUTOMATIC Statement,  Prev: OPEN CLOSE and INQUIRE Keywords,  Up: Missing Features
! 
! `ENCODE' and `DECODE'
! ---------------------
! 
!    `g77' doesn't support `ENCODE' or `DECODE'.
! 
!    These statements are best replaced by READ and WRITE statements
! involving internal files (CHARACTER variables and arrays).
! 
!    For example, replace a code fragment like
! 
!            INTEGER*1 LINE(80)
!      ...
!            DECODE (80, 9000, LINE) A, B, C
!      ...
!      9000  FORMAT (1X, 3(F10.5))
! 
! with:
! 
!            CHARACTER*80 LINE
!      ...
!            READ (UNIT=LINE, FMT=9000) A, B, C
!      ...
!      9000  FORMAT (1X, 3(F10.5))
! 
!    Similarly, replace a code fragment like
! 
!            INTEGER*1 LINE(80)
!      ...
!            ENCODE (80, 9000, LINE) A, B, C
!      ...
!      9000  FORMAT (1X, 'OUTPUT IS ', 3(F10.5))
! 
! with:
! 
!            CHARACTER*80 LINE
!      ...
!            WRITE (UNIT=LINE, FMT=9000) A, B, C
!      ...
!      9000  FORMAT (1X, 'OUTPUT IS ', 3(F10.5))
! 
!    It is entirely possible that `ENCODE' and `DECODE' will be supported
! by a future version of `g77'.
! 
! 
! File: g77.info,  Node: AUTOMATIC Statement,  Next: Suppressing Space Padding,  Prev: ENCODE and DECODE,  Up: Missing Features
! 
! `AUTOMATIC' Statement
! ---------------------
! 
!    `g77' doesn't support the `AUTOMATIC' statement that `f2c' does.
! 
!    `AUTOMATIC' would identify a variable or array as not being
! `SAVE''d, which is normally the default, but which would be especially
! useful for code that, _generally_, needed to be compiled with the
! `-fno-automatic' option.
! 
!    `AUTOMATIC' also would serve as a hint to the compiler that placing
! the variable or array--even a very large array-on the stack is
! acceptable.
! 
!    `AUTOMATIC' would not, by itself, designate the containing procedure
! as recursive.
! 
!    `AUTOMATIC' should work syntactically like `SAVE', in that
! `AUTOMATIC' with no variables listed should apply to all pertinent
! variables and arrays (which would not include common blocks or their
! members).
! 
!    Variables and arrays denoted as `AUTOMATIC' would not be permitted
! to be initialized via `DATA' or other specification of any initial
! values, requiring explicit initialization, such as via assignment
! statements.
! 
!    Perhaps `UNSAVE' and `STATIC', as strict semantic opposites to
! `SAVE' and `AUTOMATIC', should be provided as well.
! 
! 
! File: g77.info,  Node: Suppressing Space Padding,  Next: Fortran Preprocessor,  Prev: AUTOMATIC Statement,  Up: Missing Features
! 
! Suppressing Space Padding of Source Lines
! -----------------------------------------
! 
!    `g77' should offer VXT-Fortran-style suppression of virtual spaces
! at the end of a source line if an appropriate command-line option is
! specified.
! 
!    This affects cases where a character constant is continued onto the
! next line in a fixed-form source file, as in the following example:
! 
!      10    PRINT *,'HOW MANY
!           1 SPACES?'
! 
! `g77', and many other compilers, virtually extend the continued line
! through column 72 with spaces that become part of the character
! constant, but Digital Fortran normally didn't, leaving only one space
! between `MANY' and `SPACES?' in the output of the above statement.
! 
!    Fairly recently, at least one version of Digital Fortran was
! enhanced to provide the other behavior when a command-line option is
! specified, apparently due to demand from readers of the USENET group
! `comp.lang.fortran' to offer conformance to this widespread practice in
! the industry.  `g77' should return the favor by offering conformance to
! Digital's approach to handling the above example.
! 
! 
! File: g77.info,  Node: Fortran Preprocessor,  Next: Bit Operations on Floating-point Data,  Prev: Suppressing Space Padding,  Up: Missing Features
! 
! Fortran Preprocessor
! --------------------
! 
!    `g77' should offer a preprocessor designed specifically for Fortran
! to replace `cpp -traditional'.  There are several out there worth
! evaluating, at least.
! 
!    Such a preprocessor would recognize Hollerith constants, properly
! parse comments and character constants, and so on.  It might also
! recognize, process, and thus preprocess files included via the
! `INCLUDE' directive.
! 
! 
! File: g77.info,  Node: Bit Operations on Floating-point Data,  Next: Really Ugly Character Assignments,  Prev: Fortran Preprocessor,  Up: Missing Features
! 
! Bit Operations on Floating-point Data
! -------------------------------------
! 
!    `g77' does not allow `REAL' and other non-integral types for
! arguments to intrinsics like `And', `Or', and `Shift'.
! 
!    For example, this program is rejected by `g77', because the
! intrinsic `Iand' does not accept `REAL' arguments:
! 
!      DATA A/7.54/, B/9.112/
!      PRINT *, IAND(A, B)
!      END
! 
! 
! File: g77.info,  Node: Really Ugly Character Assignments,  Next: POSIX Standard,  Prev: Bit Operations on Floating-point Data,  Up: Missing Features
! 
! Really Ugly Character Assignments
! ---------------------------------
! 
!    An option such as `-fugly-char' should be provided to allow
! 
!      REAL*8 A1
!      DATA A1 / '12345678' /
! 
!    and:
! 
!      REAL*8 A1
!      A1 = 'ABCDEFGH'
! 
! 
! File: g77.info,  Node: POSIX Standard,  Next: Floating-point Exception Handling,  Prev: Really Ugly Character Assignments,  Up: Missing Features
! 
! `POSIX' Standard
! ----------------
! 
!    `g77' should support the POSIX standard for Fortran.
! 
! 
! File: g77.info,  Node: Floating-point Exception Handling,  Next: Nonportable Conversions,  Prev: POSIX Standard,  Up: Missing Features
! 
! Floating-point Exception Handling
! ---------------------------------
! 
!    The `gcc' backend and, consequently, `g77', currently provides no
! general control over whether or not floating-point exceptions are
! trapped or ignored.  (Ignoring them typically results in NaN values
! being propagated in systems that conform to IEEE 754.)  The behavior is
! normally inherited from the system-dependent startup code, though some
! targets, such as the Alpha, have code generation options which change
! the behavior.
! 
!    Most systems provide some C-callable mechanism to change this; this
! can be invoked at startup using `gcc''s `constructor' attribute.  For
! example, just compiling and linking the following C code with your
! program will turn on exception trapping for the "common" exceptions on
! a GNU system using glibc 2.2 or newer:
! 
!      #define _GNU_SOURCE 1
!      #include <fenv.h>
!      static void __attribute__ ((constructor))
!      trapfpe ()
!      {
!        /* Enable some exceptions.  At startup all exceptions are masked.  */
!      
!        feenableexcept (FE_INVALID|FE_DIVBYZERO|FE_OVERFLOW);
!      }
! 
!    A convenient trick is to compile this something like:
!      gcc -o libtrapfpe.a trapfpe.c
!    and then use it by adding `-trapfpe' to the `g77' command line when
! linking.
! 
! 
! File: g77.info,  Node: Nonportable Conversions,  Next: Large Automatic Arrays,  Prev: Floating-point Exception Handling,  Up: Missing Features
! 
! Nonportable Conversions
! -----------------------
! 
!    `g77' doesn't accept some particularly nonportable, silent data-type
! conversions such as `LOGICAL' to `REAL' (as in `A=.FALSE.', where `A'
! is type `REAL'), that other compilers might quietly accept.
! 
!    Some of these conversions are accepted by `g77' when the
! `-fugly-logint' option is specified.  Perhaps it should accept more or
! all of them.
! 
! 
! File: g77.info,  Node: Large Automatic Arrays,  Next: Support for Threads,  Prev: Nonportable Conversions,  Up: Missing Features
! 
! Large Automatic Arrays
! ----------------------
! 
!    Currently, automatic arrays always are allocated on the stack.  For
! situations where the stack cannot be made large enough, `g77' should
! offer a compiler option that specifies allocation of automatic arrays
! in heap storage.
! 
! 
! File: g77.info,  Node: Support for Threads,  Next: Increasing Precision/Range,  Prev: Large Automatic Arrays,  Up: Missing Features
! 
! Support for Threads
! -------------------
! 
!    Neither the code produced by `g77' nor the `libg2c' library are
! thread-safe, nor does `g77' have support for parallel processing (other
! than the instruction-level parallelism available on some processors).
! A package such as PVM might help here.
! 
! 
! File: g77.info,  Node: Enabling Debug Lines,  Next: Better Warnings,  Prev: Increasing Precision/Range,  Up: Missing Features
! 
! Enabling Debug Lines
! --------------------
! 
!    An option such as `-fdebug-lines' should be provided to turn
! fixed-form lines beginning with `D' to be treated as if they began with
! a space, instead of as if they began with a `C' (as comment lines).
! 
! 
! File: g77.info,  Node: Better Warnings,  Next: Gracefully Handle Sensible Bad Code,  Prev: Enabling Debug Lines,  Up: Missing Features
! 
! Better Warnings
! ---------------
! 
!    Because of how `g77' generates code via the back end, it doesn't
! always provide warnings the user wants.  Consider:
! 
!      PROGRAM X
!      PRINT *, A
!      END
! 
!    Currently, the above is not flagged as a case of using an
! uninitialized variable, because `g77' generates a run-time library call
! that looks, to the GBE, like it might actually _modify_ `A' at run time.
! (And, in fact, depending on the previous run-time library call, it
! would!)
! 
!    Fixing this requires one of the following:
! 
!    * Switch to new library, `libg77', that provides a more "clean"
!      interface, vis-a-vis input, output, and modified arguments, so the
!      GBE can tell what's going on.
! 
!      This would provide a pretty big performance improvement, at least
!      theoretically, and, ultimately, in practice, for some types of
!      code.
! 
!    * Have `g77' pass a pointer to a temporary containing a copy of `A',
!      instead of to `A' itself.  The GBE would then complain about the
!      copy operation involving a potentially uninitialized variable.
! 
!      This might also provide a performance boost for some code, because
!      `A' might then end up living in a register, which could help with
!      inner loops.
! 
!    * Have `g77' use a GBE construct similar to `ADDR_EXPR' but with
!      extra information on the fact that the item pointed to won't be
!      modified (a la `const' in C).
! 
!      Probably the best solution for now, but not quite trivial to
!      implement in the general case.
! 
! 
! File: g77.info,  Node: Gracefully Handle Sensible Bad Code,  Next: Non-standard Conversions,  Prev: Better Warnings,  Up: Missing Features
! 
! Gracefully Handle Sensible Bad Code
! -----------------------------------
! 
!    `g77' generally should continue processing for warnings and
! recoverable (user) errors whenever possible--that is, it shouldn't
! gratuitously make bad or useless code.
! 
!    For example:
! 
!      INTRINSIC ZABS
!      CALL FOO(ZABS)
!      END
! 
! When compiling the above with `-ff2c-intrinsics-disable', `g77' should
! indeed complain about passing `ZABS', but it still should compile,
! instead of rejecting the entire `CALL' statement.  (Some of this is
! related to improving the compiler internals to improve how statements
! are analyzed.)
! 
! 
! File: g77.info,  Node: Non-standard Conversions,  Next: Non-standard Intrinsics,  Prev: Gracefully Handle Sensible Bad Code,  Up: Missing Features
! 
! Non-standard Conversions
! ------------------------
! 
!    `-Wconversion' and related should flag places where non-standard
! conversions are found.  Perhaps much of this would be part of `-Wugly*'.
! 
! 
! File: g77.info,  Node: Non-standard Intrinsics,  Next: Modifying DO Variable,  Prev: Non-standard Conversions,  Up: Missing Features
! 
! Non-standard Intrinsics
! -----------------------
! 
!    `g77' needs a new option, like `-Wintrinsics', to warn about use of
! non-standard intrinsics without explicit `INTRINSIC' statements for
! them.  This would help find code that might fail silently when ported
! to another compiler.
! 
! 
! File: g77.info,  Node: Modifying DO Variable,  Next: Better Pedantic Compilation,  Prev: Non-standard Intrinsics,  Up: Missing Features
! 
! Modifying `DO' Variable
! -----------------------
! 
!    `g77' should warn about modifying `DO' variables via `EQUIVALENCE'.
! (The internal information gathered to produce this warning might also
! be useful in setting the internal "doiter" flag for a variable or even
! array reference within a loop, since that might produce faster code
! someday.)
! 
!    For example, this code is invalid, so `g77' should warn about the
! invalid assignment to `NOTHER':
! 
!      EQUIVALENCE (I, NOTHER)
!      DO I = 1, 100
!         IF (I.EQ. 10) NOTHER = 20
!      END DO
! 
! 
! File: g77.info,  Node: Better Pedantic Compilation,  Next: Warn About Implicit Conversions,  Prev: Modifying DO Variable,  Up: Missing Features
! 
! Better Pedantic Compilation
! ---------------------------
! 
!    `g77' needs to support `-fpedantic' more thoroughly, and use it only
! to generate warnings instead of rejecting constructs outright.  Have it
! warn: if a variable that dimensions an array is not a dummy or placed
! explicitly in `COMMON' (F77 does not allow it to be placed in `COMMON'
! via `EQUIVALENCE'); if specification statements follow
! statement-function-definition statements; about all sorts of syntactic
! extensions.
! 
! 
! File: g77.info,  Node: Warn About Implicit Conversions,  Next: Invalid Use of Hollerith Constant,  Prev: Better Pedantic Compilation,  Up: Missing Features
! 
! Warn About Implicit Conversions
! -------------------------------
! 
!    `g77' needs a `-Wpromotions' option to warn if source code appears
! to expect automatic, silent, and somewhat dangerous compiler-assisted
! conversion of `REAL(KIND=1)' constants to `REAL(KIND=2)' based on
! context.
! 
!    For example, it would warn about cases like this:
! 
!      DOUBLE PRECISION FOO
!      PARAMETER (TZPHI = 9.435784839284958)
!      FOO = TZPHI * 3D0
! 
! 
! File: g77.info,  Node: Invalid Use of Hollerith Constant,  Next: Dummy Array Without Dimensioning Dummy,  Prev: Warn About Implicit Conversions,  Up: Missing Features
! 
! Invalid Use of Hollerith Constant
! ---------------------------------
! 
!    `g77' should disallow statements like `RETURN 2HAB', which are
! invalid in both source forms (unlike `RETURN (2HAB)', which probably
! still makes no sense but at least can be reliably parsed).  Fixed-form
! processing rejects it, but not free-form, except in a way that is a bit
! difficult to understand.
! 
! 
! File: g77.info,  Node: Dummy Array Without Dimensioning Dummy,  Next: Invalid FORMAT Specifiers,  Prev: Invalid Use of Hollerith Constant,  Up: Missing Features
! 
! Dummy Array Without Dimensioning Dummy
! --------------------------------------
! 
!    `g77' should complain when a list of dummy arguments containing an
! adjustable dummy array does not also contain every variable listed in
! the dimension list of the adjustable array.
! 
!    Currently, `g77' does complain about a variable that dimensions an
! array but doesn't appear in any dummy list or `COMMON' area, but this
! needs to be extended to catch cases where it doesn't appear in every
! dummy list that also lists any arrays it dimensions.
! 
!    For example, `g77' should warn about the entry point `ALT' below,
! since it includes `ARRAY' but not `ISIZE' in its list of arguments:
! 
!      SUBROUTINE PRIMARY(ARRAY, ISIZE)
!      REAL ARRAY(ISIZE)
!      ENTRY ALT(ARRAY)
! 
! 
! File: g77.info,  Node: Invalid FORMAT Specifiers,  Next: Ambiguous Dialects,  Prev: Dummy Array Without Dimensioning Dummy,  Up: Missing Features
! 
! Invalid FORMAT Specifiers
! -------------------------
! 
!    `g77' should check `FORMAT' specifiers for validity as it does
! `FORMAT' statements.
! 
!    For example, a diagnostic would be produced for:
! 
!      PRINT 'HI THERE!'  !User meant PRINT *, 'HI THERE!'
! 
! 
! File: g77.info,  Node: Ambiguous Dialects,  Next: Unused Labels,  Prev: Invalid FORMAT Specifiers,  Up: Missing Features
! 
! Ambiguous Dialects
! ------------------
! 
!    `g77' needs a set of options such as `-Wugly*', `-Wautomatic',
! `-Wvxt', `-Wf90', and so on.  These would warn about places in the
! user's source where ambiguities are found, helpful in resolving
! ambiguities in the program's dialect or dialects.
! 
! 
! File: g77.info,  Node: Unused Labels,  Next: Informational Messages,  Prev: Ambiguous Dialects,  Up: Missing Features
! 
! Unused Labels
! -------------
! 
!    `g77' should warn about unused labels when `-Wunused' is in effect.
! 
! 
! File: g77.info,  Node: Informational Messages,  Next: Uninitialized Variables at Run Time,  Prev: Unused Labels,  Up: Missing Features
! 
! Informational Messages
! ----------------------
! 
!    `g77' needs an option to suppress information messages (notes).
! `-w' does this but also suppresses warnings.  The default should be to
! suppress info messages.
! 
!    Perhaps info messages should simply be eliminated.
! 
! 
! File: g77.info,  Node: Uninitialized Variables at Run Time,  Next: Portable Unformatted Files,  Prev: Informational Messages,  Up: Missing Features
! 
! Uninitialized Variables at Run Time
! -----------------------------------
! 
!    `g77' needs an option to initialize everything (not otherwise
! explicitly initialized) to "weird" (machine-dependent) values, e.g.
! NaNs, bad (non-`NULL') pointers, and largest-magnitude integers, would
! help track down references to some kinds of uninitialized variables at
! run time.
! 
!    Note that use of the options `-O -Wuninitialized' can catch many
! such bugs at compile time.
! 
! 
! File: g77.info,  Node: Portable Unformatted Files,  Next: Better List-directed I/O,  Prev: Uninitialized Variables at Run Time,  Up: Missing Features
! 
! Portable Unformatted Files
! --------------------------
! 
!    `g77' has no facility for exchanging unformatted files with systems
! using different number formats--even differing only in endianness (byte
! order)--or written by other compilers.  Some compilers provide
! facilities at least for doing byte-swapping during unformatted I/O.
! 
!    It is unrealistic to expect to cope with exchanging unformatted files
! with arbitrary other compiler runtimes, but the `g77' runtime should at
! least be able to read files written by `g77' on systems with different
! number formats, particularly if they differ only in byte order.
! 
!    In case you do need to write a program to translate to or from `g77'
! (`libf2c') unformatted files, they are written as follows:
! Sequential
!      Unformatted sequential records consist of
!        1. A number giving the length of the record contents;
! 
!        2. the length of record contents again (for backspace).
! 
!      The record length is of C type `long'; this means that it is 8
!      bytes on 64-bit systems such as Alpha GNU/Linux and 4 bytes on
!      other systems, such as x86 GNU/Linux.  Consequently such files
!      cannot be exchanged between 64-bit and 32-bit systems, even with
!      the same basic number format.
! 
! Direct access
!      Unformatted direct access files form a byte stream of length
!      RECORDS*RECL bytes, where RECORDS is the maximum record number
!      (`REC=RECORDS') written and RECL is the record length in bytes
!      specified in the `OPEN' statement (`RECL=RECL').  Data appear in
!      the records as determined by the relevant `WRITE' statement.
!      Dummy records with arbitrary contents appear in the file in place
!      of records which haven't been written.
! 
!    Thus for exchanging a sequential or direct access unformatted file
! between big- and little-endian 32-bit systems using IEEE 754 floating
! point it would be sufficient to reverse the bytes in consecutive words
! in the file if, and _only_ if, only `REAL*4', `COMPLEX', `INTEGER*4'
! and/or `LOGICAL*4' data have been written to it by `g77'.
! 
!    If necessary, it is possible to do byte-oriented i/o with `g77''s
! `FGETC' and `FPUTC' intrinsics.  Byte-swapping can be done in Fortran
! by equivalencing larger sized variables to an `INTEGER*1' array or a
! set of scalars.
! 
!    If you need to exchange binary data between arbitrary system and
! compiler variations, we recommend using a portable binary format with
! Fortran bindings, such as NCSA's HDF (`http://hdf.ncsa.uiuc.edu/') or
! PACT's PDB(1) (`http://www.llnl.gov/def_sci/pact/pact_homepage.html').
! (Unlike, say, CDF or XDR, HDF-like systems write in the native number
! formats and only incur overhead when they are read on a system with a
! different format.)  A future `g77' runtime library should use such
! techniques.
! 
!    ---------- Footnotes ----------
! 
!    (1) No, not _that_ one.
! 
! 
! File: g77.info,  Node: Better List-directed I/O,  Next: Default to Console I/O,  Prev: Portable Unformatted Files,  Up: Missing Features
! 
! Better List-directed I/O
! ------------------------
! 
!    Values output using list-directed I/O (`PRINT *, R, D') should be
! written with a field width, precision, and so on appropriate for the
! type (precision) of each value.
! 
!    (Currently, no distinction is made between single-precision and
! double-precision values by `libf2c'.)
! 
!    It is likely this item will require the `libg77' project to be
! undertaken.
! 
!    In the meantime, use of formatted I/O is recommended.  While it
! might be of little consolation, `g77' does support
! `FORMAT(F<WIDTH>.4)', for example, as long as `WIDTH' is defined as a
! named constant (via `PARAMETER').  That at least allows some
! compile-time specification of the precision of a data type, perhaps
! controlled by preprocessing directives.
! 
! 
! File: g77.info,  Node: Default to Console I/O,  Next: Labels Visible to Debugger,  Prev: Better List-directed I/O,  Up: Missing Features
! 
! Default to Console I/O
! ----------------------
! 
!    The default I/O units, specified by `READ FMT', `READ (UNIT=*)',
! `WRITE (UNIT=*)', and `PRINT FMT', should not be units 5 (input) and 6
! (output), but, rather, unit numbers not normally available for use in
! statements such as `OPEN' and `CLOSE'.
! 
!    Changing this would allow a program to connect units 5 and 6 to
! files via `OPEN', but still use `READ (UNIT=*)' and `PRINT' to do I/O
! to the "console".
! 
!    This change probably requires the `libg77' project.
! 
! 
! File: g77.info,  Node: Labels Visible to Debugger,  Prev: Default to Console I/O,  Up: Missing Features
! 
! Labels Visible to Debugger
! --------------------------
! 
!    `g77' should output debugging information for statements labels, for
! use by debuggers that know how to support them.  Same with weirder
! things like construct names.  It is not yet known if any debug formats
! or debuggers support these.
! 
! 
! File: g77.info,  Node: Disappointments,  Next: Non-bugs,  Prev: Missing Features,  Up: Trouble
! 
! Disappointments and Misunderstandings
! =====================================
! 
!    These problems are perhaps regrettable, but we don't know any
! practical way around them for now.
! 
! * Menu:
! 
! * Mangling of Names::                       `SUBROUTINE FOO' is given
!                                               external name `foo_'.
! * Multiple Definitions of External Names::  No doing both `COMMON /FOO/'
!                                               and `SUBROUTINE FOO'.
! * Limitation on Implicit Declarations::     No `IMPLICIT CHARACTER*(*)'.
! 
! 
! File: g77.info,  Node: Mangling of Names,  Next: Multiple Definitions of External Names,  Up: Disappointments
! 
! Mangling of Names in Source Code
! --------------------------------
! 
!    The current external-interface design, which includes naming of
! external procedures, COMMON blocks, and the library interface, has
! various usability problems, including things like adding underscores
! where not really necessary (and preventing easier inter-language
! operability) and yet not providing complete namespace freedom for user
! C code linked with Fortran apps (due to the naming of functions in the
! library, among other things).
! 
!    Project GNU should at least get all this "right" for systems it
! fully controls, such as the Hurd, and provide defaults and options for
! compatibility with existing systems and interoperability with popular
! existing compilers.
! 
! 
! File: g77.info,  Node: Multiple Definitions of External Names,  Next: Limitation on Implicit Declarations,  Prev: Mangling of Names,  Up: Disappointments
! 
! Multiple Definitions of External Names
! --------------------------------------
! 
!    `g77' doesn't allow a common block and an external procedure or
! `BLOCK DATA' to have the same name.  Some systems allow this, but `g77'
! does not, to be compatible with `f2c'.
! 
!    `g77' could special-case the way it handles `BLOCK DATA', since it
! is not compatible with `f2c' in this particular area (necessarily,
! since `g77' offers an important feature here), but it is likely that
! such special-casing would be very annoying to people with programs that
! use `EXTERNAL FOO', with no other mention of `FOO' in the same program
! unit, to refer to external procedures, since the result would be that
! `g77' would treat these references as requests to force-load BLOCK DATA
! program units.
! 
!    In that case, if `g77' modified names of `BLOCK DATA' so they could
! have the same names as `COMMON', users would find that their programs
! wouldn't link because the `FOO' procedure didn't have its name
! translated the same way.
! 
!    (Strictly speaking, `g77' could emit a
! null-but-externally-satisfying definition of `FOO' with its name
! transformed as if it had been a `BLOCK DATA', but that probably invites
! more trouble than it's worth.)
! 
! 
! File: g77.info,  Node: Limitation on Implicit Declarations,  Prev: Multiple Definitions of External Names,  Up: Disappointments
! 
! Limitation on Implicit Declarations
! -----------------------------------
! 
!    `g77' disallows `IMPLICIT CHARACTER*(*)'.  This is not
! standard-conforming.
! 
! 
! File: g77.info,  Node: Non-bugs,  Next: Warnings and Errors,  Prev: Disappointments,  Up: Trouble
! 
! Certain Changes We Don't Want to Make
! =====================================
! 
!    This section lists changes that people frequently request, but which
! we do not make because we think GNU Fortran is better without them.
! 
! * Menu:
! 
! * Backslash in Constants::           Why `'\\'' is a constant that
!                                        is one, not two, characters long.
! * Initializing Before Specifying::   Why `DATA VAR/1/' can't precede
!                                        `COMMON VAR'.
! * Context-Sensitive Intrinsicness::  Why `CALL SQRT' won't work.
! * Context-Sensitive Constants::      Why `9.435784839284958' is a
!                                        single-precision constant,
!                                        and might be interpreted as
!                                        `9.435785' or similar.
! * Equivalence Versus Equality::      Why `.TRUE. .EQ. .TRUE.' won't work.
! * Order of Side Effects::            Why `J = IFUNC() - IFUNC()' might
!                                        not behave as expected.
! 
! 
! File: g77.info,  Node: Backslash in Constants,  Next: Initializing Before Specifying,  Up: Non-bugs
! 
! Backslash in Constants
! ----------------------
! 
!    In the opinion of many experienced Fortran users, `-fno-backslash'
! should be the default, not `-fbackslash', as currently set by `g77'.
! 
!    First of all, you can always specify `-fno-backslash' to turn off
! this processing.
! 
!    Despite not being within the spirit (though apparently within the
! letter) of the ANSI FORTRAN 77 standard, `g77' defaults to
! `-fbackslash' because that is what most UNIX `f77' commands default to,
! and apparently lots of code depends on this feature.
! 
!    This is a particularly troubling issue.  The use of a C construct in
! the midst of Fortran code is bad enough, worse when it makes existing
! Fortran programs stop working (as happens when programs written for
! non-UNIX systems are ported to UNIX systems with compilers that provide
! the `-fbackslash' feature as the default--sometimes with no option to
! turn it off).
! 
!    The author of GNU Fortran wished, for reasons of linguistic purity,
! to make `-fno-backslash' the default for GNU Fortran and thus require
! users of UNIX `f77' and `f2c' to specify `-fbackslash' to get the UNIX
! behavior.
! 
!    However, the realization that `g77' is intended as a replacement for
! _UNIX_ `f77', caused the author to choose to make `g77' as compatible
! with `f77' as feasible, which meant making `-fbackslash' the default.
! 
!    The primary focus on compatibility is at the source-code level, and
! the question became "What will users expect a replacement for `f77' to
! do, by default?"  Although at least one UNIX `f77' does not provide
! `-fbackslash' as a default, it appears that the majority of them do,
! which suggests that the majority of code that is compiled by UNIX `f77'
! compilers expects `-fbackslash' to be the default.
! 
!    It is probably the case that more code exists that would _not_ work
! with `-fbackslash' in force than code that requires it be in force.
! 
!    However, most of _that_ code is not being compiled with `f77', and
! when it is, new build procedures (shell scripts, makefiles, and so on)
! must be set up anyway so that they work under UNIX.  That makes a much
! more natural and safe opportunity for non-UNIX users to adapt their
! build procedures for `g77''s default of `-fbackslash' than would exist
! for the majority of UNIX `f77' users who would have to modify existing,
! working build procedures to explicitly specify `-fbackslash' if that was
! not the default.
! 
!    One suggestion has been to configure the default for `-fbackslash'
! (and perhaps other options as well) based on the configuration of `g77'.
! 
!    This is technically quite straightforward, but will be avoided even
! in cases where not configuring defaults to be dependent on a particular
! configuration greatly inconveniences some users of legacy code.
! 
!    Many users appreciate the GNU compilers because they provide an
! environment that is uniform across machines.  These users would be
! inconvenienced if the compiler treated things like the format of the
! source code differently on certain machines.
! 
!    Occasionally users write programs intended only for a particular
! machine type.  On these occasions, the users would benefit if the GNU
! Fortran compiler were to support by default the same dialect as the
! other compilers on that machine.  But such applications are rare.  And
! users writing a program to run on more than one type of machine cannot
! possibly benefit from this kind of compatibility.  (This is consistent
! with the design goals for `gcc'.  To change them for `g77', you must
! first change them for `gcc'.  Do not ask the maintainers of `g77' to do
! this for you, or to disassociate `g77' from the widely understood, if
! not widely agreed-upon, goals for GNU compilers in general.)
! 
!    This is why GNU Fortran does and will treat backslashes in the same
! fashion on all types of machines (by default).  *Note Direction of
! Language Development::, for more information on this overall philosophy
! guiding the development of the GNU Fortran language.
! 
!    Of course, users strongly concerned about portability should indicate
! explicitly in their build procedures which options are expected by
! their source code, or write source code that has as few such
! expectations as possible.
! 
!    For example, avoid writing code that depends on backslash (`\')
! being interpreted either way in particular, such as by starting a
! program unit with:
! 
!      CHARACTER BACKSL
!      PARAMETER (BACKSL = '\\')
! 
! Then, use concatenation of `BACKSL' anyplace a backslash is desired.
! In this way, users can write programs which have the same meaning in
! many Fortran dialects.
! 
!    (However, this technique does not work for Hollerith constants--which
! is just as well, since the only generally portable uses for Hollerith
! constants are in places where character constants can and should be
! used instead, for readability.)
! 
! 
! File: g77.info,  Node: Initializing Before Specifying,  Next: Context-Sensitive Intrinsicness,  Prev: Backslash in Constants,  Up: Non-bugs
! 
! Initializing Before Specifying
! ------------------------------
! 
!    `g77' does not allow `DATA VAR/1/' to appear in the source code
! before `COMMON VAR', `DIMENSION VAR(10)', `INTEGER VAR', and so on.  In
! general, `g77' requires initialization of a variable or array to be
! specified _after_ all other specifications of attributes (type, size,
! placement, and so on) of that variable or array are specified (though
! _confirmation_ of data type is permitted).
! 
!    It is _possible_ `g77' will someday allow all of this, even though
! it is not allowed by the FORTRAN 77 standard.
! 
!    Then again, maybe it is better to have `g77' always require
! placement of `DATA' so that it can possibly immediately write constants
! to the output file, thus saving time and space.
! 
!    That is, `DATA A/1000000*1/' should perhaps always be immediately
! writable to canonical assembler, unless it's already known to be in a
! `COMMON' area following as-yet-uninitialized stuff, and to do this it
! cannot be followed by `COMMON A'.
! 
! 
! File: g77.info,  Node: Context-Sensitive Intrinsicness,  Next: Context-Sensitive Constants,  Prev: Initializing Before Specifying,  Up: Non-bugs
! 
! Context-Sensitive Intrinsicness
! -------------------------------
! 
!    `g77' treats procedure references to _possible_ intrinsic names as
! always enabling their intrinsic nature, regardless of whether the
! _form_ of the reference is valid for that intrinsic.
! 
!    For example, `CALL SQRT' is interpreted by `g77' as an invalid
! reference to the `SQRT' intrinsic function, because the reference is a
! subroutine invocation.
! 
!    First, `g77' recognizes the statement `CALL SQRT' as a reference to
! a _procedure_ named `SQRT', not to a _variable_ with that name (as it
! would for a statement such as `V = SQRT').
! 
!    Next, `g77' establishes that, in the program unit being compiled,
! `SQRT' is an intrinsic--not a subroutine that happens to have the same
! name as an intrinsic (as would be the case if, for example, `EXTERNAL
! SQRT' was present).
! 
!    Finally, `g77' recognizes that the _form_ of the reference is
! invalid for that particular intrinsic.  That is, it recognizes that it
! is invalid for an intrinsic _function_, such as `SQRT', to be invoked as
! a _subroutine_.
! 
!    At that point, `g77' issues a diagnostic.
! 
!    Some users claim that it is "obvious" that `CALL SQRT' references an
! external subroutine of their own, not an intrinsic function.
! 
!    However, `g77' knows about intrinsic subroutines, not just
! functions, and is able to support both having the same names, for
! example.
! 
!    As a result of this, `g77' rejects calls to intrinsics that are not
! subroutines, and function invocations of intrinsics that are not
! functions, just as it (and most compilers) rejects invocations of
! intrinsics with the wrong number (or types) of arguments.
! 
!    So, use the `EXTERNAL SQRT' statement in a program unit that calls a
! user-written subroutine named `SQRT'.
! 
! 
! File: g77.info,  Node: Context-Sensitive Constants,  Next: Equivalence Versus Equality,  Prev: Context-Sensitive Intrinsicness,  Up: Non-bugs
! 
! Context-Sensitive Constants
! ---------------------------
! 
!    `g77' does not use context to determine the types of constants or
! named constants (`PARAMETER'), except for (non-standard) typeless
! constants such as `'123'O'.
! 
!    For example, consider the following statement:
! 
!      PRINT *, 9.435784839284958 * 2D0
! 
! `g77' will interpret the (truncated) constant `9.435784839284958' as a
! `REAL(KIND=1)', not `REAL(KIND=2)', constant, because the suffix `D0'
! is not specified.
! 
!    As a result, the output of the above statement when compiled by
! `g77' will appear to have "less precision" than when compiled by other
! compilers.
! 
!    In these and other cases, some compilers detect the fact that a
! single-precision constant is used in a double-precision context and
! therefore interpret the single-precision constant as if it was
! _explicitly_ specified as a double-precision constant.  (This has the
! effect of appending _decimal_, not _binary_, zeros to the fractional
! part of the number--producing different computational results.)
! 
!    The reason this misfeature is dangerous is that a slight, apparently
! innocuous change to the source code can change the computational
! results.  Consider:
! 
!      REAL ALMOST, CLOSE
!      DOUBLE PRECISION FIVE
!      PARAMETER (ALMOST = 5.000000000001)
!      FIVE = 5
!      CLOSE = 5.000000000001
!      PRINT *, 5.000000000001 - FIVE
!      PRINT *, ALMOST - FIVE
!      PRINT *, CLOSE - FIVE
!      END
! 
! Running the above program should result in the same value being printed
! three times.  With `g77' as the compiler, it does.
! 
!    However, compiled by many other compilers, running the above program
! would print two or three distinct values, because in two or three of
! the statements, the constant `5.000000000001', which on most systems is
! exactly equal to `5.' when interpreted as a single-precision constant,
! is instead interpreted as a double-precision constant, preserving the
! represented precision.  However, this "clever" promotion of type does
! not extend to variables or, in some compilers, to named constants.
! 
!    Since programmers often are encouraged to replace manifest constants
! or permanently-assigned variables with named constants (`PARAMETER' in
! Fortran), and might need to replace some constants with variables
! having the same values for pertinent portions of code, it is important
! that compilers treat code so modified in the same way so that the
! results of such programs are the same.  `g77' helps in this regard by
! treating constants just the same as variables in terms of determining
! their types in a context-independent way.
! 
!    Still, there is a lot of existing Fortran code that has been written
! to depend on the way other compilers freely interpret constants' types
! based on context, so anything `g77' can do to help flag cases of this
! in such code could be very helpful.
! 
! 
! File: g77.info,  Node: Equivalence Versus Equality,  Next: Order of Side Effects,  Prev: Context-Sensitive Constants,  Up: Non-bugs
! 
! Equivalence Versus Equality
! ---------------------------
! 
!    Use of `.EQ.' and `.NE.' on `LOGICAL' operands is not supported,
! except via `-fugly-logint', which is not recommended except for legacy
! code (where the behavior expected by the _code_ is assumed).
! 
!    Legacy code should be changed, as resources permit, to use `.EQV.'
! and `.NEQV.' instead, as these are permitted by the various Fortran
! standards.
! 
!    New code should never be written expecting `.EQ.' or `.NE.' to work
! if either of its operands is `LOGICAL'.
! 
!    The problem with supporting this "feature" is that there is unlikely
! to be consensus on how it works, as illustrated by the following sample
! program:
! 
!      LOGICAL L,M,N
!      DATA L,M,N /3*.FALSE./
!      IF (L.AND.M.EQ.N) PRINT *,'L.AND.M.EQ.N'
!      END
! 
!    The issue raised by the above sample program is: what is the
! precedence of `.EQ.' (and `.NE.') when applied to `LOGICAL' operands?
! 
!    Some programmers will argue that it is the same as the precedence
! for `.EQ.' when applied to numeric (such as `INTEGER') operands.  By
! this interpretation, the subexpression `M.EQ.N' must be evaluated first
! in the above program, resulting in a program that, when run, does not
! execute the `PRINT' statement.
! 
!    Other programmers will argue that the precedence is the same as the
! precedence for `.EQV.', which is restricted by the standards to
! `LOGICAL' operands.  By this interpretation, the subexpression
! `L.AND.M' must be evaluated first, resulting in a program that _does_
! execute the `PRINT' statement.
! 
!    Assigning arbitrary semantic interpretations to syntactic expressions
! that might legitimately have more than one "obvious" interpretation is
! generally unwise.
! 
!    The creators of the various Fortran standards have done a good job
! in this case, requiring a distinct set of operators (which have their
! own distinct precedence) to compare `LOGICAL' operands.  This
! requirement results in expression syntax with more certain precedence
! (without requiring substantial context), making it easier for
! programmers to read existing code.  `g77' will avoid muddying up
! elements of the Fortran language that were well-designed in the first
! place.
! 
!    (Ask C programmers about the precedence of expressions such as `(a)
! & (b)' and `(a) - (b)'--they cannot even tell you, without knowing more
! context, whether the `&' and `-' operators are infix (binary) or unary!)
! 
!    Most dangerous of all is the fact that, even assuming consensus on
! its meaning, an expression like `L.AND.M.EQ.N', if it is the result of
! a typographical error, doesn't _look_ like it has such a typo.  Even
! experienced Fortran programmers would not likely notice that
! `L.AND.M.EQV.N' was, in fact, intended.
! 
!    So, this is a prime example of a circumstance in which a quality
! compiler diagnoses the code, instead of leaving it up to someone
! debugging it to know to turn on special compiler options that might
! diagnose it.
! 
! 
! File: g77.info,  Node: Order of Side Effects,  Prev: Equivalence Versus Equality,  Up: Non-bugs
! 
! Order of Side Effects
! ---------------------
! 
!    `g77' does not necessarily produce code that, when run, performs
! side effects (such as those performed by function invocations) in the
! same order as in some other compiler--or even in the same order as
! another version, port, or invocation (using different command-line
! options) of `g77'.
! 
!    It is never safe to depend on the order of evaluation of side
! effects.  For example, an expression like this may very well behave
! differently from one compiler to another:
! 
!      J = IFUNC() - IFUNC()
! 
! There is no guarantee that `IFUNC' will be evaluated in any particular
! order.  Either invocation might happen first.  If `IFUNC' returns 5 the
! first time it is invoked, and returns 12 the second time, `J' might end
! up with the value `7', or it might end up with `-7'.
! 
!    Generally, in Fortran, procedures with side-effects intended to be
! visible to the caller are best designed as _subroutines_, not functions.
! Examples of such side-effects include:
! 
!    * The generation of random numbers that are intended to influence
!      return values.
! 
!    * Performing I/O (other than internal I/O to local variables).
! 
!    * Updating information in common blocks.
! 
!    An example of a side-effect that is not intended to be visible to
! the caller is a function that maintains a cache of recently calculated
! results, intended solely to speed repeated invocations of the function
! with identical arguments.  Such a function can be safely used in
! expressions, because if the compiler optimizes away one or more calls
! to the function, operation of the program is unaffected (aside from
! being speeded up).
! 
! 
! File: g77.info,  Node: Warnings and Errors,  Prev: Non-bugs,  Up: Trouble
! 
! Warning Messages and Error Messages
! ===================================
! 
!    The GNU compiler can produce two kinds of diagnostics: errors and
! warnings.  Each kind has a different purpose:
! 
!      _Errors_ report problems that make it impossible to compile your
!      program.  GNU Fortran reports errors with the source file name,
!      line number, and column within the line where the problem is
!      apparent.
! 
!      _Warnings_ report other unusual conditions in your code that
!      _might_ indicate a problem, although compilation can (and does)
!      proceed.  Warning messages also report the source file name, line
!      number, and column information, but include the text `warning:' to
!      distinguish them from error messages.
! 
!    Warnings might indicate danger points where you should check to make
! sure that your program really does what you intend; or the use of
! obsolete features; or the use of nonstandard features of GNU Fortran.
! Many warnings are issued only if you ask for them, with one of the `-W'
! options (for instance, `-Wall' requests a variety of useful warnings).
! 
!    _Note:_ Currently, the text of the line and a pointer to the column
! is printed in most `g77' diagnostics.
! 
!    *Note Options to Request or Suppress Warnings: Warning Options, for
! more detail on these and related command-line options.
! 
! 
! File: g77.info,  Node: Open Questions,  Next: Bugs,  Prev: Trouble,  Up: Top
! 
! Open Questions
! **************
! 
!    Please consider offering useful answers to these questions!
! 
!    * `LOC()' and other intrinsics are probably somewhat misclassified.
!      Is the a need for more precise classification of intrinsics, and
!      if so, what are the appropriate groupings?  Is there a need to
!      individually enable/disable/delete/hide intrinsics from the
!      command line?
! 
! 
! File: g77.info,  Node: Bugs,  Next: Service,  Prev: Open Questions,  Up: Top
! 
! Reporting Bugs
! **************
! 
!    Your bug reports play an essential role in making GNU Fortran
! reliable.
! 
!    When you encounter a problem, the first thing to do is to see if it
! is already known.  *Note Trouble::.  If it isn't known, then you should
! report the problem.
! 
!    Reporting a bug might help you by bringing a solution to your
! problem, or it might not.  (If it does not, look in the service
! directory; see *Note Service::.)  In any case, the principal function
! of a bug report is to help the entire community by making the next
! version of GNU Fortran work better.  Bug reports are your contribution
! to the maintenance of GNU Fortran.
! 
!    Since the maintainers are very overloaded, we cannot respond to every
! bug report.  However, if the bug has not been fixed, we are likely to
! send you a patch and ask you to tell us whether it works.
! 
!    In order for a bug report to serve its purpose, you must include the
! information that makes for fixing the bug.
! 
! * Menu:
! 
! * Criteria: Bug Criteria.    Have you really found a bug?
! * Where: Bug Lists.          Where to send your bug report.
! * Reporting: Bug Reporting.  How to report a bug effectively.
! 
!    *Note Known Causes of Trouble with GNU Fortran: Trouble, for
! information on problems we already know about.
! 
!    *Note How To Get Help with GNU Fortran: Service, for information on
! where to ask for help.
! 
! 
! File: g77.info,  Node: Bug Criteria,  Next: Bug Lists,  Up: Bugs
! 
! Have You Found a Bug?
! =====================
! 
!    If you are not sure whether you have found a bug, here are some
! guidelines:
! 
!    * If the compiler gets a fatal signal, for any input whatever, that
!      is a compiler bug.  Reliable compilers never crash--they just
!      remain obsolete.
! 
!    * If the compiler produces invalid assembly code, for any input
!      whatever, that is a compiler bug, unless the compiler reports
!      errors (not just warnings) which would ordinarily prevent the
!      assembler from being run.
! 
!    * If the compiler produces valid assembly code that does not
!      correctly execute the input source code, that is a compiler bug.
! 
!      However, you must double-check to make sure, because you might
!      have run into an incompatibility between GNU Fortran and
!      traditional Fortran.  These incompatibilities might be considered
!      bugs, but they are inescapable consequences of valuable features.
! 
!      Or you might have a program whose behavior is undefined, which
!      happened by chance to give the desired results with another
!      Fortran compiler.  It is best to check the relevant Fortran
!      standard thoroughly if it is possible that the program indeed does
!      something undefined.
! 
!      After you have localized the error to a single source line, it
!      should be easy to check for these things.  If your program is
!      correct and well defined, you have found a compiler bug.
! 
!      It might help if, in your submission, you identified the specific
!      language in the relevant Fortran standard that specifies the
!      desired behavior, if it isn't likely to be obvious and agreed-upon
!      by all Fortran users.
! 
!    * If the compiler produces an error message for valid input, that is
!      a compiler bug.
! 
!    * If the compiler does not produce an error message for invalid
!      input, that is a compiler bug.  However, you should note that your
!      idea of "invalid input" might be someone else's idea of "an
!      extension" or "support for traditional practice".
! 
!    * If you are an experienced user of Fortran compilers, your
!      suggestions for improvement of GNU Fortran are welcome in any case.
! 
!    Many, perhaps most, bug reports against `g77' turn out to be bugs in
! the user's code.  While we find such bug reports educational, they
! sometimes take a considerable amount of time to track down or at least
! respond to--time we could be spending making `g77', not some user's
! code, better.
! 
!    Some steps you can take to verify that the bug is not certainly in
! the code you're compiling with `g77':
! 
!    * Compile your code using the `g77' options `-W -Wall -O'.  These
!      options enable many useful warning; the `-O' option enables flow
!      analysis that enables the uninitialized-variable warning.
! 
!      If you investigate the warnings and find evidence of possible bugs
!      in your code, fix them first and retry `g77'.
! 
!    * Compile your code using the `g77' options `-finit-local-zero',
!      `-fno-automatic', `-ffloat-store', and various combinations
!      thereof.
! 
!      If your code works with any of these combinations, that is not
!      proof that the bug isn't in `g77'--a `g77' bug exposed by your
!      code might simply be avoided, or have a different, more subtle
!      effect, when different options are used--but it can be a strong
!      indicator that your code is making unwarranted assumptions about
!      the Fortran dialect and/or underlying machine it is being compiled
!      and run on.
! 
!      *Note Overly Convenient Command-Line Options: Overly Convenient
!      Options, for information on the `-fno-automatic' and
!      `-finit-local-zero' options and how to convert their use into
!      selective changes in your own code.
! 
!    * Validate your code with `ftnchek' or a similar code-checking tool.
!      `ftnchek' can be found at `ftp://ftp.netlib.org/fortran' or
!      `ftp://ftp.dsm.fordham.edu'.
! 
!      Here are some sample `Makefile' rules using `ftnchek' "project"
!      files to do cross-file checking and `sfmakedepend' (from
!      `ftp://ahab.rutgers.edu/pub/perl/sfmakedepend') to maintain
!      dependencies automatically.  These assume the use of GNU `make'.
! 
!           # Dummy suffix for ftnchek targets:
!           .SUFFIXES: .chek
!           .PHONY: chekall
!           
!           # How to compile .f files (for implicit rule):
!           FC = g77
!           # Assume `include' directory:
!           FFLAGS = -Iinclude -g -O -Wall
!           
!           # Flags for ftnchek:
!           CHEK1 = -array=0 -include=includes -noarray
!           CHEK2 = -nonovice -usage=1 -notruncation
!           CHEKFLAGS = $(CHEK1) $(CHEK2)
!           
!           # Run ftnchek with all the .prj files except the one corresponding
!           # to the target's root:
!           %.chek : %.f ; \
!             ftnchek $(filter-out $*.prj,$(PRJS)) $(CHEKFLAGS) \
!               -noextern -library $<
!           
!           # Derive a project file from a source file:
!           %.prj : %.f ; \
!             ftnchek $(CHEKFLAGS) -noextern -project -library $<
!           
!           # The list of objects is assumed to be in variable OBJS.
!           # Sources corresponding to the objects:
!           SRCS = $(OBJS:%.o=%.f)
!           # ftnchek project files:
!           PRJS = $(OBJS:%.o=%.prj)
!           
!           # Build the program
!           prog: $(OBJS) ; \
!             $(FC) -o $ $(OBJS)
!           
!           chekall: $(PRJS) ; \
!             ftnchek $(CHEKFLAGS) $(PRJS)
!           
!           prjs: $(PRJS)
!           
!           # For Emacs M-x find-tag:
!           TAGS: $(SRCS) ; \
!             etags $(SRCS)
!           
!           # Rebuild dependencies:
!           depend: ; \
!             sfmakedepend -I $(PLTLIBDIR) -I includes -a prj $(SRCS1)
! 
!    * Try your code out using other Fortran compilers, such as `f2c'.
!      If it does not work on at least one other compiler (assuming the
!      compiler supports the features the code needs), that is a strong
!      indicator of a bug in the code.
! 
!      However, even if your code works on many compilers _except_ `g77',
!      that does _not_ mean the bug is in `g77'.  It might mean the bug
!      is in your code, and that `g77' simply exposes it more readily
!      than other compilers.
! 
! 
! File: g77.info,  Node: Bug Lists,  Next: Bug Reporting,  Prev: Bug Criteria,  Up: Bugs
! 
! Where to Report Bugs
! ====================
! 
!    Send bug reports for GNU Fortran to <gcc-bugs@gcc.gnu.org or
! bug-gcc@gnu.org>.
! 
!    Often people think of posting bug reports to a newsgroup instead of
! mailing them.  This sometimes appears to work, but it has one problem
! which can be crucial: a newsgroup posting does not contain a mail path
! back to the sender.  Thus, if maintainers need more information, they
! might be unable to reach you.  For this reason, you should always send
! bug reports by mail to the proper mailing list.
! 
!    As a last resort, send bug reports on paper to:
! 
!      GNU Compiler Bugs
!      Free Software Foundation
!      59 Temple Place - Suite 330
!      Boston, MA 02111-1307, USA
! 
! 
! File: g77.info,  Node: Bug Reporting,  Prev: Bug Lists,  Up: Bugs
! 
! How to Report Bugs
! ==================
! 
!    The fundamental principle of reporting bugs usefully is this:
! *report all the facts*.  If you are not sure whether to state a fact or
! leave it out, state it!
! 
!    Often people omit facts because they think they know what causes the
! problem and they conclude that some details don't matter.  Thus, you
! might assume that the name of the variable you use in an example does
! not matter.  Well, probably it doesn't, but one cannot be sure.
! Perhaps the bug is a stray memory reference which happens to fetch from
! the location where that name is stored in memory; perhaps, if the name
! were different, the contents of that location would fool the compiler
! into doing the right thing despite the bug.  Play it safe and give a
! specific, complete example.  That is the easiest thing for you to do,
! and the most helpful.
! 
!    Keep in mind that the purpose of a bug report is to enable someone to
! fix the bug if it is not known.  It isn't very important what happens if
! the bug is already known.  Therefore, always write your bug reports on
! the assumption that the bug is not known.
! 
!    Sometimes people give a few sketchy facts and ask, "Does this ring a
! bell?"  This cannot help us fix a bug, so it is rarely helpful.  We
! respond by asking for enough details to enable us to investigate.  You
! might as well expedite matters by sending them to begin with.
! (Besides, there are enough bells ringing around here as it is.)
! 
!    Try to make your bug report self-contained.  If we have to ask you
! for more information, it is best if you include all the previous
! information in your response, as well as the information that was
! missing.
! 
!    Please report each bug in a separate message.  This makes it easier
! for us to track which bugs have been fixed and to forward your bugs
! reports to the appropriate maintainer.
! 
!    Do not compress and encode any part of your bug report using programs
! such as `uuencode'.  If you do so it will slow down the processing of
! your bug.  If you must submit multiple large files, use `shar', which
! allows us to read your message without having to run any decompression
! programs.
! 
!    (As a special exception for GNU Fortran bug-reporting, at least for
! now, if you are sending more than a few lines of code, if your
! program's source file format contains "interesting" things like
! trailing spaces or strange characters, or if you need to include binary
! data files, it is acceptable to put all the files together in a `tar'
! archive, and, whether you need to do that, it is acceptable to then
! compress the single file (`tar' archive or source file) using `gzip'
! and encode it via `uuencode'.  Do not use any MIME stuff--the current
! maintainer can't decode this.  Using `compress' instead of `gzip' is
! acceptable, assuming you have licensed the use of the patented
! algorithm in `compress' from Unisys.)
! 
!    To enable someone to investigate the bug, you should include all
! these things:
! 
!    * The version of GNU Fortran.  You can get this by running `g77'
!      with the `-v' option.  (Ignore any error messages that might be
!      displayed when the linker is run.)
! 
!      Without this, we won't know whether there is any point in looking
!      for the bug in the current version of GNU Fortran.
! 
!    * A complete input file that will reproduce the bug.
! 
!      If your source file(s) require preprocessing (for example, their
!      names have suffixes like `.F', `.fpp', `.FPP', and `.r'), and the
!      bug is in the compiler proper (`f771') or in a subsequent phase of
!      processing, run your source file through the C preprocessor by
!      doing `g77 -E SOURCEFILE > NEWFILE'.  Then, include the contents
!      of NEWFILE in the bug report.  (When you do this, use the same
!      preprocessor options--such as `-I', `-D', and `-U'--that you used
!      in actual compilation.)
! 
!      A single statement is not enough of an example.  In order to
!      compile it, it must be embedded in a complete file of compiler
!      input.  The bug might depend on the details of how this is done.
! 
!      Without a real example one can compile, all anyone can do about
!      your bug report is wish you luck.  It would be futile to try to
!      guess how to provoke the bug.  For example, bugs in register
!      allocation and reloading can depend on every little detail of the
!      source and include files that trigger them.
! 
!    * Note that you should include with your bug report any files
!      included by the source file (via the `#include' or `INCLUDE'
!      directive) that you send, and any files they include, and so on.
! 
!      It is not necessary to replace the `#include' and `INCLUDE'
!      directives with the actual files in the version of the source file
!      that you send, but it might make submitting the bug report easier
!      in the end.  However, be sure to _reproduce_ the bug using the
!      _exact_ version of the source material you submit, to avoid
!      wild-goose chases.
! 
!    * The command arguments you gave GNU Fortran to compile that example
!      and observe the bug.  For example, did you use `-O'?  To guarantee
!      you won't omit something important, list all the options.
! 
!      If we were to try to guess the arguments, we would probably guess
!      wrong and then we would not encounter the bug.
! 
!    * The type of machine you are using, and the operating system name
!      and version number.  (Much of this information is printed by `g77
!      -v'--if you include that, send along any additional info you have
!      that you don't see clearly represented in that output.)
! 
!    * The operands you gave to the `configure' command when you installed
!      the compiler.
! 
!    * A complete list of any modifications you have made to the compiler
!      source.  (We don't promise to investigate the bug unless it
!      happens in an unmodified compiler.  But if you've made
!      modifications and don't tell us, then you are sending us on a
!      wild-goose chase.)
! 
!      Be precise about these changes.  A description in English is not
!      enough--send a context diff for them.
! 
!      Adding files of your own (such as a machine description for a
!      machine we don't support) is a modification of the compiler source.
! 
!    * Details of any other deviations from the standard procedure for
!      installing GNU Fortran.
! 
!    * A description of what behavior you observe that you believe is
!      incorrect.  For example, "The compiler gets a fatal signal," or,
!      "The assembler instruction at line 208 in the output is incorrect."
! 
!      Of course, if the bug is that the compiler gets a fatal signal,
!      then one can't miss it.  But if the bug is incorrect output, the
!      maintainer might not notice unless it is glaringly wrong.  None of
!      us has time to study all the assembler code from a 50-line Fortran
!      program just on the chance that one instruction might be wrong.
!      We need _you_ to do this part!
! 
!      Even if the problem you experience is a fatal signal, you should
!      still say so explicitly.  Suppose something strange is going on,
!      such as, your copy of the compiler is out of synch, or you have
!      encountered a bug in the C library on your system.  (This has
!      happened!)  Your copy might crash and the copy here would not.  If
!      you said to expect a crash, then when the compiler here fails to
!      crash, we would know that the bug was not happening.  If you don't
!      say to expect a crash, then we would not know whether the bug was
!      happening.  We would not be able to draw any conclusion from our
!      observations.
! 
!      If the problem is a diagnostic when building GNU Fortran with some
!      other compiler, say whether it is a warning or an error.
! 
!      Often the observed symptom is incorrect output when your program
!      is run.  Sad to say, this is not enough information unless the
!      program is short and simple.  None of us has time to study a large
!      program to figure out how it would work if compiled correctly,
!      much less which line of it was compiled wrong.  So you will have
!      to do that.  Tell us which source line it is, and what incorrect
!      result happens when that line is executed.  A person who
!      understands the program can find this as easily as finding a bug
!      in the program itself.
! 
!    * If you send examples of assembler code output from GNU Fortran,
!      please use `-g' when you make them.  The debugging information
!      includes source line numbers which are essential for correlating
!      the output with the input.
! 
!    * If you wish to mention something in the GNU Fortran source, refer
!      to it by context, not by line number.
! 
!      The line numbers in the development sources don't match those in
!      your sources.  Your line numbers would convey no convenient
!      information to the maintainers.
! 
!    * Additional information from a debugger might enable someone to
!      find a problem on a machine which he does not have available.
!      However, you need to think when you collect this information if
!      you want it to have any chance of being useful.
! 
!      For example, many people send just a backtrace, but that is never
!      useful by itself.  A simple backtrace with arguments conveys little
!      about GNU Fortran because the compiler is largely data-driven; the
!      same functions are called over and over for different RTL insns,
!      doing different things depending on the details of the insn.
! 
!      Most of the arguments listed in the backtrace are useless because
!      they are pointers to RTL list structure.  The numeric values of the
!      pointers, which the debugger prints in the backtrace, have no
!      significance whatever; all that matters is the contents of the
!      objects they point to (and most of the contents are other such
!      pointers).
! 
!      In addition, most compiler passes consist of one or more loops that
!      scan the RTL insn sequence.  The most vital piece of information
!      about such a loop--which insn it has reached--is usually in a
!      local variable, not in an argument.
! 
!      What you need to provide in addition to a backtrace are the values
!      of the local variables for several stack frames up.  When a local
!      variable or an argument is an RTX, first print its value and then
!      use the GDB command `pr' to print the RTL expression that it points
!      to.  (If GDB doesn't run on your machine, use your debugger to call
!      the function `debug_rtx' with the RTX as an argument.)  In
!      general, whenever a variable is a pointer, its value is no use
!      without the data it points to.
! 
!    Here are some things that are not necessary:
! 
!    * A description of the envelope of the bug.
! 
!      Often people who encounter a bug spend a lot of time investigating
!      which changes to the input file will make the bug go away and which
!      changes will not affect it.
! 
!      This is often time consuming and not very useful, because the way
!      we will find the bug is by running a single example under the
!      debugger with breakpoints, not by pure deduction from a series of
!      examples.  You might as well save your time for something else.
! 
!      Of course, if you can find a simpler example to report _instead_ of
!      the original one, that is a convenience.  Errors in the output
!      will be easier to spot, running under the debugger will take less
!      time, etc.  Most GNU Fortran bugs involve just one function, so
!      the most straightforward way to simplify an example is to delete
!      all the function definitions except the one where the bug occurs.
!      Those earlier in the file may be replaced by external declarations
!      if the crucial function depends on them.  (Exception: inline
!      functions might affect compilation of functions defined later in
!      the file.)
! 
!      However, simplification is not vital; if you don't want to do this,
!      report the bug anyway and send the entire test case you used.
! 
!    * In particular, some people insert conditionals `#ifdef BUG' around
!      a statement which, if removed, makes the bug not happen.  These
!      are just clutter; we won't pay any attention to them anyway.
!      Besides, you should send us preprocessor output, and that can't
!      have conditionals.
! 
!    * A patch for the bug.
! 
!      A patch for the bug is useful if it is a good one.  But don't omit
!      the necessary information, such as the test case, on the
!      assumption that a patch is all we need.  We might see problems
!      with your patch and decide to fix the problem another way, or we
!      might not understand it at all.
! 
!      Sometimes with a program as complicated as GNU Fortran it is very
!      hard to construct an example that will make the program follow a
!      certain path through the code.  If you don't send the example, we
!      won't be able to construct one, so we won't be able to verify that
!      the bug is fixed.
! 
!      And if we can't understand what bug you are trying to fix, or why
!      your patch should be an improvement, we won't install it.  A test
!      case will help us to understand.
! 
!      See `http://gcc.gnu.org/contribute.html' for guidelines on how to
!      make it easy for us to understand and install your patches.
! 
!    * A guess about what the bug is or what it depends on.
! 
!      Such guesses are usually wrong.  Even the maintainer can't guess
!      right about such things without first using the debugger to find
!      the facts.
! 
!    * A core dump file.
! 
!      We have no way of examining a core dump for your type of machine
!      unless we have an identical system--and if we do have one, we
!      should be able to reproduce the crash ourselves.
! 
! 
! File: g77.info,  Node: Service,  Next: Adding Options,  Prev: Bugs,  Up: Top
! 
! How To Get Help with GNU Fortran
! ********************************
! 
!    If you need help installing, using or changing GNU Fortran, there
! are two ways to find it:
! 
!    * Look in the service directory for someone who might help you for a
!      fee.  The service directory is found in the file named `SERVICE'
!      in the GNU CC distribution.
! 
!    * Send a message to <gcc-help@gcc.gnu.org>.
! 
! 
! File: g77.info,  Node: Adding Options,  Next: Projects,  Prev: Service,  Up: Top
! 
! Adding Options
! **************
! 
!    To add a new command-line option to `g77', first decide what kind of
! option you wish to add.  Search the `g77' and `gcc' documentation for
! one or more options that is most closely like the one you want to add
! (in terms of what kind of effect it has, and so on) to help clarify its
! nature.
! 
!    * _Fortran options_ are options that apply only when compiling
!      Fortran programs.  They are accepted by `g77' and `gcc', but they
!      apply only when compiling Fortran programs.
! 
!    * _Compiler options_ are options that apply when compiling most any
!      kind of program.
! 
!    _Fortran options_ are listed in the file `gcc/gcc/f/lang-options.h',
! which is used during the build of `gcc' to build a list of all options
! that are accepted by at least one language's compiler.  This list goes
! into the `documented_lang_options' array in `gcc/toplev.c', which uses
! this array to determine whether a particular option should be offered
! to the linked-in front end for processing by calling
! `lang_option_decode', which, for `g77', is in `gcc/gcc/f/com.c' and just
! calls `ffe_decode_option'.
! 
!    If the linked-in front end "rejects" a particular option passed to
! it, `toplev.c' just ignores the option, because _some_ language's
! compiler is willing to accept it.
! 
!    This allows commands like `gcc -fno-asm foo.c bar.f' to work, even
! though Fortran compilation does not currently support the `-fno-asm'
! option; even though the `f771' version of `lang_decode_option' rejects
! `-fno-asm', `toplev.c' doesn't produce a diagnostic because some other
! language (C) does accept it.
! 
!    This also means that commands like `g77 -fno-asm foo.f' yield no
! diagnostics, despite the fact that no phase of the command was able to
! recognize and process `-fno-asm'--perhaps a warning about this would be
! helpful if it were possible.
! 
!    Code that processes Fortran options is found in `gcc/gcc/f/top.c',
! function `ffe_decode_option'.  This code needs to check positive and
! negative forms of each option.
! 
!    The defaults for Fortran options are set in their global
! definitions, also found in `gcc/gcc/f/top.c'.  Many of these defaults
! are actually macros defined in `gcc/gcc/f/target.h', since they might be
! machine-specific.  However, since, in practice, GNU compilers should
! behave the same way on all configurations (especially when it comes to
! language constructs), the practice of setting defaults in `target.h' is
! likely to be deprecated and, ultimately, stopped in future versions of
! `g77'.
! 
!    Accessor macros for Fortran options, used by code in the `g77' FFE,
! are defined in `gcc/gcc/f/top.h'.
! 
!    _Compiler options_ are listed in `gcc/toplev.c' in the array
! `f_options'.  An option not listed in `lang_options' is looked up in
! `f_options' and handled from there.
! 
!    The defaults for compiler options are set in the global definitions
! for the corresponding variables, some of which are in `gcc/toplev.c'.
! 
!    You can set different defaults for _Fortran-oriented_ or
! _Fortran-reticent_ compiler options by changing the source code of
! `g77' and rebuilding.  How to do this depends on the version of `g77':
! 
! `G77 0.5.24 (EGCS 1.1)'
! `G77 0.5.25 (EGCS 1.2 - which became GCC 2.95)'
!      Change the `lang_init_options' routine in `gcc/gcc/f/com.c'.
! 
!      (Note that these versions of `g77' perform internal consistency
!      checking automatically when the `-fversion' option is specified.)
! 
! `G77 0.5.23'
! `G77 0.5.24 (EGCS 1.0)'
!      Change the way `f771' handles the `-fset-g77-defaults' option,
!      which is always provided as the first option when called by `g77'
!      or `gcc'.
! 
!      This code is in `ffe_decode_options' in `gcc/gcc/f/top.c'.  Have
!      it change just the variables that you want to default to a
!      different setting for Fortran compiles compared to compiles of
!      other languages.
! 
!      The `-fset-g77-defaults' option is passed to `f771' automatically
!      because of the specification information kept in
!      `gcc/gcc/f/lang-specs.h'.  This file tells the `gcc' command how
!      to recognize, in this case, Fortran source files (those to be
!      preprocessed, and those that are not), and further, how to invoke
!      the appropriate programs (including `f771') to process those
!      source files.
! 
!      It is in `gcc/gcc/f/lang-specs.h' that `-fset-g77-defaults',
!      `-fversion', and other options are passed, as appropriate, even
!      when the user has not explicitly specified them.  Other "internal"
!      options such as `-quiet' also are passed via this mechanism.
! 
! 
! File: g77.info,  Node: Projects,  Next: Front End,  Prev: Adding Options,  Up: Top
! 
! Projects
! ********
! 
!    If you want to contribute to `g77' by doing research, design,
! specification, documentation, coding, or testing, the following
! information should give you some ideas.  More relevant information
! might be available from `ftp://alpha.gnu.org/gnu/g77/projects/'.
! 
! * Menu:
! 
! * Efficiency::               Make `g77' itself compile code faster.
! * Better Optimization::      Teach `g77' to generate faster code.
! * Simplify Porting::         Make `g77' easier to configure, build,
!                              and install.
! * More Extensions::          Features many users won't know to ask for.
! * Machine Model::            `g77' should better leverage `gcc'.
! * Internals Documentation::  Make maintenance easier.
! * Internals Improvements::   Make internals more robust.
! * Better Diagnostics::       Make using `g77' on new code easier.
! 
! 
! File: g77.info,  Node: Efficiency,  Next: Better Optimization,  Up: Projects
! 
! Improve Efficiency
! ==================
! 
!    Don't bother doing any performance analysis until most of the
! following items are taken care of, because there's no question they
! represent serious space/time problems, although some of them show up
! only given certain kinds of (popular) input.
! 
!    * Improve `malloc' package and its uses to specify more info about
!      memory pools and, where feasible, use obstacks to implement them.
! 
!    * Skip over uninitialized portions of aggregate areas (arrays,
!      `COMMON' areas, `EQUIVALENCE' areas) so zeros need not be output.
!      This would reduce memory usage for large initialized aggregate
!      areas, even ones with only one initialized element.
! 
!      As of version 0.5.18, a portion of this item has already been
!      accomplished.
! 
!    * Prescan the statement (in `sta.c') so that the nature of the
!      statement is determined as much as possible by looking entirely at
!      its form, and not looking at any context (previous statements,
!      including types of symbols).  This would allow ripping out of the
!      statement-confirmation, symbol retraction/confirmation, and
!      diagnostic inhibition mechanisms.  Plus, it would result in
!      much-improved diagnostics.  For example, `CALL
!      some-intrinsic(...)', where the intrinsic is not a subroutine
!      intrinsic, would result actual error instead of the
!      unimplemented-statement catch-all.
! 
!    * Throughout `g77', don't pass line/column pairs where a simple
!      `ffewhere' type, which points to the error as much as is desired
!      by the configuration, will do, and don't pass `ffelexToken' types
!      where a simple `ffewhere' type will do.  Then, allow new default
!      configuration of `ffewhere' such that the source line text is not
!      preserved, and leave it to things like Emacs' next-error function
!      to point to them (now that `next-error' supports column, or,
!      perhaps, character-offset, numbers).  The change in calling
!      sequences should improve performance somewhat, as should not
!      having to save source lines.  (Whether this whole item will
!      improve performance is questionable, but it should improve
!      maintainability.)
! 
!    * Handle `DATA (A(I),I=1,1000000)/1000000*2/' more efficiently,
!      especially as regards the assembly output.  Some of this might
!      require improving the back end, but lots of improvement in
!      space/time required in `g77' itself can be fairly easily obtained
!      without touching the back end.  Maybe type-conversion, where
!      necessary, can be speeded up as well in cases like the one shown
!      (converting the `2' into `2.').
! 
!    * If analysis shows it to be worthwhile, optimize `lex.c'.
! 
!    * Consider redesigning `lex.c' to not need any feedback during
!      tokenization, by keeping track of enough parse state on its own.
! 
! 
! File: g77.info,  Node: Better Optimization,  Next: Simplify Porting,  Prev: Efficiency,  Up: Projects
! 
! Better Optimization
! ===================
! 
!    Much of this work should be put off until after `g77' has all the
! features necessary for its widespread acceptance as a useful F77
! compiler.  However, perhaps this work can be done in parallel during
! the feature-adding work.
! 
!    * Do the equivalent of the trick of putting `extern inline' in front
!      of every function definition in `libg2c' and #include'ing the
!      resulting file in `f2c'+`gcc'--that is, inline all
!      run-time-library functions that are at all worth inlining.  (Some
!      of this has already been done, such as for integral
!      exponentiation.)
! 
!    * When doing `CHAR_VAR = CHAR_FUNC(...)', and it's clear that types
!      line up and `CHAR_VAR' is addressable or not a `VAR_DECL', make
!      `CHAR_VAR', not a temporary, be the receiver for `CHAR_FUNC'.
!      (This is now done for `COMPLEX' variables.)
! 
!    * Design and implement Fortran-specific optimizations that don't
!      really belong in the back end, or where the front end needs to
!      give the back end more info than it currently does.
! 
!    * Design and implement a new run-time library interface, with the
!      code going into `libgcc' so no special linking is required to link
!      Fortran programs using standard language features.  This library
!      would speed up lots of things, from I/O (using precompiled formats,
!      doing just one, or, at most, very few, calls for arrays or array
!      sections, and so on) to general computing (array/section
!      implementations of various intrinsics, implementation of commonly
!      performed loops that aren't likely to be optimally compiled
!      otherwise, etc.).
! 
!      Among the important things the library would do are:
! 
!         * Be a one-stop-shop-type library, hence shareable and usable
!           by all, in that what are now library-build-time options in
!           `libg2c' would be moved at least to the `g77' compile phase,
!           if not to finer grains (such as choosing how list-directed
!           I/O formatting is done by default at `OPEN' time, for
!           preconnected units via options or even statements in the main
!           program unit, maybe even on a per-I/O basis with appropriate
!           pragma-like devices).
! 
!    * Probably requiring the new library design, change interface to
!      normally have `COMPLEX' functions return their values in the way
!      `gcc' would if they were declared `__complex__ float', rather than
!      using the mechanism currently used by `CHARACTER' functions
!      (whereby the functions are compiled as returning void and their
!      first arg is a pointer to where to store the result).  (Don't
!      append underscores to external names for `COMPLEX' functions in
!      some cases once `g77' uses `gcc' rather than `f2c' calling
!      conventions.)
! 
!    * Do something useful with `doiter' references where possible.  For
!      example, `CALL FOO(I)' cannot modify `I' if within a `DO' loop
!      that uses `I' as the iteration variable, and the back end might
!      find that info useful in determining whether it needs to read `I'
!      back into a register after the call.  (It normally has to do that,
!      unless it knows `FOO' never modifies its passed-by-reference
!      argument, which is rarely the case for Fortran-77 code.)
! 
! 
! File: g77.info,  Node: Simplify Porting,  Next: More Extensions,  Prev: Better Optimization,  Up: Projects
! 
! Simplify Porting
! ================
! 
!    Making `g77' easier to configure, port, build, and install, either
! as a single-system compiler or as a cross-compiler, would be very
! useful.
! 
!    * A new library (replacing `libg2c') should improve portability as
!      well as produce more optimal code.  Further, `g77' and the new
!      library should conspire to simplify naming of externals, such as
!      by removing unnecessarily added underscores, and to
!      reduce/eliminate the possibility of naming conflicts, while making
!      debugger more straightforward.
! 
!      Also, it should make multi-language applications more feasible,
!      such as by providing Fortran intrinsics that get Fortran unit
!      numbers given C `FILE *' descriptors.
! 
!    * Possibly related to a new library, `g77' should produce the
!      equivalent of a `gcc' `main(argc, argv)' function when it compiles
!      a main program unit, instead of compiling something that must be
!      called by a library implementation of `main()'.
! 
!      This would do many useful things such as provide more flexibility
!      in terms of setting up exception handling, not requiring
!      programmers to start their debugging sessions with `breakpoint
!      MAIN__' followed by `run', and so on.
! 
!    * The GBE needs to understand the difference between alignment
!      requirements and desires.  For example, on Intel x86 machines,
!      `g77' currently imposes overly strict alignment requirements, due
!      to the back end, but it would be useful for Fortran and C
!      programmers to be able to override these _recommendations_ as long
!      as they don't violate the actual processor _requirements_.
! 
! 
! File: g77.info,  Node: More Extensions,  Next: Machine Model,  Prev: Simplify Porting,  Up: Projects
! 
! More Extensions
! ===============
! 
!    These extensions are not the sort of things users ask for "by name",
! but they might improve the usability of `g77', and Fortran in general,
! in the long run.  Some of these items really pertain to improving `g77'
! internals so that some popular extensions can be more easily supported.
! 
!    * Look through all the documentation on the GNU Fortran language,
!      dialects, compiler, missing features, bugs, and so on.  Many
!      mentions of incomplete or missing features are sprinkled
!      throughout.  It is not worth repeating them here.
! 
!    * Consider adding a `NUMERIC' type to designate typeless numeric
!      constants, named and unnamed.  The idea is to provide a
!      forward-looking, effective replacement for things like the
!      old-style `PARAMETER' statement when people really need
!      typelessness in a maintainable, portable, clearly documented way.
!      Maybe `TYPELESS' would include `CHARACTER', `POINTER', and
!      whatever else might come along.  (This is not really a call for
!      polymorphism per se, just an ability to express limited, syntactic
!      polymorphism.)
! 
!    * Support `OPEN(...,KEY=(...),...)'.
! 
!    * Support arbitrary file unit numbers, instead of limiting them to 0
!      through `MXUNIT-1'.  (This is a `libg2c' issue.)
! 
!    * `OPEN(NOSPANBLOCKS,...)' is treated as
!      `OPEN(UNIT=NOSPANBLOCKS,...)', so a later `UNIT=' in the first
!      example is invalid.  Make sure this is what users of this feature
!      would expect.
! 
!    * Currently `g77' disallows `READ(1'10)' since it is an obnoxious
!      syntax, but supporting it might be pretty easy if needed.  More
!      details are needed, such as whether general expressions separated
!      by an apostrophe are supported, or maybe the record number can be
!      a general expression, and so on.
! 
!    * Support `STRUCTURE', `UNION', `MAP', and `RECORD' fully.
!      Currently there is no support at all for `%FILL' in `STRUCTURE'
!      and related syntax, whereas the rest of the stuff has at least
!      some parsing support.  This requires either major changes to
!      `libg2c' or its replacement.
! 
!    * F90 and `g77' probably disagree about label scoping relative to
!      `INTERFACE' and `END INTERFACE', and their contained procedure
!      interface bodies (blocks?).
! 
!    * `ENTRY' doesn't support F90 `RESULT()' yet, since that was added
!      after S8.112.
! 
!    * Empty-statement handling (10 ;;CONTINUE;;) probably isn't
!      consistent with the final form of the standard (it was vague at
!      S8.112).
! 
!    * It seems to be an "open" question whether a file, immediately
!      after being `OPEN'ed,is positioned at the beginning, the end, or
!      wherever--it might be nice to offer an option of opening to
!      "undefined" status, requiring an explicit absolute-positioning
!      operation to be performed before any other (besides `CLOSE') to
!      assist in making applications port to systems (some IBM?) that
!      `OPEN' to the end of a file or some such thing.
! 
! 
! File: g77.info,  Node: Machine Model,  Next: Internals Documentation,  Prev: More Extensions,  Up: Projects
! 
! Machine Model
! =============
! 
!    This items pertain to generalizing `g77''s view of the machine model
! to more fully accept whatever the GBE provides it via its configuration.
! 
!    * Switch to using `REAL_VALUE_TYPE' to represent floating-point
!      constants exclusively so the target float format need not be
!      required.  This means changing the way `g77' handles
!      initialization of aggregate areas having more than one type, such
!      as `REAL' and `INTEGER', because currently it initializes them as
!      if they were arrays of `char' and uses the bit patterns of the
!      constants of the various types in them to determine what to stuff
!      in elements of the arrays.
! 
!    * Rely more and more on back-end info and capabilities, especially
!      in the area of constants (where having the `g77' front-end's IL
!      just store the appropriate tree nodes containing constants might
!      be best).
! 
!    * Suite of C and Fortran programs that a user/administrator can run
!      on a machine to help determine the configuration for `g77' before
!      building and help determine if the compiler works (especially with
!      whatever libraries are installed) after building.
! 
! 
! File: g77.info,  Node: Internals Documentation,  Next: Internals Improvements,  Prev: Machine Model,  Up: Projects
! 
! Internals Documentation
! =======================
! 
!    Better info on how `g77' works and how to port it is needed.
! 
!    *Note Front End::, which contains some information on `g77'
! internals.
! 
! 
! File: g77.info,  Node: Internals Improvements,  Next: Better Diagnostics,  Prev: Internals Documentation,  Up: Projects
! 
! Internals Improvements
! ======================
! 
!    Some more items that would make `g77' more reliable and easier to
! maintain:
! 
!    * Generally make expression handling focus more on critical syntax
!      stuff, leaving semantics to callers.  For example, anything a
!      caller can check, semantically, let it do so, rather than having
!      `expr.c' do it.  (Exceptions might include things like diagnosing
!      `FOO(I--K:)=BAR' where `FOO' is a `PARAMETER'--if it seems
!      important to preserve the left-to-right-in-source order of
!      production of diagnostics.)
! 
!    * Come up with better naming conventions for `-D' to establish
!      requirements to achieve desired implementation dialect via
!      `proj.h'.
! 
!    * Clean up used tokens and `ffewhere's in `ffeglobal_terminate_1'.
! 
!    * Replace `sta.c' `outpooldisp' mechanism with `malloc_pool_use'.
! 
!    * Check for `opANY' in more places in `com.c', `std.c', and `ste.c',
!      and get rid of the `opCONVERT(opANY)' kludge (after determining if
!      there is indeed no real need for it).
! 
!    * Utility to read and check `bad.def' messages and their references
!      in the code, to make sure calls are consistent with message
!      templates.
! 
!    * Search and fix `&ffe...' and similar so that `ffe...ptr...' macros
!      are available instead (a good argument for wishing this could have
!      written all this stuff in C++, perhaps).  On the other hand, it's
!      questionable whether this sort of improvement is really necessary,
!      given the availability of tools such as Emacs and Perl, which make
!      finding any address-taking of structure members easy enough?
! 
!    * Some modules truly export the member names of their structures
!      (and the structures themselves), maybe fix this, and fix other
!      modules that just appear to as well (by appending `_', though it'd
!      be ugly and probably not worth the time).
! 
!    * Implement C macros `RETURNS(value)' and `SETS(something,value)' in
!      `proj.h' and use them throughout `g77' source code (especially in
!      the definitions of access macros in `.h' files) so they can be
!      tailored to catch code writing into a `RETURNS()' or reading from
!      a `SETS()'.
! 
!    * Decorate throughout with `const' and other such stuff.
! 
!    * All F90 notational derivations in the source code are still based
!      on the S8.112 version of the draft standard.  Probably should
!      update to the official standard, or put documentation of the rules
!      as used in the code...uh...in the code.
! 
!    * Some `ffebld_new' calls (those outside of `ffeexpr.c' or inside
!      but invoked via paths not involving `ffeexpr_lhs' or
!      `ffeexpr_rhs') might be creating things in improper pools, leading
!      to such things staying around too long or (doubtful, but possible
!      and dangerous) not long enough.
! 
!    * Some `ffebld_list_new' (or whatever) calls might not be matched by
!      `ffebld_list_bottom' (or whatever) calls, which might someday
!      matter.  (It definitely is not a problem just yet.)
! 
!    * Probably not doing clean things when we fail to `EQUIVALENCE'
!      something due to alignment/mismatch or other problems--they end up
!      without `ffestorag' objects, so maybe the backend (and other parts
!      of the front end) can notice that and handle like an `opANY' (do
!      what it wants, just don't complain or crash).  Most of this seems
!      to have been addressed by now, but a code review wouldn't hurt.
! 
! 
! File: g77.info,  Node: Better Diagnostics,  Prev: Internals Improvements,  Up: Projects
! 
! Better Diagnostics
! ==================
! 
!    These are things users might not ask about, or that need to be
! looked into, before worrying about.  Also here are items that involve
! reducing unnecessary diagnostic clutter.
! 
!    * When `FUNCTION' and `ENTRY' point types disagree (`CHARACTER'
!      lengths, type classes, and so on), `ANY'-ize the offending `ENTRY'
!      point and any _new_ dummies it specifies.
! 
!    * Speed up and improve error handling for data when repeat-count is
!      specified.  For example, don't output 20 unnecessary messages
!      after the first necessary one for:
! 
!           INTEGER X(20)
!           CONTINUE
!           DATA (X(I), J= 1, 20) /20*5/
!           END
! 
!      (The `CONTINUE' statement ensures the `DATA' statement is
!      processed in the context of executable, not specification,
!      statements.)
! 
! 
! File: g77.info,  Node: Front End,  Next: Diagnostics,  Prev: Projects,  Up: Top
! 
! Front End
! *********
! 
!    This chapter describes some aspects of the design and implementation
! of the `g77' front end.
! 
!    To find about things that are "To Be Determined" or "To Be Done",
! search for the string TBD.  If you want to help by working on one or
! more of these items, email <gcc@gcc.gnu.org>.  If you're planning to do
! more than just research issues and offer comments, see
! `http://gcc.gnu.org/contribute.html' for steps you might need to take
! first.
! 
! * Menu:
! 
! * Overview of Sources::
! * Overview of Translation Process::
! * Philosophy of Code Generation::
! * Two-pass Design::
! * Challenges Posed::
! * Transforming Statements::
! * Transforming Expressions::
! * Internal Naming Conventions::
! 
! 
! File: g77.info,  Node: Overview of Sources,  Next: Overview of Translation Process,  Up: Front End
! 
! Overview of Sources
! ===================
! 
!    The current directory layout includes the following:
! 
! `{No value for `srcdir'}/gcc/'
!      Non-g77 files in gcc
! 
! `{No value for `srcdir'}/gcc/f/'
!      GNU Fortran front end sources
! 
! `{No value for `srcdir'}/libf2c/'
!      `libg2c' configuration and `g2c.h' file generation
! 
! `{No value for `srcdir'}/libf2c/libF77/'
!      General support and math portion of `libg2c'
! 
! `{No value for `srcdir'}/libf2c/libI77/'
!      I/O portion of `libg2c'
! 
! `{No value for `srcdir'}/libf2c/libU77/'
!      Additional interfaces to Unix `libc' for `libg2c'
! 
!    Components of note in `g77' are described below.
! 
!    `f/' as a whole contains the source for `g77', while `libf2c/'
! contains a portion of the separate program `f2c'.  Note that the
! `libf2c' code is not part of the program `g77', just distributed with
! it.
! 
!    `f/' contains text files that document the Fortran compiler, source
! files for the GNU Fortran Front End (FFE), and some other stuff.  The
! `g77' compiler code is placed in `f/' because it, along with its
! contents, is designed to be a subdirectory of a `gcc' source directory,
! `gcc/', which is structured so that language-specific front ends can be
! "dropped in" as subdirectories.  The C++ front end (`g++'), is an
! example of this--it resides in the `cp/' subdirectory.  Note that the C
! front end (also referred to as `gcc') is an exception to this, as its
! source files reside in the `gcc/' directory itself.
! 
!    `libf2c/' contains the run-time libraries for the `f2c' program,
! also used by `g77'.  These libraries normally referred to collectively
! as `libf2c'.  When built as part of `g77', `libf2c' is installed under
! the name `libg2c' to avoid conflict with any existing version of
! `libf2c', and thus is often referred to as `libg2c' when the `g77'
! version is specifically being referred to.
! 
!    The `netlib' version of `libf2c/' contains two distinct libraries,
! `libF77' and `libI77', each in their own subdirectories.  In `g77',
! this distinction is not made, beyond maintaining the subdirectory
! structure in the source-code tree.
! 
!    `libf2c/' is not part of the program `g77', just distributed with it.
! It contains files not present in the official (`netlib') version of
! `libf2c', and also contains some minor changes made from `libf2c', to
! fix some bugs, and to facilitate automatic configuration, building, and
! installation of `libf2c' (as `libg2c') for use by `g77' users.  See
! `libf2c/README' for more information, including licensing conditions
! governing distribution of programs containing code from `libg2c'.
! 
!    `libg2c', `g77''s version of `libf2c', adds Dave Love's
! implementation of `libU77', in the `libf2c/libU77/' directory.  This
! library is distributed under the GNU Library General Public License
! (LGPL)--see the file `libf2c/libU77/COPYING.LIB' for more information,
! as this license governs distribution conditions for programs containing
! code from this portion of the library.
! 
!    Files of note in `f/' and `libf2c/' are described below:
! 
! `f/BUGS'
!      Lists some important bugs known to be in g77.  Or use Info (or GNU
!      Emacs Info mode) to read the "Actual Bugs" node of the `g77'
!      documentation:
! 
!           info -f f/g77.info -n "Actual Bugs"
! 
! `f/ChangeLog'
!      Lists recent changes to `g77' internals.
! 
! `libf2c/ChangeLog'
!      Lists recent changes to `libg2c' internals.
! 
! `f/NEWS'
!      Contains the per-release changes.  These include the user-visible
!      changes described in the node "Changes" in the `g77'
!      documentation, plus internal changes of import.  Or use:
! 
!           info -f f/g77.info -n News
! 
! `f/g77.info*'
!      The `g77' documentation, in Info format, produced by building
!      `g77'.
! 
!      All users of `g77' (not just installers) should read this, using
!      the `more' command if neither the `info' command, nor GNU Emacs
!      (with its Info mode), are available, or if users aren't yet
!      accustomed to using these tools.  All of these files are readable
!      as "plain text" files, though they're easier to navigate using
!      Info readers such as `info' and GNU Emacs Info mode.
! 
!    If you want to explore the FFE code, which lives entirely in `f/',
! here are a few clues.  The file `g77spec.c' contains the `g77'-specific
! source code for the `g77' command only--this just forms a variant of the
! `gcc' command, so, just as the `gcc' command itself does not contain
! the C front end, the `g77' command does not contain the Fortran front
! end (FFE).  The FFE code ends up in an executable named `f771', which
! does the actual compiling, so it contains the FFE plus the `gcc' back
! end (GBE), the latter to do most of the optimization, and the code
! generation.
! 
!    The file `parse.c' is the source file for `yyparse()', which is
! invoked by the GBE to start the compilation process, for `f771'.
! 
!    The file `top.c' contains the top-level FFE function `ffe_file' and
! it (along with top.h) define all `ffe_[a-z].*', `ffe[A-Z].*', and
! `FFE_[A-Za-z].*' symbols.
! 
!    The file `fini.c' is a `main()' program that is used when building
! the FFE to generate C header and source files for recognizing keywords.
! The files `malloc.c' and `malloc.h' comprise a memory manager that
! defines all `malloc_[a-z].*', `malloc[A-Z].*', and `MALLOC_[A-Za-z].*'
! symbols.
! 
!    All other modules named XYZ are comprised of all files named
! `XYZ*.EXT' and define all `ffeXYZ_[a-z].*', `ffeXYZ[A-Z].*', and
! `FFEXYZ_[A-Za-z].*' symbols.  If you understand all this,
! congratulations--it's easier for me to remember how it works than to
! type in these regular expressions.  But it does make it easy to find
! where a symbol is defined.  For example, the symbol
! `ffexyz_set_something' would be defined in `xyz.h' and implemented
! there (if it's a macro) or in `xyz.c'.
! 
!    The "porting" files of note currently are:
! 
! `proj.c'
! `proj.h'
!      This defines the "language" used by all the other source files,
!      the language being Standard C plus some useful things like
!      `ARRAY_SIZE' and such.
! 
! `target.c'
! `target.h'
!      These describe the target machine in terms of what data types are
!      supported, how they are denoted (to what C type does an
!      `INTEGER*8' map, for example), how to convert between them, and so
!      on.  Over time, versions of `g77' rely less on this file and more
!      on run-time configuration based on GBE info in `com.c'.
! 
! `com.c'
! `com.h'
!      These are the primary interface to the GBE.
! 
! `ste.c'
! `ste.h'
!      This contains code for implementing recognized executable
!      statements in the GBE.
! 
! `src.c'
! `src.h'
!      These contain information on the format(s) of source files (such
!      as whether they are never to be processed as case-insensitive with
!      regard to Fortran keywords).
! 
!    If you want to debug the `f771' executable, for example if it
! crashes, note that the global variables `lineno' and `input_filename'
! are usually set to reflect the current line being read by the lexer
! during the first-pass analysis of a program unit and to reflect the
! current line being processed during the second-pass compilation of a
! program unit.
! 
!    If an invocation of the function `ffestd_exec_end' is on the stack,
! the compiler is in the second pass, otherwise it is in the first.
! 
!    (This information might help you reduce a test case and/or work
! around a bug in `g77' until a fix is available.)
! 
! 
! File: g77.info,  Node: Overview of Translation Process,  Next: Philosophy of Code Generation,  Prev: Overview of Sources,  Up: Front End
! 
! Overview of Translation Process
! ===============================
! 
!    The order of phases translating source code to the form accepted by
! the GBE is:
! 
!   1. Stripping punched-card sources (`g77stripcard.c')
! 
!   2. Lexing (`lex.c')
! 
!   3. Stand-alone statement identification (`sta.c')
! 
!   4. INCLUDE handling (`sti.c')
! 
!   5. Order-dependent statement identification (`stq.c')
! 
!   6. Parsing (`stb.c' and `expr.c')
! 
!   7. Constructing (`stc.c')
! 
!   8. Collecting (`std.c')
! 
!   9. Expanding (`ste.c')
! 
!    To get a rough idea of how a particularly twisted Fortran statement
! gets treated by the passes, consider:
! 
!            FORMAT(I2 4H)=(J/
!           &   I3)
! 
!    The job of `lex.c' is to know enough about Fortran syntax rules to
! break the statement up into distinct lexemes without requiring any
! feedback from subsequent phases:
! 
!      `FORMAT'
!      `('
!      `I24H'
!      `)'
!      `='
!      `('
!      `J'
!      `/'
!      `I3'
!      `)'
! 
!    The job of `sta.c' is to figure out the kind of statement, or, at
! least, statement form, that sequence of lexemes represent.
! 
!    The sooner it can do this (in terms of using the smallest number of
! lexemes, starting with the first for each statement), the better,
! because that leaves diagnostics for problems beyond the recognition of
! the statement form to subsequent phases, which can usually better
! describe the nature of the problem.
! 
!    In this case, the `=' at "level zero" (not nested within parentheses)
! tells `sta.c' that this is an _assignment-form_, not `FORMAT',
! statement.
! 
!    An assignment-form statement might be a statement-function
! definition or an executable assignment statement.
! 
!    To make that determination, `sta.c' looks at the first two lexemes.
! 
!    Since the second lexeme is `(', the first must represent an array
! for this to be an assignment statement, else it's a statement function.
! 
!    Either way, `sta.c' hands off the statement to `stq.c' (via `sti.c',
! which expands INCLUDE files).  `stq.c' figures out what a statement
! that is, on its own, ambiguous, must actually be based on the context
! established by previous statements.
! 
!    So, `stq.c' watches the statement stream for executable statements,
! END statements, and so on, so it knows whether `A(B)=C' is (intended
! as) a statement-function definition or an assignment statement.
! 
!    After establishing the context-aware statement info, `stq.c' passes
! the original sample statement on to `stb.c' (either its
! statement-function parser or its assignment-statement parser).
! 
!    `stb.c' forms a statement-specific record containing the pertinent
! information.  That information includes a source expression and, for an
! assignment statement, a destination expression.  Expressions are parsed
! by `expr.c'.
! 
!    This record is passed to `stc.c', which copes with the implications
! of the statement within the context established by previous statements.
! 
!    For example, if it's the first statement in the file or after an
! `END' statement, `stc.c' recognizes that, first of all, a main program
! unit is now being lexed (and tells that to `std.c' before telling it
! about the current statement).
! 
!    `stc.c' attaches whatever information it can, usually derived from
! the context established by the preceding statements, and passes the
! information to `std.c'.
! 
!    `std.c' saves this information away, since the GBE cannot cope with
! information that might be incomplete at this stage.
! 
!    For example, `I3' might later be determined to be an argument to an
! alternate `ENTRY' point.
! 
!    When `std.c' is told about the end of an external (top-level)
! program unit, it passes all the information it has saved away on
! statements in that program unit to `ste.c'.
! 
!    `ste.c' "expands" each statement, in sequence, by constructing the
! appropriate GBE information and calling the appropriate GBE routines.
! 
!    Details on the transformational phases follow.  Keep in mind that
! Fortran numbering is used, so the first character on a line is column 1,
! decimal numbering is used, and so on.
! 
! * Menu:
! 
! * g77stripcard::
! * lex.c::
! * sta.c::
! * sti.c::
! * stq.c::
! * stb.c::
! * expr.c::
! * stc.c::
! * std.c::
! * ste.c::
! 
! * Gotchas (Transforming)::
! * TBD (Transforming)::
! 
! 
! File: g77.info,  Node: g77stripcard,  Next: lex.c,  Up: Overview of Translation Process
! 
! g77stripcard
! ------------
! 
!    The `g77stripcard' program handles removing content beyond column 72
! (adjustable via a command-line option), optionally warning about that
! content being something other than trailing whitespace or Fortran
! commentary.
! 
!    This program is needed because `lex.c' doesn't pay attention to
! maximum line lengths at all, to make it easier to maintain, as well as
! faster (for sources that don't depend on the maximum column length
! vis-a-vis trailing non-blank non-commentary content).
! 
!    Just how this program will be run--whether automatically for old
! source (perhaps as the default for `.f' files?)--is not yet determined.
! 
!    In the meantime, it might as well be implemented as a typical UNIX
! pipe.
! 
!    It should accept a `-fline-length-N' option, with the default line
! length set to 72.
! 
!    When the text it strips off the end of a line is not blank (not
! spaces and tabs), it should insert an additional comment line
! (beginning with `!', so it works for both fixed-form and free-form
! files) containing the text, following the stripped line.  The inserted
! comment should have a prefix of some kind, TBD, that distinguishes the
! comment as representing stripped text.  Users could use that to `sed'
! out such lines, if they wished--it seems silly to provide a
! command-line option to delete information when it can be so easily
! filtered out by another program.
! 
!    (This inserted comment should be designed to "fit in" well with
! whatever the Fortran community is using these days for preprocessor,
! translator, and other such products, like OpenMP.  What that's all
! about, and how `g77' can elegantly fit its special comment conventions
! into it all, is TBD as well.  We don't want to reinvent the wheel here,
! but if there turn out to be too many conflicting conventions, we might
! have to invent one that looks nothing like the others, but which offers
! their host products a better infrastructure in which to fit and coexist
! peacefully.)
! 
!    `g77stripcard' probably shouldn't do any tab expansion or other
! fancy stuff.  People can use `expand' or other pre-filtering if they
! like.  The idea here is to keep each stage quite simple, while providing
! excellent performance for "normal" code.
! 
!    (Code with junk beyond column 73 is not really "normal", as it comes
! from a card-punch heritage, and will be increasingly hard for
! tomorrow's Fortran programmers to read.)
! 
! 
! File: g77.info,  Node: lex.c,  Next: sta.c,  Prev: g77stripcard,  Up: Overview of Translation Process
! 
! lex.c
! -----
! 
!    To help make the lexer simple, fast, and easy to maintain, while
! also having `g77' generally encourage Fortran programmers to write
! simple, maintainable, portable code by maximizing the performance of
! compiling that kind of code:
! 
!    * There'll be just one lexer, for both fixed-form and free-form
!      source.
! 
!    * It'll care about the form only when handling the first 7 columns of
!      text, stuff like spaces between strings of alphanumerics, and how
!      lines are continued.
! 
!      Some other distinctions will be handled by subsequent phases, so
!      at least one of them will have to know which form is involved.
! 
!      For example, `I = 2 . 4' is acceptable in fixed form, and works in
!      free form as well given the implementation `g77' presently uses.
!      But the standard requires a diagnostic for it in free form, so the
!      parser has to be able to recognize that the lexemes aren't
!      contiguous (information the lexer _does_ have to provide) and that
!      free-form source is being parsed, so it can provide the diagnostic.
! 
!      The `g77' lexer doesn't try to gather `2 . 4' into a single lexeme.
!      Otherwise, it'd have to know a whole lot more about how to parse
!      Fortran, or subsequent phases (mainly parsing) would have two
!      paths through lots of critical code--one to handle the lexeme `2',
!      `.', and `4' in sequence, another to handle the lexeme `2.4'.
! 
!    * It won't worry about line lengths (beyond the first 7 columns for
!      fixed-form source).
! 
!      That is, once it starts parsing the "statement" part of a line
!      (column 7 for fixed-form, column 1 for free-form), it'll keep
!      going until it finds a newline, rather than ignoring everything
!      past a particular column (72 or 132).
! 
!      The implication here is that there shouldn't _be_ anything past
!      that last column, other than whitespace or commentary, because
!      users using typical editors (or viewing output as typically
!      printed) won't necessarily know just where the last column is.
! 
!      Code that has "garbage" beyond the last column (almost certainly
!      only fixed-form code with a punched-card legacy, such as code
!      using columns 73-80 for "sequence numbers") will have to be run
!      through `g77stripcard' first.
! 
!      Also, keeping track of the maximum column position while also
!      watching out for the end of a line _and_ while reading from a file
!      just makes things slower.  Since a file must be read, and watching
!      for the end of the line is necessary (unless the typical input
!      file was preprocessed to include the necessary number of trailing
!      spaces), dropping the tracking of the maximum column position is
!      the only way to reduce the complexity of the pertinent code while
!      maintaining high performance.
! 
!    * ASCII encoding is assumed for the input file.
! 
!      Code written in other character sets will have to be converted
!      first.
! 
!    * Tabs (ASCII code 9) will be converted to spaces via the
!      straightforward approach.
! 
!      Specifically, a tab is converted to between one and eight spaces
!      as necessary to reach column N, where dividing `(N - 1)' by eight
!      results in a remainder of zero.
! 
!      That saves having to pass most source files through `expand'.
! 
!    * Linefeeds (ASCII code 10) mark the ends of lines.
! 
!    * A carriage return (ASCII code 13) is accept if it immediately
!      precedes a linefeed, in which case it is ignored.
! 
!      Otherwise, it is rejected (with a diagnostic).
! 
!    * Any other characters other than the above that are not part of the
!      GNU Fortran Character Set (*note Character Set::) are rejected
!      with a diagnostic.
! 
!      This includes backspaces, form feeds, and the like.
! 
!      (It might make sense to allow a form feed in column 1 as long as
!      that's the only character on a line.  It certainly wouldn't seem
!      to cost much in terms of performance.)
! 
!    * The end of the input stream (EOF) ends the current line.
! 
!    * The distinction between uppercase and lowercase letters will be
!      preserved.
! 
!      It will be up to subsequent phases to decide to fold case.
! 
!      Current plans are to permit any casing for Fortran (reserved)
!      keywords while preserving casing for user-defined names.  (This
!      might not be made the default for `.f' files, though.)
! 
!      Preserving case seems necessary to provide more direct access to
!      facilities outside of `g77', such as to C or Pascal code.
! 
!      Names of intrinsics will probably be matchable in any case,
! 
!      (How `external SiN; r = sin(x)' would be handled is TBD.  I think
!      old `g77' might already handle that pretty elegantly, but whether
!      we can cope with allowing the same fragment to reference a
!      _different_ procedure, even with the same interface, via `s =
!      SiN(r)', needs to be determined.  If it can't, we need to make
!      sure that when code introduces a user-defined name, any intrinsic
!      matching that name using a case-insensitive comparison is "turned
!      off".)
! 
!    * Backslashes in `CHARACTER' and Hollerith constants are not allowed.
! 
!      This avoids the confusion introduced by some Fortran compiler
!      vendors providing C-like interpretation of backslashes, while
!      others provide straight-through interpretation.
! 
!      Some kind of lexical construct (TBD) will be provided to allow
!      flagging of a `CHARACTER' (but probably not a Hollerith) constant
!      that permits backslashes.  It'll necessarily be a prefix, such as:
! 
!           PRINT *, C'This line has a backspace \b here.'
!           PRINT *, F'This line has a straight backslash \ here.'
! 
!      Further, command-line options might be provided to specify that
!      one prefix or the other is to be assumed as the default for
!      `CHARACTER' constants.
! 
!      However, it seems more helpful for `g77' to provide a program that
!      converts prefix all constants (or just those containing
!      backslashes) with the desired designation, so printouts of code
!      can be read without knowing the compile-time options used when
!      compiling it.
! 
!      If such a program is provided (let's name it `g77slash' for now),
!      then a command-line option to `g77' should not be provided.
!      (Though, given that it'll be easy to implement, it might be hard
!      to resist user requests for it "to compile faster than if we have
!      to invoke another filter".)
! 
!      This program would take a command-line option to specify the
!      default interpretation of slashes, affecting which prefix it uses
!      for constants.
! 
!      `g77slash' probably should automatically convert Hollerith
!      constants that contain slashes to the appropriate `CHARACTER'
!      constants.  Then `g77' wouldn't have to define a prefix syntax for
!      Hollerith constants specifying whether they want C-style or
!      straight-through backslashes.
! 
!    * To allow for form-neutral INCLUDE files without requiring them to
!      be preprocessed, the fixed-form lexer should offer an extension
!      (if possible) allowing a trailing `&' to be ignored, especially if
!      after column 72, as it would be using the traditional Unix Fortran
!      source model (which ignores _everything_ after column 72).
! 
!    The above implements nearly exactly what is specified by *Note
! Character Set::, and *Note Lines::, except it also provides automatic
! conversion of tabs and ignoring of newline-related carriage returns, as
! well as accommodating form-neutral INCLUDE files.
! 
!    It also implements the "pure visual" model, by which is meant that a
! user viewing his code in a typical text editor (assuming it's not
! preprocessed via `g77stripcard' or similar) doesn't need any special
! knowledge of whether spaces on the screen are really tabs, whether
! lines end immediately after the last visible non-space character or
! after a number of spaces and tabs that follow it, or whether the last
! line in the file is ended by a newline.
! 
!    Most editors don't make these distinctions, the ANSI FORTRAN 77
! standard doesn't require them to, and it permits a standard-conforming
! compiler to define a method for transforming source code to "standard
! form" however it wants.
! 
!    So, GNU Fortran defines it such that users have the best chance of
! having the code be interpreted the way it looks on the screen of the
! typical editor.
! 
!    (Fancy editors should _never_ be required to correctly read code
! written in classic two-dimensional-plaintext form.  By correct reading
! I mean ability to read it, book-like, without mistaking text ignored by
! the compiler for program code and vice versa, and without having to
! count beyond the first several columns.  The vague meaning of ASCII
! TAB, among other things, complicates this somewhat, but as long as
! "everyone", including the editor, other tools, and printer, agrees
! about the every-eighth-column convention, the GNU Fortran "pure visual"
! model meets these requirements.  Any language or user-visible source
! form requiring special tagging of tabs, the ends of lines after
! spaces/tabs, and so on, fails to meet this fairly straightforward
! specification.  Fortunately, Fortran _itself_ does not mandate such a
! failure, though most vendor-supplied defaults for their Fortran
! compilers _do_ fail to meet this specification for readability.)
! 
!    Further, this model provides a clean interface to whatever
! preprocessors or code-generators are used to produce input to this
! phase of `g77'.  Mainly, they need not worry about long lines.
! 
! 
! File: g77.info,  Node: sta.c,  Next: sti.c,  Prev: lex.c,  Up: Overview of Translation Process
! 
! sta.c
! -----
! 
! 
! File: g77.info,  Node: sti.c,  Next: stq.c,  Prev: sta.c,  Up: Overview of Translation Process
! 
! sti.c
! -----
! 
! 
! File: g77.info,  Node: stq.c,  Next: stb.c,  Prev: sti.c,  Up: Overview of Translation Process
! 
! stq.c
! -----
! 
! 
! File: g77.info,  Node: stb.c,  Next: expr.c,  Prev: stq.c,  Up: Overview of Translation Process
! 
! stb.c
! -----
! 
! 
! File: g77.info,  Node: expr.c,  Next: stc.c,  Prev: stb.c,  Up: Overview of Translation Process
! 
! expr.c
! ------
! 
! 
! File: g77.info,  Node: stc.c,  Next: std.c,  Prev: expr.c,  Up: Overview of Translation Process
! 
! stc.c
! -----
! 
! 
! File: g77.info,  Node: std.c,  Next: ste.c,  Prev: stc.c,  Up: Overview of Translation Process
! 
! std.c
! -----
! 
! 
! File: g77.info,  Node: ste.c,  Next: Gotchas (Transforming),  Prev: std.c,  Up: Overview of Translation Process
! 
! ste.c
! -----
! 
! 
! File: g77.info,  Node: Gotchas (Transforming),  Next: TBD (Transforming),  Prev: ste.c,  Up: Overview of Translation Process
! 
! Gotchas (Transforming)
! ----------------------
! 
!    This section is not about transforming "gotchas" into something else.
! It is about the weirder aspects of transforming Fortran, however that's
! defined, into a more modern, canonical form.
! 
! Multi-character Lexemes
! .......................
! 
!    Each lexeme carries with it a pointer to where it appears in the
! source.
! 
!    To provide the ability for diagnostics to point to column numbers,
! in addition to line numbers and names, lexemes that represent more than
! one (significant) character in the source code need, generally, to
! provide pointers to where each _character_ appears in the source.
! 
!    This provides the ability to properly identify the precise location
! of the problem in code like
! 
!      SUBROUTINE X
!      END
!      BLOCK DATA X
!      END
! 
!    which, in fixed-form source, would result in single lexemes
! consisting of the strings `SUBROUTINEX' and `BLOCKDATAX'.  (The problem
! is that `X' is defined twice, so a pointer to the `X' in the second
! definition, as well as a follow-up pointer to the corresponding pointer
! in the first, would be preferable to pointing to the beginnings of the
! statements.)
! 
!    This need also arises when parsing (and diagnosing) `FORMAT'
! statements.
! 
!    Further, it arises when diagnosing `FMT=' specifiers that contain
! constants (or partial constants, or even propagated constants!)  in I/O
! statements, as in:
! 
!      PRINT '(I2, 3HAB)', J
! 
!    (A pointer to the beginning of the prematurely-terminated Hollerith
! constant, and/or to the close parenthese, is preferable to a pointer to
! the open-parenthese or the apostrophe that precedes it.)
! 
!    Multi-character lexemes, which would seem to naturally include at
! least digit strings, alphanumeric strings, `CHARACTER' constants, and
! Hollerith constants, therefore need to provide location information on
! each character.  (Maybe Hollerith constants don't, but it's unnecessary
! to except them.)
! 
!    The question then arises, what about _other_ multi-character lexemes,
! such as `**' and `//', and Fortran 90's `(/', `/)', `::', and so on?
! 
!    Turns out there's a need to identify the location of the second
! character of these two-character lexemes.  For example, in `I(/J) = K',
! the slash needs to be diagnosed as the problem, not the open parenthese.
! Similarly, it is preferable to diagnose the second slash in `I = J //
! K' rather than the first, given the implicit typing rules, which would
! result in the compiler disallowing the attempted concatenation of two
! integers.  (Though, since that's more of a semantic issue, it's not
! _that_ much preferable.)
! 
!    Even sequences that could be parsed as digit strings could use
! location info, for example, to diagnose the `9' in the octal constant
! `O'129''.  (This probably will be parsed as a character string, to be
! consistent with the parsing of `Z'129A''.)
! 
!    To avoid the hassle of recording the location of the second
! character, while also preserving the general rule that each significant
! character is distinctly pointed to by the lexeme that contains it, it's
! best to simply not have any fixed-size lexemes larger than one
! character.
! 
!    This new design is expected to make checking for two `*' lexemes in
! a row much easier than the old design, so this is not much of a
! sacrifice.  It probably makes the lexer much easier to implement than
! it makes the parser harder.
! 
! Space-padding Lexemes
! .....................
! 
!    Certain lexemes need to be padded with virtual spaces when the end
! of the line (or file) is encountered.
! 
!    This is necessary in fixed form, to handle lines that don't extend
! to column 72, assuming that's the line length in effect.
! 
! Bizarre Free-form Hollerith Constants
! .....................................
! 
!    Last I checked, the Fortran 90 standard actually required the
! compiler to silently accept something like
! 
!      FORMAT ( 1 2   Htwelve chars )
! 
!    as a valid `FORMAT' statement specifying a twelve-character
! Hollerith constant.
! 
!    The implication here is that, since the new lexer is a zero-feedback
! one, it won't know that the special case of a `FORMAT' statement being
! parsed requires apparently distinct lexemes `1' and `2' to be treated as
! a single lexeme.
! 
!    (This is a horrible misfeature of the Fortran 90 language.  It's one
! of many such misfeatures that almost make me want to not support them,
! and forge ahead with designing a new "GNU Fortran" language that has
! the features, but not the misfeatures, of Fortran 90, and provide
! utility programs to do the conversion automatically.)
! 
!    So, the lexer must gather distinct chunks of decimal strings into a
! single lexeme in contexts where a single decimal lexeme might start a
! Hollerith constant.
! 
!    (Which probably means it might as well do that all the time for all
! multi-character lexemes, even in free-form mode, leaving it to
! subsequent phases to pull them apart as they see fit.)
! 
!    Compare the treatment of this to how
! 
!      CHARACTER * 4 5 HEY
! 
!    and
! 
!      CHARACTER * 12 HEY
! 
!    must be treated--the former must be diagnosed, due to the separation
! between lexemes, the latter must be accepted as a proper declaration.
! 
! Hollerith Constants
! ...................
! 
!    Recognizing a Hollerith constant--specifically, that an `H' or `h'
! after a digit string begins such a constant--requires some knowledge of
! context.
! 
!    Hollerith constants (such as `2HAB') can appear after:
! 
!    * `('
! 
!    * `,'
! 
!    * `='
! 
!    * `+', `-', `/'
! 
!    * `*', except as noted below
! 
!    Hollerith constants don't appear after:
! 
!    * `CHARACTER*', which can be treated generally as any `*' that is
!      the second lexeme of a statement
! 
! Confusing Function Keyword
! ..........................
! 
!    While
! 
!      REAL FUNCTION FOO ()
! 
!    must be a `FUNCTION' statement and
! 
!      REAL FUNCTION FOO (5)
! 
!    must be a type-definition statement,
! 
!      REAL FUNCTION FOO (NAMES)
! 
!    where NAMES is a comma-separated list of names, can be one or the
! other.
! 
!    The only way to disambiguate that statement (short of mandating
! free-form source or a short maximum length for name for external
! procedures) is based on the context of the statement.
! 
!    In particular, the statement is known to be within an
! already-started program unit (but not at the outer level of the
! `CONTAINS' block), it is a type-declaration statement.
! 
!    Otherwise, the statement is a `FUNCTION' statement, in that it
! begins a function program unit (external, or, within `CONTAINS',
! nested).
! 
! Weird READ
! ..........
! 
!    The statement
! 
!      READ (N)
! 
!    is equivalent to either
! 
!      READ (UNIT=(N))
! 
!    or
! 
!      READ (FMT=(N))
! 
!    depending on which would be valid in context.
! 
!    Specifically, if `N' is type `INTEGER', `READ (FMT=(N))' would not
! be valid, because parentheses may not be used around `N', whereas they
! may around it in `READ (UNIT=(N))'.
! 
!    Further, if `N' is type `CHARACTER', the opposite is true--`READ
! (UNIT=(N))' is not valid, but `READ (FMT=(N))' is.
! 
!    Strictly speaking, if anything follows
! 
!      READ (N)
! 
!    in the statement, whether the first lexeme after the close
! parenthese is a comma could be used to disambiguate the two cases,
! without looking at the type of `N', because the comma is required for
! the `READ (FMT=(N))' interpretation and disallowed for the `READ
! (UNIT=(N))' interpretation.
! 
!    However, in practice, many Fortran compilers allow the comma for the
! `READ (UNIT=(N))' interpretation anyway (in that they generally allow a
! leading comma before an I/O list in an I/O statement), and much code
! takes advantage of this allowance.
! 
!    (This is quite a reasonable allowance, since the juxtaposition of a
! comma-separated list immediately after an I/O control-specification
! list, which is also comma-separated, without an intervening comma,
! looks sufficiently "wrong" to programmers that they can't resist the
! itch to insert the comma.  `READ (I, J), K, L' simply looks cleaner than
! `READ (I, J) K, L'.)
! 
!    So, type-based disambiguation is needed unless strict adherence to
! the standard is always assumed, and we're not going to assume that.
! 
! 
! File: g77.info,  Node: TBD (Transforming),  Prev: Gotchas (Transforming),  Up: Overview of Translation Process
! 
! TBD (Transforming)
! ------------------
! 
!    Continue researching gotchas, designing the transformational process,
! and implementing it.
! 
!    Specific issues to resolve:
! 
!    * Just where should (if it was implemented) `USE' processing take
!      place?
! 
!      This gets into the whole issue of how `g77' should handle the
!      concept of modules.  I think GNAT already takes on this issue, but
!      don't know more than that.  Jim Giles has written extensively on
!      `comp.lang.fortran' about his opinions on module handling, as have
!      others.  Jim's views should be taken into account.
! 
!      Actually, Richard M. Stallman (RMS) also has written up some
!      guidelines for implementing such things, but I'm not sure where I
!      read them.  Perhaps the old <gcc2@cygnus.com> list.
! 
!      If someone could dig references to these up and get them to me,
!      that would be much appreciated!  Even though modules are not on
!      the short-term list for implementation, it'd be helpful to know
!      _now_ how to avoid making them harder to implement them _later_.
! 
!    * Should the `g77' command become just a script that invokes all the
!      various preprocessing that might be needed, thus making it seem
!      slower than necessary for legacy code that people are unwilling to
!      convert, or should we provide a separate script for that, thus
!      encouraging people to convert their code once and for all?
! 
!      At least, a separate script to behave as old `g77' did, perhaps
!      named `g77old', might ease the transition, as might a
!      corresponding one that converts source codes named `g77oldnew'.
! 
!      These scripts would take all the pertinent options `g77' used to
!      take and run the appropriate filters, passing the results to `g77'
!      or just making new sources out of them (in a subdirectory, leaving
!      the user to do the dirty deed of moving or copying them over the
!      old sources).
! 
!    * Do other Fortran compilers provide a prefix syntax to govern the
!      treatment of backslashes in `CHARACTER' (or Hollerith) constants?
! 
!      Knowing what other compilers provide would help.
! 
!    * Is it okay to drop support for the `-fintrin-case-initcap',
!      `-fmatch-case-initcap', `-fsymbol-case-initcap', and
!      `-fcase-initcap' options?
! 
!      I've asked <info-gnu-fortran@gnu.org> for input on this.  Not
!      having to support these makes it easier to write the new front end,
!      and might also avoid complicated its design.
! 
!      The consensus to date (1999-11-17) has been to drop this support.
!      Can't recall anybody saying they're using it, in fact.
! 
! 
! File: g77.info,  Node: Philosophy of Code Generation,  Next: Two-pass Design,  Prev: Overview of Translation Process,  Up: Front End
! 
! Philosophy of Code Generation
! =============================
! 
!    Don't poke the bear.
! 
!    The `g77' front end generates code via the `gcc' back end.
! 
!    The `gcc' back end (GBE) is a large, complex labyrinth of intricate
! code written in a combination of the C language and specialized
! languages internal to `gcc'.
! 
!    While the _code_ that implements the GBE is written in a combination
! of languages, the GBE itself is, to the front end for a language like
! Fortran, best viewed as a _compiler_ that compiles its own, unique,
! language.
! 
!    The GBE's "source", then, is written in this language, which
! consists primarily of a combination of calls to GBE functions and
! "tree" nodes (which are, themselves, created by calling GBE functions).
! 
!    So, the `g77' generates code by, in effect, translating the Fortran
! code it reads into a form "written" in the "language" of the `gcc' back
! end.
! 
!    This language will heretofore be referred to as "GBEL", for GNU Back
! End Language.
! 
!    GBEL is an evolving language, not fully specified in any published
! form as of this writing.  It offers many facilities, but its "core"
! facilities are those that corresponding most directly to those needed
! to support `gcc' (compiling code written in GNU C).
! 
!    The `g77' Fortran Front End (FFE) is designed and implemented to
! navigate the currents and eddies of ongoing GBEL and `gcc' development
! while also delivering on the potential of an integrated FFE (as
! compared to using a converter like `f2c' and feeding the output into
! `gcc').
! 
!    Goals of the FFE's code-generation strategy include:
! 
!    * High likelihood of generation of correct code, or, failing that,
!      producing a fatal diagnostic or crashing.
! 
!    * Generation of highly optimized code, as directed by the user via
!      GBE-specific (versus `g77'-specific) constructs, such as
!      command-line options.
! 
!    * Fast overall (FFE plus GBE) compilation.
! 
!    * Preservation of source-level debugging information.
! 
!    The strategies historically, and currently, used by the FFE to
! achieve these goals include:
! 
!    * Use of GBEL constructs that most faithfully encapsulate the
!      semantics of Fortran.
! 
!    * Avoidance of GBEL constructs that are so rarely used, or limited
!      to use in specialized situations not related to Fortran, that
!      their reliability and performance has not yet been established as
!      sufficient for use by the FFE.
! 
!    * Flexible design, to readily accommodate changes to specific
!      code-generation strategies, perhaps governed by command-line
!      options.
! 
!    "Don't poke the bear" somewhat summarizes the above strategies.  The
! GBE is the bear.  The FFE is designed and implemented to avoid poking it
! in ways that are likely to just annoy it.  The FFE usually either
! tackles it head-on, or avoids treating it in ways dissimilar to how the
! `gcc' front end treats it.
! 
!    For example, the FFE uses the native array facility in the back end
! instead of the lower-level pointer-arithmetic facility used by `gcc'
! when compiling `f2c' output).  Theoretically, this presents more
! opportunities for optimization, faster compile times, and the
! production of more faithful debugging information.  These benefits were
! not, however, immediately realized, mainly because `gcc' itself makes
! little or no use of the native array facility.
! 
!    Complex arithmetic is a case study of the evolution of this strategy.
! When originally implemented, the GBEL had just evolved its own native
! complex-arithmetic facility, so the FFE took advantage of that.
! 
!    When porting `g77' to 64-bit systems, it was discovered that the GBE
! didn't really implement its native complex-arithmetic facility properly.
! 
!    The short-term solution was to rewrite the FFE to instead use the
! lower-level facilities that'd be used by `gcc'-compiled code (assuming
! that code, itself, didn't use the native complex type provided, as an
! extension, by `gcc'), since these were known to work, and, in any case,
! if shown to not work, would likely be rapidly fixed (since they'd
! likely not work for vanilla C code in similar circumstances).
! 
!    However, the rewrite accommodated the original, native approach as
! well by offering a command-line option to select it over the emulated
! approach.  This allowed users, and especially GBE maintainers, to try
! out fixes to complex-arithmetic support in the GBE while `g77'
! continued to default to compiling more code correctly, albeit producing
! (typically) slower executables.
! 
!    As of April 1999, it appeared that the last few bugs in the GBE's
! support of its native complex-arithmetic facility were worked out.  The
! FFE was changed back to default to using that native facility, leaving
! emulation as an option.
! 
!    Later during the release cycle (which was called EGCS 1.2, but soon
! became GCC 2.95), bugs in the native facility were found.  Reactions
! among various people included "the last thing we should do is change
! the default back", "we must change the default back", and "let's figure
! out whether we can narrow down the bugs to few enough cases to allow
! the now-months-long-tested default to remain the same".  The latter
! viewpoint won that particular time.  The bugs exposed other concerns
! regarding ABI compliance when the ABI specified treatment of complex
! data as different from treatment of what Fortran and GNU C consider the
! equivalent aggregation (structure) of real (or float) pairs.
! 
!    Other Fortran constructs--arrays, character strings, complex
! division, `COMMON' and `EQUIVALENCE' aggregates, and so on--involve
! issues similar to those pertaining to complex arithmetic.
! 
!    So, it is possible that the history of how the FFE handled complex
! arithmetic will be repeated, probably in modified form (and hopefully
! over shorter timeframes), for some of these other facilities.
! 
! 
! File: g77.info,  Node: Two-pass Design,  Next: Challenges Posed,  Prev: Philosophy of Code Generation,  Up: Front End
! 
! Two-pass Design
! ===============
! 
!    The FFE does not tell the GBE anything about a program unit until
! after the last statement in that unit has been parsed.  (A program unit
! is a Fortran concept that corresponds, in the C world, mostly closely
! to functions definitions in ISO C.  That is, a program unit in Fortran
! is like a top-level function in C.  Nested functions, found among the
! extensions offered by GNU C, correspond roughly to Fortran's statement
! functions.)
! 
!    So, while parsing the code in a program unit, the FFE saves up all
! the information on statements, expressions, names, and so on, until it
! has seen the last statement.
! 
!    At that point, the FFE revisits the saved information (in what
! amounts to a second "pass" over the program unit) to perform the actual
! translation of the program unit into GBEL, ultimating in the generation
! of assembly code for it.
! 
!    Some lookahead is performed during this second pass, so the FFE
! could be viewed as a "two-plus-pass" design.
! 
! * Menu:
! 
! * Two-pass Code::
! * Why Two Passes::
! 
! 
! File: g77.info,  Node: Two-pass Code,  Next: Why Two Passes,  Up: Two-pass Design
! 
! Two-pass Code
! -------------
! 
!    Most of the code that turns the first pass (parsing) into a second
! pass for code generation is in `gcc/gcc/f/std.c'.
! 
!    It has external functions, called mainly by siblings in
! `gcc/gcc/f/stc.c', that record the information on statements and
! expressions in the order they are seen in the source code.  These
! functions save that information.
! 
!    It also has an external function that revisits that information,
! calling the siblings in `gcc/gcc/f/ste.c', which handles the actual
! code generation (by generating GBEL code, that is, by calling GBE
! routines to represent and specify expressions, statements, and so on).
! 
! 
! File: g77.info,  Node: Why Two Passes,  Prev: Two-pass Code,  Up: Two-pass Design
! 
! Why Two Passes
! --------------
! 
!    The need for two passes was not immediately evident during the
! design and implementation of the code in the FFE that was to produce
! GBEL.  Only after a few kludges, to handle things like
! incorrectly-guessed `ASSIGN' label nature, had been implemented, did
! enough evidence pile up to make it clear that `std.c' had to be
! introduced to intercept, save, then revisit as part of a second pass,
! the digested contents of a program unit.
! 
!    Other such missteps have occurred during the evolution of the FFE,
! because of the different goals of the FFE and the GBE.
! 
!    Because the GBE's original, and still primary, goal was to directly
! support the GNU C language, the GBEL, and the GBE itself, requires more
! complexity on the part of most front ends than it requires of `gcc''s.
! 
!    For example, the GBEL offers an interface that permits the `gcc'
! front end to implement most, or all, of the language features it
! supports, without the front end having to make use of non-user-defined
! variables.  (It's almost certainly the case that all of K&R C, and
! probably ANSI C as well, is handled by the `gcc' front end without
! declaring such variables.)
! 
!    The FFE, on the other hand, must resort to a variety of "tricks" to
! achieve its goals.
! 
!    Consider the following C code:
! 
!      int
!      foo (int a, int b)
!      {
!        int c = 0;
!      
!        if ((c = bar (c)) == 0)
!          goto done;
!      
!        quux (c << 1);
!      
!      done:
!        return c;
!      }
! 
!    Note what kinds of objects are declared, or defined, before their
! use, and before any actual code generation involving them would
! normally take place:
! 
!    * Return type of function
! 
!    * Entry point(s) of function
! 
!    * Dummy arguments
! 
!    * Variables
! 
!    * Initial values for variables
! 
!    Whereas, the following items can, and do, suddenly appear "out of
! the blue" in C:
! 
!    * Label references
! 
!    * Function references
! 
!    Not surprisingly, the GBE faithfully permits the latter set of items
! to be "discovered" partway through GBEL "programs", just as they are
! permitted to in C.
! 
!    Yet, the GBE has tended, at least in the past, to be reticent to
! fully support similar "late" discovery of items in the former set.
! 
!    This makes Fortran a poor fit for the "safe" subset of GBEL.
! Consider:
! 
!            FUNCTION X (A, ARRAY, ID1)
!            CHARACTER*(*) A
!            DOUBLE PRECISION X, Y, Z, TMP, EE, PI
!            REAL ARRAY(ID1*ID2)
!            COMMON ID2
!            EXTERNAL FRED
!      
!            ASSIGN 100 TO J
!            CALL FOO (I)
!            IF (I .EQ. 0) PRINT *, A(0)
!            GOTO 200
!      
!            ENTRY Y (Z)
!            ASSIGN 101 TO J
!      200   PRINT *, A(1)
!            READ *, TMP
!            GOTO J
!      100   X = TMP * EE
!            RETURN
!      101   Y = TMP * PI
!            CALL FRED
!            DATA EE, PI /2.71D0, 3.14D0/
!            END
! 
!    Here are some observations about the above code, which, while
! somewhat contrived, conforms to the FORTRAN 77 and Fortran 90 standards:
! 
!    * The return type of function `X' is not known until the `DOUBLE
!      PRECISION' line has been parsed.
! 
!    * Whether `A' is a function or a variable is not known until the
!      `PRINT *, A(0)' statement has been parsed.
! 
!    * The bounds of the array of argument `ARRAY' depend on a
!      computation involving the subsequent argument `ID1' and the
!      blank-common member `ID2'.
! 
!    * Whether `Y' and `Z' are local variables, additional function entry
!      points, or dummy arguments to additional entry points is not known
!      until the `ENTRY' statement is parsed.
! 
!    * Similarly, whether `TMP' is a local variable is not known until
!      the `READ *, TMP' statement is parsed.
! 
!    * The initial values for `EE' and `PI' are not known until after the
!      `DATA' statement is parsed.
! 
!    * Whether `FRED' is a function returning type `REAL' or a subroutine
!      (which can be thought of as returning type `void' _or_, to support
!      alternate returns in a simple way, type `int') is not known until
!      the `CALL FRED' statement is parsed.
! 
!    * Whether `100' is a `FORMAT' label or the label of an executable
!      statement is not known until the `X =' statement is parsed.
!      (These two types of labels get _very_ different treatment,
!      especially when `ASSIGN''ed.)
! 
!    * That `J' is a local variable is not known until the first `ASSIGN'
!      statement is parsed.  (This happens _after_ executable code has
!      been seen.)
! 
!    Very few of these "discoveries" can be accommodated by the GBE as it
! has evolved over the years.  The GBEL doesn't support several of them,
! and those it might appear to support don't always work properly,
! especially in combination with other GBEL and GBE features, as
! implemented in the GBE.
! 
!    (Had the GBE and its GBEL originally evolved to support `g77', the
! shoe would be on the other foot, so to speak--most, if not all, of the
! above would be directly supported by the GBEL, and a few C constructs
! would probably not, as they are in reality, be supported.  Both this
! mythical, and today's real, GBE caters to its GBEL by, sometimes,
! scrambling around, cleaning up after itself--after discovering that
! assumptions it made earlier during code generation are incorrect.
! That's not a great design, since it indicates significant code paths
! that might be rarely tested but used in some key production
! environments.)
! 
!    So, the FFE handles these discrepancies--between the order in which
! it discovers facts about the code it is compiling, and the order in
! which the GBEL and GBE support such discoveries--by performing what
! amounts to two passes over each program unit.
! 
!    (A few ambiguities can remain at that point, such as whether, given
! `EXTERNAL BAZ' and no other reference to `BAZ' in the program unit, it
! is a subroutine, a function, or a block-data--which, in C-speak,
! governs its declared return type.  Fortunately, these distinctions are
! easily finessed for the procedure, library, and object-file interfaces
! supported by `g77'.)
! 
! 
! File: g77.info,  Node: Challenges Posed,  Next: Transforming Statements,  Prev: Two-pass Design,  Up: Front End
! 
! Challenges Posed
! ================
! 
!    Consider the following Fortran code, which uses various extensions
! (including some to Fortran 90):
! 
!      SUBROUTINE X(A)
!      CHARACTER*(*) A
!      COMPLEX CFUNC
!      INTEGER*2 CLOCKS(200)
!      INTEGER IFUNC
!      
!      CALL SYSTEM_CLOCK (CLOCKS (IFUNC (CFUNC ('('//A//')'))))
! 
!    The above poses the following challenges to any Fortran compiler
! that uses run-time interfaces, and a run-time library, roughly similar
! to those used by `g77':
! 
!    * Assuming the library routine that supports `SYSTEM_CLOCK' expects
!      to set an `INTEGER*4' variable via its `COUNT' argument, the
!      compiler must make available to it a temporary variable of that
!      type.
! 
!    * Further, after the `SYSTEM_CLOCK' library routine returns, the
!      compiler must ensure that the temporary variable it wrote is
!      copied into the appropriate element of the `CLOCKS' array.  (This
!      assumes the compiler doesn't just reject the code, which it should
!      if it is compiling under some kind of a "strict" option.)
! 
!    * To determine the correct index into the `CLOCKS' array, (putting
!      aside the fact that the index, in this particular case, need not
!      be computed until after the `SYSTEM_CLOCK' library routine
!      returns), the compiler must ensure that the `IFUNC' function is
!      called.
! 
!      That requires evaluating its argument, which requires, for `g77'
!      (assuming `-ff2c' is in force), reserving a temporary variable of
!      type `COMPLEX' for use as a repository for the return value being
!      computed by `CFUNC'.
! 
!    * Before invoking `CFUNC', is argument must be evaluated, which
!      requires allocating, at run time, a temporary large enough to hold
!      the result of the concatenation, as well as actually performing
!      the concatenation.
! 
!    * The large temporary needed during invocation of `CFUNC' should,
!      ideally, be deallocated (or, at least, left to the GBE to dispose
!      of, as it sees fit) as soon as `CFUNC' returns, which means before
!      `IFUNC' is called (as it might need a lot of dynamically allocated
!      memory).
! 
!    `g77' currently doesn't support all of the above, but, so that it
! might someday, it has evolved to handle at least some of the above
! requirements.
! 
!    Meeting the above requirements is made more challenging by
! conforming to the requirements of the GBEL/GBE combination.
! 
! 
! File: g77.info,  Node: Transforming Statements,  Next: Transforming Expressions,  Prev: Challenges Posed,  Up: Front End
! 
! Transforming Statements
! =======================
! 
!    Most Fortran statements are given their own block, and, for
! temporary variables they might need, their own scope.  (A block is what
! distinguishes `{ foo (); }' from just `foo ();' in C.  A scope is
! included with every such block, providing a distinct name space for
! local variables.)
! 
!    Label definitions for the statement precede this block, so `10 PRINT
! *, I' is handled more like `fl10: { ... }' than `{ fl10: ... }' (where
! `fl10' is just a notation meaning "Fortran Label 10" for the purposes
! of this document).
! 
! * Menu:
! 
! * Statements Needing Temporaries::
! * Transforming DO WHILE::
! * Transforming Iterative DO::
! * Transforming Block IF::
! * Transforming SELECT CASE::
! 
! 
! File: g77.info,  Node: Statements Needing Temporaries,  Next: Transforming DO WHILE,  Up: Transforming Statements
! 
! Statements Needing Temporaries
! ------------------------------
! 
!    Any temporaries needed during, but not beyond, execution of a
! Fortran statement, are made local to the scope of that statement's
! block.
! 
!    This allows the GBE to share storage for these temporaries among the
! various statements without the FFE having to manage that itself.
! 
!    (The GBE could, of course, decide to optimize management of these
! temporaries.  For example, it could, theoretically, schedule some of
! the computations involving these temporaries to occur in parallel.
! More practically, it might leave the storage for some temporaries
! "live" beyond their scopes, to reduce the number of manipulations of
! the stack pointer at run time.)
! 
!    Temporaries needed across distinct statement boundaries usually are
! associated with Fortran blocks (such as `DO'/`END DO').  (Also, there
! might be temporaries not associated with blocks at all--these would be
! in the scope of the entire program unit.)
! 
!    Each Fortran block _should_ get its own block/scope in the GBE.
! This is best, because it allows temporaries to be more naturally
! handled.  However, it might pose problems when handling labels (in
! particular, when they're the targets of `GOTO's outside the Fortran
! block), and generally just hassling with replicating parts of the `gcc'
! front end (because the FFE needs to support an arbitrary number of
! nested back-end blocks if each Fortran block gets one).
! 
!    So, there might still be a need for top-level temporaries, whose
! "owning" scope is that of the containing procedure.
! 
!    Also, there seems to be problems declaring new variables after
! generating code (within a block) in the back end, leading to, e.g.,
! `label not defined before binding contour' or similar messages, when
! compiling with `-fstack-check' or when compiling for certain targets.
! 
!    Because of that, and because sometimes these temporaries are not
! discovered until in the middle of of generating code for an expression
! statement (as in the case of the optimization for `X**I'), it seems
! best to always pre-scan all the expressions that'll be expanded for a
! block before generating any of the code for that block.
! 
!    This pre-scan then handles discovering and declaring, to the back
! end, the temporaries needed for that block.
! 
!    It's also important to treat distinct items in an I/O list as
! distinct statements deserving their own blocks.  That's because there's
! a requirement that each I/O item be fully processed before the next one,
! which matters in cases like `READ (*,*), I, A(I)'--the element of `A'
! read in the second item _must_ be determined from the value of `I' read
! in the first item.
! 
! 
! File: g77.info,  Node: Transforming DO WHILE,  Next: Transforming Iterative DO,  Prev: Statements Needing Temporaries,  Up: Transforming Statements
! 
! Transforming DO WHILE
! ---------------------
! 
!    `DO WHILE(expr)' _must_ be implemented so that temporaries needed to
! evaluate `expr' are generated just for the test, each time.
! 
!    Consider how `DO WHILE (A//B .NE. 'END'); ...; END DO' is
! transformed:
! 
!      for (;;)
!        {
!          int temp0;
!      
!          {
!            char temp1[large];
!      
!            libg77_catenate (temp1, a, b);
!            temp0 = libg77_ne (temp1, 'END');
!          }
!      
!          if (! temp0)
!            break;
!      
!          ...
!        }
! 
!    In this case, it seems like a time/space tradeoff between allocating
! and deallocating `temp1' for each iteration and allocating it just once
! for the entire loop.
! 
!    However, if `temp1' is allocated just once for the entire loop, it
! could be the wrong size for subsequent iterations of that loop in cases
! like `DO WHILE (A(I:J)//B .NE. 'END')', because the body of the loop
! might modify `I' or `J'.
! 
!    So, the above implementation is used, though a more optimal one can
! be used in specific circumstances.
! 
! 
! File: g77.info,  Node: Transforming Iterative DO,  Next: Transforming Block IF,  Prev: Transforming DO WHILE,  Up: Transforming Statements
! 
! Transforming Iterative DO
! -------------------------
! 
!    An iterative `DO' loop (one that specifies an iteration variable) is
! required by the Fortran standards to be implemented as though an
! iteration count is computed before entering the loop body, and that
! iteration count used to determine the number of times the loop body is
! to be performed (assuming the loop isn't cut short via `GOTO' or
! `EXIT').
! 
!    The FFE handles this by allocating a temporary variable to contain
! the computed number of iterations.  Since this variable must be in a
! scope that includes the entire loop, a GBEL block is created for that
! loop, and the variable declared as belonging to the scope of that block.
! 
! 
! File: g77.info,  Node: Transforming Block IF,  Next: Transforming SELECT CASE,  Prev: Transforming Iterative DO,  Up: Transforming Statements
! 
! Transforming Block IF
! ---------------------
! 
!    Consider:
! 
!      SUBROUTINE X(A,B,C)
!      CHARACTER*(*) A, B, C
!      LOGICAL LFUNC
!      
!      IF (LFUNC (A//B)) THEN
!        CALL SUBR1
!      ELSE IF (LFUNC (A//C)) THEN
!        CALL SUBR2
!      ELSE
!        CALL SUBR3
!      END
! 
!    The arguments to the two calls to `LFUNC' require dynamic allocation
! (at run time), but are not required during execution of the `CALL'
! statements.
! 
!    So, the scopes of those temporaries must be within blocks inside the
! block corresponding to the Fortran `IF' block.
! 
!    This cannot be represented "naturally" in vanilla C, nor in GBEL.
! The `if', `elseif', `else', and `endif' constructs provided by both
! languages must, for a given `if' block, share the same C/GBE block.
! 
!    Therefore, any temporaries needed during evaluation of `expr' while
! executing `ELSE IF(expr)' must either have been predeclared at the top
! of the corresponding `IF' block, or declared within a new block for
! that `ELSE IF'--a block that, since it cannot contain the `else' or
! `else if' itself (due to the above requirement), actually implements
! the rest of the `IF' block's `ELSE IF' and `ELSE' statements within an
! inner block.
! 
!    The FFE takes the latter approach.
! 
! 
! File: g77.info,  Node: Transforming SELECT CASE,  Prev: Transforming Block IF,  Up: Transforming Statements
! 
! Transforming SELECT CASE
! ------------------------
! 
!    `SELECT CASE' poses a few interesting problems for code generation,
! if efficiency and frugal stack management are important.
! 
!    Consider `SELECT CASE (I('PREFIX'//A))', where `A' is
! `CHARACTER*(*)'.  In a case like this--basically, in any case where
! largish temporaries are needed to evaluate the expression--those
! temporaries should not be "live" during execution of any of the `CASE'
! blocks.
! 
!    So, evaluation of the expression is best done within its own block,
! which in turn is within the `SELECT CASE' block itself (which contains
! the code for the CASE blocks as well, though each within their own
! block).
! 
!    Otherwise, we'd have the rough equivalent of this pseudo-code:
! 
!      {
!        char temp[large];
!      
!        libg77_catenate (temp, 'prefix', a);
!      
!        switch (i (temp))
!          {
!          case 0:
!            ...
!          }
!      }
! 
!    And that would leave temp[large] in scope during the CASE blocks
! (although a clever back end *could* see that it isn't referenced in
! them, and thus free that temp before executing the blocks).
! 
!    So this approach is used instead:
! 
!      {
!        int temp0;
!      
!        {
!          char temp1[large];
!      
!          libg77_catenate (temp1, 'prefix', a);
!          temp0 = i (temp1);
!        }
!      
!        switch (temp0)
!          {
!          case 0:
!            ...
!          }
!      }
! 
!    Note how `temp1' goes out of scope before starting the switch, thus
! making it easy for a back end to free it.
! 
!    The problem _that_ solution has, however, is with `SELECT
! CASE('prefix'//A)' (which is currently not supported).
! 
!    Unless the GBEL is extended to support arbitrarily long character
! strings in its `case' facility, the FFE has to implement `SELECT CASE'
! on `CHARACTER' (probably excepting `CHARACTER*1') using a cascade of
! `if', `elseif', `else', and `endif' constructs in GBEL.
! 
!    To prevent the (potentially large) temporary, needed to hold the
! selected expression itself (`'prefix'//A'), from being in scope during
! execution of the `CASE' blocks, two approaches are available:
! 
!    * Pre-evaluate all the `CASE' tests, producing an integer ordinal
!      that is used, a la `temp0' in the earlier example, as if `SELECT
!      CASE(temp0)' had been written.
! 
!      Each corresponding `CASE' is replaced with `CASE(I)', where I is
!      the ordinal for that case, determined while, or before, generating
!      the cascade of `if'-related constructs to cope with `CHARACTER'
!      selection.
! 
!    * Make `temp0' above just large enough to hold the longest `CASE'
!      string that'll actually be compared against the expression (in
!      this case, `'prefix'//A').
! 
!      Since that length must be constant (because `CASE' expressions are
!      all constant), it won't be so large, and, further, `temp1' need
!      not be dynamically allocated, since normal `CHARACTER' assignment
!      can be used into the fixed-length `temp0'.
! 
!    Both of these solutions require `SELECT CASE' implementation to be
! changed so all the corresponding `CASE' statements are seen during the
! actual code generation for `SELECT CASE'.
! 
! 
! File: g77.info,  Node: Transforming Expressions,  Next: Internal Naming Conventions,  Prev: Transforming Statements,  Up: Front End
! 
! Transforming Expressions
! ========================
! 
!    The interactions between statements, expressions, and subexpressions
! at program run time can be viewed as:
! 
!      ACTION(EXPR)
! 
!    Here, ACTION is the series of steps performed to effect the
! statement, and EXPR is the expression whose value is used by ACTION.
! 
!    Expanding the above shows a typical order of events at run time:
! 
!      Evaluate EXPR
!      Perform ACTION, using result of evaluation of EXPR
!      Clean up after evaluating EXPR
! 
!    So, if evaluating EXPR requires allocating memory, that memory can
! be freed before performing ACTION only if it is not needed to hold the
! result of evaluating EXPR.  Otherwise, it must be freed no sooner than
! after ACTION has been performed.
! 
!    The above are recursive definitions, in the sense that they apply to
! subexpressions of EXPR.
! 
!    That is, evaluating EXPR involves evaluating all of its
! subexpressions, performing the ACTION that computes the result value of
! EXPR, then cleaning up after evaluating those subexpressions.
! 
!    The recursive nature of this evaluation is implemented via
! recursive-descent transformation of the top-level statements, their
! expressions, _their_ subexpressions, and so on.
! 
!    However, that recursive-descent transformation is, due to the nature
! of the GBEL, focused primarily on generating a _single_ stream of code
! to be executed at run time.
! 
!    Yet, from the above, it's clear that multiple streams of code must
! effectively be simultaneously generated during the recursive-descent
! analysis of statements.
! 
!    The primary stream implements the primary ACTION items, while at
! least two other streams implement the evaluation and clean-up items.
! 
!    Requirements imposed by expressions include:
! 
!    * Whether the caller needs to have a temporary ready to hold the
!      value of the expression.
! 
!    * Other stuff???
! 
! 
! File: g77.info,  Node: Internal Naming Conventions,  Prev: Transforming Expressions,  Up: Front End
! 
! Internal Naming Conventions
! ===========================
! 
!    Names exported by FFE modules have the following
! (regular-expression) forms.  Note that all names beginning `ffeMOD' or
! `FFEMOD', where MOD is lowercase or uppercase alphanumerics,
! respectively, are exported by the module `ffeMOD', with the source code
! doing the exporting in `MOD.h'.  (Usually, the source code for the
! implementation is in `MOD.c'.)
! 
!    Identifiers that don't fit the following forms are not considered
! exported, even if they are according to the C language.  (For example,
! they might be made available to other modules solely for use within
! expansions of exported macros, not for use within any source code in
! those other modules.)
! 
! `ffeMOD'
!      The single typedef exported by the module.
! 
! `FFEUMOD_[A-Z][A-Z0-9_]*'
!      (Where UMOD is the uppercase for of MOD.)
! 
!      A `#define' or `enum' constant of the type `ffeMOD'.
! 
! `ffeMOD[A-Z][A-Z][a-z0-9]*'
!      A typedef exported by the module.
! 
!      The portion of the identifier after `ffeMOD' is referred to as
!      `ctype', a capitalized (mixed-case) form of `type'.
! 
! `FFEUMOD_TYPE[A-Z][A-Z0-9_]*[A-Z0-9]?'
!      (Where UMOD is the uppercase for of MOD.)
! 
!      A `#define' or `enum' constant of the type `ffeMODTYPE', where
!      TYPE is the lowercase form of CTYPE in an exported typedef.
! 
! `ffeMOD_VALUE'
!      A function that does or returns something, as described by VALUE
!      (see below).
! 
! `ffeMOD_VALUE_INPUT'
!      A function that does or returns something based primarily on the
!      thing described by INPUT (see below).
! 
!    Below are names used for VALUE and INPUT, along with their
! definitions.
! 
! `col'
!      A column number within a line (first column is number 1).
! 
! `file'
!      An encapsulation of a file's name.
! 
! `find'
!      Looks up an instance of some type that matches specified criteria,
!      and returns that, even if it has to create a new instance or crash
!      trying to find it (as appropriate).
! 
! `initialize'
!      Initializes, usually a module.  No type.
! 
! `int'
!      A generic integer of type `int'.
! 
! `is'
!      A generic integer that contains a true (nonzero) or false (zero)
!      value.
! 
! `len'
!      A generic integer that contains the length of something.
! 
! `line'
!      A line number within a source file, or a global line number.
! 
! `lookup'
!      Looks up an instance of some type that matches specified criteria,
!      and returns that, or returns nil.
! 
! `name'
!      A `text' that points to a name of something.
! 
! `new'
!      Makes a new instance of the indicated type.  Might return an
!      existing one if appropriate--if so, similar to `find' without
!      crashing.
! 
! `pt'
!      Pointer to a particular character (line, column pairs) in the
!      input file (source code being compiled).
! 
! `run'
!      Performs some herculean task.  No type.
! 
! `terminate'
!      Terminates, usually a module.  No type.
! 
! `text'
!      A `char *' that points to generic text.
! 
! 
! File: g77.info,  Node: Diagnostics,  Next: Keyword Index,  Prev: Front End,  Up: Top
! 
! Diagnostics
! ***********
! 
!    Some diagnostics produced by `g77' require sufficient explanation
! that the explanations are given below, and the diagnostics themselves
! identify the appropriate explanation.
! 
!    Identification uses the GNU Info format--specifically, the `info'
! command that displays the explanation is given within square brackets
! in the diagnostic.  For example:
! 
!      foo.f:5: Invalid statement [info -f g77 M FOOEY]
! 
!    More details about the above diagnostic is found in the `g77' Info
! documentation, menu item `M', submenu item `FOOEY', which is displayed
! by typing the UNIX command `info -f g77 M FOOEY'.
! 
!    Other Info readers, such as EMACS, may be just as easily used to
! display the pertinent node.  In the above example, `g77' is the Info
! document name, `M' is the top-level menu item to select, and, in that
! node (named `Diagnostics', the name of this chapter, which is the very
! text you're reading now), `FOOEY' is the menu item to select.
! 
! * Menu:
! 
! * CMPAMBIG::    Ambiguous use of intrinsic.
! * EXPIMP::      Intrinsic used explicitly and implicitly.
! * INTGLOB::     Intrinsic also used as name of global.
! * LEX::         Various lexer messages
! * GLOBALS::     Disagreements about globals.
! * LINKFAIL::    When linking `f771' fails.
! * Y2KBAD::      Use of non-Y2K-compliant intrinsic.
! 
! 
! File: g77.info,  Node: CMPAMBIG,  Next: EXPIMP,  Up: Diagnostics
! 
! `CMPAMBIG'
! ==========
! 
!      Ambiguous use of intrinsic INTRINSIC ...
! 
!    The type of the argument to the invocation of the INTRINSIC
! intrinsic is a `COMPLEX' type other than `COMPLEX(KIND=1)'.  Typically,
! it is `COMPLEX(KIND=2)', also known as `DOUBLE COMPLEX'.
! 
!    The interpretation of this invocation depends on the particular
! dialect of Fortran for which the code was written.  Some dialects
! convert the real part of the argument to `REAL(KIND=1)', thus losing
! precision; other dialects, and Fortran 90, do no such conversion.
! 
!    So, GNU Fortran rejects such invocations except under certain
! circumstances, to avoid making an incorrect assumption that results in
! generating the wrong code.
! 
!    To determine the dialect of the program unit, perhaps even whether
! that particular invocation is properly coded, determine how the result
! of the intrinsic is used.
! 
!    The result of INTRINSIC is expected (by the original programmer) to
! be `REAL(KIND=1)' (the non-Fortran-90 interpretation) if:
! 
!    * It is passed as an argument to a procedure that explicitly or
!      implicitly declares that argument `REAL(KIND=1)'.
! 
!      For example, a procedure with no `DOUBLE PRECISION' or `IMPLICIT
!      DOUBLE PRECISION' statement specifying the dummy argument
!      corresponding to an actual argument of `REAL(Z)', where `Z' is
!      declared `DOUBLE COMPLEX', strongly suggests that the programmer
!      expected `REAL(Z)' to return `REAL(KIND=1)' instead of
!      `REAL(KIND=2)'.
! 
!    * It is used in a context that would otherwise not include any
!      `REAL(KIND=2)' but where treating the INTRINSIC invocation as
!      `REAL(KIND=2)' would result in unnecessary promotions and
!      (typically) more expensive operations on the wider type.
! 
!      For example:
! 
!           DOUBLE COMPLEX Z
!           ...
!           R(1) = T * REAL(Z)
! 
!      The above example suggests the programmer expected the real part
!      of `Z' to be converted to `REAL(KIND=1)' before being multiplied
!      by `T' (presumed, along with `R' above, to be type `REAL(KIND=1)').
! 
!      Otherwise, the conversion would have to be delayed until after the
!      multiplication, requiring not only an extra conversion (of `T' to
!      `REAL(KIND=2)'), but a (typically) more expensive multiplication
!      (a double-precision multiplication instead of a single-precision
!      one).
! 
!    The result of INTRINSIC is expected (by the original programmer) to
! be `REAL(KIND=2)' (the Fortran 90 interpretation) if:
! 
!    * It is passed as an argument to a procedure that explicitly or
!      implicitly declares that argument `REAL(KIND=2)'.
! 
!      For example, a procedure specifying a `DOUBLE PRECISION' dummy
!      argument corresponding to an actual argument of `REAL(Z)', where
!      `Z' is declared `DOUBLE COMPLEX', strongly suggests that the
!      programmer expected `REAL(Z)' to return `REAL(KIND=2)' instead of
!      `REAL(KIND=1)'.
! 
!    * It is used in an expression context that includes other
!      `REAL(KIND=2)' operands, or is assigned to a `REAL(KIND=2)'
!      variable or array element.
! 
!      For example:
! 
!           DOUBLE COMPLEX Z
!           DOUBLE PRECISION R, T
!           ...
!           R(1) = T * REAL(Z)
! 
!      The above example suggests the programmer expected the real part
!      of `Z' to _not_ be converted to `REAL(KIND=1)' by the `REAL()'
!      intrinsic.
! 
!      Otherwise, the conversion would have to be immediately followed by
!      a conversion back to `REAL(KIND=2)', losing the original, full
!      precision of the real part of `Z', before being multiplied by `T'.
! 
!    Once you have determined whether a particular invocation of INTRINSIC
! expects the Fortran 90 interpretation, you can:
! 
!    * Change it to `DBLE(EXPR)' (if INTRINSIC is `REAL') or
!      `DIMAG(EXPR)' (if INTRINSIC is `AIMAG') if it expected the Fortran
!      90 interpretation.
! 
!      This assumes EXPR is `COMPLEX(KIND=2)'--if it is some other type,
!      such as `COMPLEX*32', you should use the appropriate intrinsic,
!      such as the one to convert to `REAL*16' (perhaps `DBLEQ()' in
!      place of `DBLE()', and `QIMAG()' in place of `DIMAG()').
! 
!    * Change it to `REAL(INTRINSIC(EXPR))', otherwise.  This converts to
!      `REAL(KIND=1)' in all working Fortran compilers.
! 
!    If you don't want to change the code, and you are certain that all
! ambiguous invocations of INTRINSIC in the source file have the same
! expectation regarding interpretation, you can:
! 
!    * Compile with the `g77' option `-ff90', to enable the Fortran 90
!      interpretation.
! 
!    * Compile with the `g77' options `-fno-f90 -fugly-complex', to
!      enable the non-Fortran-90 interpretations.
! 
!    *Note REAL() and AIMAG() of Complex::, for more information on this
! issue.
! 
!    Note: If the above suggestions don't produce enough evidence as to
! whether a particular program expects the Fortran 90 interpretation of
! this ambiguous invocation of INTRINSIC, there is one more thing you can
! try.
! 
!    If you have access to most or all the compilers used on the program
! to create successfully tested and deployed executables, read the
! documentation for, and _also_ test out, each compiler to determine how
! it treats the INTRINSIC intrinsic in this case.  (If all the compilers
! don't agree on an interpretation, there might be lurking bugs in the
! deployed versions of the program.)
! 
!    The following sample program might help:
! 
!            PROGRAM JCB003
!      C
!      C Written by James Craig Burley 1997-02-23.
!      C
!      C Determine how compilers handle non-standard REAL
!      C and AIMAG on DOUBLE COMPLEX operands.
!      C
!            DOUBLE COMPLEX Z
!            REAL R
!            Z = (3.3D0, 4.4D0)
!            R = Z
!            CALL DUMDUM(Z, R)
!            R = REAL(Z) - R
!            IF (R .NE. 0.) PRINT *, 'REAL() is Fortran 90'
!            IF (R .EQ. 0.) PRINT *, 'REAL() is not Fortran 90'
!            R = 4.4D0
!            CALL DUMDUM(Z, R)
!            R = AIMAG(Z) - R
!            IF (R .NE. 0.) PRINT *, 'AIMAG() is Fortran 90'
!            IF (R .EQ. 0.) PRINT *, 'AIMAG() is not Fortran 90'
!            END
!      C
!      C Just to make sure compiler doesn't use naive flow
!      C analysis to optimize away careful work above,
!      C which might invalidate results....
!      C
!            SUBROUTINE DUMDUM(Z, R)
!            DOUBLE COMPLEX Z
!            REAL R
!            END
! 
!    If the above program prints contradictory results on a particular
! compiler, run away!
! 
! 
! File: g77.info,  Node: EXPIMP,  Next: INTGLOB,  Prev: CMPAMBIG,  Up: Diagnostics
! 
! `EXPIMP'
! ========
! 
!      Intrinsic INTRINSIC referenced ...
! 
!    The INTRINSIC is explicitly declared in one program unit in the
! source file and implicitly used as an intrinsic in another program unit
! in the same source file.
! 
!    This diagnostic is designed to catch cases where a program might
! depend on using the name INTRINSIC as an intrinsic in one program unit
! and as a global name (such as the name of a subroutine or function) in
! another, but `g77' recognizes the name as an intrinsic in both cases.
! 
!    After verifying that the program unit making implicit use of the
! intrinsic is indeed written expecting the intrinsic, add an `INTRINSIC
! INTRINSIC' statement to that program unit to prevent this warning.
! 
!    This and related warnings are disabled by using the `-Wno-globals'
! option when compiling.
! 
!    Note that this warning is not issued for standard intrinsics.
! Standard intrinsics include those described in the FORTRAN 77 standard
! and, if `-ff90' is specified, those described in the Fortran 90
! standard.  Such intrinsics are not as likely to be confused with user
! procedures as intrinsics provided as extensions to the standard by
! `g77'.
! 
! 
! File: g77.info,  Node: INTGLOB,  Next: LEX,  Prev: EXPIMP,  Up: Diagnostics
! 
! `INTGLOB'
! =========
! 
!      Same name `INTRINSIC' given ...
! 
!    The name INTRINSIC is used for a global entity (a common block or a
! program unit) in one program unit and implicitly used as an intrinsic
! in another program unit.
! 
!    This diagnostic is designed to catch cases where a program intends
! to use a name entirely as a global name, but `g77' recognizes the name
! as an intrinsic in the program unit that references the name, a
! situation that would likely produce incorrect code.
! 
!    For example:
! 
!      INTEGER FUNCTION TIME()
!      ...
!      END
!      ...
!      PROGRAM SAMP
!      INTEGER TIME
!      PRINT *, 'Time is ', TIME()
!      END
! 
!    The above example defines a program unit named `TIME', but the
! reference to `TIME' in the main program unit `SAMP' is normally treated
! by `g77' as a reference to the intrinsic `TIME()' (unless a
! command-line option that prevents such treatment has been specified).
! 
!    As a result, the program `SAMP' will _not_ invoke the `TIME'
! function in the same source file.
! 
!    Since `g77' recognizes `libU77' procedures as intrinsics, and since
! some existing code uses the same names for its own procedures as used
! by some `libU77' procedures, this situation is expected to arise often
! enough to make this sort of warning worth issuing.
! 
!    After verifying that the program unit making implicit use of the
! intrinsic is indeed written expecting the intrinsic, add an `INTRINSIC
! INTRINSIC' statement to that program unit to prevent this warning.
! 
!    Or, if you believe the program unit is designed to invoke the
! program-defined procedure instead of the intrinsic (as recognized by
! `g77'), add an `EXTERNAL INTRINSIC' statement to the program unit that
! references the name to prevent this warning.
! 
!    This and related warnings are disabled by using the `-Wno-globals'
! option when compiling.
! 
!    Note that this warning is not issued for standard intrinsics.
! Standard intrinsics include those described in the FORTRAN 77 standard
! and, if `-ff90' is specified, those described in the Fortran 90
! standard.  Such intrinsics are not as likely to be confused with user
! procedures as intrinsics provided as extensions to the standard by
! `g77'.
! 
! 
! File: g77.info,  Node: LEX,  Next: GLOBALS,  Prev: INTGLOB,  Up: Diagnostics
! 
! `LEX'
! =====
! 
!      Unrecognized character ...
!      Invalid first character ...
!      Line too long ...
!      Non-numeric character ...
!      Continuation indicator ...
!      Label at ... invalid with continuation line indicator ...
!      Character constant ...
!      Continuation line ...
!      Statement at ... begins with invalid token
! 
!    Although the diagnostics identify specific problems, they can be
! produced when general problems such as the following occur:
! 
!    * The source file contains something other than Fortran code.
! 
!      If the code in the file does not look like many of the examples
!      elsewhere in this document, it might not be Fortran code.  (Note
!      that Fortran code often is written in lower case letters, while
!      the examples in this document use upper case letters, for
!      stylistic reasons.)
! 
!      For example, if the file contains lots of strange-looking
!      characters, it might be APL source code; if it contains lots of
!      parentheses, it might be Lisp source code; if it contains lots of
!      bugs, it might be C++ source code.
! 
!    * The source file contains free-form Fortran code, but `-ffree-form'
!      was not specified on the command line to compile it.
! 
!      Free form is a newer form for Fortran code.  The older, classic
!      form is called fixed form.
! 
!      Fixed-form code is visually fairly distinctive, because numerical
!      labels and comments are all that appear in the first five columns
!      of a line, the sixth column is reserved to denote continuation
!      lines, and actual statements start at or beyond column 7.  Spaces
!      generally are not significant, so if you see statements such as
!      `REALX,Y' and `DO10I=1,100', you are looking at fixed-form code.
!      Comment lines are indicated by the letter `C' or the symbol `*' in
!      column 1.  (Some code uses `!' or `/*' to begin in-line comments,
!      which many compilers support.)
! 
!      Free-form code is distinguished from fixed-form source primarily
!      by the fact that statements may start anywhere.  (If lots of
!      statements start in columns 1 through 6, that's a strong indicator
!      of free-form source.)  Consecutive keywords must be separated by
!      spaces, so `REALX,Y' is not valid, while `REAL X,Y' is.  There are
!      no comment lines per se, but `!' starts a comment anywhere in a
!      line (other than within a character or Hollerith constant).
! 
!      *Note Source Form::, for more information.
! 
!    * The source file is in fixed form and has been edited without
!      sensitivity to the column requirements.
! 
!      Statements in fixed-form code must be entirely contained within
!      columns 7 through 72 on a given line.  Starting them "early" is
!      more likely to result in diagnostics than finishing them "late",
!      though both kinds of errors are often caught at compile time.
! 
!      For example, if the following code fragment is edited by following
!      the commented instructions literally, the result, shown afterward,
!      would produce a diagnostic when compiled:
! 
!           C On XYZZY systems, remove "C" on next line:
!           C     CALL XYZZY_RESET
! 
!      The result of editing the above line might be:
! 
!           C On XYZZY systems, remove "C" on next line:
!                CALL XYZZY_RESET
! 
!      However, that leaves the first `C' in the `CALL' statement in
!      column 6, making it a comment line, which is not really what the
!      author intended, and which is likely to result in one of the
!      above-listed diagnostics.
! 
!      _Replacing_ the `C' in column 1 with a space is the proper change
!      to make, to ensure the `CALL' keyword starts in or after column 7.
! 
!      Another common mistake like this is to forget that fixed-form
!      source lines are significant through only column 72, and that,
!      normally, any text beyond column 72 is ignored or is diagnosed at
!      compile time.
! 
!      *Note Source Form::, for more information.
! 
!    * The source file requires preprocessing, and the preprocessing is
!      not being specified at compile time.
! 
!      A source file containing lines beginning with `#define',
!      `#include', `#if', and so on is likely one that requires
!      preprocessing.
! 
!      If the file's suffix is `.f', `.for', or `.FOR', the file normally
!      will be compiled _without_ preprocessing by `g77'.
! 
!      Change the file's suffix from `.f' to `.F' (or, on systems with
!      case-insensitive file names, to `.fpp' or `.FPP'), from `.for' to
!      `.fpp', or from `.FOR' to `.FPP'.  `g77' compiles files with such
!      names _with_ preprocessing.
! 
!      Or, learn how to use `gcc''s `-x' option to specify the language
!      `f77-cpp-input' for Fortran files that require preprocessing.
!      *Note Options Controlling the Kind of Output: (gcc)Overall Options.
! 
!    * The source file is preprocessed, and the results of preprocessing
!      result in syntactic errors that are not necessarily obvious to
!      someone examining the source file itself.
! 
!      Examples of errors resulting from preprocessor macro expansion
!      include exceeding the line-length limit, improperly starting,
!      terminating, or incorporating the apostrophe or double-quote in a
!      character constant, improperly forming a Hollerith constant, and
!      so on.
! 
!      *Note Options Controlling the Kind of Output: Overall Options, for
!      suggestions about how to use, and not use, preprocessing for
!      Fortran code.
! 
! 
! File: g77.info,  Node: GLOBALS,  Next: LINKFAIL,  Prev: LEX,  Up: Diagnostics
! 
! `GLOBALS'
! =========
! 
!      Global name NAME defined at ... already defined...
!      Global name NAME at ... has different type...
!      Too many arguments passed to NAME at ...
!      Too few arguments passed to NAME at ...
!      Argument #N of NAME is ...
! 
!    These messages all identify disagreements about the global procedure
! named NAME among different program units (usually including NAME
! itself).
! 
!    Whether a particular disagreement is reported as a warning or an
! error can depend on the relative order of the disagreeing portions of
! the source file.
! 
!    Disagreements between a procedure invocation and the _subsequent_
! procedure itself are, usually, diagnosed as errors when the procedure
! itself _precedes_ the invocation.  Other disagreements are diagnosed
! via warnings.
! 
!    This distinction, between warnings and errors, is due primarily to
! the present tendency of the `gcc' back end to inline only those
! procedure invocations that are _preceded_ by the corresponding
! procedure definitions.  If the `gcc' back end is changed to inline
! "forward references", in which invocations precede definitions, the
! `g77' front end will be changed to treat both orderings as errors,
! accordingly.
! 
!    The sorts of disagreements that are diagnosed by `g77' include
! whether a procedure is a subroutine or function; if it is a function,
! the type of the return value of the procedure; the number of arguments
! the procedure accepts; and the type of each argument.
! 
!    Disagreements regarding global names among program units in a
! Fortran program _should_ be fixed in the code itself.  However, if that
! is not immediately practical, and the code has been working for some
! time, it is possible it will work when compiled with the `-fno-globals'
! option.
! 
!    The `-fno-globals' option causes these diagnostics to all be warnings
! and disables all inlining of references to global procedures (to avoid
! subsequent compiler crashes and bad-code generation).  Use of the
! `-Wno-globals' option as well as `-fno-globals' suppresses all of these
! diagnostics.  (`-Wno-globals' by itself disables only the warnings, not
! the errors.)
! 
!    After using `-fno-globals' to work around these problems, it is wise
! to stop using that option and address them by fixing the Fortran code,
! because such problems, while they might not actually result in bugs on
! some systems, indicate that the code is not as portable as it could be.
! In particular, the code might appear to work on a particular system,
! but have bugs that affect the reliability of the data without
! exhibiting any other outward manifestations of the bugs.
! 
! 
! File: g77.info,  Node: LINKFAIL,  Next: Y2KBAD,  Prev: GLOBALS,  Up: Diagnostics
! 
! `LINKFAIL'
! ==========
! 
! On AIX 4.1, `g77' might not build with the native (non-GNU) tools due
! to a linker bug in coping with the `-bbigtoc' option which leads to a
! `Relocation overflow' error.  The GNU linker is not recommended on
! current AIX versions, though; it was developed under a now-unsupported
! version.  This bug is said to be fixed by `update PTF U455193 for APAR
! IX75823'.
! 
!    Compiling with `-mminimal-toc' might solve this problem, e.g. by
! adding
!      BOOT_CFLAGS='-mminimal-toc -O2 -g'
!    to the `make bootstrap' command line.
! 
! 
! File: g77.info,  Node: Y2KBAD,  Prev: LINKFAIL,  Up: Diagnostics
! 
! `Y2KBAD'
! ========
! 
!      Intrinsic `NAME', invoked at (^), known to be non-Y2K-compliant...
! 
!    This diagnostic indicates that the specific intrinsic invoked by the
! name NAME is known to have an interface that is not Year-2000 (Y2K)
! compliant.
! 
!    *Note Year 2000 (Y2K) Problems::.
! 
! 
! File: g77.info,  Node: Keyword Index,  Prev: Diagnostics,  Up: Top
! 
! Keyword Index
! *************
! 
! * Menu:
! 
! * ! <1>:                                 LEX.
! * ! <2>:                                 Exclamation Point.
! * ! <3>:                                 Trailing Comment.
! * ! <4>:                                 Character Set.
! * !:                                     Statements Comments Lines.
! * ":                                     Character Set.
! * # <1>:                                 Cpp-style directives.
! * #:                                     Character Set.
! * #define:                               Overall Options.
! * #if:                                   Overall Options.
! * #include:                              Overall Options.
! * #include directive:                    Bug Reporting.
! * $:                                     Dollar Signs.
! * %:                                     Character Set.
! * %DESCR() construct:                    %DESCR().
! * %LOC() construct:                      %LOC().
! * %REF() construct:                      %REF().
! * %VAL() construct:                      %VAL().
! * &:                                     Character Set.
! * *:                                     LEX.
! * *N notation <1>:                       Compiler Types.
! * *N notation:                           Star Notation.
! * --driver option <1>:                   Changes.
! * --driver option:                       News.
! * -falias-check option <1>:              Aliasing Assumed To Work.
! * -falias-check option:                  Code Gen Options.
! * -fargument-alias option <1>:           Aliasing Assumed To Work.
! * -fargument-alias option:               Code Gen Options.
! * -fargument-noalias option <1>:         Aliasing Assumed To Work.
! * -fargument-noalias option:             Code Gen Options.
! * -fbadu77-intrinsics-delete option:     Fortran Dialect Options.
! * -fbadu77-intrinsics-disable option:    Fortran Dialect Options.
! * -fbadu77-intrinsics-enable option:     Fortran Dialect Options.
! * -fbadu77-intrinsics-hide option:       Fortran Dialect Options.
! * -fbounds-check option:                 Code Gen Options.
! * -fcaller-saves option:                 Optimize Options.
! * -fcase-initcap option:                 Fortran Dialect Options.
! * -fcase-lower option:                   Fortran Dialect Options.
! * -fcase-preserve option:                Fortran Dialect Options.
! * -fcase-strict-lower option:            Fortran Dialect Options.
! * -fcase-strict-upper option:            Fortran Dialect Options.
! * -fcase-upper option:                   Fortran Dialect Options.
! * -fdelayed-branch option:               Optimize Options.
! * -fdollar-ok option:                    Fortran Dialect Options.
! * -femulate-complex option:              Code Gen Options.
! * -fexpensive-optimizations option:      Optimize Options.
! * -ff2c-intrinsics-delete option:        Fortran Dialect Options.
! * -ff2c-intrinsics-disable option:       Fortran Dialect Options.
! * -ff2c-intrinsics-enable option:        Fortran Dialect Options.
! * -ff2c-intrinsics-hide option:          Fortran Dialect Options.
! * -ff2c-library option:                  Code Gen Options.
! * -ff66 option:                          Shorthand Options.
! * -ff77 option:                          Shorthand Options.
! * -ff90:                                 Fortran 90 Features.
! * -ff90 option:                          Fortran Dialect Options.
! * -ff90-intrinsics-delete option:        Fortran Dialect Options.
! * -ff90-intrinsics-disable option:       Fortran Dialect Options.
! * -ff90-intrinsics-enable option:        Fortran Dialect Options.
! * -ff90-intrinsics-hide option:          Fortran Dialect Options.
! * -ffast-math option:                    Optimize Options.
! * -ffinite-math-only option:             Optimize Options.
! * -ffixed-line-length-N option:          Fortran Dialect Options.
! * -fflatten-arrays option:               Code Gen Options.
! * -ffloat-store option:                  Optimize Options.
! * -fforce-addr option:                   Optimize Options.
! * -fforce-mem option:                    Optimize Options.
! * -ffortran-bounds-check option:         Code Gen Options.
! * -ffree-form:                           Fortran 90 Features.
! * -ffree-form option:                    Fortran Dialect Options.
! * -fgnu-intrinsics-delete option:        Fortran Dialect Options.
! * -fgnu-intrinsics-disable option:       Fortran Dialect Options.
! * -fgnu-intrinsics-enable option:        Fortran Dialect Options.
! * -fgnu-intrinsics-hide option:          Fortran Dialect Options.
! * -fGROUP-intrinsics-hide option:        Overly Convenient Options.
! * -finit-local-zero option <1>:          Overly Convenient Options.
! * -finit-local-zero option:              Code Gen Options.
! * -fintrin-case-any option:              Fortran Dialect Options.
! * -fintrin-case-initcap option:          Fortran Dialect Options.
! * -fintrin-case-lower option:            Fortran Dialect Options.
! * -fintrin-case-upper option:            Fortran Dialect Options.
! * -fmatch-case-any option:               Fortran Dialect Options.
! * -fmatch-case-initcap option:           Fortran Dialect Options.
! * -fmatch-case-lower option:             Fortran Dialect Options.
! * -fmatch-case-upper option:             Fortran Dialect Options.
! * -fmil-intrinsics-delete option:        Fortran Dialect Options.
! * -fmil-intrinsics-disable option:       Fortran Dialect Options.
! * -fmil-intrinsics-enable option:        Fortran Dialect Options.
! * -fmil-intrinsics-hide option:          Fortran Dialect Options.
! * -fno-argument-noalias-global option <1>: Aliasing Assumed To Work.
! * -fno-argument-noalias-global option:   Code Gen Options.
! * -fno-automatic option <1>:             Overly Convenient Options.
! * -fno-automatic option:                 Code Gen Options.
! * -fno-backslash option:                 Fortran Dialect Options.
! * -fno-common option:                    Code Gen Options.
! * -fno-f2c option <1>:                   Avoid f2c Compatibility.
! * -fno-f2c option:                       Code Gen Options.
! * -fno-f77 option:                       Shorthand Options.
! * -fno-fixed-form option:                Fortran Dialect Options.
! * -fno-globals option:                   Code Gen Options.
! * -fno-ident option:                     Code Gen Options.
! * -fno-inline option:                    Optimize Options.
! * -fno-move-all-movables option:         Optimize Options.
! * -fno-reduce-all-givs option:           Optimize Options.
! * -fno-rerun-loop-opt option:            Optimize Options.
! * -fno-second-underscore:                f2c Skeletons and Prototypes.
! * -fno-second-underscore option <1>:     Names.
! * -fno-second-underscore option:         Code Gen Options.
! * -fno-silent option:                    Overall Options.
! * -fno-trapping-math option:             Optimize Options.
! * -fno-ugly option:                      Shorthand Options.
! * -fno-ugly-args option:                 Fortran Dialect Options.
! * -fno-ugly-init option:                 Fortran Dialect Options.
! * -fno-underscoring option <1>:          Names.
! * -fno-underscoring option:              Code Gen Options.
! * -fonetrip option:                      Fortran Dialect Options.
! * -fpack-struct option:                  Code Gen Options.
! * -fpcc-struct-return option:            Code Gen Options.
! * -fpedantic option:                     Warning Options.
! * -fPIC option:                          News.
! * -freg-struct-return option:            Code Gen Options.
! * -frerun-cse-after-loop option:         Optimize Options.
! * -fschedule-insns option:               Optimize Options.
! * -fschedule-insns2 option:              Optimize Options.
! * -fset-g77-defaults option:             Overall Options.
! * -fshort-double option:                 Code Gen Options.
! * -fsource-case-lower option:            Fortran Dialect Options.
! * -fsource-case-preserve option:         Fortran Dialect Options.
! * -fsource-case-upper option:            Fortran Dialect Options.
! * -fstrength-reduce option:              Optimize Options.
! * -fsymbol-case-any option:              Fortran Dialect Options.
! * -fsymbol-case-initcap option:          Fortran Dialect Options.
! * -fsymbol-case-lower option:            Fortran Dialect Options.
! * -fsymbol-case-upper option:            Fortran Dialect Options.
! * -fsyntax-only option:                  Warning Options.
! * -ftypeless-boz option:                 Fortran Dialect Options.
! * -fugly option:                         Shorthand Options.
! * -fugly-assign option:                  Fortran Dialect Options.
! * -fugly-assumed option:                 Fortran Dialect Options.
! * -fugly-comma option:                   Fortran Dialect Options.
! * -fugly-complex option:                 Fortran Dialect Options.
! * -fugly-logint option:                  Fortran Dialect Options.
! * -funix-intrinsics-delete option:       Fortran Dialect Options.
! * -funix-intrinsics-disable option:      Fortran Dialect Options.
! * -funix-intrinsics-enable option:       Fortran Dialect Options.
! * -funix-intrinsics-hide option:         Fortran Dialect Options.
! * -funroll-all-loops option:             Optimize Options.
! * -funroll-loops option:                 Optimize Options.
! * -funsafe-math-optimizations option:    Optimize Options.
! * -fversion option:                      Overall Options.
! * -fvxt option:                          Fortran Dialect Options.
! * -fvxt-intrinsics-delete option:        Fortran Dialect Options.
! * -fvxt-intrinsics-disable option:       Fortran Dialect Options.
! * -fvxt-intrinsics-enable option:        Fortran Dialect Options.
! * -fvxt-intrinsics-hide option:          Fortran Dialect Options.
! * -fzeros option:                        Code Gen Options.
! * -g option:                             Debugging Options.
! * -I- option:                            Directory Options.
! * -i8:                                   Increasing Precision/Range.
! * -Idir option:                          Directory Options.
! * -malign-double <1>:                    Changes.
! * -malign-double:                        News.
! * -malign-double option <1>:             Aligned Data.
! * -malign-double option:                 Optimize Options.
! * -Nl option:                            Compiler Limits.
! * -Nx option:                            Compiler Limits.
! * -O2:                                   News.
! * -pedantic option:                      Warning Options.
! * -pedantic-errors option:               Warning Options.
! * -qrealsize=8:                          Increasing Precision/Range.
! * -r8:                                   Increasing Precision/Range.
! * -u option:                             Warning Options.
! * -v option:                             G77 and GCC.
! * -W option:                             Warning Options.
! * -w option:                             Warning Options.
! * -Waggregate-return option:             Warning Options.
! * -Wall option:                          Warning Options.
! * -Wcomment option:                      Warning Options.
! * -Wconversion option:                   Warning Options.
! * -Werror option:                        Warning Options.
! * -Wformat option:                       Warning Options.
! * -Wid-clash-LEN option:                 Warning Options.
! * -Wimplicit option:                     Warning Options.
! * -Wlarger-than-LEN option:              Warning Options.
! * -Wno-globals option:                   Warning Options.
! * -Wparentheses option:                  Warning Options.
! * -Wredundant-decls option:              Warning Options.
! * -Wshadow option:                       Warning Options.
! * -Wsurprising option:                   Warning Options.
! * -Wswitch option:                       Warning Options.
! * -Wswitch-default option:               Warning Options.
! * -Wswitch-enum option:                  Warning Options.
! * -Wtraditional option:                  Warning Options.
! * -Wuninitialized option:                Warning Options.
! * -Wunused option:                       Warning Options.
! * -x f77-cpp-input option:               LEX.
! * .EQV., with integer operands:          Equivalence Versus Equality.
! * .F filename suffix:                    Overall Options.
! * .f filename suffix:                    Overall Options.
! * .FOR filename suffix:                  Overall Options.
! * .for filename suffix:                  Overall Options.
! * .FPP filename suffix:                  Overall Options.
! * .fpp filename suffix:                  Overall Options.
! * .gdbinit:                              Main Program Unit.
! * .r filename suffix:                    Overall Options.
! * /* <1>:                                Trailing Comment.
! * /*:                                    Overall Options.
! * /WARNINGS=DECLARATIONS switch:         Warning Options.
! * 80-bit spills:                         Floating-point Errors.
! * ; <1>:                                 Character Set.
! * ;:                                     Statements Comments Lines.
! * <:                                     Character Set.
! * <> edit descriptor:                    I/O.
! * >:                                     Character Set.
! * ?:                                     Character Set.
! * \:                                     Character Set.
! * _:                                     Character Set.
! * Abort intrinsic:                       Abort Intrinsic.
! * Abs intrinsic:                         Abs Intrinsic.
! * ACCEPT statement:                      TYPE and ACCEPT I/O Statements.
! * Access intrinsic:                      Access Intrinsic.
! * AChar intrinsic:                       AChar Intrinsic.
! * ACos intrinsic:                        ACos Intrinsic.
! * ACosD intrinsic:                       ACosD Intrinsic.
! * adding options:                        Adding Options.
! * adjustable arrays:                     Adjustable Arrays.
! * AdjustL intrinsic:                     AdjustL Intrinsic.
! * AdjustR intrinsic:                     AdjustR Intrinsic.
! * AImag intrinsic <1>:                   AImag Intrinsic.
! * AImag intrinsic:                       REAL() and AIMAG() of Complex.
! * AIMax0 intrinsic:                      AIMax0 Intrinsic.
! * AIMin0 intrinsic:                      AIMin0 Intrinsic.
! * AInt intrinsic:                        AInt Intrinsic.
! * AJMax0 intrinsic:                      AJMax0 Intrinsic.
! * AJMin0 intrinsic:                      AJMin0 Intrinsic.
! * Alarm intrinsic:                       Alarm Intrinsic.
! * aliasing <1>:                          Known Bugs.
! * aliasing:                              Aliasing Assumed To Work.
! * aligned data:                          Aligned Data.
! * aligned stack:                         Aligned Data.
! * alignment <1>:                         Aligned Data.
! * alignment <2>:                         Changes.
! * alignment:                             News.
! * alignment testing:                     Aligned Data.
! * All intrinsic:                         All Intrinsic.
! * all warnings:                          Warning Options.
! * Allocated intrinsic:                   Allocated Intrinsic.
! * ALog intrinsic:                        ALog Intrinsic.
! * ALog10 intrinsic:                      ALog10 Intrinsic.
! * Alpha, support:                        Known Bugs.
! * alternate entry points:                Alternate Entry Points.
! * alternate returns:                     Alternate Returns.
! * ALWAYS_FLUSH:                          Output Assumed To Flush.
! * AMax0 intrinsic:                       AMax0 Intrinsic.
! * AMax1 intrinsic:                       AMax1 Intrinsic.
! * AMin0 intrinsic:                       AMin0 Intrinsic.
! * AMin1 intrinsic:                       AMin1 Intrinsic.
! * AMod intrinsic:                        AMod Intrinsic.
! * ampersand:                             Character Set.
! * ampersand continuation line:           Ampersands.
! * And intrinsic <1>:                     Bit Operations on Floating-point Data.
! * And intrinsic:                         And Intrinsic.
! * ANInt intrinsic:                       ANInt Intrinsic.
! * ANS carriage control:                  OPEN CLOSE and INQUIRE Keywords.
! * ANSI FORTRAN 77 standard:              Language.
! * ANSI FORTRAN 77 support:               Standard Support.
! * anti-aliasing:                         Aliasing Assumed To Work.
! * Any intrinsic:                         Any Intrinsic.
! * arguments, null:                       Ugly Null Arguments.
! * arguments, omitting:                   Ugly Null Arguments.
! * arguments, unused <1>:                 Unused Arguments.
! * arguments, unused:                     Warning Options.
! * array bounds checking:                 Code Gen Options.
! * array bounds, adjustable:              Array Bounds Expressions.
! * array elements, in adjustable array bounds: Array Bounds Expressions.
! * array ordering:                        Arrays.
! * array performance:                     Code Gen Options.
! * array size:                            Array Size.
! * arrays:                                Arrays.
! * arrays, adjustable:                    Adjustable Arrays.
! * arrays, assumed-size:                  Ugly Assumed-Size Arrays.
! * arrays, automatic <1>:                 Large Automatic Arrays.
! * arrays, automatic <2>:                 Stack Overflow.
! * arrays, automatic <3>:                 Overly Convenient Options.
! * arrays, automatic:                     Adjustable Arrays.
! * arrays, dimensioning <1>:              Adjustable Arrays.
! * arrays, dimensioning:                  Array Size.
! * arrays, flattening:                    Code Gen Options.
! * as command:                            What is GNU Fortran?.
! * ASin intrinsic:                        ASin Intrinsic.
! * ASinD intrinsic:                       ASinD Intrinsic.
! * assembler:                             What is GNU Fortran?.
! * assembly code:                         What is GNU Fortran?.
! * assembly code, invalid:                Bug Criteria.
! * ASSIGN statement <1>:                  Assigned Statement Labels.
! * ASSIGN statement:                      Ugly Assigned Labels.
! * assigned labels:                       Ugly Assigned Labels.
! * assigned statement labels:             Assigned Statement Labels.
! * Associated intrinsic:                  Associated Intrinsic.
! * association, storage:                  Aliasing Assumed To Work.
! * assumed-size arrays:                   Ugly Assumed-Size Arrays.
! * asterisk:                              LEX.
! * ATan intrinsic:                        ATan Intrinsic.
! * ATan2 intrinsic:                       ATan2 Intrinsic.
! * ATan2D intrinsic:                      ATan2D Intrinsic.
! * ATanD intrinsic:                       ATanD Intrinsic.
! * automatic arrays <1>:                  Large Automatic Arrays.
! * automatic arrays <2>:                  Stack Overflow.
! * automatic arrays <3>:                  Overly Convenient Options.
! * automatic arrays:                      Adjustable Arrays.
! * AUTOMATIC statement:                   AUTOMATIC Statement.
! * automatic variables:                   AUTOMATIC Statement.
! * back end, gcc <1>:                     Philosophy of Code Generation.
! * back end, gcc:                         What is GNU Fortran?.
! * backslash <1>:                         Backslash in Constants.
! * backslash <2>:                         Character Set.
! * backslash:                             Fortran Dialect Options.
! * backtrace for bug reports:             Bug Reporting.
! * badu77 intrinsics:                     Fortran Dialect Options.
! * badu77 intrinsics group:               Intrinsic Groups.
! * basic concepts:                        What is GNU Fortran?.
! * Bear-poking:                           Philosophy of Code Generation.
! * beginners:                             Getting Started.
! * BesJ0 intrinsic:                       BesJ0 Intrinsic.
! * BesJ1 intrinsic:                       BesJ1 Intrinsic.
! * BesJN intrinsic:                       BesJN Intrinsic.
! * BesY0 intrinsic:                       BesY0 Intrinsic.
! * BesY1 intrinsic:                       BesY1 Intrinsic.
! * BesYN intrinsic:                       BesYN Intrinsic.
! * binary data:                           Portable Unformatted Files.
! * Bit_Size intrinsic:                    Bit_Size Intrinsic.
! * BITest intrinsic:                      BITest Intrinsic.
! * BJTest intrinsic:                      BJTest Intrinsic.
! * blank <1>:                             Lines.
! * blank:                                 Character Set.
! * block data:                            Multiple Definitions of External Names.
! * block data and libraries:              Block Data and Libraries.
! * BLOCK DATA statement <1>:              Multiple Definitions of External Names.
! * BLOCK DATA statement:                  Block Data and Libraries.
! * bounds checking:                       Code Gen Options.
! * BTest intrinsic:                       BTest Intrinsic.
! * bug criteria:                          Bug Criteria.
! * bug report mailing lists:              Bug Lists.
! * bugs:                                  Bugs.
! * bugs, finding:                         What is GNU Fortran?.
! * bugs, known:                           Trouble.
! * bus error <1>:                         Strange Behavior at Run Time.
! * bus error:                             NeXTStep Problems.
! * but-bugs:                              But-bugs.
! * byte ordering:                         Portable Unformatted Files.
! * C library:                             Strange Behavior at Run Time.
! * C preprocessor:                        Overall Options.
! * C routines calling Fortran:            Debugging and Interfacing.
! * C++:                                   C++ Considerations.
! * C++, linking with:                     Interoperating with C and C++.
! * C, linking with:                       Interoperating with C and C++.
! * CAbs intrinsic:                        CAbs Intrinsic.
! * calling C routines:                    Debugging and Interfacing.
! * card image:                            Fortran Dialect Options.
! * carriage control:                      OPEN CLOSE and INQUIRE Keywords.
! * carriage returns:                      Carriage Returns.
! * case sensitivity:                      Case Sensitivity.
! * cc1 program:                           What is GNU Fortran?.
! * cc1plus program:                       What is GNU Fortran?.
! * CCos intrinsic:                        CCos Intrinsic.
! * CDAbs intrinsic:                       CDAbs Intrinsic.
! * CDCos intrinsic:                       CDCos Intrinsic.
! * CDExp intrinsic:                       CDExp Intrinsic.
! * CDLog intrinsic:                       CDLog Intrinsic.
! * CDSin intrinsic:                       CDSin Intrinsic.
! * CDSqRt intrinsic:                      CDSqRt Intrinsic.
! * Ceiling intrinsic:                     Ceiling Intrinsic.
! * CExp intrinsic:                        CExp Intrinsic.
! * cfortran.h:                            C Interfacing Tools.
! * changes, user-visible:                 Changes.
! * Char intrinsic:                        Char Intrinsic.
! * character assignments:                 Fortran 90 Features.
! * character constants <1>:               Character and Hollerith Constants.
! * character constants <2>:               Ugly Conversion of Initializers.
! * character constants <3>:               Double Quote Meaning.
! * character constants:                   Fortran Dialect Options.
! * character set:                         Fortran Dialect Options.
! * CHARACTER*(*):                         Arbitrary Concatenation.
! * CHARACTER, null:                       Character Type.
! * character-variable length:             Character-variable Length.
! * characters:                            Character Set.
! * characters, comma:                     Ugly Null Arguments.
! * characters, comment <1>:               LEX.
! * characters, comment <2>:               Exclamation Point.
! * characters, comment <3>:               Trailing Comment.
! * characters, comment:                   Statements Comments Lines.
! * characters, continuation <1>:          LEX.
! * characters, continuation <2>:          Exclamation Point.
! * characters, continuation:              Statements Comments Lines.
! * ChDir intrinsic <1>:                   ChDir Intrinsic (function).
! * ChDir intrinsic:                       ChDir Intrinsic (subroutine).
! * checking subscripts:                   Code Gen Options.
! * checking substrings:                   Code Gen Options.
! * checks, of internal consistency:       Overall Options.
! * ChMod intrinsic <1>:                   ChMod Intrinsic (function).
! * ChMod intrinsic:                       ChMod Intrinsic (subroutine).
! * CLog intrinsic:                        CLog Intrinsic.
! * close angle:                           Character Set.
! * close bracket:                         Character Set.
! * CLOSE statement:                       OPEN CLOSE and INQUIRE Keywords.
! * Cmplx intrinsic <1>:                   Cmplx Intrinsic.
! * Cmplx intrinsic:                       CMPLX() of DOUBLE PRECISION.
! * code generation, conventions:          Code Gen Options.
! * code generation, improving:            Better Optimization.
! * code generator <1>:                    Philosophy of Code Generation.
! * code generator:                        What is GNU Fortran?.
! * code, assembly:                        What is GNU Fortran?.
! * code, displaying main source:          Known Bugs.
! * code, in-line:                         What is GNU Fortran?.
! * code, legacy:                          Collected Fortran Wisdom.
! * code, machine:                         What is GNU Fortran?.
! * code, source <1>:                      Case Sensitivity.
! * code, source <2>:                      Source Form.
! * code, source <3>:                      Lines.
! * code, source:                          What is GNU Fortran?.
! * code, user:                            Cannot Link Fortran Programs.
! * code, writing:                         Collected Fortran Wisdom.
! * column-major ordering:                 Arrays.
! * columns 73 through 80:                 Better Source Model.
! * comma, trailing:                       Ugly Null Arguments.
! * command options:                       Invoking G77.
! * commands, as:                          What is GNU Fortran?.
! * commands, g77 <1>:                     G77 and GCC.
! * commands, g77:                         What is GNU Fortran?.
! * commands, gcc <1>:                     G77 and GCC.
! * commands, gcc:                         What is GNU Fortran?.
! * commands, gdb:                         What is GNU Fortran?.
! * commands, ld:                          What is GNU Fortran?.
! * comment <1>:                           LEX.
! * comment <2>:                           Trailing Comment.
! * comment:                               Statements Comments Lines.
! * comment character:                     Exclamation Point.
! * comment line, debug <1>:               Enabling Debug Lines.
! * comment line, debug:                   Debug Line.
! * common blocks <1>:                     Mangling of Names.
! * common blocks <2>:                     Known Bugs.
! * common blocks:                         Common Blocks.
! * common blocks, large:                  Large Common Blocks.
! * COMMON layout:                         Aligned Data.
! * COMMON statement <1>:                  Multiple Definitions of External Names.
! * COMMON statement:                      Common Blocks.
! * comparing logical expressions:         Equivalence Versus Equality.
! * compatibility, f2c <1>:                Avoid f2c Compatibility.
! * compatibility, f2c <2>:                Block Data and Libraries.
! * compatibility, f2c <3>:                Code Gen Options.
! * compatibility, f2c <4>:                Shorthand Options.
! * compatibility, f2c:                    Overall Options.
! * compatibility, f77:                    Shorthand Options.
! * compatibility, FORTRAN 66 <1>:         Fortran Dialect Options.
! * compatibility, FORTRAN 66:             Shorthand Options.
! * compatibility, FORTRAN 77:             Standard Support.
! * compatibility, Fortran 90:             Fortran 90.
! * compilation, in-line <1>:              GLOBALS.
! * compilation, in-line <2>:              Code Gen Options.
! * compilation, in-line:                  Optimize Options.
! * compilation, pedantic:                 Pedantic Compilation.
! * compilation, status:                   Overall Options.
! * compiler bugs, reporting:              Bug Reporting.
! * compiler limits:                       Compiler Limits.
! * compiler memory usage:                 Known Bugs.
! * compiler speed:                        Known Bugs.
! * compilers:                             What is GNU Fortran?.
! * compiling programs:                    G77 and GCC.
! * Complex intrinsic:                     Complex Intrinsic.
! * COMPLEX intrinsics:                    Fortran Dialect Options.
! * complex performance:                   Known Bugs.
! * COMPLEX statement:                     Complex Variables.
! * complex values:                        Ugly Complex Part Extraction.
! * complex variables:                     Complex Variables.
! * COMPLEX(KIND=1) type:                  Compiler Types.
! * COMPLEX(KIND=2) type:                  Compiler Types.
! * components of g77:                     What is GNU Fortran?.
! * concatenation:                         Arbitrary Concatenation.
! * concepts, basic:                       What is GNU Fortran?.
! * conformance, IEEE 754 <1>:             Floating-point precision.
! * conformance, IEEE 754:                 Optimize Options.
! * Conjg intrinsic:                       Conjg Intrinsic.
! * consistency checks:                    Overall Options.
! * constants <1>:                         Compiler Constants.
! * constants:                             Constants.
! * constants, character <1>:              Character and Hollerith Constants.
! * constants, character <2>:              Ugly Conversion of Initializers.
! * constants, character:                  Double Quote Meaning.
! * constants, context-sensitive:          Context-Sensitive Constants.
! * constants, Hollerith <1>:              Character and Hollerith Constants.
! * constants, Hollerith <2>:              Ugly Conversion of Initializers.
! * constants, Hollerith:                  Ugly Implicit Argument Conversion.
! * constants, integer:                    Known Bugs.
! * constants, octal:                      Double Quote Meaning.
! * constants, prefix-radix:               Fortran Dialect Options.
! * constants, types:                      Fortran Dialect Options.
! * construct names:                       Construct Names.
! * context-sensitive constants:           Context-Sensitive Constants.
! * context-sensitive intrinsics:          Context-Sensitive Intrinsicness.
! * continuation character <1>:            LEX.
! * continuation character <2>:            Exclamation Point.
! * continuation character:                Statements Comments Lines.
! * continuation line, ampersand:          Ampersands.
! * continuation line, number of:          Continuation Line.
! * contributors:                          Contributors.
! * conversions, nonportable:              Nonportable Conversions.
! * core dump:                             Bug Criteria.
! * Cos intrinsic:                         Cos Intrinsic.
! * CosD intrinsic:                        CosD Intrinsic.
! * CosH intrinsic:                        CosH Intrinsic.
! * Count intrinsic:                       Count Intrinsic.
! * cpp preprocessor:                      Overall Options.
! * cpp program <1>:                       LEX.
! * cpp program <2>:                       Bug Reporting.
! * cpp program <3>:                       Preprocessor Options.
! * cpp program <4>:                       Overall Options.
! * cpp program:                           What is GNU Fortran?.
! * CPU_Time intrinsic:                    CPU_Time Intrinsic.
! * Cray pointers:                         POINTER Statements.
! * credits:                               Contributors.
! * CShift intrinsic:                      CShift Intrinsic.
! * CSin intrinsic:                        CSin Intrinsic.
! * CSqRt intrinsic:                       CSqRt Intrinsic.
! * CTime intrinsic <1>:                   CTime Intrinsic (function).
! * CTime intrinsic:                       CTime Intrinsic (subroutine).
! * CYCLE statement:                       CYCLE and EXIT.
! * DAbs intrinsic:                        DAbs Intrinsic.
! * DACos intrinsic:                       DACos Intrinsic.
! * DACosD intrinsic:                      DACosD Intrinsic.
! * DASin intrinsic:                       DASin Intrinsic.
! * DASinD intrinsic:                      DASinD Intrinsic.
! * DATA statement <1>:                    Known Bugs.
! * DATA statement:                        Code Gen Options.
! * data types:                            Compiler Types.
! * data, aligned:                         Aligned Data.
! * data, overwritten:                     Strange Behavior at Run Time.
! * DATan intrinsic:                       DATan Intrinsic.
! * DATan2 intrinsic:                      DATan2 Intrinsic.
! * DATan2D intrinsic:                     DATan2D Intrinsic.
! * DATanD intrinsic:                      DATanD Intrinsic.
! * Date intrinsic:                        Date Intrinsic.
! * Date_and_Time intrinsic:               Date_and_Time Intrinsic.
! * date_y2kbuggy_0:                       Year 2000 (Y2K) Problems.
! * DbesJ0 intrinsic:                      DbesJ0 Intrinsic.
! * DbesJ1 intrinsic:                      DbesJ1 Intrinsic.
! * DbesJN intrinsic:                      DbesJN Intrinsic.
! * DbesY0 intrinsic:                      DbesY0 Intrinsic.
! * DbesY1 intrinsic:                      DbesY1 Intrinsic.
! * DbesYN intrinsic:                      DbesYN Intrinsic.
! * Dble intrinsic:                        Dble Intrinsic.
! * DbleQ intrinsic:                       DbleQ Intrinsic.
! * DCmplx intrinsic:                      DCmplx Intrinsic.
! * DConjg intrinsic:                      DConjg Intrinsic.
! * DCos intrinsic:                        DCos Intrinsic.
! * DCosD intrinsic:                       DCosD Intrinsic.
! * DCosH intrinsic:                       DCosH Intrinsic.
! * DDiM intrinsic:                        DDiM Intrinsic.
! * debug line <1>:                        Enabling Debug Lines.
! * debug line:                            Debug Line.
! * debug_rtx:                             Bug Reporting.
! * debugger <1>:                          Known Bugs.
! * debugger:                              What is GNU Fortran?.
! * debugging <1>:                         Names.
! * debugging <2>:                         Main Program Unit.
! * debugging:                             Debugging and Interfacing.
! * debugging information options:         Debugging Options.
! * debugging main source code:            Known Bugs.
! * DECODE statement:                      ENCODE and DECODE.
! * deleted intrinsics:                    Intrinsic Groups.
! * DErF intrinsic:                        DErF Intrinsic.
! * DErFC intrinsic:                       DErFC Intrinsic.
! * DExp intrinsic:                        DExp Intrinsic.
! * DFloat intrinsic:                      DFloat Intrinsic.
! * DFlotI intrinsic:                      DFlotI Intrinsic.
! * DFlotJ intrinsic:                      DFlotJ Intrinsic.
! * diagnostics:                           Diagnostics.
! * diagnostics, incorrect:                What is GNU Fortran?.
! * dialect options:                       Fortran Dialect Options.
! * Digital Fortran features:              Fortran Dialect Options.
! * Digits intrinsic:                      Digits Intrinsic.
! * DiM intrinsic:                         DiM Intrinsic.
! * DImag intrinsic:                       DImag Intrinsic.
! * DIMENSION statement <1>:               Array Bounds Expressions.
! * DIMENSION statement <2>:               Adjustable Arrays.
! * DIMENSION statement:                   Arrays.
! * DIMENSION X(1):                        Ugly Assumed-Size Arrays.
! * dimensioning arrays:                   Adjustable Arrays.
! * DInt intrinsic:                        DInt Intrinsic.
! * direction of language development:     Direction of Language Development.
! * directive, #include:                   Bug Reporting.
! * directive, INCLUDE <1>:                Bug Reporting.
! * directive, INCLUDE <2>:                Directory Options.
! * directive, INCLUDE:                    Preprocessor Options.
! * directory, options:                    Directory Options.
! * directory, search paths for inclusion: Directory Options.
! * disabled intrinsics:                   Intrinsic Groups.
! * disk full:                             Output Assumed To Flush.
! * displaying main source code:           Known Bugs.
! * disposition of files:                  OPEN CLOSE and INQUIRE Keywords.
! * distensions:                           Distensions.
! * DLog intrinsic:                        DLog Intrinsic.
! * DLog10 intrinsic:                      DLog10 Intrinsic.
! * DMax1 intrinsic:                       DMax1 Intrinsic.
! * DMin1 intrinsic:                       DMin1 Intrinsic.
! * DMod intrinsic:                        DMod Intrinsic.
! * DNInt intrinsic:                       DNInt Intrinsic.
! * DNRM2:                                 News.
! * DO:                                    DO WHILE.
! * DO loops, one-trip:                    Fortran Dialect Options.
! * DO loops, zero-trip:                   Fortran Dialect Options.
! * DO statement <1>:                      Loops.
! * DO statement:                          Warning Options.
! * DO WHILE <1>:                          DO WHILE.
! * DO WHILE:                              Optimize Options.
! * dollar sign <1>:                       Dollar Signs.
! * dollar sign <2>:                       I/O.
! * dollar sign:                           Fortran Dialect Options.
! * Dot_Product intrinsic:                 Dot_Product Intrinsic.
! * DOUBLE COMPLEX:                        DOUBLE COMPLEX.
! * DOUBLE COMPLEX type:                   Compiler Types.
! * DOUBLE PRECISION type:                 Compiler Types.
! * double quote:                          Character Set.
! * double quoted character constants <1>: Fortran 90 Features.
! * double quoted character constants:     Character Type.
! * double quotes:                         Double Quote Meaning.
! * double-precision performance <1>:      Changes.
! * double-precision performance:          News.
! * DProd intrinsic:                       DProd Intrinsic.
! * DReal intrinsic:                       DReal Intrinsic.
! * driver, gcc command as:                What is GNU Fortran?.
! * DSign intrinsic:                       DSign Intrinsic.
! * DSin intrinsic:                        DSin Intrinsic.
! * DSinD intrinsic:                       DSinD Intrinsic.
! * DSinH intrinsic:                       DSinH Intrinsic.
! * DSqRt intrinsic:                       DSqRt Intrinsic.
! * DTan intrinsic:                        DTan Intrinsic.
! * DTanD intrinsic:                       DTanD Intrinsic.
! * DTanH intrinsic:                       DTanH Intrinsic.
! * DTime intrinsic <1>:                   DTime Intrinsic (function).
! * DTime intrinsic:                       DTime Intrinsic (subroutine).
! * dummies, unused:                       Warning Options.
! * edit descriptor, <>:                   I/O.
! * edit descriptor, O:                    I/O.
! * edit descriptor, Q:                    Q Edit Descriptor.
! * edit descriptor, Z <1>:                Fortran 90 Features.
! * edit descriptor, Z:                    I/O.
! * effecting IMPLICIT NONE:               Warning Options.
! * efficiency:                            Efficiency.
! * ELF support:                           News.
! * empty CHARACTER strings:               Character Type.
! * enabled intrinsics:                    Intrinsic Groups.
! * ENCODE statement:                      ENCODE and DECODE.
! * END DO:                                END DO.
! * entry points:                          Alternate Entry Points.
! * ENTRY statement:                       Alternate Entry Points.
! * environment variables:                 Environment Variables.
! * EOShift intrinsic:                     EOShift Intrinsic.
! * Epsilon intrinsic:                     Epsilon Intrinsic.
! * equivalence areas <1>:                 Known Bugs.
! * equivalence areas:                     Local Equivalence Areas.
! * EQUIVALENCE statement:                 Local Equivalence Areas.
! * ErF intrinsic:                         ErF Intrinsic.
! * ErFC intrinsic:                        ErFC Intrinsic.
! * error messages <1>:                    Warnings and Errors.
! * error messages:                        Run-time Library Errors.
! * error messages, incorrect:             What is GNU Fortran?.
! * error values:                          Run-time Library Errors.
! * errors, linker:                        Large Common Blocks.
! * ETime intrinsic <1>:                   ETime Intrinsic (function).
! * ETime intrinsic:                       ETime Intrinsic (subroutine).
! * exceptions, floating-point:            Floating-point Exception Handling.
! * exclamation point <1>:                 LEX.
! * exclamation point <2>:                 Exclamation Point.
! * exclamation point <3>:                 Trailing Comment.
! * exclamation point <4>:                 Character Set.
! * exclamation point:                     Statements Comments Lines.
! * executable file:                       What is GNU Fortran?.
! * Exit intrinsic:                        Exit Intrinsic.
! * EXIT statement:                        CYCLE and EXIT.
! * Exp intrinsic:                         Exp Intrinsic.
! * Exponent intrinsic:                    Exponent Intrinsic.
! * extended-source option:                Fortran Dialect Options.
! * extensions, file name:                 Overall Options.
! * extensions, from Fortran 90:           Fortran 90 Features.
! * extensions, more:                      More Extensions.
! * extensions, VXT:                       VXT Fortran.
! * external names:                        Mangling of Names.
! * extra warnings:                        Warning Options.
! * f2c:                                   Increasing Precision/Range.
! * f2c compatibility <1>:                 Avoid f2c Compatibility.
! * f2c compatibility <2>:                 Block Data and Libraries.
! * f2c compatibility <3>:                 Debugging and Interfacing.
! * f2c compatibility <4>:                 Code Gen Options.
! * f2c compatibility <5>:                 Shorthand Options.
! * f2c compatibility:                     Overall Options.
! * f2c intrinsics:                        Fortran Dialect Options.
! * f2c intrinsics group:                  Intrinsic Groups.
! * f77 compatibility:                     Shorthand Options.
! * f77 support:                           Backslash in Constants.
! * f771, program:                         What is GNU Fortran?.
! * f90 intrinsics group:                  Intrinsic Groups.
! * fatal signal:                          Bug Criteria.
! * FDate intrinsic <1>:                   FDate Intrinsic (function).
! * FDate intrinsic:                       FDate Intrinsic (subroutine).
! * FDL, GNU Free Documentation License:   GNU Free Documentation License.
! * features, language:                    Direction of Language Development.
! * features, ugly <1>:                    Distensions.
! * features, ugly:                        Shorthand Options.
! * FFE <1>:                               Front End.
! * FFE:                                   What is GNU Fortran?.
! * fflush():                              Output Assumed To Flush.
! * FGet intrinsic <1>:                    FGet Intrinsic (function).
! * FGet intrinsic:                        FGet Intrinsic (subroutine).
! * FGetC intrinsic <1>:                   FGetC Intrinsic (function).
! * FGetC intrinsic:                       FGetC Intrinsic (subroutine).
! * file format not recognized:            What is GNU Fortran?.
! * file formats:                          Portable Unformatted Files.
! * file name extension:                   Overall Options.
! * file name suffix:                      Overall Options.
! * file type:                             Overall Options.
! * file, source <1>:                      Source Form.
! * file, source <2>:                      Lines.
! * file, source:                          What is GNU Fortran?.
! * files, executable:                     What is GNU Fortran?.
! * fixed form <1>:                        Source Form.
! * fixed form <2>:                        Lines.
! * fixed form:                            Fortran Dialect Options.
! * Float intrinsic:                       Float Intrinsic.
! * FloatI intrinsic:                      FloatI Intrinsic.
! * floating-point errors:                 Floating-point Errors.
! * floating-point, errors:                Inconsistent Calling Sequences.
! * floating-point, exceptions:            Floating-point Exception Handling.
! * floating-point, precision <1>:         Floating-point precision.
! * floating-point, precision:             Optimize Options.
! * FloatJ intrinsic:                      FloatJ Intrinsic.
! * Floor intrinsic:                       Floor Intrinsic.
! * Flush intrinsic:                       Flush Intrinsic.
! * flushing output:                       Output Assumed To Flush.
! * FNum intrinsic:                        FNum Intrinsic.
! * FORM='PRINT':                          OPEN CLOSE and INQUIRE Keywords.
! * FORMAT descriptors <1>:                Fortran 90 Features.
! * FORMAT descriptors:                    I/O.
! * FORMAT statement <1>:                  Q Edit Descriptor.
! * FORMAT statement:                      Expressions in FORMAT Statements.
! * FORTRAN 66 <1>:                        Fortran Dialect Options.
! * FORTRAN 66:                            Shorthand Options.
! * FORTRAN 77 compatibility:              Standard Support.
! * Fortran 90:                            Fortran 90 Features.
! * Fortran 90, compatibility:             Fortran 90.
! * Fortran 90, features:                  Fortran Dialect Options.
! * Fortran 90, intrinsics:                Fortran Dialect Options.
! * Fortran 90, support:                   Fortran 90 Support.
! * Fortran preprocessor:                  Overall Options.
! * forward references:                    GLOBALS.
! * FPE handling:                          Floating-point Exception Handling.
! * FPut intrinsic <1>:                    FPut Intrinsic (function).
! * FPut intrinsic:                        FPut Intrinsic (subroutine).
! * FPutC intrinsic <1>:                   FPutC Intrinsic (function).
! * FPutC intrinsic:                       FPutC Intrinsic (subroutine).
! * Fraction intrinsic:                    Fraction Intrinsic.
! * free form <1>:                         Source Form.
! * free form <2>:                         Lines.
! * free form:                             Fortran Dialect Options.
! * front end, g77 <1>:                    Front End.
! * front end, g77:                        What is GNU Fortran?.
! * FSeek intrinsic:                       FSeek Intrinsic.
! * FSF, funding the:                      Funding GNU Fortran.
! * FStat intrinsic <1>:                   FStat Intrinsic (function).
! * FStat intrinsic:                       FStat Intrinsic (subroutine).
! * FTell intrinsic <1>:                   FTell Intrinsic (function).
! * FTell intrinsic:                       FTell Intrinsic (subroutine).
! * function references, in adjustable array bounds: Array Bounds Expressions.
! * FUNCTION statement <1>:                Functions.
! * FUNCTION statement:                    Procedures.
! * functions:                             Functions.
! * functions, mistyped:                   Not My Type.
! * funding improvements:                  Funding GNU Fortran.
! * funding the FSF:                       Funding GNU Fortran.
! * g77 options, --driver <1>:             Changes.
! * g77 options, --driver:                 News.
! * g77 options, -v:                       G77 and GCC.
! * g77, command <1>:                      G77 and GCC.
! * g77, command:                          What is GNU Fortran?.
! * g77, components of:                    What is GNU Fortran?.
! * g77, front end <1>:                    Front End.
! * g77, front end:                        What is GNU Fortran?.
! * g77, modifying:                        Overall Options.
! * G77_date_y2kbuggy_0:                   Year 2000 (Y2K) Problems.
! * G77_vxtidate_y2kbuggy_0:               Year 2000 (Y2K) Problems.
! * GBE <1>:                               Philosophy of Code Generation.
! * GBE:                                   What is GNU Fortran?.
! * GBEL:                                  Philosophy of Code Generation.
! * gcc, back end <1>:                     Philosophy of Code Generation.
! * gcc, back end:                         What is GNU Fortran?.
! * gcc, command <1>:                      G77 and GCC.
! * gcc, command:                          What is GNU Fortran?.
! * gcc, command as driver:                What is GNU Fortran?.
! * gcc, not recognizing Fortran source:   What is GNU Fortran?.
! * gdb, command:                          What is GNU Fortran?.
! * gdb, support:                          Debugger Problems.
! * generic intrinsics:                    Generics and Specifics.
! * GError intrinsic:                      GError Intrinsic.
! * GetArg intrinsic <1>:                  Main Program Unit.
! * GetArg intrinsic:                      GetArg Intrinsic.
! * GetCWD intrinsic <1>:                  GetCWD Intrinsic (function).
! * GetCWD intrinsic:                      GetCWD Intrinsic (subroutine).
! * GetEnv intrinsic:                      GetEnv Intrinsic.
! * GetGId intrinsic:                      GetGId Intrinsic.
! * GetLog intrinsic:                      GetLog Intrinsic.
! * GetPId intrinsic:                      GetPId Intrinsic.
! * getting started:                       Getting Started.
! * GetUId intrinsic:                      GetUId Intrinsic.
! * global names, warning <1>:             Code Gen Options.
! * global names, warning:                 Warning Options.
! * GMTime intrinsic:                      GMTime Intrinsic.
! * GNU Back End (GBE) <1>:                Philosophy of Code Generation.
! * GNU Back End (GBE):                    What is GNU Fortran?.
! * GNU Back End Language (GBEL):          Philosophy of Code Generation.
! * GNU Fortran command options:           Invoking G77.
! * GNU Fortran Front End (FFE) <1>:       Front End.
! * GNU Fortran Front End (FFE):           What is GNU Fortran?.
! * gnu intrinsics group:                  Intrinsic Groups.
! * GOTO statement:                        Assigned Statement Labels.
! * groups of intrinsics:                  Intrinsic Groups.
! * hardware errors:                       Signal 11 and Friends.
! * hash mark:                             Character Set.
! * HDF:                                   Portable Unformatted Files.
! * hidden intrinsics:                     Intrinsic Groups.
! * Hollerith constants <1>:               Character and Hollerith Constants.
! * Hollerith constants <2>:               Ugly Conversion of Initializers.
! * Hollerith constants <3>:               Ugly Implicit Argument Conversion.
! * Hollerith constants:                   Fortran Dialect Options.
! * horizontal tab:                        Tabs.
! * HostNm intrinsic <1>:                  HostNm Intrinsic (function).
! * HostNm intrinsic:                      HostNm Intrinsic (subroutine).
! * Huge intrinsic:                        Huge Intrinsic.
! * I/O, errors:                           Run-time Library Errors.
! * I/O, flushing:                         Output Assumed To Flush.
! * IAbs intrinsic:                        IAbs Intrinsic.
! * IAChar intrinsic:                      IAChar Intrinsic.
! * IAnd intrinsic:                        IAnd Intrinsic.
! * IArgC intrinsic <1>:                   Main Program Unit.
! * IArgC intrinsic:                       IArgC Intrinsic.
! * IBClr intrinsic:                       IBClr Intrinsic.
! * IBits intrinsic:                       IBits Intrinsic.
! * IBSet intrinsic:                       IBSet Intrinsic.
! * IChar intrinsic:                       IChar Intrinsic.
! * IDate intrinsic <1>:                   IDate Intrinsic (VXT).
! * IDate intrinsic:                       IDate Intrinsic (UNIX).
! * IDiM intrinsic:                        IDiM Intrinsic.
! * IDInt intrinsic:                       IDInt Intrinsic.
! * IDNInt intrinsic:                      IDNInt Intrinsic.
! * IEEE 754 conformance <1>:              Floating-point precision.
! * IEEE 754 conformance:                  Optimize Options.
! * IEOr intrinsic:                        IEOr Intrinsic.
! * IErrNo intrinsic:                      IErrNo Intrinsic.
! * IFix intrinsic:                        IFix Intrinsic.
! * IIAbs intrinsic:                       IIAbs Intrinsic.
! * IIAnd intrinsic:                       IIAnd Intrinsic.
! * IIBClr intrinsic:                      IIBClr Intrinsic.
! * IIBits intrinsic:                      IIBits Intrinsic.
! * IIBSet intrinsic:                      IIBSet Intrinsic.
! * IIDiM intrinsic:                       IIDiM Intrinsic.
! * IIDInt intrinsic:                      IIDInt Intrinsic.
! * IIDNnt intrinsic:                      IIDNnt Intrinsic.
! * IIEOr intrinsic:                       IIEOr Intrinsic.
! * IIFix intrinsic:                       IIFix Intrinsic.
! * IInt intrinsic:                        IInt Intrinsic.
! * IIOr intrinsic:                        IIOr Intrinsic.
! * IIQint intrinsic:                      IIQint Intrinsic.
! * IIQNnt intrinsic:                      IIQNnt Intrinsic.
! * IIShftC intrinsic:                     IIShftC Intrinsic.
! * IISign intrinsic:                      IISign Intrinsic.
! * illegal unit number:                   Large File Unit Numbers.
! * Imag intrinsic:                        Imag Intrinsic.
! * imaginary part <1>:                    Complex Variables.
! * imaginary part:                        Ugly Complex Part Extraction.
! * ImagPart intrinsic:                    ImagPart Intrinsic.
! * IMax0 intrinsic:                       IMax0 Intrinsic.
! * IMax1 intrinsic:                       IMax1 Intrinsic.
! * IMin0 intrinsic:                       IMin0 Intrinsic.
! * IMin1 intrinsic:                       IMin1 Intrinsic.
! * IMod intrinsic:                        IMod Intrinsic.
! * IMPLICIT CHARACTER*(*) statement:      Limitation on Implicit Declarations.
! * implicit declaration, warning:         Warning Options.
! * IMPLICIT NONE, similar effect:         Warning Options.
! * implicit typing:                       Not My Type.
! * improvements, funding:                 Funding GNU Fortran.
! * in-line code <1>:                      GLOBALS.
! * in-line code <2>:                      Code Gen Options.
! * in-line code <3>:                      Optimize Options.
! * in-line code:                          What is GNU Fortran?.
! * INCLUDE directive <1>:                 Bug Reporting.
! * INCLUDE directive <2>:                 INCLUDE.
! * INCLUDE directive <3>:                 Directory Options.
! * INCLUDE directive:                     Preprocessor Options.
! * included files:                        Bug Reporting.
! * inclusion, directory search paths for: Directory Options.
! * inconsistent floating-point results:   Floating-point Errors.
! * incorrect diagnostics:                 What is GNU Fortran?.
! * incorrect error messages:              What is GNU Fortran?.
! * incorrect use of language:             What is GNU Fortran?.
! * increasing maximum unit number:        Large File Unit Numbers.
! * increasing precision:                  Increasing Precision/Range.
! * increasing range:                      Increasing Precision/Range.
! * Index intrinsic:                       Index Intrinsic.
! * indexed (iterative) DO:                Optimize Options.
! * infinite spaces printed:               Strange Behavior at Run Time.
! * INInt intrinsic:                       INInt Intrinsic.
! * initialization, bug:                   Known Bugs.
! * initialization, of local variables:    Code Gen Options.
! * initialization, run-time:              Startup Code.
! * initialization, statement placement:   Initializing Before Specifying.
! * INot intrinsic:                        INot Intrinsic.
! * INQUIRE statement:                     OPEN CLOSE and INQUIRE Keywords.
! * installation trouble:                  Trouble.
! * Int intrinsic:                         Int Intrinsic.
! * Int2 intrinsic:                        Int2 Intrinsic.
! * Int8 intrinsic:                        Int8 Intrinsic.
! * integer constants:                     Known Bugs.
! * INTEGER(KIND=1) type:                  Compiler Types.
! * INTEGER(KIND=2) type:                  Compiler Types.
! * INTEGER(KIND=3) type:                  Compiler Types.
! * INTEGER(KIND=6) type:                  Compiler Types.
! * INTEGER*2 support:                     Popular Non-standard Types.
! * INTEGER*8 support:                     Full Support for Compiler Types.
! * Intel x86:                             News.
! * interfacing:                           Debugging and Interfacing.
! * internal consistency checks:           Overall Options.
! * intrinsics, Abort:                     Abort Intrinsic.
! * intrinsics, Abs:                       Abs Intrinsic.
! * intrinsics, Access:                    Access Intrinsic.
! * intrinsics, AChar:                     AChar Intrinsic.
! * intrinsics, ACos:                      ACos Intrinsic.
! * intrinsics, ACosD:                     ACosD Intrinsic.
! * intrinsics, AdjustL:                   AdjustL Intrinsic.
! * intrinsics, AdjustR:                   AdjustR Intrinsic.
! * intrinsics, AImag <1>:                 AImag Intrinsic.
! * intrinsics, AImag:                     REAL() and AIMAG() of Complex.
! * intrinsics, AIMax0:                    AIMax0 Intrinsic.
! * intrinsics, AIMin0:                    AIMin0 Intrinsic.
! * intrinsics, AInt:                      AInt Intrinsic.
! * intrinsics, AJMax0:                    AJMax0 Intrinsic.
! * intrinsics, AJMin0:                    AJMin0 Intrinsic.
! * intrinsics, Alarm:                     Alarm Intrinsic.
! * intrinsics, All:                       All Intrinsic.
! * intrinsics, Allocated:                 Allocated Intrinsic.
! * intrinsics, ALog:                      ALog Intrinsic.
! * intrinsics, ALog10:                    ALog10 Intrinsic.
! * intrinsics, AMax0:                     AMax0 Intrinsic.
! * intrinsics, AMax1:                     AMax1 Intrinsic.
! * intrinsics, AMin0:                     AMin0 Intrinsic.
! * intrinsics, AMin1:                     AMin1 Intrinsic.
! * intrinsics, AMod:                      AMod Intrinsic.
! * intrinsics, And <1>:                   Bit Operations on Floating-point Data.
! * intrinsics, And:                       And Intrinsic.
! * intrinsics, ANInt:                     ANInt Intrinsic.
! * intrinsics, Any:                       Any Intrinsic.
! * intrinsics, ASin:                      ASin Intrinsic.
! * intrinsics, ASinD:                     ASinD Intrinsic.
! * intrinsics, Associated:                Associated Intrinsic.
! * intrinsics, ATan:                      ATan Intrinsic.
! * intrinsics, ATan2:                     ATan2 Intrinsic.
! * intrinsics, ATan2D:                    ATan2D Intrinsic.
! * intrinsics, ATanD:                     ATanD Intrinsic.
! * intrinsics, badu77:                    Fortran Dialect Options.
! * intrinsics, BesJ0:                     BesJ0 Intrinsic.
! * intrinsics, BesJ1:                     BesJ1 Intrinsic.
! * intrinsics, BesJN:                     BesJN Intrinsic.
! * intrinsics, BesY0:                     BesY0 Intrinsic.
! * intrinsics, BesY1:                     BesY1 Intrinsic.
! * intrinsics, BesYN:                     BesYN Intrinsic.
! * intrinsics, Bit_Size:                  Bit_Size Intrinsic.
! * intrinsics, BITest:                    BITest Intrinsic.
! * intrinsics, BJTest:                    BJTest Intrinsic.
! * intrinsics, BTest:                     BTest Intrinsic.
! * intrinsics, CAbs:                      CAbs Intrinsic.
! * intrinsics, CCos:                      CCos Intrinsic.
! * intrinsics, CDAbs:                     CDAbs Intrinsic.
! * intrinsics, CDCos:                     CDCos Intrinsic.
! * intrinsics, CDExp:                     CDExp Intrinsic.
! * intrinsics, CDLog:                     CDLog Intrinsic.
! * intrinsics, CDSin:                     CDSin Intrinsic.
! * intrinsics, CDSqRt:                    CDSqRt Intrinsic.
! * intrinsics, Ceiling:                   Ceiling Intrinsic.
! * intrinsics, CExp:                      CExp Intrinsic.
! * intrinsics, Char:                      Char Intrinsic.
! * intrinsics, ChDir <1>:                 ChDir Intrinsic (function).
! * intrinsics, ChDir:                     ChDir Intrinsic (subroutine).
! * intrinsics, ChMod <1>:                 ChMod Intrinsic (function).
! * intrinsics, ChMod:                     ChMod Intrinsic (subroutine).
! * intrinsics, CLog:                      CLog Intrinsic.
! * intrinsics, Cmplx <1>:                 Cmplx Intrinsic.
! * intrinsics, Cmplx:                     CMPLX() of DOUBLE PRECISION.
! * intrinsics, Complex:                   Complex Intrinsic.
! * intrinsics, COMPLEX:                   Fortran Dialect Options.
! * intrinsics, Conjg:                     Conjg Intrinsic.
! * intrinsics, context-sensitive:         Context-Sensitive Intrinsicness.
! * intrinsics, Cos:                       Cos Intrinsic.
! * intrinsics, CosD:                      CosD Intrinsic.
! * intrinsics, CosH:                      CosH Intrinsic.
! * intrinsics, Count:                     Count Intrinsic.
! * intrinsics, CPU_Time:                  CPU_Time Intrinsic.
! * intrinsics, CShift:                    CShift Intrinsic.
! * intrinsics, CSin:                      CSin Intrinsic.
! * intrinsics, CSqRt:                     CSqRt Intrinsic.
! * intrinsics, CTime <1>:                 CTime Intrinsic (function).
! * intrinsics, CTime:                     CTime Intrinsic (subroutine).
! * intrinsics, DAbs:                      DAbs Intrinsic.
! * intrinsics, DACos:                     DACos Intrinsic.
! * intrinsics, DACosD:                    DACosD Intrinsic.
! * intrinsics, DASin:                     DASin Intrinsic.
! * intrinsics, DASinD:                    DASinD Intrinsic.
! * intrinsics, DATan:                     DATan Intrinsic.
! * intrinsics, DATan2:                    DATan2 Intrinsic.
! * intrinsics, DATan2D:                   DATan2D Intrinsic.
! * intrinsics, DATanD:                    DATanD Intrinsic.
! * intrinsics, Date:                      Date Intrinsic.
! * intrinsics, Date_and_Time:             Date_and_Time Intrinsic.
! * intrinsics, DbesJ0:                    DbesJ0 Intrinsic.
! * intrinsics, DbesJ1:                    DbesJ1 Intrinsic.
! * intrinsics, DbesJN:                    DbesJN Intrinsic.
! * intrinsics, DbesY0:                    DbesY0 Intrinsic.
! * intrinsics, DbesY1:                    DbesY1 Intrinsic.
! * intrinsics, DbesYN:                    DbesYN Intrinsic.
! * intrinsics, Dble:                      Dble Intrinsic.
! * intrinsics, DbleQ:                     DbleQ Intrinsic.
! * intrinsics, DCmplx:                    DCmplx Intrinsic.
! * intrinsics, DConjg:                    DConjg Intrinsic.
! * intrinsics, DCos:                      DCos Intrinsic.
! * intrinsics, DCosD:                     DCosD Intrinsic.
! * intrinsics, DCosH:                     DCosH Intrinsic.
! * intrinsics, DDiM:                      DDiM Intrinsic.
! * intrinsics, deleted:                   Intrinsic Groups.
! * intrinsics, DErF:                      DErF Intrinsic.
! * intrinsics, DErFC:                     DErFC Intrinsic.
! * intrinsics, DExp:                      DExp Intrinsic.
! * intrinsics, DFloat:                    DFloat Intrinsic.
! * intrinsics, DFlotI:                    DFlotI Intrinsic.
! * intrinsics, DFlotJ:                    DFlotJ Intrinsic.
! * intrinsics, Digits:                    Digits Intrinsic.
! * intrinsics, DiM:                       DiM Intrinsic.
! * intrinsics, DImag:                     DImag Intrinsic.
! * intrinsics, DInt:                      DInt Intrinsic.
! * intrinsics, disabled:                  Intrinsic Groups.
! * intrinsics, DLog:                      DLog Intrinsic.
! * intrinsics, DLog10:                    DLog10 Intrinsic.
! * intrinsics, DMax1:                     DMax1 Intrinsic.
! * intrinsics, DMin1:                     DMin1 Intrinsic.
! * intrinsics, DMod:                      DMod Intrinsic.
! * intrinsics, DNInt:                     DNInt Intrinsic.
! * intrinsics, Dot_Product:               Dot_Product Intrinsic.
! * intrinsics, DProd:                     DProd Intrinsic.
! * intrinsics, DReal:                     DReal Intrinsic.
! * intrinsics, DSign:                     DSign Intrinsic.
! * intrinsics, DSin:                      DSin Intrinsic.
! * intrinsics, DSinD:                     DSinD Intrinsic.
! * intrinsics, DSinH:                     DSinH Intrinsic.
! * intrinsics, DSqRt:                     DSqRt Intrinsic.
! * intrinsics, DTan:                      DTan Intrinsic.
! * intrinsics, DTanD:                     DTanD Intrinsic.
! * intrinsics, DTanH:                     DTanH Intrinsic.
! * intrinsics, DTime <1>:                 DTime Intrinsic (function).
! * intrinsics, DTime:                     DTime Intrinsic (subroutine).
! * intrinsics, enabled:                   Intrinsic Groups.
! * intrinsics, EOShift:                   EOShift Intrinsic.
! * intrinsics, Epsilon:                   Epsilon Intrinsic.
! * intrinsics, ErF:                       ErF Intrinsic.
! * intrinsics, ErFC:                      ErFC Intrinsic.
! * intrinsics, ETime <1>:                 ETime Intrinsic (function).
! * intrinsics, ETime:                     ETime Intrinsic (subroutine).
! * intrinsics, Exit:                      Exit Intrinsic.
! * intrinsics, Exp:                       Exp Intrinsic.
! * intrinsics, Exponent:                  Exponent Intrinsic.
! * intrinsics, f2c:                       Fortran Dialect Options.
! * intrinsics, FDate <1>:                 FDate Intrinsic (function).
! * intrinsics, FDate:                     FDate Intrinsic (subroutine).
! * intrinsics, FGet <1>:                  FGet Intrinsic (function).
! * intrinsics, FGet:                      FGet Intrinsic (subroutine).
! * intrinsics, FGetC <1>:                 FGetC Intrinsic (function).
! * intrinsics, FGetC:                     FGetC Intrinsic (subroutine).
! * intrinsics, Float:                     Float Intrinsic.
! * intrinsics, FloatI:                    FloatI Intrinsic.
! * intrinsics, FloatJ:                    FloatJ Intrinsic.
! * intrinsics, Floor:                     Floor Intrinsic.
! * intrinsics, Flush:                     Flush Intrinsic.
! * intrinsics, FNum:                      FNum Intrinsic.
! * intrinsics, Fortran 90:                Fortran Dialect Options.
! * intrinsics, FPut <1>:                  FPut Intrinsic (function).
! * intrinsics, FPut:                      FPut Intrinsic (subroutine).
! * intrinsics, FPutC <1>:                 FPutC Intrinsic (function).
! * intrinsics, FPutC:                     FPutC Intrinsic (subroutine).
! * intrinsics, Fraction:                  Fraction Intrinsic.
! * intrinsics, FSeek:                     FSeek Intrinsic.
! * intrinsics, FStat <1>:                 FStat Intrinsic (function).
! * intrinsics, FStat:                     FStat Intrinsic (subroutine).
! * intrinsics, FTell <1>:                 FTell Intrinsic (function).
! * intrinsics, FTell:                     FTell Intrinsic (subroutine).
! * intrinsics, generic:                   Generics and Specifics.
! * intrinsics, GError:                    GError Intrinsic.
! * intrinsics, GetArg <1>:                Main Program Unit.
! * intrinsics, GetArg:                    GetArg Intrinsic.
! * intrinsics, GetCWD <1>:                GetCWD Intrinsic (function).
! * intrinsics, GetCWD:                    GetCWD Intrinsic (subroutine).
! * intrinsics, GetEnv:                    GetEnv Intrinsic.
! * intrinsics, GetGId:                    GetGId Intrinsic.
! * intrinsics, GetLog:                    GetLog Intrinsic.
! * intrinsics, GetPId:                    GetPId Intrinsic.
! * intrinsics, GetUId:                    GetUId Intrinsic.
! * intrinsics, GMTime:                    GMTime Intrinsic.
! * intrinsics, groups:                    Intrinsic Groups.
! * intrinsics, groups of:                 Intrinsic Groups.
! * intrinsics, hidden:                    Intrinsic Groups.
! * intrinsics, HostNm <1>:                HostNm Intrinsic (function).
! * intrinsics, HostNm:                    HostNm Intrinsic (subroutine).
! * intrinsics, Huge:                      Huge Intrinsic.
! * intrinsics, IAbs:                      IAbs Intrinsic.
! * intrinsics, IAChar:                    IAChar Intrinsic.
! * intrinsics, IAnd:                      IAnd Intrinsic.
! * intrinsics, IArgC <1>:                 Main Program Unit.
! * intrinsics, IArgC:                     IArgC Intrinsic.
! * intrinsics, IBClr:                     IBClr Intrinsic.
! * intrinsics, IBits:                     IBits Intrinsic.
! * intrinsics, IBSet:                     IBSet Intrinsic.
! * intrinsics, IChar:                     IChar Intrinsic.
! * intrinsics, IDate <1>:                 IDate Intrinsic (VXT).
! * intrinsics, IDate:                     IDate Intrinsic (UNIX).
! * intrinsics, IDiM:                      IDiM Intrinsic.
! * intrinsics, IDInt:                     IDInt Intrinsic.
! * intrinsics, IDNInt:                    IDNInt Intrinsic.
! * intrinsics, IEOr:                      IEOr Intrinsic.
! * intrinsics, IErrNo:                    IErrNo Intrinsic.
! * intrinsics, IFix:                      IFix Intrinsic.
! * intrinsics, IIAbs:                     IIAbs Intrinsic.
! * intrinsics, IIAnd:                     IIAnd Intrinsic.
! * intrinsics, IIBClr:                    IIBClr Intrinsic.
! * intrinsics, IIBits:                    IIBits Intrinsic.
! * intrinsics, IIBSet:                    IIBSet Intrinsic.
! * intrinsics, IIDiM:                     IIDiM Intrinsic.
! * intrinsics, IIDInt:                    IIDInt Intrinsic.
! * intrinsics, IIDNnt:                    IIDNnt Intrinsic.
! * intrinsics, IIEOr:                     IIEOr Intrinsic.
! * intrinsics, IIFix:                     IIFix Intrinsic.
! * intrinsics, IInt:                      IInt Intrinsic.
! * intrinsics, IIOr:                      IIOr Intrinsic.
! * intrinsics, IIQint:                    IIQint Intrinsic.
! * intrinsics, IIQNnt:                    IIQNnt Intrinsic.
! * intrinsics, IIShftC:                   IIShftC Intrinsic.
! * intrinsics, IISign:                    IISign Intrinsic.
! * intrinsics, Imag:                      Imag Intrinsic.
! * intrinsics, ImagPart:                  ImagPart Intrinsic.
! * intrinsics, IMax0:                     IMax0 Intrinsic.
! * intrinsics, IMax1:                     IMax1 Intrinsic.
! * intrinsics, IMin0:                     IMin0 Intrinsic.
! * intrinsics, IMin1:                     IMin1 Intrinsic.
! * intrinsics, IMod:                      IMod Intrinsic.
! * intrinsics, Index:                     Index Intrinsic.
! * intrinsics, INInt:                     INInt Intrinsic.
! * intrinsics, INot:                      INot Intrinsic.
! * intrinsics, Int:                       Int Intrinsic.
! * intrinsics, Int2:                      Int2 Intrinsic.
! * intrinsics, Int8:                      Int8 Intrinsic.
! * intrinsics, IOr:                       IOr Intrinsic.
! * intrinsics, IRand:                     IRand Intrinsic.
! * intrinsics, IsaTty:                    IsaTty Intrinsic.
! * intrinsics, IShft:                     IShft Intrinsic.
! * intrinsics, IShftC:                    IShftC Intrinsic.
! * intrinsics, ISign:                     ISign Intrinsic.
! * intrinsics, ITime:                     ITime Intrinsic.
! * intrinsics, IZExt:                     IZExt Intrinsic.
! * intrinsics, JIAbs:                     JIAbs Intrinsic.
! * intrinsics, JIAnd:                     JIAnd Intrinsic.
! * intrinsics, JIBClr:                    JIBClr Intrinsic.
! * intrinsics, JIBits:                    JIBits Intrinsic.
! * intrinsics, JIBSet:                    JIBSet Intrinsic.
! * intrinsics, JIDiM:                     JIDiM Intrinsic.
! * intrinsics, JIDInt:                    JIDInt Intrinsic.
! * intrinsics, JIDNnt:                    JIDNnt Intrinsic.
! * intrinsics, JIEOr:                     JIEOr Intrinsic.
! * intrinsics, JIFix:                     JIFix Intrinsic.
! * intrinsics, JInt:                      JInt Intrinsic.
! * intrinsics, JIOr:                      JIOr Intrinsic.
! * intrinsics, JIQint:                    JIQint Intrinsic.
! * intrinsics, JIQNnt:                    JIQNnt Intrinsic.
! * intrinsics, JIShft:                    JIShft Intrinsic.
! * intrinsics, JIShftC:                   JIShftC Intrinsic.
! * intrinsics, JISign:                    JISign Intrinsic.
! * intrinsics, JMax0:                     JMax0 Intrinsic.
! * intrinsics, JMax1:                     JMax1 Intrinsic.
! * intrinsics, JMin0:                     JMin0 Intrinsic.
! * intrinsics, JMin1:                     JMin1 Intrinsic.
! * intrinsics, JMod:                      JMod Intrinsic.
! * intrinsics, JNInt:                     JNInt Intrinsic.
! * intrinsics, JNot:                      JNot Intrinsic.
! * intrinsics, JZExt:                     JZExt Intrinsic.
! * intrinsics, Kill <1>:                  Kill Intrinsic (function).
! * intrinsics, Kill:                      Kill Intrinsic (subroutine).
! * intrinsics, Kind:                      Kind Intrinsic.
! * intrinsics, LBound:                    LBound Intrinsic.
! * intrinsics, Len:                       Len Intrinsic.
! * intrinsics, Len_Trim:                  Len_Trim Intrinsic.
! * intrinsics, LGe:                       LGe Intrinsic.
! * intrinsics, LGt:                       LGt Intrinsic.
! * intrinsics, Link <1>:                  Link Intrinsic (function).
! * intrinsics, Link:                      Link Intrinsic (subroutine).
! * intrinsics, LLe:                       LLe Intrinsic.
! * intrinsics, LLt:                       LLt Intrinsic.
! * intrinsics, LnBlnk:                    LnBlnk Intrinsic.
! * intrinsics, Loc:                       Loc Intrinsic.
! * intrinsics, Log:                       Log Intrinsic.
! * intrinsics, Log10:                     Log10 Intrinsic.
! * intrinsics, Logical:                   Logical Intrinsic.
! * intrinsics, Long:                      Long Intrinsic.
! * intrinsics, LShift:                    LShift Intrinsic.
! * intrinsics, LStat <1>:                 LStat Intrinsic (function).
! * intrinsics, LStat:                     LStat Intrinsic (subroutine).
! * intrinsics, LTime:                     LTime Intrinsic.
! * intrinsics, MatMul:                    MatMul Intrinsic.
! * intrinsics, Max:                       Max Intrinsic.
! * intrinsics, Max0:                      Max0 Intrinsic.
! * intrinsics, Max1:                      Max1 Intrinsic.
! * intrinsics, MaxExponent:               MaxExponent Intrinsic.
! * intrinsics, MaxLoc:                    MaxLoc Intrinsic.
! * intrinsics, MaxVal:                    MaxVal Intrinsic.
! * intrinsics, MClock:                    MClock Intrinsic.
! * intrinsics, MClock8:                   MClock8 Intrinsic.
! * intrinsics, Merge:                     Merge Intrinsic.
! * intrinsics, MIL-STD 1753:              Fortran Dialect Options.
! * intrinsics, Min:                       Min Intrinsic.
! * intrinsics, Min0:                      Min0 Intrinsic.
! * intrinsics, Min1:                      Min1 Intrinsic.
! * intrinsics, MinExponent:               MinExponent Intrinsic.
! * intrinsics, MinLoc:                    MinLoc Intrinsic.
! * intrinsics, MinVal:                    MinVal Intrinsic.
! * intrinsics, Mod:                       Mod Intrinsic.
! * intrinsics, Modulo:                    Modulo Intrinsic.
! * intrinsics, MvBits:                    MvBits Intrinsic.
! * intrinsics, Nearest:                   Nearest Intrinsic.
! * intrinsics, NInt:                      NInt Intrinsic.
! * intrinsics, Not:                       Not Intrinsic.
! * intrinsics, Or <1>:                    Bit Operations on Floating-point Data.
! * intrinsics, Or:                        Or Intrinsic.
! * intrinsics, others:                    Other Intrinsics.
! * intrinsics, Pack:                      Pack Intrinsic.
! * intrinsics, PError:                    PError Intrinsic.
! * intrinsics, Precision:                 Precision Intrinsic.
! * intrinsics, Present:                   Present Intrinsic.
! * intrinsics, Product:                   Product Intrinsic.
! * intrinsics, QAbs:                      QAbs Intrinsic.
! * intrinsics, QACos:                     QACos Intrinsic.
! * intrinsics, QACosD:                    QACosD Intrinsic.
! * intrinsics, QASin:                     QASin Intrinsic.
! * intrinsics, QASinD:                    QASinD Intrinsic.
! * intrinsics, QATan:                     QATan Intrinsic.
! * intrinsics, QATan2:                    QATan2 Intrinsic.
! * intrinsics, QATan2D:                   QATan2D Intrinsic.
! * intrinsics, QATanD:                    QATanD Intrinsic.
! * intrinsics, QCos:                      QCos Intrinsic.
! * intrinsics, QCosD:                     QCosD Intrinsic.
! * intrinsics, QCosH:                     QCosH Intrinsic.
! * intrinsics, QDiM:                      QDiM Intrinsic.
! * intrinsics, QExp:                      QExp Intrinsic.
! * intrinsics, QExt:                      QExt Intrinsic.
! * intrinsics, QExtD:                     QExtD Intrinsic.
! * intrinsics, QFloat:                    QFloat Intrinsic.
! * intrinsics, QInt:                      QInt Intrinsic.
! * intrinsics, QLog:                      QLog Intrinsic.
! * intrinsics, QLog10:                    QLog10 Intrinsic.
! * intrinsics, QMax1:                     QMax1 Intrinsic.
! * intrinsics, QMin1:                     QMin1 Intrinsic.
! * intrinsics, QMod:                      QMod Intrinsic.
! * intrinsics, QNInt:                     QNInt Intrinsic.
! * intrinsics, QSin:                      QSin Intrinsic.
! * intrinsics, QSinD:                     QSinD Intrinsic.
! * intrinsics, QSinH:                     QSinH Intrinsic.
! * intrinsics, QSqRt:                     QSqRt Intrinsic.
! * intrinsics, QTan:                      QTan Intrinsic.
! * intrinsics, QTanD:                     QTanD Intrinsic.
! * intrinsics, QTanH:                     QTanH Intrinsic.
! * intrinsics, Radix:                     Radix Intrinsic.
! * intrinsics, Rand:                      Rand Intrinsic.
! * intrinsics, Random_Number:             Random_Number Intrinsic.
! * intrinsics, Random_Seed:               Random_Seed Intrinsic.
! * intrinsics, Range:                     Range Intrinsic.
! * intrinsics, Real <1>:                  Real Intrinsic.
! * intrinsics, Real:                      REAL() and AIMAG() of Complex.
! * intrinsics, RealPart:                  RealPart Intrinsic.
! * intrinsics, Rename <1>:                Rename Intrinsic (function).
! * intrinsics, Rename:                    Rename Intrinsic (subroutine).
! * intrinsics, Repeat:                    Repeat Intrinsic.
! * intrinsics, Reshape:                   Reshape Intrinsic.
! * intrinsics, RRSpacing:                 RRSpacing Intrinsic.
! * intrinsics, RShift:                    RShift Intrinsic.
! * intrinsics, Scale:                     Scale Intrinsic.
! * intrinsics, Scan:                      Scan Intrinsic.
! * intrinsics, Secnds:                    Secnds Intrinsic.
! * intrinsics, Second <1>:                Second Intrinsic (subroutine).
! * intrinsics, Second:                    Second Intrinsic (function).
! * intrinsics, Selected_Int_Kind:         Selected_Int_Kind Intrinsic.
! * intrinsics, Selected_Real_Kind:        Selected_Real_Kind Intrinsic.
! * intrinsics, Set_Exponent:              Set_Exponent Intrinsic.
! * intrinsics, Shape:                     Shape Intrinsic.
! * intrinsics, Shift:                     Bit Operations on Floating-point Data.
! * intrinsics, Short:                     Short Intrinsic.
! * intrinsics, Sign:                      Sign Intrinsic.
! * intrinsics, Signal <1>:                Signal Intrinsic (function).
! * intrinsics, Signal:                    Signal Intrinsic (subroutine).
! * intrinsics, Sin:                       Sin Intrinsic.
! * intrinsics, SinD:                      SinD Intrinsic.
! * intrinsics, SinH:                      SinH Intrinsic.
! * intrinsics, Sleep:                     Sleep Intrinsic.
! * intrinsics, Sngl:                      Sngl Intrinsic.
! * intrinsics, SnglQ:                     SnglQ Intrinsic.
! * intrinsics, Spacing:                   Spacing Intrinsic.
! * intrinsics, Spread:                    Spread Intrinsic.
! * intrinsics, SqRt:                      SqRt Intrinsic.
! * intrinsics, SRand:                     SRand Intrinsic.
! * intrinsics, Stat <1>:                  Stat Intrinsic (function).
! * intrinsics, Stat:                      Stat Intrinsic (subroutine).
! * intrinsics, Sum:                       Sum Intrinsic.
! * intrinsics, SymLnk <1>:                SymLnk Intrinsic (function).
! * intrinsics, SymLnk:                    SymLnk Intrinsic (subroutine).
! * intrinsics, System <1>:                System Intrinsic (function).
! * intrinsics, System:                    System Intrinsic (subroutine).
! * intrinsics, System_Clock:              System_Clock Intrinsic.
! * intrinsics, table of:                  Table of Intrinsic Functions.
! * intrinsics, Tan:                       Tan Intrinsic.
! * intrinsics, TanD:                      TanD Intrinsic.
! * intrinsics, TanH:                      TanH Intrinsic.
! * intrinsics, Time <1>:                  Time Intrinsic (VXT).
! * intrinsics, Time:                      Time Intrinsic (UNIX).
! * intrinsics, Time8:                     Time8 Intrinsic.
! * intrinsics, Tiny:                      Tiny Intrinsic.
! * intrinsics, Transfer:                  Transfer Intrinsic.
! * intrinsics, Transpose:                 Transpose Intrinsic.
! * intrinsics, Trim:                      Trim Intrinsic.
! * intrinsics, TtyNam <1>:                TtyNam Intrinsic (function).
! * intrinsics, TtyNam:                    TtyNam Intrinsic (subroutine).
! * intrinsics, UBound:                    UBound Intrinsic.
! * intrinsics, UMask <1>:                 UMask Intrinsic (function).
! * intrinsics, UMask:                     UMask Intrinsic (subroutine).
! * intrinsics, UNIX:                      Fortran Dialect Options.
! * intrinsics, Unlink <1>:                Unlink Intrinsic (function).
! * intrinsics, Unlink:                    Unlink Intrinsic (subroutine).
! * intrinsics, Unpack:                    Unpack Intrinsic.
! * intrinsics, Verify:                    Verify Intrinsic.
! * intrinsics, VXT:                       Fortran Dialect Options.
! * intrinsics, XOr:                       XOr Intrinsic.
! * intrinsics, ZAbs:                      ZAbs Intrinsic.
! * intrinsics, ZCos:                      ZCos Intrinsic.
! * intrinsics, ZExp:                      ZExp Intrinsic.
! * intrinsics, ZExt:                      ZExt Intrinsic.
! * intrinsics, ZLog:                      ZLog Intrinsic.
! * intrinsics, ZSin:                      ZSin Intrinsic.
! * intrinsics, ZSqRt:                     ZSqRt Intrinsic.
! * Introduction:                          Top.
! * invalid assembly code:                 Bug Criteria.
! * invalid input:                         Bug Criteria.
! * IOr intrinsic:                         IOr Intrinsic.
! * IOSTAT=:                               Run-time Library Errors.
! * IRand intrinsic:                       IRand Intrinsic.
! * IsaTty intrinsic:                      IsaTty Intrinsic.
! * IShft intrinsic:                       IShft Intrinsic.
! * IShftC intrinsic:                      IShftC Intrinsic.
! * ISign intrinsic:                       ISign Intrinsic.
! * iterative DO:                          Optimize Options.
! * ITime intrinsic:                       ITime Intrinsic.
! * ix86 floating-point:                   Floating-point precision.
! * ix86 FPU stack:                        Inconsistent Calling Sequences.
! * IZExt intrinsic:                       IZExt Intrinsic.
! * JCB002 program:                        Generics and Specifics.
! * JCB003 program:                        CMPAMBIG.
! * JIAbs intrinsic:                       JIAbs Intrinsic.
! * JIAnd intrinsic:                       JIAnd Intrinsic.
! * JIBClr intrinsic:                      JIBClr Intrinsic.
! * JIBits intrinsic:                      JIBits Intrinsic.
! * JIBSet intrinsic:                      JIBSet Intrinsic.
! * JIDiM intrinsic:                       JIDiM Intrinsic.
! * JIDInt intrinsic:                      JIDInt Intrinsic.
! * JIDNnt intrinsic:                      JIDNnt Intrinsic.
! * JIEOr intrinsic:                       JIEOr Intrinsic.
! * JIFix intrinsic:                       JIFix Intrinsic.
! * JInt intrinsic:                        JInt Intrinsic.
! * JIOr intrinsic:                        JIOr Intrinsic.
! * JIQint intrinsic:                      JIQint Intrinsic.
! * JIQNnt intrinsic:                      JIQNnt Intrinsic.
! * JIShft intrinsic:                      JIShft Intrinsic.
! * JIShftC intrinsic:                     JIShftC Intrinsic.
! * JISign intrinsic:                      JISign Intrinsic.
! * JMax0 intrinsic:                       JMax0 Intrinsic.
! * JMax1 intrinsic:                       JMax1 Intrinsic.
! * JMin0 intrinsic:                       JMin0 Intrinsic.
! * JMin1 intrinsic:                       JMin1 Intrinsic.
! * JMod intrinsic:                        JMod Intrinsic.
! * JNInt intrinsic:                       JNInt Intrinsic.
! * JNot intrinsic:                        JNot Intrinsic.
! * JZExt intrinsic:                       JZExt Intrinsic.
! * keywords, RECURSIVE:                   RECURSIVE Keyword.
! * Kill intrinsic <1>:                    Kill Intrinsic (function).
! * Kill intrinsic:                        Kill Intrinsic (subroutine).
! * Kind intrinsic:                        Kind Intrinsic.
! * KIND= notation:                        Kind Notation.
! * known causes of trouble:               Trouble.
! * lack of recursion:                     RECURSIVE Keyword.
! * language, dialect options:             Fortran Dialect Options.
! * language, features:                    Direction of Language Development.
! * language, incorrect use of:            What is GNU Fortran?.
! * large aggregate areas:                 Known Bugs.
! * large common blocks:                   Large Common Blocks.
! * layout of COMMON blocks:               Aligned Data.
! * LBound intrinsic:                      LBound Intrinsic.
! * ld command:                            What is GNU Fortran?.
! * ld, can't find _main:                  Cannot Link Fortran Programs.
! * ld, can't find strange names:          Cannot Link Fortran Programs.
! * ld, error linking user code:           Cannot Link Fortran Programs.
! * ld, errors:                            Large Common Blocks.
! * left angle:                            Character Set.
! * left bracket:                          Character Set.
! * legacy code:                           Collected Fortran Wisdom.
! * Len intrinsic:                         Len Intrinsic.
! * Len_Trim intrinsic:                    Len_Trim Intrinsic.
! * length of source lines:                Fortran Dialect Options.
! * letters, lowercase:                    Case Sensitivity.
! * letters, uppercase:                    Case Sensitivity.
! * LGe intrinsic:                         LGe Intrinsic.
! * LGt intrinsic:                         LGt Intrinsic.
! * libc, non-ANSI or non-default:         Strange Behavior at Run Time.
! * libf2c library:                        What is GNU Fortran?.
! * libg2c library:                        What is GNU Fortran?.
! * libraries:                             What is GNU Fortran?.
! * libraries, containing BLOCK DATA:      Block Data and Libraries.
! * libraries, libf2c:                     What is GNU Fortran?.
! * libraries, libg2c:                     What is GNU Fortran?.
! * limits, array dimensions:              Compiler Limits.
! * limits, array size:                    Array Size.
! * limits, compiler:                      Compiler Limits.
! * limits, continuation lines <1>:        Compiler Limits.
! * limits, continuation lines:            Continuation Line.
! * limits, lengths of names <1>:          Compiler Limits.
! * limits, lengths of names:              Syntactic Items.
! * limits, lengths of source lines:       Fortran Dialect Options.
! * limits, multi-dimension arrays:        Array Size.
! * limits, on character-variable length:  Character-variable Length.
! * limits, rank:                          Compiler Limits.
! * limits, run-time library:              Run-time Environment Limits.
! * limits, timings <1>:                   Secnds Intrinsic.
! * limits, timings <2>:                   DTime Intrinsic (function).
! * limits, timings <3>:                   Time8 Intrinsic.
! * limits, timings <4>:                   Time Intrinsic (UNIX).
! * limits, timings <5>:                   System_Clock Intrinsic.
! * limits, timings <6>:                   Second Intrinsic (subroutine).
! * limits, timings <7>:                   Second Intrinsic (function).
! * limits, timings <8>:                   MClock8 Intrinsic.
! * limits, timings <9>:                   MClock Intrinsic.
! * limits, timings <10>:                  ETime Intrinsic (function).
! * limits, timings <11>:                  ETime Intrinsic (subroutine).
! * limits, timings <12>:                  DTime Intrinsic (subroutine).
! * limits, timings:                       CPU_Time Intrinsic.
! * limits, Y10K <1>:                      Time Intrinsic (VXT).
! * limits, Y10K <2>:                      IDate Intrinsic (UNIX).
! * limits, Y10K <3>:                      FDate Intrinsic (function).
! * limits, Y10K <4>:                      FDate Intrinsic (subroutine).
! * limits, Y10K:                          Date_and_Time Intrinsic.
! * limits, Y2K:                           IDate Intrinsic (VXT).
! * lines:                                 Lines.
! * lines, continuation:                   Continuation Line.
! * lines, length:                         Fortran Dialect Options.
! * lines, long:                           Long Lines.
! * lines, short:                          Short Lines.
! * Link intrinsic <1>:                    Link Intrinsic (function).
! * Link intrinsic:                        Link Intrinsic (subroutine).
! * linking:                               What is GNU Fortran?.
! * linking against non-standard library:  Strange Behavior at Run Time.
! * linking error for user code:           Cannot Link Fortran Programs.
! * linking error, user code:              Cannot Link Fortran Programs.
! * linking with C:                        Interoperating with C and C++.
! * linking, errors:                       Large Common Blocks.
! * LLe intrinsic:                         LLe Intrinsic.
! * LLt intrinsic:                         LLt Intrinsic.
! * LnBlnk intrinsic:                      LnBlnk Intrinsic.
! * Loc intrinsic:                         Loc Intrinsic.
! * local equivalence areas:               Local Equivalence Areas.
! * Log intrinsic:                         Log Intrinsic.
! * Log10 intrinsic:                       Log10 Intrinsic.
! * logical expressions, comparing:        Equivalence Versus Equality.
! * Logical intrinsic:                     Logical Intrinsic.
! * LOGICAL(KIND=1) type:                  Compiler Types.
! * LOGICAL(KIND=2) type:                  Compiler Types.
! * LOGICAL(KIND=3) type:                  Compiler Types.
! * LOGICAL(KIND=6) type:                  Compiler Types.
! * LOGICAL*1 support:                     Popular Non-standard Types.
! * Long intrinsic:                        Long Intrinsic.
! * long source lines:                     Long Lines.
! * long time:                             Timer Wraparounds.
! * loops, optimizing:                     Optimize Options.
! * loops, speeding up:                    Optimize Options.
! * loops, unrolling:                      Optimize Options.
! * lowercase letters:                     Case Sensitivity.
! * LShift intrinsic:                      LShift Intrinsic.
! * LStat intrinsic <1>:                   LStat Intrinsic (function).
! * LStat intrinsic:                       LStat Intrinsic (subroutine).
! * LTime intrinsic:                       LTime Intrinsic.
! * machine code:                          What is GNU Fortran?.
! * macro options:                         Shorthand Options.
! * main program unit, debugging:          Main Program Unit.
! * main():                                Main Program Unit.
! * MAIN__():                              Main Program Unit.
! * Makefile example:                      Bug Criteria.
! * MAP statement:                         STRUCTURE UNION RECORD MAP.
! * MatMul intrinsic:                      MatMul Intrinsic.
! * Max intrinsic:                         Max Intrinsic.
! * Max0 intrinsic:                        Max0 Intrinsic.
! * Max1 intrinsic:                        Max1 Intrinsic.
! * MaxExponent intrinsic:                 MaxExponent Intrinsic.
! * maximum number of dimensions:          Compiler Limits.
! * maximum rank:                          Compiler Limits.
! * maximum unit number:                   Large File Unit Numbers.
! * MaxLoc intrinsic:                      MaxLoc Intrinsic.
! * MaxVal intrinsic:                      MaxVal Intrinsic.
! * MClock intrinsic:                      MClock Intrinsic.
! * MClock8 intrinsic:                     MClock8 Intrinsic.
! * memory usage, of compiler:             Known Bugs.
! * Merge intrinsic:                       Merge Intrinsic.
! * messages, run-time:                    Run-time Library Errors.
! * messages, warning:                     Warning Options.
! * messages, warning and error:           Warnings and Errors.
! * mil intrinsics group:                  Intrinsic Groups.
! * MIL-STD 1753 <1>:                      MIL-STD 1753.
! * MIL-STD 1753 <2>:                      END DO.
! * MIL-STD 1753 <3>:                      DO WHILE.
! * MIL-STD 1753:                          Fortran Dialect Options.
! * Min intrinsic:                         Min Intrinsic.
! * Min0 intrinsic:                        Min0 Intrinsic.
! * Min1 intrinsic:                        Min1 Intrinsic.
! * MinExponent intrinsic:                 MinExponent Intrinsic.
! * MinLoc intrinsic:                      MinLoc Intrinsic.
! * MinVal intrinsic:                      MinVal Intrinsic.
! * mistakes:                              What is GNU Fortran?.
! * mistyped functions:                    Not My Type.
! * mistyped variables:                    Not My Type.
! * Mod intrinsic:                         Mod Intrinsic.
! * modifying g77:                         Overall Options.
! * Modulo intrinsic:                      Modulo Intrinsic.
! * multi-dimension arrays:                Array Size.
! * MvBits intrinsic:                      MvBits Intrinsic.
! * MXUNIT:                                Large File Unit Numbers.
! * name space:                            Mangling of Names.
! * NAMELIST statement:                    NAMELIST.
! * naming conflicts:                      Multiple Definitions of External Names.
! * naming issues:                         Mangling of Names.
! * naming programs:                       Nothing Happens.
! * NaN values:                            Floating-point Exception Handling.
! * Nearest intrinsic:                     Nearest Intrinsic.
! * negative forms of options:             Invoking G77.
! * negative time:                         Timer Wraparounds.
! * Netlib <1>:                            Increasing Precision/Range.
! * Netlib:                                C Interfacing Tools.
! * network file system:                   Output Assumed To Flush.
! * new users:                             Getting Started.
! * newbies:                               Getting Started.
! * NeXTStep problems:                     NeXTStep Problems.
! * NFS:                                   Output Assumed To Flush.
! * NInt intrinsic:                        NInt Intrinsic.
! * nonportable conversions:               Nonportable Conversions.
! * Not intrinsic:                         Not Intrinsic.
! * nothing happens:                       Nothing Happens.
! * null arguments:                        Ugly Null Arguments.
! * null byte, trailing:                   Character and Hollerith Constants.
! * null CHARACTER strings:                Character Type.
! * number of continuation lines:          Continuation Line.
! * number of dimensions, maximum:         Compiler Limits.
! * number of trips:                       Loops.
! * O edit descriptor:                     I/O.
! * octal constants:                       Double Quote Meaning.
! * omitting arguments:                    Ugly Null Arguments.
! * one-trip DO loops:                     Fortran Dialect Options.
! * open angle:                            Character Set.
! * open bracket:                          Character Set.
! * OPEN statement:                        OPEN CLOSE and INQUIRE Keywords.
! * optimization, better:                  Better Optimization.
! * optimization, for Pentium:             Aligned Data.
! * optimize options:                      Optimize Options.
! * options, --driver <1>:                 Changes.
! * options, --driver:                     News.
! * options, -falias-check <1>:            Aliasing Assumed To Work.
! * options, -falias-check:                Code Gen Options.
! * options, -fargument-alias <1>:         Aliasing Assumed To Work.
! * options, -fargument-alias:             Code Gen Options.
! * options, -fargument-noalias <1>:       Aliasing Assumed To Work.
! * options, -fargument-noalias:           Code Gen Options.
! * options, -fbadu77-intrinsics-delete:   Fortran Dialect Options.
! * options, -fbadu77-intrinsics-disable:  Fortran Dialect Options.
! * options, -fbadu77-intrinsics-enable:   Fortran Dialect Options.
! * options, -fbadu77-intrinsics-hide:     Fortran Dialect Options.
! * options, -fcaller-saves:               Optimize Options.
! * options, -fcase-initcap:               Fortran Dialect Options.
! * options, -fcase-lower:                 Fortran Dialect Options.
! * options, -fcase-preserve:              Fortran Dialect Options.
! * options, -fcase-strict-lower:          Fortran Dialect Options.
! * options, -fcase-strict-upper:          Fortran Dialect Options.
! * options, -fcase-upper:                 Fortran Dialect Options.
! * options, -fdelayed-branch:             Optimize Options.
! * options, -fdollar-ok:                  Fortran Dialect Options.
! * options, -femulate-complex:            Code Gen Options.
! * options, -fexpensive-optimizations:    Optimize Options.
! * options, -ff2c-intrinsics-delete:      Fortran Dialect Options.
! * options, -ff2c-intrinsics-disable:     Fortran Dialect Options.
! * options, -ff2c-intrinsics-enable:      Fortran Dialect Options.
! * options, -ff2c-intrinsics-hide:        Fortran Dialect Options.
! * options, -ff2c-library:                Code Gen Options.
! * options, -ff66:                        Shorthand Options.
! * options, -ff77:                        Shorthand Options.
! * options, -ff90:                        Fortran Dialect Options.
! * options, -ff90-intrinsics-delete:      Fortran Dialect Options.
! * options, -ff90-intrinsics-disable:     Fortran Dialect Options.
! * options, -ff90-intrinsics-enable:      Fortran Dialect Options.
! * options, -ff90-intrinsics-hide:        Fortran Dialect Options.
! * options, -ffast-math:                  Optimize Options.
! * options, -ffinite-math-only:           Optimize Options.
! * options, -ffixed-line-length-N:        Fortran Dialect Options.
! * options, -ffloat-store:                Optimize Options.
! * options, -fforce-addr:                 Optimize Options.
! * options, -fforce-mem:                  Optimize Options.
! * options, -ffree-form:                  Fortran Dialect Options.
! * options, -fgnu-intrinsics-delete:      Fortran Dialect Options.
! * options, -fgnu-intrinsics-disable:     Fortran Dialect Options.
! * options, -fgnu-intrinsics-enable:      Fortran Dialect Options.
! * options, -fgnu-intrinsics-hide:        Fortran Dialect Options.
! * options, -fGROUP-intrinsics-hide:      Overly Convenient Options.
! * options, -finit-local-zero <1>:        Overly Convenient Options.
! * options, -finit-local-zero:            Code Gen Options.
! * options, -fintrin-case-any:            Fortran Dialect Options.
! * options, -fintrin-case-initcap:        Fortran Dialect Options.
! * options, -fintrin-case-lower:          Fortran Dialect Options.
! * options, -fintrin-case-upper:          Fortran Dialect Options.
! * options, -fmatch-case-any:             Fortran Dialect Options.
! * options, -fmatch-case-initcap:         Fortran Dialect Options.
! * options, -fmatch-case-lower:           Fortran Dialect Options.
! * options, -fmatch-case-upper:           Fortran Dialect Options.
! * options, -fmil-intrinsics-delete:      Fortran Dialect Options.
! * options, -fmil-intrinsics-disable:     Fortran Dialect Options.
! * options, -fmil-intrinsics-enable:      Fortran Dialect Options.
! * options, -fmil-intrinsics-hide:        Fortran Dialect Options.
! * options, -fno-argument-noalias-global <1>: Aliasing Assumed To Work.
! * options, -fno-argument-noalias-global: Code Gen Options.
! * options, -fno-automatic <1>:           Overly Convenient Options.
! * options, -fno-automatic:               Code Gen Options.
! * options, -fno-backslash:               Fortran Dialect Options.
! * options, -fno-common:                  Code Gen Options.
! * options, -fno-f2c <1>:                 Avoid f2c Compatibility.
! * options, -fno-f2c:                     Code Gen Options.
! * options, -fno-f77:                     Shorthand Options.
! * options, -fno-fixed-form:              Fortran Dialect Options.
! * options, -fno-globals:                 Code Gen Options.
! * options, -fno-ident:                   Code Gen Options.
! * options, -fno-inline:                  Optimize Options.
! * options, -fno-move-all-movables:       Optimize Options.
! * options, -fno-reduce-all-givs:         Optimize Options.
! * options, -fno-rerun-loop-opt:          Optimize Options.
! * options, -fno-second-underscore:       Code Gen Options.
! * options, -fno-silent:                  Overall Options.
! * options, -fno-trapping-math:           Optimize Options.
! * options, -fno-ugly:                    Shorthand Options.
! * options, -fno-ugly-args:               Fortran Dialect Options.
! * options, -fno-ugly-init:               Fortran Dialect Options.
! * options, -fno-underscoring <1>:        Names.
! * options, -fno-underscoring:            Code Gen Options.
! * options, -fonetrip:                    Fortran Dialect Options.
! * options, -fpack-struct:                Code Gen Options.
! * options, -fpcc-struct-return:          Code Gen Options.
! * options, -fpedantic:                   Warning Options.
! * options, -fPIC:                        News.
! * options, -freg-struct-return:          Code Gen Options.
! * options, -frerun-cse-after-loop:       Optimize Options.
! * options, -fschedule-insns:             Optimize Options.
! * options, -fschedule-insns2:            Optimize Options.
! * options, -fset-g77-defaults:           Overall Options.
! * options, -fshort-double:               Code Gen Options.
! * options, -fsource-case-lower:          Fortran Dialect Options.
! * options, -fsource-case-preserve:       Fortran Dialect Options.
! * options, -fsource-case-upper:          Fortran Dialect Options.
! * options, -fstrength-reduce:            Optimize Options.
! * options, -fsymbol-case-any:            Fortran Dialect Options.
! * options, -fsymbol-case-initcap:        Fortran Dialect Options.
! * options, -fsymbol-case-lower:          Fortran Dialect Options.
! * options, -fsymbol-case-upper:          Fortran Dialect Options.
! * options, -fsyntax-only:                Warning Options.
! * options, -ftypeless-boz:               Fortran Dialect Options.
! * options, -fugly:                       Shorthand Options.
! * options, -fugly-assign:                Fortran Dialect Options.
! * options, -fugly-assumed:               Fortran Dialect Options.
! * options, -fugly-comma:                 Fortran Dialect Options.
! * options, -fugly-complex:               Fortran Dialect Options.
! * options, -fugly-logint:                Fortran Dialect Options.
! * options, -funix-intrinsics-delete:     Fortran Dialect Options.
! * options, -funix-intrinsics-disable:    Fortran Dialect Options.
! * options, -funix-intrinsics-enable:     Fortran Dialect Options.
! * options, -funix-intrinsics-hide:       Fortran Dialect Options.
! * options, -funroll-all-loops:           Optimize Options.
! * options, -funroll-loops:               Optimize Options.
! * options, -funsafe-math-optimizations:  Optimize Options.
! * options, -fversion:                    Overall Options.
! * options, -fvxt:                        Fortran Dialect Options.
! * options, -fvxt-intrinsics-delete:      Fortran Dialect Options.
! * options, -fvxt-intrinsics-disable:     Fortran Dialect Options.
! * options, -fvxt-intrinsics-enable:      Fortran Dialect Options.
! * options, -fvxt-intrinsics-hide:        Fortran Dialect Options.
! * options, -fzeros:                      Code Gen Options.
! * options, -g:                           Debugging Options.
! * options, -I-:                          Directory Options.
! * options, -Idir:                        Directory Options.
! * options, -malign-double <1>:           Aligned Data.
! * options, -malign-double:               Optimize Options.
! * options, -Nl:                          Compiler Limits.
! * options, -Nx:                          Compiler Limits.
! * options, -pedantic:                    Warning Options.
! * options, -pedantic-errors:             Warning Options.
! * options, -v:                           G77 and GCC.
! * options, -W:                           Warning Options.
! * options, -w:                           Warning Options.
! * options, -Waggregate-return:           Warning Options.
! * options, -Wall:                        Warning Options.
! * options, -Wcomment:                    Warning Options.
! * options, -Wconversion:                 Warning Options.
! * options, -Werror:                      Warning Options.
! * options, -Wformat:                     Warning Options.
! * options, -Wid-clash-LEN:               Warning Options.
! * options, -Wimplicit:                   Warning Options.
! * options, -Wlarger-than-LEN:            Warning Options.
! * options, -Wno-globals:                 Warning Options.
! * options, -Wparentheses:                Warning Options.
! * options, -Wredundant-decls:            Warning Options.
! * options, -Wshadow:                     Warning Options.
! * options, -Wsurprising:                 Warning Options.
! * options, -Wswitch:                     Warning Options.
! * options, -Wswitch-default:             Warning Options.
! * options, -Wswitch-enum:                Warning Options.
! * options, -Wtraditional:                Warning Options.
! * options, -Wuninitialized:              Warning Options.
! * options, -Wunused:                     Warning Options.
! * options, -x f77-cpp-input:             LEX.
! * options, adding:                       Adding Options.
! * options, code generation:              Code Gen Options.
! * options, debugging:                    Debugging Options.
! * options, dialect:                      Fortran Dialect Options.
! * options, directory search:             Directory Options.
! * options, GNU Fortran command:          Invoking G77.
! * options, macro:                        Shorthand Options.
! * options, negative forms:               Invoking G77.
! * options, optimization:                 Optimize Options.
! * options, overall:                      Overall Options.
! * options, overly convenient:            Overly Convenient Options.
! * options, preprocessor:                 Preprocessor Options.
! * options, shorthand:                    Shorthand Options.
! * options, warnings:                     Warning Options.
! * Or intrinsic <1>:                      Bit Operations on Floating-point Data.
! * Or intrinsic:                          Or Intrinsic.
! * order of evaluation, side effects:     Order of Side Effects.
! * ordering, array:                       Arrays.
! * other intrinsics:                      Other Intrinsics.
! * output, flushing:                      Output Assumed To Flush.
! * overall options:                       Overall Options.
! * overflow:                              Warning Options.
! * overlapping arguments:                 Aliasing Assumed To Work.
! * overlays:                              Aliasing Assumed To Work.
! * overly convenient options:             Overly Convenient Options.
! * overwritten data:                      Strange Behavior at Run Time.
! * Pack intrinsic:                        Pack Intrinsic.
! * padding:                               Known Bugs.
! * parallel processing:                   Support for Threads.
! * PARAMETER statement <1>:               Old-style PARAMETER Statements.
! * PARAMETER statement:                   Intrinsics in PARAMETER Statements.
! * parameters, unused:                    Warning Options.
! * paths, search:                         Directory Options.
! * PDB:                                   Portable Unformatted Files.
! * pedantic compilation:                  Pedantic Compilation.
! * Pentium optimizations:                 Aligned Data.
! * percent sign:                          Character Set.
! * PError intrinsic:                      PError Intrinsic.
! * placing initialization statements:     Initializing Before Specifying.
! * POINTER statement:                     POINTER Statements.
! * pointers <1>:                          Ugly Assigned Labels.
! * pointers:                              Kind Notation.
! * Poking the bear:                       Philosophy of Code Generation.
! * porting, simplify:                     Simplify Porting.
! * pound sign:                            Character Set.
! * Precision intrinsic:                   Precision Intrinsic.
! * precision, increasing:                 Increasing Precision/Range.
! * prefix-radix constants:                Fortran Dialect Options.
! * preprocessor <1>:                      LEX.
! * preprocessor <2>:                      Bug Reporting.
! * preprocessor <3>:                      Cpp-style directives.
! * preprocessor <4>:                      Overall Options.
! * preprocessor:                          What is GNU Fortran?.
! * preprocessor options:                  Preprocessor Options.
! * Present intrinsic:                     Present Intrinsic.
! * printing compilation status:           Overall Options.
! * printing main source:                  Known Bugs.
! * printing version information <1>:      Overall Options.
! * printing version information:          What is GNU Fortran?.
! * procedures:                            Procedures.
! * Product intrinsic:                     Product Intrinsic.
! * PROGRAM statement:                     Main Program Unit.
! * programs, cc1:                         What is GNU Fortran?.
! * programs, cc1plus:                     What is GNU Fortran?.
! * programs, compiling:                   G77 and GCC.
! * programs, cpp <1>:                     LEX.
! * programs, cpp <2>:                     Bug Reporting.
! * programs, cpp <3>:                     Preprocessor Options.
! * programs, cpp <4>:                     Overall Options.
! * programs, cpp:                         What is GNU Fortran?.
! * programs, f771:                        What is GNU Fortran?.
! * programs, ratfor:                      Overall Options.
! * programs, speeding up:                 Faster Programs.
! * programs, test:                        Nothing Happens.
! * projects:                              Projects.
! * Q edit descriptor:                     Q Edit Descriptor.
! * QAbs intrinsic:                        QAbs Intrinsic.
! * QACos intrinsic:                       QACos Intrinsic.
! * QACosD intrinsic:                      QACosD Intrinsic.
! * QASin intrinsic:                       QASin Intrinsic.
! * QASinD intrinsic:                      QASinD Intrinsic.
! * QATan intrinsic:                       QATan Intrinsic.
! * QATan2 intrinsic:                      QATan2 Intrinsic.
! * QATan2D intrinsic:                     QATan2D Intrinsic.
! * QATanD intrinsic:                      QATanD Intrinsic.
! * QCos intrinsic:                        QCos Intrinsic.
! * QCosD intrinsic:                       QCosD Intrinsic.
! * QCosH intrinsic:                       QCosH Intrinsic.
! * QDiM intrinsic:                        QDiM Intrinsic.
! * QExp intrinsic:                        QExp Intrinsic.
! * QExt intrinsic:                        QExt Intrinsic.
! * QExtD intrinsic:                       QExtD Intrinsic.
! * QFloat intrinsic:                      QFloat Intrinsic.
! * QInt intrinsic:                        QInt Intrinsic.
! * QLog intrinsic:                        QLog Intrinsic.
! * QLog10 intrinsic:                      QLog10 Intrinsic.
! * QMax1 intrinsic:                       QMax1 Intrinsic.
! * QMin1 intrinsic:                       QMin1 Intrinsic.
! * QMod intrinsic:                        QMod Intrinsic.
! * QNInt intrinsic:                       QNInt Intrinsic.
! * QSin intrinsic:                        QSin Intrinsic.
! * QSinD intrinsic:                       QSinD Intrinsic.
! * QSinH intrinsic:                       QSinH Intrinsic.
! * QSqRt intrinsic:                       QSqRt Intrinsic.
! * QTan intrinsic:                        QTan Intrinsic.
! * QTanD intrinsic:                       QTanD Intrinsic.
! * QTanH intrinsic:                       QTanH Intrinsic.
! * question mark:                         Character Set.
! * questionable instructions:             What is GNU Fortran?.
! * Radix intrinsic:                       Radix Intrinsic.
! * Rand intrinsic:                        Rand Intrinsic.
! * Random_Number intrinsic:               Random_Number Intrinsic.
! * Random_Seed intrinsic:                 Random_Seed Intrinsic.
! * range checking:                        Code Gen Options.
! * Range intrinsic:                       Range Intrinsic.
! * range, increasing:                     Increasing Precision/Range.
! * rank, maximum:                         Compiler Limits.
! * ratfor:                                Overall Options.
! * Ratfor preprocessor:                   Overall Options.
! * READONLY:                              READONLY Keyword.
! * reads and writes, scheduling:          Aliasing Assumed To Work.
! * Real intrinsic <1>:                    Real Intrinsic.
! * Real intrinsic:                        REAL() and AIMAG() of Complex.
! * real part:                             Ugly Complex Part Extraction.
! * REAL(KIND=1) type:                     Compiler Types.
! * REAL(KIND=2) type:                     Compiler Types.
! * REAL*16 support:                       Full Support for Compiler Types.
! * RealPart intrinsic:                    RealPart Intrinsic.
! * recent versions <1>:                   Changes.
! * recent versions:                       News.
! * RECORD statement:                      STRUCTURE UNION RECORD MAP.
! * recursion, lack of:                    RECURSIVE Keyword.
! * RECURSIVE keyword:                     RECURSIVE Keyword.
! * reference works:                       Language.
! * Rename intrinsic <1>:                  Rename Intrinsic (function).
! * Rename intrinsic:                      Rename Intrinsic (subroutine).
! * Repeat intrinsic:                      Repeat Intrinsic.
! * reporting bugs:                        Bugs.
! * reporting compilation status:          Overall Options.
! * Reshape intrinsic:                     Reshape Intrinsic.
! * results, inconsistent:                 Floating-point Errors.
! * RETURN statement <1>:                  Alternate Returns.
! * RETURN statement:                      Functions.
! * return type of functions:              Functions.
! * right angle:                           Character Set.
! * right bracket:                         Character Set.
! * rounding errors:                       Floating-point Errors.
! * row-major ordering:                    Arrays.
! * RRSpacing intrinsic:                   RRSpacing Intrinsic.
! * RShift intrinsic:                      RShift Intrinsic.
! * run-time, dynamic allocation:          Arbitrary Concatenation.
! * run-time, initialization:              Startup Code.
! * run-time, library:                     What is GNU Fortran?.
! * run-time, options:                     Code Gen Options.
! * SAVE statement:                        Code Gen Options.
! * saved variables:                       Variables Assumed To Be Saved.
! * Scale intrinsic:                       Scale Intrinsic.
! * Scan intrinsic:                        Scan Intrinsic.
! * scheduling of reads and writes:        Aliasing Assumed To Work.
! * scope <1>:                             Scope and Classes of Names.
! * scope:                                 Scope of Names and Labels.
! * search path:                           Directory Options.
! * search paths, for included files:      Directory Options.
! * Secnds intrinsic:                      Secnds Intrinsic.
! * Second intrinsic <1>:                  Second Intrinsic (subroutine).
! * Second intrinsic:                      Second Intrinsic (function).
! * segmentation violation <1>:            Strange Behavior at Run Time.
! * segmentation violation <2>:            Stack Overflow.
! * segmentation violation:                NeXTStep Problems.
! * Selected_Int_Kind intrinsic:           Selected_Int_Kind Intrinsic.
! * Selected_Real_Kind intrinsic:          Selected_Real_Kind Intrinsic.
! * semicolon <1>:                         Character Set.
! * semicolon:                             Statements Comments Lines.
! * sequence numbers:                      Better Source Model.
! * Set_Exponent intrinsic:                Set_Exponent Intrinsic.
! * Shape intrinsic:                       Shape Intrinsic.
! * SHARED:                                READONLY Keyword.
! * Shift intrinsic:                       Bit Operations on Floating-point Data.
! * Short intrinsic:                       Short Intrinsic.
! * short source lines:                    Short Lines.
! * short time:                            Timer Wraparounds.
! * shorthand options:                     Shorthand Options.
! * side effects, order of evaluation:     Order of Side Effects.
! * Sign intrinsic:                        Sign Intrinsic.
! * signal 11:                             Signal 11 and Friends.
! * Signal intrinsic <1>:                  Signal Intrinsic (function).
! * Signal intrinsic:                      Signal Intrinsic (subroutine).
! * signature of procedures:               Procedures.
! * simplify porting:                      Simplify Porting.
! * Sin intrinsic:                         Sin Intrinsic.
! * SinD intrinsic:                        SinD Intrinsic.
! * SinH intrinsic:                        SinH Intrinsic.
! * Sleep intrinsic:                       Sleep Intrinsic.
! * Sngl intrinsic:                        Sngl Intrinsic.
! * SnglQ intrinsic:                       SnglQ Intrinsic.
! * Solaris:                               Strange Behavior at Run Time.
! * source code <1>:                       Case Sensitivity.
! * source code <2>:                       Source Form.
! * source code <3>:                       Lines.
! * source code:                           What is GNU Fortran?.
! * source file:                           What is GNU Fortran?.
! * source file format <1>:                Case Sensitivity.
! * source file format <2>:                Source Form.
! * source file format <3>:                Lines.
! * source file format:                    Fortran Dialect Options.
! * source format <1>:                     Source Form.
! * source format:                         Lines.
! * source lines, long:                    Long Lines.
! * source lines, short:                   Short Lines.
! * space <1>:                             Lines.
! * space:                                 Character Set.
! * space, endless printing of:            Strange Behavior at Run Time.
! * space, padding with:                   Short Lines.
! * Spacing intrinsic:                     Spacing Intrinsic.
! * SPC <1>:                               Lines.
! * SPC:                                   Character Set.
! * speed, of compiler:                    Known Bugs.
! * speed, of loops:                       Optimize Options.
! * speed, of programs:                    Faster Programs.
! * spills of floating-point results:      Floating-point Errors.
! * Spread intrinsic:                      Spread Intrinsic.
! * SqRt intrinsic:                        SqRt Intrinsic.
! * SRand intrinsic:                       SRand Intrinsic.
! * stack, 387 coprocessor:                News.
! * stack, aligned:                        Aligned Data.
! * stack, overflow:                       Stack Overflow.
! * standard, ANSI FORTRAN 77:             Language.
! * standard, support for:                 Standard Support.
! * startup code:                          Startup Code.
! * Stat intrinsic <1>:                    Stat Intrinsic (function).
! * Stat intrinsic:                        Stat Intrinsic (subroutine).
! * statement labels, assigned:            Assigned Statement Labels.
! * statements, ACCEPT:                    TYPE and ACCEPT I/O Statements.
! * statements, ASSIGN <1>:                Assigned Statement Labels.
! * statements, ASSIGN:                    Ugly Assigned Labels.
! * statements, AUTOMATIC:                 AUTOMATIC Statement.
! * statements, BLOCK DATA <1>:            Multiple Definitions of External Names.
! * statements, BLOCK DATA:                Block Data and Libraries.
! * statements, CLOSE:                     OPEN CLOSE and INQUIRE Keywords.
! * statements, COMMON <1>:                Multiple Definitions of External Names.
! * statements, COMMON:                    Common Blocks.
! * statements, COMPLEX:                   Complex Variables.
! * statements, CYCLE:                     CYCLE and EXIT.
! * statements, DATA <1>:                  Known Bugs.
! * statements, DATA:                      Code Gen Options.
! * statements, DECODE:                    ENCODE and DECODE.
! * statements, DIMENSION <1>:             Array Bounds Expressions.
! * statements, DIMENSION <2>:             Adjustable Arrays.
! * statements, DIMENSION:                 Arrays.
! * statements, DO <1>:                    Loops.
! * statements, DO:                        Warning Options.
! * statements, ENCODE:                    ENCODE and DECODE.
! * statements, ENTRY:                     Alternate Entry Points.
! * statements, EQUIVALENCE:               Local Equivalence Areas.
! * statements, EXIT:                      CYCLE and EXIT.
! * statements, FORMAT:                    Expressions in FORMAT Statements.
! * statements, FUNCTION <1>:              Functions.
! * statements, FUNCTION:                  Procedures.
! * statements, GOTO:                      Assigned Statement Labels.
! * statements, IMPLICIT CHARACTER*(*):    Limitation on Implicit Declarations.
! * statements, INQUIRE:                   OPEN CLOSE and INQUIRE Keywords.
! * statements, MAP:                       STRUCTURE UNION RECORD MAP.
! * statements, NAMELIST:                  NAMELIST.
! * statements, OPEN:                      OPEN CLOSE and INQUIRE Keywords.
! * statements, PARAMETER <1>:             Old-style PARAMETER Statements.
! * statements, PARAMETER:                 Intrinsics in PARAMETER Statements.
! * statements, POINTER:                   POINTER Statements.
! * statements, PROGRAM:                   Main Program Unit.
! * statements, RECORD:                    STRUCTURE UNION RECORD MAP.
! * statements, RETURN <1>:                Alternate Returns.
! * statements, RETURN:                    Functions.
! * statements, SAVE:                      Code Gen Options.
! * statements, separated by semicolon:    Statements Comments Lines.
! * statements, STRUCTURE:                 STRUCTURE UNION RECORD MAP.
! * statements, SUBROUTINE <1>:            Alternate Returns.
! * statements, SUBROUTINE:                Procedures.
! * statements, TYPE:                      TYPE and ACCEPT I/O Statements.
! * statements, UNION:                     STRUCTURE UNION RECORD MAP.
! * STATIC:                                AUTOMATIC Statement.
! * static variables:                      Variables Assumed To Be Saved.
! * status, compilation:                   Overall Options.
! * storage association:                   Aliasing Assumed To Work.
! * strings, empty:                        Character Type.
! * STRUCTURE statement:                   STRUCTURE UNION RECORD MAP.
! * structures:                            Known Bugs.
! * submodels:                             Use Submodel Options.
! * SUBROUTINE statement <1>:              Alternate Returns.
! * SUBROUTINE statement:                  Procedures.
! * subroutines:                           Alternate Returns.
! * subscript checking:                    Code Gen Options.
! * substring checking:                    Code Gen Options.
! * suffixes, file name:                   Overall Options.
! * Sum intrinsic:                         Sum Intrinsic.
! * support, Alpha:                        Known Bugs.
! * support, ELF:                          News.
! * support, f77:                          Backslash in Constants.
! * support, FORTRAN 77:                   Standard Support.
! * support, Fortran 90:                   Fortran 90 Support.
! * support, gdb:                          Debugger Problems.
! * suppressing warnings:                  Warning Options.
! * symbol names <1>:                      Names.
! * symbol names:                          Fortran Dialect Options.
! * symbol names, scope and classes:       Scope and Classes of Names.
! * symbol names, transforming:            Code Gen Options.
! * symbol names, underscores:             Code Gen Options.
! * SymLnk intrinsic <1>:                  SymLnk Intrinsic (function).
! * SymLnk intrinsic:                      SymLnk Intrinsic (subroutine).
! * synchronous write errors:              Output Assumed To Flush.
! * syntax checking:                       Warning Options.
! * System intrinsic <1>:                  System Intrinsic (function).
! * System intrinsic:                      System Intrinsic (subroutine).
! * System_Clock intrinsic:                System_Clock Intrinsic.
! * tab character:                         Tabs.
! * table of intrinsics:                   Table of Intrinsic Functions.
! * Tan intrinsic:                         Tan Intrinsic.
! * TanD intrinsic:                        TanD Intrinsic.
! * TanH intrinsic:                        TanH Intrinsic.
! * test programs:                         Nothing Happens.
! * testing alignment:                     Aligned Data.
! * textbooks:                             Language.
! * threads:                               Support for Threads.
! * Time intrinsic <1>:                    Time Intrinsic (VXT).
! * Time intrinsic:                        Time Intrinsic (UNIX).
! * Time8 intrinsic:                       Time8 Intrinsic.
! * Tiny intrinsic:                        Tiny Intrinsic.
! * Toolpack:                              Increasing Precision/Range.
! * trailing comma:                        Ugly Null Arguments.
! * trailing comment <1>:                  LEX.
! * trailing comment <2>:                  Trailing Comment.
! * trailing comment:                      Statements Comments Lines.
! * trailing null byte:                    Character and Hollerith Constants.
! * Transfer intrinsic:                    Transfer Intrinsic.
! * transforming symbol names <1>:         Names.
! * transforming symbol names:             Code Gen Options.
! * translation of user programs:          What is GNU Fortran?.
! * Transpose intrinsic:                   Transpose Intrinsic.
! * Trim intrinsic:                        Trim Intrinsic.
! * trips, number of:                      Loops.
! * truncation, of floating-point values:  Floating-point Errors.
! * truncation, of long lines:             Long Lines.
! * TtyNam intrinsic <1>:                  TtyNam Intrinsic (function).
! * TtyNam intrinsic:                      TtyNam Intrinsic (subroutine).
! * TYPE statement:                        TYPE and ACCEPT I/O Statements.
! * types, COMPLEX(KIND=1):                Compiler Types.
! * types, COMPLEX(KIND=2):                Compiler Types.
! * types, constants <1>:                  Compiler Constants.
! * types, constants <2>:                  Constants.
! * types, constants:                      Fortran Dialect Options.
! * types, DOUBLE COMPLEX:                 Compiler Types.
! * types, DOUBLE PRECISION:               Compiler Types.
! * types, file:                           Overall Options.
! * types, Fortran/C:                      C Access to Type Information.
! * types, INTEGER(KIND=1):                Compiler Types.
! * types, INTEGER(KIND=2):                Compiler Types.
! * types, INTEGER(KIND=3):                Compiler Types.
! * types, INTEGER(KIND=6):                Compiler Types.
! * types, INTEGER*2:                      Popular Non-standard Types.
! * types, INTEGER*8:                      Full Support for Compiler Types.
! * types, LOGICAL(KIND=1):                Compiler Types.
! * types, LOGICAL(KIND=2):                Compiler Types.
! * types, LOGICAL(KIND=3):                Compiler Types.
! * types, LOGICAL(KIND=6):                Compiler Types.
! * types, LOGICAL*1:                      Popular Non-standard Types.
! * types, of data:                        Compiler Types.
! * types, REAL(KIND=1):                   Compiler Types.
! * types, REAL(KIND=2):                   Compiler Types.
! * types, REAL*16:                        Full Support for Compiler Types.
! * UBound intrinsic:                      UBound Intrinsic.
! * ugly features <1>:                     Distensions.
! * ugly features:                         Shorthand Options.
! * UMask intrinsic <1>:                   UMask Intrinsic (function).
! * UMask intrinsic:                       UMask Intrinsic (subroutine).
! * undefined behavior:                    Bug Criteria.
! * undefined function value:              Bug Criteria.
! * undefined reference (_main):           Cannot Link Fortran Programs.
! * underscore <1>:                        Mangling of Names.
! * underscore <2>:                        Underscores in Symbol Names.
! * underscore <3>:                        Character Set.
! * underscore:                            Code Gen Options.
! * unformatted files:                     Portable Unformatted Files.
! * uninitialized variables <1>:           Variables Assumed To Be Zero.
! * uninitialized variables <2>:           Code Gen Options.
! * uninitialized variables:               Warning Options.
! * UNION statement:                       STRUCTURE UNION RECORD MAP.
! * unit numbers:                          Large File Unit Numbers.
! * UNIX f77:                              Shorthand Options.
! * UNIX intrinsics:                       Fortran Dialect Options.
! * Unlink intrinsic <1>:                  Unlink Intrinsic (function).
! * Unlink intrinsic:                      Unlink Intrinsic (subroutine).
! * Unpack intrinsic:                      Unpack Intrinsic.
! * unrecognized file format:              What is GNU Fortran?.
! * unresolved reference (various):        Cannot Link Fortran Programs.
! * unrolling loops:                       Optimize Options.
! * UNSAVE:                                AUTOMATIC Statement.
! * unsupported warnings:                  Warning Options.
! * unused arguments <1>:                  Unused Arguments.
! * unused arguments:                      Warning Options.
! * unused dummies:                        Warning Options.
! * unused parameters:                     Warning Options.
! * unused variables:                      Warning Options.
! * uppercase letters:                     Case Sensitivity.
! * user-visible changes:                  Changes.
! * variables, assumed to be zero:         Variables Assumed To Be Zero.
! * variables, automatic:                  AUTOMATIC Statement.
! * variables, initialization of:          Code Gen Options.
! * variables, mistyped:                   Not My Type.
! * variables, retaining values across calls: Variables Assumed To Be Saved.
! * variables, uninitialized <1>:          Code Gen Options.
! * variables, uninitialized:              Warning Options.
! * variables, unused:                     Warning Options.
! * Verify intrinsic:                      Verify Intrinsic.
! * version information, printing <1>:     Overall Options.
! * version information, printing:         What is GNU Fortran?.
! * versions, recent <1>:                  Changes.
! * versions, recent:                      News.
! * VXT extensions <1>:                    VXT Fortran.
! * VXT extensions:                        Fortran Dialect Options.
! * VXT intrinsics:                        Fortran Dialect Options.
! * vxtidate_y2kbuggy_0:                   Year 2000 (Y2K) Problems.
! * warnings:                              What is GNU Fortran?.
! * warnings vs errors:                    Warnings and Errors.
! * warnings, all:                         Warning Options.
! * warnings, extra:                       Warning Options.
! * warnings, global names <1>:            Code Gen Options.
! * warnings, global names:                Warning Options.
! * warnings, implicit declaration:        Warning Options.
! * warnings, suppressing:                 Warning Options.
! * warnings, unsupported:                 Warning Options.
! * wisdom:                                Collected Fortran Wisdom.
! * wraparound:                            Run-time Environment Limits.
! * wraparound, timings <1>:               Secnds Intrinsic.
! * wraparound, timings <2>:               DTime Intrinsic (function).
! * wraparound, timings <3>:               Time8 Intrinsic.
! * wraparound, timings <4>:               Time Intrinsic (UNIX).
! * wraparound, timings <5>:               System_Clock Intrinsic.
! * wraparound, timings <6>:               Second Intrinsic (subroutine).
! * wraparound, timings <7>:               Second Intrinsic (function).
! * wraparound, timings <8>:               MClock8 Intrinsic.
! * wraparound, timings <9>:               MClock Intrinsic.
! * wraparound, timings <10>:              ETime Intrinsic (function).
! * wraparound, timings <11>:              ETime Intrinsic (subroutine).
! * wraparound, timings <12>:              DTime Intrinsic (subroutine).
! * wraparound, timings:                   CPU_Time Intrinsic.
! * wraparound, Y10K <1>:                  Time Intrinsic (VXT).
! * wraparound, Y10K <2>:                  IDate Intrinsic (UNIX).
! * wraparound, Y10K <3>:                  FDate Intrinsic (function).
! * wraparound, Y10K <4>:                  FDate Intrinsic (subroutine).
! * wraparound, Y10K:                      Date_and_Time Intrinsic.
! * wraparound, Y2K:                       IDate Intrinsic (VXT).
! * writes, flushing:                      Output Assumed To Flush.
! * writing code:                          Collected Fortran Wisdom.
! * x86 floating-point:                    Floating-point precision.
! * x86 FPU stack:                         Inconsistent Calling Sequences.
! * XOr intrinsic:                         XOr Intrinsic.
! * Y10K compliance <1>:                   Time Intrinsic (VXT).
! * Y10K compliance <2>:                   Year 10000 (Y10K) Problems.
! * Y10K compliance <3>:                   IDate Intrinsic (UNIX).
! * Y10K compliance <4>:                   FDate Intrinsic (function).
! * Y10K compliance <5>:                   FDate Intrinsic (subroutine).
! * Y10K compliance:                       Date_and_Time Intrinsic.
! * Y2K compliance <1>:                    Y2KBAD.
! * Y2K compliance <2>:                    IDate Intrinsic (VXT).
! * Y2K compliance <3>:                    Date Intrinsic.
! * Y2K compliance:                        Year 2000 (Y2K) Problems.
! * y2kbuggy:                              Year 2000 (Y2K) Problems.
! * Year 10000 compliance <1>:             Time Intrinsic (VXT).
! * Year 10000 compliance <2>:             Year 10000 (Y10K) Problems.
! * Year 10000 compliance <3>:             IDate Intrinsic (UNIX).
! * Year 10000 compliance <4>:             FDate Intrinsic (function).
! * Year 10000 compliance <5>:             FDate Intrinsic (subroutine).
! * Year 10000 compliance:                 Date_and_Time Intrinsic.
! * Year 2000 compliance <1>:              Y2KBAD.
! * Year 2000 compliance <2>:              IDate Intrinsic (VXT).
! * Year 2000 compliance <3>:              Date Intrinsic.
! * Year 2000 compliance:                  Year 2000 (Y2K) Problems.
! * Z edit descriptor <1>:                 Fortran 90 Features.
! * Z edit descriptor:                     I/O.
! * ZAbs intrinsic:                        ZAbs Intrinsic.
! * ZCos intrinsic:                        ZCos Intrinsic.
! * zero byte, trailing:                   Character and Hollerith Constants.
! * zero-initialized variables:            Variables Assumed To Be Zero.
! * zero-length CHARACTER:                 Character Type.
! * zero-trip DO loops:                    Fortran Dialect Options.
! * ZExp intrinsic:                        ZExp Intrinsic.
! * ZExt intrinsic:                        ZExt Intrinsic.
! * ZLog intrinsic:                        ZLog Intrinsic.
! * ZSin intrinsic:                        ZSin Intrinsic.
! * ZSqRt intrinsic:                       ZSqRt Intrinsic.
! 
! 
  
  Tag Table:
! Node: Top2280
! Node: Copying4235
! Node: GNU Free Documentation License23435
! Node: Contributors45844
! Node: Funding49123
! Node: Funding GNU Fortran51635
! Node: Getting Started52849
! Node: What is GNU Fortran?55098
! Node: G77 and GCC64986
! Node: Invoking G7766204
! Node: Option Summary68142
! Node: Overall Options73000
! Node: Shorthand Options79740
! Node: Fortran Dialect Options82037
! Node: Warning Options93294
! Node: Debugging Options102211
! Node: Optimize Options103801
! Ref: Optimize Options-Footnote-1109819
! Node: Preprocessor Options110512
! Node: Directory Options111693
! Node: Code Gen Options113005
! Node: Environment Variables127912
! Node: News128367
! Node: Changes182665
! Node: Language210406
! Node: Direction of Language Development212609
! Node: Standard Support218849
! Node: No Passing External Assumed-length219570
! Node: No Passing Dummy Assumed-length220047
! Node: No Pathological Implied-DO220562
! Node: No Useless Implied-DO221249
! Node: Conformance221980
! Node: Notation Used224003
! Node: Terms and Concepts228209
! Node: Syntactic Items228721
! Node: Statements Comments Lines229403
! Node: Scope of Names and Labels231268
! Node: Characters Lines Sequence231698
! Node: Character Set232304
! Node: Lines233305
! Node: Continuation Line235781
! Node: Statements236736
! Node: Statement Labels237692
! Node: Order238384
! Node: INCLUDE239269
! Node: Cpp-style directives242041
! Node: Data Types and Constants242496
! Node: Types246017
! Node: Double Notation247106
! Node: Star Notation248178
! Node: Kind Notation251123
! Node: Constants259543
! Node: Integer Type261059
! Node: Character Type261657
! Node: Expressions262421
! Node: %LOC()262837
! Node: Specification Statements265567
! Node: NAMELIST266024
! Node: DOUBLE COMPLEX266775
! Node: Control Statements267029
! Node: DO WHILE267521
! Node: END DO267826
! Node: Construct Names268833
! Node: CYCLE and EXIT269573
! Node: Functions and Subroutines272337
! Node: %VAL()272983
! Node: %REF()274347
! Node: %DESCR()276175
! Node: Generics and Specifics278308
! Node: REAL() and AIMAG() of Complex285510
! Node: CMPLX() of DOUBLE PRECISION287343
! Node: MIL-STD 1753289069
! Node: f77/f2c Intrinsics289411
! Node: Table of Intrinsic Functions289981
! Node: Abort Intrinsic306693
! Node: Abs Intrinsic306957
! Node: Access Intrinsic307820
! Node: AChar Intrinsic308656
! Node: ACos Intrinsic309178
! Node: AdjustL Intrinsic309639
! Node: AdjustR Intrinsic309964
! Node: AImag Intrinsic310290
! Node: AInt Intrinsic311095
! Node: Alarm Intrinsic311723
! Node: All Intrinsic312555
! Node: Allocated Intrinsic312867
! Node: ALog Intrinsic313196
! Node: ALog10 Intrinsic313586
! Node: AMax0 Intrinsic313984
! Node: AMax1 Intrinsic314469
! Node: AMin0 Intrinsic314922
! Node: AMin1 Intrinsic315406
! Node: AMod Intrinsic315858
! Node: And Intrinsic316284
! Node: ANInt Intrinsic316790
! Node: Any Intrinsic317554
! Node: ASin Intrinsic317861
! Node: Associated Intrinsic318319
! Node: ATan Intrinsic318653
! Node: ATan2 Intrinsic319119
! Node: BesJ0 Intrinsic319670
! Node: BesJ1 Intrinsic320131
! Node: BesJN Intrinsic320592
! Node: BesY0 Intrinsic321123
! Node: BesY1 Intrinsic321585
! Node: BesYN Intrinsic322047
! Node: Bit_Size Intrinsic322582
! Node: BTest Intrinsic323241
! Node: CAbs Intrinsic323961
! Node: CCos Intrinsic324348
! Node: Ceiling Intrinsic324740
! Node: CExp Intrinsic325062
! Node: Char Intrinsic325454
! Node: ChDir Intrinsic (subroutine)326708
! Node: ChMod Intrinsic (subroutine)327711
! Node: CLog Intrinsic328981
! Node: Cmplx Intrinsic329385
! Node: Complex Intrinsic330186
! Node: Conjg Intrinsic331632
! Node: Cos Intrinsic332056
! Node: CosH Intrinsic332519
! Node: Count Intrinsic332894
! Node: CPU_Time Intrinsic333212
! Node: CShift Intrinsic334003
! Node: CSin Intrinsic334325
! Node: CSqRt Intrinsic334717
! Node: CTime Intrinsic (subroutine)335127
! Node: CTime Intrinsic (function)335882
! Node: DAbs Intrinsic336516
! Node: DACos Intrinsic336912
! Node: DASin Intrinsic337303
! Node: DATan Intrinsic337695
! Node: DATan2 Intrinsic338088
! Node: Date_and_Time Intrinsic338543
! Node: DbesJ0 Intrinsic339907
! Node: DbesJ1 Intrinsic340300
! Node: DbesJN Intrinsic340686
! Node: DbesY0 Intrinsic341142
! Node: DbesY1 Intrinsic341528
! Node: DbesYN Intrinsic341914
! Node: Dble Intrinsic342368
! Node: DCos Intrinsic343074
! Node: DCosH Intrinsic343458
! Node: DDiM Intrinsic343848
! Node: DErF Intrinsic344280
! Node: DErFC Intrinsic344649
! Node: DExp Intrinsic345024
! Node: Digits Intrinsic345410
! Node: DiM Intrinsic345727
! Node: DInt Intrinsic346226
! Node: DLog Intrinsic346610
! Node: DLog10 Intrinsic346995
! Node: DMax1 Intrinsic347393
! Node: DMin1 Intrinsic347847
! Node: DMod Intrinsic348299
! Node: DNInt Intrinsic348727
! Node: Dot_Product Intrinsic349126
! Node: DProd Intrinsic349466
! Node: DSign Intrinsic349848
! Node: DSin Intrinsic350287
! Node: DSinH Intrinsic350672
! Node: DSqRt Intrinsic351063
! Node: DTan Intrinsic351454
! Node: DTanH Intrinsic351839
! Node: DTime Intrinsic (subroutine)352243
! Node: EOShift Intrinsic353514
! Node: Epsilon Intrinsic353853
! Node: ErF Intrinsic354177
! Node: ErFC Intrinsic354583
! Node: ETime Intrinsic (subroutine)355143
! Node: ETime Intrinsic (function)356306
! Node: Exit Intrinsic357346
! Node: Exp Intrinsic357855
! Node: Exponent Intrinsic358317
! Node: FDate Intrinsic (subroutine)358656
! Node: FDate Intrinsic (function)359566
! Node: FGet Intrinsic (subroutine)360338
! Node: FGetC Intrinsic (subroutine)361175
! Node: Float Intrinsic362052
! Node: Floor Intrinsic362452
! Node: Flush Intrinsic362768
! Node: FNum Intrinsic363347
! Node: FPut Intrinsic (subroutine)363795
! Node: FPutC Intrinsic (subroutine)364592
! Node: Fraction Intrinsic365439
! Node: FSeek Intrinsic365780
! Node: FStat Intrinsic (subroutine)366505
! Node: FStat Intrinsic (function)368029
! Node: FTell Intrinsic (subroutine)369318
! Node: FTell Intrinsic (function)369991
! Node: GError Intrinsic370508
! Node: GetArg Intrinsic370882
! Node: GetCWD Intrinsic (subroutine)371550
! Node: GetCWD Intrinsic (function)372405
! Node: GetEnv Intrinsic373024
! Node: GetGId Intrinsic373611
! Node: GetLog Intrinsic373917
! Node: GetPId Intrinsic374455
! Node: GetUId Intrinsic374763
! Node: GMTime Intrinsic375068
! Node: HostNm Intrinsic (subroutine)376076
! Node: HostNm Intrinsic (function)377165
! Node: Huge Intrinsic378007
! Node: IAbs Intrinsic378330
! Node: IAChar Intrinsic378721
! Node: IAnd Intrinsic379261
! Node: IArgC Intrinsic379749
! Node: IBClr Intrinsic380125
! Node: IBits Intrinsic380636
! Node: IBSet Intrinsic381350
! Node: IChar Intrinsic381852
! Node: IDate Intrinsic (UNIX)383071
! Node: IDiM Intrinsic383874
! Node: IDInt Intrinsic384323
! Node: IDNInt Intrinsic384716
! Node: IEOr Intrinsic385115
! Node: IErrNo Intrinsic385613
! Node: IFix Intrinsic385940
! Node: Imag Intrinsic386328
! Node: ImagPart Intrinsic387333
! Node: Index Intrinsic388359
! Node: Int Intrinsic388912
! Node: Int2 Intrinsic389627
! Node: Int8 Intrinsic390336
! Node: IOr Intrinsic391045
! Node: IRand Intrinsic391525
! Node: IsaTty Intrinsic392445
! Node: IShft Intrinsic392869
! Node: IShftC Intrinsic393699
! Node: ISign Intrinsic394628
! Node: ITime Intrinsic395078
! Node: Kill Intrinsic (subroutine)395480
! Node: Kind Intrinsic396316
! Node: LBound Intrinsic396641
! Node: Len Intrinsic396958
! Node: Len_Trim Intrinsic397594
! Node: LGe Intrinsic398006
! Node: LGt Intrinsic399419
! Node: Link Intrinsic (subroutine)400324
! Node: LLe Intrinsic401288
! Node: LLt Intrinsic402193
! Node: LnBlnk Intrinsic403087
! Node: Loc Intrinsic403490
! Node: Log Intrinsic403921
! Node: Log10 Intrinsic404512
! Node: Logical Intrinsic405054
! Node: Long Intrinsic405377
! Node: LShift Intrinsic405901
! Node: LStat Intrinsic (subroutine)406937
! Node: LStat Intrinsic (function)408748
! Node: LTime Intrinsic410310
! Node: MatMul Intrinsic411314
! Node: Max Intrinsic411632
! Node: Max0 Intrinsic412183
! Node: Max1 Intrinsic412634
! Node: MaxExponent Intrinsic413118
! Node: MaxLoc Intrinsic413458
! Node: MaxVal Intrinsic413785
! Node: MClock Intrinsic414107
! Node: MClock8 Intrinsic415005
! Node: Merge Intrinsic416193
! Node: Min Intrinsic416509
! Node: Min0 Intrinsic417060
! Node: Min1 Intrinsic417511
! Node: MinExponent Intrinsic417995
! Node: MinLoc Intrinsic418335
! Node: MinVal Intrinsic418662
! Node: Mod Intrinsic418981
! Node: Modulo Intrinsic419504
! Node: MvBits Intrinsic419823
! Node: Nearest Intrinsic420689
! Node: NInt Intrinsic421013
! Node: Not Intrinsic421851
! Node: Or Intrinsic422246
! Node: Pack Intrinsic422744
! Node: PError Intrinsic423054
! Node: Precision Intrinsic423508
! Node: Present Intrinsic423843
! Node: Product Intrinsic424173
! Node: Radix Intrinsic424499
! Node: Rand Intrinsic424816
! Node: Random_Number Intrinsic425703
! Node: Random_Seed Intrinsic426056
! Node: Range Intrinsic426404
! Node: Real Intrinsic426725
! Node: RealPart Intrinsic427731
! Node: Rename Intrinsic (subroutine)428764
! Node: Repeat Intrinsic429735
! Node: Reshape Intrinsic430071
! Node: RRSpacing Intrinsic430400
! Node: RShift Intrinsic430735
! Node: Scale Intrinsic431733
! Node: Scan Intrinsic432049
! Node: Second Intrinsic (function)432373
! Node: Second Intrinsic (subroutine)433204
! Node: Selected_Int_Kind Intrinsic434179
! Node: Selected_Real_Kind Intrinsic434570
! Node: Set_Exponent Intrinsic434957
! Node: Shape Intrinsic435314
! Node: Short Intrinsic435637
! Node: Sign Intrinsic436332
! Node: Signal Intrinsic (subroutine)436932
! Node: Sin Intrinsic439146
! Node: SinH Intrinsic439621
! Node: Sleep Intrinsic439994
! Node: Sngl Intrinsic440336
! Node: Spacing Intrinsic440725
! Node: Spread Intrinsic441049
! Node: SqRt Intrinsic441370
! Node: SRand Intrinsic441974
! Node: Stat Intrinsic (subroutine)442351
! Node: Stat Intrinsic (function)443965
! Node: Sum Intrinsic445328
! Node: SymLnk Intrinsic (subroutine)445660
! Node: System Intrinsic (subroutine)446691
! Node: System_Clock Intrinsic447630
! Node: Tan Intrinsic448754
! Node: TanH Intrinsic449214
! Node: Time Intrinsic (UNIX)449596
! Node: Time8 Intrinsic450581
! Node: Tiny Intrinsic451760
! Node: Transfer Intrinsic452075
! Node: Transpose Intrinsic452406
! Node: Trim Intrinsic452740
! Node: TtyNam Intrinsic (subroutine)453070
! Node: TtyNam Intrinsic (function)453772
! Node: UBound Intrinsic454341
! Node: UMask Intrinsic (subroutine)454686
! Node: Unlink Intrinsic (subroutine)455383
! Node: Unpack Intrinsic456280
! Node: Verify Intrinsic456615
! Node: XOr Intrinsic456934
! Node: ZAbs Intrinsic457450
! Node: ZCos Intrinsic457819
! Node: ZExp Intrinsic458192
! Node: ZLog Intrinsic458565
! Node: ZSin Intrinsic458938
! Node: ZSqRt Intrinsic459312
! Node: Scope and Classes of Names459669
! Node: Underscores in Symbol Names460151
! Node: I/O460398
! Node: Fortran 90 Features461171
! Node: Other Dialects463973
! Node: Source Form465132
! Node: Carriage Returns466347
! Node: Tabs466676
! Node: Short Lines467549
! Node: Long Lines468523
! Node: Ampersands469134
! Node: Trailing Comment469388
! Node: Debug Line470164
! Node: Dollar Signs470833
! Node: Case Sensitivity471119
! Node: VXT Fortran479735
! Node: Double Quote Meaning480918
! Node: Exclamation Point481846
! Node: Fortran 90482889
! Node: Pedantic Compilation483941
! Node: Distensions487905
! Node: Ugly Implicit Argument Conversion488869
! Node: Ugly Assumed-Size Arrays489483
! Node: Ugly Complex Part Extraction491204
! Node: Ugly Null Arguments492826
! Node: Ugly Conversion of Initializers494429
! Node: Ugly Integer Conversions496194
! Node: Ugly Assigned Labels497302
! Node: Compiler499233
! Node: Compiler Limits499871
! Node: Run-time Environment Limits500762
! Node: Timer Wraparounds502704
! Node: Year 2000 (Y2K) Problems503983
! Node: Array Size508489
! Node: Character-variable Length509674
! Node: Year 10000 (Y10K) Problems510183
! Node: Compiler Types510729
! Node: Compiler Constants515440
! Node: Compiler Intrinsics516299
! Node: Intrinsic Groups517226
! Node: Other Intrinsics520667
! Node: ACosD Intrinsic528265
! Node: AIMax0 Intrinsic528546
! Node: AIMin0 Intrinsic528855
! Node: AJMax0 Intrinsic529165
! Node: AJMin0 Intrinsic529475
! Node: ASinD Intrinsic529784
! Node: ATan2D Intrinsic530090
! Node: ATanD Intrinsic530398
! Node: BITest Intrinsic530704
! Node: BJTest Intrinsic531013
! Node: CDAbs Intrinsic531322
! Node: CDCos Intrinsic531695
! Node: CDExp Intrinsic532070
! Node: CDLog Intrinsic532445
! Node: CDSin Intrinsic532820
! Node: CDSqRt Intrinsic533196
! Node: ChDir Intrinsic (function)533589
! Node: ChMod Intrinsic (function)534417
! Node: CosD Intrinsic535530
! Node: DACosD Intrinsic535842
! Node: DASinD Intrinsic536150
! Node: DATan2D Intrinsic536461
! Node: DATanD Intrinsic536775
! Node: Date Intrinsic537084
! Node: DbleQ Intrinsic537803
! Node: DCmplx Intrinsic538107
! Node: DConjg Intrinsic539738
! Node: DCosD Intrinsic540123
! Node: DFloat Intrinsic540429
! Node: DFlotI Intrinsic540801
! Node: DFlotJ Intrinsic541111
! Node: DImag Intrinsic541420
! Node: DReal Intrinsic541797
! Node: DSinD Intrinsic542944
! Node: DTanD Intrinsic543248
! Node: DTime Intrinsic (function)543563
! Node: FGet Intrinsic (function)544793
! Node: FGetC Intrinsic (function)545566
! Node: FloatI Intrinsic546382
! Node: FloatJ Intrinsic546702
! Node: FPut Intrinsic (function)547021
! Node: FPutC Intrinsic (function)547757
! Node: IDate Intrinsic (VXT)548550
! Node: IIAbs Intrinsic549594
! Node: IIAnd Intrinsic549904
! Node: IIBClr Intrinsic550209
! Node: IIBits Intrinsic550518
! Node: IIBSet Intrinsic550828
! Node: IIDiM Intrinsic551137
! Node: IIDInt Intrinsic551443
! Node: IIDNnt Intrinsic551752
! Node: IIEOr Intrinsic552061
! Node: IIFix Intrinsic552366
! Node: IInt Intrinsic552669
! Node: IIOr Intrinsic552968
! Node: IIQint Intrinsic553268
! Node: IIQNnt Intrinsic553576
! Node: IIShftC Intrinsic553887
! Node: IISign Intrinsic554201
! Node: IMax0 Intrinsic554511
! Node: IMax1 Intrinsic554816
! Node: IMin0 Intrinsic555120
! Node: IMin1 Intrinsic555424
! Node: IMod Intrinsic555727
! Node: INInt Intrinsic556027
! Node: INot Intrinsic556329
! Node: IZExt Intrinsic556629
! Node: JIAbs Intrinsic556932
! Node: JIAnd Intrinsic557236
! Node: JIBClr Intrinsic557541
! Node: JIBits Intrinsic557850
! Node: JIBSet Intrinsic558160
! Node: JIDiM Intrinsic558469
! Node: JIDInt Intrinsic558775
! Node: JIDNnt Intrinsic559084
! Node: JIEOr Intrinsic559393
! Node: JIFix Intrinsic559698
! Node: JInt Intrinsic560001
! Node: JIOr Intrinsic560300
! Node: JIQint Intrinsic560600
! Node: JIQNnt Intrinsic560908
! Node: JIShft Intrinsic561218
! Node: JIShftC Intrinsic561529
! Node: JISign Intrinsic561843
! Node: JMax0 Intrinsic562153
! Node: JMax1 Intrinsic562458
! Node: JMin0 Intrinsic562762
! Node: JMin1 Intrinsic563066
! Node: JMod Intrinsic563369
! Node: JNInt Intrinsic563669
! Node: JNot Intrinsic563971
! Node: JZExt Intrinsic564271
! Node: Kill Intrinsic (function)564584
! Node: Link Intrinsic (function)565265
! Node: QAbs Intrinsic566076
! Node: QACos Intrinsic566386
! Node: QACosD Intrinsic566690
! Node: QASin Intrinsic566998
! Node: QASinD Intrinsic567304
! Node: QATan Intrinsic567612
! Node: QATan2 Intrinsic567918
! Node: QATan2D Intrinsic568228
! Node: QATanD Intrinsic568542
! Node: QCos Intrinsic568851
! Node: QCosD Intrinsic569152
! Node: QCosH Intrinsic569455
! Node: QDiM Intrinsic569758
! Node: QExp Intrinsic570057
! Node: QExt Intrinsic570355
! Node: QExtD Intrinsic570654
! Node: QFloat Intrinsic570958
! Node: QInt Intrinsic571265
! Node: QLog Intrinsic571565
! Node: QLog10 Intrinsic571865
! Node: QMax1 Intrinsic572172
! Node: QMin1 Intrinsic572477
! Node: QMod Intrinsic572780
! Node: QNInt Intrinsic573080
! Node: QSin Intrinsic573382
! Node: QSinD Intrinsic573682
! Node: QSinH Intrinsic573985
! Node: QSqRt Intrinsic574289
! Node: QTan Intrinsic574592
! Node: QTanD Intrinsic574892
! Node: QTanH Intrinsic575195
! Node: Rename Intrinsic (function)575511
! Node: Secnds Intrinsic576315
! Node: Signal Intrinsic (function)576914
! Node: SinD Intrinsic579743
! Node: SnglQ Intrinsic580055
! Node: SymLnk Intrinsic (function)580370
! Node: System Intrinsic (function)581237
! Node: TanD Intrinsic582564
! Node: Time Intrinsic (VXT)582881
! Node: UMask Intrinsic (function)583635
! Node: Unlink Intrinsic (function)584243
! Node: ZExt Intrinsic584971
! Node: Other Compilers585259
! Node: Dropping f2c Compatibility587779
! Node: Compilers Other Than f2c590851
! Node: Other Languages592649
! Node: Interoperating with C and C++592914
! Node: C Interfacing Tools593947
! Node: C Access to Type Information594875
! Node: f2c Skeletons and Prototypes595562
! Ref: f2c Skeletons and Prototypes-Footnote-1597009
! Node: C++ Considerations597263
! Node: Startup Code597930
! Node: Debugging and Interfacing602719
! Node: Main Program Unit605406
! Node: Procedures607900
! Node: Functions610558
! Node: Names612176
! Node: Common Blocks615319
! Node: Local Equivalence Areas615583
! Node: Complex Variables616567
! Node: Arrays617687
! Node: Adjustable Arrays621020
! Node: Alternate Entry Points623879
! Node: Alternate Returns630581
! Node: Assigned Statement Labels631482
! Node: Run-time Library Errors633327
! Node: Collected Fortran Wisdom635279
! Node: Advantages Over f2c636715
! Node: Language Extensions637696
! Node: Diagnostic Abilities638870
! Node: Compiler Options639261
! Node: Compiler Speed640309
! Node: Program Speed641019
! Node: Ease of Debugging642604
! Node: Character and Hollerith Constants645034
! Node: Block Data and Libraries646006
! Node: Loops649335
! Node: Working Programs654561
! Node: Not My Type655305
! Node: Variables Assumed To Be Zero657236
! Node: Variables Assumed To Be Saved658290
! Node: Unwanted Variables659660
! Node: Unused Arguments660540
! Node: Surprising Interpretations of Code661003
! Node: Aliasing Assumed To Work661850
! Node: Output Assumed To Flush668048
! Node: Large File Unit Numbers670821
! Node: Floating-point precision672973
! Node: Inconsistent Calling Sequences674234
! Node: Overly Convenient Options675214
! Node: Faster Programs678520
! Node: Aligned Data678966
! Node: Prefer Automatic Uninitialized Variables683843
! Node: Avoid f2c Compatibility685209
! Node: Use Submodel Options685677
! Node: Trouble686681
! Node: But-bugs688143
! Node: Signal 11 and Friends689916
! Node: Cannot Link Fortran Programs691996
! Node: Large Common Blocks693279
! Node: Debugger Problems693705
! Node: NeXTStep Problems694420
! Node: Stack Overflow696246
! Node: Nothing Happens699135
! Node: Strange Behavior at Run Time700749
! Node: Floating-point Errors703237
! Node: Known Bugs709531
! Node: Missing Features716820
! Node: Better Source Model718747
! Node: Fortran 90 Support720516
! Node: Intrinsics in PARAMETER Statements721617
! Node: Arbitrary Concatenation722368
! Node: SELECT CASE on CHARACTER Type722771
! Node: RECURSIVE Keyword723058
! Node: Increasing Precision/Range723485
! Node: Popular Non-standard Types725023
! Node: Full Support for Compiler Types725362
! Node: Array Bounds Expressions725998
! Node: POINTER Statements726445
! Node: Sensible Non-standard Constructs727328
! Node: READONLY Keyword729654
! Node: FLUSH Statement730564
! Node: Expressions in FORMAT Statements730934
! Node: Explicit Assembler Code732109
! Node: Q Edit Descriptor732398
! Node: Old-style PARAMETER Statements732902
! Node: TYPE and ACCEPT I/O Statements733636
! Node: STRUCTURE UNION RECORD MAP734202
! Node: OPEN CLOSE and INQUIRE Keywords734688
! Node: ENCODE and DECODE735668
! Node: AUTOMATIC Statement736763
! Node: Suppressing Space Padding738010
! Node: Fortran Preprocessor739237
! Node: Bit Operations on Floating-point Data739810
! Node: Really Ugly Character Assignments740343
! Node: POSIX Standard740718
! Node: Floating-point Exception Handling740958
! Node: Nonportable Conversions742360
! Node: Large Automatic Arrays742903
! Node: Support for Threads743310
! Node: Enabling Debug Lines743735
! Node: Better Warnings744112
! Node: Gracefully Handle Sensible Bad Code745748
! Node: Non-standard Conversions746492
! Node: Non-standard Intrinsics746835
! Node: Modifying DO Variable747251
! Node: Better Pedantic Compilation747927
! Node: Warn About Implicit Conversions748555
! Node: Invalid Use of Hollerith Constant749142
! Node: Dummy Array Without Dimensioning Dummy749685
! Node: Invalid FORMAT Specifiers750598
! Node: Ambiguous Dialects750999
! Node: Unused Labels751410
! Node: Informational Messages751632
! Node: Uninitialized Variables at Run Time752035
! Node: Portable Unformatted Files752641
! Ref: Portable Unformatted Files-Footnote-1755597
! Node: Better List-directed I/O755625
! Node: Default to Console I/O756530
! Node: Labels Visible to Debugger757178
! Node: Disappointments757579
! Node: Mangling of Names758217
! Node: Multiple Definitions of External Names759067
! Node: Limitation on Implicit Declarations760430
! Node: Non-bugs760714
! Node: Backslash in Constants761839
! Node: Initializing Before Specifying766728
! Node: Context-Sensitive Intrinsicness767870
! Node: Context-Sensitive Constants769766
! Node: Equivalence Versus Equality772722
! Node: Order of Side Effects775765
! Node: Warnings and Errors777493
! Node: Open Questions778891
! Node: Bugs779360
! Node: Bug Criteria780799
! Node: Bug Lists787032
! Node: Bug Reporting787821
! Node: Service801437
! Node: Adding Options801903
! Node: Projects806496
! Node: Efficiency807431
! Node: Better Optimization810328
! Node: Simplify Porting813698
! Node: More Extensions815453
! Node: Machine Model818541
! Node: Internals Documentation819827
! Node: Internals Improvements820134
! Node: Better Diagnostics823678
! Node: Front End824595
! Node: Overview of Sources825373
! Node: Overview of Translation Process832762
! Node: g77stripcard837040
! Node: lex.c839517
! Node: sta.c849057
! Node: sti.c849168
! Node: stq.c849279
! Node: stb.c849390
! Node: expr.c849502
! Node: stc.c849616
! Node: std.c849728
! Node: ste.c849839
! Node: Gotchas (Transforming)849967
! Node: TBD (Transforming)858086
! Node: Philosophy of Code Generation860782
! Node: Two-pass Design866686
! Node: Two-pass Code867843
! Node: Why Two Passes868576
! Node: Challenges Posed874644
! Node: Transforming Statements877128
! Node: Statements Needing Temporaries877978
! Node: Transforming DO WHILE880742
! Node: Transforming Iterative DO881925
! Node: Transforming Block IF882754
! Node: Transforming SELECT CASE884119
! Node: Transforming Expressions887341
! Node: Internal Naming Conventions889330
! Node: Diagnostics892329
! Node: CMPAMBIG893727
! Node: EXPIMP900144
! Node: INTGLOB901380
! Node: LEX903624
! Node: GLOBALS909079
! Node: LINKFAIL911743
! Node: Y2KBAD912367
! Node: Keyword Index912717
  
  End Tag Table
diff -Nrc3pad gcc-3.2.3/gcc/f/g77.info-1 gcc-3.3/gcc/f/g77.info-1
*** gcc-3.2.3/gcc/f/g77.info-1	2003-04-22 07:07:23.000000000 +0000
--- gcc-3.3/gcc/f/g77.info-1	1970-01-01 00:00:00.000000000 +0000
***************
*** 1,1007 ****
- This is g77.info, produced by makeinfo version 4.5 from g77.texi.
- 
- INFO-DIR-SECTION Programming
- START-INFO-DIR-ENTRY
- * g77: (g77).                  The GNU Fortran compiler.
- END-INFO-DIR-ENTRY
-    This file documents the use and the internals of the GNU Fortran
- (`g77') compiler.  It corresponds to the GCC-3.2.3 version of `g77'.
- 
-    Published by the Free Software Foundation 59 Temple Place - Suite 330
- Boston, MA 02111-1307 USA
- 
-    Copyright (C) 1995,1996,1997,1998,1999,2000,2001,2002 Free Software
- Foundation, Inc.
- 
-    Permission is granted to copy, distribute and/or modify this document
- under the terms of the GNU Free Documentation License, Version 1.1 or
- any later version published by the Free Software Foundation; with the
- Invariant Sections being "GNU General Public License" and "Funding Free
- Software", the Front-Cover texts being (a) (see below), and with the
- Back-Cover Texts being (b) (see below).  A copy of the license is
- included in the section entitled "GNU Free Documentation License".
- 
-    (a) The FSF's Front-Cover Text is:
- 
-    A GNU Manual
- 
-    (b) The FSF's Back-Cover Text is:
- 
-    You have freedom to copy and modify this GNU Manual, like GNU
- software.  Copies published by the Free Software Foundation raise
- funds for GNU development.
- 
-    Contributed by James Craig Burley (<craig@jcb-sc.com>).  Inspired by
- a first pass at translating `g77-0.5.16/f/DOC' that was contributed to
- Craig by David Ronis (<ronis@onsager.chem.mcgill.ca>).
- 
- 
- File: g77.info,  Node: Top,  Next: Copying,  Up: (DIR)
- 
- Introduction
- ************
- 
-    This manual documents how to run, install and port `g77', as well as
- its new features and incompatibilities, and how to report bugs.  It
- corresponds to the GCC-3.2.3 version of `g77'.
- 
- * Menu:
- 
- * Copying::         GNU General Public License says
-                     how you can copy and share GNU Fortran.
- * GNU Free Documentation License::
- 		    How you can copy and share this manual.
- * Contributors::    People who have contributed to GNU Fortran.
- * Funding::         How to help assure continued work for free software.
- * Funding GNU Fortran::  How to help assure continued work on GNU Fortran.
- 
- * Getting Started:: Finding your way around this manual.
- * What is GNU Fortran?::  How `g77' fits into the universe.
- * G77 and GCC::     You can compile Fortran, C, or other programs.
- * Invoking G77::    Command options supported by `g77'.
- * News::            News about recent releases of `g77'.
- * Changes::         User-visible changes to recent releases of `g77'.
- * Language::        The GNU Fortran language.
- * Compiler::        The GNU Fortran compiler.
- * Other Dialects::  Dialects of Fortran supported by `g77'.
- * Other Compilers:: Fortran compilers other than `g77'.
- * Other Languages:: Languages other than Fortran.
- * Debugging and Interfacing::  How `g77' generates code.
- * Collected Fortran Wisdom::  How to avoid Trouble.
- * Trouble::         If you have trouble with GNU Fortran.
- * Open Questions::  Things we'd like to know.
- * Bugs::            How, why, and where to report bugs.
- * Service::         How to find suppliers of support for GNU Fortran.
- 
- * Adding Options::  Guidance on teaching `g77' about new options.
- * Projects::        Projects for `g77' internals hackers.
- * Front End::       Design and implementation of the `g77' front end.
- 
- * M: Diagnostics.   Diagnostics produced by `g77'.
- 
- * Index::           Index of concepts and symbol names.
- 
- 
- File: g77.info,  Node: Copying,  Next: GNU Free Documentation License,  Prev: Top,  Up: Top
- 
- GNU GENERAL PUBLIC LICENSE
- **************************
- 
-                          Version 2, June 1991
-      Copyright (C) 1989, 1991 Free Software Foundation, Inc.
-      59 Temple Place - Suite 330, Boston, MA 02111-1307, USA
-      
-      Everyone is permitted to copy and distribute verbatim copies
-      of this license document, but changing it is not allowed.
- 
- Preamble
- ========
- 
-    The licenses for most software are designed to take away your
- freedom to share and change it.  By contrast, the GNU General Public
- License is intended to guarantee your freedom to share and change free
- software--to make sure the software is free for all its users.  This
- General Public License applies to most of the Free Software
- Foundation's software and to any other program whose authors commit to
- using it.  (Some other Free Software Foundation software is covered by
- the GNU Library General Public License instead.)  You can apply it to
- your programs, too.
- 
-    When we speak of free software, we are referring to freedom, not
- price.  Our General Public Licenses are designed to make sure that you
- have the freedom to distribute copies of free software (and charge for
- this service if you wish), that you receive source code or can get it
- if you want it, that you can change the software or use pieces of it in
- new free programs; and that you know you can do these things.
- 
-    To protect your rights, we need to make restrictions that forbid
- anyone to deny you these rights or to ask you to surrender the rights.
- These restrictions translate to certain responsibilities for you if you
- distribute copies of the software, or if you modify it.
- 
-    For example, if you distribute copies of such a program, whether
- gratis or for a fee, you must give the recipients all the rights that
- you have.  You must make sure that they, too, receive or can get the
- source code.  And you must show them these terms so they know their
- rights.
- 
-    We protect your rights with two steps: (1) copyright the software,
- and (2) offer you this license which gives you legal permission to copy,
- distribute and/or modify the software.
- 
-    Also, for each author's protection and ours, we want to make certain
- that everyone understands that there is no warranty for this free
- software.  If the software is modified by someone else and passed on, we
- want its recipients to know that what they have is not the original, so
- that any problems introduced by others will not reflect on the original
- authors' reputations.
- 
-    Finally, any free program is threatened constantly by software
- patents.  We wish to avoid the danger that redistributors of a free
- program will individually obtain patent licenses, in effect making the
- program proprietary.  To prevent this, we have made it clear that any
- patent must be licensed for everyone's free use or not licensed at all.
- 
-    The precise terms and conditions for copying, distribution and
- modification follow.
- 
-     TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
-   0. This License applies to any program or other work which contains a
-      notice placed by the copyright holder saying it may be distributed
-      under the terms of this General Public License.  The "Program",
-      below, refers to any such program or work, and a "work based on
-      the Program" means either the Program or any derivative work under
-      copyright law: that is to say, a work containing the Program or a
-      portion of it, either verbatim or with modifications and/or
-      translated into another language.  (Hereinafter, translation is
-      included without limitation in the term "modification".)  Each
-      licensee is addressed as "you".
- 
-      Activities other than copying, distribution and modification are
-      not covered by this License; they are outside its scope.  The act
-      of running the Program is not restricted, and the output from the
-      Program is covered only if its contents constitute a work based on
-      the Program (independent of having been made by running the
-      Program).  Whether that is true depends on what the Program does.
- 
-   1. You may copy and distribute verbatim copies of the Program's
-      source code as you receive it, in any medium, provided that you
-      conspicuously and appropriately publish on each copy an appropriate
-      copyright notice and disclaimer of warranty; keep intact all the
-      notices that refer to this License and to the absence of any
-      warranty; and give any other recipients of the Program a copy of
-      this License along with the Program.
- 
-      You may charge a fee for the physical act of transferring a copy,
-      and you may at your option offer warranty protection in exchange
-      for a fee.
- 
-   2. You may modify your copy or copies of the Program or any portion
-      of it, thus forming a work based on the Program, and copy and
-      distribute such modifications or work under the terms of Section 1
-      above, provided that you also meet all of these conditions:
- 
-        a. You must cause the modified files to carry prominent notices
-           stating that you changed the files and the date of any change.
- 
-        b. You must cause any work that you distribute or publish, that
-           in whole or in part contains or is derived from the Program
-           or any part thereof, to be licensed as a whole at no charge
-           to all third parties under the terms of this License.
- 
-        c. If the modified program normally reads commands interactively
-           when run, you must cause it, when started running for such
-           interactive use in the most ordinary way, to print or display
-           an announcement including an appropriate copyright notice and
-           a notice that there is no warranty (or else, saying that you
-           provide a warranty) and that users may redistribute the
-           program under these conditions, and telling the user how to
-           view a copy of this License.  (Exception: if the Program
-           itself is interactive but does not normally print such an
-           announcement, your work based on the Program is not required
-           to print an announcement.)
- 
-      These requirements apply to the modified work as a whole.  If
-      identifiable sections of that work are not derived from the
-      Program, and can be reasonably considered independent and separate
-      works in themselves, then this License, and its terms, do not
-      apply to those sections when you distribute them as separate
-      works.  But when you distribute the same sections as part of a
-      whole which is a work based on the Program, the distribution of
-      the whole must be on the terms of this License, whose permissions
-      for other licensees extend to the entire whole, and thus to each
-      and every part regardless of who wrote it.
- 
-      Thus, it is not the intent of this section to claim rights or
-      contest your rights to work written entirely by you; rather, the
-      intent is to exercise the right to control the distribution of
-      derivative or collective works based on the Program.
- 
-      In addition, mere aggregation of another work not based on the
-      Program with the Program (or with a work based on the Program) on
-      a volume of a storage or distribution medium does not bring the
-      other work under the scope of this License.
- 
-   3. You may copy and distribute the Program (or a work based on it,
-      under Section 2) in object code or executable form under the terms
-      of Sections 1 and 2 above provided that you also do one of the
-      following:
- 
-        a. Accompany it with the complete corresponding machine-readable
-           source code, which must be distributed under the terms of
-           Sections 1 and 2 above on a medium customarily used for
-           software interchange; or,
- 
-        b. Accompany it with a written offer, valid for at least three
-           years, to give any third party, for a charge no more than your
-           cost of physically performing source distribution, a complete
-           machine-readable copy of the corresponding source code, to be
-           distributed under the terms of Sections 1 and 2 above on a
-           medium customarily used for software interchange; or,
- 
-        c. Accompany it with the information you received as to the offer
-           to distribute corresponding source code.  (This alternative is
-           allowed only for noncommercial distribution and only if you
-           received the program in object code or executable form with
-           such an offer, in accord with Subsection b above.)
- 
-      The source code for a work means the preferred form of the work for
-      making modifications to it.  For an executable work, complete
-      source code means all the source code for all modules it contains,
-      plus any associated interface definition files, plus the scripts
-      used to control compilation and installation of the executable.
-      However, as a special exception, the source code distributed need
-      not include anything that is normally distributed (in either
-      source or binary form) with the major components (compiler,
-      kernel, and so on) of the operating system on which the executable
-      runs, unless that component itself accompanies the executable.
- 
-      If distribution of executable or object code is made by offering
-      access to copy from a designated place, then offering equivalent
-      access to copy the source code from the same place counts as
-      distribution of the source code, even though third parties are not
-      compelled to copy the source along with the object code.
- 
-   4. You may not copy, modify, sublicense, or distribute the Program
-      except as expressly provided under this License.  Any attempt
-      otherwise to copy, modify, sublicense or distribute the Program is
-      void, and will automatically terminate your rights under this
-      License.  However, parties who have received copies, or rights,
-      from you under this License will not have their licenses
-      terminated so long as such parties remain in full compliance.
- 
-   5. You are not required to accept this License, since you have not
-      signed it.  However, nothing else grants you permission to modify
-      or distribute the Program or its derivative works.  These actions
-      are prohibited by law if you do not accept this License.
-      Therefore, by modifying or distributing the Program (or any work
-      based on the Program), you indicate your acceptance of this
-      License to do so, and all its terms and conditions for copying,
-      distributing or modifying the Program or works based on it.
- 
-   6. Each time you redistribute the Program (or any work based on the
-      Program), the recipient automatically receives a license from the
-      original licensor to copy, distribute or modify the Program
-      subject to these terms and conditions.  You may not impose any
-      further restrictions on the recipients' exercise of the rights
-      granted herein.  You are not responsible for enforcing compliance
-      by third parties to this License.
- 
-   7. If, as a consequence of a court judgment or allegation of patent
-      infringement or for any other reason (not limited to patent
-      issues), conditions are imposed on you (whether by court order,
-      agreement or otherwise) that contradict the conditions of this
-      License, they do not excuse you from the conditions of this
-      License.  If you cannot distribute so as to satisfy simultaneously
-      your obligations under this License and any other pertinent
-      obligations, then as a consequence you may not distribute the
-      Program at all.  For example, if a patent license would not permit
-      royalty-free redistribution of the Program by all those who
-      receive copies directly or indirectly through you, then the only
-      way you could satisfy both it and this License would be to refrain
-      entirely from distribution of the Program.
- 
-      If any portion of this section is held invalid or unenforceable
-      under any particular circumstance, the balance of the section is
-      intended to apply and the section as a whole is intended to apply
-      in other circumstances.
- 
-      It is not the purpose of this section to induce you to infringe any
-      patents or other property right claims or to contest validity of
-      any such claims; this section has the sole purpose of protecting
-      the integrity of the free software distribution system, which is
-      implemented by public license practices.  Many people have made
-      generous contributions to the wide range of software distributed
-      through that system in reliance on consistent application of that
-      system; it is up to the author/donor to decide if he or she is
-      willing to distribute software through any other system and a
-      licensee cannot impose that choice.
- 
-      This section is intended to make thoroughly clear what is believed
-      to be a consequence of the rest of this License.
- 
-   8. If the distribution and/or use of the Program is restricted in
-      certain countries either by patents or by copyrighted interfaces,
-      the original copyright holder who places the Program under this
-      License may add an explicit geographical distribution limitation
-      excluding those countries, so that distribution is permitted only
-      in or among countries not thus excluded.  In such case, this
-      License incorporates the limitation as if written in the body of
-      this License.
- 
-   9. The Free Software Foundation may publish revised and/or new
-      versions of the General Public License from time to time.  Such
-      new versions will be similar in spirit to the present version, but
-      may differ in detail to address new problems or concerns.
- 
-      Each version is given a distinguishing version number.  If the
-      Program specifies a version number of this License which applies
-      to it and "any later version", you have the option of following
-      the terms and conditions either of that version or of any later
-      version published by the Free Software Foundation.  If the Program
-      does not specify a version number of this License, you may choose
-      any version ever published by the Free Software Foundation.
- 
-  10. If you wish to incorporate parts of the Program into other free
-      programs whose distribution conditions are different, write to the
-      author to ask for permission.  For software which is copyrighted
-      by the Free Software Foundation, write to the Free Software
-      Foundation; we sometimes make exceptions for this.  Our decision
-      will be guided by the two goals of preserving the free status of
-      all derivatives of our free software and of promoting the sharing
-      and reuse of software generally.
- 
-                                 NO WARRANTY
- 
-  11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO
-      WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE
-      LAW.  EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
-      HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT
-      WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT
-      NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
-      FITNESS FOR A PARTICULAR PURPOSE.  THE ENTIRE RISK AS TO THE
-      QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.  SHOULD THE
-      PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY
-      SERVICING, REPAIR OR CORRECTION.
- 
-  12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN
-      WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY
-      MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE
-      LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL,
-      INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR
-      INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
-      DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU
-      OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY
-      OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN
-      ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
- 
-                       END OF TERMS AND CONDITIONS
- 
- How to Apply These Terms to Your New Programs
- =============================================
- 
-    If you develop a new program, and you want it to be of the greatest
- possible use to the public, the best way to achieve this is to make it
- free software which everyone can redistribute and change under these
- terms.
- 
-    To do so, attach the following notices to the program.  It is safest
- to attach them to the start of each source file to most effectively
- convey the exclusion of warranty; and each file should have at least
- the "copyright" line and a pointer to where the full notice is found.
- 
-      ONE LINE TO GIVE THE PROGRAM'S NAME AND A BRIEF IDEA OF WHAT IT DOES.
-      Copyright (C) YEAR  NAME OF AUTHOR
-      
-      This program is free software; you can redistribute it and/or modify
-      it under the terms of the GNU General Public License as published by
-      the Free Software Foundation; either version 2 of the License, or
-      (at your option) any later version.
-      
-      This program is distributed in the hope that it will be useful,
-      but WITHOUT ANY WARRANTY; without even the implied warranty of
-      MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
-      GNU General Public License for more details.
-      
-      You should have received a copy of the GNU General Public License
-      along with this program; if not, write to the Free Software
-      Foundation, Inc., 59 Temple Place - Suite 330,
-      Boston, MA 02111-1307, USA.
- 
-    Also add information on how to contact you by electronic and paper
- mail.
- 
-    If the program is interactive, make it output a short notice like
- this when it starts in an interactive mode:
- 
-      Gnomovision version 69, Copyright (C) YEAR NAME OF AUTHOR
-      Gnomovision comes with ABSOLUTELY NO WARRANTY; for details
-      type `show w'.
-      This is free software, and you are welcome to redistribute it
-      under certain conditions; type `show c' for details.
- 
-    The hypothetical commands `show w' and `show c' should show the
- appropriate parts of the General Public License.  Of course, the
- commands you use may be called something other than `show w' and `show
- c'; they could even be mouse-clicks or menu items--whatever suits your
- program.
- 
-    You should also get your employer (if you work as a programmer) or
- your school, if any, to sign a "copyright disclaimer" for the program,
- if necessary.  Here is a sample; alter the names:
- 
-      Yoyodyne, Inc., hereby disclaims all copyright interest in the program
-      `Gnomovision' (which makes passes at compilers) written by James Hacker.
-      
-      SIGNATURE OF TY COON, 1 April 1989
-      Ty Coon, President of Vice
- 
-    This General Public License does not permit incorporating your
- program into proprietary programs.  If your program is a subroutine
- library, you may consider it more useful to permit linking proprietary
- applications with the library.  If this is what you want to do, use the
- GNU Library General Public License instead of this License.
- 
- 
- File: g77.info,  Node: GNU Free Documentation License,  Next: Contributors,  Prev: Copying,  Up: Top
- 
- GNU Free Documentation License
- ******************************
- 
-                         Version 1.1, March 2000
-      Copyright (C) 2000 Free Software Foundation, Inc.
-      59 Temple Place, Suite 330, Boston, MA  02111-1307, USA
-      
-      Everyone is permitted to copy and distribute verbatim copies
-      of this license document, but changing it is not allowed.
- 
-   0. PREAMBLE
- 
-      The purpose of this License is to make a manual, textbook, or other
-      written document "free" in the sense of freedom: to assure everyone
-      the effective freedom to copy and redistribute it, with or without
-      modifying it, either commercially or noncommercially.  Secondarily,
-      this License preserves for the author and publisher a way to get
-      credit for their work, while not being considered responsible for
-      modifications made by others.
- 
-      This License is a kind of "copyleft", which means that derivative
-      works of the document must themselves be free in the same sense.
-      It complements the GNU General Public License, which is a copyleft
-      license designed for free software.
- 
-      We have designed this License in order to use it for manuals for
-      free software, because free software needs free documentation: a
-      free program should come with manuals providing the same freedoms
-      that the software does.  But this License is not limited to
-      software manuals; it can be used for any textual work, regardless
-      of subject matter or whether it is published as a printed book.
-      We recommend this License principally for works whose purpose is
-      instruction or reference.
- 
-   1. APPLICABILITY AND DEFINITIONS
- 
-      This License applies to any manual or other work that contains a
-      notice placed by the copyright holder saying it can be distributed
-      under the terms of this License.  The "Document", below, refers to
-      any such manual or work.  Any member of the public is a licensee,
-      and is addressed as "you".
- 
-      A "Modified Version" of the Document means any work containing the
-      Document or a portion of it, either copied verbatim, or with
-      modifications and/or translated into another language.
- 
-      A "Secondary Section" is a named appendix or a front-matter
-      section of the Document that deals exclusively with the
-      relationship of the publishers or authors of the Document to the
-      Document's overall subject (or to related matters) and contains
-      nothing that could fall directly within that overall subject.
-      (For example, if the Document is in part a textbook of
-      mathematics, a Secondary Section may not explain any mathematics.)
-      The relationship could be a matter of historical connection with
-      the subject or with related matters, or of legal, commercial,
-      philosophical, ethical or political position regarding them.
- 
-      The "Invariant Sections" are certain Secondary Sections whose
-      titles are designated, as being those of Invariant Sections, in
-      the notice that says that the Document is released under this
-      License.
- 
-      The "Cover Texts" are certain short passages of text that are
-      listed, as Front-Cover Texts or Back-Cover Texts, in the notice
-      that says that the Document is released under this License.
- 
-      A "Transparent" copy of the Document means a machine-readable copy,
-      represented in a format whose specification is available to the
-      general public, whose contents can be viewed and edited directly
-      and straightforwardly with generic text editors or (for images
-      composed of pixels) generic paint programs or (for drawings) some
-      widely available drawing editor, and that is suitable for input to
-      text formatters or for automatic translation to a variety of
-      formats suitable for input to text formatters.  A copy made in an
-      otherwise Transparent file format whose markup has been designed
-      to thwart or discourage subsequent modification by readers is not
-      Transparent.  A copy that is not "Transparent" is called "Opaque".
- 
-      Examples of suitable formats for Transparent copies include plain
-      ASCII without markup, Texinfo input format, LaTeX input format,
-      SGML or XML using a publicly available DTD, and
-      standard-conforming simple HTML designed for human modification.
-      Opaque formats include PostScript, PDF, proprietary formats that
-      can be read and edited only by proprietary word processors, SGML
-      or XML for which the DTD and/or processing tools are not generally
-      available, and the machine-generated HTML produced by some word
-      processors for output purposes only.
- 
-      The "Title Page" means, for a printed book, the title page itself,
-      plus such following pages as are needed to hold, legibly, the
-      material this License requires to appear in the title page.  For
-      works in formats which do not have any title page as such, "Title
-      Page" means the text near the most prominent appearance of the
-      work's title, preceding the beginning of the body of the text.
- 
-   2. VERBATIM COPYING
- 
-      You may copy and distribute the Document in any medium, either
-      commercially or noncommercially, provided that this License, the
-      copyright notices, and the license notice saying this License
-      applies to the Document are reproduced in all copies, and that you
-      add no other conditions whatsoever to those of this License.  You
-      may not use technical measures to obstruct or control the reading
-      or further copying of the copies you make or distribute.  However,
-      you may accept compensation in exchange for copies.  If you
-      distribute a large enough number of copies you must also follow
-      the conditions in section 3.
- 
-      You may also lend copies, under the same conditions stated above,
-      and you may publicly display copies.
- 
-   3. COPYING IN QUANTITY
- 
-      If you publish printed copies of the Document numbering more than
-      100, and the Document's license notice requires Cover Texts, you
-      must enclose the copies in covers that carry, clearly and legibly,
-      all these Cover Texts: Front-Cover Texts on the front cover, and
-      Back-Cover Texts on the back cover.  Both covers must also clearly
-      and legibly identify you as the publisher of these copies.  The
-      front cover must present the full title with all words of the
-      title equally prominent and visible.  You may add other material
-      on the covers in addition.  Copying with changes limited to the
-      covers, as long as they preserve the title of the Document and
-      satisfy these conditions, can be treated as verbatim copying in
-      other respects.
- 
-      If the required texts for either cover are too voluminous to fit
-      legibly, you should put the first ones listed (as many as fit
-      reasonably) on the actual cover, and continue the rest onto
-      adjacent pages.
- 
-      If you publish or distribute Opaque copies of the Document
-      numbering more than 100, you must either include a
-      machine-readable Transparent copy along with each Opaque copy, or
-      state in or with each Opaque copy a publicly-accessible
-      computer-network location containing a complete Transparent copy
-      of the Document, free of added material, which the general
-      network-using public has access to download anonymously at no
-      charge using public-standard network protocols.  If you use the
-      latter option, you must take reasonably prudent steps, when you
-      begin distribution of Opaque copies in quantity, to ensure that
-      this Transparent copy will remain thus accessible at the stated
-      location until at least one year after the last time you
-      distribute an Opaque copy (directly or through your agents or
-      retailers) of that edition to the public.
- 
-      It is requested, but not required, that you contact the authors of
-      the Document well before redistributing any large number of
-      copies, to give them a chance to provide you with an updated
-      version of the Document.
- 
-   4. MODIFICATIONS
- 
-      You may copy and distribute a Modified Version of the Document
-      under the conditions of sections 2 and 3 above, provided that you
-      release the Modified Version under precisely this License, with
-      the Modified Version filling the role of the Document, thus
-      licensing distribution and modification of the Modified Version to
-      whoever possesses a copy of it.  In addition, you must do these
-      things in the Modified Version:
- 
-        A. Use in the Title Page (and on the covers, if any) a title
-           distinct from that of the Document, and from those of
-           previous versions (which should, if there were any, be listed
-           in the History section of the Document).  You may use the
-           same title as a previous version if the original publisher of
-           that version gives permission.
- 
-        B. List on the Title Page, as authors, one or more persons or
-           entities responsible for authorship of the modifications in
-           the Modified Version, together with at least five of the
-           principal authors of the Document (all of its principal
-           authors, if it has less than five).
- 
-        C. State on the Title page the name of the publisher of the
-           Modified Version, as the publisher.
- 
-        D. Preserve all the copyright notices of the Document.
- 
-        E. Add an appropriate copyright notice for your modifications
-           adjacent to the other copyright notices.
- 
-        F. Include, immediately after the copyright notices, a license
-           notice giving the public permission to use the Modified
-           Version under the terms of this License, in the form shown in
-           the Addendum below.
- 
-        G. Preserve in that license notice the full lists of Invariant
-           Sections and required Cover Texts given in the Document's
-           license notice.
- 
-        H. Include an unaltered copy of this License.
- 
-        I. Preserve the section entitled "History", and its title, and
-           add to it an item stating at least the title, year, new
-           authors, and publisher of the Modified Version as given on
-           the Title Page.  If there is no section entitled "History" in
-           the Document, create one stating the title, year, authors,
-           and publisher of the Document as given on its Title Page,
-           then add an item describing the Modified Version as stated in
-           the previous sentence.
- 
-        J. Preserve the network location, if any, given in the Document
-           for public access to a Transparent copy of the Document, and
-           likewise the network locations given in the Document for
-           previous versions it was based on.  These may be placed in
-           the "History" section.  You may omit a network location for a
-           work that was published at least four years before the
-           Document itself, or if the original publisher of the version
-           it refers to gives permission.
- 
-        K. In any section entitled "Acknowledgments" or "Dedications",
-           preserve the section's title, and preserve in the section all
-           the substance and tone of each of the contributor
-           acknowledgments and/or dedications given therein.
- 
-        L. Preserve all the Invariant Sections of the Document,
-           unaltered in their text and in their titles.  Section numbers
-           or the equivalent are not considered part of the section
-           titles.
- 
-        M. Delete any section entitled "Endorsements".  Such a section
-           may not be included in the Modified Version.
- 
-        N. Do not retitle any existing section as "Endorsements" or to
-           conflict in title with any Invariant Section.
- 
-      If the Modified Version includes new front-matter sections or
-      appendices that qualify as Secondary Sections and contain no
-      material copied from the Document, you may at your option
-      designate some or all of these sections as invariant.  To do this,
-      add their titles to the list of Invariant Sections in the Modified
-      Version's license notice.  These titles must be distinct from any
-      other section titles.
- 
-      You may add a section entitled "Endorsements", provided it contains
-      nothing but endorsements of your Modified Version by various
-      parties--for example, statements of peer review or that the text
-      has been approved by an organization as the authoritative
-      definition of a standard.
- 
-      You may add a passage of up to five words as a Front-Cover Text,
-      and a passage of up to 25 words as a Back-Cover Text, to the end
-      of the list of Cover Texts in the Modified Version.  Only one
-      passage of Front-Cover Text and one of Back-Cover Text may be
-      added by (or through arrangements made by) any one entity.  If the
-      Document already includes a cover text for the same cover,
-      previously added by you or by arrangement made by the same entity
-      you are acting on behalf of, you may not add another; but you may
-      replace the old one, on explicit permission from the previous
-      publisher that added the old one.
- 
-      The author(s) and publisher(s) of the Document do not by this
-      License give permission to use their names for publicity for or to
-      assert or imply endorsement of any Modified Version.
- 
-   5. COMBINING DOCUMENTS
- 
-      You may combine the Document with other documents released under
-      this License, under the terms defined in section 4 above for
-      modified versions, provided that you include in the combination
-      all of the Invariant Sections of all of the original documents,
-      unmodified, and list them all as Invariant Sections of your
-      combined work in its license notice.
- 
-      The combined work need only contain one copy of this License, and
-      multiple identical Invariant Sections may be replaced with a single
-      copy.  If there are multiple Invariant Sections with the same name
-      but different contents, make the title of each such section unique
-      by adding at the end of it, in parentheses, the name of the
-      original author or publisher of that section if known, or else a
-      unique number.  Make the same adjustment to the section titles in
-      the list of Invariant Sections in the license notice of the
-      combined work.
- 
-      In the combination, you must combine any sections entitled
-      "History" in the various original documents, forming one section
-      entitled "History"; likewise combine any sections entitled
-      "Acknowledgments", and any sections entitled "Dedications".  You
-      must delete all sections entitled "Endorsements."
- 
-   6. COLLECTIONS OF DOCUMENTS
- 
-      You may make a collection consisting of the Document and other
-      documents released under this License, and replace the individual
-      copies of this License in the various documents with a single copy
-      that is included in the collection, provided that you follow the
-      rules of this License for verbatim copying of each of the
-      documents in all other respects.
- 
-      You may extract a single document from such a collection, and
-      distribute it individually under this License, provided you insert
-      a copy of this License into the extracted document, and follow
-      this License in all other respects regarding verbatim copying of
-      that document.
- 
-   7. AGGREGATION WITH INDEPENDENT WORKS
- 
-      A compilation of the Document or its derivatives with other
-      separate and independent documents or works, in or on a volume of
-      a storage or distribution medium, does not as a whole count as a
-      Modified Version of the Document, provided no compilation
-      copyright is claimed for the compilation.  Such a compilation is
-      called an "aggregate", and this License does not apply to the
-      other self-contained works thus compiled with the Document, on
-      account of their being thus compiled, if they are not themselves
-      derivative works of the Document.
- 
-      If the Cover Text requirement of section 3 is applicable to these
-      copies of the Document, then if the Document is less than one
-      quarter of the entire aggregate, the Document's Cover Texts may be
-      placed on covers that surround only the Document within the
-      aggregate.  Otherwise they must appear on covers around the whole
-      aggregate.
- 
-   8. TRANSLATION
- 
-      Translation is considered a kind of modification, so you may
-      distribute translations of the Document under the terms of section
-      4.  Replacing Invariant Sections with translations requires special
-      permission from their copyright holders, but you may include
-      translations of some or all Invariant Sections in addition to the
-      original versions of these Invariant Sections.  You may include a
-      translation of this License provided that you also include the
-      original English version of this License.  In case of a
-      disagreement between the translation and the original English
-      version of this License, the original English version will prevail.
- 
-   9. TERMINATION
- 
-      You may not copy, modify, sublicense, or distribute the Document
-      except as expressly provided for under this License.  Any other
-      attempt to copy, modify, sublicense or distribute the Document is
-      void, and will automatically terminate your rights under this
-      License.  However, parties who have received copies, or rights,
-      from you under this License will not have their licenses
-      terminated so long as such parties remain in full compliance.
- 
-  10. FUTURE REVISIONS OF THIS LICENSE
- 
-      The Free Software Foundation may publish new, revised versions of
-      the GNU Free Documentation License from time to time.  Such new
-      versions will be similar in spirit to the present version, but may
-      differ in detail to address new problems or concerns.  See
-      `http://www.gnu.org/copyleft/'.
- 
-      Each version of the License is given a distinguishing version
-      number.  If the Document specifies that a particular numbered
-      version of this License "or any later version" applies to it, you
-      have the option of following the terms and conditions either of
-      that specified version or of any later version that has been
-      published (not as a draft) by the Free Software Foundation.  If
-      the Document does not specify a version number of this License,
-      you may choose any version ever published (not as a draft) by the
-      Free Software Foundation.
- 
- ADDENDUM: How to use this License for your documents
- ====================================================
- 
-    To use this License in a document you have written, include a copy of
- the License in the document and put the following copyright and license
- notices just after the title page:
- 
-        Copyright (C)  YEAR  YOUR NAME.
-        Permission is granted to copy, distribute and/or modify this document
-        under the terms of the GNU Free Documentation License, Version 1.1
-        or any later version published by the Free Software Foundation;
-        with the Invariant Sections being LIST THEIR TITLES, with the
-        Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST.
-        A copy of the license is included in the section entitled ``GNU
-        Free Documentation License''.
- 
-    If you have no Invariant Sections, write "with no Invariant Sections"
- instead of saying which ones are invariant.  If you have no Front-Cover
- Texts, write "no Front-Cover Texts" instead of "Front-Cover Texts being
- LIST"; likewise for Back-Cover Texts.
- 
-    If your document contains nontrivial examples of program code, we
- recommend releasing these examples in parallel under your choice of
- free software license, such as the GNU General Public License, to
- permit their use in free software.
- 
- 
- File: g77.info,  Node: Contributors,  Next: Funding,  Prev: GNU Free Documentation License,  Up: Top
- 
- Contributors to GNU Fortran
- ***************************
- 
-    In addition to James Craig Burley, who wrote the front end, many
- people have helped create and improve GNU Fortran.
- 
-    * The packaging and compiler portions of GNU Fortran are based
-      largely on the GNU CC compiler.  *Note Contributors to GCC:
-      (gcc)Contributors, for more information.
- 
-    * The run-time library used by GNU Fortran is a repackaged version
-      of the `libf2c' library (combined from the `libF77' and `libI77'
-      libraries) provided as part of `f2c', available for free from
-      `netlib' sites on the Internet.
- 
-    * Cygnus Support and The Free Software Foundation contributed
-      significant money and/or equipment to Craig's efforts.
- 
-    * The following individuals served as alpha testers prior to `g77''s
-      public release.  This work consisted of testing, researching,
-      sometimes debugging, and occasionally providing small amounts of
-      code and fixes for `g77', plus offering plenty of helpful advice
-      to Craig:
- 
-           Jonathan Corbet
- 
-           Dr. Mark Fernyhough
- 
-           Takafumi Hayashi (The University of
-           Aizu)--<takafumi@u-aizu.ac.jp>
- 
-           Kate Hedstrom
- 
-           Michel Kern (INRIA and Rice
-           University)--<Michel.Kern@inria.fr>
- 
-           Dr. A. O. V. Le Blanc
- 
-           Dave Love
- 
-           Rick Lutowski
- 
-           Toon Moene
- 
-           Rick Niles
- 
-           Derk Reefman
- 
-           Wayne K. Schroll
- 
-           Bill Thorson
- 
-           Pedro A. M. Vazquez
- 
-           Ian Watson
- 
-    * Dave Love (<d.love@dl.ac.uk>) wrote the libU77 part of the
-      run-time library.
- 
-    * Scott Snyder (<snyder@d0sgif.fnal.gov>) provided the patch to add
-      rudimentary support for `INTEGER*1', `INTEGER*2', and `LOGICAL*1'.
-      This inspired Craig to add further support, even though the
-      resulting support would still be incomplete.
- 
-    * David Ronis (<ronis@onsager.chem.mcgill.ca>) inspired and
-      encouraged Craig to rewrite the documentation in texinfo format by
-      contributing a first pass at a translation of the old
-      `g77-0.5.16/f/DOC' file.
- 
-    * Toon Moene (<toon@moene.indiv.nluug.nl>) performed some analysis
-      of generated code as part of an overall project to improve `g77'
-      code generation to at least be as good as `f2c' used in
-      conjunction with `gcc'.  So far, this has resulted in the three,
-      somewhat experimental, options added by `g77' to the `gcc'
-      compiler and its back end.
- 
-      (These, in turn, had made their way into the `egcs' version of the
-      compiler, and do not exist in `gcc' version 2.8 or versions of
-      `g77' based on that version of `gcc'.)
- 
-    * John Carr (<jfc@mit.edu>) wrote the alias analysis improvements.
- 
-    * Thanks to Mary Cortani and the staff at Craftwork Solutions
-      (<support@craftwork.com>) for all of their support.
- 
-    * Many other individuals have helped debug, test, and improve `g77'
-      over the past several years, and undoubtedly more people will be
-      doing so in the future.  If you have done so, and would like to
-      see your name listed in the above list, please ask!  The default
-      is that people wish to remain anonymous.
- 
- 
- File: g77.info,  Node: Funding,  Next: Funding GNU Fortran,  Prev: Contributors,  Up: Top
- 
- Funding Free Software
- *********************
- 
-    If you want to have more free software a few years from now, it makes
- sense for you to help encourage people to contribute funds for its
- development.  The most effective approach known is to encourage
- commercial redistributors to donate.
- 
-    Users of free software systems can boost the pace of development by
- encouraging for-a-fee distributors to donate part of their selling price
- to free software developers--the Free Software Foundation, and others.
- 
-    The way to convince distributors to do this is to demand it and
- expect it from them.  So when you compare distributors, judge them
- partly by how much they give to free software development.  Show
- distributors they must compete to be the one who gives the most.
- 
-    To make this approach work, you must insist on numbers that you can
- compare, such as, "We will donate ten dollars to the Frobnitz project
- for each disk sold."  Don't be satisfied with a vague promise, such as
- "A portion of the profits are donated," since it doesn't give a basis
- for comparison.
- 
-    Even a precise fraction "of the profits from this disk" is not very
- meaningful, since creative accounting and unrelated business decisions
- can greatly alter what fraction of the sales price counts as profit.
- If the price you pay is $50, ten percent of the profit is probably less
- than a dollar; it might be a few cents, or nothing at all.
- 
-    Some redistributors do development work themselves.  This is useful
- too; but to keep everyone honest, you need to inquire how much they do,
- and what kind.  Some kinds of development make much more long-term
- difference than others.  For example, maintaining a separate version of
- a program contributes very little; maintaining the standard version of a
- program for the whole community contributes much.  Easy new ports
- contribute little, since someone else would surely do them; difficult
- ports such as adding a new CPU to the GNU Compiler Collection
- contribute more; major new features or packages contribute the most.
- 
-    By establishing the idea that supporting further development is "the
- proper thing to do" when distributing free software for a fee, we can
- assure a steady flow of resources into making more free software.
- 
-      Copyright (C) 1994 Free Software Foundation, Inc.
-      Verbatim copying and redistribution of this section is permitted
-      without royalty; alteration is not permitted.
- 
- 
- File: g77.info,  Node: Funding GNU Fortran,  Next: Getting Started,  Prev: Funding,  Up: Top
- 
- Funding GNU Fortran
- *******************
- 
-    James Craig Burley (<craig@jcb-sc.com>), the original author of
- `g77', stopped working on it in September 1999 (He has a web page at
- `http://world.std.com/%7Eburley'.)
- 
-    GNU Fortran is currently maintained by Toon Moene
- (<toon@moene.indiv.nluug.nl>), with the help of countless other
- volunteers.
- 
-    As with other GNU software, funding is important because it can pay
- for needed equipment, personnel, and so on.
- 
-    The FSF provides information on the best way to fund ongoing
- development of GNU software (such as GNU Fortran) in documents such as
- the "GNUS Bulletin".  Email <gnu@gnu.org> for information on funding
- the FSF.
- 
-    Another important way to support work on GNU Fortran is to volunteer
- to help out.
- 
-    Email <gcc@gcc.gnu.org> to volunteer for this work.
- 
-    However, we strongly expect that there will never be a version 0.6
- of `g77'.  Work on this compiler has stopped as of the release of GCC
- 3.1, except for bug fixing.  `g77' will be succeeded by `g95' - see
- `http://g95.sourceforge.net'.
- 
-    *Note Funding Free Software: Funding, for more information.
- 
--- 0 ----
diff -Nrc3pad gcc-3.2.3/gcc/f/g77.info-10 gcc-3.3/gcc/f/g77.info-10
*** gcc-3.2.3/gcc/f/g77.info-10	2003-04-22 07:07:24.000000000 +0000
--- gcc-3.3/gcc/f/g77.info-10	1970-01-01 00:00:00.000000000 +0000
***************
*** 1,1521 ****
- This is g77.info, produced by makeinfo version 4.5 from g77.texi.
- 
- INFO-DIR-SECTION Programming
- START-INFO-DIR-ENTRY
- * g77: (g77).                  The GNU Fortran compiler.
- END-INFO-DIR-ENTRY
-    This file documents the use and the internals of the GNU Fortran
- (`g77') compiler.  It corresponds to the GCC-3.2.3 version of `g77'.
- 
-    Published by the Free Software Foundation 59 Temple Place - Suite 330
- Boston, MA 02111-1307 USA
- 
-    Copyright (C) 1995,1996,1997,1998,1999,2000,2001,2002 Free Software
- Foundation, Inc.
- 
-    Permission is granted to copy, distribute and/or modify this document
- under the terms of the GNU Free Documentation License, Version 1.1 or
- any later version published by the Free Software Foundation; with the
- Invariant Sections being "GNU General Public License" and "Funding Free
- Software", the Front-Cover texts being (a) (see below), and with the
- Back-Cover Texts being (b) (see below).  A copy of the license is
- included in the section entitled "GNU Free Documentation License".
- 
-    (a) The FSF's Front-Cover Text is:
- 
-    A GNU Manual
- 
-    (b) The FSF's Back-Cover Text is:
- 
-    You have freedom to copy and modify this GNU Manual, like GNU
- software.  Copies published by the Free Software Foundation raise
- funds for GNU development.
- 
-    Contributed by James Craig Burley (<craig@jcb-sc.com>).  Inspired by
- a first pass at translating `g77-0.5.16/f/DOC' that was contributed to
- Craig by David Ronis (<ronis@onsager.chem.mcgill.ca>).
- 
- 
- File: g77.info,  Node: Real Intrinsic,  Next: RealPart Intrinsic,  Prev: Range Intrinsic,  Up: Table of Intrinsic Functions
- 
- Real Intrinsic
- ..............
- 
-      Real(A)
- 
- Real: `REAL' function.  The exact type is `REAL(KIND=1)' when argument
- A is any type other than `COMPLEX', or when it is `COMPLEX(KIND=1)'.
- When A is any `COMPLEX' type other than `COMPLEX(KIND=1)', this
- intrinsic is valid only when used as the argument to `REAL()', as
- explained below.
- 
- A: `INTEGER', `REAL', or `COMPLEX'; scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Converts A to `REAL(KIND=1)'.
- 
-    Use of `REAL()' with a `COMPLEX' argument (other than
- `COMPLEX(KIND=1)') is restricted to the following case:
- 
-      REAL(REAL(A))
- 
- This expression converts the real part of A to `REAL(KIND=1)'.
- 
-    *Note RealPart Intrinsic::, for information on a GNU Fortran
- intrinsic that extracts the real part of an arbitrary `COMPLEX' value.
- 
-    *Note REAL() and AIMAG() of Complex::, for more information.
- 
- 
- File: g77.info,  Node: RealPart Intrinsic,  Next: Rename Intrinsic (subroutine),  Prev: Real Intrinsic,  Up: Table of Intrinsic Functions
- 
- RealPart Intrinsic
- ..................
- 
-      RealPart(Z)
- 
- RealPart: `REAL' function, the `KIND=' value of the type being that of
- argument Z.
- 
- Z: `COMPLEX'; scalar; INTENT(IN).
- 
- Intrinsic groups: `gnu'.
- 
- Description:
- 
-    The real part of Z is returned, without conversion.
- 
-    _Note:_ The way to do this in standard Fortran 90 is `REAL(Z)'.
- However, when, for example, Z is `COMPLEX(KIND=2)', `REAL(Z)' means
- something different for some compilers that are not true Fortran 90
- compilers but offer some extensions standardized by Fortran 90 (such as
- the `DOUBLE COMPLEX' type, also known as `COMPLEX(KIND=2)').
- 
-    The advantage of `REALPART()' is that, while not necessarily more or
- less portable than `REAL()', it is more likely to cause a compiler that
- doesn't support it to produce a diagnostic than generate incorrect code.
- 
-    *Note REAL() and AIMAG() of Complex::, for more information.
- 
- 
- File: g77.info,  Node: Rename Intrinsic (subroutine),  Next: Repeat Intrinsic,  Prev: RealPart Intrinsic,  Up: Table of Intrinsic Functions
- 
- Rename Intrinsic (subroutine)
- .............................
- 
-      CALL Rename(PATH1, PATH2, STATUS)
- 
- PATH1: `CHARACTER'; scalar; INTENT(IN).
- 
- PATH2: `CHARACTER'; scalar; INTENT(IN).
- 
- STATUS: `INTEGER(KIND=1)'; OPTIONAL; scalar; INTENT(OUT).
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Renames the file PATH1 to PATH2.  A null character (`CHAR(0)') marks
- the end of the names in PATH1 and PATH2--otherwise, trailing blanks in
- PATH1 and PATH2 are ignored.  See `rename(2)'.  If the STATUS argument
- is supplied, it contains 0 on success or a non-zero error code upon
- return.
- 
-    Some non-GNU implementations of Fortran provide this intrinsic as
- only a function, not as a subroutine, or do not support the (optional)
- STATUS argument.
- 
-    For information on other intrinsics with the same name: *Note Rename
- Intrinsic (function)::.
- 
- 
- File: g77.info,  Node: Repeat Intrinsic,  Next: Reshape Intrinsic,  Prev: Rename Intrinsic (subroutine),  Up: Table of Intrinsic Functions
- 
- Repeat Intrinsic
- ................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL Repeat' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: Reshape Intrinsic,  Next: RRSpacing Intrinsic,  Prev: Repeat Intrinsic,  Up: Table of Intrinsic Functions
- 
- Reshape Intrinsic
- .................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL Reshape' to use this name for
- an external procedure.
- 
- 
- File: g77.info,  Node: RRSpacing Intrinsic,  Next: RShift Intrinsic,  Prev: Reshape Intrinsic,  Up: Table of Intrinsic Functions
- 
- RRSpacing Intrinsic
- ...................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL RRSpacing' to use this name
- for an external procedure.
- 
- 
- File: g77.info,  Node: RShift Intrinsic,  Next: Scale Intrinsic,  Prev: RRSpacing Intrinsic,  Up: Table of Intrinsic Functions
- 
- RShift Intrinsic
- ................
- 
-      RShift(I, SHIFT)
- 
- RShift: `INTEGER' function, the `KIND=' value of the type being that of
- argument I.
- 
- I: `INTEGER'; scalar; INTENT(IN).
- 
- SHIFT: `INTEGER'; scalar; INTENT(IN).
- 
- Intrinsic groups: `f2c'.
- 
- Description:
- 
-    Returns I shifted to the right SHIFT bits.
- 
-    Although similar to the expression `I/(2**SHIFT)', there are
- important differences.  For example, the sign of the result is
- undefined.
- 
-    Currently this intrinsic is defined assuming the underlying
- representation of I is as a two's-complement integer.  It is unclear at
- this point whether that definition will apply when a different
- representation is involved.
- 
-    *Note RShift Intrinsic::, for the inverse of this function.
- 
-    *Note IShft Intrinsic::, for information on a more widely available
- right-shifting intrinsic that is also more precisely defined.
- 
- 
- File: g77.info,  Node: Scale Intrinsic,  Next: Scan Intrinsic,  Prev: RShift Intrinsic,  Up: Table of Intrinsic Functions
- 
- Scale Intrinsic
- ...............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL Scale' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: Scan Intrinsic,  Next: Second Intrinsic (function),  Prev: Scale Intrinsic,  Up: Table of Intrinsic Functions
- 
- Scan Intrinsic
- ..............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL Scan' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: Second Intrinsic (function),  Next: Second Intrinsic (subroutine),  Prev: Scan Intrinsic,  Up: Table of Intrinsic Functions
- 
- Second Intrinsic (function)
- ...........................
- 
-      Second()
- 
- Second: `REAL(KIND=1)' function.
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Returns the process's runtime in seconds--the same value as the UNIX
- function `etime' returns.
- 
-    On some systems, the underlying timings are represented using types
- with sufficiently small limits that overflows (wraparounds) are
- possible, such as 32-bit types.  Therefore, the values returned by this
- intrinsic might be, or become, negative, or numerically less than
- previous values, during a single run of the compiled program.
- 
-    For information on other intrinsics with the same name: *Note Second
- Intrinsic (subroutine)::.
- 
- 
- File: g77.info,  Node: Second Intrinsic (subroutine),  Next: Selected_Int_Kind Intrinsic,  Prev: Second Intrinsic (function),  Up: Table of Intrinsic Functions
- 
- Second Intrinsic (subroutine)
- .............................
- 
-      CALL Second(SECONDS)
- 
- SECONDS: `REAL'; scalar; INTENT(OUT).
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Returns the process's runtime in seconds in SECONDS--the same value
- as the UNIX function `etime' returns.
- 
-    On some systems, the underlying timings are represented using types
- with sufficiently small limits that overflows (wraparounds) are
- possible, such as 32-bit types.  Therefore, the values returned by this
- intrinsic might be, or become, negative, or numerically less than
- previous values, during a single run of the compiled program.
- 
-    This routine is known from Cray Fortran.  *Note CPU_Time Intrinsic::,
- for a standard equivalent.
- 
-    For information on other intrinsics with the same name: *Note Second
- Intrinsic (function)::.
- 
- 
- File: g77.info,  Node: Selected_Int_Kind Intrinsic,  Next: Selected_Real_Kind Intrinsic,  Prev: Second Intrinsic (subroutine),  Up: Table of Intrinsic Functions
- 
- Selected_Int_Kind Intrinsic
- ...........................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL Selected_Int_Kind' to use this
- name for an external procedure.
- 
- 
- File: g77.info,  Node: Selected_Real_Kind Intrinsic,  Next: Set_Exponent Intrinsic,  Prev: Selected_Int_Kind Intrinsic,  Up: Table of Intrinsic Functions
- 
- Selected_Real_Kind Intrinsic
- ............................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL Selected_Real_Kind' to use
- this name for an external procedure.
- 
- 
- File: g77.info,  Node: Set_Exponent Intrinsic,  Next: Shape Intrinsic,  Prev: Selected_Real_Kind Intrinsic,  Up: Table of Intrinsic Functions
- 
- Set_Exponent Intrinsic
- ......................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL Set_Exponent' to use this name
- for an external procedure.
- 
- 
- File: g77.info,  Node: Shape Intrinsic,  Next: Short Intrinsic,  Prev: Set_Exponent Intrinsic,  Up: Table of Intrinsic Functions
- 
- Shape Intrinsic
- ...............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL Shape' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: Short Intrinsic,  Next: Sign Intrinsic,  Prev: Shape Intrinsic,  Up: Table of Intrinsic Functions
- 
- Short Intrinsic
- ...............
- 
-      Short(A)
- 
- Short: `INTEGER(KIND=6)' function.
- 
- A: `INTEGER'; scalar; INTENT(IN).
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Returns A with the fractional portion of its magnitude truncated and
- its sign preserved, converted to type `INTEGER(KIND=6)'.
- 
-    If A is type `COMPLEX', its real part is truncated and converted,
- and its imaginary part is disgregarded.
- 
-    *Note Int Intrinsic::.
- 
-    The precise meaning of this intrinsic might change in a future
- version of the GNU Fortran language, as more is learned about how it is
- used.
- 
- 
- File: g77.info,  Node: Sign Intrinsic,  Next: Signal Intrinsic (subroutine),  Prev: Short Intrinsic,  Up: Table of Intrinsic Functions
- 
- Sign Intrinsic
- ..............
- 
-      Sign(A, B)
- 
- Sign: `INTEGER' or `REAL' function, the exact type being the result of
- cross-promoting the types of all the arguments.
- 
- A: `INTEGER' or `REAL'; scalar; INTENT(IN).
- 
- B: `INTEGER' or `REAL'; scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Returns `ABS(A)*S', where S is +1 if `B.GE.0', -1 otherwise.
- 
-    *Note Abs Intrinsic::, for the function that returns the magnitude
- of a value.
- 
- 
- File: g77.info,  Node: Signal Intrinsic (subroutine),  Next: Sin Intrinsic,  Prev: Sign Intrinsic,  Up: Table of Intrinsic Functions
- 
- Signal Intrinsic (subroutine)
- .............................
- 
-      CALL Signal(NUMBER, HANDLER, STATUS)
- 
- NUMBER: `INTEGER'; scalar; INTENT(IN).
- 
- HANDLER: Signal handler (`INTEGER FUNCTION' or `SUBROUTINE') or
- dummy/global `INTEGER(KIND=1)' scalar.
- 
- STATUS: `INTEGER(KIND=7)'; OPTIONAL; scalar; INTENT(OUT).
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    If HANDLER is a an `EXTERNAL' routine, arranges for it to be invoked
- with a single integer argument (of system-dependent length) when signal
- NUMBER occurs.  If HANDLER is an integer, it can be used to turn off
- handling of signal NUMBER or revert to its default action.  See
- `signal(2)'.
- 
-    Note that HANDLER will be called using C conventions, so the value
- of its argument in Fortran terms Fortran terms is obtained by applying
- `%LOC()' (or LOC()) to it.
- 
-    The value returned by `signal(2)' is written to STATUS, if that
- argument is supplied.  Otherwise the return value is ignored.
- 
-    Some non-GNU implementations of Fortran provide this intrinsic as
- only a function, not as a subroutine, or do not support the (optional)
- STATUS argument.
- 
-    _Warning:_ Use of the `libf2c' run-time library function `signal_'
- directly (such as via `EXTERNAL SIGNAL') requires use of the `%VAL()'
- construct to pass an `INTEGER' value (such as `SIG_IGN' or `SIG_DFL')
- for the HANDLER argument.
- 
-    However, while `CALL SIGNAL(SIGNUM, %VAL(SIG_IGN))' works when
- `SIGNAL' is treated as an external procedure (and resolves, at link
- time, to `libf2c''s `signal_' routine), this construct is not valid
- when `SIGNAL' is recognized as the intrinsic of that name.
- 
-    Therefore, for maximum portability and reliability, code such
- references to the `SIGNAL' facility as follows:
- 
-      INTRINSIC SIGNAL
-      ...
-      CALL SIGNAL(SIGNUM, SIG_IGN)
- 
-    `g77' will compile such a call correctly, while other compilers will
- generally either do so as well or reject the `INTRINSIC SIGNAL'
- statement via a diagnostic, allowing you to take appropriate action.
- 
-    For information on other intrinsics with the same name: *Note Signal
- Intrinsic (function)::.
- 
- 
- File: g77.info,  Node: Sin Intrinsic,  Next: SinH Intrinsic,  Prev: Signal Intrinsic (subroutine),  Up: Table of Intrinsic Functions
- 
- Sin Intrinsic
- .............
- 
-      Sin(X)
- 
- Sin: `REAL' or `COMPLEX' function, the exact type being that of
- argument X.
- 
- X: `REAL' or `COMPLEX'; scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Returns the sine of X, an angle measured in radians.
- 
-    *Note ASin Intrinsic::, for the inverse of this function.
- 
- 
- File: g77.info,  Node: SinH Intrinsic,  Next: Sleep Intrinsic,  Prev: Sin Intrinsic,  Up: Table of Intrinsic Functions
- 
- SinH Intrinsic
- ..............
- 
-      SinH(X)
- 
- SinH: `REAL' function, the `KIND=' value of the type being that of
- argument X.
- 
- X: `REAL'; scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Returns the hyperbolic sine of X.
- 
- 
- File: g77.info,  Node: Sleep Intrinsic,  Next: Sngl Intrinsic,  Prev: SinH Intrinsic,  Up: Table of Intrinsic Functions
- 
- Sleep Intrinsic
- ...............
- 
-      CALL Sleep(SECONDS)
- 
- SECONDS: `INTEGER(KIND=1)'; scalar; INTENT(IN).
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Causes the process to pause for SECONDS seconds.  See `sleep(2)'.
- 
- 
- File: g77.info,  Node: Sngl Intrinsic,  Next: Spacing Intrinsic,  Prev: Sleep Intrinsic,  Up: Table of Intrinsic Functions
- 
- Sngl Intrinsic
- ..............
- 
-      Sngl(A)
- 
- Sngl: `REAL(KIND=1)' function.
- 
- A: `REAL(KIND=2)'; scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Archaic form of `REAL()' that is specific to one type for A.  *Note
- Real Intrinsic::.
- 
- 
- File: g77.info,  Node: Spacing Intrinsic,  Next: Spread Intrinsic,  Prev: Sngl Intrinsic,  Up: Table of Intrinsic Functions
- 
- Spacing Intrinsic
- .................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL Spacing' to use this name for
- an external procedure.
- 
- 
- File: g77.info,  Node: Spread Intrinsic,  Next: SqRt Intrinsic,  Prev: Spacing Intrinsic,  Up: Table of Intrinsic Functions
- 
- Spread Intrinsic
- ................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL Spread' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: SqRt Intrinsic,  Next: SRand Intrinsic,  Prev: Spread Intrinsic,  Up: Table of Intrinsic Functions
- 
- SqRt Intrinsic
- ..............
- 
-      SqRt(X)
- 
- SqRt: `REAL' or `COMPLEX' function, the exact type being that of
- argument X.
- 
- X: `REAL' or `COMPLEX'; scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Returns the square root of X, which must not be negative.
- 
-    To calculate and represent the square root of a negative number,
- complex arithmetic must be used.  For example, `SQRT(COMPLEX(X))'.
- 
-    The inverse of this function is `SQRT(X) * SQRT(X)'.
- 
- 
- File: g77.info,  Node: SRand Intrinsic,  Next: Stat Intrinsic (subroutine),  Prev: SqRt Intrinsic,  Up: Table of Intrinsic Functions
- 
- SRand Intrinsic
- ...............
- 
-      CALL SRand(SEED)
- 
- SEED: `INTEGER'; scalar; INTENT(IN).
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Reinitialises the generator with the seed in SEED.  *Note IRand
- Intrinsic::.  *Note Rand Intrinsic::.
- 
- 
- File: g77.info,  Node: Stat Intrinsic (subroutine),  Next: Stat Intrinsic (function),  Prev: SRand Intrinsic,  Up: Table of Intrinsic Functions
- 
- Stat Intrinsic (subroutine)
- ...........................
- 
-      CALL Stat(FILE, SARRAY, STATUS)
- 
- FILE: `CHARACTER'; scalar; INTENT(IN).
- 
- SARRAY: `INTEGER(KIND=1)'; DIMENSION(13); INTENT(OUT).
- 
- STATUS: `INTEGER(KIND=1)'; OPTIONAL; scalar; INTENT(OUT).
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Obtains data about the given file FILE and places them in the array
- SARRAY.  A null character (`CHAR(0)') marks the end of the name in
- FILE--otherwise, trailing blanks in FILE are ignored.  The values in
- this array are extracted from the `stat' structure as returned by
- `fstat(2)' q.v., as follows:
- 
-   1. Device ID
- 
-   2. Inode number
- 
-   3. File mode
- 
-   4. Number of links
- 
-   5. Owner's uid
- 
-   6. Owner's gid
- 
-   7. ID of device containing directory entry for file (0 if not
-      available)
- 
-   8. File size (bytes)
- 
-   9. Last access time
- 
-  10. Last modification time
- 
-  11. Last file status change time
- 
-  12. Preferred I/O block size (-1 if not available)
- 
-  13. Number of blocks allocated (-1 if not available)
- 
-    Not all these elements are relevant on all systems.  If an element
- is not relevant, it is returned as 0.
- 
-    If the STATUS argument is supplied, it contains 0 on success or a
- non-zero error code upon return.
- 
-    Some non-GNU implementations of Fortran provide this intrinsic as
- only a function, not as a subroutine, or do not support the (optional)
- STATUS argument.
- 
-    For information on other intrinsics with the same name: *Note Stat
- Intrinsic (function)::.
- 
- 
- File: g77.info,  Node: Stat Intrinsic (function),  Next: Sum Intrinsic,  Prev: Stat Intrinsic (subroutine),  Up: Table of Intrinsic Functions
- 
- Stat Intrinsic (function)
- .........................
- 
-      Stat(FILE, SARRAY)
- 
- Stat: `INTEGER(KIND=1)' function.
- 
- FILE: `CHARACTER'; scalar; INTENT(IN).
- 
- SARRAY: `INTEGER(KIND=1)'; DIMENSION(13); INTENT(OUT).
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Obtains data about the given file FILE and places them in the array
- SARRAY.  A null character (`CHAR(0)') marks the end of the name in
- FILE--otherwise, trailing blanks in FILE are ignored.  The values in
- this array are extracted from the `stat' structure as returned by
- `fstat(2)' q.v., as follows:
- 
-   1. Device ID
- 
-   2. Inode number
- 
-   3. File mode
- 
-   4. Number of links
- 
-   5. Owner's uid
- 
-   6. Owner's gid
- 
-   7. ID of device containing directory entry for file (0 if not
-      available)
- 
-   8. File size (bytes)
- 
-   9. Last access time
- 
-  10. Last modification time
- 
-  11. Last file status change time
- 
-  12. Preferred I/O block size (-1 if not available)
- 
-  13. Number of blocks allocated (-1 if not available)
- 
-    Not all these elements are relevant on all systems.  If an element
- is not relevant, it is returned as 0.
- 
-    Returns 0 on success or a non-zero error code.
- 
-    For information on other intrinsics with the same name: *Note Stat
- Intrinsic (subroutine)::.
- 
- 
- File: g77.info,  Node: Sum Intrinsic,  Next: SymLnk Intrinsic (subroutine),  Prev: Stat Intrinsic (function),  Up: Table of Intrinsic Functions
- 
- Sum Intrinsic
- .............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL Sum' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: SymLnk Intrinsic (subroutine),  Next: System Intrinsic (subroutine),  Prev: Sum Intrinsic,  Up: Table of Intrinsic Functions
- 
- SymLnk Intrinsic (subroutine)
- .............................
- 
-      CALL SymLnk(PATH1, PATH2, STATUS)
- 
- PATH1: `CHARACTER'; scalar; INTENT(IN).
- 
- PATH2: `CHARACTER'; scalar; INTENT(IN).
- 
- STATUS: `INTEGER(KIND=1)'; OPTIONAL; scalar; INTENT(OUT).
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Makes a symbolic link from file PATH1 to PATH2.  A null character
- (`CHAR(0)') marks the end of the names in PATH1 and PATH2--otherwise,
- trailing blanks in PATH1 and PATH2 are ignored.  If the STATUS argument
- is supplied, it contains 0 on success or a non-zero error code upon
- return (`ENOSYS' if the system does not provide `symlink(2)').
- 
-    Some non-GNU implementations of Fortran provide this intrinsic as
- only a function, not as a subroutine, or do not support the (optional)
- STATUS argument.
- 
-    For information on other intrinsics with the same name: *Note SymLnk
- Intrinsic (function)::.
- 
- 
- File: g77.info,  Node: System Intrinsic (subroutine),  Next: System_Clock Intrinsic,  Prev: SymLnk Intrinsic (subroutine),  Up: Table of Intrinsic Functions
- 
- System Intrinsic (subroutine)
- .............................
- 
-      CALL System(COMMAND, STATUS)
- 
- COMMAND: `CHARACTER'; scalar; INTENT(IN).
- 
- STATUS: `INTEGER(KIND=1)'; OPTIONAL; scalar; INTENT(OUT).
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Passes the command COMMAND to a shell (see `system(3)').  If
- argument STATUS is present, it contains the value returned by
- `system(3)', presumably 0 if the shell command succeeded.  Note that
- which shell is used to invoke the command is system-dependent and
- environment-dependent.
- 
-    Some non-GNU implementations of Fortran provide this intrinsic as
- only a function, not as a subroutine, or do not support the (optional)
- STATUS argument.
- 
-    For information on other intrinsics with the same name: *Note System
- Intrinsic (function)::.
- 
- 
- File: g77.info,  Node: System_Clock Intrinsic,  Next: Tan Intrinsic,  Prev: System Intrinsic (subroutine),  Up: Table of Intrinsic Functions
- 
- System_Clock Intrinsic
- ......................
- 
-      CALL System_Clock(COUNT, RATE, MAX)
- 
- COUNT: `INTEGER(KIND=1)'; scalar; INTENT(OUT).
- 
- RATE: `INTEGER(KIND=1)'; OPTIONAL; scalar; INTENT(OUT).
- 
- MAX: `INTEGER(KIND=1)'; OPTIONAL; scalar; INTENT(OUT).
- 
- Intrinsic groups: `f90'.
- 
- Description:
- 
-    Returns in COUNT the current value of the system clock; this is the
- value returned by the UNIX function `times(2)' in this implementation,
- but isn't in general.  RATE is the number of clock ticks per second and
- MAX is the maximum value this can take, which isn't very useful in this
- implementation since it's just the maximum C `unsigned int' value.
- 
-    On some systems, the underlying timings are represented using types
- with sufficiently small limits that overflows (wraparounds) are
- possible, such as 32-bit types.  Therefore, the values returned by this
- intrinsic might be, or become, negative, or numerically less than
- previous values, during a single run of the compiled program.
- 
- 
- File: g77.info,  Node: Tan Intrinsic,  Next: TanH Intrinsic,  Prev: System_Clock Intrinsic,  Up: Table of Intrinsic Functions
- 
- Tan Intrinsic
- .............
- 
-      Tan(X)
- 
- Tan: `REAL' function, the `KIND=' value of the type being that of
- argument X.
- 
- X: `REAL'; scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Returns the tangent of X, an angle measured in radians.
- 
-    *Note ATan Intrinsic::, for the inverse of this function.
- 
- 
- File: g77.info,  Node: TanH Intrinsic,  Next: Time Intrinsic (UNIX),  Prev: Tan Intrinsic,  Up: Table of Intrinsic Functions
- 
- TanH Intrinsic
- ..............
- 
-      TanH(X)
- 
- TanH: `REAL' function, the `KIND=' value of the type being that of
- argument X.
- 
- X: `REAL'; scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Returns the hyperbolic tangent of X.
- 
- 
- File: g77.info,  Node: Time Intrinsic (UNIX),  Next: Time8 Intrinsic,  Prev: TanH Intrinsic,  Up: Table of Intrinsic Functions
- 
- Time Intrinsic (UNIX)
- .....................
- 
-      Time()
- 
- Time: `INTEGER(KIND=1)' function.
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Returns the current time encoded as an integer (in the manner of the
- UNIX function `time(3)').  This value is suitable for passing to
- `CTIME', `GMTIME', and `LTIME'.
- 
-    This intrinsic is not fully portable, such as to systems with 32-bit
- `INTEGER' types but supporting times wider than 32 bits.  Therefore,
- the values returned by this intrinsic might be, or become, negative, or
- numerically less than previous values, during a single run of the
- compiled program.
- 
-    *Note Time8 Intrinsic::, for information on a similar intrinsic that
- might be portable to more GNU Fortran implementations, though to fewer
- Fortran compilers.
- 
-    For information on other intrinsics with the same name: *Note Time
- Intrinsic (VXT)::.
- 
- 
- File: g77.info,  Node: Time8 Intrinsic,  Next: Tiny Intrinsic,  Prev: Time Intrinsic (UNIX),  Up: Table of Intrinsic Functions
- 
- Time8 Intrinsic
- ...............
- 
-      Time8()
- 
- Time8: `INTEGER(KIND=2)' function.
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Returns the current time encoded as a long integer (in the manner of
- the UNIX function `time(3)').  This value is suitable for passing to
- `CTIME', `GMTIME', and `LTIME'.
- 
-    _Warning:_ this intrinsic does not increase the range of the timing
- values over that returned by `time(3)'.  On a system with a 32-bit
- `time(3)', `TIME8' will return a 32-bit value, even though converted to
- an `INTEGER(KIND=2)' value.  That means overflows of the 32-bit value
- can still occur.  Therefore, the values returned by this intrinsic
- might be, or become, negative, or numerically less than previous values,
- during a single run of the compiled program.
- 
-    No Fortran implementations other than GNU Fortran are known to
- support this intrinsic at the time of this writing.  *Note Time
- Intrinsic (UNIX)::, for information on a similar intrinsic that might
- be portable to more Fortran compilers, though to fewer GNU Fortran
- implementations.
- 
- 
- File: g77.info,  Node: Tiny Intrinsic,  Next: Transfer Intrinsic,  Prev: Time8 Intrinsic,  Up: Table of Intrinsic Functions
- 
- Tiny Intrinsic
- ..............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL Tiny' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: Transfer Intrinsic,  Next: Transpose Intrinsic,  Prev: Tiny Intrinsic,  Up: Table of Intrinsic Functions
- 
- Transfer Intrinsic
- ..................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL Transfer' to use this name for
- an external procedure.
- 
- 
- File: g77.info,  Node: Transpose Intrinsic,  Next: Trim Intrinsic,  Prev: Transfer Intrinsic,  Up: Table of Intrinsic Functions
- 
- Transpose Intrinsic
- ...................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL Transpose' to use this name
- for an external procedure.
- 
- 
- File: g77.info,  Node: Trim Intrinsic,  Next: TtyNam Intrinsic (subroutine),  Prev: Transpose Intrinsic,  Up: Table of Intrinsic Functions
- 
- Trim Intrinsic
- ..............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL Trim' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: TtyNam Intrinsic (subroutine),  Next: TtyNam Intrinsic (function),  Prev: Trim Intrinsic,  Up: Table of Intrinsic Functions
- 
- TtyNam Intrinsic (subroutine)
- .............................
- 
-      CALL TtyNam(UNIT, NAME)
- 
- UNIT: `INTEGER'; scalar; INTENT(IN).
- 
- NAME: `CHARACTER'; scalar; INTENT(OUT).
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Sets NAME to the name of the terminal device open on logical unit
- UNIT or to a blank string if UNIT is not connected to a terminal.
- 
-    Some non-GNU implementations of Fortran provide this intrinsic as
- only a function, not as a subroutine.
- 
-    For information on other intrinsics with the same name: *Note TtyNam
- Intrinsic (function)::.
- 
- 
- File: g77.info,  Node: TtyNam Intrinsic (function),  Next: UBound Intrinsic,  Prev: TtyNam Intrinsic (subroutine),  Up: Table of Intrinsic Functions
- 
- TtyNam Intrinsic (function)
- ...........................
- 
-      TtyNam(UNIT)
- 
- TtyNam: `CHARACTER*(*)' function.
- 
- UNIT: `INTEGER'; scalar; INTENT(IN).
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Returns the name of the terminal device open on logical unit UNIT or
- a blank string if UNIT is not connected to a terminal.
- 
-    For information on other intrinsics with the same name: *Note TtyNam
- Intrinsic (subroutine)::.
- 
- 
- File: g77.info,  Node: UBound Intrinsic,  Next: UMask Intrinsic (subroutine),  Prev: TtyNam Intrinsic (function),  Up: Table of Intrinsic Functions
- 
- UBound Intrinsic
- ................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL UBound' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: UMask Intrinsic (subroutine),  Next: Unlink Intrinsic (subroutine),  Prev: UBound Intrinsic,  Up: Table of Intrinsic Functions
- 
- UMask Intrinsic (subroutine)
- ............................
- 
-      CALL UMask(MASK, OLD)
- 
- MASK: `INTEGER'; scalar; INTENT(IN).
- 
- OLD: `INTEGER(KIND=1)'; OPTIONAL; scalar; INTENT(OUT).
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Sets the file creation mask to MASK and returns the old value in
- argument OLD if it is supplied.  See `umask(2)'.
- 
-    Some non-GNU implementations of Fortran provide this intrinsic as
- only a function, not as a subroutine.
- 
-    For information on other intrinsics with the same name: *Note UMask
- Intrinsic (function)::.
- 
- 
- File: g77.info,  Node: Unlink Intrinsic (subroutine),  Next: Unpack Intrinsic,  Prev: UMask Intrinsic (subroutine),  Up: Table of Intrinsic Functions
- 
- Unlink Intrinsic (subroutine)
- .............................
- 
-      CALL Unlink(FILE, STATUS)
- 
- FILE: `CHARACTER'; scalar; INTENT(IN).
- 
- STATUS: `INTEGER(KIND=1)'; OPTIONAL; scalar; INTENT(OUT).
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Unlink the file FILE.  A null character (`CHAR(0)') marks the end of
- the name in FILE--otherwise, trailing blanks in FILE are ignored.  If
- the STATUS argument is supplied, it contains 0 on success or a non-zero
- error code upon return.  See `unlink(2)'.
- 
-    Some non-GNU implementations of Fortran provide this intrinsic as
- only a function, not as a subroutine, or do not support the (optional)
- STATUS argument.
- 
-    For information on other intrinsics with the same name: *Note Unlink
- Intrinsic (function)::.
- 
- 
- File: g77.info,  Node: Unpack Intrinsic,  Next: Verify Intrinsic,  Prev: Unlink Intrinsic (subroutine),  Up: Table of Intrinsic Functions
- 
- Unpack Intrinsic
- ................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL Unpack' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: Verify Intrinsic,  Next: XOr Intrinsic,  Prev: Unpack Intrinsic,  Up: Table of Intrinsic Functions
- 
- Verify Intrinsic
- ................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL Verify' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: XOr Intrinsic,  Next: ZAbs Intrinsic,  Prev: Verify Intrinsic,  Up: Table of Intrinsic Functions
- 
- XOr Intrinsic
- .............
- 
-      XOr(I, J)
- 
- XOr: `INTEGER' or `LOGICAL' function, the exact type being the result
- of cross-promoting the types of all the arguments.
- 
- I: `INTEGER' or `LOGICAL'; scalar; INTENT(IN).
- 
- J: `INTEGER' or `LOGICAL'; scalar; INTENT(IN).
- 
- Intrinsic groups: `f2c'.
- 
- Description:
- 
-    Returns value resulting from boolean exclusive-OR of pair of bits in
- each of I and J.
- 
- 
- File: g77.info,  Node: ZAbs Intrinsic,  Next: ZCos Intrinsic,  Prev: XOr Intrinsic,  Up: Table of Intrinsic Functions
- 
- ZAbs Intrinsic
- ..............
- 
-      ZAbs(A)
- 
- ZAbs: `REAL(KIND=2)' function.
- 
- A: `COMPLEX(KIND=2)'; scalar; INTENT(IN).
- 
- Intrinsic groups: `f2c'.
- 
- Description:
- 
-    Archaic form of `ABS()' that is specific to one type for A.  *Note
- Abs Intrinsic::.
- 
- 
- File: g77.info,  Node: ZCos Intrinsic,  Next: ZExp Intrinsic,  Prev: ZAbs Intrinsic,  Up: Table of Intrinsic Functions
- 
- ZCos Intrinsic
- ..............
- 
-      ZCos(X)
- 
- ZCos: `COMPLEX(KIND=2)' function.
- 
- X: `COMPLEX(KIND=2)'; scalar; INTENT(IN).
- 
- Intrinsic groups: `f2c'.
- 
- Description:
- 
-    Archaic form of `COS()' that is specific to one type for X.  *Note
- Cos Intrinsic::.
- 
- 
- File: g77.info,  Node: ZExp Intrinsic,  Next: ZLog Intrinsic,  Prev: ZCos Intrinsic,  Up: Table of Intrinsic Functions
- 
- ZExp Intrinsic
- ..............
- 
-      ZExp(X)
- 
- ZExp: `COMPLEX(KIND=2)' function.
- 
- X: `COMPLEX(KIND=2)'; scalar; INTENT(IN).
- 
- Intrinsic groups: `f2c'.
- 
- Description:
- 
-    Archaic form of `EXP()' that is specific to one type for X.  *Note
- Exp Intrinsic::.
- 
- 
- File: g77.info,  Node: ZLog Intrinsic,  Next: ZSin Intrinsic,  Prev: ZExp Intrinsic,  Up: Table of Intrinsic Functions
- 
- ZLog Intrinsic
- ..............
- 
-      ZLog(X)
- 
- ZLog: `COMPLEX(KIND=2)' function.
- 
- X: `COMPLEX(KIND=2)'; scalar; INTENT(IN).
- 
- Intrinsic groups: `f2c'.
- 
- Description:
- 
-    Archaic form of `LOG()' that is specific to one type for X.  *Note
- Log Intrinsic::.
- 
- 
- File: g77.info,  Node: ZSin Intrinsic,  Next: ZSqRt Intrinsic,  Prev: ZLog Intrinsic,  Up: Table of Intrinsic Functions
- 
- ZSin Intrinsic
- ..............
- 
-      ZSin(X)
- 
- ZSin: `COMPLEX(KIND=2)' function.
- 
- X: `COMPLEX(KIND=2)'; scalar; INTENT(IN).
- 
- Intrinsic groups: `f2c'.
- 
- Description:
- 
-    Archaic form of `SIN()' that is specific to one type for X.  *Note
- Sin Intrinsic::.
- 
- 
- File: g77.info,  Node: ZSqRt Intrinsic,  Prev: ZSin Intrinsic,  Up: Table of Intrinsic Functions
- 
- ZSqRt Intrinsic
- ...............
- 
-      ZSqRt(X)
- 
- ZSqRt: `COMPLEX(KIND=2)' function.
- 
- X: `COMPLEX(KIND=2)'; scalar; INTENT(IN).
- 
- Intrinsic groups: `f2c'.
- 
- Description:
- 
-    Archaic form of `SQRT()' that is specific to one type for X.  *Note
- SqRt Intrinsic::.
- 
- 
- File: g77.info,  Node: Scope and Classes of Names,  Next: I/O,  Prev: Functions and Subroutines,  Up: Language
- 
- Scope and Classes of Symbolic Names
- ===================================
- 
-    (The following information augments or overrides the information in
- Chapter 18 of ANSI X3.9-1978 FORTRAN 77 in specifying the GNU Fortran
- language.  Chapter 18 of that document otherwise serves as the basis
- for the relevant aspects of GNU Fortran.)
- 
- * Menu:
- 
- * Underscores in Symbol Names::
- 
- 
- File: g77.info,  Node: Underscores in Symbol Names,  Up: Scope and Classes of Names
- 
- Underscores in Symbol Names
- ---------------------------
- 
-    Underscores (`_') are accepted in symbol names after the first
- character (which must be a letter).
- 
- 
- File: g77.info,  Node: I/O,  Next: Fortran 90 Features,  Prev: Scope and Classes of Names,  Up: Language
- 
- I/O
- ===
- 
-    A dollar sign at the end of an output format specification suppresses
- the newline at the end of the output.
- 
-    Edit descriptors in `FORMAT' statements may contain compile-time
- `INTEGER' constant expressions in angle brackets, such as
-      10    FORMAT (I<WIDTH>)
- 
-    The `OPEN' specifier `NAME=' is equivalent to `FILE='.
- 
-    These Fortran 90 features are supported:
-    * The `O' and `Z' edit descriptors are supported for I/O of integers
-      in octal and hexadecimal formats, respectively.
- 
-    * The `FILE=' specifier may be omitted in an `OPEN' statement if
-      `STATUS='SCRATCH'' is supplied.  The `STATUS='REPLACE'' specifier
-      is supported.
- 
- 
- File: g77.info,  Node: Fortran 90 Features,  Prev: I/O,  Up: Language
- 
- Fortran 90 Features
- ===================
- 
-    For convenience this section collects a list (probably incomplete) of
- the Fortran 90 features supported by the GNU Fortran language, even if
- they are documented elsewhere.  *Note Characters, Lines, and Execution
- Sequence: Characters Lines Sequence, for information on additional
- fixed source form lexical issues.  Further, the free source form is
- supported through the `-ffree-form' option.  Other Fortran 90 features
- can be turned on by the `-ff90' option; see *Note Fortran 90::.  For
- information on the Fortran 90 intrinsics available, see *Note Table of
- Intrinsic Functions::.
- 
- Automatic arrays in procedures
- 
- Character assignments
-      In character assignments, the variable being assigned may occur on
-      the right hand side of the assignment.
- 
- Character strings
-      Strings may have zero length and substrings of character constants
-      are permitted.  Character constants may be enclosed in double
-      quotes (`"') as well as single quotes.  *Note Character Type::.
- 
- Construct names
-      (Symbolic tags on blocks.)  *Note Construct Names::.
- 
- `CYCLE' and `EXIT'
-      *Note The `CYCLE' and `EXIT' Statements: CYCLE and EXIT.
- 
- `DOUBLE COMPLEX'
-      *Note `DOUBLE COMPLEX' Statement: DOUBLE COMPLEX.
- 
- `DO WHILE'
-      *Note DO WHILE::.
- 
- `END' decoration
-      *Note Statements::.
- 
- `END DO'
-      *Note END DO::.
- 
- `KIND'
- 
- `IMPLICIT NONE'
- 
- `INCLUDE' statements
-      *Note INCLUDE::.
- 
- List-directed and namelist I/O on internal files
- 
- Binary, octal and hexadecimal constants
-      These are supported more generally than required by Fortran 90.
-      *Note Integer Type::.
- 
- `O' and `Z' edit descriptors
- 
- `NAMELIST'
-      *Note NAMELIST::.
- 
- `OPEN' specifiers
-      `STATUS='REPLACE'' is supported.  The `FILE=' specifier may be
-      omitted in an `OPEN' statement if `STATUS='SCRATCH'' is supplied.
- 
- `FORMAT' edit descriptors
-      The `Z' edit descriptor is supported.
- 
- Relational operators
-      The operators `<', `<=', `==', `/=', `>' and `>=' may be used
-      instead of `.LT.', `.LE.', `.EQ.', `.NE.', `.GT.' and `.GE.'
-      respectively.
- 
- `SELECT CASE'
-      Not fully implemented.  *Note `SELECT CASE' on `CHARACTER' Type:
-      SELECT CASE on CHARACTER Type.
- 
- Specification statements
-      A limited subset of the Fortran 90 syntax and semantics for
-      variable declarations is supported, including `KIND'.  *Note Kind
-      Notation::.  (`KIND' is of limited usefulness in the absence of the
-      `KIND'-related intrinsics, since these intrinsics permit writing
-      more widely portable code.)  An example of supported `KIND' usage
-      is:
-           INTEGER (KIND=1) :: FOO=1, BAR=2
-           CHARACTER (LEN=3) FOO
-      `PARAMETER' and `DIMENSION' attributes aren't supported.
- 
- 
- File: g77.info,  Node: Other Dialects,  Next: Other Compilers,  Prev: Compiler,  Up: Top
- 
- Other Dialects
- **************
- 
-    GNU Fortran supports a variety of features that are not considered
- part of the GNU Fortran language itself, but are representative of
- various dialects of Fortran that `g77' supports in whole or in part.
- 
-    Any of the features listed below might be disallowed by `g77' unless
- some command-line option is specified.  Currently, some of the features
- are accepted using the default invocation of `g77', but that might
- change in the future.
- 
-    _Note: This portion of the documentation definitely needs a lot of
- work!_
- 
- * Menu:
- 
- * Source Form::       Details of fixed-form and free-form source.
- * Trailing Comment::  Use of `/*' to start a comment.
- * Debug Line::        Use of `D' in column 1.
- * Dollar Signs::      Use of `$' in symbolic names.
- * Case Sensitivity::  Uppercase and lowercase in source files.
- * VXT Fortran::       ...versus the GNU Fortran language.
- * Fortran 90::        ...versus the GNU Fortran language.
- * Pedantic Compilation::  Enforcing the standard.
- * Distensions::       Misfeatures supported by GNU Fortran.
- 
- 
- File: g77.info,  Node: Source Form,  Next: Trailing Comment,  Up: Other Dialects
- 
- Source Form
- ===========
- 
-    GNU Fortran accepts programs written in either fixed form or free
- form.
- 
-    Fixed form corresponds to ANSI FORTRAN 77 (plus popular extensions,
- such as allowing tabs) and Fortran 90's fixed form.
- 
-    Free form corresponds to Fortran 90's free form (though possibly not
- entirely up-to-date, and without complaining about some things that for
- which Fortran 90 requires diagnostics, such as the spaces in the
- constant in `R = 3 . 1').
- 
-    The way a Fortran compiler views source files depends entirely on the
- implementation choices made for the compiler, since those choices are
- explicitly left to the implementation by the published Fortran
- standards.  GNU Fortran currently tries to be somewhat like a few
- popular compilers (`f2c', Digital ("DEC") Fortran, and so on).
- 
-    This section describes how `g77' interprets source lines.
- 
- * Menu:
- 
- * Carriage Returns::  Carriage returns ignored.
- * Tabs::              Tabs converted to spaces.
- * Short Lines::       Short lines padded with spaces (fixed-form only).
- * Long Lines::        Long lines truncated.
- * Ampersands::        Special Continuation Lines.
- 
- 
- File: g77.info,  Node: Carriage Returns,  Next: Tabs,  Up: Source Form
- 
- Carriage Returns
- ----------------
- 
-    Carriage returns (`\r') in source lines are ignored.  This is
- somewhat different from `f2c', which seems to treat them as spaces
- outside character/Hollerith constants, and encodes them as `\r' inside
- such constants.
- 
- 
- File: g77.info,  Node: Tabs,  Next: Short Lines,  Prev: Carriage Returns,  Up: Source Form
- 
- Tabs
- ----
- 
-    A source line with a <TAB> character anywhere in it is treated as
- entirely significant--however long it is--instead of ending in column
- 72 (for fixed-form source) or 132 (for free-form source).  This also is
- different from `f2c', which encodes tabs as `\t' (the ASCII <TAB>
- character) inside character and Hollerith constants, but nevertheless
- seems to treat the column position as if it had been affected by the
- canonical tab positioning.
- 
-    `g77' effectively translates tabs to the appropriate number of
- spaces (a la the default for the UNIX `expand' command) before doing
- any other processing, other than (currently) noting whether a tab was
- found on a line and using this information to decide how to interpret
- the length of the line and continued constants.
- 
- 
- File: g77.info,  Node: Short Lines,  Next: Long Lines,  Prev: Tabs,  Up: Source Form
- 
- Short Lines
- -----------
- 
-    Source lines shorter than the applicable fixed-form length are
- treated as if they were padded with spaces to that length.  (None of
- this is relevant to source files written in free form.)
- 
-    This affects only continued character and Hollerith constants, and
- is a different interpretation than provided by some other popular
- compilers (although a bit more consistent with the traditional
- punched-card basis of Fortran and the way the Fortran standard
- expressed fixed source form).
- 
-    `g77' might someday offer an option to warn about cases where
- differences might be seen as a result of this treatment, and perhaps an
- option to specify the alternate behavior as well.
- 
-    Note that this padding cannot apply to lines that are effectively of
- infinite length--such lines are specified using command-line options
- like `-ffixed-line-length-none', for example.
- 
- 
- File: g77.info,  Node: Long Lines,  Next: Ampersands,  Prev: Short Lines,  Up: Source Form
- 
- Long Lines
- ----------
- 
-    Source lines longer than the applicable length are truncated to that
- length.  Currently, `g77' does not warn if the truncated characters are
- not spaces, to accommodate existing code written for systems that
- treated truncated text as commentary (especially in columns 73 through
- 80).
- 
-    *Note Options Controlling Fortran Dialect: Fortran Dialect Options,
- for information on the `-ffixed-line-length-N' option, which can be
- used to set the line length applicable to fixed-form source files.
- 
- 
- File: g77.info,  Node: Ampersands,  Prev: Long Lines,  Up: Source Form
- 
- Ampersand Continuation Line
- ---------------------------
- 
-    A `&' in column 1 of fixed-form source denotes an arbitrary-length
- continuation line, imitating the behavior of `f2c'.
- 
- 
- File: g77.info,  Node: Trailing Comment,  Next: Debug Line,  Prev: Source Form,  Up: Other Dialects
- 
- Trailing Comment
- ================
- 
-    `g77' supports use of `/*' to start a trailing comment.  In the GNU
- Fortran language, `!' is used for this purpose.
- 
-    `/*' is not in the GNU Fortran language because the use of `/*' in a
- program might suggest to some readers that a block, not trailing,
- comment is started (and thus ended by `*/', not end of line), since
- that is the meaning of `/*' in C.
- 
-    Also, such readers might think they can use `//' to start a trailing
- comment as an alternative to `/*', but `//' already denotes
- concatenation, and such a "comment" might actually result in a program
- that compiles without error (though it would likely behave incorrectly).
- 
- 
- File: g77.info,  Node: Debug Line,  Next: Dollar Signs,  Prev: Trailing Comment,  Up: Other Dialects
- 
- Debug Line
- ==========
- 
-    Use of `D' or `d' as the first character (column 1) of a source line
- denotes a debug line.
- 
-    In turn, a debug line is treated as either a comment line or a
- normal line, depending on whether debug lines are enabled.
- 
-    When treated as a comment line, a line beginning with `D' or `d' is
- treated as if it the first character was `C' or `c', respectively.
- When treated as a normal line, such a line is treated as if the first
- character was <SPC> (space).
- 
-    (Currently, `g77' provides no means for treating debug lines as
- normal lines.)
- 
- 
- File: g77.info,  Node: Dollar Signs,  Next: Case Sensitivity,  Prev: Debug Line,  Up: Other Dialects
- 
- Dollar Signs in Symbol Names
- ============================
- 
-    Dollar signs (`$') are allowed in symbol names (after the first
- character) when the `-fdollar-ok' option is specified.
- 
--- 0 ----
diff -Nrc3pad gcc-3.2.3/gcc/f/g77.info-11 gcc-3.3/gcc/f/g77.info-11
*** gcc-3.2.3/gcc/f/g77.info-11	2003-04-22 07:07:24.000000000 +0000
--- gcc-3.3/gcc/f/g77.info-11	1970-01-01 00:00:00.000000000 +0000
***************
*** 1,1317 ****
- This is g77.info, produced by makeinfo version 4.5 from g77.texi.
- 
- INFO-DIR-SECTION Programming
- START-INFO-DIR-ENTRY
- * g77: (g77).                  The GNU Fortran compiler.
- END-INFO-DIR-ENTRY
-    This file documents the use and the internals of the GNU Fortran
- (`g77') compiler.  It corresponds to the GCC-3.2.3 version of `g77'.
- 
-    Published by the Free Software Foundation 59 Temple Place - Suite 330
- Boston, MA 02111-1307 USA
- 
-    Copyright (C) 1995,1996,1997,1998,1999,2000,2001,2002 Free Software
- Foundation, Inc.
- 
-    Permission is granted to copy, distribute and/or modify this document
- under the terms of the GNU Free Documentation License, Version 1.1 or
- any later version published by the Free Software Foundation; with the
- Invariant Sections being "GNU General Public License" and "Funding Free
- Software", the Front-Cover texts being (a) (see below), and with the
- Back-Cover Texts being (b) (see below).  A copy of the license is
- included in the section entitled "GNU Free Documentation License".
- 
-    (a) The FSF's Front-Cover Text is:
- 
-    A GNU Manual
- 
-    (b) The FSF's Back-Cover Text is:
- 
-    You have freedom to copy and modify this GNU Manual, like GNU
- software.  Copies published by the Free Software Foundation raise
- funds for GNU development.
- 
-    Contributed by James Craig Burley (<craig@jcb-sc.com>).  Inspired by
- a first pass at translating `g77-0.5.16/f/DOC' that was contributed to
- Craig by David Ronis (<ronis@onsager.chem.mcgill.ca>).
- 
- 
- File: g77.info,  Node: Case Sensitivity,  Next: VXT Fortran,  Prev: Dollar Signs,  Up: Other Dialects
- 
- Case Sensitivity
- ================
- 
-    GNU Fortran offers the programmer way too much flexibility in
- deciding how source files are to be treated vis-a-vis uppercase and
- lowercase characters.  There are 66 useful settings that affect case
- sensitivity, plus 10 settings that are nearly useless, with the
- remaining 116 settings being either redundant or useless.
- 
-    None of these settings have any effect on the contents of comments
- (the text after a `c' or `C' in Column 1, for example) or of character
- or Hollerith constants.  Note that things like the `E' in the statement
- `CALL FOO(3.2E10)' and the `TO' in `ASSIGN 10 TO LAB' are considered
- built-in keywords, and so are affected by these settings.
- 
-    Low-level switches are identified in this section as follows:
- 
-      A Source Case Conversion:
- 
-           0 Preserve (see Note 1)
- 
-           1 Convert to Upper Case
- 
-           2 Convert to Lower Case
- 
-      B Built-in Keyword Matching:
- 
-           0 Match Any Case (per-character basis)
- 
-           1 Match Upper Case Only
- 
-           2 Match Lower Case Only
- 
-           3 Match InitialCaps Only (see tables for spellings)
- 
-      C Built-in Intrinsic Matching:
- 
-           0 Match Any Case (per-character basis)
- 
-           1 Match Upper Case Only
- 
-           2 Match Lower Case Only
- 
-           3 Match InitialCaps Only (see tables for spellings)
- 
-      D User-defined Symbol Possibilities (warnings only):
- 
-           0 Allow Any Case (per-character basis)
- 
-           1 Allow Upper Case Only
- 
-           2 Allow Lower Case Only
- 
-           3 Allow InitialCaps Only (see Note 2)
- 
-    Note 1: `g77' eventually will support `NAMELIST' in a manner that is
- consistent with these source switches--in the sense that input will be
- expected to meet the same requirements as source code in terms of
- matching symbol names and keywords (for the exponent letters).
- 
-    Currently, however, `NAMELIST' is supported by `libg2c', which
- uppercases `NAMELIST' input and symbol names for matching.  This means
- not only that `NAMELIST' output currently shows symbol (and keyword)
- names in uppercase even if lower-case source conversion (option A2) is
- selected, but that `NAMELIST' cannot be adequately supported when
- source case preservation (option A0) is selected.
- 
-    If A0 is selected, a warning message will be output for each
- `NAMELIST' statement to this effect.  The behavior of the program is
- undefined at run time if two or more symbol names appear in a given
- `NAMELIST' such that the names are identical when converted to upper
- case (e.g. `NAMELIST /X/ VAR, Var, var').  For complete and total
- elegance, perhaps there should be a warning when option A2 is selected,
- since the output of NAMELIST is currently in uppercase but will someday
- be lowercase (when a `libg77' is written), but that seems to be
- overkill for a product in beta test.
- 
-    Note 2: Rules for InitialCaps names are:
- 
-    - Must be a single uppercase letter, *or*
- 
-    - Must start with an uppercase letter and contain at least one
-      lowercase letter.
- 
-    So `A', `Ab', `ABc', `AbC', and `Abc' are valid InitialCaps names,
- but `AB', `A2', and `ABC' are not.  Note that most, but not all,
- built-in names meet these requirements--the exceptions are some of the
- two-letter format specifiers, such as `BN' and `BZ'.
- 
-    Here are the names of the corresponding command-line options:
- 
-      A0: -fsource-case-preserve
-      A1: -fsource-case-upper
-      A2: -fsource-case-lower
-      
-      B0: -fmatch-case-any
-      B1: -fmatch-case-upper
-      B2: -fmatch-case-lower
-      B3: -fmatch-case-initcap
-      
-      C0: -fintrin-case-any
-      C1: -fintrin-case-upper
-      C2: -fintrin-case-lower
-      C3: -fintrin-case-initcap
-      
-      D0: -fsymbol-case-any
-      D1: -fsymbol-case-upper
-      D2: -fsymbol-case-lower
-      D3: -fsymbol-case-initcap
- 
-    Useful combinations of the above settings, along with abbreviated
- option names that set some of these combinations all at once:
- 
-       1: A0--  B0---  C0---  D0---    -fcase-preserve
-       2: A0--  B0---  C0---  D-1--
-       3: A0--  B0---  C0---  D--2-
-       4: A0--  B0---  C0---  D---3
-       5: A0--  B0---  C-1--  D0---
-       6: A0--  B0---  C-1--  D-1--
-       7: A0--  B0---  C-1--  D--2-
-       8: A0--  B0---  C-1--  D---3
-       9: A0--  B0---  C--2-  D0---
-      10: A0--  B0---  C--2-  D-1--
-      11: A0--  B0---  C--2-  D--2-
-      12: A0--  B0---  C--2-  D---3
-      13: A0--  B0---  C---3  D0---
-      14: A0--  B0---  C---3  D-1--
-      15: A0--  B0---  C---3  D--2-
-      16: A0--  B0---  C---3  D---3
-      17: A0--  B-1--  C0---  D0---
-      18: A0--  B-1--  C0---  D-1--
-      19: A0--  B-1--  C0---  D--2-
-      20: A0--  B-1--  C0---  D---3
-      21: A0--  B-1--  C-1--  D0---
-      22: A0--  B-1--  C-1--  D-1--    -fcase-strict-upper
-      23: A0--  B-1--  C-1--  D--2-
-      24: A0--  B-1--  C-1--  D---3
-      25: A0--  B-1--  C--2-  D0---
-      26: A0--  B-1--  C--2-  D-1--
-      27: A0--  B-1--  C--2-  D--2-
-      28: A0--  B-1--  C--2-  D---3
-      29: A0--  B-1--  C---3  D0---
-      30: A0--  B-1--  C---3  D-1--
-      31: A0--  B-1--  C---3  D--2-
-      32: A0--  B-1--  C---3  D---3
-      33: A0--  B--2-  C0---  D0---
-      34: A0--  B--2-  C0---  D-1--
-      35: A0--  B--2-  C0---  D--2-
-      36: A0--  B--2-  C0---  D---3
-      37: A0--  B--2-  C-1--  D0---
-      38: A0--  B--2-  C-1--  D-1--
-      39: A0--  B--2-  C-1--  D--2-
-      40: A0--  B--2-  C-1--  D---3
-      41: A0--  B--2-  C--2-  D0---
-      42: A0--  B--2-  C--2-  D-1--
-      43: A0--  B--2-  C--2-  D--2-    -fcase-strict-lower
-      44: A0--  B--2-  C--2-  D---3
-      45: A0--  B--2-  C---3  D0---
-      46: A0--  B--2-  C---3  D-1--
-      47: A0--  B--2-  C---3  D--2-
-      48: A0--  B--2-  C---3  D---3
-      49: A0--  B---3  C0---  D0---
-      50: A0--  B---3  C0---  D-1--
-      51: A0--  B---3  C0---  D--2-
-      52: A0--  B---3  C0---  D---3
-      53: A0--  B---3  C-1--  D0---
-      54: A0--  B---3  C-1--  D-1--
-      55: A0--  B---3  C-1--  D--2-
-      56: A0--  B---3  C-1--  D---3
-      57: A0--  B---3  C--2-  D0---
-      58: A0--  B---3  C--2-  D-1--
-      59: A0--  B---3  C--2-  D--2-
-      60: A0--  B---3  C--2-  D---3
-      61: A0--  B---3  C---3  D0---
-      62: A0--  B---3  C---3  D-1--
-      63: A0--  B---3  C---3  D--2-
-      64: A0--  B---3  C---3  D---3    -fcase-initcap
-      65: A-1-  B01--  C01--  D01--    -fcase-upper
-      66: A--2  B0-2-  C0-2-  D0-2-    -fcase-lower
- 
-    Number 22 is the "strict" ANSI FORTRAN 77 model wherein all input
- (except comments, character constants, and Hollerith strings) must be
- entered in uppercase.  Use `-fcase-strict-upper' to specify this
- combination.
- 
-    Number 43 is like Number 22 except all input must be lowercase.  Use
- `-fcase-strict-lower' to specify this combination.
- 
-    Number 65 is the "classic" ANSI FORTRAN 77 model as implemented on
- many non-UNIX machines whereby all the source is translated to
- uppercase.  Use `-fcase-upper' to specify this combination.
- 
-    Number 66 is the "canonical" UNIX model whereby all the source is
- translated to lowercase.  Use `-fcase-lower' to specify this
- combination.
- 
-    There are a few nearly useless combinations:
- 
-      67: A-1-  B01--  C01--  D--2-
-      68: A-1-  B01--  C01--  D---3
-      69: A-1-  B01--  C--23  D01--
-      70: A-1-  B01--  C--23  D--2-
-      71: A-1-  B01--  C--23  D---3
-      72: A--2  B01--  C0-2-  D-1--
-      73: A--2  B01--  C0-2-  D---3
-      74: A--2  B01--  C-1-3  D0-2-
-      75: A--2  B01--  C-1-3  D-1--
-      76: A--2  B01--  C-1-3  D---3
- 
-    The above allow some programs to be compiled but with restrictions
- that make most useful programs impossible: Numbers 67 and 72 warn about
- _any_ user-defined symbol names (such as `SUBROUTINE FOO'); Numbers 68
- and 73 warn about any user-defined symbol names longer than one
- character that don't have at least one non-alphabetic character after
- the first; Numbers 69 and 74 disallow any references to intrinsics; and
- Numbers 70, 71, 75, and 76 are combinations of the restrictions in
- 67+69, 68+69, 72+74, and 73+74, respectively.
- 
-    All redundant combinations are shown in the above tables anyplace
- where more than one setting is shown for a low-level switch.  For
- example, `B0-2-' means either setting 0 or 2 is valid for switch B.
- The "proper" setting in such a case is the one that copies the setting
- of switch A--any other setting might slightly reduce the speed of the
- compiler, though possibly to an unmeasurable extent.
- 
-    All remaining combinations are useless in that they prevent
- successful compilation of non-null source files (source files with
- something other than comments).
- 
- 
- File: g77.info,  Node: VXT Fortran,  Next: Fortran 90,  Prev: Case Sensitivity,  Up: Other Dialects
- 
- VXT Fortran
- ===========
- 
-    `g77' supports certain constructs that have different meanings in
- VXT Fortran than they do in the GNU Fortran language.
- 
-    Generally, this manual uses the invented term VXT Fortran to refer
- VAX FORTRAN (circa v4).  That compiler offered many popular features,
- though not necessarily those that are specific to the VAX processor
- architecture, the VMS operating system, or Digital Equipment
- Corporation's Fortran product line.  (VAX and VMS probably are
- trademarks of Digital Equipment Corporation.)
- 
-    An extension offered by a Digital Fortran product that also is
- offered by several other Fortran products for different kinds of
- systems is probably going to be considered for inclusion in `g77'
- someday, and is considered a VXT Fortran feature.
- 
-    The `-fvxt' option generally specifies that, where the meaning of a
- construct is ambiguous (means one thing in GNU Fortran and another in
- VXT Fortran), the VXT Fortran meaning is to be assumed.
- 
- * Menu:
- 
- * Double Quote Meaning::  `"2000' as octal constant.
- * Exclamation Point::     `!' in column 6.
- 
- 
- File: g77.info,  Node: Double Quote Meaning,  Next: Exclamation Point,  Up: VXT Fortran
- 
- Meaning of Double Quote
- -----------------------
- 
-    `g77' treats double-quote (`"') as beginning an octal constant of
- `INTEGER(KIND=1)' type when the `-fvxt' option is specified.  The form
- of this octal constant is
- 
-      "OCTAL-DIGITS
- 
- where OCTAL-DIGITS is a nonempty string of characters in the set
- `01234567'.
- 
-    For example, the `-fvxt' option permits this:
- 
-      PRINT *, "20
-      END
- 
- The above program would print the value `16'.
- 
-    *Note Integer Type::, for information on the preferred construct for
- integer constants specified using GNU Fortran's octal notation.
- 
-    (In the GNU Fortran language, the double-quote character (`"')
- delimits a character constant just as does apostrophe (`'').  There is
- no way to allow both constructs in the general case, since statements
- like `PRINT *,"2000 !comment?"' would be ambiguous.)
- 
- 
- File: g77.info,  Node: Exclamation Point,  Prev: Double Quote Meaning,  Up: VXT Fortran
- 
- Meaning of Exclamation Point in Column 6
- ----------------------------------------
- 
-    `g77' treats an exclamation point (`!') in column 6 of a fixed-form
- source file as a continuation character rather than as the beginning of
- a comment (as it does in any other column) when the `-fvxt' option is
- specified.
- 
-    The following program, when run, prints a message indicating whether
- it is interpreted according to GNU Fortran (and Fortran 90) rules or
- VXT Fortran rules:
- 
-      C234567  (This line begins in column 1.)
-            I = 0
-           !1
-            IF (I.EQ.0) PRINT *, ' I am a VXT Fortran program'
-            IF (I.EQ.1) PRINT *, ' I am a Fortran 90 program'
-            IF (I.LT.0 .OR. I.GT.1) PRINT *, ' I am a HAL 9000 computer'
-            END
- 
-    (In the GNU Fortran and Fortran 90 languages, exclamation point is a
- valid character and, unlike space (<SPC>) or zero (`0'), marks a line
- as a continuation line when it appears in column 6.)
- 
- 
- File: g77.info,  Node: Fortran 90,  Next: Pedantic Compilation,  Prev: VXT Fortran,  Up: Other Dialects
- 
- Fortran 90
- ==========
- 
-    The GNU Fortran language includes a number of features that are part
- of Fortran 90, even when the `-ff90' option is not specified.  The
- features enabled by `-ff90' are intended to be those that, when `-ff90'
- is not specified, would have another meaning to `g77'--usually meaning
- something invalid in the GNU Fortran language.
- 
-    So, the purpose of `-ff90' is not to specify whether `g77' is to
- gratuitously reject Fortran 90 constructs.  The `-pedantic' option
- specified with `-fno-f90' is intended to do that, although its
- implementation is certainly incomplete at this point.
- 
-    When `-ff90' is specified:
- 
-    * The type of `REAL(EXPR)' and `AIMAG(EXPR)', where EXPR is
-      `COMPLEX' type, is the same type as the real part of EXPR.
- 
-      For example, assuming `Z' is type `COMPLEX(KIND=2)', `REAL(Z)'
-      would return a value of type `REAL(KIND=2)', not of type
-      `REAL(KIND=1)', since `-ff90' is specified.
- 
- 
- File: g77.info,  Node: Pedantic Compilation,  Next: Distensions,  Prev: Fortran 90,  Up: Other Dialects
- 
- Pedantic Compilation
- ====================
- 
-    The `-fpedantic' command-line option specifies that `g77' is to warn
- about code that is not standard-conforming.  This is useful for finding
- some extensions `g77' accepts that other compilers might not accept.
- (Note that the `-pedantic' and `-pedantic-errors' options always imply
- `-fpedantic'.)
- 
-    With `-fno-f90' in force, ANSI FORTRAN 77 is used as the standard
- for conforming code.  With `-ff90' in force, Fortran 90 is used.
- 
-    The constructs for which `g77' issues diagnostics when `-fpedantic'
- and `-fno-f90' are in force are:
- 
-    * Automatic arrays, as in
- 
-           SUBROUTINE X(N)
-           REAL A(N)
-           ...
- 
-      where `A' is not listed in any `ENTRY' statement, and thus is not
-      a dummy argument.
- 
-    * The commas in `READ (5), I' and `WRITE (10), J'.
- 
-      These commas are disallowed by FORTRAN 77, but, while strictly
-      superfluous, are syntactically elegant, especially given that
-      commas are required in statements such as `READ 99, I' and `PRINT
-      *, J'.  Many compilers permit the superfluous commas for this
-      reason.
- 
-    * `DOUBLE COMPLEX', either explicitly or implicitly.
- 
-      An explicit use of this type is via a `DOUBLE COMPLEX' or
-      `IMPLICIT DOUBLE COMPLEX' statement, for examples.
- 
-      An example of an implicit use is the expression `C*D', where `C'
-      is `COMPLEX(KIND=1)' and `D' is `DOUBLE PRECISION'.  This
-      expression is prohibited by ANSI FORTRAN 77 because the rules of
-      promotion would suggest that it produce a `DOUBLE COMPLEX'
-      result--a type not provided for by that standard.
- 
-    * Automatic conversion of numeric expressions to `INTEGER(KIND=1)'
-      in contexts such as:
- 
-         - Array-reference indexes.
- 
-         - Alternate-return values.
- 
-         - Computed `GOTO'.
- 
-         - `FORMAT' run-time expressions (not yet supported).
- 
-         - Dimension lists in specification statements.
- 
-         - Numbers for I/O statements (such as `READ (UNIT=3.2), I')
- 
-         - Sizes of `CHARACTER' entities in specification statements.
- 
-         - Kind types in specification entities (a Fortran 90 feature).
- 
-         - Initial, terminal, and incrementation parameters for
-           implied-`DO' constructs in `DATA' statements.
- 
-    * Automatic conversion of `LOGICAL' expressions to `INTEGER' in
-      contexts such as arithmetic `IF' (where `COMPLEX' expressions are
-      disallowed anyway).
- 
-    * Zero-size array dimensions, as in:
- 
-           INTEGER I(10,20,4:2)
- 
-    * Zero-length `CHARACTER' entities, as in:
- 
-           PRINT *, ''
- 
-    * Substring operators applied to character constants and named
-      constants, as in:
- 
-           PRINT *, 'hello'(3:5)
- 
-    * Null arguments passed to statement function, as in:
- 
-           PRINT *, FOO(,3)
- 
-    * Disagreement among program units regarding whether a given `COMMON'
-      area is `SAVE'd (for targets where program units in a single source
-      file are "glued" together as they typically are for UNIX
-      development environments).
- 
-    * Disagreement among program units regarding the size of a named
-      `COMMON' block.
- 
-    * Specification statements following first `DATA' statement.
- 
-      (In the GNU Fortran language, `DATA I/1/' may be followed by
-      `INTEGER J', but not `INTEGER I'.  The `-fpedantic' option
-      disallows both of these.)
- 
-    * Semicolon as statement separator, as in:
- 
-           CALL FOO; CALL BAR
- 
-    * Use of `&' in column 1 of fixed-form source (to indicate
-      continuation).
- 
-    * Use of `CHARACTER' constants to initialize numeric entities, and
-      vice versa.
- 
-    * Expressions having two arithmetic operators in a row, such as
-      `X*-Y'.
- 
-    If `-fpedantic' is specified along with `-ff90', the following
- constructs result in diagnostics:
- 
-    * Use of semicolon as a statement separator on a line that has an
-      `INCLUDE' directive.
- 
- 
- File: g77.info,  Node: Distensions,  Prev: Pedantic Compilation,  Up: Other Dialects
- 
- Distensions
- ===========
- 
-    The `-fugly-*' command-line options determine whether certain
- features supported by VAX FORTRAN and other such compilers, but
- considered too ugly to be in code that can be changed to use safer
- and/or more portable constructs, are accepted.  These are humorously
- referred to as "distensions", extensions that just plain look ugly in
- the harsh light of day.
- 
- * Menu:
- 
- * Ugly Implicit Argument Conversion::  Disabled via `-fno-ugly-args'.
- * Ugly Assumed-Size Arrays::           Enabled via `-fugly-assumed'.
- * Ugly Null Arguments::                Enabled via `-fugly-comma'.
- * Ugly Complex Part Extraction::       Enabled via `-fugly-complex'.
- * Ugly Conversion of Initializers::    Disabled via `-fno-ugly-init'.
- * Ugly Integer Conversions::           Enabled via `-fugly-logint'.
- * Ugly Assigned Labels::               Enabled via `-fugly-assign'.
- 
- 
- File: g77.info,  Node: Ugly Implicit Argument Conversion,  Next: Ugly Assumed-Size Arrays,  Up: Distensions
- 
- Implicit Argument Conversion
- ----------------------------
- 
-    The `-fno-ugly-args' option disables passing typeless and Hollerith
- constants as actual arguments in procedure invocations.  For example:
- 
-      CALL FOO(4HABCD)
-      CALL BAR('123'O)
- 
- These constructs can be too easily used to create non-portable code,
- but are not considered as "ugly" as others.  Further, they are widely
- used in existing Fortran source code in ways that often are quite
- portable.  Therefore, they are enabled by default.
- 
- 
- File: g77.info,  Node: Ugly Assumed-Size Arrays,  Next: Ugly Null Arguments,  Prev: Ugly Implicit Argument Conversion,  Up: Distensions
- 
- Ugly Assumed-Size Arrays
- ------------------------
- 
-    The `-fugly-assumed' option enables the treatment of any array with
- a final dimension specified as `1' as an assumed-size array, as if `*'
- had been specified instead.
- 
-    For example, `DIMENSION X(1)' is treated as if it had read
- `DIMENSION X(*)' if `X' is listed as a dummy argument in a preceding
- `SUBROUTINE', `FUNCTION', or `ENTRY' statement in the same program unit.
- 
-    Use an explicit lower bound to avoid this interpretation.  For
- example, `DIMENSION X(1:1)' is never treated as if it had read
- `DIMENSION X(*)' or `DIMENSION X(1:*)'.  Nor is `DIMENSION X(2-1)'
- affected by this option, since that kind of expression is unlikely to
- have been intended to designate an assumed-size array.
- 
-    This option is used to prevent warnings being issued about apparent
- out-of-bounds reference such as `X(2) = 99'.
- 
-    It also prevents the array from being used in contexts that disallow
- assumed-size arrays, such as `PRINT *,X'.  In such cases, a diagnostic
- is generated and the source file is not compiled.
- 
-    The construct affected by this option is used only in old code that
- pre-exists the widespread acceptance of adjustable and assumed-size
- arrays in the Fortran community.
- 
-    _Note:_ This option does not affect how `DIMENSION X(1)' is treated
- if `X' is listed as a dummy argument only _after_ the `DIMENSION'
- statement (presumably in an `ENTRY' statement).  For example,
- `-fugly-assumed' has no effect on the following program unit:
- 
-      SUBROUTINE X
-      REAL A(1)
-      RETURN
-      ENTRY Y(A)
-      PRINT *, A
-      END
- 
- 
- File: g77.info,  Node: Ugly Complex Part Extraction,  Next: Ugly Conversion of Initializers,  Prev: Ugly Null Arguments,  Up: Distensions
- 
- Ugly Complex Part Extraction
- ----------------------------
- 
-    The `-fugly-complex' option enables use of the `REAL()' and `AIMAG()'
- intrinsics with arguments that are `COMPLEX' types other than
- `COMPLEX(KIND=1)'.
- 
-    With `-ff90' in effect, these intrinsics return the unconverted real
- and imaginary parts (respectively) of their argument.
- 
-    With `-fno-f90' in effect, these intrinsics convert the real and
- imaginary parts to `REAL(KIND=1)', and return the result of that
- conversion.
- 
-    Due to this ambiguity, the GNU Fortran language defines these
- constructs as invalid, except in the specific case where they are
- entirely and solely passed as an argument to an invocation of the
- `REAL()' intrinsic.  For example,
- 
-      REAL(REAL(Z))
- 
- is permitted even when `Z' is `COMPLEX(KIND=2)' and `-fno-ugly-complex'
- is in effect, because the meaning is clear.
- 
-    `g77' enforces this restriction, unless `-fugly-complex' is
- specified, in which case the appropriate interpretation is chosen and
- no diagnostic is issued.
- 
-    *Note CMPAMBIG::, for information on how to cope with existing code
- with unclear expectations of `REAL()' and `AIMAG()' with
- `COMPLEX(KIND=2)' arguments.
- 
-    *Note RealPart Intrinsic::, for information on the `REALPART()'
- intrinsic, used to extract the real part of a complex expression
- without conversion.  *Note ImagPart Intrinsic::, for information on the
- `IMAGPART()' intrinsic, used to extract the imaginary part of a complex
- expression without conversion.
- 
- 
- File: g77.info,  Node: Ugly Null Arguments,  Next: Ugly Complex Part Extraction,  Prev: Ugly Assumed-Size Arrays,  Up: Distensions
- 
- Ugly Null Arguments
- -------------------
- 
-    The `-fugly-comma' option enables use of a single trailing comma to
- mean "pass an extra trailing null argument" in a list of actual
- arguments to an external procedure, and use of an empty list of
- arguments to such a procedure to mean "pass a single null argument".
- 
-    (Null arguments often are used in some procedure-calling schemes to
- indicate omitted arguments.)
- 
-    For example, `CALL FOO(,)' means "pass two null arguments", rather
- than "pass one null argument".  Also, `CALL BAR()' means "pass one null
- argument".
- 
-    This construct is considered "ugly" because it does not provide an
- elegant way to pass a single null argument that is syntactically
- distinct from passing no arguments.  That is, this construct changes
- the meaning of code that makes no use of the construct.
- 
-    So, with `-fugly-comma' in force, `CALL FOO()' and `I = JFUNC()'
- pass a single null argument, instead of passing no arguments as
- required by the Fortran 77 and 90 standards.
- 
-    _Note:_ Many systems gracefully allow the case where a procedure
- call passes one extra argument that the called procedure does not
- expect.
- 
-    So, in practice, there might be no difference in the behavior of a
- program that does `CALL FOO()' or `I = JFUNC()' and is compiled with
- `-fugly-comma' in force as compared to its behavior when compiled with
- the default, `-fno-ugly-comma', in force, assuming `FOO' and `JFUNC' do
- not expect any arguments to be passed.
- 
- 
- File: g77.info,  Node: Ugly Conversion of Initializers,  Next: Ugly Integer Conversions,  Prev: Ugly Complex Part Extraction,  Up: Distensions
- 
- Ugly Conversion of Initializers
- -------------------------------
- 
-    The constructs disabled by `-fno-ugly-init' are:
- 
-    * Use of Hollerith and typeless constants in contexts where they set
-      initial (compile-time) values for variables, arrays, and named
-      constants--that is, `DATA' and `PARAMETER' statements, plus
-      type-declaration statements specifying initial values.
- 
-      Here are some sample initializations that are disabled by the
-      `-fno-ugly-init' option:
- 
-           PARAMETER (VAL='9A304FFE'X)
-           REAL*8 STRING/8HOUTPUT00/
-           DATA VAR/4HABCD/
- 
-    * In the same contexts as above, use of character constants to
-      initialize numeric items and vice versa (one constant per item).
- 
-      Here are more sample initializations that are disabled by the
-      `-fno-ugly-init' option:
- 
-           INTEGER IA
-           CHARACTER BELL
-           PARAMETER (IA = 'A')
-           PARAMETER (BELL = 7)
- 
-    * Use of Hollerith and typeless constants on the right-hand side of
-      assignment statements to numeric types, and in other contexts
-      (such as passing arguments in invocations of intrinsic procedures
-      and statement functions) that are treated as assignments to known
-      types (the dummy arguments, in these cases).
- 
-      Here are sample statements that are disabled by the
-      `-fno-ugly-init' option:
- 
-           IVAR = 4HABCD
-           PRINT *, IMAX0(2HAB, 2HBA)
- 
-    The above constructs, when used, can tend to result in non-portable
- code.  But, they are widely used in existing Fortran code in ways that
- often are quite portable.  Therefore, they are enabled by default.
- 
- 
- File: g77.info,  Node: Ugly Integer Conversions,  Next: Ugly Assigned Labels,  Prev: Ugly Conversion of Initializers,  Up: Distensions
- 
- Ugly Integer Conversions
- ------------------------
- 
-    The constructs enabled via `-fugly-logint' are:
- 
-    * Automatic conversion between `INTEGER' and `LOGICAL' as dictated by
-      context (typically implies nonportable dependencies on how a
-      particular implementation encodes `.TRUE.' and `.FALSE.').
- 
-    * Use of a `LOGICAL' variable in `ASSIGN' and assigned-`GOTO'
-      statements.
- 
-    The above constructs are disabled by default because use of them
- tends to lead to non-portable code.  Even existing Fortran code that
- uses that often turns out to be non-portable, if not outright buggy.
- 
-    Some of this is due to differences among implementations as far as
- how `.TRUE.' and `.FALSE.' are encoded as `INTEGER' values--Fortran
- code that assumes a particular coding is likely to use one of the above
- constructs, and is also likely to not work correctly on implementations
- using different encodings.
- 
-    *Note Equivalence Versus Equality::, for more information.
- 
- 
- File: g77.info,  Node: Ugly Assigned Labels,  Prev: Ugly Integer Conversions,  Up: Distensions
- 
- Ugly Assigned Labels
- --------------------
- 
-    The `-fugly-assign' option forces `g77' to use the same storage for
- assigned labels as it would for a normal assignment to the same
- variable.
- 
-    For example, consider the following code fragment:
- 
-      I = 3
-      ASSIGN 10 TO I
- 
- Normally, for portability and improved diagnostics, `g77' reserves
- distinct storage for a "sibling" of `I', used only for `ASSIGN'
- statements to that variable (along with the corresponding
- assigned-`GOTO' and assigned-`FORMAT'-I/O statements that reference the
- variable).
- 
-    However, some code (that violates the ANSI FORTRAN 77 standard)
- attempts to copy assigned labels among variables involved with `ASSIGN'
- statements, as in:
- 
-      ASSIGN 10 TO I
-      ISTATE(5) = I
-      ...
-      J = ISTATE(ICUR)
-      GOTO J
- 
- Such code doesn't work under `g77' unless `-fugly-assign' is specified
- on the command-line, ensuring that the value of `I' referenced in the
- second line is whatever value `g77' uses to designate statement label
- `10', so the value may be copied into the `ISTATE' array, later
- retrieved into a variable of the appropriate type (`J'), and used as
- the target of an assigned-`GOTO' statement.
- 
-    _Note:_ To avoid subtle program bugs, when `-fugly-assign' is
- specified, `g77' requires the type of variables specified in
- assigned-label contexts _must_ be the same type returned by `%LOC()'.
- On many systems, this type is effectively the same as
- `INTEGER(KIND=1)', while, on others, it is effectively the same as
- `INTEGER(KIND=2)'.
- 
-    Do _not_ depend on `g77' actually writing valid pointers to these
- variables, however.  While `g77' currently chooses that implementation,
- it might be changed in the future.
- 
-    *Note Assigned Statement Labels (ASSIGN and GOTO): Assigned
- Statement Labels, for implementation details on assigned-statement
- labels.
- 
- 
- File: g77.info,  Node: Compiler,  Next: Other Dialects,  Prev: Language,  Up: Top
- 
- The GNU Fortran Compiler
- ************************
- 
-    The GNU Fortran compiler, `g77', supports programs written in the
- GNU Fortran language and in some other dialects of Fortran.
- 
-    Some aspects of how `g77' works are universal regardless of dialect,
- and yet are not properly part of the GNU Fortran language itself.
- These are described below.
- 
-    _Note: This portion of the documentation definitely needs a lot of
- work!_
- 
- * Menu:
- 
- * Compiler Limits::
- * Run-time Environment Limits::
- * Compiler Types::
- * Compiler Constants::
- * Compiler Intrinsics::
- 
- 
- File: g77.info,  Node: Compiler Limits,  Next: Run-time Environment Limits,  Up: Compiler
- 
- Compiler Limits
- ===============
- 
-    `g77', as with GNU tools in general, imposes few arbitrary
- restrictions on lengths of identifiers, number of continuation lines,
- number of external symbols in a program, and so on.
- 
-    For example, some other Fortran compiler have an option (such as
- `-NlX') to increase the limit on the number of continuation lines.
- Also, some Fortran compilation systems have an option (such as `-NxX')
- to increase the limit on the number of external symbols.
- 
-    `g77', `gcc', and GNU `ld' (the GNU linker) have no equivalent
- options, since they do not impose arbitrary limits in these areas.
- 
-    `g77' does currently limit the number of dimensions in an array to
- the same degree as do the Fortran standards--seven (7).  This
- restriction might be lifted in a future version.
- 
- 
- File: g77.info,  Node: Run-time Environment Limits,  Next: Compiler Types,  Prev: Compiler Limits,  Up: Compiler
- 
- Run-time Environment Limits
- ===========================
- 
-    As a portable Fortran implementation, `g77' offers its users direct
- access to, and otherwise depends upon, the underlying facilities of the
- system used to build `g77', the system on which `g77' itself is used to
- compile programs, and the system on which the `g77'-compiled program is
- actually run.  (For most users, the three systems are of the same
- type--combination of operating environment and hardware--often the same
- physical system.)
- 
-    The run-time environment for a particular system inevitably imposes
- some limits on a program's use of various system facilities.  These
- limits vary from system to system.
- 
-    Even when such limits might be well beyond the possibility of being
- encountered on a particular system, the `g77' run-time environment has
- certain built-in limits, usually, but not always, stemming from
- intrinsics with inherently limited interfaces.
- 
-    Currently, the `g77' run-time environment does not generally offer a
- less-limiting environment by augmenting the underlying system's own
- environment.
- 
-    Therefore, code written in the GNU Fortran language, while
- syntactically and semantically portable, might nevertheless make
- non-portable assumptions about the run-time environment--assumptions
- that prove to be false for some particular environments.
- 
-    The GNU Fortran language, the `g77' compiler and run-time
- environment, and the `g77' documentation do not yet offer comprehensive
- portable work-arounds for such limits, though programmers should be
- able to find their own in specific instances.
- 
-    Not all of the limitations are described in this document.  Some of
- the known limitations include:
- 
- * Menu:
- 
- * Timer Wraparounds::
- * Year 2000 (Y2K) Problems::
- * Array Size::
- * Character-variable Length::
- * Year 10000 (Y10K) Problems::
- 
- 
- File: g77.info,  Node: Timer Wraparounds,  Next: Year 2000 (Y2K) Problems,  Up: Run-time Environment Limits
- 
- Timer Wraparounds
- -----------------
- 
-    Intrinsics that return values computed from system timers, whether
- elapsed (wall-clock) timers, process CPU timers, or other kinds of
- timers, are prone to experiencing wrap-around errors (or returning
- wrapped-around values from successive calls) due to insufficient ranges
- offered by the underlying system's timers.
- 
-    Some of the symptoms of such behaviors include apparently negative
- time being computed for a duration, an extremely short amount of time
- being computed for a long duration, and an extremely long amount of
- time being computed for a short duration.
- 
-    See the following for intrinsics known to have potential problems in
- these areas on at least some systems: *Note CPU_Time Intrinsic::, *Note
- DTime Intrinsic (function)::, *Note DTime Intrinsic (subroutine)::,
- *Note ETime Intrinsic (function)::, *Note ETime Intrinsic
- (subroutine)::, *Note MClock Intrinsic::, *Note MClock8 Intrinsic::,
- *Note Secnds Intrinsic::, *Note Second Intrinsic (function)::, *Note
- Second Intrinsic (subroutine)::, *Note System_Clock Intrinsic::, *Note
- Time Intrinsic (UNIX)::, *Note Time Intrinsic (VXT)::, *Note Time8
- Intrinsic::.
- 
- 
- File: g77.info,  Node: Year 2000 (Y2K) Problems,  Next: Array Size,  Prev: Timer Wraparounds,  Up: Run-time Environment Limits
- 
- Year 2000 (Y2K) Problems
- ------------------------
- 
-    While the `g77' compiler itself is believed to be Year-2000 (Y2K)
- compliant, some intrinsics are not, and, potentially, some underlying
- systems are not, perhaps rendering some Y2K-compliant intrinsics
- non-compliant when used on those particular systems.
- 
-    Fortran code that uses non-Y2K-compliant intrinsics (listed below)
- is, itself, almost certainly not compliant, and should be modified to
- use Y2K-compliant intrinsics instead.
- 
-    Fortran code that uses no non-Y2K-compliant intrinsics, but which
- currently is running on a non-Y2K-compliant system, can be made more
- Y2K compliant by compiling and linking it for use on a new
- Y2K-compliant system, such as a new version of an old,
- non-Y2K-compliant, system.
- 
-    Currently, information on Y2K and related issues is being maintained
- at `http://www.gnu.org/software/year2000-list.html'.
- 
-    See the following for intrinsics known to have potential problems in
- these areas on at least some systems: *Note Date Intrinsic::, *Note
- IDate Intrinsic (VXT)::.
- 
-    The `libg2c' library shipped with any `g77' that warns about
- invocation of a non-Y2K-compliant intrinsic has renamed the `EXTERNAL'
- procedure names of those intrinsics.  This is done so that the `libg2c'
- implementations of these intrinsics cannot be directly linked to as
- `EXTERNAL' names (which normally would avoid the non-Y2K-intrinsic
- warning).
- 
-    The renamed forms of the `EXTERNAL' names of these renamed procedures
- may be linked to by appending the string `_y2kbug' to the name of the
- procedure in the source code.  For example:
- 
-      CHARACTER*20 STR
-      INTEGER YY, MM, DD
-      EXTERNAL DATE_Y2KBUG, VXTIDATE_Y2KBUG
-      CALL DATE_Y2KBUG (STR)
-      CALL VXTIDATE_Y2KBUG (MM, DD, YY)
- 
-    (Note that the `EXTERNAL' statement is not actually required, since
- the modified names are not recognized as intrinsics by the current
- version of `g77'.  But it is shown in this specific case, for purposes
- of illustration.)
- 
-    The renaming of `EXTERNAL' procedure names of these intrinsics
- causes unresolved references at link time.  For example, `EXTERNAL
- DATE; CALL DATE(STR)' is normally compiled by `g77' as, in C,
- `date_(&str, 20);'.  This, in turn, links to the `date_' procedure in
- the `libE77' portion of `libg2c', which purposely calls a nonexistent
- procedure named `G77_date_y2kbuggy_0'.  The resulting link-time error
- is designed, via this name, to encourage the programmer to look up the
- index entries to this portion of the `g77' documentation.
- 
-    Generally, we recommend that the `EXTERNAL' method of invoking
- procedures in `libg2c' _not_ be used.  When used, some of the
- correctness checking normally performed by `g77' is skipped.
- 
-    In particular, it is probably better to use the `INTRINSIC' method
- of invoking non-Y2K-compliant procedures, so anyone compiling the code
- can quickly notice the potential Y2K problems (via the warnings
- printing by `g77') without having to even look at the code itself.
- 
-    If there are problems linking `libg2c' to code compiled by `g77'
- that involve the string `y2kbug', and these are not explained above,
- that probably indicates that a version of `libg2c' older than `g77' is
- being linked to, or that the new library is being linked to code
- compiled by an older version of `g77'.
- 
-    That's because, as of the version that warns about non-Y2K-compliant
- intrinsic invocation, `g77' references the `libg2c' implementations of
- those intrinsics using new names, containing the string `y2kbug'.
- 
-    So, linking newly-compiled code (invoking one of the intrinsics in
- question) to an old library might yield an unresolved reference to
- `G77_date_y2kbug_0'.  (The old library calls it `G77_date_0'.)
- 
-    Similarly, linking previously-compiled code to a new library might
- yield an unresolved reference to `G77_vxtidate_0'.  (The new library
- calls it `G77_vxtidate_y2kbug_0'.)
- 
-    The proper fix for the above problems is to obtain the latest
- release of `g77' and related products (including `libg2c') and install
- them on all systems, then recompile, relink, and install (as
- appropriate) all existing Fortran programs.
- 
-    (Normally, this sort of renaming is steadfastly avoided.  In this
- case, however, it seems more important to highlight potential Y2K
- problems than to ease the transition of potentially non-Y2K-compliant
- code to new versions of `g77' and `libg2c'.)
- 
- 
- File: g77.info,  Node: Array Size,  Next: Character-variable Length,  Prev: Year 2000 (Y2K) Problems,  Up: Run-time Environment Limits
- 
- Array Size
- ----------
- 
-    Currently, `g77' uses the default `INTEGER' type for array indexes,
- which limits the sizes of single-dimension arrays on systems offering a
- larger address space than can be addressed by that type.  (That `g77'
- puts all arrays in memory could be considered another limitation--it
- could use large temporary files--but that decision is left to the
- programmer as an implementation choice by most Fortran implementations.)
- 
-    It is not yet clear whether this limitation never, sometimes, or
- always applies to the sizes of multiple-dimension arrays as a whole.
- 
-    For example, on a system with 64-bit addresses and 32-bit default
- `INTEGER', an array with a size greater than can be addressed by a
- 32-bit offset can be declared using multiple dimensions.  Such an array
- is therefore larger than a single-dimension array can be, on the same
- system.
- 
-    Whether large multiple-dimension arrays are reliably supported
- depends mostly on the `gcc' back end (code generator) used by `g77',
- and has not yet been fully investigated.
- 
- 
- File: g77.info,  Node: Character-variable Length,  Next: Year 10000 (Y10K) Problems,  Prev: Array Size,  Up: Run-time Environment Limits
- 
- Character-variable Length
- -------------------------
- 
-    Currently, `g77' uses the default `INTEGER' type for the lengths of
- `CHARACTER' variables and array elements.
- 
-    This means that, for example, a system with a 64-bit address space
- and a 32-bit default `INTEGER' type does not, under `g77', support a
- `CHARACTER*N' declaration where N is greater than 2147483647.
- 
- 
- File: g77.info,  Node: Year 10000 (Y10K) Problems,  Prev: Character-variable Length,  Up: Run-time Environment Limits
- 
- Year 10000 (Y10K) Problems
- --------------------------
- 
-    Most intrinsics returning, or computing values based on, date
- information are prone to Year-10000 (Y10K) problems, due to supporting
- only 4 digits for the year.
- 
-    See the following for examples: *Note FDate Intrinsic (function)::,
- *Note FDate Intrinsic (subroutine)::, *Note IDate Intrinsic (UNIX)::,
- *Note Time Intrinsic (VXT)::, *Note Date_and_Time Intrinsic::.
- 
- 
- File: g77.info,  Node: Compiler Types,  Next: Compiler Constants,  Prev: Run-time Environment Limits,  Up: Compiler
- 
- Compiler Types
- ==============
- 
-    Fortran implementations have a fair amount of freedom given them by
- the standard as far as how much storage space is used and how much
- precision and range is offered by the various types such as
- `LOGICAL(KIND=1)', `INTEGER(KIND=1)', `REAL(KIND=1)', `REAL(KIND=2)',
- `COMPLEX(KIND=1)', and `CHARACTER'.  Further, many compilers offer
- so-called `*N' notation, but the interpretation of N varies across
- compilers and target architectures.
- 
-    The standard requires that `LOGICAL(KIND=1)', `INTEGER(KIND=1)', and
- `REAL(KIND=1)' occupy the same amount of storage space, and that
- `COMPLEX(KIND=1)' and `REAL(KIND=2)' take twice as much storage space
- as `REAL(KIND=1)'.  Further, it requires that `COMPLEX(KIND=1)'
- entities be ordered such that when a `COMPLEX(KIND=1)' variable is
- storage-associated (such as via `EQUIVALENCE') with a two-element
- `REAL(KIND=1)' array named `R', `R(1)' corresponds to the real element
- and `R(2)' to the imaginary element of the `COMPLEX(KIND=1)' variable.
- 
-    (Few requirements as to precision or ranges of any of these are
- placed on the implementation, nor is the relationship of storage sizes
- of these types to the `CHARACTER' type specified, by the standard.)
- 
-    `g77' follows the above requirements, warning when compiling a
- program requires placement of items in memory that contradict the
- requirements of the target architecture.  (For example, a program can
- require placement of a `REAL(KIND=2)' on a boundary that is not an even
- multiple of its size, but still an even multiple of the size of a
- `REAL(KIND=1)' variable.  On some target architectures, using the
- canonical mapping of Fortran types to underlying architectural types,
- such placement is prohibited by the machine definition or the
- Application Binary Interface (ABI) in force for the configuration
- defined for building `gcc' and `g77'.  `g77' warns about such
- situations when it encounters them.)
- 
-    `g77' follows consistent rules for configuring the mapping between
- Fortran types, including the `*N' notation, and the underlying
- architectural types as accessed by a similarly-configured applicable
- version of the `gcc' compiler.  These rules offer a widely portable,
- consistent Fortran/C environment, although they might well conflict
- with the expectations of users of Fortran compilers designed and
- written for particular architectures.
- 
-    These rules are based on the configuration that is in force for the
- version of `gcc' built in the same release as `g77' (and which was
- therefore used to build both the `g77' compiler components and the
- `libg2c' run-time library):
- 
- `REAL(KIND=1)'
-      Same as `float' type.
- 
- `REAL(KIND=2)'
-      Same as whatever floating-point type that is twice the size of a
-      `float'--usually, this is a `double'.
- 
- `INTEGER(KIND=1)'
-      Same as an integral type that is occupies the same amount of
-      memory storage as `float'--usually, this is either an `int' or a
-      `long int'.
- 
- `LOGICAL(KIND=1)'
-      Same `gcc' type as `INTEGER(KIND=1)'.
- 
- `INTEGER(KIND=2)'
-      Twice the size, and usually nearly twice the range, as
-      `INTEGER(KIND=1)'--usually, this is either a `long int' or a `long
-      long int'.
- 
- `LOGICAL(KIND=2)'
-      Same `gcc' type as `INTEGER(KIND=2)'.
- 
- `INTEGER(KIND=3)'
-      Same `gcc' type as signed `char'.
- 
- `LOGICAL(KIND=3)'
-      Same `gcc' type as `INTEGER(KIND=3)'.
- 
- `INTEGER(KIND=6)'
-      Twice the size, and usually nearly twice the range, as
-      `INTEGER(KIND=3)'--usually, this is a `short'.
- 
- `LOGICAL(KIND=6)'
-      Same `gcc' type as `INTEGER(KIND=6)'.
- 
- `COMPLEX(KIND=1)'
-      Two `REAL(KIND=1)' scalars (one for the real part followed by one
-      for the imaginary part).
- 
- `COMPLEX(KIND=2)'
-      Two `REAL(KIND=2)' scalars.
- 
- `NUMERIC-TYPE*N'
-      (Where NUMERIC-TYPE is any type other than `CHARACTER'.)  Same as
-      whatever `gcc' type occupies N times the storage space of a `gcc'
-      `char' item.
- 
- `DOUBLE PRECISION'
-      Same as `REAL(KIND=2)'.
- 
- `DOUBLE COMPLEX'
-      Same as `COMPLEX(KIND=2)'.
- 
-    Note that the above are proposed correspondences and might change in
- future versions of `g77'--avoid writing code depending on them.
- 
-    Other types supported by `g77' are derived from gcc types such as
- `char', `short', `int', `long int', `long long int', `long double', and
- so on.  That is, whatever types `gcc' already supports, `g77' supports
- now or probably will support in a future version.  The rules for the
- `NUMERIC-TYPE*N' notation apply to these types, and new values for
- `NUMERIC-TYPE(KIND=N)' will be assigned in a way that encourages
- clarity, consistency, and portability.
- 
- 
- File: g77.info,  Node: Compiler Constants,  Next: Compiler Intrinsics,  Prev: Compiler Types,  Up: Compiler
- 
- Compiler Constants
- ==================
- 
-    `g77' strictly assigns types to _all_ constants not documented as
- "typeless" (typeless constants including `'1'Z', for example).  Many
- other Fortran compilers attempt to assign types to typed constants
- based on their context.  This results in hard-to-find bugs, nonportable
- code, and is not in the spirit (though it strictly follows the letter)
- of the 77 and 90 standards.
- 
-    `g77' might offer, in a future release, explicit constructs by which
- a wider variety of typeless constants may be specified, and/or
- user-requested warnings indicating places where `g77' might differ from
- how other compilers assign types to constants.
- 
-    *Note Context-Sensitive Constants::, for more information on this
- issue.
- 
- 
- File: g77.info,  Node: Compiler Intrinsics,  Prev: Compiler Constants,  Up: Compiler
- 
- Compiler Intrinsics
- ===================
- 
-    `g77' offers an ever-widening set of intrinsics.  Currently these
- all are procedures (functions and subroutines).
- 
-    Some of these intrinsics are unimplemented, but their names reserved
- to reduce future problems with existing code as they are implemented.
- Others are implemented as part of the GNU Fortran language, while yet
- others are provided for compatibility with other dialects of Fortran
- but are not part of the GNU Fortran language.
- 
-    To manage these distinctions, `g77' provides intrinsic _groups_, a
- facility that is simply an extension of the intrinsic groups provided
- by the GNU Fortran language.
- 
- * Menu:
- 
- * Intrinsic Groups::  How intrinsics are grouped for easy management.
- * Other Intrinsics::  Intrinsics other than those in the GNU
-                        Fortran language.
- 
- 
- File: g77.info,  Node: Intrinsic Groups,  Next: Other Intrinsics,  Up: Compiler Intrinsics
- 
- Intrinsic Groups
- ----------------
- 
-    A given specific intrinsic belongs in one or more groups.  Each
- group is deleted, disabled, hidden, or enabled by default or a
- command-line option.  The meaning of each term follows.
- 
- Deleted
-      No intrinsics are recognized as belonging to that group.
- 
- Disabled
-      Intrinsics are recognized as belonging to the group, but
-      references to them (other than via the `INTRINSIC' statement) are
-      disallowed through that group.
- 
- Hidden
-      Intrinsics in that group are recognized and enabled (if
-      implemented) _only_ if the first mention of the actual name of an
-      intrinsic in a program unit is in an `INTRINSIC' statement.
- 
- Enabled
-      Intrinsics in that group are recognized and enabled (if
-      implemented).
- 
-    The distinction between deleting and disabling a group is illustrated
- by the following example.  Assume intrinsic `FOO' belongs only to group
- `FGR'.  If group `FGR' is deleted, the following program unit will
- successfully compile, because `FOO()' will be seen as a reference to an
- external function named `FOO':
- 
-      PRINT *, FOO()
-      END
- 
- If group `FGR' is disabled, compiling the above program will produce
- diagnostics, either because the `FOO' intrinsic is improperly invoked
- or, if properly invoked, it is not enabled.  To change the above
- program so it references an external function `FOO' instead of the
- disabled `FOO' intrinsic, add the following line to the top:
- 
-      EXTERNAL FOO
- 
- So, deleting a group tells `g77' to pretend as though the intrinsics in
- that group do not exist at all, whereas disabling it tells `g77' to
- recognize them as (disabled) intrinsics in intrinsic-like contexts.
- 
-    Hiding a group is like enabling it, but the intrinsic must be first
- named in an `INTRINSIC' statement to be considered a reference to the
- intrinsic rather than to an external procedure.  This might be the
- "safest" way to treat a new group of intrinsics when compiling old
- code, because it allows the old code to be generally written as if
- those new intrinsics never existed, but to be changed to use them by
- inserting `INTRINSIC' statements in the appropriate places.  However,
- it should be the goal of development to use `EXTERNAL' for all names of
- external procedures that might be intrinsic names.
- 
-    If an intrinsic is in more than one group, it is enabled if any of
- its containing groups are enabled; if not so enabled, it is hidden if
- any of its containing groups are hidden; if not so hidden, it is
- disabled if any of its containing groups are disabled; if not so
- disabled, it is deleted.  This extra complication is necessary because
- some intrinsics, such as `IBITS', belong to more than one group, and
- hence should be enabled if any of the groups to which they belong are
- enabled, and so on.
- 
-    The groups are:
- 
- `badu77'
-      UNIX intrinsics having inappropriate forms (usually functions that
-      have intended side effects).
- 
- `gnu'
-      Intrinsics the GNU Fortran language supports that are extensions to
-      the Fortran standards (77 and 90).
- 
- `f2c'
-      Intrinsics supported by AT&T's `f2c' converter and/or `libf2c'.
- 
- `f90'
-      Fortran 90 intrinsics.
- 
- `mil'
-      MIL-STD 1753 intrinsics (`MVBITS', `IAND', `BTEST', and so on).
- 
- `unix'
-      UNIX intrinsics (`IARGC', `EXIT', `ERF', and so on).
- 
- `vxt'
-      VAX/VMS FORTRAN (current as of v4) intrinsics.
- 
--- 0 ----
diff -Nrc3pad gcc-3.2.3/gcc/f/g77.info-12 gcc-3.3/gcc/f/g77.info-12
*** gcc-3.2.3/gcc/f/g77.info-12	2003-04-22 07:07:24.000000000 +0000
--- gcc-3.3/gcc/f/g77.info-12	1970-01-01 00:00:00.000000000 +0000
***************
*** 1,1687 ****
- This is g77.info, produced by makeinfo version 4.5 from g77.texi.
- 
- INFO-DIR-SECTION Programming
- START-INFO-DIR-ENTRY
- * g77: (g77).                  The GNU Fortran compiler.
- END-INFO-DIR-ENTRY
-    This file documents the use and the internals of the GNU Fortran
- (`g77') compiler.  It corresponds to the GCC-3.2.3 version of `g77'.
- 
-    Published by the Free Software Foundation 59 Temple Place - Suite 330
- Boston, MA 02111-1307 USA
- 
-    Copyright (C) 1995,1996,1997,1998,1999,2000,2001,2002 Free Software
- Foundation, Inc.
- 
-    Permission is granted to copy, distribute and/or modify this document
- under the terms of the GNU Free Documentation License, Version 1.1 or
- any later version published by the Free Software Foundation; with the
- Invariant Sections being "GNU General Public License" and "Funding Free
- Software", the Front-Cover texts being (a) (see below), and with the
- Back-Cover Texts being (b) (see below).  A copy of the license is
- included in the section entitled "GNU Free Documentation License".
- 
-    (a) The FSF's Front-Cover Text is:
- 
-    A GNU Manual
- 
-    (b) The FSF's Back-Cover Text is:
- 
-    You have freedom to copy and modify this GNU Manual, like GNU
- software.  Copies published by the Free Software Foundation raise
- funds for GNU development.
- 
-    Contributed by James Craig Burley (<craig@jcb-sc.com>).  Inspired by
- a first pass at translating `g77-0.5.16/f/DOC' that was contributed to
- Craig by David Ronis (<ronis@onsager.chem.mcgill.ca>).
- 
- 
- File: g77.info,  Node: Other Intrinsics,  Prev: Intrinsic Groups,  Up: Compiler Intrinsics
- 
- Other Intrinsics
- ----------------
- 
-    `g77' supports intrinsics other than those in the GNU Fortran
- language proper.  This set of intrinsics is described below.
- 
-    (Note that the empty lines appearing in the menu below are not
- intentional--they result from a bug in the `makeinfo' program.)
- 
- * Menu:
- 
- 
- * ACosD Intrinsic::     (Reserved for future use.)
- 
- * AIMax0 Intrinsic::    (Reserved for future use.)
- * AIMin0 Intrinsic::    (Reserved for future use.)
- 
- * AJMax0 Intrinsic::    (Reserved for future use.)
- * AJMin0 Intrinsic::    (Reserved for future use.)
- 
- * ASinD Intrinsic::     (Reserved for future use.)
- 
- * ATan2D Intrinsic::    (Reserved for future use.)
- * ATanD Intrinsic::     (Reserved for future use.)
- 
- * BITest Intrinsic::    (Reserved for future use.)
- 
- * BJTest Intrinsic::    (Reserved for future use.)
- 
- * CDAbs Intrinsic::     Absolute value (archaic).
- * CDCos Intrinsic::     Cosine (archaic).
- * CDExp Intrinsic::     Exponential (archaic).
- * CDLog Intrinsic::     Natural logarithm (archaic).
- * CDSin Intrinsic::     Sine (archaic).
- * CDSqRt Intrinsic::    Square root (archaic).
- 
- * ChDir Intrinsic (function):: Change directory.
- 
- * ChMod Intrinsic (function):: Change file modes.
- 
- * CosD Intrinsic::      (Reserved for future use.)
- 
- * DACosD Intrinsic::    (Reserved for future use.)
- 
- * DASinD Intrinsic::    (Reserved for future use.)
- 
- * DATan2D Intrinsic::   (Reserved for future use.)
- * DATanD Intrinsic::    (Reserved for future use.)
- * Date Intrinsic::      Get current date as dd-Mon-yy.
- 
- * DbleQ Intrinsic::     (Reserved for future use.)
- 
- * DCmplx Intrinsic::    Construct `COMPLEX(KIND=2)' value.
- * DConjg Intrinsic::    Complex conjugate (archaic).
- 
- * DCosD Intrinsic::     (Reserved for future use.)
- 
- * DFloat Intrinsic::    Conversion (archaic).
- 
- * DFlotI Intrinsic::    (Reserved for future use.)
- * DFlotJ Intrinsic::    (Reserved for future use.)
- 
- * DImag Intrinsic::     Convert/extract imaginary part of complex (archaic).
- 
- * DReal Intrinsic::     Convert value to type `REAL(KIND=2)'.
- 
- * DSinD Intrinsic::     (Reserved for future use.)
- 
- * DTanD Intrinsic::     (Reserved for future use.)
- 
- * DTime Intrinsic (function):: Get elapsed time since last time.
- 
- * FGet Intrinsic (function):: Read a character from unit 5 stream-wise.
- 
- * FGetC Intrinsic (function):: Read a character stream-wise.
- 
- * FloatI Intrinsic::    (Reserved for future use.)
- * FloatJ Intrinsic::    (Reserved for future use.)
- 
- * FPut Intrinsic (function):: Write a character to unit 6 stream-wise.
- 
- * FPutC Intrinsic (function):: Write a character stream-wise.
- 
- * IDate Intrinsic (VXT):: Get local time info (VAX/VMS).
- 
- * IIAbs Intrinsic::     (Reserved for future use.)
- * IIAnd Intrinsic::     (Reserved for future use.)
- * IIBClr Intrinsic::    (Reserved for future use.)
- * IIBits Intrinsic::    (Reserved for future use.)
- * IIBSet Intrinsic::    (Reserved for future use.)
- * IIDiM Intrinsic::     (Reserved for future use.)
- * IIDInt Intrinsic::    (Reserved for future use.)
- * IIDNnt Intrinsic::    (Reserved for future use.)
- * IIEOr Intrinsic::     (Reserved for future use.)
- * IIFix Intrinsic::     (Reserved for future use.)
- * IInt Intrinsic::      (Reserved for future use.)
- * IIOr Intrinsic::      (Reserved for future use.)
- * IIQint Intrinsic::    (Reserved for future use.)
- * IIQNnt Intrinsic::    (Reserved for future use.)
- * IIShftC Intrinsic::   (Reserved for future use.)
- * IISign Intrinsic::    (Reserved for future use.)
- 
- * IMax0 Intrinsic::     (Reserved for future use.)
- * IMax1 Intrinsic::     (Reserved for future use.)
- * IMin0 Intrinsic::     (Reserved for future use.)
- * IMin1 Intrinsic::     (Reserved for future use.)
- * IMod Intrinsic::      (Reserved for future use.)
- 
- * INInt Intrinsic::     (Reserved for future use.)
- * INot Intrinsic::      (Reserved for future use.)
- 
- * IZExt Intrinsic::     (Reserved for future use.)
- * JIAbs Intrinsic::     (Reserved for future use.)
- * JIAnd Intrinsic::     (Reserved for future use.)
- * JIBClr Intrinsic::    (Reserved for future use.)
- * JIBits Intrinsic::    (Reserved for future use.)
- * JIBSet Intrinsic::    (Reserved for future use.)
- * JIDiM Intrinsic::     (Reserved for future use.)
- * JIDInt Intrinsic::    (Reserved for future use.)
- * JIDNnt Intrinsic::    (Reserved for future use.)
- * JIEOr Intrinsic::     (Reserved for future use.)
- * JIFix Intrinsic::     (Reserved for future use.)
- * JInt Intrinsic::      (Reserved for future use.)
- * JIOr Intrinsic::      (Reserved for future use.)
- * JIQint Intrinsic::    (Reserved for future use.)
- * JIQNnt Intrinsic::    (Reserved for future use.)
- * JIShft Intrinsic::    (Reserved for future use.)
- * JIShftC Intrinsic::   (Reserved for future use.)
- * JISign Intrinsic::    (Reserved for future use.)
- * JMax0 Intrinsic::     (Reserved for future use.)
- * JMax1 Intrinsic::     (Reserved for future use.)
- * JMin0 Intrinsic::     (Reserved for future use.)
- * JMin1 Intrinsic::     (Reserved for future use.)
- * JMod Intrinsic::      (Reserved for future use.)
- * JNInt Intrinsic::     (Reserved for future use.)
- * JNot Intrinsic::      (Reserved for future use.)
- * JZExt Intrinsic::     (Reserved for future use.)
- 
- * Kill Intrinsic (function):: Signal a process.
- 
- * Link Intrinsic (function):: Make hard link in file system.
- 
- * QAbs Intrinsic::      (Reserved for future use.)
- * QACos Intrinsic::     (Reserved for future use.)
- * QACosD Intrinsic::    (Reserved for future use.)
- * QASin Intrinsic::     (Reserved for future use.)
- * QASinD Intrinsic::    (Reserved for future use.)
- * QATan Intrinsic::     (Reserved for future use.)
- * QATan2 Intrinsic::    (Reserved for future use.)
- * QATan2D Intrinsic::   (Reserved for future use.)
- * QATanD Intrinsic::    (Reserved for future use.)
- * QCos Intrinsic::      (Reserved for future use.)
- * QCosD Intrinsic::     (Reserved for future use.)
- * QCosH Intrinsic::     (Reserved for future use.)
- * QDiM Intrinsic::      (Reserved for future use.)
- * QExp Intrinsic::      (Reserved for future use.)
- * QExt Intrinsic::      (Reserved for future use.)
- * QExtD Intrinsic::     (Reserved for future use.)
- * QFloat Intrinsic::    (Reserved for future use.)
- * QInt Intrinsic::      (Reserved for future use.)
- * QLog Intrinsic::      (Reserved for future use.)
- * QLog10 Intrinsic::    (Reserved for future use.)
- * QMax1 Intrinsic::     (Reserved for future use.)
- * QMin1 Intrinsic::     (Reserved for future use.)
- * QMod Intrinsic::      (Reserved for future use.)
- * QNInt Intrinsic::     (Reserved for future use.)
- * QSin Intrinsic::      (Reserved for future use.)
- * QSinD Intrinsic::     (Reserved for future use.)
- * QSinH Intrinsic::     (Reserved for future use.)
- * QSqRt Intrinsic::     (Reserved for future use.)
- * QTan Intrinsic::      (Reserved for future use.)
- * QTanD Intrinsic::     (Reserved for future use.)
- * QTanH Intrinsic::     (Reserved for future use.)
- 
- * Rename Intrinsic (function):: Rename file.
- 
- * Secnds Intrinsic::    Get local time offset since midnight.
- 
- * Signal Intrinsic (function):: Muck with signal handling.
- 
- * SinD Intrinsic::      (Reserved for future use.)
- 
- * SnglQ Intrinsic::     (Reserved for future use.)
- 
- * SymLnk Intrinsic (function):: Make symbolic link in file system.
- 
- * System Intrinsic (function):: Invoke shell (system) command.
- 
- * TanD Intrinsic::      (Reserved for future use.)
- 
- * Time Intrinsic (VXT):: Get the time as a character value.
- 
- * UMask Intrinsic (function):: Set file creation permissions mask.
- 
- * Unlink Intrinsic (function):: Unlink file.
- 
- * ZExt Intrinsic::      (Reserved for future use.)
- 
- 
- File: g77.info,  Node: ACosD Intrinsic,  Next: AIMax0 Intrinsic,  Up: Other Intrinsics
- 
- ACosD Intrinsic
- ...............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL ACosD' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: AIMax0 Intrinsic,  Next: AIMin0 Intrinsic,  Prev: ACosD Intrinsic,  Up: Other Intrinsics
- 
- AIMax0 Intrinsic
- ................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL AIMax0' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: AIMin0 Intrinsic,  Next: AJMax0 Intrinsic,  Prev: AIMax0 Intrinsic,  Up: Other Intrinsics
- 
- AIMin0 Intrinsic
- ................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL AIMin0' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: AJMax0 Intrinsic,  Next: AJMin0 Intrinsic,  Prev: AIMin0 Intrinsic,  Up: Other Intrinsics
- 
- AJMax0 Intrinsic
- ................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL AJMax0' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: AJMin0 Intrinsic,  Next: ASinD Intrinsic,  Prev: AJMax0 Intrinsic,  Up: Other Intrinsics
- 
- AJMin0 Intrinsic
- ................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL AJMin0' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: ASinD Intrinsic,  Next: ATan2D Intrinsic,  Prev: AJMin0 Intrinsic,  Up: Other Intrinsics
- 
- ASinD Intrinsic
- ...............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL ASinD' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: ATan2D Intrinsic,  Next: ATanD Intrinsic,  Prev: ASinD Intrinsic,  Up: Other Intrinsics
- 
- ATan2D Intrinsic
- ................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL ATan2D' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: ATanD Intrinsic,  Next: BITest Intrinsic,  Prev: ATan2D Intrinsic,  Up: Other Intrinsics
- 
- ATanD Intrinsic
- ...............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL ATanD' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: BITest Intrinsic,  Next: BJTest Intrinsic,  Prev: ATanD Intrinsic,  Up: Other Intrinsics
- 
- BITest Intrinsic
- ................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL BITest' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: BJTest Intrinsic,  Next: CDAbs Intrinsic,  Prev: BITest Intrinsic,  Up: Other Intrinsics
- 
- BJTest Intrinsic
- ................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL BJTest' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: CDAbs Intrinsic,  Next: CDCos Intrinsic,  Prev: BJTest Intrinsic,  Up: Other Intrinsics
- 
- CDAbs Intrinsic
- ...............
- 
-      CDAbs(A)
- 
- CDAbs: `REAL(KIND=2)' function.
- 
- A: `COMPLEX(KIND=2)'; scalar; INTENT(IN).
- 
- Intrinsic groups: `f2c', `vxt'.
- 
- Description:
- 
-    Archaic form of `ABS()' that is specific to one type for A.  *Note
- Abs Intrinsic::.
- 
- 
- File: g77.info,  Node: CDCos Intrinsic,  Next: CDExp Intrinsic,  Prev: CDAbs Intrinsic,  Up: Other Intrinsics
- 
- CDCos Intrinsic
- ...............
- 
-      CDCos(X)
- 
- CDCos: `COMPLEX(KIND=2)' function.
- 
- X: `COMPLEX(KIND=2)'; scalar; INTENT(IN).
- 
- Intrinsic groups: `f2c', `vxt'.
- 
- Description:
- 
-    Archaic form of `COS()' that is specific to one type for X.  *Note
- Cos Intrinsic::.
- 
- 
- File: g77.info,  Node: CDExp Intrinsic,  Next: CDLog Intrinsic,  Prev: CDCos Intrinsic,  Up: Other Intrinsics
- 
- CDExp Intrinsic
- ...............
- 
-      CDExp(X)
- 
- CDExp: `COMPLEX(KIND=2)' function.
- 
- X: `COMPLEX(KIND=2)'; scalar; INTENT(IN).
- 
- Intrinsic groups: `f2c', `vxt'.
- 
- Description:
- 
-    Archaic form of `EXP()' that is specific to one type for X.  *Note
- Exp Intrinsic::.
- 
- 
- File: g77.info,  Node: CDLog Intrinsic,  Next: CDSin Intrinsic,  Prev: CDExp Intrinsic,  Up: Other Intrinsics
- 
- CDLog Intrinsic
- ...............
- 
-      CDLog(X)
- 
- CDLog: `COMPLEX(KIND=2)' function.
- 
- X: `COMPLEX(KIND=2)'; scalar; INTENT(IN).
- 
- Intrinsic groups: `f2c', `vxt'.
- 
- Description:
- 
-    Archaic form of `LOG()' that is specific to one type for X.  *Note
- Log Intrinsic::.
- 
- 
- File: g77.info,  Node: CDSin Intrinsic,  Next: CDSqRt Intrinsic,  Prev: CDLog Intrinsic,  Up: Other Intrinsics
- 
- CDSin Intrinsic
- ...............
- 
-      CDSin(X)
- 
- CDSin: `COMPLEX(KIND=2)' function.
- 
- X: `COMPLEX(KIND=2)'; scalar; INTENT(IN).
- 
- Intrinsic groups: `f2c', `vxt'.
- 
- Description:
- 
-    Archaic form of `SIN()' that is specific to one type for X.  *Note
- Sin Intrinsic::.
- 
- 
- File: g77.info,  Node: CDSqRt Intrinsic,  Next: ChDir Intrinsic (function),  Prev: CDSin Intrinsic,  Up: Other Intrinsics
- 
- CDSqRt Intrinsic
- ................
- 
-      CDSqRt(X)
- 
- CDSqRt: `COMPLEX(KIND=2)' function.
- 
- X: `COMPLEX(KIND=2)'; scalar; INTENT(IN).
- 
- Intrinsic groups: `f2c', `vxt'.
- 
- Description:
- 
-    Archaic form of `SQRT()' that is specific to one type for X.  *Note
- SqRt Intrinsic::.
- 
- 
- File: g77.info,  Node: ChDir Intrinsic (function),  Next: ChMod Intrinsic (function),  Prev: CDSqRt Intrinsic,  Up: Other Intrinsics
- 
- ChDir Intrinsic (function)
- ..........................
- 
-      ChDir(DIR)
- 
- ChDir: `INTEGER(KIND=1)' function.
- 
- DIR: `CHARACTER'; scalar; INTENT(IN).
- 
- Intrinsic groups: `badu77'.
- 
- Description:
- 
-    Sets the current working directory to be DIR.  Returns 0 on success
- or a non-zero error code.  See `chdir(3)'.
- 
-    _Caution:_ Using this routine during I/O to a unit connected with a
- non-absolute file name can cause subsequent I/O on such a unit to fail
- because the I/O library might reopen files by name.
- 
-    Due to the side effects performed by this intrinsic, the function
- form is not recommended.
- 
-    For information on other intrinsics with the same name: *Note ChDir
- Intrinsic (subroutine)::.
- 
- 
- File: g77.info,  Node: ChMod Intrinsic (function),  Next: CosD Intrinsic,  Prev: ChDir Intrinsic (function),  Up: Other Intrinsics
- 
- ChMod Intrinsic (function)
- ..........................
- 
-      ChMod(NAME, MODE)
- 
- ChMod: `INTEGER(KIND=1)' function.
- 
- NAME: `CHARACTER'; scalar; INTENT(IN).
- 
- MODE: `CHARACTER'; scalar; INTENT(IN).
- 
- Intrinsic groups: `badu77'.
- 
- Description:
- 
-    Changes the access mode of file NAME according to the specification
- MODE, which is given in the format of `chmod(1)'.  A null character
- (`CHAR(0)') marks the end of the name in NAME--otherwise, trailing
- blanks in NAME are ignored.  Currently, NAME must not contain the
- single quote character.
- 
-    Returns 0 on success or a non-zero error code otherwise.
- 
-    Note that this currently works by actually invoking `/bin/chmod' (or
- the `chmod' found when the library was configured) and so might fail in
- some circumstances and will, anyway, be slow.
- 
-    Due to the side effects performed by this intrinsic, the function
- form is not recommended.
- 
-    For information on other intrinsics with the same name: *Note ChMod
- Intrinsic (subroutine)::.
- 
- 
- File: g77.info,  Node: CosD Intrinsic,  Next: DACosD Intrinsic,  Prev: ChMod Intrinsic (function),  Up: Other Intrinsics
- 
- CosD Intrinsic
- ..............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL CosD' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: DACosD Intrinsic,  Next: DASinD Intrinsic,  Prev: CosD Intrinsic,  Up: Other Intrinsics
- 
- DACosD Intrinsic
- ................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL DACosD' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: DASinD Intrinsic,  Next: DATan2D Intrinsic,  Prev: DACosD Intrinsic,  Up: Other Intrinsics
- 
- DASinD Intrinsic
- ................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL DASinD' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: DATan2D Intrinsic,  Next: DATanD Intrinsic,  Prev: DASinD Intrinsic,  Up: Other Intrinsics
- 
- DATan2D Intrinsic
- .................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL DATan2D' to use this name for
- an external procedure.
- 
- 
- File: g77.info,  Node: DATanD Intrinsic,  Next: Date Intrinsic,  Prev: DATan2D Intrinsic,  Up: Other Intrinsics
- 
- DATanD Intrinsic
- ................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL DATanD' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: Date Intrinsic,  Next: DbleQ Intrinsic,  Prev: DATanD Intrinsic,  Up: Other Intrinsics
- 
- Date Intrinsic
- ..............
- 
-      CALL Date(DATE)
- 
- DATE: `CHARACTER'; scalar; INTENT(OUT).
- 
- Intrinsic groups: `vxt'.
- 
- Description:
- 
-    Returns DATE in the form `DD-MMM-YY', representing the numeric day
- of the month DD, a three-character abbreviation of the month name MMM
- and the last two digits of the year YY, e.g. `25-Nov-96'.
- 
-    This intrinsic is not recommended, due to the year 2000 approaching.
- Therefore, programs making use of this intrinsic might not be Year 2000
- (Y2K) compliant.  *Note CTime Intrinsic (subroutine)::, for information
- on obtaining more digits for the current (or any) date.
- 
- 
- File: g77.info,  Node: DbleQ Intrinsic,  Next: DCmplx Intrinsic,  Prev: Date Intrinsic,  Up: Other Intrinsics
- 
- DbleQ Intrinsic
- ...............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL DbleQ' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: DCmplx Intrinsic,  Next: DConjg Intrinsic,  Prev: DbleQ Intrinsic,  Up: Other Intrinsics
- 
- DCmplx Intrinsic
- ................
- 
-      DCmplx(X, Y)
- 
- DCmplx: `COMPLEX(KIND=2)' function.
- 
- X: `INTEGER', `REAL', or `COMPLEX'; scalar; INTENT(IN).
- 
- Y: `INTEGER' or `REAL'; OPTIONAL (must be omitted if X is `COMPLEX');
- scalar; INTENT(IN).
- 
- Intrinsic groups: `f2c', `vxt'.
- 
- Description:
- 
-    If X is not type `COMPLEX', constructs a value of type
- `COMPLEX(KIND=2)' from the real and imaginary values specified by X and
- Y, respectively.  If Y is omitted, `0D0' is assumed.
- 
-    If X is type `COMPLEX', converts it to type `COMPLEX(KIND=2)'.
- 
-    Although this intrinsic is not standard Fortran, it is a popular
- extension offered by many compilers that support `DOUBLE COMPLEX',
- since it offers the easiest way to convert to `DOUBLE COMPLEX' without
- using Fortran 90 features (such as the `KIND=' argument to the
- `CMPLX()' intrinsic).
- 
-    (`CMPLX(0D0, 0D0)' returns a single-precision `COMPLEX' result, as
- required by standard FORTRAN 77.  That's why so many compilers provide
- `DCMPLX()', since `DCMPLX(0D0, 0D0)' returns a `DOUBLE COMPLEX' result.
- Still, `DCMPLX()' converts even `REAL*16' arguments to their `REAL*8'
- equivalents in most dialects of Fortran, so neither it nor `CMPLX()'
- allow easy construction of arbitrary-precision values without
- potentially forcing a conversion involving extending or reducing
- precision.  GNU Fortran provides such an intrinsic, called `COMPLEX()'.)
- 
-    *Note Complex Intrinsic::, for information on easily constructing a
- `COMPLEX' value of arbitrary precision from `REAL' arguments.
- 
- 
- File: g77.info,  Node: DConjg Intrinsic,  Next: DCosD Intrinsic,  Prev: DCmplx Intrinsic,  Up: Other Intrinsics
- 
- DConjg Intrinsic
- ................
- 
-      DConjg(Z)
- 
- DConjg: `COMPLEX(KIND=2)' function.
- 
- Z: `COMPLEX(KIND=2)'; scalar; INTENT(IN).
- 
- Intrinsic groups: `f2c', `vxt'.
- 
- Description:
- 
-    Archaic form of `CONJG()' that is specific to one type for Z.  *Note
- Conjg Intrinsic::.
- 
- 
- File: g77.info,  Node: DCosD Intrinsic,  Next: DFloat Intrinsic,  Prev: DConjg Intrinsic,  Up: Other Intrinsics
- 
- DCosD Intrinsic
- ...............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL DCosD' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: DFloat Intrinsic,  Next: DFlotI Intrinsic,  Prev: DCosD Intrinsic,  Up: Other Intrinsics
- 
- DFloat Intrinsic
- ................
- 
-      DFloat(A)
- 
- DFloat: `REAL(KIND=2)' function.
- 
- A: `INTEGER'; scalar; INTENT(IN).
- 
- Intrinsic groups: `f2c', `vxt'.
- 
- Description:
- 
-    Archaic form of `REAL()' that is specific to one type for A.  *Note
- Real Intrinsic::.
- 
- 
- File: g77.info,  Node: DFlotI Intrinsic,  Next: DFlotJ Intrinsic,  Prev: DFloat Intrinsic,  Up: Other Intrinsics
- 
- DFlotI Intrinsic
- ................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL DFlotI' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: DFlotJ Intrinsic,  Next: DImag Intrinsic,  Prev: DFlotI Intrinsic,  Up: Other Intrinsics
- 
- DFlotJ Intrinsic
- ................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL DFlotJ' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: DImag Intrinsic,  Next: DReal Intrinsic,  Prev: DFlotJ Intrinsic,  Up: Other Intrinsics
- 
- DImag Intrinsic
- ...............
- 
-      DImag(Z)
- 
- DImag: `REAL(KIND=2)' function.
- 
- Z: `COMPLEX(KIND=2)'; scalar; INTENT(IN).
- 
- Intrinsic groups: `f2c', `vxt'.
- 
- Description:
- 
-    Archaic form of `AIMAG()' that is specific to one type for Z.  *Note
- AImag Intrinsic::.
- 
- 
- File: g77.info,  Node: DReal Intrinsic,  Next: DSinD Intrinsic,  Prev: DImag Intrinsic,  Up: Other Intrinsics
- 
- DReal Intrinsic
- ...............
- 
-      DReal(A)
- 
- DReal: `REAL(KIND=2)' function.
- 
- A: `INTEGER', `REAL', or `COMPLEX'; scalar; INTENT(IN).
- 
- Intrinsic groups: `vxt'.
- 
- Description:
- 
-    Converts A to `REAL(KIND=2)'.
- 
-    If A is type `COMPLEX', its real part is converted (if necessary) to
- `REAL(KIND=2)', and its imaginary part is disregarded.
- 
-    Although this intrinsic is not standard Fortran, it is a popular
- extension offered by many compilers that support `DOUBLE COMPLEX',
- since it offers the easiest way to extract the real part of a `DOUBLE
- COMPLEX' value without using the Fortran 90 `REAL()' intrinsic in a way
- that produces a return value inconsistent with the way many FORTRAN 77
- compilers handle `REAL()' of a `DOUBLE COMPLEX' value.
- 
-    *Note RealPart Intrinsic::, for information on a GNU Fortran
- intrinsic that avoids these areas of confusion.
- 
-    *Note Dble Intrinsic::, for information on the standard FORTRAN 77
- replacement for `DREAL()'.
- 
-    *Note REAL() and AIMAG() of Complex::, for more information on this
- issue.
- 
- 
- File: g77.info,  Node: DSinD Intrinsic,  Next: DTanD Intrinsic,  Prev: DReal Intrinsic,  Up: Other Intrinsics
- 
- DSinD Intrinsic
- ...............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL DSinD' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: DTanD Intrinsic,  Next: DTime Intrinsic (function),  Prev: DSinD Intrinsic,  Up: Other Intrinsics
- 
- DTanD Intrinsic
- ...............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL DTanD' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: DTime Intrinsic (function),  Next: FGet Intrinsic (function),  Prev: DTanD Intrinsic,  Up: Other Intrinsics
- 
- DTime Intrinsic (function)
- ..........................
- 
-      DTime(TARRAY)
- 
- DTime: `REAL(KIND=1)' function.
- 
- TARRAY: `REAL(KIND=1)'; DIMENSION(2); INTENT(OUT).
- 
- Intrinsic groups: `badu77'.
- 
- Description:
- 
-    Initially, return the number of seconds of runtime since the start
- of the process's execution as the function value, and the user and
- system components of this in `TARRAY(1)' and `TARRAY(2)' respectively.
- The functions' value is equal to `TARRAY(1) + TARRAY(2)'.
- 
-    Subsequent invocations of `DTIME()' return values accumulated since
- the previous invocation.
- 
-    On some systems, the underlying timings are represented using types
- with sufficiently small limits that overflows (wraparounds) are
- possible, such as 32-bit types.  Therefore, the values returned by this
- intrinsic might be, or become, negative, or numerically less than
- previous values, during a single run of the compiled program.
- 
-    Due to the side effects performed by this intrinsic, the function
- form is not recommended.
- 
-    For information on other intrinsics with the same name: *Note DTime
- Intrinsic (subroutine)::.
- 
- 
- File: g77.info,  Node: FGet Intrinsic (function),  Next: FGetC Intrinsic (function),  Prev: DTime Intrinsic (function),  Up: Other Intrinsics
- 
- FGet Intrinsic (function)
- .........................
- 
-      FGet(C)
- 
- FGet: `INTEGER(KIND=1)' function.
- 
- C: `CHARACTER'; scalar; INTENT(OUT).
- 
- Intrinsic groups: `badu77'.
- 
- Description:
- 
-    Reads a single character into C in stream mode from unit 5
- (by-passing normal formatted input) using `getc(3)'.  Returns 0 on
- success, -1 on end-of-file, and the error code from `ferror(3)'
- otherwise.
- 
-    Stream I/O should not be mixed with normal record-oriented
- (formatted or unformatted) I/O on the same unit; the results are
- unpredictable.
- 
-    For information on other intrinsics with the same name: *Note FGet
- Intrinsic (subroutine)::.
- 
- 
- File: g77.info,  Node: FGetC Intrinsic (function),  Next: FloatI Intrinsic,  Prev: FGet Intrinsic (function),  Up: Other Intrinsics
- 
- FGetC Intrinsic (function)
- ..........................
- 
-      FGetC(UNIT, C)
- 
- FGetC: `INTEGER(KIND=1)' function.
- 
- UNIT: `INTEGER'; scalar; INTENT(IN).
- 
- C: `CHARACTER'; scalar; INTENT(OUT).
- 
- Intrinsic groups: `badu77'.
- 
- Description:
- 
-    Reads a single character into C in stream mode from unit UNIT
- (by-passing normal formatted output) using `getc(3)'.  Returns 0 on
- success, -1 on end-of-file, and the error code from `ferror(3)'
- otherwise.
- 
-    Stream I/O should not be mixed with normal record-oriented
- (formatted or unformatted) I/O on the same unit; the results are
- unpredictable.
- 
-    For information on other intrinsics with the same name: *Note FGetC
- Intrinsic (subroutine)::.
- 
- 
- File: g77.info,  Node: FloatI Intrinsic,  Next: FloatJ Intrinsic,  Prev: FGetC Intrinsic (function),  Up: Other Intrinsics
- 
- FloatI Intrinsic
- ................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL FloatI' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: FloatJ Intrinsic,  Next: FPut Intrinsic (function),  Prev: FloatI Intrinsic,  Up: Other Intrinsics
- 
- FloatJ Intrinsic
- ................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL FloatJ' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: FPut Intrinsic (function),  Next: FPutC Intrinsic (function),  Prev: FloatJ Intrinsic,  Up: Other Intrinsics
- 
- FPut Intrinsic (function)
- .........................
- 
-      FPut(C)
- 
- FPut: `INTEGER(KIND=1)' function.
- 
- C: `CHARACTER'; scalar; INTENT(IN).
- 
- Intrinsic groups: `badu77'.
- 
- Description:
- 
-    Writes the single character C in stream mode to unit 6 (by-passing
- normal formatted output) using `getc(3)'.  Returns 0 on success, the
- error code from `ferror(3)' otherwise.
- 
-    Stream I/O should not be mixed with normal record-oriented
- (formatted or unformatted) I/O on the same unit; the results are
- unpredictable.
- 
-    For information on other intrinsics with the same name: *Note FPut
- Intrinsic (subroutine)::.
- 
- 
- File: g77.info,  Node: FPutC Intrinsic (function),  Next: IDate Intrinsic (VXT),  Prev: FPut Intrinsic (function),  Up: Other Intrinsics
- 
- FPutC Intrinsic (function)
- ..........................
- 
-      FPutC(UNIT, C)
- 
- FPutC: `INTEGER(KIND=1)' function.
- 
- UNIT: `INTEGER'; scalar; INTENT(IN).
- 
- C: `CHARACTER'; scalar; INTENT(IN).
- 
- Intrinsic groups: `badu77'.
- 
- Description:
- 
-    Writes the single character C in stream mode to unit UNIT
- (by-passing normal formatted output) using `putc(3)'.  Returns 0 on
- success, the error code from `ferror(3)' otherwise.
- 
-    Stream I/O should not be mixed with normal record-oriented
- (formatted or unformatted) I/O on the same unit; the results are
- unpredictable.
- 
-    For information on other intrinsics with the same name: *Note FPutC
- Intrinsic (subroutine)::.
- 
- 
- File: g77.info,  Node: IDate Intrinsic (VXT),  Next: IIAbs Intrinsic,  Prev: FPutC Intrinsic (function),  Up: Other Intrinsics
- 
- IDate Intrinsic (VXT)
- .....................
- 
-      CALL IDate(M, D, Y)
- 
- M: `INTEGER(KIND=1)'; scalar; INTENT(OUT).
- 
- D: `INTEGER(KIND=1)'; scalar; INTENT(OUT).
- 
- Y: `INTEGER(KIND=1)'; scalar; INTENT(OUT).
- 
- Intrinsic groups: `vxt'.
- 
- Description:
- 
-    Returns the numerical values of the current local time.  The month
- (in the range 1-12) is returned in M, the day (in the range 1-7) in D,
- and the year in Y (in the range 0-99).
- 
-    This intrinsic is not recommended, due to the year 2000 approaching.
- Therefore, programs making use of this intrinsic might not be Year 2000
- (Y2K) compliant.  For example, the date might appear, to such programs,
- to wrap around (change from a larger value to a smaller one) as of the
- Year 2000.
- 
-    *Note IDate Intrinsic (UNIX)::, for information on obtaining more
- digits for the current date.
- 
-    For information on other intrinsics with the same name: *Note IDate
- Intrinsic (UNIX)::.
- 
- 
- File: g77.info,  Node: IIAbs Intrinsic,  Next: IIAnd Intrinsic,  Prev: IDate Intrinsic (VXT),  Up: Other Intrinsics
- 
- IIAbs Intrinsic
- ...............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL IIAbs' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: IIAnd Intrinsic,  Next: IIBClr Intrinsic,  Prev: IIAbs Intrinsic,  Up: Other Intrinsics
- 
- IIAnd Intrinsic
- ...............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL IIAnd' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: IIBClr Intrinsic,  Next: IIBits Intrinsic,  Prev: IIAnd Intrinsic,  Up: Other Intrinsics
- 
- IIBClr Intrinsic
- ................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL IIBClr' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: IIBits Intrinsic,  Next: IIBSet Intrinsic,  Prev: IIBClr Intrinsic,  Up: Other Intrinsics
- 
- IIBits Intrinsic
- ................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL IIBits' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: IIBSet Intrinsic,  Next: IIDiM Intrinsic,  Prev: IIBits Intrinsic,  Up: Other Intrinsics
- 
- IIBSet Intrinsic
- ................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL IIBSet' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: IIDiM Intrinsic,  Next: IIDInt Intrinsic,  Prev: IIBSet Intrinsic,  Up: Other Intrinsics
- 
- IIDiM Intrinsic
- ...............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL IIDiM' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: IIDInt Intrinsic,  Next: IIDNnt Intrinsic,  Prev: IIDiM Intrinsic,  Up: Other Intrinsics
- 
- IIDInt Intrinsic
- ................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL IIDInt' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: IIDNnt Intrinsic,  Next: IIEOr Intrinsic,  Prev: IIDInt Intrinsic,  Up: Other Intrinsics
- 
- IIDNnt Intrinsic
- ................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL IIDNnt' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: IIEOr Intrinsic,  Next: IIFix Intrinsic,  Prev: IIDNnt Intrinsic,  Up: Other Intrinsics
- 
- IIEOr Intrinsic
- ...............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL IIEOr' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: IIFix Intrinsic,  Next: IInt Intrinsic,  Prev: IIEOr Intrinsic,  Up: Other Intrinsics
- 
- IIFix Intrinsic
- ...............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL IIFix' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: IInt Intrinsic,  Next: IIOr Intrinsic,  Prev: IIFix Intrinsic,  Up: Other Intrinsics
- 
- IInt Intrinsic
- ..............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL IInt' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: IIOr Intrinsic,  Next: IIQint Intrinsic,  Prev: IInt Intrinsic,  Up: Other Intrinsics
- 
- IIOr Intrinsic
- ..............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL IIOr' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: IIQint Intrinsic,  Next: IIQNnt Intrinsic,  Prev: IIOr Intrinsic,  Up: Other Intrinsics
- 
- IIQint Intrinsic
- ................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL IIQint' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: IIQNnt Intrinsic,  Next: IIShftC Intrinsic,  Prev: IIQint Intrinsic,  Up: Other Intrinsics
- 
- IIQNnt Intrinsic
- ................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL IIQNnt' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: IIShftC Intrinsic,  Next: IISign Intrinsic,  Prev: IIQNnt Intrinsic,  Up: Other Intrinsics
- 
- IIShftC Intrinsic
- .................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL IIShftC' to use this name for
- an external procedure.
- 
- 
- File: g77.info,  Node: IISign Intrinsic,  Next: IMax0 Intrinsic,  Prev: IIShftC Intrinsic,  Up: Other Intrinsics
- 
- IISign Intrinsic
- ................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL IISign' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: IMax0 Intrinsic,  Next: IMax1 Intrinsic,  Prev: IISign Intrinsic,  Up: Other Intrinsics
- 
- IMax0 Intrinsic
- ...............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL IMax0' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: IMax1 Intrinsic,  Next: IMin0 Intrinsic,  Prev: IMax0 Intrinsic,  Up: Other Intrinsics
- 
- IMax1 Intrinsic
- ...............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL IMax1' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: IMin0 Intrinsic,  Next: IMin1 Intrinsic,  Prev: IMax1 Intrinsic,  Up: Other Intrinsics
- 
- IMin0 Intrinsic
- ...............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL IMin0' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: IMin1 Intrinsic,  Next: IMod Intrinsic,  Prev: IMin0 Intrinsic,  Up: Other Intrinsics
- 
- IMin1 Intrinsic
- ...............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL IMin1' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: IMod Intrinsic,  Next: INInt Intrinsic,  Prev: IMin1 Intrinsic,  Up: Other Intrinsics
- 
- IMod Intrinsic
- ..............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL IMod' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: INInt Intrinsic,  Next: INot Intrinsic,  Prev: IMod Intrinsic,  Up: Other Intrinsics
- 
- INInt Intrinsic
- ...............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL INInt' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: INot Intrinsic,  Next: IZExt Intrinsic,  Prev: INInt Intrinsic,  Up: Other Intrinsics
- 
- INot Intrinsic
- ..............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL INot' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: IZExt Intrinsic,  Next: JIAbs Intrinsic,  Prev: INot Intrinsic,  Up: Other Intrinsics
- 
- IZExt Intrinsic
- ...............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL IZExt' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: JIAbs Intrinsic,  Next: JIAnd Intrinsic,  Prev: IZExt Intrinsic,  Up: Other Intrinsics
- 
- JIAbs Intrinsic
- ...............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL JIAbs' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: JIAnd Intrinsic,  Next: JIBClr Intrinsic,  Prev: JIAbs Intrinsic,  Up: Other Intrinsics
- 
- JIAnd Intrinsic
- ...............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL JIAnd' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: JIBClr Intrinsic,  Next: JIBits Intrinsic,  Prev: JIAnd Intrinsic,  Up: Other Intrinsics
- 
- JIBClr Intrinsic
- ................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL JIBClr' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: JIBits Intrinsic,  Next: JIBSet Intrinsic,  Prev: JIBClr Intrinsic,  Up: Other Intrinsics
- 
- JIBits Intrinsic
- ................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL JIBits' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: JIBSet Intrinsic,  Next: JIDiM Intrinsic,  Prev: JIBits Intrinsic,  Up: Other Intrinsics
- 
- JIBSet Intrinsic
- ................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL JIBSet' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: JIDiM Intrinsic,  Next: JIDInt Intrinsic,  Prev: JIBSet Intrinsic,  Up: Other Intrinsics
- 
- JIDiM Intrinsic
- ...............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL JIDiM' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: JIDInt Intrinsic,  Next: JIDNnt Intrinsic,  Prev: JIDiM Intrinsic,  Up: Other Intrinsics
- 
- JIDInt Intrinsic
- ................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL JIDInt' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: JIDNnt Intrinsic,  Next: JIEOr Intrinsic,  Prev: JIDInt Intrinsic,  Up: Other Intrinsics
- 
- JIDNnt Intrinsic
- ................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL JIDNnt' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: JIEOr Intrinsic,  Next: JIFix Intrinsic,  Prev: JIDNnt Intrinsic,  Up: Other Intrinsics
- 
- JIEOr Intrinsic
- ...............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL JIEOr' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: JIFix Intrinsic,  Next: JInt Intrinsic,  Prev: JIEOr Intrinsic,  Up: Other Intrinsics
- 
- JIFix Intrinsic
- ...............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL JIFix' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: JInt Intrinsic,  Next: JIOr Intrinsic,  Prev: JIFix Intrinsic,  Up: Other Intrinsics
- 
- JInt Intrinsic
- ..............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL JInt' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: JIOr Intrinsic,  Next: JIQint Intrinsic,  Prev: JInt Intrinsic,  Up: Other Intrinsics
- 
- JIOr Intrinsic
- ..............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL JIOr' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: JIQint Intrinsic,  Next: JIQNnt Intrinsic,  Prev: JIOr Intrinsic,  Up: Other Intrinsics
- 
- JIQint Intrinsic
- ................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL JIQint' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: JIQNnt Intrinsic,  Next: JIShft Intrinsic,  Prev: JIQint Intrinsic,  Up: Other Intrinsics
- 
- JIQNnt Intrinsic
- ................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL JIQNnt' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: JIShft Intrinsic,  Next: JIShftC Intrinsic,  Prev: JIQNnt Intrinsic,  Up: Other Intrinsics
- 
- JIShft Intrinsic
- ................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL JIShft' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: JIShftC Intrinsic,  Next: JISign Intrinsic,  Prev: JIShft Intrinsic,  Up: Other Intrinsics
- 
- JIShftC Intrinsic
- .................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL JIShftC' to use this name for
- an external procedure.
- 
- 
- File: g77.info,  Node: JISign Intrinsic,  Next: JMax0 Intrinsic,  Prev: JIShftC Intrinsic,  Up: Other Intrinsics
- 
- JISign Intrinsic
- ................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL JISign' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: JMax0 Intrinsic,  Next: JMax1 Intrinsic,  Prev: JISign Intrinsic,  Up: Other Intrinsics
- 
- JMax0 Intrinsic
- ...............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL JMax0' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: JMax1 Intrinsic,  Next: JMin0 Intrinsic,  Prev: JMax0 Intrinsic,  Up: Other Intrinsics
- 
- JMax1 Intrinsic
- ...............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL JMax1' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: JMin0 Intrinsic,  Next: JMin1 Intrinsic,  Prev: JMax1 Intrinsic,  Up: Other Intrinsics
- 
- JMin0 Intrinsic
- ...............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL JMin0' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: JMin1 Intrinsic,  Next: JMod Intrinsic,  Prev: JMin0 Intrinsic,  Up: Other Intrinsics
- 
- JMin1 Intrinsic
- ...............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL JMin1' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: JMod Intrinsic,  Next: JNInt Intrinsic,  Prev: JMin1 Intrinsic,  Up: Other Intrinsics
- 
- JMod Intrinsic
- ..............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL JMod' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: JNInt Intrinsic,  Next: JNot Intrinsic,  Prev: JMod Intrinsic,  Up: Other Intrinsics
- 
- JNInt Intrinsic
- ...............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL JNInt' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: JNot Intrinsic,  Next: JZExt Intrinsic,  Prev: JNInt Intrinsic,  Up: Other Intrinsics
- 
- JNot Intrinsic
- ..............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL JNot' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: JZExt Intrinsic,  Next: Kill Intrinsic (function),  Prev: JNot Intrinsic,  Up: Other Intrinsics
- 
- JZExt Intrinsic
- ...............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL JZExt' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: Kill Intrinsic (function),  Next: Link Intrinsic (function),  Prev: JZExt Intrinsic,  Up: Other Intrinsics
- 
- Kill Intrinsic (function)
- .........................
- 
-      Kill(PID, SIGNAL)
- 
- Kill: `INTEGER(KIND=1)' function.
- 
- PID: `INTEGER'; scalar; INTENT(IN).
- 
- SIGNAL: `INTEGER'; scalar; INTENT(IN).
- 
- Intrinsic groups: `badu77'.
- 
- Description:
- 
-    Sends the signal specified by SIGNAL to the process PID.  Returns 0
- on success or a non-zero error code.  See `kill(2)'.
- 
-    Due to the side effects performed by this intrinsic, the function
- form is not recommended.
- 
-    For information on other intrinsics with the same name: *Note Kill
- Intrinsic (subroutine)::.
- 
- 
- File: g77.info,  Node: Link Intrinsic (function),  Next: QAbs Intrinsic,  Prev: Kill Intrinsic (function),  Up: Other Intrinsics
- 
- Link Intrinsic (function)
- .........................
- 
-      Link(PATH1, PATH2)
- 
- Link: `INTEGER(KIND=1)' function.
- 
- PATH1: `CHARACTER'; scalar; INTENT(IN).
- 
- PATH2: `CHARACTER'; scalar; INTENT(IN).
- 
- Intrinsic groups: `badu77'.
- 
- Description:
- 
-    Makes a (hard) link from file PATH1 to PATH2.  A null character
- (`CHAR(0)') marks the end of the names in PATH1 and PATH2--otherwise,
- trailing blanks in PATH1 and PATH2 are ignored.  Returns 0 on success
- or a non-zero error code.  See `link(2)'.
- 
-    Due to the side effects performed by this intrinsic, the function
- form is not recommended.
- 
-    For information on other intrinsics with the same name: *Note Link
- Intrinsic (subroutine)::.
- 
- 
- File: g77.info,  Node: QAbs Intrinsic,  Next: QACos Intrinsic,  Prev: Link Intrinsic (function),  Up: Other Intrinsics
- 
- QAbs Intrinsic
- ..............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL QAbs' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: QACos Intrinsic,  Next: QACosD Intrinsic,  Prev: QAbs Intrinsic,  Up: Other Intrinsics
- 
- QACos Intrinsic
- ...............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL QACos' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: QACosD Intrinsic,  Next: QASin Intrinsic,  Prev: QACos Intrinsic,  Up: Other Intrinsics
- 
- QACosD Intrinsic
- ................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL QACosD' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: QASin Intrinsic,  Next: QASinD Intrinsic,  Prev: QACosD Intrinsic,  Up: Other Intrinsics
- 
- QASin Intrinsic
- ...............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL QASin' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: QASinD Intrinsic,  Next: QATan Intrinsic,  Prev: QASin Intrinsic,  Up: Other Intrinsics
- 
- QASinD Intrinsic
- ................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL QASinD' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: QATan Intrinsic,  Next: QATan2 Intrinsic,  Prev: QASinD Intrinsic,  Up: Other Intrinsics
- 
- QATan Intrinsic
- ...............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL QATan' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: QATan2 Intrinsic,  Next: QATan2D Intrinsic,  Prev: QATan Intrinsic,  Up: Other Intrinsics
- 
- QATan2 Intrinsic
- ................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL QATan2' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: QATan2D Intrinsic,  Next: QATanD Intrinsic,  Prev: QATan2 Intrinsic,  Up: Other Intrinsics
- 
- QATan2D Intrinsic
- .................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL QATan2D' to use this name for
- an external procedure.
- 
- 
- File: g77.info,  Node: QATanD Intrinsic,  Next: QCos Intrinsic,  Prev: QATan2D Intrinsic,  Up: Other Intrinsics
- 
- QATanD Intrinsic
- ................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL QATanD' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: QCos Intrinsic,  Next: QCosD Intrinsic,  Prev: QATanD Intrinsic,  Up: Other Intrinsics
- 
- QCos Intrinsic
- ..............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL QCos' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: QCosD Intrinsic,  Next: QCosH Intrinsic,  Prev: QCos Intrinsic,  Up: Other Intrinsics
- 
- QCosD Intrinsic
- ...............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL QCosD' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: QCosH Intrinsic,  Next: QDiM Intrinsic,  Prev: QCosD Intrinsic,  Up: Other Intrinsics
- 
- QCosH Intrinsic
- ...............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL QCosH' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: QDiM Intrinsic,  Next: QExp Intrinsic,  Prev: QCosH Intrinsic,  Up: Other Intrinsics
- 
- QDiM Intrinsic
- ..............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL QDiM' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: QExp Intrinsic,  Next: QExt Intrinsic,  Prev: QDiM Intrinsic,  Up: Other Intrinsics
- 
- QExp Intrinsic
- ..............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL QExp' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: QExt Intrinsic,  Next: QExtD Intrinsic,  Prev: QExp Intrinsic,  Up: Other Intrinsics
- 
- QExt Intrinsic
- ..............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL QExt' to use this name for an
- external procedure.
- 
--- 0 ----
diff -Nrc3pad gcc-3.2.3/gcc/f/g77.info-13 gcc-3.3/gcc/f/g77.info-13
*** gcc-3.2.3/gcc/f/g77.info-13	2003-04-22 07:07:24.000000000 +0000
--- gcc-3.3/gcc/f/g77.info-13	1970-01-01 00:00:00.000000000 +0000
***************
*** 1,1245 ****
- This is g77.info, produced by makeinfo version 4.5 from g77.texi.
- 
- INFO-DIR-SECTION Programming
- START-INFO-DIR-ENTRY
- * g77: (g77).                  The GNU Fortran compiler.
- END-INFO-DIR-ENTRY
-    This file documents the use and the internals of the GNU Fortran
- (`g77') compiler.  It corresponds to the GCC-3.2.3 version of `g77'.
- 
-    Published by the Free Software Foundation 59 Temple Place - Suite 330
- Boston, MA 02111-1307 USA
- 
-    Copyright (C) 1995,1996,1997,1998,1999,2000,2001,2002 Free Software
- Foundation, Inc.
- 
-    Permission is granted to copy, distribute and/or modify this document
- under the terms of the GNU Free Documentation License, Version 1.1 or
- any later version published by the Free Software Foundation; with the
- Invariant Sections being "GNU General Public License" and "Funding Free
- Software", the Front-Cover texts being (a) (see below), and with the
- Back-Cover Texts being (b) (see below).  A copy of the license is
- included in the section entitled "GNU Free Documentation License".
- 
-    (a) The FSF's Front-Cover Text is:
- 
-    A GNU Manual
- 
-    (b) The FSF's Back-Cover Text is:
- 
-    You have freedom to copy and modify this GNU Manual, like GNU
- software.  Copies published by the Free Software Foundation raise
- funds for GNU development.
- 
-    Contributed by James Craig Burley (<craig@jcb-sc.com>).  Inspired by
- a first pass at translating `g77-0.5.16/f/DOC' that was contributed to
- Craig by David Ronis (<ronis@onsager.chem.mcgill.ca>).
- 
- 
- File: g77.info,  Node: QExtD Intrinsic,  Next: QFloat Intrinsic,  Prev: QExt Intrinsic,  Up: Other Intrinsics
- 
- QExtD Intrinsic
- ...............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL QExtD' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: QFloat Intrinsic,  Next: QInt Intrinsic,  Prev: QExtD Intrinsic,  Up: Other Intrinsics
- 
- QFloat Intrinsic
- ................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL QFloat' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: QInt Intrinsic,  Next: QLog Intrinsic,  Prev: QFloat Intrinsic,  Up: Other Intrinsics
- 
- QInt Intrinsic
- ..............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL QInt' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: QLog Intrinsic,  Next: QLog10 Intrinsic,  Prev: QInt Intrinsic,  Up: Other Intrinsics
- 
- QLog Intrinsic
- ..............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL QLog' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: QLog10 Intrinsic,  Next: QMax1 Intrinsic,  Prev: QLog Intrinsic,  Up: Other Intrinsics
- 
- QLog10 Intrinsic
- ................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL QLog10' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: QMax1 Intrinsic,  Next: QMin1 Intrinsic,  Prev: QLog10 Intrinsic,  Up: Other Intrinsics
- 
- QMax1 Intrinsic
- ...............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL QMax1' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: QMin1 Intrinsic,  Next: QMod Intrinsic,  Prev: QMax1 Intrinsic,  Up: Other Intrinsics
- 
- QMin1 Intrinsic
- ...............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL QMin1' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: QMod Intrinsic,  Next: QNInt Intrinsic,  Prev: QMin1 Intrinsic,  Up: Other Intrinsics
- 
- QMod Intrinsic
- ..............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL QMod' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: QNInt Intrinsic,  Next: QSin Intrinsic,  Prev: QMod Intrinsic,  Up: Other Intrinsics
- 
- QNInt Intrinsic
- ...............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL QNInt' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: QSin Intrinsic,  Next: QSinD Intrinsic,  Prev: QNInt Intrinsic,  Up: Other Intrinsics
- 
- QSin Intrinsic
- ..............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL QSin' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: QSinD Intrinsic,  Next: QSinH Intrinsic,  Prev: QSin Intrinsic,  Up: Other Intrinsics
- 
- QSinD Intrinsic
- ...............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL QSinD' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: QSinH Intrinsic,  Next: QSqRt Intrinsic,  Prev: QSinD Intrinsic,  Up: Other Intrinsics
- 
- QSinH Intrinsic
- ...............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL QSinH' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: QSqRt Intrinsic,  Next: QTan Intrinsic,  Prev: QSinH Intrinsic,  Up: Other Intrinsics
- 
- QSqRt Intrinsic
- ...............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL QSqRt' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: QTan Intrinsic,  Next: QTanD Intrinsic,  Prev: QSqRt Intrinsic,  Up: Other Intrinsics
- 
- QTan Intrinsic
- ..............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL QTan' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: QTanD Intrinsic,  Next: QTanH Intrinsic,  Prev: QTan Intrinsic,  Up: Other Intrinsics
- 
- QTanD Intrinsic
- ...............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL QTanD' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: QTanH Intrinsic,  Next: Rename Intrinsic (function),  Prev: QTanD Intrinsic,  Up: Other Intrinsics
- 
- QTanH Intrinsic
- ...............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL QTanH' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: Rename Intrinsic (function),  Next: Secnds Intrinsic,  Prev: QTanH Intrinsic,  Up: Other Intrinsics
- 
- Rename Intrinsic (function)
- ...........................
- 
-      Rename(PATH1, PATH2)
- 
- Rename: `INTEGER(KIND=1)' function.
- 
- PATH1: `CHARACTER'; scalar; INTENT(IN).
- 
- PATH2: `CHARACTER'; scalar; INTENT(IN).
- 
- Intrinsic groups: `badu77'.
- 
- Description:
- 
-    Renames the file PATH1 to PATH2.  A null character (`CHAR(0)') marks
- the end of the names in PATH1 and PATH2--otherwise, trailing blanks in
- PATH1 and PATH2 are ignored.  See `rename(2)'.  Returns 0 on success or
- a non-zero error code.
- 
-    Due to the side effects performed by this intrinsic, the function
- form is not recommended.
- 
-    For information on other intrinsics with the same name: *Note Rename
- Intrinsic (subroutine)::.
- 
- 
- File: g77.info,  Node: Secnds Intrinsic,  Next: Signal Intrinsic (function),  Prev: Rename Intrinsic (function),  Up: Other Intrinsics
- 
- Secnds Intrinsic
- ................
- 
-      Secnds(T)
- 
- Secnds: `REAL(KIND=1)' function.
- 
- T: `REAL(KIND=1)'; scalar; INTENT(IN).
- 
- Intrinsic groups: `vxt'.
- 
- Description:
- 
-    Returns the local time in seconds since midnight minus the value T.
- 
-    This values returned by this intrinsic become numerically less than
- previous values (they wrap around) during a single run of the compiler
- program, under normal circumstances (such as running through the
- midnight hour).
- 
- 
- File: g77.info,  Node: Signal Intrinsic (function),  Next: SinD Intrinsic,  Prev: Secnds Intrinsic,  Up: Other Intrinsics
- 
- Signal Intrinsic (function)
- ...........................
- 
-      Signal(NUMBER, HANDLER)
- 
- Signal: `INTEGER(KIND=7)' function.
- 
- NUMBER: `INTEGER'; scalar; INTENT(IN).
- 
- HANDLER: Signal handler (`INTEGER FUNCTION' or `SUBROUTINE') or
- dummy/global `INTEGER(KIND=1)' scalar.
- 
- Intrinsic groups: `badu77'.
- 
- Description:
- 
-    If HANDLER is a an `EXTERNAL' routine, arranges for it to be invoked
- with a single integer argument (of system-dependent length) when signal
- NUMBER occurs.  If HANDLER is an integer, it can be used to turn off
- handling of signal NUMBER or revert to its default action.  See
- `signal(2)'.
- 
-    Note that HANDLER will be called using C conventions, so the value
- of its argument in Fortran terms is obtained by applying `%LOC()' (or
- LOC()) to it.
- 
-    The value returned by `signal(2)' is returned.
- 
-    Due to the side effects performed by this intrinsic, the function
- form is not recommended.
- 
-    _Warning:_ If the returned value is stored in an `INTEGER(KIND=1)'
- (default `INTEGER') argument, truncation of the original return value
- occurs on some systems (such as Alphas, which have 64-bit pointers but
- 32-bit default integers), with no warning issued by `g77' under normal
- circumstances.
- 
-    Therefore, the following code fragment might silently fail on some
- systems:
- 
-      INTEGER RTN
-      EXTERNAL MYHNDL
-      RTN = SIGNAL(SIGNUM, MYHNDL)
-      ...
-      ! Restore original handler:
-      RTN = SIGNAL(SIGNUM, RTN)
- 
-    The reason for the failure is that `RTN' might not hold all the
- information on the original handler for the signal, thus restoring an
- invalid handler.  This bug could manifest itself as a spurious run-time
- failure at an arbitrary point later during the program's execution, for
- example.
- 
-    _Warning:_ Use of the `libf2c' run-time library function `signal_'
- directly (such as via `EXTERNAL SIGNAL') requires use of the `%VAL()'
- construct to pass an `INTEGER' value (such as `SIG_IGN' or `SIG_DFL')
- for the HANDLER argument.
- 
-    However, while `RTN = SIGNAL(SIGNUM, %VAL(SIG_IGN))' works when
- `SIGNAL' is treated as an external procedure (and resolves, at link
- time, to `libf2c''s `signal_' routine), this construct is not valid
- when `SIGNAL' is recognized as the intrinsic of that name.
- 
-    Therefore, for maximum portability and reliability, code such
- references to the `SIGNAL' facility as follows:
- 
-      INTRINSIC SIGNAL
-      ...
-      RTN = SIGNAL(SIGNUM, SIG_IGN)
- 
-    `g77' will compile such a call correctly, while other compilers will
- generally either do so as well or reject the `INTRINSIC SIGNAL'
- statement via a diagnostic, allowing you to take appropriate action.
- 
-    For information on other intrinsics with the same name: *Note Signal
- Intrinsic (subroutine)::.
- 
- 
- File: g77.info,  Node: SinD Intrinsic,  Next: SnglQ Intrinsic,  Prev: Signal Intrinsic (function),  Up: Other Intrinsics
- 
- SinD Intrinsic
- ..............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL SinD' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: SnglQ Intrinsic,  Next: SymLnk Intrinsic (function),  Prev: SinD Intrinsic,  Up: Other Intrinsics
- 
- SnglQ Intrinsic
- ...............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL SnglQ' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: SymLnk Intrinsic (function),  Next: System Intrinsic (function),  Prev: SnglQ Intrinsic,  Up: Other Intrinsics
- 
- SymLnk Intrinsic (function)
- ...........................
- 
-      SymLnk(PATH1, PATH2)
- 
- SymLnk: `INTEGER(KIND=1)' function.
- 
- PATH1: `CHARACTER'; scalar; INTENT(IN).
- 
- PATH2: `CHARACTER'; scalar; INTENT(IN).
- 
- Intrinsic groups: `badu77'.
- 
- Description:
- 
-    Makes a symbolic link from file PATH1 to PATH2.  A null character
- (`CHAR(0)') marks the end of the names in PATH1 and PATH2--otherwise,
- trailing blanks in PATH1 and PATH2 are ignored.  Returns 0 on success
- or a non-zero error code (`ENOSYS' if the system does not provide
- `symlink(2)').
- 
-    Due to the side effects performed by this intrinsic, the function
- form is not recommended.
- 
-    For information on other intrinsics with the same name: *Note SymLnk
- Intrinsic (subroutine)::.
- 
- 
- File: g77.info,  Node: System Intrinsic (function),  Next: TanD Intrinsic,  Prev: SymLnk Intrinsic (function),  Up: Other Intrinsics
- 
- System Intrinsic (function)
- ...........................
- 
-      System(COMMAND)
- 
- System: `INTEGER(KIND=1)' function.
- 
- COMMAND: `CHARACTER'; scalar; INTENT(IN).
- 
- Intrinsic groups: `badu77'.
- 
- Description:
- 
-    Passes the command COMMAND to a shell (see `system(3)').  Returns
- the value returned by `system(3)', presumably 0 if the shell command
- succeeded.  Note that which shell is used to invoke the command is
- system-dependent and environment-dependent.
- 
-    Due to the side effects performed by this intrinsic, the function
- form is not recommended.  However, the function form can be valid in
- cases where the actual side effects performed by the call are
- unimportant to the application.
- 
-    For example, on a UNIX system, `SAME = SYSTEM('cmp a b')' does not
- perform any side effects likely to be important to the program, so the
- programmer would not care if the actual system call (and invocation of
- `cmp') was optimized away in a situation where the return value could
- be determined otherwise, or was not actually needed (`SAME' not
- actually referenced after the sample assignment statement).
- 
-    For information on other intrinsics with the same name: *Note System
- Intrinsic (subroutine)::.
- 
- 
- File: g77.info,  Node: TanD Intrinsic,  Next: Time Intrinsic (VXT),  Prev: System Intrinsic (function),  Up: Other Intrinsics
- 
- TanD Intrinsic
- ..............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL TanD' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: Time Intrinsic (VXT),  Next: UMask Intrinsic (function),  Prev: TanD Intrinsic,  Up: Other Intrinsics
- 
- Time Intrinsic (VXT)
- ....................
- 
-      CALL Time(TIME)
- 
- TIME: `CHARACTER*8'; scalar; INTENT(OUT).
- 
- Intrinsic groups: `vxt'.
- 
- Description:
- 
-    Returns in TIME a character representation of the current time as
- obtained from `ctime(3)'.
- 
-    Programs making use of this intrinsic might not be Year 10000 (Y10K)
- compliant.  For example, the date might appear, to such programs, to
- wrap around (change from a larger value to a smaller one) as of the
- Year 10000.
- 
-    *Note FDate Intrinsic (subroutine)::, for an equivalent routine.
- 
-    For information on other intrinsics with the same name: *Note Time
- Intrinsic (UNIX)::.
- 
- 
- File: g77.info,  Node: UMask Intrinsic (function),  Next: Unlink Intrinsic (function),  Prev: Time Intrinsic (VXT),  Up: Other Intrinsics
- 
- UMask Intrinsic (function)
- ..........................
- 
-      UMask(MASK)
- 
- UMask: `INTEGER(KIND=1)' function.
- 
- MASK: `INTEGER'; scalar; INTENT(IN).
- 
- Intrinsic groups: `badu77'.
- 
- Description:
- 
-    Sets the file creation mask to MASK and returns the old value.  See
- `umask(2)'.
- 
-    Due to the side effects performed by this intrinsic, the function
- form is not recommended.
- 
-    For information on other intrinsics with the same name: *Note UMask
- Intrinsic (subroutine)::.
- 
- 
- File: g77.info,  Node: Unlink Intrinsic (function),  Next: ZExt Intrinsic,  Prev: UMask Intrinsic (function),  Up: Other Intrinsics
- 
- Unlink Intrinsic (function)
- ...........................
- 
-      Unlink(FILE)
- 
- Unlink: `INTEGER(KIND=1)' function.
- 
- FILE: `CHARACTER'; scalar; INTENT(IN).
- 
- Intrinsic groups: `badu77'.
- 
- Description:
- 
-    Unlink the file FILE.  A null character (`CHAR(0)') marks the end of
- the name in FILE--otherwise, trailing blanks in FILE are ignored.
- Returns 0 on success or a non-zero error code.  See `unlink(2)'.
- 
-    Due to the side effects performed by this intrinsic, the function
- form is not recommended.
- 
-    For information on other intrinsics with the same name: *Note Unlink
- Intrinsic (subroutine)::.
- 
- 
- File: g77.info,  Node: ZExt Intrinsic,  Prev: Unlink Intrinsic (function),  Up: Other Intrinsics
- 
- ZExt Intrinsic
- ..............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL ZExt' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: Other Compilers,  Next: Other Languages,  Prev: Other Dialects,  Up: Top
- 
- Other Compilers
- ***************
- 
-    An individual Fortran source file can be compiled to an object
- (`*.o') file instead of to the final program executable.  This allows
- several portions of a program to be compiled at different times and
- linked together whenever a new version of the program is needed.
- However, it introduces the issue of "object compatibility" across the
- various object files (and libraries, or `*.a' files) that are linked
- together to produce any particular executable file.
- 
-    Object compatibility is an issue when combining, in one program,
- Fortran code compiled by more than one compiler (or more than one
- configuration of a compiler).  If the compilers disagree on how to
- transform the names of procedures, there will normally be errors when
- linking such programs.  Worse, if the compilers agree on naming, but
- disagree on issues like how to pass parameters, return arguments, and
- lay out `COMMON' areas, the earliest detected errors might be the
- incorrect results produced by the program (and that assumes these
- errors are detected, which is not always the case).
- 
-    Normally, `g77' generates code that is object-compatible with code
- generated by a version of `f2c' configured (with, for example, `f2c.h'
- definitions) to be generally compatible with `g77' as built by `gcc'.
- (Normally, `f2c' will, by default, conform to the appropriate
- configuration, but it is possible that older or perhaps even newer
- versions of `f2c', or versions having certain configuration changes to
- `f2c' internals, will produce object files that are incompatible with
- `g77'.)
- 
-    For example, a Fortran string subroutine argument will become two
- arguments on the C side: a `char *' and an `int' length.
- 
-    Much of this compatibility results from the fact that `g77' uses the
- same run-time library, `libf2c', used by `f2c', though `g77' gives its
- version the name `libg2c' so as to avoid conflicts when linking,
- installing them in the same directories, and so on.
- 
-    Other compilers might or might not generate code that is
- object-compatible with `libg2c' and current `g77', and some might offer
- such compatibility only when explicitly selected via a command-line
- option to the compiler.
- 
-    _Note: This portion of the documentation definitely needs a lot of
- work!_
- 
- * Menu:
- 
- * Dropping f2c Compatibility::  When speed is more important.
- * Compilers Other Than f2c::    Interoperation with code from other compilers.
- 
- 
- File: g77.info,  Node: Dropping f2c Compatibility,  Next: Compilers Other Than f2c,  Up: Other Compilers
- 
- Dropping `f2c' Compatibility
- ============================
- 
-    Specifying `-fno-f2c' allows `g77' to generate, in some cases,
- faster code, by not needing to allow to the possibility of linking with
- code compiled by `f2c'.
- 
-    For example, this affects how `REAL(KIND=1)', `COMPLEX(KIND=1)', and
- `COMPLEX(KIND=2)' functions are called.  With `-fno-f2c', they are
- compiled as returning the appropriate `gcc' type (`float', `__complex__
- float', `__complex__ double', in many configurations).
- 
-    With `-ff2c' in force, they are compiled differently (with perhaps
- slower run-time performance) to accommodate the restrictions inherent
- in `f2c''s use of K&R C as an intermediate language--`REAL(KIND=1)'
- functions return C's `double' type, while `COMPLEX' functions return
- `void' and use an extra argument pointing to a place for the functions
- to return their values.
- 
-    It is possible that, in some cases, leaving `-ff2c' in force might
- produce faster code than using `-fno-f2c'.  Feel free to experiment,
- but remember to experiment with changing the way _entire programs and
- their Fortran libraries are compiled_ at a time, since this sort of
- experimentation affects the interface of code generated for a Fortran
- source file--that is, it affects object compatibility.
- 
-    Note that `f2c' compatibility is a fairly static target to achieve,
- though not necessarily perfectly so, since, like `g77', it is still
- being improved.  However, specifying `-fno-f2c' causes `g77' to
- generate code that will probably be incompatible with code generated by
- future versions of `g77' when the same option is in force.  You should
- make sure you are always able to recompile complete programs from
- source code when upgrading to new versions of `g77' or `f2c',
- especially when using options such as `-fno-f2c'.
- 
-    Therefore, if you are using `g77' to compile libraries and other
- object files for possible future use and you don't want to require
- recompilation for future use with subsequent versions of `g77', you
- might want to stick with `f2c' compatibility for now, and carefully
- watch for any announcements about changes to the `f2c'/`libf2c'
- interface that might affect existing programs (thus requiring
- recompilation).
- 
-    It is probable that a future version of `g77' will not, by default,
- generate object files compatible with `f2c', and that version probably
- would no longer use `libf2c'.  If you expect to depend on this
- compatibility in the long term, use the options `-ff2c -ff2c-library'
- when compiling all of the applicable code.  This should cause future
- versions of `g77' either to produce compatible code (at the expense of
- the availability of some features and performance), or at the very
- least, to produce diagnostics.
- 
-    (The library `g77' produces will no longer be named `libg2c' when it
- is no longer generally compatible with `libf2c'.  It will likely be
- referred to, and, if installed as a distinct library, named `libg77',
- or some other as-yet-unused name.)
- 
- 
- File: g77.info,  Node: Compilers Other Than f2c,  Prev: Dropping f2c Compatibility,  Up: Other Compilers
- 
- Compilers Other Than `f2c'
- ==========================
- 
-    On systems with Fortran compilers other than `f2c' and `g77', code
- compiled by `g77' is not expected to work well with code compiled by
- the native compiler.  (This is true for `f2c'-compiled objects as well.)
- Libraries compiled with the native compiler probably will have to be
- recompiled with `g77' to be used with `g77'-compiled code.
- 
-    Reasons for such incompatibilities include:
- 
-    * There might be differences in the way names of Fortran procedures
-      are translated for use in the system's object-file format.  For
-      example, the statement `CALL FOO' might be compiled by `g77' to
-      call a procedure the linker `ld' sees given the name `_foo_',
-      while the apparently corresponding statement `SUBROUTINE FOO'
-      might be compiled by the native compiler to define the
-      linker-visible name `_foo', or `_FOO_', and so on.
- 
-    * There might be subtle type mismatches which cause subroutine
-      arguments and function return values to get corrupted.
- 
-      This is why simply getting `g77' to transform procedure names the
-      same way a native compiler does is not usually a good idea--unless
-      some effort has been made to ensure that, aside from the way the
-      two compilers transform procedure names, everything else about the
-      way they generate code for procedure interfaces is identical.
- 
-    * Native compilers use libraries of private I/O routines which will
-      not be available at link time unless you have the native
-      compiler--and you would have to explicitly ask for them.
- 
-      For example, on the Sun you would have to add `-L/usr/lang/SCx.x
-      -lF77 -lV77' to the link command.
- 
- 
- File: g77.info,  Node: Other Languages,  Next: Debugging and Interfacing,  Prev: Other Compilers,  Up: Top
- 
- Other Languages
- ***************
- 
-    _Note: This portion of the documentation definitely needs a lot of
- work!_
- 
- * Menu:
- 
- * Interoperating with C and C++::
- 
- 
- File: g77.info,  Node: Interoperating with C and C++,  Up: Other Languages
- 
- Tools and advice for interoperating with C and C++
- ==================================================
- 
-    The following discussion assumes that you are running `g77' in `f2c'
- compatibility mode, i.e. not using `-fno-f2c'.  It provides some advice
- about quick and simple techniques for linking Fortran and C (or C++),
- the most common requirement.  For the full story consult the
- description of code generation.  *Note Debugging and Interfacing::.
- 
-    When linking Fortran and C, it's usually best to use `g77' to do the
- linking so that the correct libraries are included (including the maths
- one).  If you're linking with C++ you will want to add `-lstdc++',
- `-lg++' or whatever.  If you need to use another driver program (or
- `ld' directly), you can find out what linkage options `g77' passes by
- running `g77 -v'.
- 
- * Menu:
- 
- * C Interfacing Tools::
- * C Access to Type Information::
- * f2c Skeletons and Prototypes::
- * C++ Considerations::
- * Startup Code::
- 
- 
- File: g77.info,  Node: C Interfacing Tools,  Next: C Access to Type Information,  Up: Interoperating with C and C++
- 
- C Interfacing Tools
- -------------------
- 
-    Even if you don't actually use it as a compiler, `f2c' from
- `ftp://ftp.netlib.org/f2c/src', can be a useful tool when you're
- interfacing (linking) Fortran and C.  *Note Generating Skeletons and
- Prototypes with `f2c': f2c Skeletons and Prototypes.
- 
-    To use `f2c' for this purpose you only need retrieve and build the
- `src' directory from the distribution, consult the `README'
- instructions there for machine-specifics, and install the `f2c' program
- on your path.
- 
-    Something else that might be useful is `cfortran.h' from
- `ftp://zebra.desy.de/cfortran'.  This is a fairly general tool which
- can be used to generate interfaces for calling in both directions
- between Fortran and C.  It can be used in `f2c' mode with
- `g77'--consult its documentation for details.
- 
- 
- File: g77.info,  Node: C Access to Type Information,  Next: f2c Skeletons and Prototypes,  Prev: C Interfacing Tools,  Up: Interoperating with C and C++
- 
- Accessing Type Information in C
- -------------------------------
- 
-    Generally, C code written to link with `g77' code--calling and/or
- being called from Fortran--should `#include <g2c.h>' to define the C
- versions of the Fortran types.  Don't assume Fortran `INTEGER' types
- correspond to C `int's, for instance; instead, declare them as
- `integer', a type defined by `g2c.h'.  `g2c.h' is installed where `gcc'
- will find it by default, assuming you use a copy of `gcc' compatible
- with `g77', probably built at the same time as `g77'.
- 
- 
- File: g77.info,  Node: f2c Skeletons and Prototypes,  Next: C++ Considerations,  Prev: C Access to Type Information,  Up: Interoperating with C and C++
- 
- Generating Skeletons and Prototypes with `f2c'
- ----------------------------------------------
- 
-    A simple and foolproof way to write `g77'-callable C routines--e.g.
- to interface with an existing library--is to write a file (named, for
- example, `fred.f') of dummy Fortran skeletons comprising just the
- declaration of the routine(s) and dummy arguments plus `END' statements.
- Then run `f2c' on file `fred.f' to produce `fred.c' into which you can
- edit useful code, confident the calling sequence is correct, at least.
- (There are some errors otherwise commonly made in generating C
- interfaces with `f2c' conventions, such as not using `doublereal' as
- the return type of a `REAL' `FUNCTION'.)
- 
-    `f2c' also can help with calling Fortran from C, using its `-P'
- option to generate C prototypes appropriate for calling the Fortran.(1)
- If the Fortran code containing any routines to be called from C is in
- file `joe.f', use the command `f2c -P joe.f' to generate the file
- `joe.P' containing prototype information.  `#include' this in the C
- which has to call the Fortran routines to make sure you get it right.
- 
-    *Note Arrays (DIMENSION): Arrays, for information on the differences
- between the way Fortran (including compilers like `g77') and C handle
- arrays.
- 
-    ---------- Footnotes ----------
- 
-    (1) The files generated like this can also be used for inter-unit
- consistency checking of dummy and actual arguments, although the
- `ftnchek' tool from `ftp://ftp.netlib.org/fortran' or
- `ftp://ftp.dsm.fordham.edu' is probably better for this purpose.
- 
- 
- File: g77.info,  Node: C++ Considerations,  Next: Startup Code,  Prev: f2c Skeletons and Prototypes,  Up: Interoperating with C and C++
- 
- C++ Considerations
- ------------------
- 
-    `f2c' can be used to generate suitable code for compilation with a
- C++ system using the `-C++' option.  The important thing about linking
- `g77'-compiled code with C++ is that the prototypes for the `g77'
- routines must specify C linkage to avoid name mangling.  So, use an
- `extern "C"' declaration.  `f2c''s `-C++' option will take care of this
- when generating skeletons or prototype files as above, and also avoid
- clashes with C++ reserved words in addition to those in C.
- 
- 
- File: g77.info,  Node: Startup Code,  Prev: C++ Considerations,  Up: Interoperating with C and C++
- 
- Startup Code
- ------------
- 
-    Unlike with some runtime systems, it shouldn't be necessary (unless
- there are bugs) to use a Fortran main program unit to ensure the
- runtime--specifically the I/O system--is initialized.
- 
-    However, to use the `g77' intrinsics `GETARG' and `IARGC', either
- the `main' routine from the `libg2c' library must be used, or the
- `f_setarg' routine (new as of `egcs' version 1.1 and `g77' version
- 0.5.23) must be called with the appropriate `argc' and `argv' arguments
- prior to the program calling `GETARG' or `IARGC'.
- 
-    To provide more flexibility for mixed-language programming involving
- `g77' while allowing for shared libraries, as of `egcs' version 1.1 and
- `g77' version 0.5.23, `g77''s `main' routine in `libg2c' does the
- following, in order:
- 
-   1. Calls `f_setarg' with the incoming `argc' and `argv' arguments, in
-      the same order as for `main' itself.
- 
-      This sets up the command-line environment for `GETARG' and `IARGC'.
- 
-   2. Calls `f_setsig' (with no arguments).
- 
-      This sets up the signaling and exception environment.
- 
-   3. Calls `f_init' (with no arguments).
- 
-      This initializes the I/O environment, though that should not be
-      necessary, as all I/O functions in `libf2c' are believed to call
-      `f_init' automatically, if necessary.
- 
-      (A future version of `g77' might skip this explicit step, to speed
-      up normal exit of a program.)
- 
-   4. Arranges for `f_exit' to be called (with no arguments) when the
-      program exits.
- 
-      This ensures that the I/O environment is properly shut down before
-      the program exits normally.  Otherwise, output buffers might not
-      be fully flushed, scratch files might not be deleted, and so on.
- 
-      The simple way `main' does this is to call `f_exit' itself after
-      calling `MAIN__' (in the next step).
- 
-      However, this does not catch the cases where the program might
-      call `exit' directly, instead of using the `EXIT' intrinsic
-      (implemented as `exit_' in `libf2c').
- 
-      So, `main' attempts to use the operating environment's `onexit' or
-      `atexit' facility, if available, to cause `f_exit' to be called
-      automatically upon any invocation of `exit'.
- 
-   5. Calls `MAIN__' (with no arguments).
- 
-      This starts executing the Fortran main program unit for the
-      application.  (Both `g77' and `f2c' currently compile a main
-      program unit so that its global name is `MAIN__'.)
- 
-   6. If no `onexit' or `atexit' is provided by the system, calls
-      `f_exit'.
- 
-   7. Calls `exit' with a zero argument, to signal a successful program
-      termination.
- 
-   8. Returns a zero value to the caller, to signal a successful program
-      termination, in case `exit' doesn't exit on the system.
- 
-    All of the above names are C `extern' names, i.e. not mangled.
- 
-    When using the `main' procedure provided by `g77' without a Fortran
- main program unit, you need to provide `MAIN__' as the entry point for
- your C code.  (Make sure you link the object file that defines that
- entry point with the rest of your program.)
- 
-    To provide your own `main' procedure in place of `g77''s, make sure
- you specify the object file defining that procedure _before_ `-lg2c' on
- the `g77' command line.  Since the `-lg2c' option is implicitly
- provided, this is usually straightforward.  (Use the `--verbose' option
- to see how and where `g77' implicitly adds `-lg2c' in a command line
- that will link the program.  Feel free to specify `-lg2c' explicitly,
- as appropriate.)
- 
-    However, when providing your own `main', make sure you perform the
- appropriate tasks in the appropriate order.  For example, if your
- `main' does not call `f_setarg', make sure the rest of your application
- does not call `GETARG' or `IARGC'.
- 
-    And, if your `main' fails to ensure that `f_exit' is called upon
- program exit, some files might end up incompletely written, some
- scratch files might be left lying around, and some existing files being
- written might be left with old data not properly truncated at the end.
- 
-    Note that, generally, the `g77' operating environment does not
- depend on a procedure named `MAIN__' actually being called prior to any
- other `g77'-compiled code.  That is, `MAIN__' does not, itself, set up
- any important operating-environment characteristics upon which other
- code might depend.  This might change in future versions of `g77', with
- appropriate notification in the release notes.
- 
-    For more information, consult the source code for the above routines.
- These are in `gcc/libf2c/libF77/', named `main.c', `setarg.c',
- `setsig.c', `getarg_.c', and `iargc_.c'.
- 
-    Also, the file `gcc/gcc/f/com.c' contains the code `g77' uses to
- open-code (inline) references to `IARGC'.
- 
- 
- File: g77.info,  Node: Debugging and Interfacing,  Next: Collected Fortran Wisdom,  Prev: Other Languages,  Up: Top
- 
- Debugging and Interfacing
- *************************
- 
-    GNU Fortran currently generates code that is object-compatible with
- the `f2c' converter.  Also, it avoids limitations in the current GBE,
- such as the inability to generate a procedure with multiple entry
- points, by generating code that is structured differently (in terms of
- procedure names, scopes, arguments, and so on) than might be expected.
- 
-    As a result, writing code in other languages that calls on, is
- called by, or shares in-memory data with `g77'-compiled code generally
- requires some understanding of the way `g77' compiles code for various
- constructs.
- 
-    Similarly, using a debugger to debug `g77'-compiled code, even if
- that debugger supports native Fortran debugging, generally requires
- this sort of information.
- 
-    This section describes some of the basic information on how `g77'
- compiles code for constructs involving interfaces to other languages
- and to debuggers.
- 
-    _Caution:_ Much or all of this information pertains to only the
- current release of `g77', sometimes even to using certain compiler
- options with `g77' (such as `-fno-f2c').  Do not write code that
- depends on this information without clearly marking said code as
- nonportable and subject to review for every new release of `g77'.  This
- information is provided primarily to make debugging of code generated
- by this particular release of `g77' easier for the user, and partly to
- make writing (generally nonportable) interface code easier.  Both of
- these activities require tracking changes in new version of `g77' as
- they are installed, because new versions can change the behaviors
- described in this section.
- 
- * Menu:
- 
- * Main Program Unit::  How `g77' compiles a main program unit.
- * Procedures::         How `g77' constructs parameter lists
-                        for procedures.
- * Functions::          Functions returning floating-point or character data.
- * Names::              Naming of user-defined variables, procedures, etc.
- * Common Blocks::      Accessing common variables while debugging.
- * Local Equivalence Areas::  Accessing `EQUIVALENCE' while debugging.
- * Complex Variables::  How `g77' performs complex arithmetic.
- * Arrays::             Dealing with (possibly multi-dimensional) arrays.
- * Adjustable Arrays::  Special consideration for adjustable arrays.
- * Alternate Entry Points::  How `g77' implements alternate `ENTRY'.
- * Alternate Returns::  How `g77' handles alternate returns.
- * Assigned Statement Labels::  How `g77' handles `ASSIGN'.
- * Run-time Library Errors::  Meanings of some `IOSTAT=' values.
- 
- 
- File: g77.info,  Node: Main Program Unit,  Next: Procedures,  Up: Debugging and Interfacing
- 
- Main Program Unit (PROGRAM)
- ===========================
- 
-    When `g77' compiles a main program unit, it gives it the public
- procedure name `MAIN__'.  The `libg2c' library has the actual `main()'
- procedure as is typical of C-based environments, and it is this
- procedure that performs some initial start-up activity and then calls
- `MAIN__'.
- 
-    Generally, `g77' and `libg2c' are designed so that you need not
- include a main program unit written in Fortran in your program--it can
- be written in C or some other language.  Especially for I/O handling,
- this is the case, although `g77' version 0.5.16 includes a bug fix for
- `libg2c' that solved a problem with using the `OPEN' statement as the
- first Fortran I/O activity in a program without a Fortran main program
- unit.
- 
-    However, if you don't intend to use `g77' (or `f2c') to compile your
- main program unit--that is, if you intend to compile a `main()'
- procedure using some other language--you should carefully examine the
- code for `main()' in `libg2c', found in the source file
- `gcc/libf2c/libF77/main.c', to see what kinds of things might need to
- be done by your `main()' in order to provide the Fortran environment
- your Fortran code is expecting.
- 
-    For example, `libg2c''s `main()' sets up the information used by the
- `IARGC' and `GETARG' intrinsics.  Bypassing `libg2c''s `main()' without
- providing a substitute for this activity would mean that invoking
- `IARGC' and `GETARG' would produce undefined results.
- 
-    When debugging, one implication of the fact that `main()', which is
- the place where the debugged program "starts" from the debugger's point
- of view, is in `libg2c' is that you won't be starting your Fortran
- program at a point you recognize as your Fortran code.
- 
-    The standard way to get around this problem is to set a break point
- (a one-time, or temporary, break point will do) at the entrance to
- `MAIN__', and then run the program.  A convenient way to do so is to
- add the `gdb' command
- 
-      tbreak MAIN__
- 
- to the file `.gdbinit' in the directory in which you're debugging
- (using `gdb').
- 
-    After doing this, the debugger will see the current execution point
- of the program as at the beginning of the main program unit of your
- program.
- 
-    Of course, if you really want to set a break point at some other
- place in your program and just start the program running, without first
- breaking at `MAIN__', that should work fine.
- 
- 
- File: g77.info,  Node: Procedures,  Next: Functions,  Prev: Main Program Unit,  Up: Debugging and Interfacing
- 
- Procedures (SUBROUTINE and FUNCTION)
- ====================================
- 
-    Currently, `g77' passes arguments via reference--specifically, by
- passing a pointer to the location in memory of a variable, array, array
- element, a temporary location that holds the result of evaluating an
- expression, or a temporary or permanent location that holds the value
- of a constant.
- 
-    Procedures that accept `CHARACTER' arguments are implemented by
- `g77' so that each `CHARACTER' argument has two actual arguments.
- 
-    The first argument occupies the expected position in the argument
- list and has the user-specified name.  This argument is a pointer to an
- array of characters, passed by the caller.
- 
-    The second argument is appended to the end of the user-specified
- calling sequence and is named `__g77_length_X', where X is the
- user-specified name.  This argument is of the C type `ftnlen' (see
- `gcc/libf2c/g2c.h.in' for information on that type) and is the number
- of characters the caller has allocated in the array pointed to by the
- first argument.
- 
-    A procedure will ignore the length argument if `X' is not declared
- `CHARACTER*(*)', because for other declarations, it knows the length.
- Not all callers necessarily "know" this, however, which is why they all
- pass the extra argument.
- 
-    The contents of the `CHARACTER' argument are specified by the
- address passed in the first argument (named after it).  The procedure
- can read or write these contents as appropriate.
- 
-    When more than one `CHARACTER' argument is present in the argument
- list, the length arguments are appended in the order the original
- arguments appear.  So `CALL FOO('HI','THERE')' is implemented in C as
- `foo("hi","there",2,5);', ignoring the fact that `g77' does not provide
- the trailing null bytes on the constant strings (`f2c' does provide
- them, but they are unnecessary in a Fortran environment, and you should
- not expect them to be there).
- 
-    Note that the above information applies to `CHARACTER' variables and
- arrays *only*.  It does *not* apply to external `CHARACTER' functions
- or to intrinsic `CHARACTER' functions.  That is, no second length
- argument is passed to `FOO' in this case:
- 
-      CHARACTER X
-      EXTERNAL X
-      CALL FOO(X)
- 
- Nor does `FOO' expect such an argument in this case:
- 
-      SUBROUTINE FOO(X)
-      CHARACTER X
-      EXTERNAL X
- 
-    Because of this implementation detail, if a program has a bug such
- that there is disagreement as to whether an argument is a procedure,
- and the type of the argument is `CHARACTER', subtle symptoms might
- appear.
- 
- 
- File: g77.info,  Node: Functions,  Next: Names,  Prev: Procedures,  Up: Debugging and Interfacing
- 
- Functions (FUNCTION and RETURN)
- ===============================
- 
-    `g77' handles in a special way functions that return the following
- types:
- 
-    * `CHARACTER'
- 
-    * `COMPLEX'
- 
-    * `REAL(KIND=1)'
- 
-    For `CHARACTER', `g77' implements a subroutine (a C function
- returning `void') with two arguments prepended: `__g77_result', which
- the caller passes as a pointer to a `char' array expected to hold the
- return value, and `__g77_length', which the caller passes as an
- `ftnlen' value specifying the length of the return value as declared in
- the calling program.  For `CHARACTER*(*)', the called function uses
- `__g77_length' to determine the size of the array that `__g77_result'
- points to; otherwise, it ignores that argument.
- 
-    For `COMPLEX', when `-ff2c' is in force, `g77' implements a
- subroutine with one argument prepended: `__g77_result', which the
- caller passes as a pointer to a variable of the type of the function.
- The called function writes the return value into this variable instead
- of returning it as a function value.  When `-fno-f2c' is in force,
- `g77' implements a `COMPLEX' function as `gcc''s `__complex__ float' or
- `__complex__ double' function (or an emulation thereof, when
- `-femulate-complex' is in effect), returning the result of the function
- in the same way as `gcc' would.
- 
-    For `REAL(KIND=1)', when `-ff2c' is in force, `g77' implements a
- function that actually returns `REAL(KIND=2)' (typically C's `double'
- type).  When `-fno-f2c' is in force, `REAL(KIND=1)' functions return
- `float'.
- 
- 
- File: g77.info,  Node: Names,  Next: Common Blocks,  Prev: Functions,  Up: Debugging and Interfacing
- 
- Names
- =====
- 
-    Fortran permits each implementation to decide how to represent names
- as far as how they're seen in other contexts, such as debuggers and
- when interfacing to other languages, and especially as far as how
- casing is handled.
- 
-    External names--names of entities that are public, or "accessible",
- to all modules in a program--normally have an underscore (`_') appended
- by `g77', to generate code that is compatible with `f2c'.  External
- names include names of Fortran things like common blocks, external
- procedures (subroutines and functions, but not including statement
- functions, which are internal procedures), and entry point names.
- 
-    However, use of the `-fno-underscoring' option disables this kind of
- transformation of external names (though inhibiting the transformation
- certainly improves the chances of colliding with incompatible externals
- written in other languages--but that might be intentional.
- 
-    When `-funderscoring' is in force, any name (external or local) that
- already has at least one underscore in it is implemented by `g77' by
- appending two underscores.  (This second underscore can be disabled via
- the `-fno-second-underscore' option.)  External names are changed this
- way for `f2c' compatibility.  Local names are changed this way to avoid
- collisions with external names that are different in the source
- code--`f2c' does the same thing, but there's no compatibility issue
- there except for user expectations while debugging.
- 
-    For example:
- 
-      Max_Cost = 0
- 
- Here, a user would, in the debugger, refer to this variable using the
- name `max_cost__' (or `MAX_COST__' or `Max_Cost__', as described below).
- (We hope to improve `g77' in this regard in the future--don't write
- scripts depending on this behavior!  Also, consider experimenting with
- the `-fno-underscoring' option to try out debugging without having to
- massage names by hand like this.)
- 
-    `g77' provides a number of command-line options that allow the user
- to control how case mapping is handled for source files.  The default
- is the traditional UNIX model for Fortran compilers--names are mapped
- to lower case.  Other command-line options can be specified to map
- names to upper case, or to leave them exactly as written in the source
- file.
- 
-    For example:
- 
-      Foo = 9.436
- 
- Here, it is normally the case that the variable assigned will be named
- `foo'.  This would be the name to enter when using a debugger to access
- the variable.
- 
-    However, depending on the command-line options specified, the name
- implemented by `g77' might instead be `FOO' or even `Foo', thus
- affecting how debugging is done.
- 
-    Also:
- 
-      Call Foo
- 
- This would normally call a procedure that, if it were in a separate C
- program, be defined starting with the line:
- 
-      void foo_()
- 
- However, `g77' command-line options could be used to change the casing
- of names, resulting in the name `FOO_' or `Foo_' being given to the
- procedure instead of `foo_', and the `-fno-underscoring' option could
- be used to inhibit the appending of the underscore to the name.
- 
- 
- File: g77.info,  Node: Common Blocks,  Next: Local Equivalence Areas,  Prev: Names,  Up: Debugging and Interfacing
- 
- Common Blocks (COMMON)
- ======================
- 
-    `g77' names and lays out `COMMON' areas the same way `f2c' does, for
- compatibility with `f2c'.
- 
- 
- File: g77.info,  Node: Local Equivalence Areas,  Next: Complex Variables,  Prev: Common Blocks,  Up: Debugging and Interfacing
- 
- Local Equivalence Areas (EQUIVALENCE)
- =====================================
- 
-    `g77' treats storage-associated areas involving a `COMMON' block as
- explained in the section on common blocks.
- 
-    A local `EQUIVALENCE' area is a collection of variables and arrays
- connected to each other in any way via `EQUIVALENCE', none of which are
- listed in a `COMMON' statement.
- 
-    (_Note:_ `g77' version 0.5.18 and earlier chose the name for X using
- a different method when more than one name was in the list of names of
- entities placed at the beginning of the array.  Though the
- documentation specified that the first name listed in the `EQUIVALENCE'
- statements was chosen for X, `g77' in fact chose the name using a
- method that was so complicated, it seemed easier to change it to an
- alphabetical sort than to describe the previous method in the
- documentation.)
- 
- 
- File: g77.info,  Node: Complex Variables,  Next: Arrays,  Prev: Local Equivalence Areas,  Up: Debugging and Interfacing
- 
- Complex Variables (COMPLEX)
- ===========================
- 
-    As of 0.5.20, `g77' defaults to handling `COMPLEX' types (and
- related intrinsics, constants, functions, and so on) in a manner that
- makes direct debugging involving these types in Fortran language mode
- difficult.
- 
-    Essentially, `g77' implements these types using an internal
- construct similar to C's `struct', at least as seen by the `gcc' back
- end.
- 
-    Currently, the back end, when outputting debugging info with the
- compiled code for the assembler to digest, does not detect these
- `struct' types as being substitutes for Fortran complex.  As a result,
- the Fortran language modes of debuggers such as `gdb' see these types
- as C `struct' types, which they might or might not support.
- 
-    Until this is fixed, switch to C language mode to work with entities
- of `COMPLEX' type and then switch back to Fortran language mode
- afterward.  (In `gdb', this is accomplished via `set lang c' and either
- `set lang fortran' or `set lang auto'.)
- 
--- 0 ----
diff -Nrc3pad gcc-3.2.3/gcc/f/g77.info-14 gcc-3.3/gcc/f/g77.info-14
*** gcc-3.2.3/gcc/f/g77.info-14	2003-04-22 07:07:24.000000000 +0000
--- gcc-3.3/gcc/f/g77.info-14	1970-01-01 00:00:00.000000000 +0000
***************
*** 1,1066 ****
- This is g77.info, produced by makeinfo version 4.5 from g77.texi.
- 
- INFO-DIR-SECTION Programming
- START-INFO-DIR-ENTRY
- * g77: (g77).                  The GNU Fortran compiler.
- END-INFO-DIR-ENTRY
-    This file documents the use and the internals of the GNU Fortran
- (`g77') compiler.  It corresponds to the GCC-3.2.3 version of `g77'.
- 
-    Published by the Free Software Foundation 59 Temple Place - Suite 330
- Boston, MA 02111-1307 USA
- 
-    Copyright (C) 1995,1996,1997,1998,1999,2000,2001,2002 Free Software
- Foundation, Inc.
- 
-    Permission is granted to copy, distribute and/or modify this document
- under the terms of the GNU Free Documentation License, Version 1.1 or
- any later version published by the Free Software Foundation; with the
- Invariant Sections being "GNU General Public License" and "Funding Free
- Software", the Front-Cover texts being (a) (see below), and with the
- Back-Cover Texts being (b) (see below).  A copy of the license is
- included in the section entitled "GNU Free Documentation License".
- 
-    (a) The FSF's Front-Cover Text is:
- 
-    A GNU Manual
- 
-    (b) The FSF's Back-Cover Text is:
- 
-    You have freedom to copy and modify this GNU Manual, like GNU
- software.  Copies published by the Free Software Foundation raise
- funds for GNU development.
- 
-    Contributed by James Craig Burley (<craig@jcb-sc.com>).  Inspired by
- a first pass at translating `g77-0.5.16/f/DOC' that was contributed to
- Craig by David Ronis (<ronis@onsager.chem.mcgill.ca>).
- 
- 
- File: g77.info,  Node: Arrays,  Next: Adjustable Arrays,  Prev: Complex Variables,  Up: Debugging and Interfacing
- 
- Arrays (DIMENSION)
- ==================
- 
-    Fortran uses "column-major ordering" in its arrays.  This differs
- from other languages, such as C, which use "row-major ordering".  The
- difference is that, with Fortran, array elements adjacent to each other
- in memory differ in the _first_ subscript instead of the last;
- `A(5,10,20)' immediately follows `A(4,10,20)', whereas with row-major
- ordering it would follow `A(5,10,19)'.
- 
-    This consideration affects not only interfacing with and debugging
- Fortran code, it can greatly affect how code is designed and written,
- especially when code speed and size is a concern.
- 
-    Fortran also differs from C, a popular language for interfacing and
- to support directly in debuggers, in the way arrays are treated.  In C,
- arrays are single-dimensional and have interesting relationships to
- pointers, neither of which is true for Fortran.  As a result, dealing
- with Fortran arrays from within an environment limited to C concepts
- can be challenging.
- 
-    For example, accessing the array element `A(5,10,20)' is easy enough
- in Fortran (use `A(5,10,20)'), but in C some difficult machinations are
- needed.  First, C would treat the A array as a single-dimension array.
- Second, C does not understand low bounds for arrays as does Fortran.
- Third, C assumes a low bound of zero (0), while Fortran defaults to a
- low bound of one (1) and can supports an arbitrary low bound.
- Therefore, calculations must be done to determine what the C equivalent
- of `A(5,10,20)' would be, and these calculations require knowing the
- dimensions of `A'.
- 
-    For `DIMENSION A(2:11,21,0:29)', the calculation of the offset of
- `A(5,10,20)' would be:
- 
-        (5-2)
-      + (10-1)*(11-2+1)
-      + (20-0)*(11-2+1)*(21-1+1)
-      = 4293
- 
- So the C equivalent in this case would be `a[4293]'.
- 
-    When using a debugger directly on Fortran code, the C equivalent
- might not work, because some debuggers cannot understand the notion of
- low bounds other than zero.  However, unlike `f2c', `g77' does inform
- the GBE that a multi-dimensional array (like `A' in the above example)
- is really multi-dimensional, rather than a single-dimensional array, so
- at least the dimensionality of the array is preserved.
- 
-    Debuggers that understand Fortran should have no trouble with
- non-zero low bounds, but for non-Fortran debuggers, especially C
- debuggers, the above example might have a C equivalent of `a[4305]'.
- This calculation is arrived at by eliminating the subtraction of the
- lower bound in the first parenthesized expression on each line--that
- is, for `(5-2)' substitute `(5)', for `(10-1)' substitute `(10)', and
- for `(20-0)' substitute `(20)'.  Actually, the implication of this can
- be that the expression `*(&a[2][1][0] + 4293)' works fine, but that
- `a[20][10][5]' produces the equivalent of `*(&a[0][0][0] + 4305)'
- because of the missing lower bounds.
- 
-    Come to think of it, perhaps the behavior is due to the debugger
- internally compensating for the lower bounds by offsetting the base
- address of `a', leaving `&a' set lower, in this case, than
- `&a[2][1][0]' (the address of its first element as identified by
- subscripts equal to the corresponding lower bounds).
- 
-    You know, maybe nobody really needs to use arrays.
- 
- 
- File: g77.info,  Node: Adjustable Arrays,  Next: Alternate Entry Points,  Prev: Arrays,  Up: Debugging and Interfacing
- 
- Adjustable Arrays (DIMENSION)
- =============================
- 
-    Adjustable and automatic arrays in Fortran require the implementation
- (in this case, the `g77' compiler) to "memorize" the expressions that
- dimension the arrays each time the procedure is invoked.  This is so
- that subsequent changes to variables used in those expressions, made
- during execution of the procedure, do not have any effect on the
- dimensions of those arrays.
- 
-    For example:
- 
-      REAL ARRAY(5)
-      DATA ARRAY/5*2/
-      CALL X(ARRAY, 5)
-      END
-      SUBROUTINE X(A, N)
-      DIMENSION A(N)
-      N = 20
-      PRINT *, N, A
-      END
- 
- Here, the implementation should, when running the program, print
- something like:
- 
-      20   2.  2.  2.  2.  2.
- 
- Note that this shows that while the value of `N' was successfully
- changed, the size of the `A' array remained at 5 elements.
- 
-    To support this, `g77' generates code that executes before any user
- code (and before the internally generated computed `GOTO' to handle
- alternate entry points, as described below) that evaluates each
- (nonconstant) expression in the list of subscripts for an array, and
- saves the result of each such evaluation to be used when determining
- the size of the array (instead of re-evaluating the expressions).
- 
-    So, in the above example, when `X' is first invoked, code is
- executed that copies the value of `N' to a temporary.  And that same
- temporary serves as the actual high bound for the single dimension of
- the `A' array (the low bound being the constant 1).  Since the user
- program cannot (legitimately) change the value of the temporary during
- execution of the procedure, the size of the array remains constant
- during each invocation.
- 
-    For alternate entry points, the code `g77' generates takes into
- account the possibility that a dummy adjustable array is not actually
- passed to the actual entry point being invoked at that time.  In that
- case, the public procedure implementing the entry point passes to the
- master private procedure implementing all the code for the entry points
- a `NULL' pointer where a pointer to that adjustable array would be
- expected.  The `g77'-generated code doesn't attempt to evaluate any of
- the expressions in the subscripts for an array if the pointer to that
- array is `NULL' at run time in such cases.  (Don't depend on this
- particular implementation by writing code that purposely passes `NULL'
- pointers where the callee expects adjustable arrays, even if you know
- the callee won't reference the arrays--nor should you pass `NULL'
- pointers for any dummy arguments used in calculating the bounds of such
- arrays or leave undefined any values used for that purpose in
- COMMON--because the way `g77' implements these things might change in
- the future!)
- 
- 
- File: g77.info,  Node: Alternate Entry Points,  Next: Alternate Returns,  Prev: Adjustable Arrays,  Up: Debugging and Interfacing
- 
- Alternate Entry Points (ENTRY)
- ==============================
- 
-    The GBE does not understand the general concept of alternate entry
- points as Fortran provides via the ENTRY statement.  `g77' gets around
- this by using an approach to compiling procedures having at least one
- `ENTRY' statement that is almost identical to the approach used by
- `f2c'.  (An alternate approach could be used that would probably
- generate faster, but larger, code that would also be a bit easier to
- debug.)
- 
-    Information on how `g77' implements `ENTRY' is provided for those
- trying to debug such code.  The choice of implementation seems unlikely
- to affect code (compiled in other languages) that interfaces to such
- code.
- 
-    `g77' compiles exactly one public procedure for the primary entry
- point of a procedure plus each `ENTRY' point it specifies, as usual.
- That is, in terms of the public interface, there is no difference
- between
- 
-      SUBROUTINE X
-      END
-      SUBROUTINE Y
-      END
- 
- and:
- 
-      SUBROUTINE X
-      ENTRY Y
-      END
- 
-    The difference between the above two cases lies in the code compiled
- for the `X' and `Y' procedures themselves, plus the fact that, for the
- second case, an extra internal procedure is compiled.
- 
-    For every Fortran procedure with at least one `ENTRY' statement,
- `g77' compiles an extra procedure named `__g77_masterfun_X', where X is
- the name of the primary entry point (which, in the above case, using
- the standard compiler options, would be `x_' in C).
- 
-    This extra procedure is compiled as a private procedure--that is, a
- procedure not accessible by name to separately compiled modules.  It
- contains all the code in the program unit, including the code for the
- primary entry point plus for every entry point.  (The code for each
- public procedure is quite short, and explained later.)
- 
-    The extra procedure has some other interesting characteristics.
- 
-    The argument list for this procedure is invented by `g77'.  It
- contains a single integer argument named `__g77_which_entrypoint',
- passed by value (as in Fortran's `%VAL()' intrinsic), specifying the
- entry point index--0 for the primary entry point, 1 for the first entry
- point (the first `ENTRY' statement encountered), 2 for the second entry
- point, and so on.
- 
-    It also contains, for functions returning `CHARACTER' and (when
- `-ff2c' is in effect) `COMPLEX' functions, and for functions returning
- different types among the `ENTRY' statements (e.g. `REAL FUNCTION R()'
- containing `ENTRY I()'), an argument named `__g77_result' that is
- expected at run time to contain a pointer to where to store the result
- of the entry point.  For `CHARACTER' functions, this storage area is an
- array of the appropriate number of characters; for `COMPLEX' functions,
- it is the appropriate area for the return type; for
- multiple-return-type functions, it is a union of all the supported
- return types (which cannot include `CHARACTER', since combining
- `CHARACTER' and non-`CHARACTER' return types via `ENTRY' in a single
- function is not supported by `g77').
- 
-    For `CHARACTER' functions, the `__g77_result' argument is followed
- by yet another argument named `__g77_length' that, at run time,
- specifies the caller's expected length of the returned value.  Note
- that only `CHARACTER*(*)' functions and entry points actually make use
- of this argument, even though it is always passed by all callers of
- public `CHARACTER' functions (since the caller does not generally know
- whether such a function is `CHARACTER*(*)' or whether there are any
- other callers that don't have that information).
- 
-    The rest of the argument list is the union of all the arguments
- specified for all the entry points (in their usual forms, e.g.
- `CHARACTER' arguments have extra length arguments, all appended at the
- end of this list).  This is considered the "master list" of arguments.
- 
-    The code for this procedure has, before the code for the first
- executable statement, code much like that for the following Fortran
- statement:
- 
-             GOTO (100000,100001,100002), __g77_which_entrypoint
-      100000 ...code for primary entry point...
-      100001 ...code immediately following first ENTRY statement...
-      100002 ...code immediately following second ENTRY statement...
- 
- (Note that invalid Fortran statement labels and variable names are used
- in the above example to highlight the fact that it represents code
- generated by the `g77' internals, not code to be written by the user.)
- 
-    It is this code that, when the procedure is called, picks which
- entry point to start executing.
- 
-    Getting back to the public procedures (`x' and `Y' in the original
- example), those procedures are fairly simple.  Their interfaces are
- just like they would be if they were self-contained procedures (without
- `ENTRY'), of course, since that is what the callers expect.  Their code
- consists of simply calling the private procedure, described above, with
- the appropriate extra arguments (the entry point index, and perhaps a
- pointer to a multiple-type- return variable, local to the public
- procedure, that contains all the supported returnable non-character
- types).  For arguments that are not listed for a given entry point that
- are listed for other entry points, and therefore that are in the
- "master list" for the private procedure, null pointers (in C, the
- `NULL' macro) are passed.  Also, for entry points that are part of a
- multiple-type- returning function, code is compiled after the call of
- the private procedure to extract from the multi-type union the
- appropriate result, depending on the type of the entry point in
- question, returning that result to the original caller.
- 
-    When debugging a procedure containing alternate entry points, you
- can either set a break point on the public procedure itself (e.g.  a
- break point on `X' or `Y') or on the private procedure that contains
- most of the pertinent code (e.g. `__g77_masterfun_X').  If you do the
- former, you should use the debugger's command to "step into" the called
- procedure to get to the actual code; with the latter approach, the
- break point leaves you right at the actual code, skipping over the
- public entry point and its call to the private procedure (unless you
- have set a break point there as well, of course).
- 
-    Further, the list of dummy arguments that is visible when the
- private procedure is active is going to be the expanded version of the
- list for whichever particular entry point is active, as explained
- above, and the way in which return values are handled might well be
- different from how they would be handled for an equivalent single-entry
- function.
- 
- 
- File: g77.info,  Node: Alternate Returns,  Next: Assigned Statement Labels,  Prev: Alternate Entry Points,  Up: Debugging and Interfacing
- 
- Alternate Returns (SUBROUTINE and RETURN)
- =========================================
- 
-    Subroutines with alternate returns (e.g. `SUBROUTINE X(*)' and `CALL
- X(*50)') are implemented by `g77' as functions returning the C `int'
- type.  The actual alternate-return arguments are omitted from the
- calling sequence.  Instead, the caller uses the return value to do a
- rough equivalent of the Fortran computed-`GOTO' statement, as in `GOTO
- (50), X()' in the example above (where `X' is quietly declared as an
- `INTEGER(KIND=1)' function), and the callee just returns whatever
- integer is specified in the `RETURN' statement for the subroutine For
- example, `RETURN 1' is implemented as `X = 1' followed by `RETURN' in
- C, and `RETURN' by itself is `X = 0' and `RETURN').
- 
- 
- File: g77.info,  Node: Assigned Statement Labels,  Next: Run-time Library Errors,  Prev: Alternate Returns,  Up: Debugging and Interfacing
- 
- Assigned Statement Labels (ASSIGN and GOTO)
- ===========================================
- 
-    For portability to machines where a pointer (such as to a label,
- which is how `g77' implements `ASSIGN' and its relatives, the
- assigned-`GOTO' and assigned-`FORMAT'-I/O statements) is wider
- (bitwise) than an `INTEGER(KIND=1)', `g77' uses a different memory
- location to hold the `ASSIGN'ed value of a variable than it does the
- numerical value in that variable, unless the variable is wide enough
- (can hold enough bits).
- 
-    In particular, while `g77' implements
- 
-      I = 10
- 
- as, in C notation, `i = 10;', it implements
- 
-      ASSIGN 10 TO I
- 
- as, in GNU's extended C notation (for the label syntax),
- `__g77_ASSIGN_I = &&L10;' (where `L10' is just a massaging of the
- Fortran label `10' to make the syntax C-like; `g77' doesn't actually
- generate the name `L10' or any other name like that, since debuggers
- cannot access labels anyway).
- 
-    While this currently means that an `ASSIGN' statement does not
- overwrite the numeric contents of its target variable, _do not_ write
- any code depending on this feature.  `g77' has already changed this
- implementation across versions and might do so in the future.  This
- information is provided only to make debugging Fortran programs
- compiled with the current version of `g77' somewhat easier.  If there's
- no debugger-visible variable named `__g77_ASSIGN_I' in a program unit
- that does `ASSIGN 10 TO I', that probably means `g77' has decided it
- can store the pointer to the label directly into `I' itself.
- 
-    *Note Ugly Assigned Labels::, for information on a command-line
- option to force `g77' to use the same storage for both normal and
- assigned-label uses of a variable.
- 
- 
- File: g77.info,  Node: Run-time Library Errors,  Prev: Assigned Statement Labels,  Up: Debugging and Interfacing
- 
- Run-time Library Errors
- =======================
- 
-    The `libg2c' library currently has the following table to relate
- error code numbers, returned in `IOSTAT=' variables, to messages.  This
- information should, in future versions of this document, be expanded
- upon to include detailed descriptions of each message.
- 
-    In line with good coding practices, any of the numbers in the list
- below should _not_ be directly written into Fortran code you write.
- Instead, make a separate `INCLUDE' file that defines `PARAMETER' names
- for them, and use those in your code, so you can more easily change the
- actual numbers in the future.
- 
-    The information below is culled from the definition of `F_err' in
- `f/runtime/libI77/err.c' in the `g77' source tree.
- 
-      100: "error in format"
-      101: "illegal unit number"
-      102: "formatted io not allowed"
-      103: "unformatted io not allowed"
-      104: "direct io not allowed"
-      105: "sequential io not allowed"
-      106: "can't backspace file"
-      107: "null file name"
-      108: "can't stat file"
-      109: "unit not connected"
-      110: "off end of record"
-      111: "truncation failed in endfile"
-      112: "incomprehensible list input"
-      113: "out of free space"
-      114: "unit not connected"
-      115: "read unexpected character"
-      116: "bad logical input field"
-      117: "bad variable type"
-      118: "bad namelist name"
-      119: "variable not in namelist"
-      120: "no end record"
-      121: "variable count incorrect"
-      122: "subscript for scalar variable"
-      123: "invalid array section"
-      124: "substring out of bounds"
-      125: "subscript out of bounds"
-      126: "can't read file"
-      127: "can't write file"
-      128: "'new' file exists"
-      129: "can't append to file"
-      130: "non-positive record number"
-      131: "I/O started while already doing I/O"
- 
- 
- File: g77.info,  Node: Collected Fortran Wisdom,  Next: Trouble,  Prev: Debugging and Interfacing,  Up: Top
- 
- Collected Fortran Wisdom
- ************************
- 
-    Most users of `g77' can be divided into two camps:
- 
-    * Those writing new Fortran code to be compiled by `g77'.
- 
-    * Those using `g77' to compile existing, "legacy" code.
- 
-    Users writing new code generally understand most of the necessary
- aspects of Fortran to write "mainstream" code, but often need help
- deciding how to handle problems, such as the construction of libraries
- containing `BLOCK DATA'.
- 
-    Users dealing with "legacy" code sometimes don't have much
- experience with Fortran, but believe that the code they're compiling
- already works when compiled by other compilers (and might not
- understand why, as is sometimes the case, it doesn't work when compiled
- by `g77').
- 
-    The following information is designed to help users do a better job
- coping with existing, "legacy" Fortran code, and with writing new code
- as well.
- 
- * Menu:
- 
- * Advantages Over f2c::        If `f2c' is so great, why `g77'?
- * Block Data and Libraries::   How `g77' solves a common problem.
- * Loops::                      Fortran `DO' loops surprise many people.
- * Working Programs::           Getting programs to work should be done first.
- * Overly Convenient Options::  Temptations to avoid, habits to not form.
- * Faster Programs::            Everybody wants these, but at what cost?
- 
- 
- File: g77.info,  Node: Advantages Over f2c,  Next: Block Data and Libraries,  Up: Collected Fortran Wisdom
- 
- Advantages Over f2c
- ===================
- 
-    Without `f2c', `g77' would have taken much longer to do and probably
- not been as good for quite a while.  Sometimes people who notice how
- much `g77' depends on, and documents encouragement to use, `f2c' ask
- why `g77' was created if `f2c' already existed.
- 
-    This section gives some basic answers to these questions, though it
- is not intended to be comprehensive.
- 
- * Menu:
- 
- * Language Extensions::  Features used by Fortran code.
- * Diagnostic Abilities:: Abilities to spot problems early.
- * Compiler Options::     Features helpful to accommodate legacy code, etc.
- * Compiler Speed::       Speed of the compilation process.
- * Program Speed::        Speed of the generated, optimized code.
- * Ease of Debugging::    Debugging ease-of-use at the source level.
- * Character and Hollerith Constants::  A byte saved is a byte earned.
- 
- 
- File: g77.info,  Node: Language Extensions,  Next: Diagnostic Abilities,  Up: Advantages Over f2c
- 
- Language Extensions
- -------------------
- 
-    `g77' offers several extensions to FORTRAN 77 language that `f2c'
- doesn't:
- 
-    * Automatic arrays
- 
-    * `CYCLE' and `EXIT'
- 
-    * Construct names
- 
-    * `SELECT CASE'
- 
-    * `KIND=' and `LEN=' notation
- 
-    * Semicolon as statement separator
- 
-    * Constant expressions in `FORMAT' statements (such as
-      `FORMAT(I<J>)', where `J' is a `PARAMETER' named constant)
- 
-    * `MvBits' intrinsic
- 
-    * `libU77' (Unix-compatibility) library, with routines known to
-      compiler as intrinsics (so they work even when compiler options
-      are used to change the interfaces used by Fortran routines)
- 
-    `g77' also implements iterative `DO' loops so that they work even in
- the presence of certain "extreme" inputs, unlike `f2c'.  *Note Loops::.
- 
-    However, `f2c' offers a few that `g77' doesn't, such as:
- 
-    * Intrinsics in `PARAMETER' statements
- 
-    * Array bounds expressions (such as `REAL M(N(2))')
- 
-    * `AUTOMATIC' statement
- 
-    It is expected that `g77' will offer some or all of these missing
- features at some time in the future.
- 
- 
- File: g77.info,  Node: Diagnostic Abilities,  Next: Compiler Options,  Prev: Language Extensions,  Up: Advantages Over f2c
- 
- Diagnostic Abilities
- --------------------
- 
-    `g77' offers better diagnosis of problems in `FORMAT' statements.
- `f2c' doesn't, for example, emit any diagnostic for
- `FORMAT(XZFAJG10324)', leaving that to be diagnosed, at run time, by
- the `libf2c' run-time library.
- 
- 
- File: g77.info,  Node: Compiler Options,  Next: Compiler Speed,  Prev: Diagnostic Abilities,  Up: Advantages Over f2c
- 
- Compiler Options
- ----------------
- 
-    `g77' offers compiler options that `f2c' doesn't, most of which are
- designed to more easily accommodate legacy code:
- 
-    * Two that control the automatic appending of extra underscores to
-      external names
- 
-    * One that allows dollar signs (`$') in symbol names
- 
-    * A variety that control acceptance of various "ugly" constructs
- 
-    * Several that specify acceptable use of upper and lower case in the
-      source code
- 
-    * Many that enable, disable, delete, or hide groups of intrinsics
- 
-    * One to specify the length of fixed-form source lines (normally 72)
- 
-    * One to specify the the source code is written in Fortran-90-style
-      free-form
- 
-    However, `f2c' offers a few that `g77' doesn't, like an option to
- have `REAL' default to `REAL*8'.  It is expected that `g77' will offer
- all of the missing options pertinent to being a Fortran compiler at
- some time in the future.
- 
- 
- File: g77.info,  Node: Compiler Speed,  Next: Program Speed,  Prev: Compiler Options,  Up: Advantages Over f2c
- 
- Compiler Speed
- --------------
- 
-    Saving the steps of writing and then rereading C code is a big reason
- why `g77' should be able to compile code much faster than using `f2c'
- in conjunction with the equivalent invocation of `gcc'.
- 
-    However, due to `g77''s youth, lots of self-checking is still being
- performed.  As a result, this improvement is as yet unrealized (though
- the potential seems to be there for quite a big speedup in the future).
- It is possible that, as of version 0.5.18, `g77' is noticeably faster
- compiling many Fortran source files than using `f2c' in conjunction
- with `gcc'.
- 
- 
- File: g77.info,  Node: Program Speed,  Next: Ease of Debugging,  Prev: Compiler Speed,  Up: Advantages Over f2c
- 
- Program Speed
- -------------
- 
-    `g77' has the potential to better optimize code than `f2c', even
- when `gcc' is used to compile the output of `f2c', because `f2c' must
- necessarily translate Fortran into a somewhat lower-level language (C)
- that cannot preserve all the information that is potentially useful for
- optimization, while `g77' can gather, preserve, and transmit that
- information directly to the GBE.
- 
-    For example, `g77' implements `ASSIGN' and assigned `GOTO' using
- direct assignment of pointers to labels and direct jumps to labels,
- whereas `f2c' maps the assigned labels to integer values and then uses
- a C `switch' statement to encode the assigned `GOTO' statements.
- 
-    However, as is typical, theory and reality don't quite match, at
- least not in all cases, so it is still the case that `f2c' plus `gcc'
- can generate code that is faster than `g77'.
- 
-    Version 0.5.18 of `g77' offered default settings and options, via
- patches to the `gcc' back end, that allow for better program speed,
- though some of these improvements also affected the performance of
- programs translated by `f2c' and then compiled by `g77''s version of
- `gcc'.
- 
-    Version 0.5.20 of `g77' offers further performance improvements, at
- least one of which (alias analysis) is not generally applicable to
- `f2c' (though `f2c' could presumably be changed to also take advantage
- of this new capability of the `gcc' back end, assuming this is made
- available in an upcoming release of `gcc').
- 
- 
- File: g77.info,  Node: Ease of Debugging,  Next: Character and Hollerith Constants,  Prev: Program Speed,  Up: Advantages Over f2c
- 
- Ease of Debugging
- -----------------
- 
-    Because `g77' compiles directly to assembler code like `gcc',
- instead of translating to an intermediate language (C) as does `f2c',
- support for debugging can be better for `g77' than `f2c'.
- 
-    However, although `g77' might be somewhat more "native" in terms of
- debugging support than `f2c' plus `gcc', there still are a lot of
- things "not quite right".  Many of the important ones should be
- resolved in the near future.
- 
-    For example, `g77' doesn't have to worry about reserved names like
- `f2c' does.  Given `FOR = WHILE', `f2c' must necessarily translate this
- to something _other_ than `for = while;', because C reserves those
- words.
- 
-    However, `g77' does still uses things like an extra level of
- indirection for `ENTRY'-laden procedures--in this case, because the
- back end doesn't yet support multiple entry points.
- 
-    Another example is that, given
- 
-      COMMON A, B
-      EQUIVALENCE (B, C)
- 
- the `g77' user should be able to access the variables directly, by name,
- without having to traverse C-like structures and unions, while `f2c' is
- unlikely to ever offer this ability (due to limitations in the C
- language).
- 
-    However, due to apparent bugs in the back end, `g77' currently
- doesn't take advantage of this facility at all--it doesn't emit any
- debugging information for `COMMON' and `EQUIVALENCE' areas, other than
- information on the array of `char' it creates (and, in the case of
- local `EQUIVALENCE', names) for each such area.
- 
-    Yet another example is arrays.  `g77' represents them to the debugger
- using the same "dimensionality" as in the source code, while `f2c' must
- necessarily convert them all to one-dimensional arrays to fit into the
- confines of the C language.  However, the level of support offered by
- debuggers for interactive Fortran-style access to arrays as compiled by
- `g77' can vary widely.  In some cases, it can actually be an advantage
- that `f2c' converts everything to widely supported C semantics.
- 
-    In fairness, `g77' could do many of the things `f2c' does to get
- things working at least as well as `f2c'--for now, the developers
- prefer making `g77' work the way they think it is supposed to, and
- finding help improving the other products (the back end of `gcc';
- `gdb'; and so on) to get things working properly.
- 
- 
- File: g77.info,  Node: Character and Hollerith Constants,  Prev: Ease of Debugging,  Up: Advantages Over f2c
- 
- Character and Hollerith Constants
- ---------------------------------
- 
-    To avoid the extensive hassle that would be needed to avoid this,
- `f2c' uses C character constants to encode character and Hollerith
- constants.  That means a constant like `'HELLO'' is translated to
- `"hello"' in C, which further means that an extra null byte is present
- at the end of the constant.  This null byte is superfluous.
- 
-    `g77' does not generate such null bytes.  This represents significant
- savings of resources, such as on systems where `/dev/null' or
- `/dev/zero' represent bottlenecks in the systems' performance, because
- `g77' simply asks for fewer zeros from the operating system than `f2c'.
- (Avoiding spurious use of zero bytes, each byte typically have eight
- zero bits, also reduces the liabilities in case Microsoft's rumored
- patent on the digits 0 and 1 is upheld.)
- 
- 
- File: g77.info,  Node: Block Data and Libraries,  Next: Loops,  Prev: Advantages Over f2c,  Up: Collected Fortran Wisdom
- 
- Block Data and Libraries
- ========================
- 
-    To ensure that block data program units are linked, especially a
- concern when they are put into libraries, give each one a name (as in
- `BLOCK DATA FOO') and make sure there is an `EXTERNAL FOO' statement in
- every program unit that uses any common block initialized by the
- corresponding `BLOCK DATA'.  `g77' currently compiles a `BLOCK DATA' as
- if it were a `SUBROUTINE', that is, it generates an actual procedure
- having the appropriate name.  The procedure does nothing but return
- immediately if it happens to be called.  For `EXTERNAL FOO', where
- `FOO' is not otherwise referenced in the same program unit, `g77'
- assumes there exists a `BLOCK DATA FOO' in the program and ensures that
- by generating a reference to it so the linker will make sure it is
- present.  (Specifically, `g77' outputs in the data section a static
- pointer to the external name `FOO'.)
- 
-    The implementation `g77' currently uses to make this work is one of
- the few things not compatible with `f2c' as currently shipped.  `f2c'
- currently does nothing with `EXTERNAL FOO' except issue a warning that
- `FOO' is not otherwise referenced, and, for `BLOCK DATA FOO', `f2c'
- doesn't generate a dummy procedure with the name `FOO'.  The upshot is
- that you shouldn't mix `f2c' and `g77' in this particular case.  If you
- use `f2c' to compile `BLOCK DATA FOO', then any `g77'-compiled program
- unit that says `EXTERNAL FOO' will result in an unresolved reference
- when linked.  If you do the opposite, then `FOO' might not be linked in
- under various circumstances (such as when `FOO' is in a library, or
- you're using a "clever" linker--so clever, it produces a broken program
- with little or no warning by omitting initializations of global data
- because they are contained in unreferenced procedures).
- 
-    The changes you make to your code to make `g77' handle this
- situation, however, appear to be a widely portable way to handle it.
- That is, many systems permit it (as they should, since the FORTRAN 77
- standard permits `EXTERNAL FOO' when `FOO' is a block data program
- unit), and of the ones that might not link `BLOCK DATA FOO' under some
- circumstances, most of them appear to do so once `EXTERNAL FOO' is
- present in the appropriate program units.
- 
-    Here is the recommended approach to modifying a program containing a
- program unit such as the following:
- 
-      BLOCK DATA FOO
-      COMMON /VARS/ X, Y, Z
-      DATA X, Y, Z / 3., 4., 5. /
-      END
- 
- If the above program unit might be placed in a library module, then
- ensure that every program unit in every program that references that
- particular `COMMON' area uses the `EXTERNAL' statement to force the
- area to be initialized.
- 
-    For example, change a program unit that starts with
- 
-      INTEGER FUNCTION CURX()
-      COMMON /VARS/ X, Y, Z
-      CURX = X
-      END
- 
- so that it uses the `EXTERNAL' statement, as in:
- 
-      INTEGER FUNCTION CURX()
-      COMMON /VARS/ X, Y, Z
-      EXTERNAL FOO
-      CURX = X
-      END
- 
- That way, `CURX' is compiled by `g77' (and many other compilers) so
- that the linker knows it must include `FOO', the `BLOCK DATA' program
- unit that sets the initial values for the variables in `VAR', in the
- executable program.
- 
- 
- File: g77.info,  Node: Loops,  Next: Working Programs,  Prev: Block Data and Libraries,  Up: Collected Fortran Wisdom
- 
- Loops
- =====
- 
-    The meaning of a `DO' loop in Fortran is precisely specified in the
- Fortran standard...and is quite different from what many programmers
- might expect.
- 
-    In particular, Fortran iterative `DO' loops are implemented as if
- the number of trips through the loop is calculated _before_ the loop is
- entered.
- 
-    The number of trips for a loop is calculated from the START, END,
- and INCREMENT values specified in a statement such as:
- 
-      DO ITER = START, END, INCREMENT
- 
- The trip count is evaluated using a fairly simple formula based on the
- three values following the `=' in the statement, and it is that trip
- count that is effectively decremented during each iteration of the loop.
- If, at the beginning of an iteration of the loop, the trip count is
- zero or negative, the loop terminates.  The per-loop-iteration
- modifications to ITER are not related to determining whether to
- terminate the loop.
- 
-    There are two important things to remember about the trip count:
- 
-    * It can be _negative_, in which case it is treated as if it was
-      zero--meaning the loop is not executed at all.
- 
-    * The type used to _calculate_ the trip count is the same type as
-      ITER, but the final calculation, and thus the type of the trip
-      count itself, always is `INTEGER(KIND=1)'.
- 
-    These two items mean that there are loops that cannot be written in
- straightforward fashion using the Fortran `DO'.
- 
-    For example, on a system with the canonical 32-bit two's-complement
- implementation of `INTEGER(KIND=1)', the following loop will not work:
- 
-      DO I = -2000000000, 2000000000
- 
- Although the START and END values are well within the range of
- `INTEGER(KIND=1)', the _trip count_ is not.  The expected trip count is
- 40000000001, which is outside the range of `INTEGER(KIND=1)' on many
- systems.
- 
-    Instead, the above loop should be constructed this way:
- 
-      I = -2000000000
-      DO
-        IF (I .GT. 2000000000) EXIT
-        ...
-        I = I + 1
-      END DO
- 
- The simple `DO' construct and the `EXIT' statement (used to leave the
- innermost loop) are F90 features that `g77' supports.
- 
-    Some Fortran compilers have buggy implementations of `DO', in that
- they don't follow the standard.  They implement `DO' as a
- straightforward translation to what, in C, would be a `for' statement.
- Instead of creating a temporary variable to hold the trip count as
- calculated at run time, these compilers use the iteration variable ITER
- to control whether the loop continues at each iteration.
- 
-    The bug in such an implementation shows up when the trip count is
- within the range of the type of ITER, but the magnitude of `ABS(END) +
- ABS(INCR)' exceeds that range.  For example:
- 
-      DO I = 2147483600, 2147483647
- 
- A loop started by the above statement will work as implemented by
- `g77', but the use, by some compilers, of a more C-like implementation
- akin to
- 
-      for (i = 2147483600; i <= 2147483647; ++i)
- 
- produces a loop that does not terminate, because `i' can never be
- greater than 2147483647, since incrementing it beyond that value
- overflows `i', setting it to -2147483648.  This is a large, negative
- number that still is less than 2147483647.
- 
-    Another example of unexpected behavior of `DO' involves using a
- nonintegral iteration variable ITER, that is, a `REAL' variable.
- Consider the following program:
- 
-            DATA BEGIN, END, STEP /.1, .31, .007/
-            DO 10 R = BEGIN, END, STEP
-               IF (R .GT. END) PRINT *, R, ' .GT. ', END, '!!'
-               PRINT *,R
-      10    CONTINUE
-            PRINT *,'LAST = ',R
-            IF (R .LE. END) PRINT *, R, ' .LE. ', END, '!!'
-            END
- 
- A C-like view of `DO' would hold that the two "exclamatory" `PRINT'
- statements are never executed.  However, this is the output of running
- the above program as compiled by `g77' on a GNU/Linux ix86 system:
- 
-       .100000001
-       .107000001
-       .114
-       .120999999
-       ...
-       .289000005
-       .296000004
-       .303000003
-      LAST =   .310000002
-       .310000002 .LE.   .310000002!!
- 
-    Note that one of the two checks in the program turned up an apparent
- violation of the programmer's expectation--yet, the loop is correctly
- implemented by `g77', in that it has 30 iterations.  This trip count of
- 30 is correct when evaluated using the floating-point representations
- for the BEGIN, END, and INCR values (.1, .31, .007) on GNU/Linux ix86
- are used.  On other systems, an apparently more accurate trip count of
- 31 might result, but, nevertheless, `g77' is faithfully following the
- Fortran standard, and the result is not what the author of the sample
- program above apparently expected.  (Such other systems might, for
- different values in the `DATA' statement, violate the other
- programmer's expectation, for example.)
- 
-    Due to this combination of imprecise representation of
- floating-point values and the often-misunderstood interpretation of
- `DO' by standard-conforming compilers such as `g77', use of `DO' loops
- with `REAL' iteration variables is not recommended.  Such use can be
- caught by specifying `-Wsurprising'.  *Note Warning Options::, for more
- information on this option.
- 
- 
- File: g77.info,  Node: Working Programs,  Next: Overly Convenient Options,  Prev: Loops,  Up: Collected Fortran Wisdom
- 
- Working Programs
- ================
- 
-    Getting Fortran programs to work in the first place can be quite a
- challenge--even when the programs already work on other systems, or
- when using other compilers.
- 
-    `g77' offers some facilities that might be useful for tracking down
- bugs in such programs.
- 
- * Menu:
- 
- * Not My Type::
- * Variables Assumed To Be Zero::
- * Variables Assumed To Be Saved::
- * Unwanted Variables::
- * Unused Arguments::
- * Surprising Interpretations of Code::
- * Aliasing Assumed To Work::
- * Output Assumed To Flush::
- * Large File Unit Numbers::
- * Floating-point precision::
- * Inconsistent Calling Sequences::
- 
- 
- File: g77.info,  Node: Not My Type,  Next: Variables Assumed To Be Zero,  Up: Working Programs
- 
- Not My Type
- -----------
- 
-    A fruitful source of bugs in Fortran source code is use, or mis-use,
- of Fortran's implicit-typing feature, whereby the type of a variable,
- array, or function is determined by the first character of its name.
- 
-    Simple cases of this include statements like `LOGX=9.227', without a
- statement such as `REAL LOGX'.  In this case, `LOGX' is implicitly
- given `INTEGER(KIND=1)' type, with the result of the assignment being
- that it is given the value `9'.
- 
-    More involved cases include a function that is defined starting with
- a statement like `DOUBLE PRECISION FUNCTION IPS(...)'.  Any caller of
- this function that does not also declare `IPS' as type `DOUBLE
- PRECISION' (or, in GNU Fortran, `REAL(KIND=2)') is likely to assume it
- returns `INTEGER', or some other type, leading to invalid results or
- even program crashes.
- 
-    The `-Wimplicit' option might catch failures to properly specify the
- types of variables, arrays, and functions in the code.
- 
-    However, in code that makes heavy use of Fortran's implicit-typing
- facility, this option might produce so many warnings about cases that
- are working, it would be hard to find the one or two that represent
- bugs.  This is why so many experienced Fortran programmers strongly
- recommend widespread use of the `IMPLICIT NONE' statement, despite it
- not being standard FORTRAN 77, to completely turn off implicit typing.
- (`g77' supports `IMPLICIT NONE', as do almost all FORTRAN 77 compilers.)
- 
-    Note that `-Wimplicit' catches only implicit typing of _names_.  It
- does not catch implicit typing of expressions such as `X**(2/3)'.  Such
- expressions can be buggy as well--in fact, `X**(2/3)' is equivalent to
- `X**0', due to the way Fortran expressions are given types and then
- evaluated.  (In this particular case, the programmer probably wanted
- `X**(2./3.)'.)
- 
- 
- File: g77.info,  Node: Variables Assumed To Be Zero,  Next: Variables Assumed To Be Saved,  Prev: Not My Type,  Up: Working Programs
- 
- Variables Assumed To Be Zero
- ----------------------------
- 
-    Many Fortran programs were developed on systems that provided
- automatic initialization of all, or some, variables and arrays to zero.
- As a result, many of these programs depend, sometimes inadvertently, on
- this behavior, though to do so violates the Fortran standards.
- 
-    You can ask `g77' for this behavior by specifying the
- `-finit-local-zero' option when compiling Fortran code.  (You might
- want to specify `-fno-automatic' as well, to avoid code-size inflation
- for non-optimized compilations.)
- 
-    Note that a program that works better when compiled with the
- `-finit-local-zero' option is almost certainly depending on a
- particular system's, or compiler's, tendency to initialize some
- variables to zero.  It might be worthwhile finding such cases and
- fixing them, using techniques such as compiling with the `-O
- -Wuninitialized' options using `g77'.
- 
- 
- File: g77.info,  Node: Variables Assumed To Be Saved,  Next: Unwanted Variables,  Prev: Variables Assumed To Be Zero,  Up: Working Programs
- 
- Variables Assumed To Be Saved
- -----------------------------
- 
-    Many Fortran programs were developed on systems that saved the
- values of all, or some, variables and arrays across procedure calls.
- As a result, many of these programs depend, sometimes inadvertently, on
- being able to assign a value to a variable, perform a `RETURN' to a
- calling procedure, and, upon subsequent invocation, reference the
- previously assigned variable to obtain the value.
- 
-    They expect this despite not using the `SAVE' statement to specify
- that the value in a variable is expected to survive procedure returns
- and calls.  Depending on variables and arrays to retain values across
- procedure calls without using `SAVE' to require it violates the Fortran
- standards.
- 
-    You can ask `g77' to assume `SAVE' is specified for all relevant
- (local) variables and arrays by using the `-fno-automatic' option.
- 
-    Note that a program that works better when compiled with the
- `-fno-automatic' option is almost certainly depending on not having to
- use the `SAVE' statement as required by the Fortran standard.  It might
- be worthwhile finding such cases and fixing them, using techniques such
- as compiling with the `-O -Wuninitialized' options using `g77'.
- 
- 
- File: g77.info,  Node: Unwanted Variables,  Next: Unused Arguments,  Prev: Variables Assumed To Be Saved,  Up: Working Programs
- 
- Unwanted Variables
- ------------------
- 
-    The `-Wunused' option can find bugs involving implicit typing,
- sometimes more easily than using `-Wimplicit' in code that makes heavy
- use of implicit typing.  An unused variable or array might indicate
- that the spelling for its declaration is different from that of its
- intended uses.
- 
-    Other than cases involving typos, unused variables rarely indicate
- actual bugs in a program.  However, investigating such cases thoroughly
- has, on occasion, led to the discovery of code that had not been
- completely written--where the programmer wrote declarations as needed
- for the whole algorithm, wrote some or even most of the code for that
- algorithm, then got distracted and forgot that the job was not complete.
- 
- 
- File: g77.info,  Node: Unused Arguments,  Next: Surprising Interpretations of Code,  Prev: Unwanted Variables,  Up: Working Programs
- 
- Unused Arguments
- ----------------
- 
-    As with unused variables, It is possible that unused arguments to a
- procedure might indicate a bug.  Compile with `-W -Wunused' option to
- catch cases of unused arguments.
- 
-    Note that `-W' also enables warnings regarding overflow of
- floating-point constants under certain circumstances.
- 
- 
- File: g77.info,  Node: Surprising Interpretations of Code,  Next: Aliasing Assumed To Work,  Prev: Unused Arguments,  Up: Working Programs
- 
- Surprising Interpretations of Code
- ----------------------------------
- 
-    The `-Wsurprising' option can help find bugs involving expression
- evaluation or in the way `DO' loops with non-integral iteration
- variables are handled.  Cases found by this option might indicate a
- difference of interpretation between the author of the code involved,
- and a standard-conforming compiler such as `g77'.  Such a difference
- might produce actual bugs.
- 
-    In any case, changing the code to explicitly do what the programmer
- might have expected it to do, so `g77' and other compilers are more
- likely to follow the programmer's expectations, might be worthwhile,
- especially if such changes make the program work better.
- 
--- 0 ----
diff -Nrc3pad gcc-3.2.3/gcc/f/g77.info-15 gcc-3.3/gcc/f/g77.info-15
*** gcc-3.2.3/gcc/f/g77.info-15	2003-04-22 07:07:24.000000000 +0000
--- gcc-3.3/gcc/f/g77.info-15	1970-01-01 00:00:00.000000000 +0000
***************
*** 1,1087 ****
- This is g77.info, produced by makeinfo version 4.5 from g77.texi.
- 
- INFO-DIR-SECTION Programming
- START-INFO-DIR-ENTRY
- * g77: (g77).                  The GNU Fortran compiler.
- END-INFO-DIR-ENTRY
-    This file documents the use and the internals of the GNU Fortran
- (`g77') compiler.  It corresponds to the GCC-3.2.3 version of `g77'.
- 
-    Published by the Free Software Foundation 59 Temple Place - Suite 330
- Boston, MA 02111-1307 USA
- 
-    Copyright (C) 1995,1996,1997,1998,1999,2000,2001,2002 Free Software
- Foundation, Inc.
- 
-    Permission is granted to copy, distribute and/or modify this document
- under the terms of the GNU Free Documentation License, Version 1.1 or
- any later version published by the Free Software Foundation; with the
- Invariant Sections being "GNU General Public License" and "Funding Free
- Software", the Front-Cover texts being (a) (see below), and with the
- Back-Cover Texts being (b) (see below).  A copy of the license is
- included in the section entitled "GNU Free Documentation License".
- 
-    (a) The FSF's Front-Cover Text is:
- 
-    A GNU Manual
- 
-    (b) The FSF's Back-Cover Text is:
- 
-    You have freedom to copy and modify this GNU Manual, like GNU
- software.  Copies published by the Free Software Foundation raise
- funds for GNU development.
- 
-    Contributed by James Craig Burley (<craig@jcb-sc.com>).  Inspired by
- a first pass at translating `g77-0.5.16/f/DOC' that was contributed to
- Craig by David Ronis (<ronis@onsager.chem.mcgill.ca>).
- 
- 
- File: g77.info,  Node: Aliasing Assumed To Work,  Next: Output Assumed To Flush,  Prev: Surprising Interpretations of Code,  Up: Working Programs
- 
- Aliasing Assumed To Work
- ------------------------
- 
-    The `-falias-check', `-fargument-alias', `-fargument-noalias', and
- `-fno-argument-noalias-global' options, introduced in version 0.5.20 and
- `g77''s version 2.7.2.2.f.2 of `gcc', were withdrawn as of `g77'
- version 0.5.23 due to their not being supported by `gcc' version 2.8.
- 
-    These options control the assumptions regarding aliasing
- (overlapping) of writes and reads to main memory (core) made by the
- `gcc' back end.
- 
-    The information below still is useful, but applies to only those
- versions of `g77' that support the alias analysis implied by support
- for these options.
- 
-    These options are effective only when compiling with `-O'
- (specifying any level other than `-O0') or with `-falias-check'.
- 
-    The default for Fortran code is `-fargument-noalias-global'.  (The
- default for C code and code written in other C-based languages is
- `-fargument-alias'.  These defaults apply regardless of whether you use
- `g77' or `gcc' to compile your code.)
- 
-    Note that, on some systems, compiling with `-fforce-addr' in effect
- can produce more optimal code when the default aliasing options are in
- effect (and when optimization is enabled).
- 
-    If your program is not working when compiled with optimization, it
- is possible it is violating the Fortran standards (77 and 90) by
- relying on the ability to "safely" modify variables and arrays that are
- aliased, via procedure calls, to other variables and arrays, without
- using `EQUIVALENCE' to explicitly set up this kind of aliasing.
- 
-    (The FORTRAN 77 standard's prohibition of this sort of overlap,
- generally referred to therein as "storage assocation", appears in
- Sections 15.9.3.6.  This prohibition allows implementations, such as
- `g77', to, for example, implement the passing of procedures and even
- values in `COMMON' via copy operations into local, perhaps more
- efficiently accessed temporaries at entry to a procedure, and, where
- appropriate, via copy operations back out to their original locations
- in memory at exit from that procedure, without having to take into
- consideration the order in which the local copies are updated by the
- code, among other things.)
- 
-    To test this hypothesis, try compiling your program with the
- `-fargument-alias' option, which causes the compiler to revert to
- assumptions essentially the same as made by versions of `g77' prior to
- 0.5.20.
- 
-    If the program works using this option, that strongly suggests that
- the bug is in your program.  Finding and fixing the bug(s) should
- result in a program that is more standard-conforming and that can be
- compiled by `g77' in a way that results in a faster executable.
- 
-    (You might want to try compiling with `-fargument-noalias', a kind
- of half-way point, to see if the problem is limited to aliasing between
- dummy arguments and `COMMON' variables--this option assumes that such
- aliasing is not done, while still allowing aliasing among dummy
- arguments.)
- 
-    An example of aliasing that is invalid according to the standards is
- shown in the following program, which might _not_ produce the expected
- results when executed:
- 
-      I = 1
-      CALL FOO(I, I)
-      PRINT *, I
-      END
-      
-      SUBROUTINE FOO(J, K)
-      J = J + K
-      K = J * K
-      PRINT *, J, K
-      END
- 
-    The above program attempts to use the temporary aliasing of the `J'
- and `K' arguments in `FOO' to effect a pathological behavior--the
- simultaneous changing of the values of _both_ `J' and `K' when either
- one of them is written.
- 
-    The programmer likely expects the program to print these values:
- 
-      2  4
-      4
- 
-    However, since the program is not standard-conforming, an
- implementation's behavior when running it is undefined, because
- subroutine `FOO' modifies at least one of the arguments, and they are
- aliased with each other.  (Even if one of the assignment statements was
- deleted, the program would still violate these rules.  This kind of
- on-the-fly aliasing is permitted by the standard only when none of the
- aliased items are defined, or written, while the aliasing is in effect.)
- 
-    As a practical example, an optimizing compiler might schedule the `J
- =' part of the second line of `FOO' _after_ the reading of `J' and `K'
- for the `J * K' expression, resulting in the following output:
- 
-      2  2
-      2
- 
-    Essentially, compilers are promised (by the standard and, therefore,
- by programmers who write code they claim to be standard-conforming)
- that if they cannot detect aliasing via static analysis of a single
- program unit's `EQUIVALENCE' and `COMMON' statements, no such aliasing
- exists.  In such cases, compilers are free to assume that an assignment
- to one variable will not change the value of another variable, allowing
- it to avoid generating code to re-read the value of the other variable,
- to re-schedule reads and writes, and so on, to produce a faster
- executable.
- 
-    The same promise holds true for arrays (as seen by the called
- procedure)--an element of one dummy array cannot be aliased with, or
- overlap, any element of another dummy array or be in a `COMMON' area
- known to the procedure.
- 
-    (These restrictions apply only when the procedure defines, or writes
- to, one of the aliased variables or arrays.)
- 
-    Unfortunately, there is no way to find _all_ possible cases of
- violations of the prohibitions against aliasing in Fortran code.
- Static analysis is certainly imperfect, as is run-time analysis, since
- neither can catch all violations.  (Static analysis can catch all
- likely violations, and some that might never actually happen, while
- run-time analysis can catch only those violations that actually happen
- during a particular run.  Neither approach can cope with programs
- mixing Fortran code with routines written in other languages, however.)
- 
-    Currently, `g77' provides neither static nor run-time facilities to
- detect any cases of this problem, although other products might.
- Run-time facilities are more likely to be offered by future versions of
- `g77', though patches improving `g77' so that it provides either form
- of detection are welcome.
- 
- 
- File: g77.info,  Node: Output Assumed To Flush,  Next: Large File Unit Numbers,  Prev: Aliasing Assumed To Work,  Up: Working Programs
- 
- Output Assumed To Flush
- -----------------------
- 
-    For several versions prior to 0.5.20, `g77' configured its version
- of the `libf2c' run-time library so that one of its configuration
- macros, `ALWAYS_FLUSH', was defined.
- 
-    This was done as a result of a belief that many programs expected
- output to be flushed to the operating system (under UNIX, via the
- `fflush()' library call) with the result that errors, such as disk
- full, would be immediately flagged via the relevant `ERR=' and
- `IOSTAT=' mechanism.
- 
-    Because of the adverse effects this approach had on the performance
- of many programs, `g77' no longer configures `libf2c' (now named
- `libg2c' in its `g77' incarnation) to always flush output.
- 
-    If your program depends on this behavior, either insert the
- appropriate `CALL FLUSH' statements, or modify the sources to the
- `libg2c', rebuild and reinstall `g77', and relink your programs with
- the modified library.
- 
-    (Ideally, `libg2c' would offer the choice at run-time, so that a
- compile-time option to `g77' or `f2c' could result in generating the
- appropriate calls to flushing or non-flushing library routines.)
- 
-    Some Fortran programs require output (writes) to be flushed to the
- operating system (under UNIX, via the `fflush()' library call) so that
- errors, such as disk full, are immediately flagged via the relevant
- `ERR=' and `IOSTAT=' mechanism, instead of such errors being flagged
- later as subsequent writes occur, forcing the previously written data
- to disk, or when the file is closed.
- 
-    Essentially, the difference can be viewed as synchronous error
- reporting (immediate flagging of errors during writes) versus
- asynchronous, or, more precisely, buffered error reporting (detection
- of errors might be delayed).
- 
-    `libg2c' supports flagging write errors immediately when it is built
- with the `ALWAYS_FLUSH' macro defined.  This results in a `libg2c' that
- runs slower, sometimes quite a bit slower, under certain
- circumstances--for example, accessing files via the networked file
- system NFS--but the effect can be more reliable, robust file I/O.
- 
-    If you know that Fortran programs requiring this level of precision
- of error reporting are to be compiled using the version of `g77' you
- are building, you might wish to modify the `g77' source tree so that
- the version of `libg2c' is built with the `ALWAYS_FLUSH' macro defined,
- enabling this behavior.
- 
-    To do this, find this line in `gcc/libf2c/f2c.h' in your `g77'
- source tree:
- 
-      /* #define ALWAYS_FLUSH */
- 
-    Remove the leading `/* ', so the line begins with `#define', and the
- trailing ` */'.
- 
-    Then build or rebuild `g77' as appropriate.
- 
- 
- File: g77.info,  Node: Large File Unit Numbers,  Next: Floating-point precision,  Prev: Output Assumed To Flush,  Up: Working Programs
- 
- Large File Unit Numbers
- -----------------------
- 
-    If your program crashes at run time with a message including the
- text `illegal unit number', that probably is a message from the
- run-time library, `libg2c'.
- 
-    The message means that your program has attempted to use a file unit
- number that is out of the range accepted by `libg2c'.  Normally, this
- range is 0 through 99, and the high end of the range is controlled by a
- `libg2c' source-file macro named `MXUNIT'.
- 
-    If you can easily change your program to use unit numbers in the
- range 0 through 99, you should do so.
- 
-    As distributed, whether as part of `f2c' or `g77', `libf2c' accepts
- file unit numbers only in the range 0 through 99.  For example, a
- statement such as `WRITE (UNIT=100)' causes a run-time crash in
- `libf2c', because the unit number, 100, is out of range.
- 
-    If you know that Fortran programs at your installation require the
- use of unit numbers higher than 99, you can change the value of the
- `MXUNIT' macro, which represents the maximum unit number, to an
- appropriately higher value.
- 
-    To do this, edit the file `gcc/libf2c/libI77/fio.h' in your `g77'
- source tree, changing the following line:
- 
-      #define MXUNIT 100
- 
-    Change the line so that the value of `MXUNIT' is defined to be at
- least one _greater_ than the maximum unit number used by the Fortran
- programs on your system.
- 
-    (For example, a program that does `WRITE (UNIT=255)' would require
- `MXUNIT' set to at least 256 to avoid crashing.)
- 
-    Then build or rebuild `g77' as appropriate.
- 
-    _Note:_ Changing this macro has _no_ effect on other limits your
- system might place on the number of files open at the same time.  That
- is, the macro might allow a program to do `WRITE (UNIT=100)', but the
- library and operating system underlying `libf2c' might disallow it if
- many other files have already been opened (via `OPEN' or implicitly via
- `READ', `WRITE', and so on).  Information on how to increase these
- other limits should be found in your system's documentation.
- 
- 
- File: g77.info,  Node: Floating-point precision,  Next: Inconsistent Calling Sequences,  Prev: Large File Unit Numbers,  Up: Working Programs
- 
- Floating-point precision
- ------------------------
- 
-    If your program depends on exact IEEE 754 floating-point handling it
- may help on some systems--specifically x86 or m68k hardware--to use the
- `-ffloat-store' option or to reset the precision flag on the
- floating-point unit.  *Note Optimize Options::.
- 
-    However, it might be better simply to put the FPU into double
- precision mode and not take the performance hit of `-ffloat-store'.  On
- x86 and m68k GNU systems you can do this with a technique similar to
- that for turning on floating-point exceptions (*note Floating-point
- Exception Handling::).  The control word could be set to double
- precision by some code like this one:
-      #include <fpu_control.h>
-      {
-        fpu_control_t cw = (_FPU_DEFAULT & ~_FPU_EXTENDED) | _FPU_DOUBLE;
-        _FPU_SETCW(cw);
-      }
-    (It is not clear whether this has any effect on the operation of the
- GNU maths library, but we have no evidence of it causing trouble.)
- 
-    Some targets (such as the Alpha) may need special options for full
- IEEE conformance.  *Note Hardware Models and Configurations:
- (gcc)Submodel Options.
- 
- 
- File: g77.info,  Node: Inconsistent Calling Sequences,  Prev: Floating-point precision,  Up: Working Programs
- 
- Inconsistent Calling Sequences
- ------------------------------
- 
-    Code containing inconsistent calling sequences in the same file is
- normally rejected--see *Note GLOBALS::.  (Use, say, `ftnchek' to ensure
- consistency across source files.  *Note Generating Skeletons and
- Prototypes with `f2c': f2c Skeletons and Prototypes.)
- 
-    Mysterious errors, which may appear to be code generation problems,
- can appear specifically on the x86 architecture with some such
- inconsistencies.  On x86 hardware, floating-point return values of
- functions are placed on the floating-point unit's register stack, not
- the normal stack.  Thus calling a `REAL' or `DOUBLE PRECISION'
- `FUNCTION' as some other sort of procedure, or vice versa, scrambles
- the floating-point stack.  This may break unrelated code executed
- later.  Similarly if, say, external C routines are written incorrectly.
- 
- 
- File: g77.info,  Node: Overly Convenient Options,  Next: Faster Programs,  Prev: Working Programs,  Up: Collected Fortran Wisdom
- 
- Overly Convenient Command-line Options
- ======================================
- 
-    These options should be used only as a quick-and-dirty way to
- determine how well your program will run under different compilation
- models without having to change the source.  Some are more problematic
- than others, depending on how portable and maintainable you want the
- program to be (and, of course, whether you are allowed to change it at
- all is crucial).
- 
-    You should not continue to use these command-line options to compile
- a given program, but rather should make changes to the source code:
- 
- `-finit-local-zero'
-      (This option specifies that any uninitialized local variables and
-      arrays have default initialization to binary zeros.)
- 
-      Many other compilers do this automatically, which means lots of
-      Fortran code developed with those compilers depends on it.
- 
-      It is safer (and probably would produce a faster program) to find
-      the variables and arrays that need such initialization and provide
-      it explicitly via `DATA', so that `-finit-local-zero' is not
-      needed.
- 
-      Consider using `-Wuninitialized' (which requires `-O') to find
-      likely candidates, but do not specify `-finit-local-zero' or
-      `-fno-automatic', or this technique won't work.
- 
- `-fno-automatic'
-      (This option specifies that all local variables and arrays are to
-      be treated as if they were named in `SAVE' statements.)
- 
-      Many other compilers do this automatically, which means lots of
-      Fortran code developed with those compilers depends on it.
- 
-      The effect of this is that all non-automatic variables and arrays
-      are made static, that is, not placed on the stack or in heap
-      storage.  This might cause a buggy program to appear to work
-      better.  If so, rather than relying on this command-line option
-      (and hoping all compilers provide the equivalent one), add `SAVE'
-      statements to some or all program unit sources, as appropriate.
-      Consider using `-Wuninitialized' (which requires `-O') to find
-      likely candidates, but do not specify `-finit-local-zero' or
-      `-fno-automatic', or this technique won't work.
- 
-      The default is `-fautomatic', which tells `g77' to try and put
-      variables and arrays on the stack (or in fast registers) where
-      possible and reasonable.  This tends to make programs faster.
- 
-      _Note:_ Automatic variables and arrays are not affected by this
-      option.  These are variables and arrays that are _necessarily_
-      automatic, either due to explicit statements, or due to the way
-      they are declared.  Examples include local variables and arrays
-      not given the `SAVE' attribute in procedures declared `RECURSIVE',
-      and local arrays declared with non-constant bounds (automatic
-      arrays).  Currently, `g77' supports only automatic arrays, not
-      `RECURSIVE' procedures or other means of explicitly specifying
-      that variables or arrays are automatic.
- 
- `-fGROUP-intrinsics-hide'
-      Change the source code to use `EXTERNAL' for any external procedure
-      that might be the name of an intrinsic.  It is easy to find these
-      using `-fGROUP-intrinsics-disable'.
- 
- 
- File: g77.info,  Node: Faster Programs,  Prev: Overly Convenient Options,  Up: Collected Fortran Wisdom
- 
- Faster Programs
- ===============
- 
-    Aside from the usual `gcc' options, such as `-O', `-ffast-math', and
- so on, consider trying some of the following approaches to speed up
- your program (once you get it working).
- 
- * Menu:
- 
- * Aligned Data::
- * Prefer Automatic Uninitialized Variables::
- * Avoid f2c Compatibility::
- * Use Submodel Options::
- 
- 
- File: g77.info,  Node: Aligned Data,  Next: Prefer Automatic Uninitialized Variables,  Up: Faster Programs
- 
- Aligned Data
- ------------
- 
-    On some systems, such as those with Pentium Pro CPUs, programs that
- make heavy use of `REAL(KIND=2)' (`DOUBLE PRECISION') might run much
- slower than possible due to the compiler not aligning these 64-bit
- values to 64-bit boundaries in memory.  (The effect also is present,
- though to a lesser extent, on the 586 (Pentium) architecture.)
- 
-    The Intel x86 architecture generally ensures that these programs will
- work on all its implementations, but particular implementations (such
- as Pentium Pro) perform better with more strict alignment.  (Such
- behavior isn't unique to the Intel x86 architecture.)  Other
- architectures might _demand_ 64-bit alignment of 64-bit data.
- 
-    There are a variety of approaches to use to address this problem:
- 
-    * Order your `COMMON' and `EQUIVALENCE' areas such that the
-      variables and arrays with the widest alignment guidelines come
-      first.
- 
-      For example, on most systems, this would mean placing
-      `COMPLEX(KIND=2)', `REAL(KIND=2)', and `INTEGER(KIND=2)' entities
-      first, followed by `REAL(KIND=1)', `INTEGER(KIND=1)', and
-      `LOGICAL(KIND=1)' entities, then `INTEGER(KIND=6)' entities, and
-      finally `CHARACTER' and `INTEGER(KIND=3)' entities.
- 
-      The reason to use such placement is it makes it more likely that
-      your data will be aligned properly, without requiring you to do
-      detailed analysis of each aggregate (`COMMON' and `EQUIVALENCE')
-      area.
- 
-      Specifically, on systems where the above guidelines are
-      appropriate, placing `CHARACTER' entities before `REAL(KIND=2)'
-      entities can work just as well, but only if the number of bytes
-      occupied by the `CHARACTER' entities is divisible by the
-      recommended alignment for `REAL(KIND=2)'.
- 
-      By ordering the placement of entities in aggregate areas according
-      to the simple guidelines above, you avoid having to carefully
-      count the number of bytes occupied by each entity to determine
-      whether the actual alignment of each subsequent entity meets the
-      alignment guidelines for the type of that entity.
- 
-      If you don't ensure correct alignment of `COMMON' elements, the
-      compiler may be forced by some systems to violate the Fortran
-      semantics by adding padding to get `DOUBLE PRECISION' data
-      properly aligned.  If the unfortunate practice is employed of
-      overlaying different types of data in the `COMMON' block, the
-      different variants of this block may become misaligned with
-      respect to each other.  Even if your platform doesn't require
-      strict alignment, `COMMON' should be laid out as above for
-      portability.  (Unfortunately the FORTRAN 77 standard didn't
-      anticipate this possible requirement, which is
-      compiler-independent on a given platform.)
- 
-    * Use the (x86-specific) `-malign-double' option when compiling
-      programs for the Pentium and Pentium Pro architectures (called 586
-      and 686 in the `gcc' configuration subsystem).  The warning about
-      this in the `gcc' manual isn't generally relevant to Fortran, but
-      using it will force `COMMON' to be padded if necessary to align
-      `DOUBLE PRECISION' data.
- 
-      When `DOUBLE PRECISION' data is forcibly aligned in `COMMON' by
-      `g77' due to specifying `-malign-double', `g77' issues a warning
-      about the need to insert padding.
- 
-      In this case, each and every program unit that uses the same
-      `COMMON' area must specify the same layout of variables and their
-      types for that area and be compiled with `-malign-double' as well.
-      `g77' will issue warnings in each case, but as long as every
-      program unit using that area is compiled with the same warnings,
-      the resulting object files should work when linked together unless
-      the program makes additional assumptions about `COMMON' area
-      layouts that are outside the scope of the FORTRAN 77 standard, or
-      uses `EQUIVALENCE' or different layouts in ways that assume no
-      padding is ever inserted by the compiler.
- 
-    * Ensure that `crt0.o' or `crt1.o' on your system guarantees a 64-bit
-      aligned stack for `main()'.  The recent one from GNU (`glibc2')
-      will do this on x86 systems, but we don't know of any other x86
-      setups where it will be right.  Read your system's documentation
-      to determine if it is appropriate to upgrade to a more recent
-      version to obtain the optimal alignment.
- 
-    Progress is being made on making this work "out of the box" on
- future versions of `g77', `gcc', and some of the relevant operating
- systems (such as GNU/Linux).
- 
-    A package that tests the degree to which a Fortran compiler (such as
- `g77') aligns 64-bit floating-point variables and arrays is available
- at `ftp://alpha.gnu.org/gnu/g77/align/'.
- 
- 
- File: g77.info,  Node: Prefer Automatic Uninitialized Variables,  Next: Avoid f2c Compatibility,  Prev: Aligned Data,  Up: Faster Programs
- 
- Prefer Automatic Uninitialized Variables
- ----------------------------------------
- 
-    If you're using `-fno-automatic' already, you probably should change
- your code to allow compilation with `-fautomatic' (the default), to
- allow the program to run faster.
- 
-    Similarly, you should be able to use `-fno-init-local-zero' (the
- default) instead of `-finit-local-zero'.  This is because it is rare
- that every variable affected by these options in a given program
- actually needs to be so affected.
- 
-    For example, `-fno-automatic', which effectively `SAVE's every local
- non-automatic variable and array, affects even things like `DO'
- iteration variables, which rarely need to be `SAVE'd, and this often
- reduces run-time performances.  Similarly, `-fno-init-local-zero'
- forces such variables to be initialized to zero--when `SAVE'd (such as
- when `-fno-automatic'), this by itself generally affects only startup
- time for a program, but when not `SAVE'd, it can slow down the
- procedure every time it is called.
- 
-    *Note Overly Convenient Command-Line Options: Overly Convenient
- Options, for information on the `-fno-automatic' and
- `-finit-local-zero' options and how to convert their use into selective
- changes in your own code.
- 
- 
- File: g77.info,  Node: Avoid f2c Compatibility,  Next: Use Submodel Options,  Prev: Prefer Automatic Uninitialized Variables,  Up: Faster Programs
- 
- Avoid f2c Compatibility
- -----------------------
- 
-    If you aren't linking with any code compiled using `f2c', try using
- the `-fno-f2c' option when compiling _all_ the code in your program.
- (Note that `libf2c' is _not_ an example of code that is compiled using
- `f2c'--it is compiled by a C compiler, typically `gcc'.)
- 
- 
- File: g77.info,  Node: Use Submodel Options,  Prev: Avoid f2c Compatibility,  Up: Faster Programs
- 
- Use Submodel Options
- --------------------
- 
-    Using an appropriate `-m' option to generate specific code for your
- CPU may be worthwhile, though it may mean the executable won't run on
- other versions of the CPU that don't support the same instruction set.
- *Note Hardware Models and Configurations: (gcc)Submodel Options.  For
- instance on an x86 system the compiler might have been built--as shown
- by `g77 -v'--for the target `i386-pc-linux-gnu', i.e. an `i386' CPU.
- In that case to generate code best optimized for a Pentium you could
- use the option `-march=pentium'.
- 
-    For recent CPUs that don't have explicit support in the released
- version of `gcc', it _might_ still be possible to get improvements with
- certain `-m' options.
- 
-    `-fomit-frame-pointer' can help performance on x86 systems and
- others.  It will, however, inhibit debugging on the systems on which it
- is not turned on anyway by `-O'.
- 
- 
- File: g77.info,  Node: Trouble,  Next: Open Questions,  Prev: Collected Fortran Wisdom,  Up: Top
- 
- Known Causes of Trouble with GNU Fortran
- ****************************************
- 
-    This section describes known problems that affect users of GNU
- Fortran.  Most of these are not GNU Fortran bugs per se--if they were,
- we would fix them.  But the result for a user might be like the result
- of a bug.
- 
-    Some of these problems are due to bugs in other software, some are
- missing features that are too much work to add, and some are places
- where people's opinions differ as to what is best.
- 
-    To find out about major bugs discovered in the current release and
- possible workarounds for them, see `ftp://alpha.gnu.org/g77.plan'.
- 
-    (Note that some of this portion of the manual is lifted directly
- from the `gcc' manual, with minor modifications to tailor it to users
- of `g77'.  Anytime a bug seems to have more to do with the `gcc'
- portion of `g77', see *Note Known Causes of Trouble with GCC:
- (gcc)Trouble.)
- 
- * Menu:
- 
- * But-bugs::         Bugs really in other programs or elsewhere.
- * Known Bugs::       Bugs known to be in this version of `g77'.
- * Missing Features:: Features we already know we want to add later.
- * Disappointments::  Regrettable things we can't change.
- * Non-bugs::         Things we think are right, but some others disagree.
- * Warnings and Errors::  Which problems in your code get warnings,
-                         and which get errors.
- 
- 
- File: g77.info,  Node: But-bugs,  Next: Known Bugs,  Up: Trouble
- 
- Bugs Not In GNU Fortran
- =======================
- 
-    These are bugs to which the maintainers often have to reply, "but
- that isn't a bug in `g77'...".  Some of these already are fixed in new
- versions of other software; some still need to be fixed; some are
- problems with how `g77' is installed or is being used; some are the
- result of bad hardware that causes software to misbehave in sometimes
- bizarre ways; some just cannot be addressed at this time until more is
- known about the problem.
- 
-    Please don't re-report these bugs to the `g77' maintainers--if you
- must remind someone how important it is to you that the problem be
- fixed, talk to the people responsible for the other products identified
- below, but preferably only after you've tried the latest versions of
- those products.  The `g77' maintainers have their hands full working on
- just fixing and improving `g77', without serving as a clearinghouse for
- all bugs that happen to affect `g77' users.
- 
-    *Note Collected Fortran Wisdom::, for information on behavior of
- Fortran programs, and the programs that compile them, that might be
- _thought_ to indicate bugs.
- 
- * Menu:
- 
- * Signal 11 and Friends::  Strange behavior by any software.
- * Cannot Link Fortran Programs::  Unresolved references.
- * Large Common Blocks::    Problems on older GNU/Linux systems.
- * Debugger Problems::      When the debugger crashes.
- * NeXTStep Problems::      Misbehaving executables.
- * Stack Overflow::         More misbehaving executables.
- * Nothing Happens::        Less behaving executables.
- * Strange Behavior at Run Time::  Executables misbehaving due to
-                             bugs in your program.
- * Floating-point Errors::  The results look wrong, but....
- 
- 
- File: g77.info,  Node: Signal 11 and Friends,  Next: Cannot Link Fortran Programs,  Up: But-bugs
- 
- Signal 11 and Friends
- ---------------------
- 
-    A whole variety of strange behaviors can occur when the software, or
- the way you are using the software, stresses the hardware in a way that
- triggers hardware bugs.  This might seem hard to believe, but it
- happens frequently enough that there exist documents explaining in
- detail what the various causes of the problems are, what typical
- symptoms look like, and so on.
- 
-    Generally these problems are referred to in this document as "signal
- 11" crashes, because the Linux kernel, running on the most popular
- hardware (the Intel x86 line), often stresses the hardware more than
- other popular operating systems.  When hardware problems do occur under
- GNU/Linux on x86 systems, these often manifest themselves as "signal 11"
- problems, as illustrated by the following diagnostic:
- 
-      sh# g77 myprog.f
-      gcc: Internal compiler error: program f771 got fatal signal 11
-      sh#
- 
-    It is _very_ important to remember that the above message is _not_
- the only one that indicates a hardware problem, nor does it always
- indicate a hardware problem.
- 
-    In particular, on systems other than those running the Linux kernel,
- the message might appear somewhat or very different, as it will if the
- error manifests itself while running a program other than the `g77'
- compiler.  For example, it will appear somewhat different when running
- your program, when running Emacs, and so on.
- 
-    How to cope with such problems is well beyond the scope of this
- manual.
- 
-    However, users of Linux-based systems (such as GNU/Linux) should
- review `http://www.bitwizard.nl/sig11/', a source of detailed
- information on diagnosing hardware problems, by recognizing their
- common symptoms.
- 
-    Users of other operating systems and hardware might find this
- reference useful as well.  If you know of similar material for another
- hardware/software combination, please let us know so we can consider
- including a reference to it in future versions of this manual.
- 
- 
- File: g77.info,  Node: Cannot Link Fortran Programs,  Next: Large Common Blocks,  Prev: Signal 11 and Friends,  Up: But-bugs
- 
- Cannot Link Fortran Programs
- ----------------------------
- 
-    On some systems, perhaps just those with out-of-date (shared?)
- libraries, unresolved-reference errors happen when linking
- `g77'-compiled programs (which should be done using `g77').
- 
-    If this happens to you, try appending `-lc' to the command you use
- to link the program, e.g. `g77 foo.f -lc'.  `g77' already specifies
- `-lg2c -lm' when it calls the linker, but it cannot also specify `-lc'
- because not all systems have a file named `libc.a'.
- 
-    It is unclear at this point whether there are legitimately installed
- systems where `-lg2c -lm' is insufficient to resolve code produced by
- `g77'.
- 
-    If your program doesn't link due to unresolved references to names
- like `_main', make sure you're using the `g77' command to do the link,
- since this command ensures that the necessary libraries are loaded by
- specifying `-lg2c -lm' when it invokes the `gcc' command to do the
- actual link.  (Use the `-v' option to discover more about what actually
- happens when you use the `g77' and `gcc' commands.)
- 
-    Also, try specifying `-lc' as the last item on the `g77' command
- line, in case that helps.
- 
- 
- File: g77.info,  Node: Large Common Blocks,  Next: Debugger Problems,  Prev: Cannot Link Fortran Programs,  Up: But-bugs
- 
- Large Common Blocks
- -------------------
- 
-    On some older GNU/Linux systems, programs with common blocks larger
- than 16MB cannot be linked without some kind of error message being
- produced.
- 
-    This is a bug in older versions of `ld', fixed in more recent
- versions of `binutils', such as version 2.6.
- 
- 
- File: g77.info,  Node: Debugger Problems,  Next: NeXTStep Problems,  Prev: Large Common Blocks,  Up: But-bugs
- 
- Debugger Problems
- -----------------
- 
-    There are some known problems when using `gdb' on code compiled by
- `g77'.  Inadequate investigation as of the release of 0.5.16 results in
- not knowing which products are the culprit, but `gdb-4.14' definitely
- crashes when, for example, an attempt is made to print the contents of
- a `COMPLEX(KIND=2)' dummy array, on at least some GNU/Linux machines,
- plus some others.  Attempts to access assumed-size arrays are also
- known to crash recent versions of `gdb'.  (`gdb''s Fortran support was
- done for a different compiler and isn't properly compatible with `g77'.)
- 
- 
- File: g77.info,  Node: NeXTStep Problems,  Next: Stack Overflow,  Prev: Debugger Problems,  Up: But-bugs
- 
- NeXTStep Problems
- -----------------
- 
-    Developers of Fortran code on NeXTStep (all architectures) have to
- watch out for the following problem when writing programs with large,
- statically allocated (i.e. non-stack based) data structures (common
- blocks, saved arrays).
- 
-    Due to the way the native loader (`/bin/ld') lays out data
- structures in virtual memory, it is very easy to create an executable
- wherein the `__DATA' segment overlaps (has addresses in common) with
- the `UNIX STACK' segment.
- 
-    This leads to all sorts of trouble, from the executable simply not
- executing, to bus errors.  The NeXTStep command line tool `ebadexec'
- points to the problem as follows:
- 
-      % /bin/ebadexec a.out
-      /bin/ebadexec: __LINKEDIT segment (truncated address = 0x3de000
-      rounded size = 0x2a000) of executable file: a.out overlaps with UNIX
-      STACK segment (truncated address = 0x400000 rounded size =
-      0x3c00000) of executable file: a.out
- 
-    (In the above case, it is the `__LINKEDIT' segment that overlaps the
- stack segment.)
- 
-    This can be cured by assigning the `__DATA' segment (virtual)
- addresses beyond the stack segment.  A conservative estimate for this
- is from address 6000000 (hexadecimal) onwards--this has always worked
- for me [Toon Moene]:
- 
-      % g77 -segaddr __DATA 6000000 test.f
-      % ebadexec a.out
-      ebadexec: file: a.out appears to be executable
-      %
- 
-    Browsing through `gcc/gcc/f/Makefile.in', you will find that the
- `f771' program itself also has to be linked with these flags--it has
- large statically allocated data structures.  (Version 0.5.18 reduces
- this somewhat, but probably not enough.)
- 
-    (The above item was contributed by Toon Moene
- (<toon@moene.indiv.nluug.nl>).)
- 
- 
- File: g77.info,  Node: Stack Overflow,  Next: Nothing Happens,  Prev: NeXTStep Problems,  Up: But-bugs
- 
- Stack Overflow
- --------------
- 
-    `g77' code might fail at runtime (probably with a "segmentation
- violation") due to overflowing the stack.  This happens most often on
- systems with an environment that provides substantially more heap space
- (for use when arbitrarily allocating and freeing memory) than stack
- space.
- 
-    Often this can be cured by increasing or removing your shell's limit
- on stack usage, typically using `limit stacksize' (in `csh' and
- derivatives) or `ulimit -s' (in `sh' and derivatives).
- 
-    Increasing the allowed stack size might, however, require changing
- some operating system or system configuration parameters.
- 
-    You might be able to work around the problem by compiling with the
- `-fno-automatic' option to reduce stack usage, probably at the expense
- of speed.
- 
-    `g77', on most machines, puts many variables and arrays on the stack
- where possible, and can be configured (by changing
- `FFECOM_sizeMAXSTACKITEM' in `gcc/gcc/f/com.c') to force smaller-sized
- entities into static storage (saving on stack space) or permit
- larger-sized entities to be put on the stack (which can improve
- run-time performance, as it presents more opportunities for the GBE to
- optimize the generated code).
- 
-    _Note:_ Putting more variables and arrays on the stack might cause
- problems due to system-dependent limits on stack size.  Also, the value
- of `FFECOM_sizeMAXSTACKITEM' has no effect on automatic variables and
- arrays.  *Note But-bugs::, for more information.  _Note:_ While
- `libg2c' places a limit on the range of Fortran file-unit numbers, the
- underlying library and operating system might impose different kinds of
- limits.  For example, some systems limit the number of files
- simultaneously open by a running program.  Information on how to
- increase these limits should be found in your system's documentation.
- 
-    However, if your program uses large automatic arrays (for example,
- has declarations like `REAL A(N)' where `A' is a local array and `N' is
- a dummy or `COMMON' variable that can have a large value), neither use
- of `-fno-automatic', nor changing the cut-off point for `g77' for using
- the stack, will solve the problem by changing the placement of these
- large arrays, as they are _necessarily_ automatic.
- 
-    `g77' currently provides no means to specify that automatic arrays
- are to be allocated on the heap instead of the stack.  So, other than
- increasing the stack size, your best bet is to change your source code
- to avoid large automatic arrays.  Methods for doing this currently are
- outside the scope of this document.
- 
-    (_Note:_ If your system puts stack and heap space in the same memory
- area, such that they are effectively combined, then a stack overflow
- probably indicates a program that is either simply too large for the
- system, or buggy.)
- 
- 
- File: g77.info,  Node: Nothing Happens,  Next: Strange Behavior at Run Time,  Prev: Stack Overflow,  Up: But-bugs
- 
- Nothing Happens
- ---------------
- 
-    It is occasionally reported that a "simple" program, such as a
- "Hello, World!" program, does nothing when it is run, even though the
- compiler reported no errors, despite the program containing nothing
- other than a simple `PRINT' statement.
- 
-    This most often happens because the program has been compiled and
- linked on a UNIX system and named `test', though other names can lead
- to similarly unexpected run-time behavior on various systems.
- 
-    Essentially this problem boils down to giving your program a name
- that is already known to the shell you are using to identify some other
- program, which the shell continues to execute instead of your program
- when you invoke it via, for example:
- 
-      sh# test
-      sh#
- 
-    Under UNIX and many other system, a simple command name invokes a
- searching mechanism that might well not choose the program located in
- the current working directory if there is another alternative (such as
- the `test' command commonly installed on UNIX systems).
- 
-    The reliable way to invoke a program you just linked in the current
- directory under UNIX is to specify it using an explicit pathname, as in:
- 
-      sh# ./test
-       Hello, World!
-      sh#
- 
-    Users who encounter this problem should take the time to read up on
- how their shell searches for commands, how to set their search path,
- and so on.  The relevant UNIX commands to learn about include `man',
- `info' (on GNU systems), `setenv' (or `set' and `env'), `which', and
- `find'.
- 
- 
- File: g77.info,  Node: Strange Behavior at Run Time,  Next: Floating-point Errors,  Prev: Nothing Happens,  Up: But-bugs
- 
- Strange Behavior at Run Time
- ----------------------------
- 
-    `g77' code might fail at runtime with "segmentation violation", "bus
- error", or even something as subtle as a procedure call overwriting a
- variable or array element that it is not supposed to touch.
- 
-    These can be symptoms of a wide variety of actual bugs that occurred
- earlier during the program's run, but manifested themselves as
- _visible_ problems some time later.
- 
-    Overflowing the bounds of an array--usually by writing beyond the
- end of it--is one of two kinds of bug that often occurs in Fortran code.
- (Compile your code with the `-fbounds-check' option to catch many of
- these kinds of errors at program run time.)
- 
-    The other kind of bug is a mismatch between the actual arguments
- passed to a procedure and the dummy arguments as declared by that
- procedure.
- 
-    Both of these kinds of bugs, and some others as well, can be
- difficult to track down, because the bug can change its behavior, or
- even appear to not occur, when using a debugger.
- 
-    That is, these bugs can be quite sensitive to data, including data
- representing the placement of other data in memory (that is, pointers,
- such as the placement of stack frames in memory).
- 
-    `g77' now offers the ability to catch and report some of these
- problems at compile, link, or run time, such as by generating code to
- detect references to beyond the bounds of most arrays (except
- assumed-size arrays), and checking for agreement between calling and
- called procedures.  Future improvements are likely to be made in the
- procedure-mismatch area, at least.
- 
-    In the meantime, finding and fixing the programming bugs that lead
- to these behaviors is, ultimately, the user's responsibility, as
- difficult as that task can sometimes be.
- 
-    One runtime problem that has been observed might have a simple
- solution.  If a formatted `WRITE' produces an endless stream of spaces,
- check that your program is linked against the correct version of the C
- library.  The configuration process takes care to account for your
- system's normal `libc' not being ANSI-standard, which will otherwise
- cause this behaviour.  If your system's default library is
- ANSI-standard and you subsequently link against a non-ANSI one, there
- might be problems such as this one.
- 
-    Specifically, on Solaris2 systems, avoid picking up the `BSD'
- library from `/usr/ucblib'.
- 
- 
- File: g77.info,  Node: Floating-point Errors,  Prev: Strange Behavior at Run Time,  Up: But-bugs
- 
- Floating-point Errors
- ---------------------
- 
-    Some programs appear to produce inconsistent floating-point results
- compiled by `g77' versus by other compilers.
- 
-    Often the reason for this behavior is the fact that floating-point
- values are represented on almost all Fortran systems by
- _approximations_, and these approximations are inexact even for
- apparently simple values like 0.1, 0.2, 0.3, 0.4, 0.6, 0.7, 0.8, 0.9,
- 1.1, and so on.  Most Fortran systems, including all current ports of
- `g77', use binary arithmetic to represent these approximations.
- 
-    Therefore, the exact value of any floating-point approximation as
- manipulated by `g77'-compiled code is representable by adding some
- combination of the values 1.0, 0.5, 0.25, 0.125, and so on (just keep
- dividing by two) through the precision of the fraction (typically
- around 23 bits for `REAL(KIND=1)', 52 for `REAL(KIND=2)'), then
- multiplying the sum by a integral power of two (in Fortran, by `2**N')
- that typically is between -127 and +128 for `REAL(KIND=1)' and -1023
- and +1024 for `REAL(KIND=2)', then multiplying by -1 if the number is
- negative.
- 
-    So, a value like 0.2 is exactly represented in decimal--since it is
- a fraction, `2/10', with a denominator that is compatible with the base
- of the number system (base 10).  However, `2/10' cannot be represented
- by any finite number of sums of any of 1.0, 0.5, 0.25, and so on, so
- 0.2 cannot be exactly represented in binary notation.
- 
-    (On the other hand, decimal notation can represent any binary number
- in a finite number of digits.  Decimal notation cannot do so with
- ternary, or base-3, notation, which would represent floating-point
- numbers as sums of any of `1/1', `1/3', `1/9', and so on.  After all,
- no finite number of decimal digits can exactly represent `1/3'.
- Fortunately, few systems use ternary notation.)
- 
-    Moreover, differences in the way run-time I/O libraries convert
- between these approximations and the decimal representation often used
- by programmers and the programs they write can result in apparent
- differences between results that do not actually exist, or exist to
- such a small degree that they usually are not worth worrying about.
- 
-    For example, consider the following program:
- 
-      PRINT *, 0.2
-      END
- 
-    When compiled by `g77', the above program might output `0.20000003',
- while another compiler might produce a executable that outputs `0.2'.
- 
-    This particular difference is due to the fact that, currently,
- conversion of floating-point values by the `libg2c' library, used by
- `g77', handles only double-precision values.
- 
-    Since `0.2' in the program is a single-precision value, it is
- converted to double precision (still in binary notation) before being
- converted back to decimal.  The conversion to binary appends _binary_
- zero digits to the original value--which, again, is an inexact
- approximation of 0.2--resulting in an approximation that is much less
- exact than is connoted by the use of double precision.
- 
-    (The appending of binary zero digits has essentially the same effect
- as taking a particular decimal approximation of `1/3', such as
- `0.3333333', and appending decimal zeros to it, producing
- `0.33333330000000000'.  Treating the resulting decimal approximation as
- if it really had 18 or so digits of valid precision would make it seem
- a very poor approximation of `1/3'.)
- 
-    As a result of converting the single-precision approximation to
- double precision by appending binary zeros, the conversion of the
- resulting double-precision value to decimal produces what looks like an
- incorrect result, when in fact the result is _inexact_, and is probably
- no less inaccurate or imprecise an approximation of 0.2 than is
- produced by other compilers that happen to output the converted value
- as "exactly" `0.2'.  (Some compilers behave in a way that can make them
- appear to retain more accuracy across a conversion of a single-precision
- constant to double precision.  *Note Context-Sensitive Constants::, to
- see why this practice is illusory and even dangerous.)
- 
-    Note that a more exact approximation of the constant is computed
- when the program is changed to specify a double-precision constant:
- 
-      PRINT *, 0.2D0
-      END
- 
-    Future versions of `g77' and/or `libg2c' might convert
- single-precision values directly to decimal, instead of converting them
- to double precision first.  This would tend to result in output that is
- more consistent with that produced by some other Fortran
- implementations.
- 
-    A useful source of information on floating-point computation is David
- Goldberg, `What Every Computer Scientist Should Know About
- Floating-Point Arithmetic', Computing Surveys, 23, March 1991, pp.
- 5-48.  An online version is available at `http://docs.sun.com/', and
- there is a supplemented version, in PostScript form, at
- `http://www.validgh.com/goldberg/paper.ps'.
- 
-    Information related to the IEEE 754 floating-point standard by a
- leading light can be found at
- `http://http.cs.berkeley.edu/%7Ewkahan/ieee754status/'; see also slides
- from the short course referenced from
- `http://http.cs.berkeley.edu/%7Efateman/'.
- `http://www.linuxsupportline.com/%7Ebillm/' has a brief guide to IEEE
- 754, a somewhat x86-GNU/Linux-specific FAQ, and library code for
- GNU/Linux x86 systems.
- 
-    The supplement to the PostScript-formatted Goldberg document,
- referenced above, is available in HTML format.  See `Differences Among
- IEEE 754 Implementations' by Doug Priest, available online at
- `http://www.validgh.com/goldberg/addendum.html'.  This document
- explores some of the issues surrounding computing of extended (80-bit)
- results on processors such as the x86, especially when those results
- are arbitrarily truncated to 32-bit or 64-bit values by the compiler as
- "spills".
- 
-    (_Note:_ `g77' specifically, and `gcc' generally, does arbitrarily
- truncate 80-bit results during spills as of this writing.  It is not
- yet clear whether a future version of the GNU compiler suite will offer
- 80-bit spills as an option, or perhaps even as the default behavior.)
- 
-    The GNU C library provides routines for controlling the FPU, and
- other documentation about this.
- 
-    *Note Floating-point precision::, regarding IEEE 754 conformance.
- 
--- 0 ----
diff -Nrc3pad gcc-3.2.3/gcc/f/g77.info-16 gcc-3.3/gcc/f/g77.info-16
*** gcc-3.2.3/gcc/f/g77.info-16	2003-04-22 07:07:24.000000000 +0000
--- gcc-3.3/gcc/f/g77.info-16	1970-01-01 00:00:00.000000000 +0000
***************
*** 1,1283 ****
- This is g77.info, produced by makeinfo version 4.5 from g77.texi.
- 
- INFO-DIR-SECTION Programming
- START-INFO-DIR-ENTRY
- * g77: (g77).                  The GNU Fortran compiler.
- END-INFO-DIR-ENTRY
-    This file documents the use and the internals of the GNU Fortran
- (`g77') compiler.  It corresponds to the GCC-3.2.3 version of `g77'.
- 
-    Published by the Free Software Foundation 59 Temple Place - Suite 330
- Boston, MA 02111-1307 USA
- 
-    Copyright (C) 1995,1996,1997,1998,1999,2000,2001,2002 Free Software
- Foundation, Inc.
- 
-    Permission is granted to copy, distribute and/or modify this document
- under the terms of the GNU Free Documentation License, Version 1.1 or
- any later version published by the Free Software Foundation; with the
- Invariant Sections being "GNU General Public License" and "Funding Free
- Software", the Front-Cover texts being (a) (see below), and with the
- Back-Cover Texts being (b) (see below).  A copy of the license is
- included in the section entitled "GNU Free Documentation License".
- 
-    (a) The FSF's Front-Cover Text is:
- 
-    A GNU Manual
- 
-    (b) The FSF's Back-Cover Text is:
- 
-    You have freedom to copy and modify this GNU Manual, like GNU
- software.  Copies published by the Free Software Foundation raise
- funds for GNU development.
- 
-    Contributed by James Craig Burley (<craig@jcb-sc.com>).  Inspired by
- a first pass at translating `g77-0.5.16/f/DOC' that was contributed to
- Craig by David Ronis (<ronis@onsager.chem.mcgill.ca>).
- 
- 
- File: g77.info,  Node: Known Bugs,  Next: Missing Features,  Prev: But-bugs,  Up: Trouble
- 
- Known Bugs In GNU Fortran
- =========================
- 
-    This section identifies bugs that `g77' _users_ might run into in
- the GCC-3.2.3 version of `g77'.  This includes bugs that are actually
- in the `gcc' back end (GBE) or in `libf2c', because those sets of code
- are at least somewhat under the control of (and necessarily intertwined
- with) `g77', so it isn't worth separating them out.
- 
-    For information on bugs in _other_ versions of `g77', see *Note News
- About GNU Fortran: News.  There, lists of bugs fixed in various
- versions of `g77' can help determine what bugs existed in prior
- versions.
- 
-    An online, "live" version of this document (derived directly from
- the mainline, development version of `g77' within `gcc') is available
- via `http://www.gnu.org/software/gcc/onlinedocs/g77/Trouble.html'.
- Follow the "Known Bugs" link.
- 
-    The following information was last updated on 2002-02-01:
- 
-    * `g77' fails to warn about use of a "live" iterative-DO variable as
-      an implied-DO variable in a `WRITE' or `PRINT' statement (although
-      it does warn about this in a `READ' statement).
- 
-    * Something about `g77''s straightforward handling of label
-      references and definitions sometimes prevents the GBE from
-      unrolling loops.  Until this is solved, try inserting or removing
-      `CONTINUE' statements as the terminal statement, using the `END DO'
-      form instead, and so on.
- 
-    * Some confusion in diagnostics concerning failing `INCLUDE'
-      statements from within `INCLUDE''d or `#include''d files.
- 
-    * `g77' assumes that `INTEGER(KIND=1)' constants range from `-2**31'
-      to `2**31-1' (the range for two's-complement 32-bit values),
-      instead of determining their range from the actual range of the
-      type for the configuration (and, someday, for the constant).
- 
-      Further, it generally doesn't implement the handling of constants
-      very well in that it makes assumptions about the configuration
-      that it no longer makes regarding variables (types).
- 
-      Included with this item is the fact that `g77' doesn't recognize
-      that, on IEEE-754/854-compliant systems, `0./0.' should produce a
-      NaN and no warning instead of the value `0.' and a warning.
- 
-    * `g77' uses way too much memory and CPU time to process large
-      aggregate areas having any initialized elements.
- 
-      For example, `REAL A(1000000)' followed by `DATA A(1)/1/' takes up
-      way too much time and space, including the size of the generated
-      assembler file.
- 
-      Version 0.5.18 improves cases like this--specifically, cases of
-      _sparse_ initialization that leave large, contiguous areas
-      uninitialized--significantly.  However, even with the
-      improvements, these cases still require too much memory and CPU
-      time.
- 
-      (Version 0.5.18 also improves cases where the initial values are
-      zero to a much greater degree, so if the above example ends with
-      `DATA A(1)/0/', the compile-time performance will be about as good
-      as it will ever get, aside from unrelated improvements to the
-      compiler.)
- 
-      Note that `g77' does display a warning message to notify the user
-      before the compiler appears to hang.  A warning message is issued
-      when `g77' sees code that provides initial values (e.g. via
-      `DATA') to an aggregate area (`COMMON' or `EQUIVALENCE', or even a
-      large enough array or `CHARACTER' variable) that is large enough
-      to increase `g77''s compile time by roughly a factor of 10.
- 
-      This size currently is quite small, since `g77' currently has a
-      known bug requiring too much memory and time to handle such cases.
-      In `gcc/gcc/f/data.c', the macro `FFEDATA_sizeTOO_BIG_INIT_' is
-      defined to the minimum size for the warning to appear.  The size
-      is specified in storage units, which can be bytes, words, or
-      whatever, on a case-by-case basis.
- 
-      After changing this macro definition, you must (of course) rebuild
-      and reinstall `g77' for the change to take effect.
- 
-      Note that, as of version 0.5.18, improvements have reduced the
-      scope of the problem for _sparse_ initialization of large arrays,
-      especially those with large, contiguous uninitialized areas.
-      However, the warning is issued at a point prior to when `g77'
-      knows whether the initialization is sparse, and delaying the
-      warning could mean it is produced too late to be helpful.
- 
-      Therefore, the macro definition should not be adjusted to reflect
-      sparse cases.  Instead, adjust it to generate the warning when
-      densely initialized arrays begin to cause responses noticeably
-      slower than linear performance would suggest.
- 
-    * When debugging, after starting up the debugger but before being
-      able to see the source code for the main program unit, the user
-      must currently set a breakpoint at `MAIN__' (or `MAIN___' or
-      `MAIN_' if `MAIN__' doesn't exist) and run the program until it
-      hits the breakpoint.  At that point, the main program unit is
-      activated and about to execute its first executable statement, but
-      that's the state in which the debugger should start up, as is the
-      case for languages like C.
- 
-    * Debugging `g77'-compiled code using debuggers other than `gdb' is
-      likely not to work.
- 
-      Getting `g77' and `gdb' to work together is a known
-      problem--getting `g77' to work properly with other debuggers, for
-      which source code often is unavailable to `g77' developers, seems
-      like a much larger, unknown problem, and is a lower priority than
-      making `g77' and `gdb' work together properly.
- 
-      On the other hand, information about problems other debuggers have
-      with `g77' output might make it easier to properly fix `g77', and
-      perhaps even improve `gdb', so it is definitely welcome.  Such
-      information might even lead to all relevant products working
-      together properly sooner.
- 
-    * `g77' doesn't work perfectly on 64-bit configurations such as the
-      Digital Semiconductor ("DEC") Alpha.
- 
-      This problem is largely resolved as of version 0.5.23.
- 
-    * `g77' currently inserts needless padding for things like `COMMON
-      A,IPAD' where `A' is `CHARACTER*1' and `IPAD' is `INTEGER(KIND=1)'
-      on machines like x86, because the back end insists that `IPAD' be
-      aligned to a 4-byte boundary, but the processor has no such
-      requirement (though it is usually good for performance).
- 
-      The `gcc' back end needs to provide a wider array of
-      specifications of alignment requirements and preferences for
-      targets, and front ends like `g77' should take advantage of this
-      when it becomes available.
- 
-    * The `libf2c' routines that perform some run-time arithmetic on
-      `COMPLEX' operands were modified circa version 0.5.20 of `g77' to
-      work properly even in the presence of aliased operands.
- 
-      While the `g77' and `netlib' versions of `libf2c' differ on how
-      this is accomplished, the main differences are that we believe the
-      `g77' version works properly even in the presence of _partially_
-      aliased operands.
- 
-      However, these modifications have reduced performance on targets
-      such as x86, due to the extra copies of operands involved.
- 
- 
- File: g77.info,  Node: Missing Features,  Next: Disappointments,  Prev: Known Bugs,  Up: Trouble
- 
- Missing Features
- ================
- 
-    This section lists features we know are missing from `g77', and
- which we want to add someday.  (There is no priority implied in the
- ordering below.)
- 
- * Menu:
- 
- GNU Fortran language:
- * Better Source Model::
- * Fortran 90 Support::
- * Intrinsics in PARAMETER Statements::
- * Arbitrary Concatenation::
- * SELECT CASE on CHARACTER Type::
- * RECURSIVE Keyword::
- * Popular Non-standard Types::
- * Full Support for Compiler Types::
- * Array Bounds Expressions::
- * POINTER Statements::
- * Sensible Non-standard Constructs::
- * READONLY Keyword::
- * FLUSH Statement::
- * Expressions in FORMAT Statements::
- * Explicit Assembler Code::
- * Q Edit Descriptor::
- 
- GNU Fortran dialects:
- * Old-style PARAMETER Statements::
- * TYPE and ACCEPT I/O Statements::
- * STRUCTURE UNION RECORD MAP::
- * OPEN CLOSE and INQUIRE Keywords::
- * ENCODE and DECODE::
- * AUTOMATIC Statement::
- * Suppressing Space Padding::
- * Fortran Preprocessor::
- * Bit Operations on Floating-point Data::
- * Really Ugly Character Assignments::
- 
- New facilities:
- * POSIX Standard::
- * Floating-point Exception Handling::
- * Nonportable Conversions::
- * Large Automatic Arrays::
- * Support for Threads::
- * Increasing Precision/Range::
- * Enabling Debug Lines::
- 
- Better diagnostics:
- * Better Warnings::
- * Gracefully Handle Sensible Bad Code::
- * Non-standard Conversions::
- * Non-standard Intrinsics::
- * Modifying DO Variable::
- * Better Pedantic Compilation::
- * Warn About Implicit Conversions::
- * Invalid Use of Hollerith Constant::
- * Dummy Array Without Dimensioning Dummy::
- * Invalid FORMAT Specifiers::
- * Ambiguous Dialects::
- * Unused Labels::
- * Informational Messages::
- 
- Run-time facilities:
- * Uninitialized Variables at Run Time::
- * Portable Unformatted Files::
- * Better List-directed I/O::
- * Default to Console I/O::
- 
- Debugging:
- * Labels Visible to Debugger::
- 
- 
- File: g77.info,  Node: Better Source Model,  Next: Fortran 90 Support,  Up: Missing Features
- 
- Better Source Model
- -------------------
- 
-    `g77' needs to provide, as the default source-line model, a "pure
- visual" mode, where the interpretation of a source program in this mode
- can be accurately determined by a user looking at a traditionally
- displayed rendition of the program (assuming the user knows whether the
- program is fixed or free form).
- 
-    The design should assume the user cannot tell tabs from spaces and
- cannot see trailing spaces on lines, but has canonical tab stops and,
- for fixed-form source, has the ability to always know exactly where
- column 72 is (since the Fortran standard itself requires this for
- fixed-form source).
- 
-    This would change the default treatment of fixed-form source to not
- treat lines with tabs as if they were infinitely long--instead, they
- would end at column 72 just as if the tabs were replaced by spaces in
- the canonical way.
- 
-    As part of this, provide common alternate models (Digital, `f2c',
- and so on) via command-line options.  This includes allowing
- arbitrarily long lines for free-form source as well as fixed-form
- source and providing various limits and diagnostics as appropriate.
- 
-    Also, `g77' should offer, perhaps even default to, warnings when
- characters beyond the last valid column are anything other than spaces.
- This would mean code with "sequence numbers" in columns 73 through 80
- would be rejected, and there's a lot of that kind of code around, but
- one of the most frequent bugs encountered by new users is accidentally
- writing fixed-form source code into and beyond column 73.  So, maybe
- the users of old code would be able to more easily handle having to
- specify, say, a `-Wno-col73to80' option.
- 
- 
- File: g77.info,  Node: Fortran 90 Support,  Next: Intrinsics in PARAMETER Statements,  Prev: Better Source Model,  Up: Missing Features
- 
- Fortran 90 Support
- ------------------
- 
-    `g77' does not support many of the features that distinguish Fortran
- 90 (and, now, Fortran 95) from ANSI FORTRAN 77.
- 
-    Some Fortran 90 features are supported, because they make sense to
- offer even to die-hard users of F77.  For example, many of them codify
- various ways F77 has been extended to meet users' needs during its
- tenure, so `g77' might as well offer them as the primary way to meet
- those same needs, even if it offers compatibility with one or more of
- the ways those needs were met by other F77 compilers in the industry.
- 
-    Still, many important F90 features are not supported, because no
- attempt has been made to research each and every feature and assess its
- viability in `g77'.  In the meantime, users who need those features must
- use Fortran 90 compilers anyway, and the best approach to adding some
- F90 features to GNU Fortran might well be to fund a comprehensive
- project to create GNU Fortran 95.
- 
- 
- File: g77.info,  Node: Intrinsics in PARAMETER Statements,  Next: Arbitrary Concatenation,  Prev: Fortran 90 Support,  Up: Missing Features
- 
- Intrinsics in `PARAMETER' Statements
- ------------------------------------
- 
-    `g77' doesn't allow intrinsics in `PARAMETER' statements.
- 
-    Related to this, `g77' doesn't allow non-integral exponentiation in
- `PARAMETER' statements, such as `PARAMETER (R=2**.25)'.  It is unlikely
- `g77' will ever support this feature, as doing it properly requires
- complete emulation of a target computer's floating-point facilities when
- building `g77' as a cross-compiler.  But, if the `gcc' back end is
- enhanced to provide such a facility, `g77' will likely use that facility
- in implementing this feature soon afterwards.
- 
- 
- File: g77.info,  Node: Arbitrary Concatenation,  Next: SELECT CASE on CHARACTER Type,  Prev: Intrinsics in PARAMETER Statements,  Up: Missing Features
- 
- Arbitrary Concatenation
- -----------------------
- 
-    `g77' doesn't support arbitrary operands for concatenation in
- contexts where run-time allocation is required.  For example:
- 
-      SUBROUTINE X(A)
-      CHARACTER*(*) A
-      CALL FOO(A // 'suffix')
- 
- 
- File: g77.info,  Node: SELECT CASE on CHARACTER Type,  Next: RECURSIVE Keyword,  Prev: Arbitrary Concatenation,  Up: Missing Features
- 
- `SELECT CASE' on `CHARACTER' Type
- ---------------------------------
- 
-    Character-type selector/cases for `SELECT CASE' currently are not
- supported.
- 
- 
- File: g77.info,  Node: RECURSIVE Keyword,  Next: Popular Non-standard Types,  Prev: SELECT CASE on CHARACTER Type,  Up: Missing Features
- 
- `RECURSIVE' Keyword
- -------------------
- 
-    `g77' doesn't support the `RECURSIVE' keyword that F90 compilers do.
- Nor does it provide any means for compiling procedures designed to do
- recursion.
- 
-    All recursive code can be rewritten to not use recursion, but the
- result is not pretty.
- 
- 
- File: g77.info,  Node: Increasing Precision/Range,  Next: Enabling Debug Lines,  Prev: Support for Threads,  Up: Missing Features
- 
- Increasing Precision/Range
- --------------------------
- 
-    Some compilers, such as `f2c', have an option (`-r8', `-qrealsize=8'
- or similar) that provides automatic treatment of `REAL' entities such
- that they have twice the storage size, and a corresponding increase in
- the range and precision, of what would normally be the `REAL(KIND=1)'
- (default `REAL') type.  (This affects `COMPLEX' the same way.)
- 
-    They also typically offer another option (`-i8') to increase
- `INTEGER' entities so they are twice as large (with roughly twice as
- much range).
- 
-    (There are potential pitfalls in using these options.)
- 
-    `g77' does not yet offer any option that performs these kinds of
- transformations.  Part of the problem is the lack of detailed
- specifications regarding exactly how these options affect the
- interpretation of constants, intrinsics, and so on.
- 
-    Until `g77' addresses this need, programmers could improve the
- portability of their code by modifying it to not require compile-time
- options to produce correct results.  Some free tools are available
- which may help, specifically in Toolpack (which one would expect to be
- sound) and the `fortran' section of the Netlib repository.
- 
-    Use of preprocessors can provide a fairly portable means to work
- around the lack of widely portable methods in the Fortran language
- itself (though increasing acceptance of Fortran 90 would alleviate this
- problem).
- 
- 
- File: g77.info,  Node: Popular Non-standard Types,  Next: Full Support for Compiler Types,  Prev: RECURSIVE Keyword,  Up: Missing Features
- 
- Popular Non-standard Types
- --------------------------
- 
-    `g77' doesn't fully support `INTEGER*2', `LOGICAL*1', and similar.
- In the meantime, version 0.5.18 provides rudimentary support for them.
- 
- 
- File: g77.info,  Node: Full Support for Compiler Types,  Next: Array Bounds Expressions,  Prev: Popular Non-standard Types,  Up: Missing Features
- 
- Full Support for Compiler Types
- -------------------------------
- 
-    `g77' doesn't support `INTEGER', `REAL', and `COMPLEX' equivalents
- for _all_ applicable back-end-supported types (`char', `short int',
- `int', `long int', `long long int', and `long double').  This means
- providing intrinsic support, and maybe constant support (using F90
- syntax) as well, and, for most machines will result in automatic
- support of `INTEGER*1', `INTEGER*2', `INTEGER*8', maybe even `REAL*16',
- and so on.
- 
- 
- File: g77.info,  Node: Array Bounds Expressions,  Next: POINTER Statements,  Prev: Full Support for Compiler Types,  Up: Missing Features
- 
- Array Bounds Expressions
- ------------------------
- 
-    `g77' doesn't support more general expressions to dimension arrays,
- such as array element references, function references, etc.
- 
-    For example, `g77' currently does not accept the following:
- 
-      SUBROUTINE X(M, N)
-      INTEGER N(10), M(N(2), N(1))
- 
- 
- File: g77.info,  Node: POINTER Statements,  Next: Sensible Non-standard Constructs,  Prev: Array Bounds Expressions,  Up: Missing Features
- 
- POINTER Statements
- ------------------
- 
-    `g77' doesn't support pointers or allocatable objects (other than
- automatic arrays).  This set of features is probably considered just
- behind intrinsics in `PARAMETER' statements on the list of large,
- important things to add to `g77'.
- 
-    In the meantime, consider using the `INTEGER(KIND=7)' declaration to
- specify that a variable must be able to hold a pointer.  This construct
- is not portable to other non-GNU compilers, but it is portable to all
- machines GNU Fortran supports when `g77' is used.
- 
-    *Note Functions and Subroutines::, for information on `%VAL()',
- `%REF()', and `%DESCR()' constructs, which are useful for passing
- pointers to procedures written in languages other than Fortran.
- 
- 
- File: g77.info,  Node: Sensible Non-standard Constructs,  Next: READONLY Keyword,  Prev: POINTER Statements,  Up: Missing Features
- 
- Sensible Non-standard Constructs
- --------------------------------
- 
-    `g77' rejects things other compilers accept, like `INTRINSIC
- SQRT,SQRT'.  As time permits in the future, some of these things that
- are easy for humans to read and write and unlikely to be intended to
- mean something else will be accepted by `g77' (though `-fpedantic'
- should trigger warnings about such non-standard constructs).
- 
-    Until `g77' no longer gratuitously rejects sensible code, you might
- as well fix your code to be more standard-conforming and portable.
- 
-    The kind of case that is important to except from the recommendation
- to change your code is one where following good coding rules would
- force you to write non-standard code that nevertheless has a clear
- meaning.
- 
-    For example, when writing an `INCLUDE' file that defines a common
- block, it might be appropriate to include a `SAVE' statement for the
- common block (such as `SAVE /CBLOCK/'), so that variables defined in
- the common block retain their values even when all procedures declaring
- the common block become inactive (return to their callers).
- 
-    However, putting `SAVE' statements in an `INCLUDE' file would
- prevent otherwise standard-conforming code from also specifying the
- `SAVE' statement, by itself, to indicate that all local variables and
- arrays are to have the `SAVE' attribute.
- 
-    For this reason, `g77' already has been changed to allow this
- combination, because although the general problem of gratuitously
- rejecting unambiguous and "safe" constructs still exists in `g77', this
- particular construct was deemed useful enough that it was worth fixing
- `g77' for just this case.
- 
-    So, while there is no need to change your code to avoid using this
- particular construct, there might be other, equally appropriate but
- non-standard constructs, that you shouldn't have to stop using just
- because `g77' (or any other compiler) gratuitously rejects it.
- 
-    Until the general problem is solved, if you have any such construct
- you believe is worthwhile using (e.g. not just an arbitrary, redundant
- specification of an attribute), please submit a bug report with an
- explanation, so we can consider fixing `g77' just for cases like yours.
- 
- 
- File: g77.info,  Node: READONLY Keyword,  Next: FLUSH Statement,  Prev: Sensible Non-standard Constructs,  Up: Missing Features
- 
- `READONLY' Keyword
- ------------------
- 
-    Support for `READONLY', in `OPEN' statements, requires `libg2c'
- support, to make sure that `CLOSE(...,STATUS='DELETE')' does not delete
- a file opened on a unit with the `READONLY' keyword, and perhaps to
- trigger a fatal diagnostic if a `WRITE' or `PRINT' to such a unit is
- attempted.
- 
-    _Note:_ It is not sufficient for `g77' and `libg2c' (its version of
- `libf2c') to assume that `READONLY' does not need some kind of explicit
- support at run time, due to UNIX systems not (generally) needing it.
- `g77' is not just a UNIX-based compiler!
- 
-    Further, mounting of non-UNIX filesystems on UNIX systems (such as
- via NFS) might require proper `READONLY' support.
- 
-    (Similar issues might be involved with supporting the `SHARED'
- keyword.)
- 
- 
- File: g77.info,  Node: FLUSH Statement,  Next: Expressions in FORMAT Statements,  Prev: READONLY Keyword,  Up: Missing Features
- 
- `FLUSH' Statement
- -----------------
- 
-    `g77' could perhaps use a `FLUSH' statement that does what `CALL
- FLUSH' does, but that supports `*' as the unit designator (same unit as
- for `PRINT') and accepts `ERR=' and/or `IOSTAT=' specifiers.
- 
- 
- File: g77.info,  Node: Expressions in FORMAT Statements,  Next: Explicit Assembler Code,  Prev: FLUSH Statement,  Up: Missing Features
- 
- Expressions in `FORMAT' Statements
- ----------------------------------
- 
-    `g77' doesn't support `FORMAT(I<J>)' and the like.  Supporting this
- requires a significant redesign or replacement of `libg2c'.
- 
-    However, `g77' does support this construct when the expression is
- constant (as of version 0.5.22).  For example:
- 
-            PARAMETER (IWIDTH = 12)
-      10    FORMAT (I<IWIDTH>)
- 
-    Otherwise, at least for output (`PRINT' and `WRITE'), Fortran code
- making use of this feature can be rewritten to avoid it by constructing
- the `FORMAT' string in a `CHARACTER' variable or array, then using that
- variable or array in place of the `FORMAT' statement label to do the
- original `PRINT' or `WRITE'.
- 
-    Many uses of this feature on input can be rewritten this way as
- well, but not all can.  For example, this can be rewritten:
- 
-            READ 20, I
-      20    FORMAT (I<J>)
- 
-    However, this cannot, in general, be rewritten, especially when
- `ERR=' and `END=' constructs are employed:
- 
-            READ 30, J, I
-      30    FORMAT (I<J>)
- 
- 
- File: g77.info,  Node: Explicit Assembler Code,  Next: Q Edit Descriptor,  Prev: Expressions in FORMAT Statements,  Up: Missing Features
- 
- Explicit Assembler Code
- -----------------------
- 
-    `g77' needs to provide some way, a la `gcc', for `g77' code to
- specify explicit assembler code.
- 
- 
- File: g77.info,  Node: Q Edit Descriptor,  Next: Old-style PARAMETER Statements,  Prev: Explicit Assembler Code,  Up: Missing Features
- 
- Q Edit Descriptor
- -----------------
- 
-    The `Q' edit descriptor in `FORMAT's isn't supported.  (This is
- meant to get the number of characters remaining in an input record.)
- Supporting this requires a significant redesign or replacement of
- `libg2c'.
- 
-    A workaround might be using internal I/O or the stream-based
- intrinsics.  *Note FGetC Intrinsic (subroutine)::.
- 
- 
- File: g77.info,  Node: Old-style PARAMETER Statements,  Next: TYPE and ACCEPT I/O Statements,  Prev: Q Edit Descriptor,  Up: Missing Features
- 
- Old-style PARAMETER Statements
- ------------------------------
- 
-    `g77' doesn't accept `PARAMETER I=1'.  Supporting this obsolete form
- of the `PARAMETER' statement would not be particularly hard, as most of
- the parsing code is already in place and working.
- 
-    Until time/money is spent implementing it, you might as well fix
- your code to use the standard form, `PARAMETER (I=1)' (possibly needing
- `INTEGER I' preceding the `PARAMETER' statement as well, otherwise, in
- the obsolete form of `PARAMETER', the type of the variable is set from
- the type of the constant being assigned to it).
- 
- 
- File: g77.info,  Node: TYPE and ACCEPT I/O Statements,  Next: STRUCTURE UNION RECORD MAP,  Prev: Old-style PARAMETER Statements,  Up: Missing Features
- 
- `TYPE' and `ACCEPT' I/O Statements
- ----------------------------------
- 
-    `g77' doesn't support the I/O statements `TYPE' and `ACCEPT'.  These
- are common extensions that should be easy to support, but also are
- fairly easy to work around in user code.
- 
-    Generally, any `TYPE fmt,list' I/O statement can be replaced by
- `PRINT fmt,list'.  And, any `ACCEPT fmt,list' statement can be replaced
- by `READ fmt,list'.
- 
- 
- File: g77.info,  Node: STRUCTURE UNION RECORD MAP,  Next: OPEN CLOSE and INQUIRE Keywords,  Prev: TYPE and ACCEPT I/O Statements,  Up: Missing Features
- 
- `STRUCTURE', `UNION', `RECORD', `MAP'
- -------------------------------------
- 
-    `g77' doesn't support `STRUCTURE', `UNION', `RECORD', `MAP'.  This
- set of extensions is quite a bit lower on the list of large, important
- things to add to `g77', partly because it requires a great deal of work
- either upgrading or replacing `libg2c'.
- 
- 
- File: g77.info,  Node: OPEN CLOSE and INQUIRE Keywords,  Next: ENCODE and DECODE,  Prev: STRUCTURE UNION RECORD MAP,  Up: Missing Features
- 
- `OPEN', `CLOSE', and `INQUIRE' Keywords
- ---------------------------------------
- 
-    `g77' doesn't have support for keywords such as `DISP='DELETE'' in
- the `OPEN', `CLOSE', and `INQUIRE' statements.  These extensions are
- easy to add to `g77' itself, but require much more work on `libg2c'.
- 
-    `g77' doesn't support `FORM='PRINT'' or an equivalent to translate
- the traditional `carriage control' characters in column 1 of output to
- use backspaces, carriage returns and the like.  However programs exist
- to translate them in output files (or standard output).  These are
- typically called either `fpr' or `asa'.  You can get a version of `asa'
- from `ftp://sunsite.unc.edu/pub/Linux/devel/lang/fortran' for GNU
- systems which will probably build easily on other systems.
- Alternatively, `fpr' is in BSD distributions in various archive sites.
- 
- 
- File: g77.info,  Node: ENCODE and DECODE,  Next: AUTOMATIC Statement,  Prev: OPEN CLOSE and INQUIRE Keywords,  Up: Missing Features
- 
- `ENCODE' and `DECODE'
- ---------------------
- 
-    `g77' doesn't support `ENCODE' or `DECODE'.
- 
-    These statements are best replaced by READ and WRITE statements
- involving internal files (CHARACTER variables and arrays).
- 
-    For example, replace a code fragment like
- 
-            INTEGER*1 LINE(80)
-      ...
-            DECODE (80, 9000, LINE) A, B, C
-      ...
-      9000  FORMAT (1X, 3(F10.5))
- 
- with:
- 
-            CHARACTER*80 LINE
-      ...
-            READ (UNIT=LINE, FMT=9000) A, B, C
-      ...
-      9000  FORMAT (1X, 3(F10.5))
- 
-    Similarly, replace a code fragment like
- 
-            INTEGER*1 LINE(80)
-      ...
-            ENCODE (80, 9000, LINE) A, B, C
-      ...
-      9000  FORMAT (1X, 'OUTPUT IS ', 3(F10.5))
- 
- with:
- 
-            CHARACTER*80 LINE
-      ...
-            WRITE (UNIT=LINE, FMT=9000) A, B, C
-      ...
-      9000  FORMAT (1X, 'OUTPUT IS ', 3(F10.5))
- 
-    It is entirely possible that `ENCODE' and `DECODE' will be supported
- by a future version of `g77'.
- 
- 
- File: g77.info,  Node: AUTOMATIC Statement,  Next: Suppressing Space Padding,  Prev: ENCODE and DECODE,  Up: Missing Features
- 
- `AUTOMATIC' Statement
- ---------------------
- 
-    `g77' doesn't support the `AUTOMATIC' statement that `f2c' does.
- 
-    `AUTOMATIC' would identify a variable or array as not being
- `SAVE''d, which is normally the default, but which would be especially
- useful for code that, _generally_, needed to be compiled with the
- `-fno-automatic' option.
- 
-    `AUTOMATIC' also would serve as a hint to the compiler that placing
- the variable or array--even a very large array-on the stack is
- acceptable.
- 
-    `AUTOMATIC' would not, by itself, designate the containing procedure
- as recursive.
- 
-    `AUTOMATIC' should work syntactically like `SAVE', in that
- `AUTOMATIC' with no variables listed should apply to all pertinent
- variables and arrays (which would not include common blocks or their
- members).
- 
-    Variables and arrays denoted as `AUTOMATIC' would not be permitted
- to be initialized via `DATA' or other specification of any initial
- values, requiring explicit initialization, such as via assignment
- statements.
- 
-    Perhaps `UNSAVE' and `STATIC', as strict semantic opposites to
- `SAVE' and `AUTOMATIC', should be provided as well.
- 
- 
- File: g77.info,  Node: Suppressing Space Padding,  Next: Fortran Preprocessor,  Prev: AUTOMATIC Statement,  Up: Missing Features
- 
- Suppressing Space Padding of Source Lines
- -----------------------------------------
- 
-    `g77' should offer VXT-Fortran-style suppression of virtual spaces
- at the end of a source line if an appropriate command-line option is
- specified.
- 
-    This affects cases where a character constant is continued onto the
- next line in a fixed-form source file, as in the following example:
- 
-      10    PRINT *,'HOW MANY
-           1 SPACES?'
- 
- `g77', and many other compilers, virtually extend the continued line
- through column 72 with spaces that become part of the character
- constant, but Digital Fortran normally didn't, leaving only one space
- between `MANY' and `SPACES?' in the output of the above statement.
- 
-    Fairly recently, at least one version of Digital Fortran was
- enhanced to provide the other behavior when a command-line option is
- specified, apparently due to demand from readers of the USENET group
- `comp.lang.fortran' to offer conformance to this widespread practice in
- the industry.  `g77' should return the favor by offering conformance to
- Digital's approach to handling the above example.
- 
- 
- File: g77.info,  Node: Fortran Preprocessor,  Next: Bit Operations on Floating-point Data,  Prev: Suppressing Space Padding,  Up: Missing Features
- 
- Fortran Preprocessor
- --------------------
- 
-    `g77' should offer a preprocessor designed specifically for Fortran
- to replace `cpp -traditional'.  There are several out there worth
- evaluating, at least.
- 
-    Such a preprocessor would recognize Hollerith constants, properly
- parse comments and character constants, and so on.  It might also
- recognize, process, and thus preprocess files included via the
- `INCLUDE' directive.
- 
- 
- File: g77.info,  Node: Bit Operations on Floating-point Data,  Next: Really Ugly Character Assignments,  Prev: Fortran Preprocessor,  Up: Missing Features
- 
- Bit Operations on Floating-point Data
- -------------------------------------
- 
-    `g77' does not allow `REAL' and other non-integral types for
- arguments to intrinsics like `And', `Or', and `Shift'.
- 
-    For example, this program is rejected by `g77', because the
- intrinsic `Iand' does not accept `REAL' arguments:
- 
-      DATA A/7.54/, B/9.112/
-      PRINT *, IAND(A, B)
-      END
- 
- 
- File: g77.info,  Node: Really Ugly Character Assignments,  Next: POSIX Standard,  Prev: Bit Operations on Floating-point Data,  Up: Missing Features
- 
- Really Ugly Character Assignments
- ---------------------------------
- 
-    An option such as `-fugly-char' should be provided to allow
- 
-      REAL*8 A1
-      DATA A1 / '12345678' /
- 
-    and:
- 
-      REAL*8 A1
-      A1 = 'ABCDEFGH'
- 
- 
- File: g77.info,  Node: POSIX Standard,  Next: Floating-point Exception Handling,  Prev: Really Ugly Character Assignments,  Up: Missing Features
- 
- `POSIX' Standard
- ----------------
- 
-    `g77' should support the POSIX standard for Fortran.
- 
- 
- File: g77.info,  Node: Floating-point Exception Handling,  Next: Nonportable Conversions,  Prev: POSIX Standard,  Up: Missing Features
- 
- Floating-point Exception Handling
- ---------------------------------
- 
-    The `gcc' backend and, consequently, `g77', currently provides no
- general control over whether or not floating-point exceptions are
- trapped or ignored.  (Ignoring them typically results in NaN values
- being propagated in systems that conform to IEEE 754.)  The behaviour
- is normally inherited from the system-dependent startup code, though
- some targets, such as the Alpha, have code generation options which
- change the behaviour.
- 
-    Most systems provide some C-callable mechanism to change this; this
- can be invoked at startup using `gcc''s `constructor' attribute.  For
- example, just compiling and linking the following C code with your
- program will turn on exception trapping for the "common" exceptions on
- a GNU system using glibc 2.2 or newer:
- 
-      #define _GNU_SOURCE 1
-      #include <fenv.h>
-      static void __attribute__ ((constructor))
-      trapfpe ()
-      {
-        /* Enable some exceptions.  At startup all exceptions are masked.  */
-      
-        feenableexcept (FE_INVALID|FE_DIVBYZERO|FE_OVERFLOW);
-      }
- 
-    A convenient trick is to compile this something like:
-      gcc -o libtrapfpe.a trapfpe.c
-    and then use it by adding `-trapfpe' to the `g77' command line when
- linking.
- 
- 
- File: g77.info,  Node: Nonportable Conversions,  Next: Large Automatic Arrays,  Prev: Floating-point Exception Handling,  Up: Missing Features
- 
- Nonportable Conversions
- -----------------------
- 
-    `g77' doesn't accept some particularly nonportable, silent data-type
- conversions such as `LOGICAL' to `REAL' (as in `A=.FALSE.', where `A'
- is type `REAL'), that other compilers might quietly accept.
- 
-    Some of these conversions are accepted by `g77' when the
- `-fugly-logint' option is specified.  Perhaps it should accept more or
- all of them.
- 
- 
- File: g77.info,  Node: Large Automatic Arrays,  Next: Support for Threads,  Prev: Nonportable Conversions,  Up: Missing Features
- 
- Large Automatic Arrays
- ----------------------
- 
-    Currently, automatic arrays always are allocated on the stack.  For
- situations where the stack cannot be made large enough, `g77' should
- offer a compiler option that specifies allocation of automatic arrays
- in heap storage.
- 
- 
- File: g77.info,  Node: Support for Threads,  Next: Increasing Precision/Range,  Prev: Large Automatic Arrays,  Up: Missing Features
- 
- Support for Threads
- -------------------
- 
-    Neither the code produced by `g77' nor the `libg2c' library are
- thread-safe, nor does `g77' have support for parallel processing (other
- than the instruction-level parallelism available on some processors).
- A package such as PVM might help here.
- 
- 
- File: g77.info,  Node: Enabling Debug Lines,  Next: Better Warnings,  Prev: Increasing Precision/Range,  Up: Missing Features
- 
- Enabling Debug Lines
- --------------------
- 
-    An option such as `-fdebug-lines' should be provided to turn
- fixed-form lines beginning with `D' to be treated as if they began with
- a space, instead of as if they began with a `C' (as comment lines).
- 
- 
- File: g77.info,  Node: Better Warnings,  Next: Gracefully Handle Sensible Bad Code,  Prev: Enabling Debug Lines,  Up: Missing Features
- 
- Better Warnings
- ---------------
- 
-    Because of how `g77' generates code via the back end, it doesn't
- always provide warnings the user wants.  Consider:
- 
-      PROGRAM X
-      PRINT *, A
-      END
- 
-    Currently, the above is not flagged as a case of using an
- uninitialized variable, because `g77' generates a run-time library call
- that looks, to the GBE, like it might actually _modify_ `A' at run time.
- (And, in fact, depending on the previous run-time library call, it
- would!)
- 
-    Fixing this requires one of the following:
- 
-    * Switch to new library, `libg77', that provides a more "clean"
-      interface, vis-a-vis input, output, and modified arguments, so the
-      GBE can tell what's going on.
- 
-      This would provide a pretty big performance improvement, at least
-      theoretically, and, ultimately, in practice, for some types of
-      code.
- 
-    * Have `g77' pass a pointer to a temporary containing a copy of `A',
-      instead of to `A' itself.  The GBE would then complain about the
-      copy operation involving a potentially uninitialized variable.
- 
-      This might also provide a performance boost for some code, because
-      `A' might then end up living in a register, which could help with
-      inner loops.
- 
-    * Have `g77' use a GBE construct similar to `ADDR_EXPR' but with
-      extra information on the fact that the item pointed to won't be
-      modified (a la `const' in C).
- 
-      Probably the best solution for now, but not quite trivial to
-      implement in the general case.
- 
- 
- File: g77.info,  Node: Gracefully Handle Sensible Bad Code,  Next: Non-standard Conversions,  Prev: Better Warnings,  Up: Missing Features
- 
- Gracefully Handle Sensible Bad Code
- -----------------------------------
- 
-    `g77' generally should continue processing for warnings and
- recoverable (user) errors whenever possible--that is, it shouldn't
- gratuitously make bad or useless code.
- 
-    For example:
- 
-      INTRINSIC ZABS
-      CALL FOO(ZABS)
-      END
- 
- When compiling the above with `-ff2c-intrinsics-disable', `g77' should
- indeed complain about passing `ZABS', but it still should compile,
- instead of rejecting the entire `CALL' statement.  (Some of this is
- related to improving the compiler internals to improve how statements
- are analyzed.)
- 
- 
- File: g77.info,  Node: Non-standard Conversions,  Next: Non-standard Intrinsics,  Prev: Gracefully Handle Sensible Bad Code,  Up: Missing Features
- 
- Non-standard Conversions
- ------------------------
- 
-    `-Wconversion' and related should flag places where non-standard
- conversions are found.  Perhaps much of this would be part of `-Wugly*'.
- 
- 
- File: g77.info,  Node: Non-standard Intrinsics,  Next: Modifying DO Variable,  Prev: Non-standard Conversions,  Up: Missing Features
- 
- Non-standard Intrinsics
- -----------------------
- 
-    `g77' needs a new option, like `-Wintrinsics', to warn about use of
- non-standard intrinsics without explicit `INTRINSIC' statements for
- them.  This would help find code that might fail silently when ported
- to another compiler.
- 
- 
- File: g77.info,  Node: Modifying DO Variable,  Next: Better Pedantic Compilation,  Prev: Non-standard Intrinsics,  Up: Missing Features
- 
- Modifying `DO' Variable
- -----------------------
- 
-    `g77' should warn about modifying `DO' variables via `EQUIVALENCE'.
- (The internal information gathered to produce this warning might also
- be useful in setting the internal "doiter" flag for a variable or even
- array reference within a loop, since that might produce faster code
- someday.)
- 
-    For example, this code is invalid, so `g77' should warn about the
- invalid assignment to `NOTHER':
- 
-      EQUIVALENCE (I, NOTHER)
-      DO I = 1, 100
-         IF (I.EQ. 10) NOTHER = 20
-      END DO
- 
- 
- File: g77.info,  Node: Better Pedantic Compilation,  Next: Warn About Implicit Conversions,  Prev: Modifying DO Variable,  Up: Missing Features
- 
- Better Pedantic Compilation
- ---------------------------
- 
-    `g77' needs to support `-fpedantic' more thoroughly, and use it only
- to generate warnings instead of rejecting constructs outright.  Have it
- warn: if a variable that dimensions an array is not a dummy or placed
- explicitly in `COMMON' (F77 does not allow it to be placed in `COMMON'
- via `EQUIVALENCE'); if specification statements follow
- statement-function-definition statements; about all sorts of syntactic
- extensions.
- 
- 
- File: g77.info,  Node: Warn About Implicit Conversions,  Next: Invalid Use of Hollerith Constant,  Prev: Better Pedantic Compilation,  Up: Missing Features
- 
- Warn About Implicit Conversions
- -------------------------------
- 
-    `g77' needs a `-Wpromotions' option to warn if source code appears
- to expect automatic, silent, and somewhat dangerous compiler-assisted
- conversion of `REAL(KIND=1)' constants to `REAL(KIND=2)' based on
- context.
- 
-    For example, it would warn about cases like this:
- 
-      DOUBLE PRECISION FOO
-      PARAMETER (TZPHI = 9.435784839284958)
-      FOO = TZPHI * 3D0
- 
- 
- File: g77.info,  Node: Invalid Use of Hollerith Constant,  Next: Dummy Array Without Dimensioning Dummy,  Prev: Warn About Implicit Conversions,  Up: Missing Features
- 
- Invalid Use of Hollerith Constant
- ---------------------------------
- 
-    `g77' should disallow statements like `RETURN 2HAB', which are
- invalid in both source forms (unlike `RETURN (2HAB)', which probably
- still makes no sense but at least can be reliably parsed).  Fixed-form
- processing rejects it, but not free-form, except in a way that is a bit
- difficult to understand.
- 
- 
- File: g77.info,  Node: Dummy Array Without Dimensioning Dummy,  Next: Invalid FORMAT Specifiers,  Prev: Invalid Use of Hollerith Constant,  Up: Missing Features
- 
- Dummy Array Without Dimensioning Dummy
- --------------------------------------
- 
-    `g77' should complain when a list of dummy arguments containing an
- adjustable dummy array does not also contain every variable listed in
- the dimension list of the adjustable array.
- 
-    Currently, `g77' does complain about a variable that dimensions an
- array but doesn't appear in any dummy list or `COMMON' area, but this
- needs to be extended to catch cases where it doesn't appear in every
- dummy list that also lists any arrays it dimensions.
- 
-    For example, `g77' should warn about the entry point `ALT' below,
- since it includes `ARRAY' but not `ISIZE' in its list of arguments:
- 
-      SUBROUTINE PRIMARY(ARRAY, ISIZE)
-      REAL ARRAY(ISIZE)
-      ENTRY ALT(ARRAY)
- 
- 
- File: g77.info,  Node: Invalid FORMAT Specifiers,  Next: Ambiguous Dialects,  Prev: Dummy Array Without Dimensioning Dummy,  Up: Missing Features
- 
- Invalid FORMAT Specifiers
- -------------------------
- 
-    `g77' should check `FORMAT' specifiers for validity as it does
- `FORMAT' statements.
- 
-    For example, a diagnostic would be produced for:
- 
-      PRINT 'HI THERE!'  !User meant PRINT *, 'HI THERE!'
- 
- 
- File: g77.info,  Node: Ambiguous Dialects,  Next: Unused Labels,  Prev: Invalid FORMAT Specifiers,  Up: Missing Features
- 
- Ambiguous Dialects
- ------------------
- 
-    `g77' needs a set of options such as `-Wugly*', `-Wautomatic',
- `-Wvxt', `-Wf90', and so on.  These would warn about places in the
- user's source where ambiguities are found, helpful in resolving
- ambiguities in the program's dialect or dialects.
- 
- 
- File: g77.info,  Node: Unused Labels,  Next: Informational Messages,  Prev: Ambiguous Dialects,  Up: Missing Features
- 
- Unused Labels
- -------------
- 
-    `g77' should warn about unused labels when `-Wunused' is in effect.
- 
- 
- File: g77.info,  Node: Informational Messages,  Next: Uninitialized Variables at Run Time,  Prev: Unused Labels,  Up: Missing Features
- 
- Informational Messages
- ----------------------
- 
-    `g77' needs an option to suppress information messages (notes).
- `-w' does this but also suppresses warnings.  The default should be to
- suppress info messages.
- 
-    Perhaps info messages should simply be eliminated.
- 
- 
- File: g77.info,  Node: Uninitialized Variables at Run Time,  Next: Portable Unformatted Files,  Prev: Informational Messages,  Up: Missing Features
- 
- Uninitialized Variables at Run Time
- -----------------------------------
- 
-    `g77' needs an option to initialize everything (not otherwise
- explicitly initialized) to "weird" (machine-dependent) values, e.g.
- NaNs, bad (non-`NULL') pointers, and largest-magnitude integers, would
- help track down references to some kinds of uninitialized variables at
- run time.
- 
-    Note that use of the options `-O -Wuninitialized' can catch many
- such bugs at compile time.
- 
- 
- File: g77.info,  Node: Portable Unformatted Files,  Next: Better List-directed I/O,  Prev: Uninitialized Variables at Run Time,  Up: Missing Features
- 
- Portable Unformatted Files
- --------------------------
- 
-    `g77' has no facility for exchanging unformatted files with systems
- using different number formats--even differing only in endianness (byte
- order)--or written by other compilers.  Some compilers provide
- facilities at least for doing byte-swapping during unformatted I/O.
- 
-    It is unrealistic to expect to cope with exchanging unformatted files
- with arbitrary other compiler runtimes, but the `g77' runtime should at
- least be able to read files written by `g77' on systems with different
- number formats, particularly if they differ only in byte order.
- 
-    In case you do need to write a program to translate to or from `g77'
- (`libf2c') unformatted files, they are written as follows:
- Sequential
-      Unformatted sequential records consist of
-        1. A number giving the length of the record contents;
- 
-        2. the length of record contents again (for backspace).
- 
-      The record length is of C type `long'; this means that it is 8
-      bytes on 64-bit systems such as Alpha GNU/Linux and 4 bytes on
-      other systems, such as x86 GNU/Linux.  Consequently such files
-      cannot be exchanged between 64-bit and 32-bit systems, even with
-      the same basic number format.
- 
- Direct access
-      Unformatted direct access files form a byte stream of length
-      RECORDS*RECL bytes, where RECORDS is the maximum record number
-      (`REC=RECORDS') written and RECL is the record length in bytes
-      specified in the `OPEN' statement (`RECL=RECL').  Data appear in
-      the records as determined by the relevant `WRITE' statement.
-      Dummy records with arbitrary contents appear in the file in place
-      of records which haven't been written.
- 
-    Thus for exchanging a sequential or direct access unformatted file
- between big- and little-endian 32-bit systems using IEEE 754 floating
- point it would be sufficient to reverse the bytes in consecutive words
- in the file if, and _only_ if, only `REAL*4', `COMPLEX', `INTEGER*4'
- and/or `LOGICAL*4' data have been written to it by `g77'.
- 
-    If necessary, it is possible to do byte-oriented i/o with `g77''s
- `FGETC' and `FPUTC' intrinsics.  Byte-swapping can be done in Fortran
- by equivalencing larger sized variables to an `INTEGER*1' array or a
- set of scalars.
- 
-    If you need to exchange binary data between arbitrary system and
- compiler variations, we recommend using a portable binary format with
- Fortran bindings, such as NCSA's HDF (`http://hdf.ncsa.uiuc.edu/') or
- PACT's PDB(1) (`http://www.llnl.gov/def_sci/pact/pact_homepage.html').
- (Unlike, say, CDF or XDR, HDF-like systems write in the native number
- formats and only incur overhead when they are read on a system with a
- different format.)  A future `g77' runtime library should use such
- techniques.
- 
-    ---------- Footnotes ----------
- 
-    (1) No, not _that_ one.
- 
- 
- File: g77.info,  Node: Better List-directed I/O,  Next: Default to Console I/O,  Prev: Portable Unformatted Files,  Up: Missing Features
- 
- Better List-directed I/O
- ------------------------
- 
-    Values output using list-directed I/O (`PRINT *, R, D') should be
- written with a field width, precision, and so on appropriate for the
- type (precision) of each value.
- 
-    (Currently, no distinction is made between single-precision and
- double-precision values by `libf2c'.)
- 
-    It is likely this item will require the `libg77' project to be
- undertaken.
- 
-    In the meantime, use of formatted I/O is recommended.  While it
- might be of little consolation, `g77' does support
- `FORMAT(F<WIDTH>.4)', for example, as long as `WIDTH' is defined as a
- named constant (via `PARAMETER').  That at least allows some
- compile-time specification of the precision of a data type, perhaps
- controlled by preprocessing directives.
- 
- 
- File: g77.info,  Node: Default to Console I/O,  Next: Labels Visible to Debugger,  Prev: Better List-directed I/O,  Up: Missing Features
- 
- Default to Console I/O
- ----------------------
- 
-    The default I/O units, specified by `READ FMT', `READ (UNIT=*)',
- `WRITE (UNIT=*)', and `PRINT FMT', should not be units 5 (input) and 6
- (output), but, rather, unit numbers not normally available for use in
- statements such as `OPEN' and `CLOSE'.
- 
-    Changing this would allow a program to connect units 5 and 6 to
- files via `OPEN', but still use `READ (UNIT=*)' and `PRINT' to do I/O
- to the "console".
- 
-    This change probably requires the `libg77' project.
- 
- 
- File: g77.info,  Node: Labels Visible to Debugger,  Prev: Default to Console I/O,  Up: Missing Features
- 
- Labels Visible to Debugger
- --------------------------
- 
-    `g77' should output debugging information for statements labels, for
- use by debuggers that know how to support them.  Same with weirder
- things like construct names.  It is not yet known if any debug formats
- or debuggers support these.
- 
- 
- File: g77.info,  Node: Disappointments,  Next: Non-bugs,  Prev: Missing Features,  Up: Trouble
- 
- Disappointments and Misunderstandings
- =====================================
- 
-    These problems are perhaps regrettable, but we don't know any
- practical way around them for now.
- 
- * Menu:
- 
- * Mangling of Names::                       `SUBROUTINE FOO' is given
-                                               external name `foo_'.
- * Multiple Definitions of External Names::  No doing both `COMMON /FOO/'
-                                               and `SUBROUTINE FOO'.
- * Limitation on Implicit Declarations::     No `IMPLICIT CHARACTER*(*)'.
- 
- 
- File: g77.info,  Node: Mangling of Names,  Next: Multiple Definitions of External Names,  Up: Disappointments
- 
- Mangling of Names in Source Code
- --------------------------------
- 
-    The current external-interface design, which includes naming of
- external procedures, COMMON blocks, and the library interface, has
- various usability problems, including things like adding underscores
- where not really necessary (and preventing easier inter-language
- operability) and yet not providing complete namespace freedom for user
- C code linked with Fortran apps (due to the naming of functions in the
- library, among other things).
- 
-    Project GNU should at least get all this "right" for systems it
- fully controls, such as the Hurd, and provide defaults and options for
- compatibility with existing systems and interoperability with popular
- existing compilers.
- 
--- 0 ----
diff -Nrc3pad gcc-3.2.3/gcc/f/g77.info-17 gcc-3.3/gcc/f/g77.info-17
*** gcc-3.2.3/gcc/f/g77.info-17	2003-04-22 07:07:24.000000000 +0000
--- gcc-3.3/gcc/f/g77.info-17	1970-01-01 00:00:00.000000000 +0000
***************
*** 1,1123 ****
- This is g77.info, produced by makeinfo version 4.5 from g77.texi.
- 
- INFO-DIR-SECTION Programming
- START-INFO-DIR-ENTRY
- * g77: (g77).                  The GNU Fortran compiler.
- END-INFO-DIR-ENTRY
-    This file documents the use and the internals of the GNU Fortran
- (`g77') compiler.  It corresponds to the GCC-3.2.3 version of `g77'.
- 
-    Published by the Free Software Foundation 59 Temple Place - Suite 330
- Boston, MA 02111-1307 USA
- 
-    Copyright (C) 1995,1996,1997,1998,1999,2000,2001,2002 Free Software
- Foundation, Inc.
- 
-    Permission is granted to copy, distribute and/or modify this document
- under the terms of the GNU Free Documentation License, Version 1.1 or
- any later version published by the Free Software Foundation; with the
- Invariant Sections being "GNU General Public License" and "Funding Free
- Software", the Front-Cover texts being (a) (see below), and with the
- Back-Cover Texts being (b) (see below).  A copy of the license is
- included in the section entitled "GNU Free Documentation License".
- 
-    (a) The FSF's Front-Cover Text is:
- 
-    A GNU Manual
- 
-    (b) The FSF's Back-Cover Text is:
- 
-    You have freedom to copy and modify this GNU Manual, like GNU
- software.  Copies published by the Free Software Foundation raise
- funds for GNU development.
- 
-    Contributed by James Craig Burley (<craig@jcb-sc.com>).  Inspired by
- a first pass at translating `g77-0.5.16/f/DOC' that was contributed to
- Craig by David Ronis (<ronis@onsager.chem.mcgill.ca>).
- 
- 
- File: g77.info,  Node: Multiple Definitions of External Names,  Next: Limitation on Implicit Declarations,  Prev: Mangling of Names,  Up: Disappointments
- 
- Multiple Definitions of External Names
- --------------------------------------
- 
-    `g77' doesn't allow a common block and an external procedure or
- `BLOCK DATA' to have the same name.  Some systems allow this, but `g77'
- does not, to be compatible with `f2c'.
- 
-    `g77' could special-case the way it handles `BLOCK DATA', since it
- is not compatible with `f2c' in this particular area (necessarily,
- since `g77' offers an important feature here), but it is likely that
- such special-casing would be very annoying to people with programs that
- use `EXTERNAL FOO', with no other mention of `FOO' in the same program
- unit, to refer to external procedures, since the result would be that
- `g77' would treat these references as requests to force-load BLOCK DATA
- program units.
- 
-    In that case, if `g77' modified names of `BLOCK DATA' so they could
- have the same names as `COMMON', users would find that their programs
- wouldn't link because the `FOO' procedure didn't have its name
- translated the same way.
- 
-    (Strictly speaking, `g77' could emit a
- null-but-externally-satisfying definition of `FOO' with its name
- transformed as if it had been a `BLOCK DATA', but that probably invites
- more trouble than it's worth.)
- 
- 
- File: g77.info,  Node: Limitation on Implicit Declarations,  Prev: Multiple Definitions of External Names,  Up: Disappointments
- 
- Limitation on Implicit Declarations
- -----------------------------------
- 
-    `g77' disallows `IMPLICIT CHARACTER*(*)'.  This is not
- standard-conforming.
- 
- 
- File: g77.info,  Node: Non-bugs,  Next: Warnings and Errors,  Prev: Disappointments,  Up: Trouble
- 
- Certain Changes We Don't Want to Make
- =====================================
- 
-    This section lists changes that people frequently request, but which
- we do not make because we think GNU Fortran is better without them.
- 
- * Menu:
- 
- * Backslash in Constants::           Why `'\\'' is a constant that
-                                        is one, not two, characters long.
- * Initializing Before Specifying::   Why `DATA VAR/1/' can't precede
-                                        `COMMON VAR'.
- * Context-Sensitive Intrinsicness::  Why `CALL SQRT' won't work.
- * Context-Sensitive Constants::      Why `9.435784839284958' is a
-                                        single-precision constant,
-                                        and might be interpreted as
-                                        `9.435785' or similar.
- * Equivalence Versus Equality::      Why `.TRUE. .EQ. .TRUE.' won't work.
- * Order of Side Effects::            Why `J = IFUNC() - IFUNC()' might
-                                        not behave as expected.
- 
- 
- File: g77.info,  Node: Backslash in Constants,  Next: Initializing Before Specifying,  Up: Non-bugs
- 
- Backslash in Constants
- ----------------------
- 
-    In the opinion of many experienced Fortran users, `-fno-backslash'
- should be the default, not `-fbackslash', as currently set by `g77'.
- 
-    First of all, you can always specify `-fno-backslash' to turn off
- this processing.
- 
-    Despite not being within the spirit (though apparently within the
- letter) of the ANSI FORTRAN 77 standard, `g77' defaults to
- `-fbackslash' because that is what most UNIX `f77' commands default to,
- and apparently lots of code depends on this feature.
- 
-    This is a particularly troubling issue.  The use of a C construct in
- the midst of Fortran code is bad enough, worse when it makes existing
- Fortran programs stop working (as happens when programs written for
- non-UNIX systems are ported to UNIX systems with compilers that provide
- the `-fbackslash' feature as the default--sometimes with no option to
- turn it off).
- 
-    The author of GNU Fortran wished, for reasons of linguistic purity,
- to make `-fno-backslash' the default for GNU Fortran and thus require
- users of UNIX `f77' and `f2c' to specify `-fbackslash' to get the UNIX
- behavior.
- 
-    However, the realization that `g77' is intended as a replacement for
- _UNIX_ `f77', caused the author to choose to make `g77' as compatible
- with `f77' as feasible, which meant making `-fbackslash' the default.
- 
-    The primary focus on compatibility is at the source-code level, and
- the question became "What will users expect a replacement for `f77' to
- do, by default?"  Although at least one UNIX `f77' does not provide
- `-fbackslash' as a default, it appears that the majority of them do,
- which suggests that the majority of code that is compiled by UNIX `f77'
- compilers expects `-fbackslash' to be the default.
- 
-    It is probably the case that more code exists that would _not_ work
- with `-fbackslash' in force than code that requires it be in force.
- 
-    However, most of _that_ code is not being compiled with `f77', and
- when it is, new build procedures (shell scripts, makefiles, and so on)
- must be set up anyway so that they work under UNIX.  That makes a much
- more natural and safe opportunity for non-UNIX users to adapt their
- build procedures for `g77''s default of `-fbackslash' than would exist
- for the majority of UNIX `f77' users who would have to modify existing,
- working build procedures to explicitly specify `-fbackslash' if that was
- not the default.
- 
-    One suggestion has been to configure the default for `-fbackslash'
- (and perhaps other options as well) based on the configuration of `g77'.
- 
-    This is technically quite straightforward, but will be avoided even
- in cases where not configuring defaults to be dependent on a particular
- configuration greatly inconveniences some users of legacy code.
- 
-    Many users appreciate the GNU compilers because they provide an
- environment that is uniform across machines.  These users would be
- inconvenienced if the compiler treated things like the format of the
- source code differently on certain machines.
- 
-    Occasionally users write programs intended only for a particular
- machine type.  On these occasions, the users would benefit if the GNU
- Fortran compiler were to support by default the same dialect as the
- other compilers on that machine.  But such applications are rare.  And
- users writing a program to run on more than one type of machine cannot
- possibly benefit from this kind of compatibility.  (This is consistent
- with the design goals for `gcc'.  To change them for `g77', you must
- first change them for `gcc'.  Do not ask the maintainers of `g77' to do
- this for you, or to disassociate `g77' from the widely understood, if
- not widely agreed-upon, goals for GNU compilers in general.)
- 
-    This is why GNU Fortran does and will treat backslashes in the same
- fashion on all types of machines (by default).  *Note Direction of
- Language Development::, for more information on this overall philosophy
- guiding the development of the GNU Fortran language.
- 
-    Of course, users strongly concerned about portability should indicate
- explicitly in their build procedures which options are expected by
- their source code, or write source code that has as few such
- expectations as possible.
- 
-    For example, avoid writing code that depends on backslash (`\')
- being interpreted either way in particular, such as by starting a
- program unit with:
- 
-      CHARACTER BACKSL
-      PARAMETER (BACKSL = '\\')
- 
- Then, use concatenation of `BACKSL' anyplace a backslash is desired.
- In this way, users can write programs which have the same meaning in
- many Fortran dialects.
- 
-    (However, this technique does not work for Hollerith constants--which
- is just as well, since the only generally portable uses for Hollerith
- constants are in places where character constants can and should be
- used instead, for readability.)
- 
- 
- File: g77.info,  Node: Initializing Before Specifying,  Next: Context-Sensitive Intrinsicness,  Prev: Backslash in Constants,  Up: Non-bugs
- 
- Initializing Before Specifying
- ------------------------------
- 
-    `g77' does not allow `DATA VAR/1/' to appear in the source code
- before `COMMON VAR', `DIMENSION VAR(10)', `INTEGER VAR', and so on.  In
- general, `g77' requires initialization of a variable or array to be
- specified _after_ all other specifications of attributes (type, size,
- placement, and so on) of that variable or array are specified (though
- _confirmation_ of data type is permitted).
- 
-    It is _possible_ `g77' will someday allow all of this, even though
- it is not allowed by the FORTRAN 77 standard.
- 
-    Then again, maybe it is better to have `g77' always require
- placement of `DATA' so that it can possibly immediately write constants
- to the output file, thus saving time and space.
- 
-    That is, `DATA A/1000000*1/' should perhaps always be immediately
- writable to canonical assembler, unless it's already known to be in a
- `COMMON' area following as-yet-uninitialized stuff, and to do this it
- cannot be followed by `COMMON A'.
- 
- 
- File: g77.info,  Node: Context-Sensitive Intrinsicness,  Next: Context-Sensitive Constants,  Prev: Initializing Before Specifying,  Up: Non-bugs
- 
- Context-Sensitive Intrinsicness
- -------------------------------
- 
-    `g77' treats procedure references to _possible_ intrinsic names as
- always enabling their intrinsic nature, regardless of whether the
- _form_ of the reference is valid for that intrinsic.
- 
-    For example, `CALL SQRT' is interpreted by `g77' as an invalid
- reference to the `SQRT' intrinsic function, because the reference is a
- subroutine invocation.
- 
-    First, `g77' recognizes the statement `CALL SQRT' as a reference to
- a _procedure_ named `SQRT', not to a _variable_ with that name (as it
- would for a statement such as `V = SQRT').
- 
-    Next, `g77' establishes that, in the program unit being compiled,
- `SQRT' is an intrinsic--not a subroutine that happens to have the same
- name as an intrinsic (as would be the case if, for example, `EXTERNAL
- SQRT' was present).
- 
-    Finally, `g77' recognizes that the _form_ of the reference is
- invalid for that particular intrinsic.  That is, it recognizes that it
- is invalid for an intrinsic _function_, such as `SQRT', to be invoked as
- a _subroutine_.
- 
-    At that point, `g77' issues a diagnostic.
- 
-    Some users claim that it is "obvious" that `CALL SQRT' references an
- external subroutine of their own, not an intrinsic function.
- 
-    However, `g77' knows about intrinsic subroutines, not just
- functions, and is able to support both having the same names, for
- example.
- 
-    As a result of this, `g77' rejects calls to intrinsics that are not
- subroutines, and function invocations of intrinsics that are not
- functions, just as it (and most compilers) rejects invocations of
- intrinsics with the wrong number (or types) of arguments.
- 
-    So, use the `EXTERNAL SQRT' statement in a program unit that calls a
- user-written subroutine named `SQRT'.
- 
- 
- File: g77.info,  Node: Context-Sensitive Constants,  Next: Equivalence Versus Equality,  Prev: Context-Sensitive Intrinsicness,  Up: Non-bugs
- 
- Context-Sensitive Constants
- ---------------------------
- 
-    `g77' does not use context to determine the types of constants or
- named constants (`PARAMETER'), except for (non-standard) typeless
- constants such as `'123'O'.
- 
-    For example, consider the following statement:
- 
-      PRINT *, 9.435784839284958 * 2D0
- 
- `g77' will interpret the (truncated) constant `9.435784839284958' as a
- `REAL(KIND=1)', not `REAL(KIND=2)', constant, because the suffix `D0'
- is not specified.
- 
-    As a result, the output of the above statement when compiled by
- `g77' will appear to have "less precision" than when compiled by other
- compilers.
- 
-    In these and other cases, some compilers detect the fact that a
- single-precision constant is used in a double-precision context and
- therefore interpret the single-precision constant as if it was
- _explicitly_ specified as a double-precision constant.  (This has the
- effect of appending _decimal_, not _binary_, zeros to the fractional
- part of the number--producing different computational results.)
- 
-    The reason this misfeature is dangerous is that a slight, apparently
- innocuous change to the source code can change the computational
- results.  Consider:
- 
-      REAL ALMOST, CLOSE
-      DOUBLE PRECISION FIVE
-      PARAMETER (ALMOST = 5.000000000001)
-      FIVE = 5
-      CLOSE = 5.000000000001
-      PRINT *, 5.000000000001 - FIVE
-      PRINT *, ALMOST - FIVE
-      PRINT *, CLOSE - FIVE
-      END
- 
- Running the above program should result in the same value being printed
- three times.  With `g77' as the compiler, it does.
- 
-    However, compiled by many other compilers, running the above program
- would print two or three distinct values, because in two or three of
- the statements, the constant `5.000000000001', which on most systems is
- exactly equal to `5.' when interpreted as a single-precision constant,
- is instead interpreted as a double-precision constant, preserving the
- represented precision.  However, this "clever" promotion of type does
- not extend to variables or, in some compilers, to named constants.
- 
-    Since programmers often are encouraged to replace manifest constants
- or permanently-assigned variables with named constants (`PARAMETER' in
- Fortran), and might need to replace some constants with variables
- having the same values for pertinent portions of code, it is important
- that compilers treat code so modified in the same way so that the
- results of such programs are the same.  `g77' helps in this regard by
- treating constants just the same as variables in terms of determining
- their types in a context-independent way.
- 
-    Still, there is a lot of existing Fortran code that has been written
- to depend on the way other compilers freely interpret constants' types
- based on context, so anything `g77' can do to help flag cases of this
- in such code could be very helpful.
- 
- 
- File: g77.info,  Node: Equivalence Versus Equality,  Next: Order of Side Effects,  Prev: Context-Sensitive Constants,  Up: Non-bugs
- 
- Equivalence Versus Equality
- ---------------------------
- 
-    Use of `.EQ.' and `.NE.' on `LOGICAL' operands is not supported,
- except via `-fugly-logint', which is not recommended except for legacy
- code (where the behavior expected by the _code_ is assumed).
- 
-    Legacy code should be changed, as resources permit, to use `.EQV.'
- and `.NEQV.' instead, as these are permitted by the various Fortran
- standards.
- 
-    New code should never be written expecting `.EQ.' or `.NE.' to work
- if either of its operands is `LOGICAL'.
- 
-    The problem with supporting this "feature" is that there is unlikely
- to be consensus on how it works, as illustrated by the following sample
- program:
- 
-      LOGICAL L,M,N
-      DATA L,M,N /3*.FALSE./
-      IF (L.AND.M.EQ.N) PRINT *,'L.AND.M.EQ.N'
-      END
- 
-    The issue raised by the above sample program is: what is the
- precedence of `.EQ.' (and `.NE.') when applied to `LOGICAL' operands?
- 
-    Some programmers will argue that it is the same as the precedence
- for `.EQ.' when applied to numeric (such as `INTEGER') operands.  By
- this interpretation, the subexpression `M.EQ.N' must be evaluated first
- in the above program, resulting in a program that, when run, does not
- execute the `PRINT' statement.
- 
-    Other programmers will argue that the precedence is the same as the
- precedence for `.EQV.', which is restricted by the standards to
- `LOGICAL' operands.  By this interpretation, the subexpression
- `L.AND.M' must be evaluated first, resulting in a program that _does_
- execute the `PRINT' statement.
- 
-    Assigning arbitrary semantic interpretations to syntactic expressions
- that might legitimately have more than one "obvious" interpretation is
- generally unwise.
- 
-    The creators of the various Fortran standards have done a good job
- in this case, requiring a distinct set of operators (which have their
- own distinct precedence) to compare `LOGICAL' operands.  This
- requirement results in expression syntax with more certain precedence
- (without requiring substantial context), making it easier for
- programmers to read existing code.  `g77' will avoid muddying up
- elements of the Fortran language that were well-designed in the first
- place.
- 
-    (Ask C programmers about the precedence of expressions such as `(a)
- & (b)' and `(a) - (b)'--they cannot even tell you, without knowing more
- context, whether the `&' and `-' operators are infix (binary) or unary!)
- 
-    Most dangerous of all is the fact that, even assuming consensus on
- its meaning, an expression like `L.AND.M.EQ.N', if it is the result of
- a typographical error, doesn't _look_ like it has such a typo.  Even
- experienced Fortran programmers would not likely notice that
- `L.AND.M.EQV.N' was, in fact, intended.
- 
-    So, this is a prime example of a circumstance in which a quality
- compiler diagnoses the code, instead of leaving it up to someone
- debugging it to know to turn on special compiler options that might
- diagnose it.
- 
- 
- File: g77.info,  Node: Order of Side Effects,  Prev: Equivalence Versus Equality,  Up: Non-bugs
- 
- Order of Side Effects
- ---------------------
- 
-    `g77' does not necessarily produce code that, when run, performs
- side effects (such as those performed by function invocations) in the
- same order as in some other compiler--or even in the same order as
- another version, port, or invocation (using different command-line
- options) of `g77'.
- 
-    It is never safe to depend on the order of evaluation of side
- effects.  For example, an expression like this may very well behave
- differently from one compiler to another:
- 
-      J = IFUNC() - IFUNC()
- 
- There is no guarantee that `IFUNC' will be evaluated in any particular
- order.  Either invocation might happen first.  If `IFUNC' returns 5 the
- first time it is invoked, and returns 12 the second time, `J' might end
- up with the value `7', or it might end up with `-7'.
- 
-    Generally, in Fortran, procedures with side-effects intended to be
- visible to the caller are best designed as _subroutines_, not functions.
- Examples of such side-effects include:
- 
-    * The generation of random numbers that are intended to influence
-      return values.
- 
-    * Performing I/O (other than internal I/O to local variables).
- 
-    * Updating information in common blocks.
- 
-    An example of a side-effect that is not intended to be visible to
- the caller is a function that maintains a cache of recently calculated
- results, intended solely to speed repeated invocations of the function
- with identical arguments.  Such a function can be safely used in
- expressions, because if the compiler optimizes away one or more calls
- to the function, operation of the program is unaffected (aside from
- being speeded up).
- 
- 
- File: g77.info,  Node: Warnings and Errors,  Prev: Non-bugs,  Up: Trouble
- 
- Warning Messages and Error Messages
- ===================================
- 
-    The GNU compiler can produce two kinds of diagnostics: errors and
- warnings.  Each kind has a different purpose:
- 
-      _Errors_ report problems that make it impossible to compile your
-      program.  GNU Fortran reports errors with the source file name,
-      line number, and column within the line where the problem is
-      apparent.
- 
-      _Warnings_ report other unusual conditions in your code that
-      _might_ indicate a problem, although compilation can (and does)
-      proceed.  Warning messages also report the source file name, line
-      number, and column information, but include the text `warning:' to
-      distinguish them from error messages.
- 
-    Warnings might indicate danger points where you should check to make
- sure that your program really does what you intend; or the use of
- obsolete features; or the use of nonstandard features of GNU Fortran.
- Many warnings are issued only if you ask for them, with one of the `-W'
- options (for instance, `-Wall' requests a variety of useful warnings).
- 
-    _Note:_ Currently, the text of the line and a pointer to the column
- is printed in most `g77' diagnostics.
- 
-    *Note Options to Request or Suppress Warnings: Warning Options, for
- more detail on these and related command-line options.
- 
- 
- File: g77.info,  Node: Open Questions,  Next: Bugs,  Prev: Trouble,  Up: Top
- 
- Open Questions
- **************
- 
-    Please consider offering useful answers to these questions!
- 
-    * `LOC()' and other intrinsics are probably somewhat misclassified.
-      Is the a need for more precise classification of intrinsics, and
-      if so, what are the appropriate groupings?  Is there a need to
-      individually enable/disable/delete/hide intrinsics from the
-      command line?
- 
- 
- File: g77.info,  Node: Bugs,  Next: Service,  Prev: Open Questions,  Up: Top
- 
- Reporting Bugs
- **************
- 
-    Your bug reports play an essential role in making GNU Fortran
- reliable.
- 
-    When you encounter a problem, the first thing to do is to see if it
- is already known.  *Note Trouble::.  If it isn't known, then you should
- report the problem.
- 
-    Reporting a bug might help you by bringing a solution to your
- problem, or it might not.  (If it does not, look in the service
- directory; see *Note Service::.)  In any case, the principal function
- of a bug report is to help the entire community by making the next
- version of GNU Fortran work better.  Bug reports are your contribution
- to the maintenance of GNU Fortran.
- 
-    Since the maintainers are very overloaded, we cannot respond to every
- bug report.  However, if the bug has not been fixed, we are likely to
- send you a patch and ask you to tell us whether it works.
- 
-    In order for a bug report to serve its purpose, you must include the
- information that makes for fixing the bug.
- 
- * Menu:
- 
- * Criteria: Bug Criteria.    Have you really found a bug?
- * Where: Bug Lists.          Where to send your bug report.
- * Reporting: Bug Reporting.  How to report a bug effectively.
- 
-    *Note Known Causes of Trouble with GNU Fortran: Trouble, for
- information on problems we already know about.
- 
-    *Note How To Get Help with GNU Fortran: Service, for information on
- where to ask for help.
- 
- 
- File: g77.info,  Node: Bug Criteria,  Next: Bug Lists,  Up: Bugs
- 
- Have You Found a Bug?
- =====================
- 
-    If you are not sure whether you have found a bug, here are some
- guidelines:
- 
-    * If the compiler gets a fatal signal, for any input whatever, that
-      is a compiler bug.  Reliable compilers never crash--they just
-      remain obsolete.
- 
-    * If the compiler produces invalid assembly code, for any input
-      whatever, that is a compiler bug, unless the compiler reports
-      errors (not just warnings) which would ordinarily prevent the
-      assembler from being run.
- 
-    * If the compiler produces valid assembly code that does not
-      correctly execute the input source code, that is a compiler bug.
- 
-      However, you must double-check to make sure, because you might
-      have run into an incompatibility between GNU Fortran and
-      traditional Fortran.  These incompatibilities might be considered
-      bugs, but they are inescapable consequences of valuable features.
- 
-      Or you might have a program whose behavior is undefined, which
-      happened by chance to give the desired results with another
-      Fortran compiler.  It is best to check the relevant Fortran
-      standard thoroughly if it is possible that the program indeed does
-      something undefined.
- 
-      After you have localized the error to a single source line, it
-      should be easy to check for these things.  If your program is
-      correct and well defined, you have found a compiler bug.
- 
-      It might help if, in your submission, you identified the specific
-      language in the relevant Fortran standard that specifies the
-      desired behavior, if it isn't likely to be obvious and agreed-upon
-      by all Fortran users.
- 
-    * If the compiler produces an error message for valid input, that is
-      a compiler bug.
- 
-    * If the compiler does not produce an error message for invalid
-      input, that is a compiler bug.  However, you should note that your
-      idea of "invalid input" might be someone else's idea of "an
-      extension" or "support for traditional practice".
- 
-    * If you are an experienced user of Fortran compilers, your
-      suggestions for improvement of GNU Fortran are welcome in any case.
- 
-    Many, perhaps most, bug reports against `g77' turn out to be bugs in
- the user's code.  While we find such bug reports educational, they
- sometimes take a considerable amount of time to track down or at least
- respond to--time we could be spending making `g77', not some user's
- code, better.
- 
-    Some steps you can take to verify that the bug is not certainly in
- the code you're compiling with `g77':
- 
-    * Compile your code using the `g77' options `-W -Wall -O'.  These
-      options enable many useful warning; the `-O' option enables flow
-      analysis that enables the uninitialized-variable warning.
- 
-      If you investigate the warnings and find evidence of possible bugs
-      in your code, fix them first and retry `g77'.
- 
-    * Compile your code using the `g77' options `-finit-local-zero',
-      `-fno-automatic', `-ffloat-store', and various combinations
-      thereof.
- 
-      If your code works with any of these combinations, that is not
-      proof that the bug isn't in `g77'--a `g77' bug exposed by your
-      code might simply be avoided, or have a different, more subtle
-      effect, when different options are used--but it can be a strong
-      indicator that your code is making unwarranted assumptions about
-      the Fortran dialect and/or underlying machine it is being compiled
-      and run on.
- 
-      *Note Overly Convenient Command-Line Options: Overly Convenient
-      Options, for information on the `-fno-automatic' and
-      `-finit-local-zero' options and how to convert their use into
-      selective changes in your own code.
- 
-    * Validate your code with `ftnchek' or a similar code-checking tool.
-      `ftnchek' can be found at `ftp://ftp.netlib.org/fortran' or
-      `ftp://ftp.dsm.fordham.edu'.
- 
-      Here are some sample `Makefile' rules using `ftnchek' "project"
-      files to do cross-file checking and `sfmakedepend' (from
-      `ftp://ahab.rutgers.edu/pub/perl/sfmakedepend') to maintain
-      dependencies automatically.  These assume the use of GNU `make'.
- 
-           # Dummy suffix for ftnchek targets:
-           .SUFFIXES: .chek
-           .PHONY: chekall
-           
-           # How to compile .f files (for implicit rule):
-           FC = g77
-           # Assume `include' directory:
-           FFLAGS = -Iinclude -g -O -Wall
-           
-           # Flags for ftnchek:
-           CHEK1 = -array=0 -include=includes -noarray
-           CHEK2 = -nonovice -usage=1 -notruncation
-           CHEKFLAGS = $(CHEK1) $(CHEK2)
-           
-           # Run ftnchek with all the .prj files except the one corresponding
-           # to the target's root:
-           %.chek : %.f ; \
-             ftnchek $(filter-out $*.prj,$(PRJS)) $(CHEKFLAGS) \
-               -noextern -library $<
-           
-           # Derive a project file from a source file:
-           %.prj : %.f ; \
-             ftnchek $(CHEKFLAGS) -noextern -project -library $<
-           
-           # The list of objects is assumed to be in variable OBJS.
-           # Sources corresponding to the objects:
-           SRCS = $(OBJS:%.o=%.f)
-           # ftnchek project files:
-           PRJS = $(OBJS:%.o=%.prj)
-           
-           # Build the program
-           prog: $(OBJS) ; \
-             $(FC) -o $ $(OBJS)
-           
-           chekall: $(PRJS) ; \
-             ftnchek $(CHEKFLAGS) $(PRJS)
-           
-           prjs: $(PRJS)
-           
-           # For Emacs M-x find-tag:
-           TAGS: $(SRCS) ; \
-             etags $(SRCS)
-           
-           # Rebuild dependencies:
-           depend: ; \
-             sfmakedepend -I $(PLTLIBDIR) -I includes -a prj $(SRCS1)
- 
-    * Try your code out using other Fortran compilers, such as `f2c'.
-      If it does not work on at least one other compiler (assuming the
-      compiler supports the features the code needs), that is a strong
-      indicator of a bug in the code.
- 
-      However, even if your code works on many compilers _except_ `g77',
-      that does _not_ mean the bug is in `g77'.  It might mean the bug
-      is in your code, and that `g77' simply exposes it more readily
-      than other compilers.
- 
- 
- File: g77.info,  Node: Bug Lists,  Next: Bug Reporting,  Prev: Bug Criteria,  Up: Bugs
- 
- Where to Report Bugs
- ====================
- 
-    Send bug reports for GNU Fortran to <gcc-bugs@gcc.gnu.org or
- bug-gcc@gnu.org>.
- 
-    Often people think of posting bug reports to a newsgroup instead of
- mailing them.  This sometimes appears to work, but it has one problem
- which can be crucial: a newsgroup posting does not contain a mail path
- back to the sender.  Thus, if maintainers need more information, they
- might be unable to reach you.  For this reason, you should always send
- bug reports by mail to the proper mailing list.
- 
-    As a last resort, send bug reports on paper to:
- 
-      GNU Compiler Bugs
-      Free Software Foundation
-      59 Temple Place - Suite 330
-      Boston, MA 02111-1307, USA
- 
- 
- File: g77.info,  Node: Bug Reporting,  Prev: Bug Lists,  Up: Bugs
- 
- How to Report Bugs
- ==================
- 
-    The fundamental principle of reporting bugs usefully is this:
- *report all the facts*.  If you are not sure whether to state a fact or
- leave it out, state it!
- 
-    Often people omit facts because they think they know what causes the
- problem and they conclude that some details don't matter.  Thus, you
- might assume that the name of the variable you use in an example does
- not matter.  Well, probably it doesn't, but one cannot be sure.
- Perhaps the bug is a stray memory reference which happens to fetch from
- the location where that name is stored in memory; perhaps, if the name
- were different, the contents of that location would fool the compiler
- into doing the right thing despite the bug.  Play it safe and give a
- specific, complete example.  That is the easiest thing for you to do,
- and the most helpful.
- 
-    Keep in mind that the purpose of a bug report is to enable someone to
- fix the bug if it is not known.  It isn't very important what happens if
- the bug is already known.  Therefore, always write your bug reports on
- the assumption that the bug is not known.
- 
-    Sometimes people give a few sketchy facts and ask, "Does this ring a
- bell?"  This cannot help us fix a bug, so it is rarely helpful.  We
- respond by asking for enough details to enable us to investigate.  You
- might as well expedite matters by sending them to begin with.
- (Besides, there are enough bells ringing around here as it is.)
- 
-    Try to make your bug report self-contained.  If we have to ask you
- for more information, it is best if you include all the previous
- information in your response, as well as the information that was
- missing.
- 
-    Please report each bug in a separate message.  This makes it easier
- for us to track which bugs have been fixed and to forward your bugs
- reports to the appropriate maintainer.
- 
-    Do not compress and encode any part of your bug report using programs
- such as `uuencode'.  If you do so it will slow down the processing of
- your bug.  If you must submit multiple large files, use `shar', which
- allows us to read your message without having to run any decompression
- programs.
- 
-    (As a special exception for GNU Fortran bug-reporting, at least for
- now, if you are sending more than a few lines of code, if your
- program's source file format contains "interesting" things like
- trailing spaces or strange characters, or if you need to include binary
- data files, it is acceptable to put all the files together in a `tar'
- archive, and, whether you need to do that, it is acceptable to then
- compress the single file (`tar' archive or source file) using `gzip'
- and encode it via `uuencode'.  Do not use any MIME stuff--the current
- maintainer can't decode this.  Using `compress' instead of `gzip' is
- acceptable, assuming you have licensed the use of the patented
- algorithm in `compress' from Unisys.)
- 
-    To enable someone to investigate the bug, you should include all
- these things:
- 
-    * The version of GNU Fortran.  You can get this by running `g77'
-      with the `-v' option.  (Ignore any error messages that might be
-      displayed when the linker is run.)
- 
-      Without this, we won't know whether there is any point in looking
-      for the bug in the current version of GNU Fortran.
- 
-    * A complete input file that will reproduce the bug.
- 
-      If your source file(s) require preprocessing (for example, their
-      names have suffixes like `.F', `.fpp', `.FPP', and `.r'), and the
-      bug is in the compiler proper (`f771') or in a subsequent phase of
-      processing, run your source file through the C preprocessor by
-      doing `g77 -E SOURCEFILE > NEWFILE'.  Then, include the contents
-      of NEWFILE in the bug report.  (When you do this, use the same
-      preprocessor options--such as `-I', `-D', and `-U'--that you used
-      in actual compilation.)
- 
-      A single statement is not enough of an example.  In order to
-      compile it, it must be embedded in a complete file of compiler
-      input.  The bug might depend on the details of how this is done.
- 
-      Without a real example one can compile, all anyone can do about
-      your bug report is wish you luck.  It would be futile to try to
-      guess how to provoke the bug.  For example, bugs in register
-      allocation and reloading can depend on every little detail of the
-      source and include files that trigger them.
- 
-    * Note that you should include with your bug report any files
-      included by the source file (via the `#include' or `INCLUDE'
-      directive) that you send, and any files they include, and so on.
- 
-      It is not necessary to replace the `#include' and `INCLUDE'
-      directives with the actual files in the version of the source file
-      that you send, but it might make submitting the bug report easier
-      in the end.  However, be sure to _reproduce_ the bug using the
-      _exact_ version of the source material you submit, to avoid
-      wild-goose chases.
- 
-    * The command arguments you gave GNU Fortran to compile that example
-      and observe the bug.  For example, did you use `-O'?  To guarantee
-      you won't omit something important, list all the options.
- 
-      If we were to try to guess the arguments, we would probably guess
-      wrong and then we would not encounter the bug.
- 
-    * The type of machine you are using, and the operating system name
-      and version number.  (Much of this information is printed by `g77
-      -v'--if you include that, send along any additional info you have
-      that you don't see clearly represented in that output.)
- 
-    * The operands you gave to the `configure' command when you installed
-      the compiler.
- 
-    * A complete list of any modifications you have made to the compiler
-      source.  (We don't promise to investigate the bug unless it
-      happens in an unmodified compiler.  But if you've made
-      modifications and don't tell us, then you are sending us on a
-      wild-goose chase.)
- 
-      Be precise about these changes.  A description in English is not
-      enough--send a context diff for them.
- 
-      Adding files of your own (such as a machine description for a
-      machine we don't support) is a modification of the compiler source.
- 
-    * Details of any other deviations from the standard procedure for
-      installing GNU Fortran.
- 
-    * A description of what behavior you observe that you believe is
-      incorrect.  For example, "The compiler gets a fatal signal," or,
-      "The assembler instruction at line 208 in the output is incorrect."
- 
-      Of course, if the bug is that the compiler gets a fatal signal,
-      then one can't miss it.  But if the bug is incorrect output, the
-      maintainer might not notice unless it is glaringly wrong.  None of
-      us has time to study all the assembler code from a 50-line Fortran
-      program just on the chance that one instruction might be wrong.
-      We need _you_ to do this part!
- 
-      Even if the problem you experience is a fatal signal, you should
-      still say so explicitly.  Suppose something strange is going on,
-      such as, your copy of the compiler is out of synch, or you have
-      encountered a bug in the C library on your system.  (This has
-      happened!)  Your copy might crash and the copy here would not.  If
-      you said to expect a crash, then when the compiler here fails to
-      crash, we would know that the bug was not happening.  If you don't
-      say to expect a crash, then we would not know whether the bug was
-      happening.  We would not be able to draw any conclusion from our
-      observations.
- 
-      If the problem is a diagnostic when building GNU Fortran with some
-      other compiler, say whether it is a warning or an error.
- 
-      Often the observed symptom is incorrect output when your program
-      is run.  Sad to say, this is not enough information unless the
-      program is short and simple.  None of us has time to study a large
-      program to figure out how it would work if compiled correctly,
-      much less which line of it was compiled wrong.  So you will have
-      to do that.  Tell us which source line it is, and what incorrect
-      result happens when that line is executed.  A person who
-      understands the program can find this as easily as finding a bug
-      in the program itself.
- 
-    * If you send examples of assembler code output from GNU Fortran,
-      please use `-g' when you make them.  The debugging information
-      includes source line numbers which are essential for correlating
-      the output with the input.
- 
-    * If you wish to mention something in the GNU Fortran source, refer
-      to it by context, not by line number.
- 
-      The line numbers in the development sources don't match those in
-      your sources.  Your line numbers would convey no convenient
-      information to the maintainers.
- 
-    * Additional information from a debugger might enable someone to
-      find a problem on a machine which he does not have available.
-      However, you need to think when you collect this information if
-      you want it to have any chance of being useful.
- 
-      For example, many people send just a backtrace, but that is never
-      useful by itself.  A simple backtrace with arguments conveys little
-      about GNU Fortran because the compiler is largely data-driven; the
-      same functions are called over and over for different RTL insns,
-      doing different things depending on the details of the insn.
- 
-      Most of the arguments listed in the backtrace are useless because
-      they are pointers to RTL list structure.  The numeric values of the
-      pointers, which the debugger prints in the backtrace, have no
-      significance whatever; all that matters is the contents of the
-      objects they point to (and most of the contents are other such
-      pointers).
- 
-      In addition, most compiler passes consist of one or more loops that
-      scan the RTL insn sequence.  The most vital piece of information
-      about such a loop--which insn it has reached--is usually in a
-      local variable, not in an argument.
- 
-      What you need to provide in addition to a backtrace are the values
-      of the local variables for several stack frames up.  When a local
-      variable or an argument is an RTX, first print its value and then
-      use the GDB command `pr' to print the RTL expression that it points
-      to.  (If GDB doesn't run on your machine, use your debugger to call
-      the function `debug_rtx' with the RTX as an argument.)  In
-      general, whenever a variable is a pointer, its value is no use
-      without the data it points to.
- 
-    Here are some things that are not necessary:
- 
-    * A description of the envelope of the bug.
- 
-      Often people who encounter a bug spend a lot of time investigating
-      which changes to the input file will make the bug go away and which
-      changes will not affect it.
- 
-      This is often time consuming and not very useful, because the way
-      we will find the bug is by running a single example under the
-      debugger with breakpoints, not by pure deduction from a series of
-      examples.  You might as well save your time for something else.
- 
-      Of course, if you can find a simpler example to report _instead_ of
-      the original one, that is a convenience.  Errors in the output
-      will be easier to spot, running under the debugger will take less
-      time, etc.  Most GNU Fortran bugs involve just one function, so
-      the most straightforward way to simplify an example is to delete
-      all the function definitions except the one where the bug occurs.
-      Those earlier in the file may be replaced by external declarations
-      if the crucial function depends on them.  (Exception: inline
-      functions might affect compilation of functions defined later in
-      the file.)
- 
-      However, simplification is not vital; if you don't want to do this,
-      report the bug anyway and send the entire test case you used.
- 
-    * In particular, some people insert conditionals `#ifdef BUG' around
-      a statement which, if removed, makes the bug not happen.  These
-      are just clutter; we won't pay any attention to them anyway.
-      Besides, you should send us preprocessor output, and that can't
-      have conditionals.
- 
-    * A patch for the bug.
- 
-      A patch for the bug is useful if it is a good one.  But don't omit
-      the necessary information, such as the test case, on the
-      assumption that a patch is all we need.  We might see problems
-      with your patch and decide to fix the problem another way, or we
-      might not understand it at all.
- 
-      Sometimes with a program as complicated as GNU Fortran it is very
-      hard to construct an example that will make the program follow a
-      certain path through the code.  If you don't send the example, we
-      won't be able to construct one, so we won't be able to verify that
-      the bug is fixed.
- 
-      And if we can't understand what bug you are trying to fix, or why
-      your patch should be an improvement, we won't install it.  A test
-      case will help us to understand.
- 
-      See `http://gcc.gnu.org/contribute.html' for guidelines on how to
-      make it easy for us to understand and install your patches.
- 
-    * A guess about what the bug is or what it depends on.
- 
-      Such guesses are usually wrong.  Even the maintainer can't guess
-      right about such things without first using the debugger to find
-      the facts.
- 
-    * A core dump file.
- 
-      We have no way of examining a core dump for your type of machine
-      unless we have an identical system--and if we do have one, we
-      should be able to reproduce the crash ourselves.
- 
- 
- File: g77.info,  Node: Service,  Next: Adding Options,  Prev: Bugs,  Up: Top
- 
- How To Get Help with GNU Fortran
- ********************************
- 
-    If you need help installing, using or changing GNU Fortran, there
- are two ways to find it:
- 
-    * Look in the service directory for someone who might help you for a
-      fee.  The service directory is found in the file named `SERVICE'
-      in the GNU CC distribution.
- 
-    * Send a message to <gcc-help@gcc.gnu.org>.
- 
- 
- File: g77.info,  Node: Adding Options,  Next: Projects,  Prev: Service,  Up: Top
- 
- Adding Options
- **************
- 
-    To add a new command-line option to `g77', first decide what kind of
- option you wish to add.  Search the `g77' and `gcc' documentation for
- one or more options that is most closely like the one you want to add
- (in terms of what kind of effect it has, and so on) to help clarify its
- nature.
- 
-    * _Fortran options_ are options that apply only when compiling
-      Fortran programs.  They are accepted by `g77' and `gcc', but they
-      apply only when compiling Fortran programs.
- 
-    * _Compiler options_ are options that apply when compiling most any
-      kind of program.
- 
-    _Fortran options_ are listed in the file `gcc/gcc/f/lang-options.h',
- which is used during the build of `gcc' to build a list of all options
- that are accepted by at least one language's compiler.  This list goes
- into the `documented_lang_options' array in `gcc/toplev.c', which uses
- this array to determine whether a particular option should be offered
- to the linked-in front end for processing by calling
- `lang_option_decode', which, for `g77', is in `gcc/gcc/f/com.c' and just
- calls `ffe_decode_option'.
- 
-    If the linked-in front end "rejects" a particular option passed to
- it, `toplev.c' just ignores the option, because _some_ language's
- compiler is willing to accept it.
- 
-    This allows commands like `gcc -fno-asm foo.c bar.f' to work, even
- though Fortran compilation does not currently support the `-fno-asm'
- option; even though the `f771' version of `lang_decode_option' rejects
- `-fno-asm', `toplev.c' doesn't produce a diagnostic because some other
- language (C) does accept it.
- 
-    This also means that commands like `g77 -fno-asm foo.f' yield no
- diagnostics, despite the fact that no phase of the command was able to
- recognize and process `-fno-asm'--perhaps a warning about this would be
- helpful if it were possible.
- 
-    Code that processes Fortran options is found in `gcc/gcc/f/top.c',
- function `ffe_decode_option'.  This code needs to check positive and
- negative forms of each option.
- 
-    The defaults for Fortran options are set in their global
- definitions, also found in `gcc/gcc/f/top.c'.  Many of these defaults
- are actually macros defined in `gcc/gcc/f/target.h', since they might be
- machine-specific.  However, since, in practice, GNU compilers should
- behave the same way on all configurations (especially when it comes to
- language constructs), the practice of setting defaults in `target.h' is
- likely to be deprecated and, ultimately, stopped in future versions of
- `g77'.
- 
-    Accessor macros for Fortran options, used by code in the `g77' FFE,
- are defined in `gcc/gcc/f/top.h'.
- 
-    _Compiler options_ are listed in `gcc/toplev.c' in the array
- `f_options'.  An option not listed in `lang_options' is looked up in
- `f_options' and handled from there.
- 
-    The defaults for compiler options are set in the global definitions
- for the corresponding variables, some of which are in `gcc/toplev.c'.
- 
-    You can set different defaults for _Fortran-oriented_ or
- _Fortran-reticent_ compiler options by changing the source code of
- `g77' and rebuilding.  How to do this depends on the version of `g77':
- 
- `G77 0.5.24 (EGCS 1.1)'
- `G77 0.5.25 (EGCS 1.2 - which became GCC 2.95)'
-      Change the `lang_init_options' routine in `gcc/gcc/f/com.c'.
- 
-      (Note that these versions of `g77' perform internal consistency
-      checking automatically when the `-fversion' option is specified.)
- 
- `G77 0.5.23'
- `G77 0.5.24 (EGCS 1.0)'
-      Change the way `f771' handles the `-fset-g77-defaults' option,
-      which is always provided as the first option when called by `g77'
-      or `gcc'.
- 
-      This code is in `ffe_decode_options' in `gcc/gcc/f/top.c'.  Have
-      it change just the variables that you want to default to a
-      different setting for Fortran compiles compared to compiles of
-      other languages.
- 
-      The `-fset-g77-defaults' option is passed to `f771' automatically
-      because of the specification information kept in
-      `gcc/gcc/f/lang-specs.h'.  This file tells the `gcc' command how
-      to recognize, in this case, Fortran source files (those to be
-      preprocessed, and those that are not), and further, how to invoke
-      the appropriate programs (including `f771') to process those
-      source files.
- 
-      It is in `gcc/gcc/f/lang-specs.h' that `-fset-g77-defaults',
-      `-fversion', and other options are passed, as appropriate, even
-      when the user has not explicitly specified them.  Other "internal"
-      options such as `-quiet' also are passed via this mechanism.
- 
- 
- File: g77.info,  Node: Projects,  Next: Front End,  Prev: Adding Options,  Up: Top
- 
- Projects
- ********
- 
-    If you want to contribute to `g77' by doing research, design,
- specification, documentation, coding, or testing, the following
- information should give you some ideas.  More relevant information
- might be available from `ftp://alpha.gnu.org/gnu/g77/projects/'.
- 
- * Menu:
- 
- * Efficiency::               Make `g77' itself compile code faster.
- * Better Optimization::      Teach `g77' to generate faster code.
- * Simplify Porting::         Make `g77' easier to configure, build,
-                              and install.
- * More Extensions::          Features many users won't know to ask for.
- * Machine Model::            `g77' should better leverage `gcc'.
- * Internals Documentation::  Make maintenance easier.
- * Internals Improvements::   Make internals more robust.
- * Better Diagnostics::       Make using `g77' on new code easier.
- 
--- 0 ----
diff -Nrc3pad gcc-3.2.3/gcc/f/g77.info-18 gcc-3.3/gcc/f/g77.info-18
*** gcc-3.2.3/gcc/f/g77.info-18	2003-04-22 07:07:25.000000000 +0000
--- gcc-3.3/gcc/f/g77.info-18	1970-01-01 00:00:00.000000000 +0000
***************
*** 1,1051 ****
- This is g77.info, produced by makeinfo version 4.5 from g77.texi.
- 
- INFO-DIR-SECTION Programming
- START-INFO-DIR-ENTRY
- * g77: (g77).                  The GNU Fortran compiler.
- END-INFO-DIR-ENTRY
-    This file documents the use and the internals of the GNU Fortran
- (`g77') compiler.  It corresponds to the GCC-3.2.3 version of `g77'.
- 
-    Published by the Free Software Foundation 59 Temple Place - Suite 330
- Boston, MA 02111-1307 USA
- 
-    Copyright (C) 1995,1996,1997,1998,1999,2000,2001,2002 Free Software
- Foundation, Inc.
- 
-    Permission is granted to copy, distribute and/or modify this document
- under the terms of the GNU Free Documentation License, Version 1.1 or
- any later version published by the Free Software Foundation; with the
- Invariant Sections being "GNU General Public License" and "Funding Free
- Software", the Front-Cover texts being (a) (see below), and with the
- Back-Cover Texts being (b) (see below).  A copy of the license is
- included in the section entitled "GNU Free Documentation License".
- 
-    (a) The FSF's Front-Cover Text is:
- 
-    A GNU Manual
- 
-    (b) The FSF's Back-Cover Text is:
- 
-    You have freedom to copy and modify this GNU Manual, like GNU
- software.  Copies published by the Free Software Foundation raise
- funds for GNU development.
- 
-    Contributed by James Craig Burley (<craig@jcb-sc.com>).  Inspired by
- a first pass at translating `g77-0.5.16/f/DOC' that was contributed to
- Craig by David Ronis (<ronis@onsager.chem.mcgill.ca>).
- 
- 
- File: g77.info,  Node: Efficiency,  Next: Better Optimization,  Up: Projects
- 
- Improve Efficiency
- ==================
- 
-    Don't bother doing any performance analysis until most of the
- following items are taken care of, because there's no question they
- represent serious space/time problems, although some of them show up
- only given certain kinds of (popular) input.
- 
-    * Improve `malloc' package and its uses to specify more info about
-      memory pools and, where feasible, use obstacks to implement them.
- 
-    * Skip over uninitialized portions of aggregate areas (arrays,
-      `COMMON' areas, `EQUIVALENCE' areas) so zeros need not be output.
-      This would reduce memory usage for large initialized aggregate
-      areas, even ones with only one initialized element.
- 
-      As of version 0.5.18, a portion of this item has already been
-      accomplished.
- 
-    * Prescan the statement (in `sta.c') so that the nature of the
-      statement is determined as much as possible by looking entirely at
-      its form, and not looking at any context (previous statements,
-      including types of symbols).  This would allow ripping out of the
-      statement-confirmation, symbol retraction/confirmation, and
-      diagnostic inhibition mechanisms.  Plus, it would result in
-      much-improved diagnostics.  For example, `CALL
-      some-intrinsic(...)', where the intrinsic is not a subroutine
-      intrinsic, would result actual error instead of the
-      unimplemented-statement catch-all.
- 
-    * Throughout `g77', don't pass line/column pairs where a simple
-      `ffewhere' type, which points to the error as much as is desired
-      by the configuration, will do, and don't pass `ffelexToken' types
-      where a simple `ffewhere' type will do.  Then, allow new default
-      configuration of `ffewhere' such that the source line text is not
-      preserved, and leave it to things like Emacs' next-error function
-      to point to them (now that `next-error' supports column, or,
-      perhaps, character-offset, numbers).  The change in calling
-      sequences should improve performance somewhat, as should not
-      having to save source lines.  (Whether this whole item will
-      improve performance is questionable, but it should improve
-      maintainability.)
- 
-    * Handle `DATA (A(I),I=1,1000000)/1000000*2/' more efficiently,
-      especially as regards the assembly output.  Some of this might
-      require improving the back end, but lots of improvement in
-      space/time required in `g77' itself can be fairly easily obtained
-      without touching the back end.  Maybe type-conversion, where
-      necessary, can be speeded up as well in cases like the one shown
-      (converting the `2' into `2.').
- 
-    * If analysis shows it to be worthwhile, optimize `lex.c'.
- 
-    * Consider redesigning `lex.c' to not need any feedback during
-      tokenization, by keeping track of enough parse state on its own.
- 
- 
- File: g77.info,  Node: Better Optimization,  Next: Simplify Porting,  Prev: Efficiency,  Up: Projects
- 
- Better Optimization
- ===================
- 
-    Much of this work should be put off until after `g77' has all the
- features necessary for its widespread acceptance as a useful F77
- compiler.  However, perhaps this work can be done in parallel during
- the feature-adding work.
- 
-    * Do the equivalent of the trick of putting `extern inline' in front
-      of every function definition in `libg2c' and #include'ing the
-      resulting file in `f2c'+`gcc'--that is, inline all
-      run-time-library functions that are at all worth inlining.  (Some
-      of this has already been done, such as for integral
-      exponentiation.)
- 
-    * When doing `CHAR_VAR = CHAR_FUNC(...)', and it's clear that types
-      line up and `CHAR_VAR' is addressable or not a `VAR_DECL', make
-      `CHAR_VAR', not a temporary, be the receiver for `CHAR_FUNC'.
-      (This is now done for `COMPLEX' variables.)
- 
-    * Design and implement Fortran-specific optimizations that don't
-      really belong in the back end, or where the front end needs to
-      give the back end more info than it currently does.
- 
-    * Design and implement a new run-time library interface, with the
-      code going into `libgcc' so no special linking is required to link
-      Fortran programs using standard language features.  This library
-      would speed up lots of things, from I/O (using precompiled formats,
-      doing just one, or, at most, very few, calls for arrays or array
-      sections, and so on) to general computing (array/section
-      implementations of various intrinsics, implementation of commonly
-      performed loops that aren't likely to be optimally compiled
-      otherwise, etc.).
- 
-      Among the important things the library would do are:
- 
-         * Be a one-stop-shop-type library, hence shareable and usable
-           by all, in that what are now library-build-time options in
-           `libg2c' would be moved at least to the `g77' compile phase,
-           if not to finer grains (such as choosing how list-directed
-           I/O formatting is done by default at `OPEN' time, for
-           preconnected units via options or even statements in the main
-           program unit, maybe even on a per-I/O basis with appropriate
-           pragma-like devices).
- 
-    * Probably requiring the new library design, change interface to
-      normally have `COMPLEX' functions return their values in the way
-      `gcc' would if they were declared `__complex__ float', rather than
-      using the mechanism currently used by `CHARACTER' functions
-      (whereby the functions are compiled as returning void and their
-      first arg is a pointer to where to store the result).  (Don't
-      append underscores to external names for `COMPLEX' functions in
-      some cases once `g77' uses `gcc' rather than `f2c' calling
-      conventions.)
- 
-    * Do something useful with `doiter' references where possible.  For
-      example, `CALL FOO(I)' cannot modify `I' if within a `DO' loop
-      that uses `I' as the iteration variable, and the back end might
-      find that info useful in determining whether it needs to read `I'
-      back into a register after the call.  (It normally has to do that,
-      unless it knows `FOO' never modifies its passed-by-reference
-      argument, which is rarely the case for Fortran-77 code.)
- 
- 
- File: g77.info,  Node: Simplify Porting,  Next: More Extensions,  Prev: Better Optimization,  Up: Projects
- 
- Simplify Porting
- ================
- 
-    Making `g77' easier to configure, port, build, and install, either
- as a single-system compiler or as a cross-compiler, would be very
- useful.
- 
-    * A new library (replacing `libg2c') should improve portability as
-      well as produce more optimal code.  Further, `g77' and the new
-      library should conspire to simplify naming of externals, such as
-      by removing unnecessarily added underscores, and to
-      reduce/eliminate the possibility of naming conflicts, while making
-      debugger more straightforward.
- 
-      Also, it should make multi-language applications more feasible,
-      such as by providing Fortran intrinsics that get Fortran unit
-      numbers given C `FILE *' descriptors.
- 
-    * Possibly related to a new library, `g77' should produce the
-      equivalent of a `gcc' `main(argc, argv)' function when it compiles
-      a main program unit, instead of compiling something that must be
-      called by a library implementation of `main()'.
- 
-      This would do many useful things such as provide more flexibility
-      in terms of setting up exception handling, not requiring
-      programmers to start their debugging sessions with `breakpoint
-      MAIN__' followed by `run', and so on.
- 
-    * The GBE needs to understand the difference between alignment
-      requirements and desires.  For example, on Intel x86 machines,
-      `g77' currently imposes overly strict alignment requirements, due
-      to the back end, but it would be useful for Fortran and C
-      programmers to be able to override these _recommendations_ as long
-      as they don't violate the actual processor _requirements_.
- 
- 
- File: g77.info,  Node: More Extensions,  Next: Machine Model,  Prev: Simplify Porting,  Up: Projects
- 
- More Extensions
- ===============
- 
-    These extensions are not the sort of things users ask for "by name",
- but they might improve the usability of `g77', and Fortran in general,
- in the long run.  Some of these items really pertain to improving `g77'
- internals so that some popular extensions can be more easily supported.
- 
-    * Look through all the documentation on the GNU Fortran language,
-      dialects, compiler, missing features, bugs, and so on.  Many
-      mentions of incomplete or missing features are sprinkled
-      throughout.  It is not worth repeating them here.
- 
-    * Consider adding a `NUMERIC' type to designate typeless numeric
-      constants, named and unnamed.  The idea is to provide a
-      forward-looking, effective replacement for things like the
-      old-style `PARAMETER' statement when people really need
-      typelessness in a maintainable, portable, clearly documented way.
-      Maybe `TYPELESS' would include `CHARACTER', `POINTER', and
-      whatever else might come along.  (This is not really a call for
-      polymorphism per se, just an ability to express limited, syntactic
-      polymorphism.)
- 
-    * Support `OPEN(...,KEY=(...),...)'.
- 
-    * Support arbitrary file unit numbers, instead of limiting them to 0
-      through `MXUNIT-1'.  (This is a `libg2c' issue.)
- 
-    * `OPEN(NOSPANBLOCKS,...)' is treated as
-      `OPEN(UNIT=NOSPANBLOCKS,...)', so a later `UNIT=' in the first
-      example is invalid.  Make sure this is what users of this feature
-      would expect.
- 
-    * Currently `g77' disallows `READ(1'10)' since it is an obnoxious
-      syntax, but supporting it might be pretty easy if needed.  More
-      details are needed, such as whether general expressions separated
-      by an apostrophe are supported, or maybe the record number can be
-      a general expression, and so on.
- 
-    * Support `STRUCTURE', `UNION', `MAP', and `RECORD' fully.
-      Currently there is no support at all for `%FILL' in `STRUCTURE'
-      and related syntax, whereas the rest of the stuff has at least
-      some parsing support.  This requires either major changes to
-      `libg2c' or its replacement.
- 
-    * F90 and `g77' probably disagree about label scoping relative to
-      `INTERFACE' and `END INTERFACE', and their contained procedure
-      interface bodies (blocks?).
- 
-    * `ENTRY' doesn't support F90 `RESULT()' yet, since that was added
-      after S8.112.
- 
-    * Empty-statement handling (10 ;;CONTINUE;;) probably isn't
-      consistent with the final form of the standard (it was vague at
-      S8.112).
- 
-    * It seems to be an "open" question whether a file, immediately
-      after being `OPEN'ed,is positioned at the beginning, the end, or
-      wherever--it might be nice to offer an option of opening to
-      "undefined" status, requiring an explicit absolute-positioning
-      operation to be performed before any other (besides `CLOSE') to
-      assist in making applications port to systems (some IBM?) that
-      `OPEN' to the end of a file or some such thing.
- 
- 
- File: g77.info,  Node: Machine Model,  Next: Internals Documentation,  Prev: More Extensions,  Up: Projects
- 
- Machine Model
- =============
- 
-    This items pertain to generalizing `g77''s view of the machine model
- to more fully accept whatever the GBE provides it via its configuration.
- 
-    * Switch to using `REAL_VALUE_TYPE' to represent floating-point
-      constants exclusively so the target float format need not be
-      required.  This means changing the way `g77' handles
-      initialization of aggregate areas having more than one type, such
-      as `REAL' and `INTEGER', because currently it initializes them as
-      if they were arrays of `char' and uses the bit patterns of the
-      constants of the various types in them to determine what to stuff
-      in elements of the arrays.
- 
-    * Rely more and more on back-end info and capabilities, especially
-      in the area of constants (where having the `g77' front-end's IL
-      just store the appropriate tree nodes containing constants might
-      be best).
- 
-    * Suite of C and Fortran programs that a user/administrator can run
-      on a machine to help determine the configuration for `g77' before
-      building and help determine if the compiler works (especially with
-      whatever libraries are installed) after building.
- 
- 
- File: g77.info,  Node: Internals Documentation,  Next: Internals Improvements,  Prev: Machine Model,  Up: Projects
- 
- Internals Documentation
- =======================
- 
-    Better info on how `g77' works and how to port it is needed.
- 
-    *Note Front End::, which contains some information on `g77'
- internals.
- 
- 
- File: g77.info,  Node: Internals Improvements,  Next: Better Diagnostics,  Prev: Internals Documentation,  Up: Projects
- 
- Internals Improvements
- ======================
- 
-    Some more items that would make `g77' more reliable and easier to
- maintain:
- 
-    * Generally make expression handling focus more on critical syntax
-      stuff, leaving semantics to callers.  For example, anything a
-      caller can check, semantically, let it do so, rather than having
-      `expr.c' do it.  (Exceptions might include things like diagnosing
-      `FOO(I--K:)=BAR' where `FOO' is a `PARAMETER'--if it seems
-      important to preserve the left-to-right-in-source order of
-      production of diagnostics.)
- 
-    * Come up with better naming conventions for `-D' to establish
-      requirements to achieve desired implementation dialect via
-      `proj.h'.
- 
-    * Clean up used tokens and `ffewhere's in `ffeglobal_terminate_1'.
- 
-    * Replace `sta.c' `outpooldisp' mechanism with `malloc_pool_use'.
- 
-    * Check for `opANY' in more places in `com.c', `std.c', and `ste.c',
-      and get rid of the `opCONVERT(opANY)' kludge (after determining if
-      there is indeed no real need for it).
- 
-    * Utility to read and check `bad.def' messages and their references
-      in the code, to make sure calls are consistent with message
-      templates.
- 
-    * Search and fix `&ffe...' and similar so that `ffe...ptr...' macros
-      are available instead (a good argument for wishing this could have
-      written all this stuff in C++, perhaps).  On the other hand, it's
-      questionable whether this sort of improvement is really necessary,
-      given the availability of tools such as Emacs and Perl, which make
-      finding any address-taking of structure members easy enough?
- 
-    * Some modules truly export the member names of their structures
-      (and the structures themselves), maybe fix this, and fix other
-      modules that just appear to as well (by appending `_', though it'd
-      be ugly and probably not worth the time).
- 
-    * Implement C macros `RETURNS(value)' and `SETS(something,value)' in
-      `proj.h' and use them throughout `g77' source code (especially in
-      the definitions of access macros in `.h' files) so they can be
-      tailored to catch code writing into a `RETURNS()' or reading from
-      a `SETS()'.
- 
-    * Decorate throughout with `const' and other such stuff.
- 
-    * All F90 notational derivations in the source code are still based
-      on the S8.112 version of the draft standard.  Probably should
-      update to the official standard, or put documentation of the rules
-      as used in the code...uh...in the code.
- 
-    * Some `ffebld_new' calls (those outside of `ffeexpr.c' or inside
-      but invoked via paths not involving `ffeexpr_lhs' or
-      `ffeexpr_rhs') might be creating things in improper pools, leading
-      to such things staying around too long or (doubtful, but possible
-      and dangerous) not long enough.
- 
-    * Some `ffebld_list_new' (or whatever) calls might not be matched by
-      `ffebld_list_bottom' (or whatever) calls, which might someday
-      matter.  (It definitely is not a problem just yet.)
- 
-    * Probably not doing clean things when we fail to `EQUIVALENCE'
-      something due to alignment/mismatch or other problems--they end up
-      without `ffestorag' objects, so maybe the backend (and other parts
-      of the front end) can notice that and handle like an `opANY' (do
-      what it wants, just don't complain or crash).  Most of this seems
-      to have been addressed by now, but a code review wouldn't hurt.
- 
- 
- File: g77.info,  Node: Better Diagnostics,  Prev: Internals Improvements,  Up: Projects
- 
- Better Diagnostics
- ==================
- 
-    These are things users might not ask about, or that need to be
- looked into, before worrying about.  Also here are items that involve
- reducing unnecessary diagnostic clutter.
- 
-    * When `FUNCTION' and `ENTRY' point types disagree (`CHARACTER'
-      lengths, type classes, and so on), `ANY'-ize the offending `ENTRY'
-      point and any _new_ dummies it specifies.
- 
-    * Speed up and improve error handling for data when repeat-count is
-      specified.  For example, don't output 20 unnecessary messages
-      after the first necessary one for:
- 
-           INTEGER X(20)
-           CONTINUE
-           DATA (X(I), J= 1, 20) /20*5/
-           END
- 
-      (The `CONTINUE' statement ensures the `DATA' statement is
-      processed in the context of executable, not specification,
-      statements.)
- 
- 
- File: g77.info,  Node: Front End,  Next: Diagnostics,  Prev: Projects,  Up: Top
- 
- Front End
- *********
- 
-    This chapter describes some aspects of the design and implementation
- of the `g77' front end.
- 
-    To find about things that are "To Be Determined" or "To Be Done",
- search for the string TBD.  If you want to help by working on one or
- more of these items, email <gcc@gcc.gnu.org>.  If you're planning to do
- more than just research issues and offer comments, see
- `http://www.gnu.org/software/contribute.html' for steps you might need
- to take first.
- 
- * Menu:
- 
- * Overview of Sources::
- * Overview of Translation Process::
- * Philosophy of Code Generation::
- * Two-pass Design::
- * Challenges Posed::
- * Transforming Statements::
- * Transforming Expressions::
- * Internal Naming Conventions::
- 
- 
- File: g77.info,  Node: Overview of Sources,  Next: Overview of Translation Process,  Up: Front End
- 
- Overview of Sources
- ===================
- 
-    The current directory layout includes the following:
- 
- `{No value for `srcdir'}/gcc/'
-      Non-g77 files in gcc
- 
- `{No value for `srcdir'}/gcc/f/'
-      GNU Fortran front end sources
- 
- `{No value for `srcdir'}/libf2c/'
-      `libg2c' configuration and `g2c.h' file generation
- 
- `{No value for `srcdir'}/libf2c/libF77/'
-      General support and math portion of `libg2c'
- 
- `{No value for `srcdir'}/libf2c/libI77/'
-      I/O portion of `libg2c'
- 
- `{No value for `srcdir'}/libf2c/libU77/'
-      Additional interfaces to Unix `libc' for `libg2c'
- 
-    Components of note in `g77' are described below.
- 
-    `f/' as a whole contains the source for `g77', while `libf2c/'
- contains a portion of the separate program `f2c'.  Note that the
- `libf2c' code is not part of the program `g77', just distributed with
- it.
- 
-    `f/' contains text files that document the Fortran compiler, source
- files for the GNU Fortran Front End (FFE), and some other stuff.  The
- `g77' compiler code is placed in `f/' because it, along with its
- contents, is designed to be a subdirectory of a `gcc' source directory,
- `gcc/', which is structured so that language-specific front ends can be
- "dropped in" as subdirectories.  The C++ front end (`g++'), is an
- example of this--it resides in the `cp/' subdirectory.  Note that the C
- front end (also referred to as `gcc') is an exception to this, as its
- source files reside in the `gcc/' directory itself.
- 
-    `libf2c/' contains the run-time libraries for the `f2c' program,
- also used by `g77'.  These libraries normally referred to collectively
- as `libf2c'.  When built as part of `g77', `libf2c' is installed under
- the name `libg2c' to avoid conflict with any existing version of
- `libf2c', and thus is often referred to as `libg2c' when the `g77'
- version is specifically being referred to.
- 
-    The `netlib' version of `libf2c/' contains two distinct libraries,
- `libF77' and `libI77', each in their own subdirectories.  In `g77',
- this distinction is not made, beyond maintaining the subdirectory
- structure in the source-code tree.
- 
-    `libf2c/' is not part of the program `g77', just distributed with it.
- It contains files not present in the official (`netlib') version of
- `libf2c', and also contains some minor changes made from `libf2c', to
- fix some bugs, and to facilitate automatic configuration, building, and
- installation of `libf2c' (as `libg2c') for use by `g77' users.  See
- `libf2c/README' for more information, including licensing conditions
- governing distribution of programs containing code from `libg2c'.
- 
-    `libg2c', `g77''s version of `libf2c', adds Dave Love's
- implementation of `libU77', in the `libf2c/libU77/' directory.  This
- library is distributed under the GNU Library General Public License
- (LGPL)--see the file `libf2c/libU77/COPYING.LIB' for more information,
- as this license governs distribution conditions for programs containing
- code from this portion of the library.
- 
-    Files of note in `f/' and `libf2c/' are described below:
- 
- `f/BUGS'
-      Lists some important bugs known to be in g77.  Or use Info (or GNU
-      Emacs Info mode) to read the "Actual Bugs" node of the `g77'
-      documentation:
- 
-           info -f f/g77.info -n "Actual Bugs"
- 
- `f/ChangeLog'
-      Lists recent changes to `g77' internals.
- 
- `libf2c/ChangeLog'
-      Lists recent changes to `libg2c' internals.
- 
- `f/NEWS'
-      Contains the per-release changes.  These include the user-visible
-      changes described in the node "Changes" in the `g77'
-      documentation, plus internal changes of import.  Or use:
- 
-           info -f f/g77.info -n News
- 
- `f/g77.info*'
-      The `g77' documentation, in Info format, produced by building
-      `g77'.
- 
-      All users of `g77' (not just installers) should read this, using
-      the `more' command if neither the `info' command, nor GNU Emacs
-      (with its Info mode), are available, or if users aren't yet
-      accustomed to using these tools.  All of these files are readable
-      as "plain text" files, though they're easier to navigate using
-      Info readers such as `info' and GNU Emacs Info mode.
- 
-    If you want to explore the FFE code, which lives entirely in `f/',
- here are a few clues.  The file `g77spec.c' contains the `g77'-specific
- source code for the `g77' command only--this just forms a variant of the
- `gcc' command, so, just as the `gcc' command itself does not contain
- the C front end, the `g77' command does not contain the Fortran front
- end (FFE).  The FFE code ends up in an executable named `f771', which
- does the actual compiling, so it contains the FFE plus the `gcc' back
- end (GBE), the latter to do most of the optimization, and the code
- generation.
- 
-    The file `parse.c' is the source file for `yyparse()', which is
- invoked by the GBE to start the compilation process, for `f771'.
- 
-    The file `top.c' contains the top-level FFE function `ffe_file' and
- it (along with top.h) define all `ffe_[a-z].*', `ffe[A-Z].*', and
- `FFE_[A-Za-z].*' symbols.
- 
-    The file `fini.c' is a `main()' program that is used when building
- the FFE to generate C header and source files for recognizing keywords.
- The files `malloc.c' and `malloc.h' comprise a memory manager that
- defines all `malloc_[a-z].*', `malloc[A-Z].*', and `MALLOC_[A-Za-z].*'
- symbols.
- 
-    All other modules named XYZ are comprised of all files named
- `XYZ*.EXT' and define all `ffeXYZ_[a-z].*', `ffeXYZ[A-Z].*', and
- `FFEXYZ_[A-Za-z].*' symbols.  If you understand all this,
- congratulations--it's easier for me to remember how it works than to
- type in these regular expressions.  But it does make it easy to find
- where a symbol is defined.  For example, the symbol
- `ffexyz_set_something' would be defined in `xyz.h' and implemented
- there (if it's a macro) or in `xyz.c'.
- 
-    The "porting" files of note currently are:
- 
- `proj.c'
- `proj.h'
-      This defines the "language" used by all the other source files,
-      the language being Standard C plus some useful things like
-      `ARRAY_SIZE' and such.
- 
- `target.c'
- `target.h'
-      These describe the target machine in terms of what data types are
-      supported, how they are denoted (to what C type does an
-      `INTEGER*8' map, for example), how to convert between them, and so
-      on.  Over time, versions of `g77' rely less on this file and more
-      on run-time configuration based on GBE info in `com.c'.
- 
- `com.c'
- `com.h'
-      These are the primary interface to the GBE.
- 
- `ste.c'
- `ste.h'
-      This contains code for implementing recognized executable
-      statements in the GBE.
- 
- `src.c'
- `src.h'
-      These contain information on the format(s) of source files (such
-      as whether they are never to be processed as case-insensitive with
-      regard to Fortran keywords).
- 
-    If you want to debug the `f771' executable, for example if it
- crashes, note that the global variables `lineno' and `input_filename'
- are usually set to reflect the current line being read by the lexer
- during the first-pass analysis of a program unit and to reflect the
- current line being processed during the second-pass compilation of a
- program unit.
- 
-    If an invocation of the function `ffestd_exec_end' is on the stack,
- the compiler is in the second pass, otherwise it is in the first.
- 
-    (This information might help you reduce a test case and/or work
- around a bug in `g77' until a fix is available.)
- 
- 
- File: g77.info,  Node: Overview of Translation Process,  Next: Philosophy of Code Generation,  Prev: Overview of Sources,  Up: Front End
- 
- Overview of Translation Process
- ===============================
- 
-    The order of phases translating source code to the form accepted by
- the GBE is:
- 
-   1. Stripping punched-card sources (`g77stripcard.c')
- 
-   2. Lexing (`lex.c')
- 
-   3. Stand-alone statement identification (`sta.c')
- 
-   4. INCLUDE handling (`sti.c')
- 
-   5. Order-dependent statement identification (`stq.c')
- 
-   6. Parsing (`stb.c' and `expr.c')
- 
-   7. Constructing (`stc.c')
- 
-   8. Collecting (`std.c')
- 
-   9. Expanding (`ste.c')
- 
-    To get a rough idea of how a particularly twisted Fortran statement
- gets treated by the passes, consider:
- 
-            FORMAT(I2 4H)=(J/
-           &   I3)
- 
-    The job of `lex.c' is to know enough about Fortran syntax rules to
- break the statement up into distinct lexemes without requiring any
- feedback from subsequent phases:
- 
-      `FORMAT'
-      `('
-      `I24H'
-      `)'
-      `='
-      `('
-      `J'
-      `/'
-      `I3'
-      `)'
- 
-    The job of `sta.c' is to figure out the kind of statement, or, at
- least, statement form, that sequence of lexemes represent.
- 
-    The sooner it can do this (in terms of using the smallest number of
- lexemes, starting with the first for each statement), the better,
- because that leaves diagnostics for problems beyond the recognition of
- the statement form to subsequent phases, which can usually better
- describe the nature of the problem.
- 
-    In this case, the `=' at "level zero" (not nested within parentheses)
- tells `sta.c' that this is an _assignment-form_, not `FORMAT',
- statement.
- 
-    An assignment-form statement might be a statement-function
- definition or an executable assignment statement.
- 
-    To make that determination, `sta.c' looks at the first two lexemes.
- 
-    Since the second lexeme is `(', the first must represent an array
- for this to be an assignment statement, else it's a statement function.
- 
-    Either way, `sta.c' hands off the statement to `stq.c' (via `sti.c',
- which expands INCLUDE files).  `stq.c' figures out what a statement
- that is, on its own, ambiguous, must actually be based on the context
- established by previous statements.
- 
-    So, `stq.c' watches the statement stream for executable statements,
- END statements, and so on, so it knows whether `A(B)=C' is (intended
- as) a statement-function definition or an assignment statement.
- 
-    After establishing the context-aware statement info, `stq.c' passes
- the original sample statement on to `stb.c' (either its
- statement-function parser or its assignment-statement parser).
- 
-    `stb.c' forms a statement-specific record containing the pertinent
- information.  That information includes a source expression and, for an
- assignment statement, a destination expression.  Expressions are parsed
- by `expr.c'.
- 
-    This record is passed to `stc.c', which copes with the implications
- of the statement within the context established by previous statements.
- 
-    For example, if it's the first statement in the file or after an
- `END' statement, `stc.c' recognizes that, first of all, a main program
- unit is now being lexed (and tells that to `std.c' before telling it
- about the current statement).
- 
-    `stc.c' attaches whatever information it can, usually derived from
- the context established by the preceding statements, and passes the
- information to `std.c'.
- 
-    `std.c' saves this information away, since the GBE cannot cope with
- information that might be incomplete at this stage.
- 
-    For example, `I3' might later be determined to be an argument to an
- alternate `ENTRY' point.
- 
-    When `std.c' is told about the end of an external (top-level)
- program unit, it passes all the information it has saved away on
- statements in that program unit to `ste.c'.
- 
-    `ste.c' "expands" each statement, in sequence, by constructing the
- appropriate GBE information and calling the appropriate GBE routines.
- 
-    Details on the transformational phases follow.  Keep in mind that
- Fortran numbering is used, so the first character on a line is column 1,
- decimal numbering is used, and so on.
- 
- * Menu:
- 
- * g77stripcard::
- * lex.c::
- * sta.c::
- * sti.c::
- * stq.c::
- * stb.c::
- * expr.c::
- * stc.c::
- * std.c::
- * ste.c::
- 
- * Gotchas (Transforming)::
- * TBD (Transforming)::
- 
- 
- File: g77.info,  Node: g77stripcard,  Next: lex.c,  Up: Overview of Translation Process
- 
- g77stripcard
- ------------
- 
-    The `g77stripcard' program handles removing content beyond column 72
- (adjustable via a command-line option), optionally warning about that
- content being something other than trailing whitespace or Fortran
- commentary.
- 
-    This program is needed because `lex.c' doesn't pay attention to
- maximum line lengths at all, to make it easier to maintain, as well as
- faster (for sources that don't depend on the maximum column length
- vis-a-vis trailing non-blank non-commentary content).
- 
-    Just how this program will be run--whether automatically for old
- source (perhaps as the default for `.f' files?)--is not yet determined.
- 
-    In the meantime, it might as well be implemented as a typical UNIX
- pipe.
- 
-    It should accept a `-fline-length-N' option, with the default line
- length set to 72.
- 
-    When the text it strips off the end of a line is not blank (not
- spaces and tabs), it should insert an additional comment line
- (beginning with `!', so it works for both fixed-form and free-form
- files) containing the text, following the stripped line.  The inserted
- comment should have a prefix of some kind, TBD, that distinguishes the
- comment as representing stripped text.  Users could use that to `sed'
- out such lines, if they wished--it seems silly to provide a
- command-line option to delete information when it can be so easily
- filtered out by another program.
- 
-    (This inserted comment should be designed to "fit in" well with
- whatever the Fortran community is using these days for preprocessor,
- translator, and other such products, like OpenMP.  What that's all
- about, and how `g77' can elegantly fit its special comment conventions
- into it all, is TBD as well.  We don't want to reinvent the wheel here,
- but if there turn out to be too many conflicting conventions, we might
- have to invent one that looks nothing like the others, but which offers
- their host products a better infrastructure in which to fit and coexist
- peacefully.)
- 
-    `g77stripcard' probably shouldn't do any tab expansion or other
- fancy stuff.  People can use `expand' or other pre-filtering if they
- like.  The idea here is to keep each stage quite simple, while providing
- excellent performance for "normal" code.
- 
-    (Code with junk beyond column 73 is not really "normal", as it comes
- from a card-punch heritage, and will be increasingly hard for
- tomorrow's Fortran programmers to read.)
- 
- 
- File: g77.info,  Node: lex.c,  Next: sta.c,  Prev: g77stripcard,  Up: Overview of Translation Process
- 
- lex.c
- -----
- 
-    To help make the lexer simple, fast, and easy to maintain, while
- also having `g77' generally encourage Fortran programmers to write
- simple, maintainable, portable code by maximizing the performance of
- compiling that kind of code:
- 
-    * There'll be just one lexer, for both fixed-form and free-form
-      source.
- 
-    * It'll care about the form only when handling the first 7 columns of
-      text, stuff like spaces between strings of alphanumerics, and how
-      lines are continued.
- 
-      Some other distinctions will be handled by subsequent phases, so
-      at least one of them will have to know which form is involved.
- 
-      For example, `I = 2 . 4' is acceptable in fixed form, and works in
-      free form as well given the implementation `g77' presently uses.
-      But the standard requires a diagnostic for it in free form, so the
-      parser has to be able to recognize that the lexemes aren't
-      contiguous (information the lexer _does_ have to provide) and that
-      free-form source is being parsed, so it can provide the diagnostic.
- 
-      The `g77' lexer doesn't try to gather `2 . 4' into a single lexeme.
-      Otherwise, it'd have to know a whole lot more about how to parse
-      Fortran, or subsequent phases (mainly parsing) would have two
-      paths through lots of critical code--one to handle the lexeme `2',
-      `.', and `4' in sequence, another to handle the lexeme `2.4'.
- 
-    * It won't worry about line lengths (beyond the first 7 columns for
-      fixed-form source).
- 
-      That is, once it starts parsing the "statement" part of a line
-      (column 7 for fixed-form, column 1 for free-form), it'll keep
-      going until it finds a newline, rather than ignoring everything
-      past a particular column (72 or 132).
- 
-      The implication here is that there shouldn't _be_ anything past
-      that last column, other than whitespace or commentary, because
-      users using typical editors (or viewing output as typically
-      printed) won't necessarily know just where the last column is.
- 
-      Code that has "garbage" beyond the last column (almost certainly
-      only fixed-form code with a punched-card legacy, such as code
-      using columns 73-80 for "sequence numbers") will have to be run
-      through `g77stripcard' first.
- 
-      Also, keeping track of the maximum column position while also
-      watching out for the end of a line _and_ while reading from a file
-      just makes things slower.  Since a file must be read, and watching
-      for the end of the line is necessary (unless the typical input
-      file was preprocessed to include the necessary number of trailing
-      spaces), dropping the tracking of the maximum column position is
-      the only way to reduce the complexity of the pertinent code while
-      maintaining high performance.
- 
-    * ASCII encoding is assumed for the input file.
- 
-      Code written in other character sets will have to be converted
-      first.
- 
-    * Tabs (ASCII code 9) will be converted to spaces via the
-      straightforward approach.
- 
-      Specifically, a tab is converted to between one and eight spaces
-      as necessary to reach column N, where dividing `(N - 1)' by eight
-      results in a remainder of zero.
- 
-      That saves having to pass most source files through `expand'.
- 
-    * Linefeeds (ASCII code 10) mark the ends of lines.
- 
-    * A carriage return (ASCII code 13) is accept if it immediately
-      precedes a linefeed, in which case it is ignored.
- 
-      Otherwise, it is rejected (with a diagnostic).
- 
-    * Any other characters other than the above that are not part of the
-      GNU Fortran Character Set (*note Character Set::) are rejected
-      with a diagnostic.
- 
-      This includes backspaces, form feeds, and the like.
- 
-      (It might make sense to allow a form feed in column 1 as long as
-      that's the only character on a line.  It certainly wouldn't seem
-      to cost much in terms of performance.)
- 
-    * The end of the input stream (EOF) ends the current line.
- 
-    * The distinction between uppercase and lowercase letters will be
-      preserved.
- 
-      It will be up to subsequent phases to decide to fold case.
- 
-      Current plans are to permit any casing for Fortran (reserved)
-      keywords while preserving casing for user-defined names.  (This
-      might not be made the default for `.f' files, though.)
- 
-      Preserving case seems necessary to provide more direct access to
-      facilities outside of `g77', such as to C or Pascal code.
- 
-      Names of intrinsics will probably be matchable in any case,
- 
-      (How `external SiN; r = sin(x)' would be handled is TBD.  I think
-      old `g77' might already handle that pretty elegantly, but whether
-      we can cope with allowing the same fragment to reference a
-      _different_ procedure, even with the same interface, via `s =
-      SiN(r)', needs to be determined.  If it can't, we need to make
-      sure that when code introduces a user-defined name, any intrinsic
-      matching that name using a case-insensitive comparison is "turned
-      off".)
- 
-    * Backslashes in `CHARACTER' and Hollerith constants are not allowed.
- 
-      This avoids the confusion introduced by some Fortran compiler
-      vendors providing C-like interpretation of backslashes, while
-      others provide straight-through interpretation.
- 
-      Some kind of lexical construct (TBD) will be provided to allow
-      flagging of a `CHARACTER' (but probably not a Hollerith) constant
-      that permits backslashes.  It'll necessarily be a prefix, such as:
- 
-           PRINT *, C'This line has a backspace \b here.'
-           PRINT *, F'This line has a straight backslash \ here.'
- 
-      Further, command-line options might be provided to specify that
-      one prefix or the other is to be assumed as the default for
-      `CHARACTER' constants.
- 
-      However, it seems more helpful for `g77' to provide a program that
-      converts prefix all constants (or just those containing
-      backslashes) with the desired designation, so printouts of code
-      can be read without knowing the compile-time options used when
-      compiling it.
- 
-      If such a program is provided (let's name it `g77slash' for now),
-      then a command-line option to `g77' should not be provided.
-      (Though, given that it'll be easy to implement, it might be hard
-      to resist user requests for it "to compile faster than if we have
-      to invoke another filter".)
- 
-      This program would take a command-line option to specify the
-      default interpretation of slashes, affecting which prefix it uses
-      for constants.
- 
-      `g77slash' probably should automatically convert Hollerith
-      constants that contain slashes to the appropriate `CHARACTER'
-      constants.  Then `g77' wouldn't have to define a prefix syntax for
-      Hollerith constants specifying whether they want C-style or
-      straight-through backslashes.
- 
-    * To allow for form-neutral INCLUDE files without requiring them to
-      be preprocessed, the fixed-form lexer should offer an extension
-      (if possible) allowing a trailing `&' to be ignored, especially if
-      after column 72, as it would be using the traditional Unix Fortran
-      source model (which ignores _everything_ after column 72).
- 
-    The above implements nearly exactly what is specified by *Note
- Character Set::, and *Note Lines::, except it also provides automatic
- conversion of tabs and ignoring of newline-related carriage returns, as
- well as accommodating form-neutral INCLUDE files.
- 
-    It also implements the "pure visual" model, by which is meant that a
- user viewing his code in a typical text editor (assuming it's not
- preprocessed via `g77stripcard' or similar) doesn't need any special
- knowledge of whether spaces on the screen are really tabs, whether
- lines end immediately after the last visible non-space character or
- after a number of spaces and tabs that follow it, or whether the last
- line in the file is ended by a newline.
- 
-    Most editors don't make these distinctions, the ANSI FORTRAN 77
- standard doesn't require them to, and it permits a standard-conforming
- compiler to define a method for transforming source code to "standard
- form" however it wants.
- 
-    So, GNU Fortran defines it such that users have the best chance of
- having the code be interpreted the way it looks on the screen of the
- typical editor.
- 
-    (Fancy editors should _never_ be required to correctly read code
- written in classic two-dimensional-plaintext form.  By correct reading
- I mean ability to read it, book-like, without mistaking text ignored by
- the compiler for program code and vice versa, and without having to
- count beyond the first several columns.  The vague meaning of ASCII
- TAB, among other things, complicates this somewhat, but as long as
- "everyone", including the editor, other tools, and printer, agrees
- about the every-eighth-column convention, the GNU Fortran "pure visual"
- model meets these requirements.  Any language or user-visible source
- form requiring special tagging of tabs, the ends of lines after
- spaces/tabs, and so on, fails to meet this fairly straightforward
- specification.  Fortunately, Fortran _itself_ does not mandate such a
- failure, though most vendor-supplied defaults for their Fortran
- compilers _do_ fail to meet this specification for readability.)
- 
-    Further, this model provides a clean interface to whatever
- preprocessors or code-generators are used to produce input to this
- phase of `g77'.  Mainly, they need not worry about long lines.
- 
- 
- File: g77.info,  Node: sta.c,  Next: sti.c,  Prev: lex.c,  Up: Overview of Translation Process
- 
- sta.c
- -----
- 
- 
- File: g77.info,  Node: sti.c,  Next: stq.c,  Prev: sta.c,  Up: Overview of Translation Process
- 
- sti.c
- -----
- 
- 
- File: g77.info,  Node: stq.c,  Next: stb.c,  Prev: sti.c,  Up: Overview of Translation Process
- 
- stq.c
- -----
- 
- 
- File: g77.info,  Node: stb.c,  Next: expr.c,  Prev: stq.c,  Up: Overview of Translation Process
- 
- stb.c
- -----
- 
- 
- File: g77.info,  Node: expr.c,  Next: stc.c,  Prev: stb.c,  Up: Overview of Translation Process
- 
- expr.c
- ------
- 
- 
- File: g77.info,  Node: stc.c,  Next: std.c,  Prev: expr.c,  Up: Overview of Translation Process
- 
- stc.c
- -----
- 
- 
- File: g77.info,  Node: std.c,  Next: ste.c,  Prev: stc.c,  Up: Overview of Translation Process
- 
- std.c
- -----
- 
- 
- File: g77.info,  Node: ste.c,  Next: Gotchas (Transforming),  Prev: std.c,  Up: Overview of Translation Process
- 
- ste.c
- -----
- 
--- 0 ----
diff -Nrc3pad gcc-3.2.3/gcc/f/g77.info-19 gcc-3.3/gcc/f/g77.info-19
*** gcc-3.2.3/gcc/f/g77.info-19	2003-04-22 07:07:25.000000000 +0000
--- gcc-3.3/gcc/f/g77.info-19	1970-01-01 00:00:00.000000000 +0000
***************
*** 1,1209 ****
- This is g77.info, produced by makeinfo version 4.5 from g77.texi.
- 
- INFO-DIR-SECTION Programming
- START-INFO-DIR-ENTRY
- * g77: (g77).                  The GNU Fortran compiler.
- END-INFO-DIR-ENTRY
-    This file documents the use and the internals of the GNU Fortran
- (`g77') compiler.  It corresponds to the GCC-3.2.3 version of `g77'.
- 
-    Published by the Free Software Foundation 59 Temple Place - Suite 330
- Boston, MA 02111-1307 USA
- 
-    Copyright (C) 1995,1996,1997,1998,1999,2000,2001,2002 Free Software
- Foundation, Inc.
- 
-    Permission is granted to copy, distribute and/or modify this document
- under the terms of the GNU Free Documentation License, Version 1.1 or
- any later version published by the Free Software Foundation; with the
- Invariant Sections being "GNU General Public License" and "Funding Free
- Software", the Front-Cover texts being (a) (see below), and with the
- Back-Cover Texts being (b) (see below).  A copy of the license is
- included in the section entitled "GNU Free Documentation License".
- 
-    (a) The FSF's Front-Cover Text is:
- 
-    A GNU Manual
- 
-    (b) The FSF's Back-Cover Text is:
- 
-    You have freedom to copy and modify this GNU Manual, like GNU
- software.  Copies published by the Free Software Foundation raise
- funds for GNU development.
- 
-    Contributed by James Craig Burley (<craig@jcb-sc.com>).  Inspired by
- a first pass at translating `g77-0.5.16/f/DOC' that was contributed to
- Craig by David Ronis (<ronis@onsager.chem.mcgill.ca>).
- 
- 
- File: g77.info,  Node: Gotchas (Transforming),  Next: TBD (Transforming),  Prev: ste.c,  Up: Overview of Translation Process
- 
- Gotchas (Transforming)
- ----------------------
- 
-    This section is not about transforming "gotchas" into something else.
- It is about the weirder aspects of transforming Fortran, however that's
- defined, into a more modern, canonical form.
- 
- Multi-character Lexemes
- .......................
- 
-    Each lexeme carries with it a pointer to where it appears in the
- source.
- 
-    To provide the ability for diagnostics to point to column numbers,
- in addition to line numbers and names, lexemes that represent more than
- one (significant) character in the source code need, generally, to
- provide pointers to where each _character_ appears in the source.
- 
-    This provides the ability to properly identify the precise location
- of the problem in code like
- 
-      SUBROUTINE X
-      END
-      BLOCK DATA X
-      END
- 
-    which, in fixed-form source, would result in single lexemes
- consisting of the strings `SUBROUTINEX' and `BLOCKDATAX'.  (The problem
- is that `X' is defined twice, so a pointer to the `X' in the second
- definition, as well as a follow-up pointer to the corresponding pointer
- in the first, would be preferable to pointing to the beginnings of the
- statements.)
- 
-    This need also arises when parsing (and diagnosing) `FORMAT'
- statements.
- 
-    Further, it arises when diagnosing `FMT=' specifiers that contain
- constants (or partial constants, or even propagated constants!)  in I/O
- statements, as in:
- 
-      PRINT '(I2, 3HAB)', J
- 
-    (A pointer to the beginning of the prematurely-terminated Hollerith
- constant, and/or to the close parenthese, is preferable to a pointer to
- the open-parenthese or the apostrophe that precedes it.)
- 
-    Multi-character lexemes, which would seem to naturally include at
- least digit strings, alphanumeric strings, `CHARACTER' constants, and
- Hollerith constants, therefore need to provide location information on
- each character.  (Maybe Hollerith constants don't, but it's unnecessary
- to except them.)
- 
-    The question then arises, what about _other_ multi-character lexemes,
- such as `**' and `//', and Fortran 90's `(/', `/)', `::', and so on?
- 
-    Turns out there's a need to identify the location of the second
- character of these two-character lexemes.  For example, in `I(/J) = K',
- the slash needs to be diagnosed as the problem, not the open parenthese.
- Similarly, it is preferable to diagnose the second slash in `I = J //
- K' rather than the first, given the implicit typing rules, which would
- result in the compiler disallowing the attempted concatenation of two
- integers.  (Though, since that's more of a semantic issue, it's not
- _that_ much preferable.)
- 
-    Even sequences that could be parsed as digit strings could use
- location info, for example, to diagnose the `9' in the octal constant
- `O'129''.  (This probably will be parsed as a character string, to be
- consistent with the parsing of `Z'129A''.)
- 
-    To avoid the hassle of recording the location of the second
- character, while also preserving the general rule that each significant
- character is distinctly pointed to by the lexeme that contains it, it's
- best to simply not have any fixed-size lexemes larger than one
- character.
- 
-    This new design is expected to make checking for two `*' lexemes in
- a row much easier than the old design, so this is not much of a
- sacrifice.  It probably makes the lexer much easier to implement than
- it makes the parser harder.
- 
- Space-padding Lexemes
- .....................
- 
-    Certain lexemes need to be padded with virtual spaces when the end
- of the line (or file) is encountered.
- 
-    This is necessary in fixed form, to handle lines that don't extend
- to column 72, assuming that's the line length in effect.
- 
- Bizarre Free-form Hollerith Constants
- .....................................
- 
-    Last I checked, the Fortran 90 standard actually required the
- compiler to silently accept something like
- 
-      FORMAT ( 1 2   Htwelve chars )
- 
-    as a valid `FORMAT' statement specifying a twelve-character
- Hollerith constant.
- 
-    The implication here is that, since the new lexer is a zero-feedback
- one, it won't know that the special case of a `FORMAT' statement being
- parsed requires apparently distinct lexemes `1' and `2' to be treated as
- a single lexeme.
- 
-    (This is a horrible misfeature of the Fortran 90 language.  It's one
- of many such misfeatures that almost make me want to not support them,
- and forge ahead with designing a new "GNU Fortran" language that has
- the features, but not the misfeatures, of Fortran 90, and provide
- utility programs to do the conversion automatically.)
- 
-    So, the lexer must gather distinct chunks of decimal strings into a
- single lexeme in contexts where a single decimal lexeme might start a
- Hollerith constant.
- 
-    (Which probably means it might as well do that all the time for all
- multi-character lexemes, even in free-form mode, leaving it to
- subsequent phases to pull them apart as they see fit.)
- 
-    Compare the treatment of this to how
- 
-      CHARACTER * 4 5 HEY
- 
-    and
- 
-      CHARACTER * 12 HEY
- 
-    must be treated--the former must be diagnosed, due to the separation
- between lexemes, the latter must be accepted as a proper declaration.
- 
- Hollerith Constants
- ...................
- 
-    Recognizing a Hollerith constant--specifically, that an `H' or `h'
- after a digit string begins such a constant--requires some knowledge of
- context.
- 
-    Hollerith constants (such as `2HAB') can appear after:
- 
-    * `('
- 
-    * `,'
- 
-    * `='
- 
-    * `+', `-', `/'
- 
-    * `*', except as noted below
- 
-    Hollerith constants don't appear after:
- 
-    * `CHARACTER*', which can be treated generally as any `*' that is
-      the second lexeme of a statement
- 
- Confusing Function Keyword
- ..........................
- 
-    While
- 
-      REAL FUNCTION FOO ()
- 
-    must be a `FUNCTION' statement and
- 
-      REAL FUNCTION FOO (5)
- 
-    must be a type-definition statement,
- 
-      REAL FUNCTION FOO (NAMES)
- 
-    where NAMES is a comma-separated list of names, can be one or the
- other.
- 
-    The only way to disambiguate that statement (short of mandating
- free-form source or a short maximum length for name for external
- procedures) is based on the context of the statement.
- 
-    In particular, the statement is known to be within an
- already-started program unit (but not at the outer level of the
- `CONTAINS' block), it is a type-declaration statement.
- 
-    Otherwise, the statement is a `FUNCTION' statement, in that it
- begins a function program unit (external, or, within `CONTAINS',
- nested).
- 
- Weird READ
- ..........
- 
-    The statement
- 
-      READ (N)
- 
-    is equivalent to either
- 
-      READ (UNIT=(N))
- 
-    or
- 
-      READ (FMT=(N))
- 
-    depending on which would be valid in context.
- 
-    Specifically, if `N' is type `INTEGER', `READ (FMT=(N))' would not
- be valid, because parentheses may not be used around `N', whereas they
- may around it in `READ (UNIT=(N))'.
- 
-    Further, if `N' is type `CHARACTER', the opposite is true--`READ
- (UNIT=(N))' is not valid, but `READ (FMT=(N))' is.
- 
-    Strictly speaking, if anything follows
- 
-      READ (N)
- 
-    in the statement, whether the first lexeme after the close
- parenthese is a comma could be used to disambiguate the two cases,
- without looking at the type of `N', because the comma is required for
- the `READ (FMT=(N))' interpretation and disallowed for the `READ
- (UNIT=(N))' interpretation.
- 
-    However, in practice, many Fortran compilers allow the comma for the
- `READ (UNIT=(N))' interpretation anyway (in that they generally allow a
- leading comma before an I/O list in an I/O statement), and much code
- takes advantage of this allowance.
- 
-    (This is quite a reasonable allowance, since the juxtaposition of a
- comma-separated list immediately after an I/O control-specification
- list, which is also comma-separated, without an intervening comma,
- looks sufficiently "wrong" to programmers that they can't resist the
- itch to insert the comma.  `READ (I, J), K, L' simply looks cleaner than
- `READ (I, J) K, L'.)
- 
-    So, type-based disambiguation is needed unless strict adherence to
- the standard is always assumed, and we're not going to assume that.
- 
- 
- File: g77.info,  Node: TBD (Transforming),  Prev: Gotchas (Transforming),  Up: Overview of Translation Process
- 
- TBD (Transforming)
- ------------------
- 
-    Continue researching gotchas, designing the transformational process,
- and implementing it.
- 
-    Specific issues to resolve:
- 
-    * Just where should (if it was implemented) `USE' processing take
-      place?
- 
-      This gets into the whole issue of how `g77' should handle the
-      concept of modules.  I think GNAT already takes on this issue, but
-      don't know more than that.  Jim Giles has written extensively on
-      `comp.lang.fortran' about his opinions on module handling, as have
-      others.  Jim's views should be taken into account.
- 
-      Actually, Richard M. Stallman (RMS) also has written up some
-      guidelines for implementing such things, but I'm not sure where I
-      read them.  Perhaps the old <gcc2@cygnus.com> list.
- 
-      If someone could dig references to these up and get them to me,
-      that would be much appreciated!  Even though modules are not on
-      the short-term list for implementation, it'd be helpful to know
-      _now_ how to avoid making them harder to implement them _later_.
- 
-    * Should the `g77' command become just a script that invokes all the
-      various preprocessing that might be needed, thus making it seem
-      slower than necessary for legacy code that people are unwilling to
-      convert, or should we provide a separate script for that, thus
-      encouraging people to convert their code once and for all?
- 
-      At least, a separate script to behave as old `g77' did, perhaps
-      named `g77old', might ease the transition, as might a
-      corresponding one that converts source codes named `g77oldnew'.
- 
-      These scripts would take all the pertinent options `g77' used to
-      take and run the appropriate filters, passing the results to `g77'
-      or just making new sources out of them (in a subdirectory, leaving
-      the user to do the dirty deed of moving or copying them over the
-      old sources).
- 
-    * Do other Fortran compilers provide a prefix syntax to govern the
-      treatment of backslashes in `CHARACTER' (or Hollerith) constants?
- 
-      Knowing what other compilers provide would help.
- 
-    * Is it okay to drop support for the `-fintrin-case-initcap',
-      `-fmatch-case-initcap', `-fsymbol-case-initcap', and
-      `-fcase-initcap' options?
- 
-      I've asked <info-gnu-fortran@gnu.org> for input on this.  Not
-      having to support these makes it easier to write the new front end,
-      and might also avoid complicated its design.
- 
-      The consensus to date (1999-11-17) has been to drop this support.
-      Can't recall anybody saying they're using it, in fact.
- 
- 
- File: g77.info,  Node: Philosophy of Code Generation,  Next: Two-pass Design,  Prev: Overview of Translation Process,  Up: Front End
- 
- Philosophy of Code Generation
- =============================
- 
-    Don't poke the bear.
- 
-    The `g77' front end generates code via the `gcc' back end.
- 
-    The `gcc' back end (GBE) is a large, complex labyrinth of intricate
- code written in a combination of the C language and specialized
- languages internal to `gcc'.
- 
-    While the _code_ that implements the GBE is written in a combination
- of languages, the GBE itself is, to the front end for a language like
- Fortran, best viewed as a _compiler_ that compiles its own, unique,
- language.
- 
-    The GBE's "source", then, is written in this language, which
- consists primarily of a combination of calls to GBE functions and
- "tree" nodes (which are, themselves, created by calling GBE functions).
- 
-    So, the `g77' generates code by, in effect, translating the Fortran
- code it reads into a form "written" in the "language" of the `gcc' back
- end.
- 
-    This language will heretofore be referred to as "GBEL", for GNU Back
- End Language.
- 
-    GBEL is an evolving language, not fully specified in any published
- form as of this writing.  It offers many facilities, but its "core"
- facilities are those that corresponding most directly to those needed
- to support `gcc' (compiling code written in GNU C).
- 
-    The `g77' Fortran Front End (FFE) is designed and implemented to
- navigate the currents and eddies of ongoing GBEL and `gcc' development
- while also delivering on the potential of an integrated FFE (as
- compared to using a converter like `f2c' and feeding the output into
- `gcc').
- 
-    Goals of the FFE's code-generation strategy include:
- 
-    * High likelihood of generation of correct code, or, failing that,
-      producing a fatal diagnostic or crashing.
- 
-    * Generation of highly optimized code, as directed by the user via
-      GBE-specific (versus `g77'-specific) constructs, such as
-      command-line options.
- 
-    * Fast overall (FFE plus GBE) compilation.
- 
-    * Preservation of source-level debugging information.
- 
-    The strategies historically, and currently, used by the FFE to
- achieve these goals include:
- 
-    * Use of GBEL constructs that most faithfully encapsulate the
-      semantics of Fortran.
- 
-    * Avoidance of GBEL constructs that are so rarely used, or limited
-      to use in specialized situations not related to Fortran, that
-      their reliability and performance has not yet been established as
-      sufficient for use by the FFE.
- 
-    * Flexible design, to readily accommodate changes to specific
-      code-generation strategies, perhaps governed by command-line
-      options.
- 
-    "Don't poke the bear" somewhat summarizes the above strategies.  The
- GBE is the bear.  The FFE is designed and implemented to avoid poking it
- in ways that are likely to just annoy it.  The FFE usually either
- tackles it head-on, or avoids treating it in ways dissimilar to how the
- `gcc' front end treats it.
- 
-    For example, the FFE uses the native array facility in the back end
- instead of the lower-level pointer-arithmetic facility used by `gcc'
- when compiling `f2c' output).  Theoretically, this presents more
- opportunities for optimization, faster compile times, and the
- production of more faithful debugging information.  These benefits were
- not, however, immediately realized, mainly because `gcc' itself makes
- little or no use of the native array facility.
- 
-    Complex arithmetic is a case study of the evolution of this strategy.
- When originally implemented, the GBEL had just evolved its own native
- complex-arithmetic facility, so the FFE took advantage of that.
- 
-    When porting `g77' to 64-bit systems, it was discovered that the GBE
- didn't really implement its native complex-arithmetic facility properly.
- 
-    The short-term solution was to rewrite the FFE to instead use the
- lower-level facilities that'd be used by `gcc'-compiled code (assuming
- that code, itself, didn't use the native complex type provided, as an
- extension, by `gcc'), since these were known to work, and, in any case,
- if shown to not work, would likely be rapidly fixed (since they'd
- likely not work for vanilla C code in similar circumstances).
- 
-    However, the rewrite accommodated the original, native approach as
- well by offering a command-line option to select it over the emulated
- approach.  This allowed users, and especially GBE maintainers, to try
- out fixes to complex-arithmetic support in the GBE while `g77'
- continued to default to compiling more code correctly, albeit producing
- (typically) slower executables.
- 
-    As of April 1999, it appeared that the last few bugs in the GBE's
- support of its native complex-arithmetic facility were worked out.  The
- FFE was changed back to default to using that native facility, leaving
- emulation as an option.
- 
-    Later during the release cycle (which was called EGCS 1.2, but soon
- became GCC 2.95), bugs in the native facility were found.  Reactions
- among various people included "the last thing we should do is change
- the default back", "we must change the default back", and "let's figure
- out whether we can narrow down the bugs to few enough cases to allow
- the now-months-long-tested default to remain the same".  The latter
- viewpoint won that particular time.  The bugs exposed other concerns
- regarding ABI compliance when the ABI specified treatment of complex
- data as different from treatment of what Fortran and GNU C consider the
- equivalent aggregation (structure) of real (or float) pairs.
- 
-    Other Fortran constructs--arrays, character strings, complex
- division, `COMMON' and `EQUIVALENCE' aggregates, and so on--involve
- issues similar to those pertaining to complex arithmetic.
- 
-    So, it is possible that the history of how the FFE handled complex
- arithmetic will be repeated, probably in modified form (and hopefully
- over shorter timeframes), for some of these other facilities.
- 
- 
- File: g77.info,  Node: Two-pass Design,  Next: Challenges Posed,  Prev: Philosophy of Code Generation,  Up: Front End
- 
- Two-pass Design
- ===============
- 
-    The FFE does not tell the GBE anything about a program unit until
- after the last statement in that unit has been parsed.  (A program unit
- is a Fortran concept that corresponds, in the C world, mostly closely
- to functions definitions in ISO C.  That is, a program unit in Fortran
- is like a top-level function in C.  Nested functions, found among the
- extensions offered by GNU C, correspond roughly to Fortran's statement
- functions.)
- 
-    So, while parsing the code in a program unit, the FFE saves up all
- the information on statements, expressions, names, and so on, until it
- has seen the last statement.
- 
-    At that point, the FFE revisits the saved information (in what
- amounts to a second "pass" over the program unit) to perform the actual
- translation of the program unit into GBEL, ultimating in the generation
- of assembly code for it.
- 
-    Some lookahead is performed during this second pass, so the FFE
- could be viewed as a "two-plus-pass" design.
- 
- * Menu:
- 
- * Two-pass Code::
- * Why Two Passes::
- 
- 
- File: g77.info,  Node: Two-pass Code,  Next: Why Two Passes,  Up: Two-pass Design
- 
- Two-pass Code
- -------------
- 
-    Most of the code that turns the first pass (parsing) into a second
- pass for code generation is in `gcc/gcc/f/std.c'.
- 
-    It has external functions, called mainly by siblings in
- `gcc/gcc/f/stc.c', that record the information on statements and
- expressions in the order they are seen in the source code.  These
- functions save that information.
- 
-    It also has an external function that revisits that information,
- calling the siblings in `gcc/gcc/f/ste.c', which handles the actual
- code generation (by generating GBEL code, that is, by calling GBE
- routines to represent and specify expressions, statements, and so on).
- 
- 
- File: g77.info,  Node: Why Two Passes,  Prev: Two-pass Code,  Up: Two-pass Design
- 
- Why Two Passes
- --------------
- 
-    The need for two passes was not immediately evident during the
- design and implementation of the code in the FFE that was to produce
- GBEL.  Only after a few kludges, to handle things like
- incorrectly-guessed `ASSIGN' label nature, had been implemented, did
- enough evidence pile up to make it clear that `std.c' had to be
- introduced to intercept, save, then revisit as part of a second pass,
- the digested contents of a program unit.
- 
-    Other such missteps have occurred during the evolution of the FFE,
- because of the different goals of the FFE and the GBE.
- 
-    Because the GBE's original, and still primary, goal was to directly
- support the GNU C language, the GBEL, and the GBE itself, requires more
- complexity on the part of most front ends than it requires of `gcc''s.
- 
-    For example, the GBEL offers an interface that permits the `gcc'
- front end to implement most, or all, of the language features it
- supports, without the front end having to make use of non-user-defined
- variables.  (It's almost certainly the case that all of K&R C, and
- probably ANSI C as well, is handled by the `gcc' front end without
- declaring such variables.)
- 
-    The FFE, on the other hand, must resort to a variety of "tricks" to
- achieve its goals.
- 
-    Consider the following C code:
- 
-      int
-      foo (int a, int b)
-      {
-        int c = 0;
-      
-        if ((c = bar (c)) == 0)
-          goto done;
-      
-        quux (c << 1);
-      
-      done:
-        return c;
-      }
- 
-    Note what kinds of objects are declared, or defined, before their
- use, and before any actual code generation involving them would
- normally take place:
- 
-    * Return type of function
- 
-    * Entry point(s) of function
- 
-    * Dummy arguments
- 
-    * Variables
- 
-    * Initial values for variables
- 
-    Whereas, the following items can, and do, suddenly appear "out of
- the blue" in C:
- 
-    * Label references
- 
-    * Function references
- 
-    Not surprisingly, the GBE faithfully permits the latter set of items
- to be "discovered" partway through GBEL "programs", just as they are
- permitted to in C.
- 
-    Yet, the GBE has tended, at least in the past, to be reticent to
- fully support similar "late" discovery of items in the former set.
- 
-    This makes Fortran a poor fit for the "safe" subset of GBEL.
- Consider:
- 
-            FUNCTION X (A, ARRAY, ID1)
-            CHARACTER*(*) A
-            DOUBLE PRECISION X, Y, Z, TMP, EE, PI
-            REAL ARRAY(ID1*ID2)
-            COMMON ID2
-            EXTERNAL FRED
-      
-            ASSIGN 100 TO J
-            CALL FOO (I)
-            IF (I .EQ. 0) PRINT *, A(0)
-            GOTO 200
-      
-            ENTRY Y (Z)
-            ASSIGN 101 TO J
-      200   PRINT *, A(1)
-            READ *, TMP
-            GOTO J
-      100   X = TMP * EE
-            RETURN
-      101   Y = TMP * PI
-            CALL FRED
-            DATA EE, PI /2.71D0, 3.14D0/
-            END
- 
-    Here are some observations about the above code, which, while
- somewhat contrived, conforms to the FORTRAN 77 and Fortran 90 standards:
- 
-    * The return type of function `X' is not known until the `DOUBLE
-      PRECISION' line has been parsed.
- 
-    * Whether `A' is a function or a variable is not known until the
-      `PRINT *, A(0)' statement has been parsed.
- 
-    * The bounds of the array of argument `ARRAY' depend on a
-      computation involving the subsequent argument `ID1' and the
-      blank-common member `ID2'.
- 
-    * Whether `Y' and `Z' are local variables, additional function entry
-      points, or dummy arguments to additional entry points is not known
-      until the `ENTRY' statement is parsed.
- 
-    * Similarly, whether `TMP' is a local variable is not known until
-      the `READ *, TMP' statement is parsed.
- 
-    * The initial values for `EE' and `PI' are not known until after the
-      `DATA' statement is parsed.
- 
-    * Whether `FRED' is a function returning type `REAL' or a subroutine
-      (which can be thought of as returning type `void' _or_, to support
-      alternate returns in a simple way, type `int') is not known until
-      the `CALL FRED' statement is parsed.
- 
-    * Whether `100' is a `FORMAT' label or the label of an executable
-      statement is not known until the `X =' statement is parsed.
-      (These two types of labels get _very_ different treatment,
-      especially when `ASSIGN''ed.)
- 
-    * That `J' is a local variable is not known until the first `ASSIGN'
-      statement is parsed.  (This happens _after_ executable code has
-      been seen.)
- 
-    Very few of these "discoveries" can be accommodated by the GBE as it
- has evolved over the years.  The GBEL doesn't support several of them,
- and those it might appear to support don't always work properly,
- especially in combination with other GBEL and GBE features, as
- implemented in the GBE.
- 
-    (Had the GBE and its GBEL originally evolved to support `g77', the
- shoe would be on the other foot, so to speak--most, if not all, of the
- above would be directly supported by the GBEL, and a few C constructs
- would probably not, as they are in reality, be supported.  Both this
- mythical, and today's real, GBE caters to its GBEL by, sometimes,
- scrambling around, cleaning up after itself--after discovering that
- assumptions it made earlier during code generation are incorrect.
- That's not a great design, since it indicates significant code paths
- that might be rarely tested but used in some key production
- environments.)
- 
-    So, the FFE handles these discrepancies--between the order in which
- it discovers facts about the code it is compiling, and the order in
- which the GBEL and GBE support such discoveries--by performing what
- amounts to two passes over each program unit.
- 
-    (A few ambiguities can remain at that point, such as whether, given
- `EXTERNAL BAZ' and no other reference to `BAZ' in the program unit, it
- is a subroutine, a function, or a block-data--which, in C-speak,
- governs its declared return type.  Fortunately, these distinctions are
- easily finessed for the procedure, library, and object-file interfaces
- supported by `g77'.)
- 
- 
- File: g77.info,  Node: Challenges Posed,  Next: Transforming Statements,  Prev: Two-pass Design,  Up: Front End
- 
- Challenges Posed
- ================
- 
-    Consider the following Fortran code, which uses various extensions
- (including some to Fortran 90):
- 
-      SUBROUTINE X(A)
-      CHARACTER*(*) A
-      COMPLEX CFUNC
-      INTEGER*2 CLOCKS(200)
-      INTEGER IFUNC
-      
-      CALL SYSTEM_CLOCK (CLOCKS (IFUNC (CFUNC ('('//A//')'))))
- 
-    The above poses the following challenges to any Fortran compiler
- that uses run-time interfaces, and a run-time library, roughly similar
- to those used by `g77':
- 
-    * Assuming the library routine that supports `SYSTEM_CLOCK' expects
-      to set an `INTEGER*4' variable via its `COUNT' argument, the
-      compiler must make available to it a temporary variable of that
-      type.
- 
-    * Further, after the `SYSTEM_CLOCK' library routine returns, the
-      compiler must ensure that the temporary variable it wrote is
-      copied into the appropriate element of the `CLOCKS' array.  (This
-      assumes the compiler doesn't just reject the code, which it should
-      if it is compiling under some kind of a "strict" option.)
- 
-    * To determine the correct index into the `CLOCKS' array, (putting
-      aside the fact that the index, in this particular case, need not
-      be computed until after the `SYSTEM_CLOCK' library routine
-      returns), the compiler must ensure that the `IFUNC' function is
-      called.
- 
-      That requires evaluating its argument, which requires, for `g77'
-      (assuming `-ff2c' is in force), reserving a temporary variable of
-      type `COMPLEX' for use as a repository for the return value being
-      computed by `CFUNC'.
- 
-    * Before invoking `CFUNC', is argument must be evaluated, which
-      requires allocating, at run time, a temporary large enough to hold
-      the result of the concatenation, as well as actually performing
-      the concatenation.
- 
-    * The large temporary needed during invocation of `CFUNC' should,
-      ideally, be deallocated (or, at least, left to the GBE to dispose
-      of, as it sees fit) as soon as `CFUNC' returns, which means before
-      `IFUNC' is called (as it might need a lot of dynamically allocated
-      memory).
- 
-    `g77' currently doesn't support all of the above, but, so that it
- might someday, it has evolved to handle at least some of the above
- requirements.
- 
-    Meeting the above requirements is made more challenging by
- conforming to the requirements of the GBEL/GBE combination.
- 
- 
- File: g77.info,  Node: Transforming Statements,  Next: Transforming Expressions,  Prev: Challenges Posed,  Up: Front End
- 
- Transforming Statements
- =======================
- 
-    Most Fortran statements are given their own block, and, for
- temporary variables they might need, their own scope.  (A block is what
- distinguishes `{ foo (); }' from just `foo ();' in C.  A scope is
- included with every such block, providing a distinct name space for
- local variables.)
- 
-    Label definitions for the statement precede this block, so `10 PRINT
- *, I' is handled more like `fl10: { ... }' than `{ fl10: ... }' (where
- `fl10' is just a notation meaning "Fortran Label 10" for the purposes
- of this document).
- 
- * Menu:
- 
- * Statements Needing Temporaries::
- * Transforming DO WHILE::
- * Transforming Iterative DO::
- * Transforming Block IF::
- * Transforming SELECT CASE::
- 
- 
- File: g77.info,  Node: Statements Needing Temporaries,  Next: Transforming DO WHILE,  Up: Transforming Statements
- 
- Statements Needing Temporaries
- ------------------------------
- 
-    Any temporaries needed during, but not beyond, execution of a
- Fortran statement, are made local to the scope of that statement's
- block.
- 
-    This allows the GBE to share storage for these temporaries among the
- various statements without the FFE having to manage that itself.
- 
-    (The GBE could, of course, decide to optimize management of these
- temporaries.  For example, it could, theoretically, schedule some of
- the computations involving these temporaries to occur in parallel.
- More practically, it might leave the storage for some temporaries
- "live" beyond their scopes, to reduce the number of manipulations of
- the stack pointer at run time.)
- 
-    Temporaries needed across distinct statement boundaries usually are
- associated with Fortran blocks (such as `DO'/`END DO').  (Also, there
- might be temporaries not associated with blocks at all--these would be
- in the scope of the entire program unit.)
- 
-    Each Fortran block _should_ get its own block/scope in the GBE.
- This is best, because it allows temporaries to be more naturally
- handled.  However, it might pose problems when handling labels (in
- particular, when they're the targets of `GOTO's outside the Fortran
- block), and generally just hassling with replicating parts of the `gcc'
- front end (because the FFE needs to support an arbitrary number of
- nested back-end blocks if each Fortran block gets one).
- 
-    So, there might still be a need for top-level temporaries, whose
- "owning" scope is that of the containing procedure.
- 
-    Also, there seems to be problems declaring new variables after
- generating code (within a block) in the back end, leading to, e.g.,
- `label not defined before binding contour' or similar messages, when
- compiling with `-fstack-check' or when compiling for certain targets.
- 
-    Because of that, and because sometimes these temporaries are not
- discovered until in the middle of of generating code for an expression
- statement (as in the case of the optimization for `X**I'), it seems
- best to always pre-scan all the expressions that'll be expanded for a
- block before generating any of the code for that block.
- 
-    This pre-scan then handles discovering and declaring, to the back
- end, the temporaries needed for that block.
- 
-    It's also important to treat distinct items in an I/O list as
- distinct statements deserving their own blocks.  That's because there's
- a requirement that each I/O item be fully processed before the next one,
- which matters in cases like `READ (*,*), I, A(I)'--the element of `A'
- read in the second item _must_ be determined from the value of `I' read
- in the first item.
- 
- 
- File: g77.info,  Node: Transforming DO WHILE,  Next: Transforming Iterative DO,  Prev: Statements Needing Temporaries,  Up: Transforming Statements
- 
- Transforming DO WHILE
- ---------------------
- 
-    `DO WHILE(expr)' _must_ be implemented so that temporaries needed to
- evaluate `expr' are generated just for the test, each time.
- 
-    Consider how `DO WHILE (A//B .NE. 'END'); ...; END DO' is
- transformed:
- 
-      for (;;)
-        {
-          int temp0;
-      
-          {
-            char temp1[large];
-      
-            libg77_catenate (temp1, a, b);
-            temp0 = libg77_ne (temp1, 'END');
-          }
-      
-          if (! temp0)
-            break;
-      
-          ...
-        }
- 
-    In this case, it seems like a time/space tradeoff between allocating
- and deallocating `temp1' for each iteration and allocating it just once
- for the entire loop.
- 
-    However, if `temp1' is allocated just once for the entire loop, it
- could be the wrong size for subsequent iterations of that loop in cases
- like `DO WHILE (A(I:J)//B .NE. 'END')', because the body of the loop
- might modify `I' or `J'.
- 
-    So, the above implementation is used, though a more optimal one can
- be used in specific circumstances.
- 
- 
- File: g77.info,  Node: Transforming Iterative DO,  Next: Transforming Block IF,  Prev: Transforming DO WHILE,  Up: Transforming Statements
- 
- Transforming Iterative DO
- -------------------------
- 
-    An iterative `DO' loop (one that specifies an iteration variable) is
- required by the Fortran standards to be implemented as though an
- iteration count is computed before entering the loop body, and that
- iteration count used to determine the number of times the loop body is
- to be performed (assuming the loop isn't cut short via `GOTO' or
- `EXIT').
- 
-    The FFE handles this by allocating a temporary variable to contain
- the computed number of iterations.  Since this variable must be in a
- scope that includes the entire loop, a GBEL block is created for that
- loop, and the variable declared as belonging to the scope of that block.
- 
- 
- File: g77.info,  Node: Transforming Block IF,  Next: Transforming SELECT CASE,  Prev: Transforming Iterative DO,  Up: Transforming Statements
- 
- Transforming Block IF
- ---------------------
- 
-    Consider:
- 
-      SUBROUTINE X(A,B,C)
-      CHARACTER*(*) A, B, C
-      LOGICAL LFUNC
-      
-      IF (LFUNC (A//B)) THEN
-        CALL SUBR1
-      ELSE IF (LFUNC (A//C)) THEN
-        CALL SUBR2
-      ELSE
-        CALL SUBR3
-      END
- 
-    The arguments to the two calls to `LFUNC' require dynamic allocation
- (at run time), but are not required during execution of the `CALL'
- statements.
- 
-    So, the scopes of those temporaries must be within blocks inside the
- block corresponding to the Fortran `IF' block.
- 
-    This cannot be represented "naturally" in vanilla C, nor in GBEL.
- The `if', `elseif', `else', and `endif' constructs provided by both
- languages must, for a given `if' block, share the same C/GBE block.
- 
-    Therefore, any temporaries needed during evaluation of `expr' while
- executing `ELSE IF(expr)' must either have been predeclared at the top
- of the corresponding `IF' block, or declared within a new block for
- that `ELSE IF'--a block that, since it cannot contain the `else' or
- `else if' itself (due to the above requirement), actually implements
- the rest of the `IF' block's `ELSE IF' and `ELSE' statements within an
- inner block.
- 
-    The FFE takes the latter approach.
- 
- 
- File: g77.info,  Node: Transforming SELECT CASE,  Prev: Transforming Block IF,  Up: Transforming Statements
- 
- Transforming SELECT CASE
- ------------------------
- 
-    `SELECT CASE' poses a few interesting problems for code generation,
- if efficiency and frugal stack management are important.
- 
-    Consider `SELECT CASE (I('PREFIX'//A))', where `A' is
- `CHARACTER*(*)'.  In a case like this--basically, in any case where
- largish temporaries are needed to evaluate the expression--those
- temporaries should not be "live" during execution of any of the `CASE'
- blocks.
- 
-    So, evaluation of the expression is best done within its own block,
- which in turn is within the `SELECT CASE' block itself (which contains
- the code for the CASE blocks as well, though each within their own
- block).
- 
-    Otherwise, we'd have the rough equivalent of this pseudo-code:
- 
-      {
-        char temp[large];
-      
-        libg77_catenate (temp, 'prefix', a);
-      
-        switch (i (temp))
-          {
-          case 0:
-            ...
-          }
-      }
- 
-    And that would leave temp[large] in scope during the CASE blocks
- (although a clever back end *could* see that it isn't referenced in
- them, and thus free that temp before executing the blocks).
- 
-    So this approach is used instead:
- 
-      {
-        int temp0;
-      
-        {
-          char temp1[large];
-      
-          libg77_catenate (temp1, 'prefix', a);
-          temp0 = i (temp1);
-        }
-      
-        switch (temp0)
-          {
-          case 0:
-            ...
-          }
-      }
- 
-    Note how `temp1' goes out of scope before starting the switch, thus
- making it easy for a back end to free it.
- 
-    The problem _that_ solution has, however, is with `SELECT
- CASE('prefix'//A)' (which is currently not supported).
- 
-    Unless the GBEL is extended to support arbitrarily long character
- strings in its `case' facility, the FFE has to implement `SELECT CASE'
- on `CHARACTER' (probably excepting `CHARACTER*1') using a cascade of
- `if', `elseif', `else', and `endif' constructs in GBEL.
- 
-    To prevent the (potentially large) temporary, needed to hold the
- selected expression itself (`'prefix'//A'), from being in scope during
- execution of the `CASE' blocks, two approaches are available:
- 
-    * Pre-evaluate all the `CASE' tests, producing an integer ordinal
-      that is used, a la `temp0' in the earlier example, as if `SELECT
-      CASE(temp0)' had been written.
- 
-      Each corresponding `CASE' is replaced with `CASE(I)', where I is
-      the ordinal for that case, determined while, or before, generating
-      the cascade of `if'-related constructs to cope with `CHARACTER'
-      selection.
- 
-    * Make `temp0' above just large enough to hold the longest `CASE'
-      string that'll actually be compared against the expression (in
-      this case, `'prefix'//A').
- 
-      Since that length must be constant (because `CASE' expressions are
-      all constant), it won't be so large, and, further, `temp1' need
-      not be dynamically allocated, since normal `CHARACTER' assignment
-      can be used into the fixed-length `temp0'.
- 
-    Both of these solutions require `SELECT CASE' implementation to be
- changed so all the corresponding `CASE' statements are seen during the
- actual code generation for `SELECT CASE'.
- 
- 
- File: g77.info,  Node: Transforming Expressions,  Next: Internal Naming Conventions,  Prev: Transforming Statements,  Up: Front End
- 
- Transforming Expressions
- ========================
- 
-    The interactions between statements, expressions, and subexpressions
- at program run time can be viewed as:
- 
-      ACTION(EXPR)
- 
-    Here, ACTION is the series of steps performed to effect the
- statement, and EXPR is the expression whose value is used by ACTION.
- 
-    Expanding the above shows a typical order of events at run time:
- 
-      Evaluate EXPR
-      Perform ACTION, using result of evaluation of EXPR
-      Clean up after evaluating EXPR
- 
-    So, if evaluating EXPR requires allocating memory, that memory can
- be freed before performing ACTION only if it is not needed to hold the
- result of evaluating EXPR.  Otherwise, it must be freed no sooner than
- after ACTION has been performed.
- 
-    The above are recursive definitions, in the sense that they apply to
- subexpressions of EXPR.
- 
-    That is, evaluating EXPR involves evaluating all of its
- subexpressions, performing the ACTION that computes the result value of
- EXPR, then cleaning up after evaluating those subexpressions.
- 
-    The recursive nature of this evaluation is implemented via
- recursive-descent transformation of the top-level statements, their
- expressions, _their_ subexpressions, and so on.
- 
-    However, that recursive-descent transformation is, due to the nature
- of the GBEL, focused primarily on generating a _single_ stream of code
- to be executed at run time.
- 
-    Yet, from the above, it's clear that multiple streams of code must
- effectively be simultaneously generated during the recursive-descent
- analysis of statements.
- 
-    The primary stream implements the primary ACTION items, while at
- least two other streams implement the evaluation and clean-up items.
- 
-    Requirements imposed by expressions include:
- 
-    * Whether the caller needs to have a temporary ready to hold the
-      value of the expression.
- 
-    * Other stuff???
- 
- 
- File: g77.info,  Node: Internal Naming Conventions,  Prev: Transforming Expressions,  Up: Front End
- 
- Internal Naming Conventions
- ===========================
- 
-    Names exported by FFE modules have the following
- (regular-expression) forms.  Note that all names beginning `ffeMOD' or
- `FFEMOD', where MOD is lowercase or uppercase alphanumerics,
- respectively, are exported by the module `ffeMOD', with the source code
- doing the exporting in `MOD.h'.  (Usually, the source code for the
- implementation is in `MOD.c'.)
- 
-    Identifiers that don't fit the following forms are not considered
- exported, even if they are according to the C language.  (For example,
- they might be made available to other modules solely for use within
- expansions of exported macros, not for use within any source code in
- those other modules.)
- 
- `ffeMOD'
-      The single typedef exported by the module.
- 
- `FFEUMOD_[A-Z][A-Z0-9_]*'
-      (Where UMOD is the uppercase for of MOD.)
- 
-      A `#define' or `enum' constant of the type `ffeMOD'.
- 
- `ffeMOD[A-Z][A-Z][a-z0-9]*'
-      A typedef exported by the module.
- 
-      The portion of the identifier after `ffeMOD' is referred to as
-      `ctype', a capitalized (mixed-case) form of `type'.
- 
- `FFEUMOD_TYPE[A-Z][A-Z0-9_]*[A-Z0-9]?'
-      (Where UMOD is the uppercase for of MOD.)
- 
-      A `#define' or `enum' constant of the type `ffeMODTYPE', where
-      TYPE is the lowercase form of CTYPE in an exported typedef.
- 
- `ffeMOD_VALUE'
-      A function that does or returns something, as described by VALUE
-      (see below).
- 
- `ffeMOD_VALUE_INPUT'
-      A function that does or returns something based primarily on the
-      thing described by INPUT (see below).
- 
-    Below are names used for VALUE and INPUT, along with their
- definitions.
- 
- `col'
-      A column number within a line (first column is number 1).
- 
- `file'
-      An encapsulation of a file's name.
- 
- `find'
-      Looks up an instance of some type that matches specified criteria,
-      and returns that, even if it has to create a new instance or crash
-      trying to find it (as appropriate).
- 
- `initialize'
-      Initializes, usually a module.  No type.
- 
- `int'
-      A generic integer of type `int'.
- 
- `is'
-      A generic integer that contains a true (non-zero) or false (zero)
-      value.
- 
- `len'
-      A generic integer that contains the length of something.
- 
- `line'
-      A line number within a source file, or a global line number.
- 
- `lookup'
-      Looks up an instance of some type that matches specified criteria,
-      and returns that, or returns nil.
- 
- `name'
-      A `text' that points to a name of something.
- 
- `new'
-      Makes a new instance of the indicated type.  Might return an
-      existing one if appropriate--if so, similar to `find' without
-      crashing.
- 
- `pt'
-      Pointer to a particular character (line, column pairs) in the
-      input file (source code being compiled).
- 
- `run'
-      Performs some herculean task.  No type.
- 
- `terminate'
-      Terminates, usually a module.  No type.
- 
- `text'
-      A `char *' that points to generic text.
- 
- 
- File: g77.info,  Node: Diagnostics,  Next: Index,  Prev: Front End,  Up: Top
- 
- Diagnostics
- ***********
- 
-    Some diagnostics produced by `g77' require sufficient explanation
- that the explanations are given below, and the diagnostics themselves
- identify the appropriate explanation.
- 
-    Identification uses the GNU Info format--specifically, the `info'
- command that displays the explanation is given within square brackets
- in the diagnostic.  For example:
- 
-      foo.f:5: Invalid statement [info -f g77 M FOOEY]
- 
-    More details about the above diagnostic is found in the `g77' Info
- documentation, menu item `M', submenu item `FOOEY', which is displayed
- by typing the UNIX command `info -f g77 M FOOEY'.
- 
-    Other Info readers, such as EMACS, may be just as easily used to
- display the pertinent node.  In the above example, `g77' is the Info
- document name, `M' is the top-level menu item to select, and, in that
- node (named `Diagnostics', the name of this chapter, which is the very
- text you're reading now), `FOOEY' is the menu item to select.
- 
- * Menu:
- 
- * CMPAMBIG::    Ambiguous use of intrinsic.
- * EXPIMP::      Intrinsic used explicitly and implicitly.
- * INTGLOB::     Intrinsic also used as name of global.
- * LEX::         Various lexer messages
- * GLOBALS::     Disagreements about globals.
- * LINKFAIL::    When linking `f771' fails.
- * Y2KBAD::      Use of non-Y2K-compliant intrinsic.
- 
--- 0 ----
diff -Nrc3pad gcc-3.2.3/gcc/f/g77.info-2 gcc-3.3/gcc/f/g77.info-2
*** gcc-3.2.3/gcc/f/g77.info-2	2003-04-22 07:07:23.000000000 +0000
--- gcc-3.3/gcc/f/g77.info-2	1970-01-01 00:00:00.000000000 +0000
***************
*** 1,1234 ****
- This is g77.info, produced by makeinfo version 4.5 from g77.texi.
- 
- INFO-DIR-SECTION Programming
- START-INFO-DIR-ENTRY
- * g77: (g77).                  The GNU Fortran compiler.
- END-INFO-DIR-ENTRY
-    This file documents the use and the internals of the GNU Fortran
- (`g77') compiler.  It corresponds to the GCC-3.2.3 version of `g77'.
- 
-    Published by the Free Software Foundation 59 Temple Place - Suite 330
- Boston, MA 02111-1307 USA
- 
-    Copyright (C) 1995,1996,1997,1998,1999,2000,2001,2002 Free Software
- Foundation, Inc.
- 
-    Permission is granted to copy, distribute and/or modify this document
- under the terms of the GNU Free Documentation License, Version 1.1 or
- any later version published by the Free Software Foundation; with the
- Invariant Sections being "GNU General Public License" and "Funding Free
- Software", the Front-Cover texts being (a) (see below), and with the
- Back-Cover Texts being (b) (see below).  A copy of the license is
- included in the section entitled "GNU Free Documentation License".
- 
-    (a) The FSF's Front-Cover Text is:
- 
-    A GNU Manual
- 
-    (b) The FSF's Back-Cover Text is:
- 
-    You have freedom to copy and modify this GNU Manual, like GNU
- software.  Copies published by the Free Software Foundation raise
- funds for GNU development.
- 
-    Contributed by James Craig Burley (<craig@jcb-sc.com>).  Inspired by
- a first pass at translating `g77-0.5.16/f/DOC' that was contributed to
- Craig by David Ronis (<ronis@onsager.chem.mcgill.ca>).
- 
- 
- File: g77.info,  Node: Getting Started,  Next: What is GNU Fortran?,  Prev: Funding GNU Fortran,  Up: Top
- 
- Getting Started
- ***************
- 
-    If you don't need help getting started reading the portions of this
- manual that are most important to you, you should skip this portion of
- the manual.
- 
-    If you are new to compilers, especially Fortran compilers, or new to
- how compilers are structured under UNIX and UNIX-like systems, you'll
- want to see *Note What is GNU Fortran?::.
- 
-    If you are new to GNU compilers, or have used only one GNU compiler
- in the past and not had to delve into how it lets you manage various
- versions and configurations of `gcc', you should see *Note G77 and
- GCC::.
- 
-    Everyone except experienced `g77' users should see *Note Invoking
- G77::.
- 
-    If you're acquainted with previous versions of `g77', you should see
- *Note News About GNU Fortran: News.  Further, if you've actually used
- previous versions of `g77', especially if you've written or modified
- Fortran code to be compiled by previous versions of `g77', you should
- see *Note Changes::.
- 
-    If you intend to write or otherwise compile code that is not already
- strictly conforming ANSI FORTRAN 77--and this is probably everyone--you
- should see *Note Language::.
- 
-    If you run into trouble getting Fortran code to compile, link, run,
- or work properly, you might find answers if you see *Note Debugging and
- Interfacing::, see *Note Collected Fortran Wisdom::, and see *Note
- Trouble::.  You might also find that the problems you are encountering
- are bugs in `g77'--see *Note Bugs::, for information on reporting them,
- after reading the other material.
- 
-    If you need further help with `g77', or with freely redistributable
- software in general, see *Note Service::.
- 
-    If you would like to help the `g77' project, see *Note Funding GNU
- Fortran::, for information on helping financially, and see *Note
- Projects::, for information on helping in other ways.
- 
-    If you're generally curious about the future of `g77', see *Note
- Projects::.  If you're curious about its past, see *Note Contributors::,
- and see *Note Funding GNU Fortran::.
- 
-    To see a few of the questions maintainers of `g77' have, and that
- you might be able to answer, see *Note Open Questions::.
- 
- 
- File: g77.info,  Node: What is GNU Fortran?,  Next: G77 and GCC,  Prev: Getting Started,  Up: Top
- 
- What is GNU Fortran?
- ********************
- 
-    GNU Fortran, or `g77', is designed initially as a free replacement
- for, or alternative to, the UNIX `f77' command.  (Similarly, `gcc' is
- designed as a replacement for the UNIX `cc' command.)
- 
-    `g77' also is designed to fit in well with the other fine GNU
- compilers and tools.
- 
-    Sometimes these design goals conflict--in such cases, resolution
- often is made in favor of fitting in well with Project GNU.  These
- cases are usually identified in the appropriate sections of this manual.
- 
-    As compilers, `g77', `gcc', and `f77' share the following
- characteristics:
- 
-    * They read a user's program, stored in a file and containing
-      instructions written in the appropriate language (Fortran, C, and
-      so on).  This file contains "source code".
- 
-    * They translate the user's program into instructions a computer can
-      carry out more quickly than it takes to translate the instructions
-      in the first place.  These instructions are called "machine
-      code"--code designed to be efficiently translated and processed by
-      a machine such as a computer.  Humans usually aren't as good
-      writing machine code as they are at writing Fortran or C, because
-      it is easy to make tiny mistakes writing machine code.  When
-      writing Fortran or C, it is easy to make big mistakes.
- 
-    * They provide information in the generated machine code that can
-      make it easier to find bugs in the program (using a debugging
-      tool, called a "debugger", such as `gdb').
- 
-    * They locate and gather machine code already generated to perform
-      actions requested by statements in the user's program.  This
-      machine code is organized into "libraries" and is located and
-      gathered during the "link" phase of the compilation process.
-      (Linking often is thought of as a separate step, because it can be
-      directly invoked via the `ld' command.  However, the `g77' and
-      `gcc' commands, as with most compiler commands, automatically
-      perform the linking step by calling on `ld' directly, unless asked
-      to not do so by the user.)
- 
-    * They attempt to diagnose cases where the user's program contains
-      incorrect usages of the language.  The "diagnostics" produced by
-      the compiler indicate the problem and the location in the user's
-      source file where the problem was first noticed.  The user can use
-      this information to locate and fix the problem.  (Sometimes an
-      incorrect usage of the language leads to a situation where the
-      compiler can no longer make any sense of what follows--while a
-      human might be able to--and thus ends up complaining about many
-      "problems" it encounters that, in fact, stem from just one
-      problem, usually the first one reported.)
- 
-    * They attempt to diagnose cases where the user's program contains a
-      correct usage of the language, but instructs the computer to do
-      something questionable.  These diagnostics often are in the form
-      of "warnings", instead of the "errors" that indicate incorrect
-      usage of the language.
- 
-    How these actions are performed is generally under the control of
- the user.  Using command-line options, the user can specify how
- persnickety the compiler is to be regarding the program (whether to
- diagnose questionable usage of the language), how much time to spend
- making the generated machine code run faster, and so on.
- 
-    `g77' consists of several components:
- 
-    * A modified version of the `gcc' command, which also might be
-      installed as the system's `cc' command.  (In many cases, `cc'
-      refers to the system's "native" C compiler, which might be a
-      non-GNU compiler, or an older version of `gcc' considered more
-      stable or that is used to build the operating system kernel.)
- 
-    * The `g77' command itself, which also might be installed as the
-      system's `f77' command.
- 
-    * The `libg2c' run-time library.  This library contains the machine
-      code needed to support capabilities of the Fortran language that
-      are not directly provided by the machine code generated by the
-      `g77' compilation phase.
- 
-      `libg2c' is just the unique name `g77' gives to its version of
-      `libf2c' to distinguish it from any copy of `libf2c' installed
-      from `f2c' (or versions of `g77' that built `libf2c' under that
-      same name) on the system.
- 
-      The maintainer of `libf2c' currently is <dmg@bell-labs.com>.
- 
-    * The compiler itself, internally named `f771'.
- 
-      Note that `f771' does not generate machine code directly--it
-      generates "assembly code" that is a more readable form of machine
-      code, leaving the conversion to actual machine code to an
-      "assembler", usually named `as'.
- 
-    `gcc' is often thought of as "the C compiler" only, but it does more
- than that.  Based on command-line options and the names given for files
- on the command line, `gcc' determines which actions to perform,
- including preprocessing, compiling (in a variety of possible
- languages), assembling, and linking.
- 
-    For example, the command `gcc foo.c' "drives" the file `foo.c'
- through the preprocessor `cpp', then the C compiler (internally named
- `cc1'), then the assembler (usually `as'), then the linker (`ld'),
- producing an executable program named `a.out' (on UNIX systems).
- 
-    As another example, the command `gcc foo.cc' would do much the same
- as `gcc foo.c', but instead of using the C compiler named `cc1', `gcc'
- would use the C++ compiler (named `cc1plus').
- 
-    In a GNU Fortran installation, `gcc' recognizes Fortran source files
- by name just like it does C and C++ source files.  It knows to use the
- Fortran compiler named `f771', instead of `cc1' or `cc1plus', to
- compile Fortran files.
- 
-    Non-Fortran-related operation of `gcc' is generally unaffected by
- installing the GNU Fortran version of `gcc'.  However, without the
- installed version of `gcc' being the GNU Fortran version, `gcc' will
- not be able to compile and link Fortran programs--and since `g77' uses
- `gcc' to do most of the actual work, neither will `g77'!
- 
-    The `g77' command is essentially just a front-end for the `gcc'
- command.  Fortran users will normally use `g77' instead of `gcc',
- because `g77' knows how to specify the libraries needed to link with
- Fortran programs (`libg2c' and `lm').  `g77' can still compile and link
- programs and source files written in other languages, just like `gcc'.
- 
-    The command `g77 -v' is a quick way to display lots of version
- information for the various programs used to compile a typical
- preprocessed Fortran source file--this produces much more output than
- `gcc -v' currently does.  (If it produces an error message near the end
- of the output--diagnostics from the linker, usually `ld'--you might
- have an out-of-date `libf2c' that improperly handles complex
- arithmetic.)  In the output of this command, the line beginning `GNU
- Fortran Front End' identifies the version number of GNU Fortran;
- immediately preceding that line is a line identifying the version of
- `gcc' with which that version of `g77' was built.
- 
-    The `libf2c' library is distributed with GNU Fortran for the
- convenience of its users, but is not part of GNU Fortran.  It contains
- the procedures needed by Fortran programs while they are running.
- 
-    For example, while code generated by `g77' is likely to do
- additions, subtractions, and multiplications "in line"--in the actual
- compiled code--it is not likely to do trigonometric functions this way.
- 
-    Instead, operations like trigonometric functions are compiled by the
- `f771' compiler (invoked by `g77' when compiling Fortran code) into
- machine code that, when run, calls on functions in `libg2c', so
- `libg2c' must be linked with almost every useful program having any
- component compiled by GNU Fortran.  (As mentioned above, the `g77'
- command takes care of all this for you.)
- 
-    The `f771' program represents most of what is unique to GNU Fortran.
- While much of the `libg2c' component comes from the `libf2c' component
- of `f2c', a free Fortran-to-C converter distributed by Bellcore (AT&T),
- plus `libU77', provided by Dave Love, and the `g77' command is just a
- small front-end to `gcc', `f771' is a combination of two rather large
- chunks of code.
- 
-    One chunk is the so-called "GNU Back End", or GBE, which knows how
- to generate fast code for a wide variety of processors.  The same GBE
- is used by the C, C++, and Fortran compiler programs `cc1', `cc1plus',
- and `f771', plus others.  Often the GBE is referred to as the "gcc back
- end" or even just "gcc"--in this manual, the term GBE is used whenever
- the distinction is important.
- 
-    The other chunk of `f771' is the majority of what is unique about
- GNU Fortran--the code that knows how to interpret Fortran programs to
- determine what they are intending to do, and then communicate that
- knowledge to the GBE for actual compilation of those programs.  This
- chunk is called the "Fortran Front End" (FFE).  The `cc1' and `cc1plus'
- programs have their own front ends, for the C and C++ languages,
- respectively.  These fronts ends are responsible for diagnosing
- incorrect usage of their respective languages by the programs the
- process, and are responsible for most of the warnings about
- questionable constructs as well.  (The GBE handles producing some
- warnings, like those concerning possible references to undefined
- variables.)
- 
-    Because so much is shared among the compilers for various languages,
- much of the behavior and many of the user-selectable options for these
- compilers are similar.  For example, diagnostics (error messages and
- warnings) are similar in appearance; command-line options like `-Wall'
- have generally similar effects; and the quality of generated code (in
- terms of speed and size) is roughly similar (since that work is done by
- the shared GBE).
- 
- 
- File: g77.info,  Node: G77 and GCC,  Next: Invoking G77,  Prev: What is GNU Fortran?,  Up: Top
- 
- Compile Fortran, C, or Other Programs
- *************************************
- 
-    A GNU Fortran installation includes a modified version of the `gcc'
- command.
- 
-    In a non-Fortran installation, `gcc' recognizes C, C++, and
- Objective-C source files.
- 
-    In a GNU Fortran installation, `gcc' also recognizes Fortran source
- files and accepts Fortran-specific command-line options, plus some
- command-line options that are designed to cater to Fortran users but
- apply to other languages as well.
- 
-    *Note Compile C; C++; Objective-C; Ada; Fortran; or Java: (gcc)G++
- and GCC, for information on the way different languages are handled by
- the GNU CC compiler (`gcc').
- 
-    Also provided as part of GNU Fortran is the `g77' command.  The
- `g77' command is designed to make compiling and linking Fortran
- programs somewhat easier than when using the `gcc' command for these
- tasks.  It does this by analyzing the command line somewhat and
- changing it appropriately before submitting it to the `gcc' command.
- 
-    Use the `-v' option with `g77' to see what is going on--the first
- line of output is the invocation of the `gcc' command.
- 
- 
- File: g77.info,  Node: Invoking G77,  Next: News,  Prev: G77 and GCC,  Up: Top
- 
- GNU Fortran Command Options
- ***************************
- 
-    The `g77' command supports all the options supported by the `gcc'
- command.  *Note GCC Command Options: (gcc)Invoking GCC, for information
- on the non-Fortran-specific aspects of the `gcc' command (and,
- therefore, the `g77' command).
- 
-    All `gcc' and `g77' options are accepted both by `g77' and by `gcc'
- (as well as any other drivers built at the same time, such as `g++'),
- since adding `g77' to the `gcc' distribution enables acceptance of
- `g77' options by all of the relevant drivers.
- 
-    In some cases, options have positive and negative forms; the
- negative form of `-ffoo' would be `-fno-foo'.  This manual documents
- only one of these two forms, whichever one is not the default.
- 
- * Menu:
- 
- * Option Summary::      Brief list of all `g77' options,
-                         without explanations.
- * Overall Options::     Controlling the kind of output:
-                         an executable, object files, assembler files,
-                         or preprocessed source.
- * Shorthand Options::   Options that are shorthand for other options.
- * Fortran Dialect Options::  Controlling the variant of Fortran language
-                              compiled.
- * Warning Options::     How picky should the compiler be?
- * Debugging Options::   Symbol tables, measurements, and debugging dumps.
- * Optimize Options::    How much optimization?
- * Preprocessor Options:: Controlling header files and macro definitions.
-                          Also, getting dependency information for Make.
- * Directory Options::   Where to find header files and libraries.
-                         Where to find the compiler executable files.
- * Code Gen Options::    Specifying conventions for function calls, data layout
-                         and register usage.
- * Environment Variables:: Env vars that affect GNU Fortran.
- 
- 
- File: g77.info,  Node: Option Summary,  Next: Overall Options,  Up: Invoking G77
- 
- Option Summary
- ==============
- 
-    Here is a summary of all the options specific to GNU Fortran, grouped
- by type.  Explanations are in the following sections.
- 
- _Overall Options_
-      *Note Options Controlling the Kind of Output: Overall Options.
-           -fversion  -fset-g77-defaults  -fno-silent
- 
- _Shorthand Options_
-      *Note Shorthand Options::.
-           -ff66  -fno-f66  -ff77  -fno-f77  -fno-ugly
- 
- _Fortran Language Options_
-      *Note Options Controlling Fortran Dialect: Fortran Dialect Options.
-           -ffree-form  -fno-fixed-form  -ff90 
-           -fvxt  -fdollar-ok  -fno-backslash 
-           -fno-ugly-args  -fno-ugly-assign  -fno-ugly-assumed 
-           -fugly-comma  -fugly-complex  -fugly-init  -fugly-logint 
-           -fonetrip  -ftypeless-boz 
-           -fintrin-case-initcap  -fintrin-case-upper 
-           -fintrin-case-lower  -fintrin-case-any 
-           -fmatch-case-initcap  -fmatch-case-upper 
-           -fmatch-case-lower  -fmatch-case-any 
-           -fsource-case-upper  -fsource-case-lower 
-           -fsource-case-preserve 
-           -fsymbol-case-initcap  -fsymbol-case-upper 
-           -fsymbol-case-lower  -fsymbol-case-any 
-           -fcase-strict-upper  -fcase-strict-lower 
-           -fcase-initcap  -fcase-upper  -fcase-lower  -fcase-preserve 
-           -ff2c-intrinsics-delete  -ff2c-intrinsics-hide 
-           -ff2c-intrinsics-disable  -ff2c-intrinsics-enable 
-           -fbadu77-intrinsics-delete  -fbadu77-intrinsics-hide 
-           -fbadu77-intrinsics-disable  -fbadu77-intrinsics-enable 
-           -ff90-intrinsics-delete  -ff90-intrinsics-hide 
-           -ff90-intrinsics-disable  -ff90-intrinsics-enable 
-           -fgnu-intrinsics-delete  -fgnu-intrinsics-hide 
-           -fgnu-intrinsics-disable  -fgnu-intrinsics-enable 
-           -fmil-intrinsics-delete  -fmil-intrinsics-hide 
-           -fmil-intrinsics-disable  -fmil-intrinsics-enable 
-           -funix-intrinsics-delete  -funix-intrinsics-hide 
-           -funix-intrinsics-disable  -funix-intrinsics-enable 
-           -fvxt-intrinsics-delete  -fvxt-intrinsics-hide 
-           -fvxt-intrinsics-disable  -fvxt-intrinsics-enable 
-           -ffixed-line-length-N  -ffixed-line-length-none
- 
- _Warning Options_
-      *Note Options to Request or Suppress Warnings: Warning Options.
-           -fsyntax-only  -pedantic  -pedantic-errors  -fpedantic 
-           -w  -Wno-globals  -Wimplicit  -Wunused  -Wuninitialized 
-           -Wall  -Wsurprising 
-           -Werror  -W
- 
- _Debugging Options_
-      *Note Options for Debugging Your Program or GCC: Debugging Options.
-           -g
- 
- _Optimization Options_
-      *Note Options that Control Optimization: Optimize Options.
-           -malign-double 
-           -ffloat-store  -fforce-mem  -fforce-addr  -fno-inline 
-           -ffast-math  -fstrength-reduce  -frerun-cse-after-loop 
-           -funsafe-math-optimizations -fno-trapping-math 
-           -fexpensive-optimizations  -fdelayed-branch 
-           -fschedule-insns  -fschedule-insn2  -fcaller-saves 
-           -funroll-loops  -funroll-all-loops 
-           -fno-move-all-movables  -fno-reduce-all-givs 
-           -fno-rerun-loop-opt
- 
- _Directory Options_
-      *Note Options for Directory Search: Directory Options.
-           -IDIR  -I-
- 
- _Code Generation Options_
-      *Note Options for Code Generation Conventions: Code Gen Options.
-           -fno-automatic  -finit-local-zero  -fno-f2c 
-           -ff2c-library  -fno-underscoring  -fno-ident 
-           -fpcc-struct-return  -freg-struct-return 
-           -fshort-double  -fno-common  -fpack-struct 
-           -fzeros  -fno-second-underscore 
-           -femulate-complex 
-           -falias-check  -fargument-alias 
-           -fargument-noalias  -fno-argument-noalias-global 
-           -fno-globals  -fflatten-arrays 
-           -fbounds-check  -ffortran-bounds-check
- 
- 
- * Menu:
- 
- * Overall Options::     Controlling the kind of output:
-                         an executable, object files, assembler files,
-                         or preprocessed source.
- * Shorthand Options::   Options that are shorthand for other options.
- * Fortran Dialect Options::  Controlling the variant of Fortran language
-                              compiled.
- * Warning Options::     How picky should the compiler be?
- * Debugging Options::   Symbol tables, measurements, and debugging dumps.
- * Optimize Options::    How much optimization?
- * Preprocessor Options:: Controlling header files and macro definitions.
-                          Also, getting dependency information for Make.
- * Directory Options::   Where to find header files and libraries.
-                         Where to find the compiler executable files.
- * Code Gen Options::    Specifying conventions for function calls, data layout
-                         and register usage.
- 
- 
- File: g77.info,  Node: Overall Options,  Next: Shorthand Options,  Prev: Option Summary,  Up: Invoking G77
- 
- Options Controlling the Kind of Output
- ======================================
- 
-    Compilation can involve as many as four stages: preprocessing, code
- generation (often what is really meant by the term "compilation"),
- assembly, and linking, always in that order.  The first three stages
- apply to an individual source file, and end by producing an object
- file; linking combines all the object files (those newly compiled, and
- those specified as input) into an executable file.
- 
-    For any given input file, the file name suffix determines what kind
- of program is contained in the file--that is, the language in which the
- program is written is generally indicated by the suffix.  Suffixes
- specific to GNU Fortran are listed below.  *Note Options Controlling
- the Kind of Output: (gcc)Overall Options, for information on suffixes
- recognized by GNU CC.
- 
- `FILE.f'
- 
- `FILE.for'
- 
- `FILE.FOR'
-      Fortran source code that should not be preprocessed.
- 
-      Such source code cannot contain any preprocessor directives, such
-      as `#include', `#define', `#if', and so on.
- 
-      You can force `.f' files to be preprocessed by `cpp' by using `-x
-      f77-cpp-input'.  *Note LEX::.
- 
- `FILE.F'
- 
- `FILE.fpp'
- 
- `FILE.FPP'
-      Fortran source code that must be preprocessed (by the C
-      preprocessor `cpp', which is part of GNU CC).
- 
-      Note that preprocessing is not extended to the contents of files
-      included by the `INCLUDE' directive--the `#include' preprocessor
-      directive must be used instead.
- 
- `FILE.r'
-      Ratfor source code, which must be preprocessed by the `ratfor'
-      command, which is available separately (as it is not yet part of
-      the GNU Fortran distribution).  One version in Fortran, adapted
-      for use with `g77' is at `ftp://members.aol.com/n8tm/rat7.uue' (of
-      uncertain copyright status).  Another, public domain version in C
-      is at `http://sepwww.stanford.edu/sep/prof/ratfor.shar.2'.
- 
-    UNIX users typically use the `FILE.f' and `FILE.F' nomenclature.
- Users of other operating systems, especially those that cannot
- distinguish upper-case letters from lower-case letters in their file
- names, typically use the `FILE.for' and `FILE.fpp' nomenclature.
- 
-    Use of the preprocessor `cpp' allows use of C-like constructs such
- as `#define' and `#include', but can lead to unexpected, even mistaken,
- results due to Fortran's source file format.  It is recommended that
- use of the C preprocessor be limited to `#include' and, in conjunction
- with `#define', only `#if' and related directives, thus avoiding
- in-line macro expansion entirely.  This recommendation applies
- especially when using the traditional fixed source form.  With free
- source form, fewer unexpected transformations are likely to happen, but
- use of constructs such as Hollerith and character constants can
- nevertheless present problems, especially when these are continued
- across multiple source lines.  These problems result, primarily, from
- differences between the way such constants are interpreted by the C
- preprocessor and by a Fortran compiler.
- 
-    Another example of a problem that results from using the C
- preprocessor is that a Fortran comment line that happens to contain any
- characters "interesting" to the C preprocessor, such as a backslash at
- the end of the line, is not recognized by the preprocessor as a comment
- line, so instead of being passed through "raw", the line is edited
- according to the rules for the preprocessor.  For example, the
- backslash at the end of the line is removed, along with the subsequent
- newline, resulting in the next line being effectively commented
- out--unfortunate if that line is a non-comment line of important code!
- 
-    _Note:_ The `-traditional' and `-undef' flags are supplied to `cpp'
- by default, to help avoid unpleasant surprises.  *Note Options
- Controlling the Preprocessor: (gcc)Preprocessor Options.  This means
- that ANSI C preprocessor features (such as the `#' operator) aren't
- available, and only variables in the C reserved namespace (generally,
- names with a leading underscore) are liable to substitution by C
- predefines.  Thus, if you want to do system-specific tests, use, for
- example, `#ifdef __linux__' rather than `#ifdef linux'.  Use the `-v'
- option to see exactly how the preprocessor is invoked.
- 
-    Unfortunately, the `-traditional' flag will not avoid an error from
- anything that `cpp' sees as an unterminated C comment, such as:
-      C Some Fortran compilers accept /* as starting
-      C an inline comment.
-    *Note Trailing Comment::.
- 
-    The following options that affect overall processing are recognized
- by the `g77' and `gcc' commands in a GNU Fortran installation:
- 
- `-fversion'
-      Ensure that the `g77' version of the compiler phase is reported,
-      if run, and, starting in `egcs' version 1.1, that internal
-      consistency checks in the `f771' program are run.
- 
-      This option is supplied automatically when `-v' or `--verbose' is
-      specified as a command-line option for `g77' or `gcc' and when the
-      resulting commands compile Fortran source files.
- 
-      In GCC 3.1, this is changed back to the behaviour `gcc' displays
-      for `.c' files.
- 
- `-fset-g77-defaults'
-      _Version info:_ This option was obsolete as of `egcs' version 1.1.
-      The effect is instead achieved by the `lang_init_options' routine
-      in `gcc/gcc/f/com.c'.
- 
-      Set up whatever `gcc' options are to apply to Fortran
-      compilations, and avoid running internal consistency checks that
-      might take some time.
- 
-      This option is supplied automatically when compiling Fortran code
-      via the `g77' or `gcc' command.  The description of this option is
-      provided so that users seeing it in the output of, say, `g77 -v'
-      understand why it is there.
- 
-      Also, developers who run `f771' directly might want to specify it
-      by hand to get the same defaults as they would running `f771' via
-      `g77' or `gcc' However, such developers should, after linking a
-      new `f771' executable, invoke it without this option once, e.g.
-      via `./f771 -quiet < /dev/null', to ensure that they have not
-      introduced any internal inconsistencies (such as in the table of
-      intrinsics) before proceeding--`g77' will crash with a diagnostic
-      if it detects an inconsistency.
- 
- `-fno-silent'
-      Print (to `stderr') the names of the program units as they are
-      compiled, in a form similar to that used by popular UNIX `f77'
-      implementations and `f2c'
- 
-    *Note Options Controlling the Kind of Output: (gcc)Overall Options,
- for information on more options that control the overall operation of
- the `gcc' command (and, by extension, the `g77' command).
- 
- 
- File: g77.info,  Node: Shorthand Options,  Next: Fortran Dialect Options,  Prev: Overall Options,  Up: Invoking G77
- 
- Shorthand Options
- =================
- 
-    The following options serve as "shorthand" for other options
- accepted by the compiler:
- 
- `-fugly'
-      _Note:_ This option is no longer supported.  The information,
-      below, is provided to aid in the conversion of old scripts.
- 
-      Specify that certain "ugly" constructs are to be quietly accepted.
-      Same as:
- 
-           -fugly-args -fugly-assign -fugly-assumed
-           -fugly-comma -fugly-complex -fugly-init
-           -fugly-logint
- 
-      These constructs are considered inappropriate to use in new or
-      well-maintained portable Fortran code, but widely used in old code.
-      *Note Distensions::, for more information.
- 
- `-fno-ugly'
-      Specify that all "ugly" constructs are to be noisily rejected.
-      Same as:
- 
-           -fno-ugly-args -fno-ugly-assign -fno-ugly-assumed
-           -fno-ugly-comma -fno-ugly-complex -fno-ugly-init
-           -fno-ugly-logint
- 
-      *Note Distensions::, for more information.
- 
- `-ff66'
-      Specify that the program is written in idiomatic FORTRAN 66.  Same
-      as `-fonetrip -fugly-assumed'.
- 
-      The `-fno-f66' option is the inverse of `-ff66'.  As such, it is
-      the same as `-fno-onetrip -fno-ugly-assumed'.
- 
-      The meaning of this option is likely to be refined as future
-      versions of `g77' provide more compatibility with other existing
-      and obsolete Fortran implementations.
- 
- `-ff77'
-      Specify that the program is written in idiomatic UNIX FORTRAN 77
-      and/or the dialect accepted by the `f2c' product.  Same as
-      `-fbackslash -fno-typeless-boz'.
- 
-      The meaning of this option is likely to be refined as future
-      versions of `g77' provide more compatibility with other existing
-      and obsolete Fortran implementations.
- 
- `-fno-f77'
-      The `-fno-f77' option is _not_ the inverse of `-ff77'.  It
-      specifies that the program is not written in idiomatic UNIX
-      FORTRAN 77 or `f2c' but in a more widely portable dialect.
-      `-fno-f77' is the same as `-fno-backslash'.
- 
-      The meaning of this option is likely to be refined as future
-      versions of `g77' provide more compatibility with other existing
-      and obsolete Fortran implementations.
- 
- 
- File: g77.info,  Node: Fortran Dialect Options,  Next: Warning Options,  Prev: Shorthand Options,  Up: Invoking G77
- 
- Options Controlling Fortran Dialect
- ===================================
- 
-    The following options control the dialect of Fortran that the
- compiler accepts:
- 
- `-ffree-form'
- 
- `-fno-fixed-form'
-      Specify that the source file is written in free form (introduced
-      in Fortran 90) instead of the more-traditional fixed form.
- 
- `-ff90'
-      Allow certain Fortran-90 constructs.
- 
-      This option controls whether certain Fortran 90 constructs are
-      recognized.  (Other Fortran 90 constructs might or might not be
-      recognized depending on other options such as `-fvxt',
-      `-ff90-intrinsics-enable', and the current level of support for
-      Fortran 90.)
- 
-      *Note Fortran 90::, for more information.
- 
- `-fvxt'
-      Specify the treatment of certain constructs that have different
-      meanings depending on whether the code is written in GNU Fortran
-      (based on FORTRAN 77 and akin to Fortran 90) or VXT Fortran (more
-      like VAX FORTRAN).
- 
-      The default is `-fno-vxt'.  `-fvxt' specifies that the VXT Fortran
-      interpretations for those constructs are to be chosen.
- 
-      *Note VXT Fortran::, for more information.
- 
- `-fdollar-ok'
-      Allow `$' as a valid character in a symbol name.
- 
- `-fno-backslash'
-      Specify that `\' is not to be specially interpreted in character
-      and Hollerith constants a la C and many UNIX Fortran compilers.
- 
-      For example, with `-fbackslash' in effect, `A\nB' specifies three
-      characters, with the second one being newline.  With
-      `-fno-backslash', it specifies four characters, `A', `\', `n', and
-      `B'.
- 
-      Note that `g77' implements a fairly general form of backslash
-      processing that is incompatible with the narrower forms supported
-      by some other compilers.  For example, `'A\003B'' is a
-      three-character string in `g77' whereas other compilers that
-      support backslash might not support the three-octal-digit form,
-      and thus treat that string as longer than three characters.
- 
-      *Note Backslash in Constants::, for information on why
-      `-fbackslash' is the default instead of `-fno-backslash'.
- 
- `-fno-ugly-args'
-      Disallow passing Hollerith and typeless constants as actual
-      arguments (for example, `CALL FOO(4HABCD)').
- 
-      *Note Ugly Implicit Argument Conversion::, for more information.
- 
- `-fugly-assign'
-      Use the same storage for a given variable regardless of whether it
-      is used to hold an assigned-statement label (as in `ASSIGN 10 TO
-      I') or used to hold numeric data (as in `I = 3').
- 
-      *Note Ugly Assigned Labels::, for more information.
- 
- `-fugly-assumed'
-      Assume any dummy array with a final dimension specified as `1' is
-      really an assumed-size array, as if `*' had been specified for the
-      final dimension instead of `1'.
- 
-      For example, `DIMENSION X(1)' is treated as if it had read
-      `DIMENSION X(*)'.
- 
-      *Note Ugly Assumed-Size Arrays::, for more information.
- 
- `-fugly-comma'
-      In an external-procedure invocation, treat a trailing comma in the
-      argument list as specification of a trailing null argument, and
-      treat an empty argument list as specification of a single null
-      argument.
- 
-      For example, `CALL FOO(,)' is treated as `CALL FOO(%VAL(0),
-      %VAL(0))'.  That is, _two_ null arguments are specified by the
-      procedure call when `-fugly-comma' is in force.  And `F = FUNC()'
-      is treated as `F = FUNC(%VAL(0))'.
- 
-      The default behavior, `-fno-ugly-comma', is to ignore a single
-      trailing comma in an argument list.  So, by default, `CALL
-      FOO(X,)' is treated exactly the same as `CALL FOO(X)'.
- 
-      *Note Ugly Null Arguments::, for more information.
- 
- `-fugly-complex'
-      Do not complain about `REAL(EXPR)' or `AIMAG(EXPR)' when EXPR is a
-      `COMPLEX' type other than `COMPLEX(KIND=1)'--usually this is used
-      to permit `COMPLEX(KIND=2)' (`DOUBLE COMPLEX') operands.
- 
-      The `-ff90' option controls the interpretation of this construct.
- 
-      *Note Ugly Complex Part Extraction::, for more information.
- 
- `-fno-ugly-init'
-      Disallow use of Hollerith and typeless constants as initial values
-      (in `PARAMETER' and `DATA' statements), and use of character
-      constants to initialize numeric types and vice versa.
- 
-      For example, `DATA I/'F'/, CHRVAR/65/, J/4HABCD/' is disallowed by
-      `-fno-ugly-init'.
- 
-      *Note Ugly Conversion of Initializers::, for more information.
- 
- `-fugly-logint'
-      Treat `INTEGER' and `LOGICAL' variables and expressions as
-      potential stand-ins for each other.
- 
-      For example, automatic conversion between `INTEGER' and `LOGICAL'
-      is enabled, for many contexts, via this option.
- 
-      *Note Ugly Integer Conversions::, for more information.
- 
- `-fonetrip'
-      Executable iterative `DO' loops are to be executed at least once
-      each time they are reached.
- 
-      ANSI FORTRAN 77 and more recent versions of the Fortran standard
-      specify that the body of an iterative `DO' loop is not executed if
-      the number of iterations calculated from the parameters of the
-      loop is less than 1.  (For example, `DO 10 I = 1, 0'.)  Such a
-      loop is called a "zero-trip loop".
- 
-      Prior to ANSI FORTRAN 77, many compilers implemented `DO' loops
-      such that the body of a loop would be executed at least once, even
-      if the iteration count was zero.  Fortran code written assuming
-      this behavior is said to require "one-trip loops".  For example,
-      some code written to the FORTRAN 66 standard expects this behavior
-      from its `DO' loops, although that standard did not specify this
-      behavior.
- 
-      The `-fonetrip' option specifies that the source file(s) being
-      compiled require one-trip loops.
- 
-      This option affects only those loops specified by the (iterative)
-      `DO' statement and by implied-`DO' lists in I/O statements.  Loops
-      specified by implied-`DO' lists in `DATA' and specification
-      (non-executable) statements are not affected.
- 
- `-ftypeless-boz'
-      Specifies that prefix-radix non-decimal constants, such as
-      `Z'ABCD'', are typeless instead of `INTEGER(KIND=1)'.
- 
-      You can test for yourself whether a particular compiler treats the
-      prefix form as `INTEGER(KIND=1)' or typeless by running the
-      following program:
- 
-           EQUIVALENCE (I, R)
-           R = Z'ABCD1234'
-           J = Z'ABCD1234'
-           IF (J .EQ. I) PRINT *, 'Prefix form is TYPELESS'
-           IF (J .NE. I) PRINT *, 'Prefix form is INTEGER'
-           END
- 
-      Reports indicate that many compilers process this form as
-      `INTEGER(KIND=1)', though a few as typeless, and at least one
-      based on a command-line option specifying some kind of
-      compatibility.
- 
- `-fintrin-case-initcap'
- 
- `-fintrin-case-upper'
- 
- `-fintrin-case-lower'
- 
- `-fintrin-case-any'
-      Specify expected case for intrinsic names.  `-fintrin-case-lower'
-      is the default.
- 
- `-fmatch-case-initcap'
- 
- `-fmatch-case-upper'
- 
- `-fmatch-case-lower'
- 
- `-fmatch-case-any'
-      Specify expected case for keywords.  `-fmatch-case-lower' is the
-      default.
- 
- `-fsource-case-upper'
- 
- `-fsource-case-lower'
- 
- `-fsource-case-preserve'
-      Specify whether source text other than character and Hollerith
-      constants is to be translated to uppercase, to lowercase, or
-      preserved as is.  `-fsource-case-lower' is the default.
- 
- `-fsymbol-case-initcap'
- 
- `-fsymbol-case-upper'
- 
- `-fsymbol-case-lower'
- 
- `-fsymbol-case-any'
-      Specify valid cases for user-defined symbol names.
-      `-fsymbol-case-any' is the default.
- 
- `-fcase-strict-upper'
-      Same as `-fintrin-case-upper -fmatch-case-upper
-      -fsource-case-preserve -fsymbol-case-upper'.  (Requires all
-      pertinent source to be in uppercase.)
- 
- `-fcase-strict-lower'
-      Same as `-fintrin-case-lower -fmatch-case-lower
-      -fsource-case-preserve -fsymbol-case-lower'.  (Requires all
-      pertinent source to be in lowercase.)
- 
- `-fcase-initcap'
-      Same as `-fintrin-case-initcap -fmatch-case-initcap
-      -fsource-case-preserve -fsymbol-case-initcap'.  (Requires all
-      pertinent source to be in initial capitals, as in `Print
-      *,SqRt(Value)'.)
- 
- `-fcase-upper'
-      Same as `-fintrin-case-any -fmatch-case-any -fsource-case-upper
-      -fsymbol-case-any'.  (Maps all pertinent source to uppercase.)
- 
- `-fcase-lower'
-      Same as `-fintrin-case-any -fmatch-case-any -fsource-case-lower
-      -fsymbol-case-any'.  (Maps all pertinent source to lowercase.)
- 
- `-fcase-preserve'
-      Same as `-fintrin-case-any -fmatch-case-any -fsource-case-preserve
-      -fsymbol-case-any'.  (Preserves all case in user-defined symbols,
-      while allowing any-case matching of intrinsics and keywords.  For
-      example, `call Foo(i,I)' would pass two _different_ variables
-      named `i' and `I' to a procedure named `Foo'.)
- 
- `-fbadu77-intrinsics-delete'
- 
- `-fbadu77-intrinsics-hide'
- 
- `-fbadu77-intrinsics-disable'
- 
- `-fbadu77-intrinsics-enable'
-      Specify status of UNIX intrinsics having inappropriate forms.
-      `-fbadu77-intrinsics-enable' is the default.  *Note Intrinsic
-      Groups::.
- 
- `-ff2c-intrinsics-delete'
- 
- `-ff2c-intrinsics-hide'
- 
- `-ff2c-intrinsics-disable'
- 
- `-ff2c-intrinsics-enable'
-      Specify status of f2c-specific intrinsics.
-      `-ff2c-intrinsics-enable' is the default.  *Note Intrinsic
-      Groups::.
- 
- `-ff90-intrinsics-delete'
- 
- `-ff90-intrinsics-hide'
- 
- `-ff90-intrinsics-disable'
- 
- `-ff90-intrinsics-enable'
-      Specify status of F90-specific intrinsics.
-      `-ff90-intrinsics-enable' is the default.  *Note Intrinsic
-      Groups::.
- 
- `-fgnu-intrinsics-delete'
- 
- `-fgnu-intrinsics-hide'
- 
- `-fgnu-intrinsics-disable'
- 
- `-fgnu-intrinsics-enable'
-      Specify status of Digital's COMPLEX-related intrinsics.
-      `-fgnu-intrinsics-enable' is the default.  *Note Intrinsic
-      Groups::.
- 
- `-fmil-intrinsics-delete'
- 
- `-fmil-intrinsics-hide'
- 
- `-fmil-intrinsics-disable'
- 
- `-fmil-intrinsics-enable'
-      Specify status of MIL-STD-1753-specific intrinsics.
-      `-fmil-intrinsics-enable' is the default.  *Note Intrinsic
-      Groups::.
- 
- `-funix-intrinsics-delete'
- 
- `-funix-intrinsics-hide'
- 
- `-funix-intrinsics-disable'
- 
- `-funix-intrinsics-enable'
-      Specify status of UNIX intrinsics.  `-funix-intrinsics-enable' is
-      the default.  *Note Intrinsic Groups::.
- 
- `-fvxt-intrinsics-delete'
- 
- `-fvxt-intrinsics-hide'
- 
- `-fvxt-intrinsics-disable'
- 
- `-fvxt-intrinsics-enable'
-      Specify status of VXT intrinsics.  `-fvxt-intrinsics-enable' is
-      the default.  *Note Intrinsic Groups::.
- 
- `-ffixed-line-length-N'
-      Set column after which characters are ignored in typical fixed-form
-      lines in the source file, and through which spaces are assumed (as
-      if padded to that length) after the ends of short fixed-form lines.
- 
-      Popular values for N include 72 (the standard and the default), 80
-      (card image), and 132 (corresponds to "extended-source" options in
-      some popular compilers).  N may be `none', meaning that the entire
-      line is meaningful and that continued character constants never
-      have implicit spaces appended to them to fill out the line.
-      `-ffixed-line-length-0' means the same thing as
-      `-ffixed-line-length-none'.
- 
-      *Note Source Form::, for more information.
- 
- 
- File: g77.info,  Node: Warning Options,  Next: Debugging Options,  Prev: Fortran Dialect Options,  Up: Invoking G77
- 
- Options to Request or Suppress Warnings
- =======================================
- 
-    Warnings are diagnostic messages that report constructions which are
- not inherently erroneous but which are risky or suggest there might
- have been an error.
- 
-    You can request many specific warnings with options beginning `-W',
- for example `-Wimplicit' to request warnings on implicit declarations.
- Each of these specific warning options also has a negative form
- beginning `-Wno-' to turn off warnings; for example, `-Wno-implicit'.
- This manual lists only one of the two forms, whichever is not the
- default.
- 
-    These options control the amount and kinds of warnings produced by
- GNU Fortran:
- 
- `-fsyntax-only'
-      Check the code for syntax errors, but don't do anything beyond
-      that.
- 
- `-pedantic'
-      Issue warnings for uses of extensions to ANSI FORTRAN 77.
-      `-pedantic' also applies to C-language constructs where they occur
-      in GNU Fortran source files, such as use of `\e' in a character
-      constant within a directive like `#include'.
- 
-      Valid ANSI FORTRAN 77 programs should compile properly with or
-      without this option.  However, without this option, certain GNU
-      extensions and traditional Fortran features are supported as well.
-      With this option, many of them are rejected.
- 
-      Some users try to use `-pedantic' to check programs for strict ANSI
-      conformance.  They soon find that it does not do quite what they
-      want--it finds some non-ANSI practices, but not all.  However,
-      improvements to `g77' in this area are welcome.
- 
- `-pedantic-errors'
-      Like `-pedantic', except that errors are produced rather than
-      warnings.
- 
- `-fpedantic'
-      Like `-pedantic', but applies only to Fortran constructs.
- 
- `-w'
-      Inhibit all warning messages.
- 
- `-Wno-globals'
-      Inhibit warnings about use of a name as both a global name (a
-      subroutine, function, or block data program unit, or a common
-      block) and implicitly as the name of an intrinsic in a source file.
- 
-      Also inhibit warnings about inconsistent invocations and/or
-      definitions of global procedures (function and subroutines).  Such
-      inconsistencies include different numbers of arguments and
-      different types of arguments.
- 
- `-Wimplicit'
-      Warn whenever a variable, array, or function is implicitly
-      declared.  Has an effect similar to using the `IMPLICIT NONE'
-      statement in every program unit.  (Some Fortran compilers provide
-      this feature by an option named `-u' or `/WARNINGS=DECLARATIONS'.)
- 
- `-Wunused'
-      Warn whenever a variable is unused aside from its declaration.
- 
- `-Wuninitialized'
-      Warn whenever an automatic variable is used without first being
-      initialized.
- 
-      These warnings are possible only in optimizing compilation,
-      because they require data-flow information that is computed only
-      when optimizing.  If you don't specify `-O', you simply won't get
-      these warnings.
- 
-      These warnings occur only for variables that are candidates for
-      register allocation.  Therefore, they do not occur for a variable
-      whose address is taken, or whose size is other than 1, 2, 4 or 8
-      bytes.  Also, they do not occur for arrays, even when they are in
-      registers.
- 
-      Note that there might be no warning about a variable that is used
-      only to compute a value that itself is never used, because such
-      computations may be deleted by data-flow analysis before the
-      warnings are printed.
- 
-      These warnings are made optional because GNU Fortran is not smart
-      enough to see all the reasons why the code might be correct
-      despite appearing to have an error.  Here is one example of how
-      this can happen:
- 
-           SUBROUTINE DISPAT(J)
-           IF (J.EQ.1) I=1
-           IF (J.EQ.2) I=4
-           IF (J.EQ.3) I=5
-           CALL FOO(I)
-           END
- 
-      If the value of `J' is always 1, 2 or 3, then `I' is always
-      initialized, but GNU Fortran doesn't know this.  Here is another
-      common case:
- 
-           SUBROUTINE MAYBE(FLAG)
-           LOGICAL FLAG
-           IF (FLAG) VALUE = 9.4
-           ...
-           IF (FLAG) PRINT *, VALUE
-           END
- 
-      This has no bug because `VALUE' is used only if it is set.
- 
- `-Wall'
-      The `-Wunused' and `-Wuninitialized' options combined.  These are
-      all the options which pertain to usage that we recommend avoiding
-      and that we believe is easy to avoid.  (As more warnings are added
-      to `g77' some might be added to the list enabled by `-Wall'.)
- 
-    The remaining `-W...' options are not implied by `-Wall' because
- they warn about constructions that we consider reasonable to use, on
- occasion, in clean programs.
- 
- `-Wsurprising'
-      Warn about "suspicious" constructs that are interpreted by the
-      compiler in a way that might well be surprising to someone reading
-      the code.  These differences can result in subtle,
-      compiler-dependent (even machine-dependent) behavioral differences.
-      The constructs warned about include:
- 
-         * Expressions having two arithmetic operators in a row, such as
-           `X*-Y'.  Such a construct is nonstandard, and can produce
-           unexpected results in more complicated situations such as
-           `X**-Y*Z'.  `g77' along with many other compilers, interprets
-           this example differently than many programmers, and a few
-           other compilers.  Specifically, `g77' interprets `X**-Y*Z' as
-           `(X**(-Y))*Z', while others might think it should be
-           interpreted as `X**(-(Y*Z))'.
- 
-           A revealing example is the constant expression `2**-2*1.',
-           which `g77' evaluates to .25, while others might evaluate it
-           to 0., the difference resulting from the way precedence
-           affects type promotion.
- 
-           (The `-fpedantic' option also warns about expressions having
-           two arithmetic operators in a row.)
- 
-         * Expressions with a unary minus followed by an operand and then
-           a binary operator other than plus or minus.  For example,
-           `-2**2' produces a warning, because the precedence is
-           `-(2**2)', yielding -4, not `(-2)**2', which yields 4, and
-           which might represent what a programmer expects.
- 
-           An example of an expression producing different results in a
-           surprising way is `-I*S', where I holds the value
-           `-2147483648' and S holds `0.5'.  On many systems, negating I
-           results in the same value, not a positive number, because it
-           is already the lower bound of what an `INTEGER(KIND=1)'
-           variable can hold.  So, the expression evaluates to a
-           positive number, while the "expected" interpretation,
-           `(-I)*S', would evaluate to a negative number.
- 
-           Even cases such as `-I*J' produce warnings, even though, in
-           most configurations and situations, there is no computational
-           difference between the results of the two
-           interpretations--the purpose of this warning is to warn about
-           differing interpretations and encourage a better style of
-           coding, not to identify only those places where bugs might
-           exist in the user's code.
- 
-         * `DO' loops with `DO' variables that are not of integral
-           type--that is, using `REAL' variables as loop control
-           variables.  Although such loops can be written to work in the
-           "obvious" way, the way `g77' is required by the Fortran
-           standard to interpret such code is likely to be quite
-           different from the way many programmers expect.  (This is
-           true of all `DO' loops, but the differences are pronounced
-           for non-integral loop control variables.)
- 
-           *Note Loops::, for more information.
- 
- `-Werror'
-      Make all warnings into errors.
- 
- `-W'
-      Turns on "extra warnings" and, if optimization is specified via
-      `-O', the `-Wuninitialized' option.  (This might change in future
-      versions of `g77'
- 
-      "Extra warnings" are issued for:
- 
-         * Unused parameters to a procedure (when `-Wunused' also is
-           specified).
- 
-         * Overflows involving floating-point constants (not available
-           for certain configurations).
- 
-    *Note Options to Request or Suppress Warnings: (gcc)Warning Options,
- for information on more options offered by the GBE shared by `g77'
- `gcc' and other GNU compilers.
- 
-    Some of these have no effect when compiling programs written in
- Fortran:
- 
- `-Wcomment'
- 
- `-Wformat'
- 
- `-Wparentheses'
- 
- `-Wswitch'
- 
- `-Wtraditional'
- 
- `-Wshadow'
- 
- `-Wid-clash-LEN'
- 
- `-Wlarger-than-LEN'
- 
- `-Wconversion'
- 
- `-Waggregate-return'
- 
- `-Wredundant-decls'
-      These options all could have some relevant meaning for GNU Fortran
-      programs, but are not yet supported.
- 
--- 0 ----
diff -Nrc3pad gcc-3.2.3/gcc/f/g77.info-20 gcc-3.3/gcc/f/g77.info-20
*** gcc-3.2.3/gcc/f/g77.info-20	2003-04-22 07:07:25.000000000 +0000
--- gcc-3.3/gcc/f/g77.info-20	1970-01-01 00:00:00.000000000 +0000
***************
*** 1,511 ****
- This is g77.info, produced by makeinfo version 4.5 from g77.texi.
- 
- INFO-DIR-SECTION Programming
- START-INFO-DIR-ENTRY
- * g77: (g77).                  The GNU Fortran compiler.
- END-INFO-DIR-ENTRY
-    This file documents the use and the internals of the GNU Fortran
- (`g77') compiler.  It corresponds to the GCC-3.2.3 version of `g77'.
- 
-    Published by the Free Software Foundation 59 Temple Place - Suite 330
- Boston, MA 02111-1307 USA
- 
-    Copyright (C) 1995,1996,1997,1998,1999,2000,2001,2002 Free Software
- Foundation, Inc.
- 
-    Permission is granted to copy, distribute and/or modify this document
- under the terms of the GNU Free Documentation License, Version 1.1 or
- any later version published by the Free Software Foundation; with the
- Invariant Sections being "GNU General Public License" and "Funding Free
- Software", the Front-Cover texts being (a) (see below), and with the
- Back-Cover Texts being (b) (see below).  A copy of the license is
- included in the section entitled "GNU Free Documentation License".
- 
-    (a) The FSF's Front-Cover Text is:
- 
-    A GNU Manual
- 
-    (b) The FSF's Back-Cover Text is:
- 
-    You have freedom to copy and modify this GNU Manual, like GNU
- software.  Copies published by the Free Software Foundation raise
- funds for GNU development.
- 
-    Contributed by James Craig Burley (<craig@jcb-sc.com>).  Inspired by
- a first pass at translating `g77-0.5.16/f/DOC' that was contributed to
- Craig by David Ronis (<ronis@onsager.chem.mcgill.ca>).
- 
- 
- File: g77.info,  Node: CMPAMBIG,  Next: EXPIMP,  Up: Diagnostics
- 
- `CMPAMBIG'
- ==========
- 
-      Ambiguous use of intrinsic INTRINSIC ...
- 
-    The type of the argument to the invocation of the INTRINSIC
- intrinsic is a `COMPLEX' type other than `COMPLEX(KIND=1)'.  Typically,
- it is `COMPLEX(KIND=2)', also known as `DOUBLE COMPLEX'.
- 
-    The interpretation of this invocation depends on the particular
- dialect of Fortran for which the code was written.  Some dialects
- convert the real part of the argument to `REAL(KIND=1)', thus losing
- precision; other dialects, and Fortran 90, do no such conversion.
- 
-    So, GNU Fortran rejects such invocations except under certain
- circumstances, to avoid making an incorrect assumption that results in
- generating the wrong code.
- 
-    To determine the dialect of the program unit, perhaps even whether
- that particular invocation is properly coded, determine how the result
- of the intrinsic is used.
- 
-    The result of INTRINSIC is expected (by the original programmer) to
- be `REAL(KIND=1)' (the non-Fortran-90 interpretation) if:
- 
-    * It is passed as an argument to a procedure that explicitly or
-      implicitly declares that argument `REAL(KIND=1)'.
- 
-      For example, a procedure with no `DOUBLE PRECISION' or `IMPLICIT
-      DOUBLE PRECISION' statement specifying the dummy argument
-      corresponding to an actual argument of `REAL(Z)', where `Z' is
-      declared `DOUBLE COMPLEX', strongly suggests that the programmer
-      expected `REAL(Z)' to return `REAL(KIND=1)' instead of
-      `REAL(KIND=2)'.
- 
-    * It is used in a context that would otherwise not include any
-      `REAL(KIND=2)' but where treating the INTRINSIC invocation as
-      `REAL(KIND=2)' would result in unnecessary promotions and
-      (typically) more expensive operations on the wider type.
- 
-      For example:
- 
-           DOUBLE COMPLEX Z
-           ...
-           R(1) = T * REAL(Z)
- 
-      The above example suggests the programmer expected the real part
-      of `Z' to be converted to `REAL(KIND=1)' before being multiplied
-      by `T' (presumed, along with `R' above, to be type `REAL(KIND=1)').
- 
-      Otherwise, the conversion would have to be delayed until after the
-      multiplication, requiring not only an extra conversion (of `T' to
-      `REAL(KIND=2)'), but a (typically) more expensive multiplication
-      (a double-precision multiplication instead of a single-precision
-      one).
- 
-    The result of INTRINSIC is expected (by the original programmer) to
- be `REAL(KIND=2)' (the Fortran 90 interpretation) if:
- 
-    * It is passed as an argument to a procedure that explicitly or
-      implicitly declares that argument `REAL(KIND=2)'.
- 
-      For example, a procedure specifying a `DOUBLE PRECISION' dummy
-      argument corresponding to an actual argument of `REAL(Z)', where
-      `Z' is declared `DOUBLE COMPLEX', strongly suggests that the
-      programmer expected `REAL(Z)' to return `REAL(KIND=2)' instead of
-      `REAL(KIND=1)'.
- 
-    * It is used in an expression context that includes other
-      `REAL(KIND=2)' operands, or is assigned to a `REAL(KIND=2)'
-      variable or array element.
- 
-      For example:
- 
-           DOUBLE COMPLEX Z
-           DOUBLE PRECISION R, T
-           ...
-           R(1) = T * REAL(Z)
- 
-      The above example suggests the programmer expected the real part
-      of `Z' to _not_ be converted to `REAL(KIND=1)' by the `REAL()'
-      intrinsic.
- 
-      Otherwise, the conversion would have to be immediately followed by
-      a conversion back to `REAL(KIND=2)', losing the original, full
-      precision of the real part of `Z', before being multiplied by `T'.
- 
-    Once you have determined whether a particular invocation of INTRINSIC
- expects the Fortran 90 interpretation, you can:
- 
-    * Change it to `DBLE(EXPR)' (if INTRINSIC is `REAL') or
-      `DIMAG(EXPR)' (if INTRINSIC is `AIMAG') if it expected the Fortran
-      90 interpretation.
- 
-      This assumes EXPR is `COMPLEX(KIND=2)'--if it is some other type,
-      such as `COMPLEX*32', you should use the appropriate intrinsic,
-      such as the one to convert to `REAL*16' (perhaps `DBLEQ()' in
-      place of `DBLE()', and `QIMAG()' in place of `DIMAG()').
- 
-    * Change it to `REAL(INTRINSIC(EXPR))', otherwise.  This converts to
-      `REAL(KIND=1)' in all working Fortran compilers.
- 
-    If you don't want to change the code, and you are certain that all
- ambiguous invocations of INTRINSIC in the source file have the same
- expectation regarding interpretation, you can:
- 
-    * Compile with the `g77' option `-ff90', to enable the Fortran 90
-      interpretation.
- 
-    * Compile with the `g77' options `-fno-f90 -fugly-complex', to
-      enable the non-Fortran-90 interpretations.
- 
-    *Note REAL() and AIMAG() of Complex::, for more information on this
- issue.
- 
-    Note: If the above suggestions don't produce enough evidence as to
- whether a particular program expects the Fortran 90 interpretation of
- this ambiguous invocation of INTRINSIC, there is one more thing you can
- try.
- 
-    If you have access to most or all the compilers used on the program
- to create successfully tested and deployed executables, read the
- documentation for, and _also_ test out, each compiler to determine how
- it treats the INTRINSIC intrinsic in this case.  (If all the compilers
- don't agree on an interpretation, there might be lurking bugs in the
- deployed versions of the program.)
- 
-    The following sample program might help:
- 
-            PROGRAM JCB003
-      C
-      C Written by James Craig Burley 1997-02-23.
-      C
-      C Determine how compilers handle non-standard REAL
-      C and AIMAG on DOUBLE COMPLEX operands.
-      C
-            DOUBLE COMPLEX Z
-            REAL R
-            Z = (3.3D0, 4.4D0)
-            R = Z
-            CALL DUMDUM(Z, R)
-            R = REAL(Z) - R
-            IF (R .NE. 0.) PRINT *, 'REAL() is Fortran 90'
-            IF (R .EQ. 0.) PRINT *, 'REAL() is not Fortran 90'
-            R = 4.4D0
-            CALL DUMDUM(Z, R)
-            R = AIMAG(Z) - R
-            IF (R .NE. 0.) PRINT *, 'AIMAG() is Fortran 90'
-            IF (R .EQ. 0.) PRINT *, 'AIMAG() is not Fortran 90'
-            END
-      C
-      C Just to make sure compiler doesn't use naive flow
-      C analysis to optimize away careful work above,
-      C which might invalidate results....
-      C
-            SUBROUTINE DUMDUM(Z, R)
-            DOUBLE COMPLEX Z
-            REAL R
-            END
- 
-    If the above program prints contradictory results on a particular
- compiler, run away!
- 
- 
- File: g77.info,  Node: EXPIMP,  Next: INTGLOB,  Prev: CMPAMBIG,  Up: Diagnostics
- 
- `EXPIMP'
- ========
- 
-      Intrinsic INTRINSIC referenced ...
- 
-    The INTRINSIC is explicitly declared in one program unit in the
- source file and implicitly used as an intrinsic in another program unit
- in the same source file.
- 
-    This diagnostic is designed to catch cases where a program might
- depend on using the name INTRINSIC as an intrinsic in one program unit
- and as a global name (such as the name of a subroutine or function) in
- another, but `g77' recognizes the name as an intrinsic in both cases.
- 
-    After verifying that the program unit making implicit use of the
- intrinsic is indeed written expecting the intrinsic, add an `INTRINSIC
- INTRINSIC' statement to that program unit to prevent this warning.
- 
-    This and related warnings are disabled by using the `-Wno-globals'
- option when compiling.
- 
-    Note that this warning is not issued for standard intrinsics.
- Standard intrinsics include those described in the FORTRAN 77 standard
- and, if `-ff90' is specified, those described in the Fortran 90
- standard.  Such intrinsics are not as likely to be confused with user
- procedures as intrinsics provided as extensions to the standard by
- `g77'.
- 
- 
- File: g77.info,  Node: INTGLOB,  Next: LEX,  Prev: EXPIMP,  Up: Diagnostics
- 
- `INTGLOB'
- =========
- 
-      Same name `INTRINSIC' given ...
- 
-    The name INTRINSIC is used for a global entity (a common block or a
- program unit) in one program unit and implicitly used as an intrinsic
- in another program unit.
- 
-    This diagnostic is designed to catch cases where a program intends
- to use a name entirely as a global name, but `g77' recognizes the name
- as an intrinsic in the program unit that references the name, a
- situation that would likely produce incorrect code.
- 
-    For example:
- 
-      INTEGER FUNCTION TIME()
-      ...
-      END
-      ...
-      PROGRAM SAMP
-      INTEGER TIME
-      PRINT *, 'Time is ', TIME()
-      END
- 
-    The above example defines a program unit named `TIME', but the
- reference to `TIME' in the main program unit `SAMP' is normally treated
- by `g77' as a reference to the intrinsic `TIME()' (unless a
- command-line option that prevents such treatment has been specified).
- 
-    As a result, the program `SAMP' will _not_ invoke the `TIME'
- function in the same source file.
- 
-    Since `g77' recognizes `libU77' procedures as intrinsics, and since
- some existing code uses the same names for its own procedures as used
- by some `libU77' procedures, this situation is expected to arise often
- enough to make this sort of warning worth issuing.
- 
-    After verifying that the program unit making implicit use of the
- intrinsic is indeed written expecting the intrinsic, add an `INTRINSIC
- INTRINSIC' statement to that program unit to prevent this warning.
- 
-    Or, if you believe the program unit is designed to invoke the
- program-defined procedure instead of the intrinsic (as recognized by
- `g77'), add an `EXTERNAL INTRINSIC' statement to the program unit that
- references the name to prevent this warning.
- 
-    This and related warnings are disabled by using the `-Wno-globals'
- option when compiling.
- 
-    Note that this warning is not issued for standard intrinsics.
- Standard intrinsics include those described in the FORTRAN 77 standard
- and, if `-ff90' is specified, those described in the Fortran 90
- standard.  Such intrinsics are not as likely to be confused with user
- procedures as intrinsics provided as extensions to the standard by
- `g77'.
- 
- 
- File: g77.info,  Node: LEX,  Next: GLOBALS,  Prev: INTGLOB,  Up: Diagnostics
- 
- `LEX'
- =====
- 
-      Unrecognized character ...
-      Invalid first character ...
-      Line too long ...
-      Non-numeric character ...
-      Continuation indicator ...
-      Label at ... invalid with continuation line indicator ...
-      Character constant ...
-      Continuation line ...
-      Statement at ... begins with invalid token
- 
-    Although the diagnostics identify specific problems, they can be
- produced when general problems such as the following occur:
- 
-    * The source file contains something other than Fortran code.
- 
-      If the code in the file does not look like many of the examples
-      elsewhere in this document, it might not be Fortran code.  (Note
-      that Fortran code often is written in lower case letters, while
-      the examples in this document use upper case letters, for
-      stylistic reasons.)
- 
-      For example, if the file contains lots of strange-looking
-      characters, it might be APL source code; if it contains lots of
-      parentheses, it might be Lisp source code; if it contains lots of
-      bugs, it might be C++ source code.
- 
-    * The source file contains free-form Fortran code, but `-ffree-form'
-      was not specified on the command line to compile it.
- 
-      Free form is a newer form for Fortran code.  The older, classic
-      form is called fixed form.
- 
-      Fixed-form code is visually fairly distinctive, because numerical
-      labels and comments are all that appear in the first five columns
-      of a line, the sixth column is reserved to denote continuation
-      lines, and actual statements start at or beyond column 7.  Spaces
-      generally are not significant, so if you see statements such as
-      `REALX,Y' and `DO10I=1,100', you are looking at fixed-form code.
-      Comment lines are indicated by the letter `C' or the symbol `*' in
-      column 1.  (Some code uses `!' or `/*' to begin in-line comments,
-      which many compilers support.)
- 
-      Free-form code is distinguished from fixed-form source primarily
-      by the fact that statements may start anywhere.  (If lots of
-      statements start in columns 1 through 6, that's a strong indicator
-      of free-form source.)  Consecutive keywords must be separated by
-      spaces, so `REALX,Y' is not valid, while `REAL X,Y' is.  There are
-      no comment lines per se, but `!' starts a comment anywhere in a
-      line (other than within a character or Hollerith constant).
- 
-      *Note Source Form::, for more information.
- 
-    * The source file is in fixed form and has been edited without
-      sensitivity to the column requirements.
- 
-      Statements in fixed-form code must be entirely contained within
-      columns 7 through 72 on a given line.  Starting them "early" is
-      more likely to result in diagnostics than finishing them "late",
-      though both kinds of errors are often caught at compile time.
- 
-      For example, if the following code fragment is edited by following
-      the commented instructions literally, the result, shown afterward,
-      would produce a diagnostic when compiled:
- 
-           C On XYZZY systems, remove "C" on next line:
-           C     CALL XYZZY_RESET
- 
-      The result of editing the above line might be:
- 
-           C On XYZZY systems, remove "C" on next line:
-                CALL XYZZY_RESET
- 
-      However, that leaves the first `C' in the `CALL' statement in
-      column 6, making it a comment line, which is not really what the
-      author intended, and which is likely to result in one of the
-      above-listed diagnostics.
- 
-      _Replacing_ the `C' in column 1 with a space is the proper change
-      to make, to ensure the `CALL' keyword starts in or after column 7.
- 
-      Another common mistake like this is to forget that fixed-form
-      source lines are significant through only column 72, and that,
-      normally, any text beyond column 72 is ignored or is diagnosed at
-      compile time.
- 
-      *Note Source Form::, for more information.
- 
-    * The source file requires preprocessing, and the preprocessing is
-      not being specified at compile time.
- 
-      A source file containing lines beginning with `#define',
-      `#include', `#if', and so on is likely one that requires
-      preprocessing.
- 
-      If the file's suffix is `.f', `.for', or `.FOR', the file normally
-      will be compiled _without_ preprocessing by `g77'.
- 
-      Change the file's suffix from `.f' to `.F' (or, on systems with
-      case-insensitive file names, to `.fpp' or `.FPP'), from `.for' to
-      `.fpp', or from `.FOR' to `.FPP'.  `g77' compiles files with such
-      names _with_ preprocessing.
- 
-      Or, learn how to use `gcc''s `-x' option to specify the language
-      `f77-cpp-input' for Fortran files that require preprocessing.
-      *Note Options Controlling the Kind of Output: (gcc)Overall Options.
- 
-    * The source file is preprocessed, and the results of preprocessing
-      result in syntactic errors that are not necessarily obvious to
-      someone examining the source file itself.
- 
-      Examples of errors resulting from preprocessor macro expansion
-      include exceeding the line-length limit, improperly starting,
-      terminating, or incorporating the apostrophe or double-quote in a
-      character constant, improperly forming a Hollerith constant, and
-      so on.
- 
-      *Note Options Controlling the Kind of Output: Overall Options, for
-      suggestions about how to use, and not use, preprocessing for
-      Fortran code.
- 
- 
- File: g77.info,  Node: GLOBALS,  Next: LINKFAIL,  Prev: LEX,  Up: Diagnostics
- 
- `GLOBALS'
- =========
- 
-      Global name NAME defined at ... already defined...
-      Global name NAME at ... has different type...
-      Too many arguments passed to NAME at ...
-      Too few arguments passed to NAME at ...
-      Argument #N of NAME is ...
- 
-    These messages all identify disagreements about the global procedure
- named NAME among different program units (usually including NAME
- itself).
- 
-    Whether a particular disagreement is reported as a warning or an
- error can depend on the relative order of the disagreeing portions of
- the source file.
- 
-    Disagreements between a procedure invocation and the _subsequent_
- procedure itself are, usually, diagnosed as errors when the procedure
- itself _precedes_ the invocation.  Other disagreements are diagnosed
- via warnings.
- 
-    This distinction, between warnings and errors, is due primarily to
- the present tendency of the `gcc' back end to inline only those
- procedure invocations that are _preceded_ by the corresponding
- procedure definitions.  If the `gcc' back end is changed to inline
- "forward references", in which invocations precede definitions, the
- `g77' front end will be changed to treat both orderings as errors,
- accordingly.
- 
-    The sorts of disagreements that are diagnosed by `g77' include
- whether a procedure is a subroutine or function; if it is a function,
- the type of the return value of the procedure; the number of arguments
- the procedure accepts; and the type of each argument.
- 
-    Disagreements regarding global names among program units in a
- Fortran program _should_ be fixed in the code itself.  However, if that
- is not immediately practical, and the code has been working for some
- time, it is possible it will work when compiled with the `-fno-globals'
- option.
- 
-    The `-fno-globals' option causes these diagnostics to all be warnings
- and disables all inlining of references to global procedures (to avoid
- subsequent compiler crashes and bad-code generation).  Use of the
- `-Wno-globals' option as well as `-fno-globals' suppresses all of these
- diagnostics.  (`-Wno-globals' by itself disables only the warnings, not
- the errors.)
- 
-    After using `-fno-globals' to work around these problems, it is wise
- to stop using that option and address them by fixing the Fortran code,
- because such problems, while they might not actually result in bugs on
- some systems, indicate that the code is not as portable as it could be.
- In particular, the code might appear to work on a particular system,
- but have bugs that affect the reliability of the data without
- exhibiting any other outward manifestations of the bugs.
- 
- 
- File: g77.info,  Node: LINKFAIL,  Next: Y2KBAD,  Prev: GLOBALS,  Up: Diagnostics
- 
- `LINKFAIL'
- ==========
- 
- On AIX 4.1, `g77' might not build with the native (non-GNU) tools due
- to a linker bug in coping with the `-bbigtoc' option which leads to a
- `Relocation overflow' error.  The GNU linker is not recommended on
- current AIX versions, though; it was developed under a now-unsupported
- version.  This bug is said to be fixed by `update PTF U455193 for APAR
- IX75823'.
- 
-    Compiling with `-mminimal-toc' might solve this problem, e.g. by
- adding
-      BOOT_CFLAGS='-mminimal-toc -O2 -g'
-    to the `make bootstrap' command line.
- 
- 
- File: g77.info,  Node: Y2KBAD,  Prev: LINKFAIL,  Up: Diagnostics
- 
- `Y2KBAD'
- ========
- 
-      Intrinsic `NAME', invoked at (^), known to be non-Y2K-compliant...
- 
-    This diagnostic indicates that the specific intrinsic invoked by the
- name NAME is known to have an interface that is not Year-2000 (Y2K)
- compliant.
- 
-    *Note Year 2000 (Y2K) Problems::.
- 
--- 0 ----
diff -Nrc3pad gcc-3.2.3/gcc/f/g77.info-21 gcc-3.3/gcc/f/g77.info-21
*** gcc-3.2.3/gcc/f/g77.info-21	2003-04-22 07:07:25.000000000 +0000
--- gcc-3.3/gcc/f/g77.info-21	1970-01-01 00:00:00.000000000 +0000
***************
*** 1,2269 ****
- This is g77.info, produced by makeinfo version 4.5 from g77.texi.
- 
- INFO-DIR-SECTION Programming
- START-INFO-DIR-ENTRY
- * g77: (g77).                  The GNU Fortran compiler.
- END-INFO-DIR-ENTRY
-    This file documents the use and the internals of the GNU Fortran
- (`g77') compiler.  It corresponds to the GCC-3.2.3 version of `g77'.
- 
-    Published by the Free Software Foundation 59 Temple Place - Suite 330
- Boston, MA 02111-1307 USA
- 
-    Copyright (C) 1995,1996,1997,1998,1999,2000,2001,2002 Free Software
- Foundation, Inc.
- 
-    Permission is granted to copy, distribute and/or modify this document
- under the terms of the GNU Free Documentation License, Version 1.1 or
- any later version published by the Free Software Foundation; with the
- Invariant Sections being "GNU General Public License" and "Funding Free
- Software", the Front-Cover texts being (a) (see below), and with the
- Back-Cover Texts being (b) (see below).  A copy of the license is
- included in the section entitled "GNU Free Documentation License".
- 
-    (a) The FSF's Front-Cover Text is:
- 
-    A GNU Manual
- 
-    (b) The FSF's Back-Cover Text is:
- 
-    You have freedom to copy and modify this GNU Manual, like GNU
- software.  Copies published by the Free Software Foundation raise
- funds for GNU development.
- 
-    Contributed by James Craig Burley (<craig@jcb-sc.com>).  Inspired by
- a first pass at translating `g77-0.5.16/f/DOC' that was contributed to
- Craig by David Ronis (<ronis@onsager.chem.mcgill.ca>).
- 
- 
- File: g77.info,  Node: Index,  Prev: Diagnostics,  Up: Top
- 
- Index
- *****
- 
- * Menu:
- 
- * ! <1>:                                 LEX.
- * ! <2>:                                 Exclamation Point.
- * ! <3>:                                 Trailing Comment.
- * ! <4>:                                 Character Set.
- * !:                                     Statements Comments Lines.
- * ":                                     Character Set.
- * # <1>:                                 Cpp-style directives.
- * #:                                     Character Set.
- * #define:                               Overall Options.
- * #if:                                   Overall Options.
- * #include:                              Overall Options.
- * #include directive:                    Bug Reporting.
- * $:                                     Dollar Signs.
- * %:                                     Character Set.
- * %DESCR() construct:                    %DESCR().
- * %LOC() construct:                      %LOC().
- * %REF() construct:                      %REF().
- * %VAL() construct:                      %VAL().
- * &:                                     Character Set.
- * *:                                     LEX.
- * *N notation <1>:                       Compiler Types.
- * *N notation:                           Star Notation.
- * --driver option <1>:                   Changes.
- * --driver option:                       News.
- * -falias-check option <1>:              Aliasing Assumed To Work.
- * -falias-check option:                  Code Gen Options.
- * -fargument-alias option <1>:           Aliasing Assumed To Work.
- * -fargument-alias option:               Code Gen Options.
- * -fargument-noalias option <1>:         Aliasing Assumed To Work.
- * -fargument-noalias option:             Code Gen Options.
- * -fbadu77-intrinsics-delete option:     Fortran Dialect Options.
- * -fbadu77-intrinsics-disable option:    Fortran Dialect Options.
- * -fbadu77-intrinsics-enable option:     Fortran Dialect Options.
- * -fbadu77-intrinsics-hide option:       Fortran Dialect Options.
- * -fbounds-check option:                 Code Gen Options.
- * -fcaller-saves option:                 Optimize Options.
- * -fcase-initcap option:                 Fortran Dialect Options.
- * -fcase-lower option:                   Fortran Dialect Options.
- * -fcase-preserve option:                Fortran Dialect Options.
- * -fcase-strict-lower option:            Fortran Dialect Options.
- * -fcase-strict-upper option:            Fortran Dialect Options.
- * -fcase-upper option:                   Fortran Dialect Options.
- * -fdelayed-branch option:               Optimize Options.
- * -fdollar-ok option:                    Fortran Dialect Options.
- * -femulate-complex option:              Code Gen Options.
- * -fexpensive-optimizations option:      Optimize Options.
- * -ff2c-intrinsics-delete option:        Fortran Dialect Options.
- * -ff2c-intrinsics-disable option:       Fortran Dialect Options.
- * -ff2c-intrinsics-enable option:        Fortran Dialect Options.
- * -ff2c-intrinsics-hide option:          Fortran Dialect Options.
- * -ff2c-library option:                  Code Gen Options.
- * -ff66 option:                          Shorthand Options.
- * -ff77 option:                          Shorthand Options.
- * -ff90:                                 Fortran 90 Features.
- * -ff90 option:                          Fortran Dialect Options.
- * -ff90-intrinsics-delete option:        Fortran Dialect Options.
- * -ff90-intrinsics-disable option:       Fortran Dialect Options.
- * -ff90-intrinsics-enable option:        Fortran Dialect Options.
- * -ff90-intrinsics-hide option:          Fortran Dialect Options.
- * -ffast-math option:                    Optimize Options.
- * -ffixed-line-length-N option:          Fortran Dialect Options.
- * -fflatten-arrays option:               Code Gen Options.
- * -ffloat-store option:                  Optimize Options.
- * -fforce-addr option:                   Optimize Options.
- * -fforce-mem option:                    Optimize Options.
- * -ffortran-bounds-check option:         Code Gen Options.
- * -ffree-form:                           Fortran 90 Features.
- * -ffree-form option:                    Fortran Dialect Options.
- * -fgnu-intrinsics-delete option:        Fortran Dialect Options.
- * -fgnu-intrinsics-disable option:       Fortran Dialect Options.
- * -fgnu-intrinsics-enable option:        Fortran Dialect Options.
- * -fgnu-intrinsics-hide option:          Fortran Dialect Options.
- * -fGROUP-intrinsics-hide option:        Overly Convenient Options.
- * -finit-local-zero option <1>:          Overly Convenient Options.
- * -finit-local-zero option:              Code Gen Options.
- * -fintrin-case-any option:              Fortran Dialect Options.
- * -fintrin-case-initcap option:          Fortran Dialect Options.
- * -fintrin-case-lower option:            Fortran Dialect Options.
- * -fintrin-case-upper option:            Fortran Dialect Options.
- * -fmatch-case-any option:               Fortran Dialect Options.
- * -fmatch-case-initcap option:           Fortran Dialect Options.
- * -fmatch-case-lower option:             Fortran Dialect Options.
- * -fmatch-case-upper option:             Fortran Dialect Options.
- * -fmil-intrinsics-delete option:        Fortran Dialect Options.
- * -fmil-intrinsics-disable option:       Fortran Dialect Options.
- * -fmil-intrinsics-enable option:        Fortran Dialect Options.
- * -fmil-intrinsics-hide option:          Fortran Dialect Options.
- * -fno-argument-noalias-global option <1>: Aliasing Assumed To Work.
- * -fno-argument-noalias-global option:   Code Gen Options.
- * -fno-automatic option <1>:             Overly Convenient Options.
- * -fno-automatic option:                 Code Gen Options.
- * -fno-backslash option:                 Fortran Dialect Options.
- * -fno-common option:                    Code Gen Options.
- * -fno-f2c option <1>:                   Avoid f2c Compatibility.
- * -fno-f2c option:                       Code Gen Options.
- * -fno-f77 option:                       Shorthand Options.
- * -fno-fixed-form option:                Fortran Dialect Options.
- * -fno-globals option:                   Code Gen Options.
- * -fno-ident option:                     Code Gen Options.
- * -fno-inline option:                    Optimize Options.
- * -fno-move-all-movables option:         Optimize Options.
- * -fno-reduce-all-givs option:           Optimize Options.
- * -fno-rerun-loop-opt option:            Optimize Options.
- * -fno-second-underscore:                f2c Skeletons and Prototypes.
- * -fno-second-underscore option <1>:     Names.
- * -fno-second-underscore option:         Code Gen Options.
- * -fno-silent option:                    Overall Options.
- * -fno-trapping-math option:             Optimize Options.
- * -fno-ugly option:                      Shorthand Options.
- * -fno-ugly-args option:                 Fortran Dialect Options.
- * -fno-ugly-init option:                 Fortran Dialect Options.
- * -fno-underscoring option <1>:          Names.
- * -fno-underscoring option:              Code Gen Options.
- * -fonetrip option:                      Fortran Dialect Options.
- * -fpack-struct option:                  Code Gen Options.
- * -fpcc-struct-return option:            Code Gen Options.
- * -fpedantic option:                     Warning Options.
- * -fPIC option:                          News.
- * -freg-struct-return option:            Code Gen Options.
- * -frerun-cse-after-loop option:         Optimize Options.
- * -fschedule-insns option:               Optimize Options.
- * -fschedule-insns2 option:              Optimize Options.
- * -fset-g77-defaults option:             Overall Options.
- * -fshort-double option:                 Code Gen Options.
- * -fsource-case-lower option:            Fortran Dialect Options.
- * -fsource-case-preserve option:         Fortran Dialect Options.
- * -fsource-case-upper option:            Fortran Dialect Options.
- * -fstrength-reduce option:              Optimize Options.
- * -fsymbol-case-any option:              Fortran Dialect Options.
- * -fsymbol-case-initcap option:          Fortran Dialect Options.
- * -fsymbol-case-lower option:            Fortran Dialect Options.
- * -fsymbol-case-upper option:            Fortran Dialect Options.
- * -fsyntax-only option:                  Warning Options.
- * -ftypeless-boz option:                 Fortran Dialect Options.
- * -fugly option:                         Shorthand Options.
- * -fugly-assign option:                  Fortran Dialect Options.
- * -fugly-assumed option:                 Fortran Dialect Options.
- * -fugly-comma option:                   Fortran Dialect Options.
- * -fugly-complex option:                 Fortran Dialect Options.
- * -fugly-logint option:                  Fortran Dialect Options.
- * -funix-intrinsics-delete option:       Fortran Dialect Options.
- * -funix-intrinsics-disable option:      Fortran Dialect Options.
- * -funix-intrinsics-enable option:       Fortran Dialect Options.
- * -funix-intrinsics-hide option:         Fortran Dialect Options.
- * -funroll-all-loops option:             Optimize Options.
- * -funroll-loops option:                 Optimize Options.
- * -funsafe-math-optimizations option:    Optimize Options.
- * -fversion option:                      Overall Options.
- * -fvxt option:                          Fortran Dialect Options.
- * -fvxt-intrinsics-delete option:        Fortran Dialect Options.
- * -fvxt-intrinsics-disable option:       Fortran Dialect Options.
- * -fvxt-intrinsics-enable option:        Fortran Dialect Options.
- * -fvxt-intrinsics-hide option:          Fortran Dialect Options.
- * -fzeros option:                        Code Gen Options.
- * -g option:                             Debugging Options.
- * -I- option:                            Directory Options.
- * -i8:                                   Increasing Precision/Range.
- * -Idir option:                          Directory Options.
- * -malign-double <1>:                    Changes.
- * -malign-double:                        News.
- * -malign-double option <1>:             Aligned Data.
- * -malign-double option:                 Optimize Options.
- * -Nl option:                            Compiler Limits.
- * -Nx option:                            Compiler Limits.
- * -O2:                                   News.
- * -pedantic option:                      Warning Options.
- * -pedantic-errors option:               Warning Options.
- * -qrealsize=8:                          Increasing Precision/Range.
- * -r8:                                   Increasing Precision/Range.
- * -u option:                             Warning Options.
- * -v option:                             G77 and GCC.
- * -W option:                             Warning Options.
- * -w option:                             Warning Options.
- * -Waggregate-return option:             Warning Options.
- * -Wall option:                          Warning Options.
- * -Wcomment option:                      Warning Options.
- * -Wconversion option:                   Warning Options.
- * -Werror option:                        Warning Options.
- * -Wformat option:                       Warning Options.
- * -Wid-clash-LEN option:                 Warning Options.
- * -Wimplicit option:                     Warning Options.
- * -Wlarger-than-LEN option:              Warning Options.
- * -Wno-globals option:                   Warning Options.
- * -Wparentheses option:                  Warning Options.
- * -Wredundant-decls option:              Warning Options.
- * -Wshadow option:                       Warning Options.
- * -Wsurprising option:                   Warning Options.
- * -Wswitch option:                       Warning Options.
- * -Wtraditional option:                  Warning Options.
- * -Wuninitialized option:                Warning Options.
- * -Wunused option:                       Warning Options.
- * -x f77-cpp-input option:               LEX.
- * .EQV., with integer operands:          Equivalence Versus Equality.
- * .F filename suffix:                    Overall Options.
- * .f filename suffix:                    Overall Options.
- * .FOR filename suffix:                  Overall Options.
- * .for filename suffix:                  Overall Options.
- * .FPP filename suffix:                  Overall Options.
- * .fpp filename suffix:                  Overall Options.
- * .gdbinit:                              Main Program Unit.
- * .r filename suffix:                    Overall Options.
- * /* <1>:                                Trailing Comment.
- * /*:                                    Overall Options.
- * /WARNINGS=DECLARATIONS switch:         Warning Options.
- * 80-bit spills:                         Floating-point Errors.
- * ; <1>:                                 Character Set.
- * ;:                                     Statements Comments Lines.
- * <:                                     Character Set.
- * <> edit descriptor:                    I/O.
- * >:                                     Character Set.
- * ?:                                     Character Set.
- * \:                                     Character Set.
- * _:                                     Character Set.
- * Abort intrinsic:                       Abort Intrinsic.
- * Abs intrinsic:                         Abs Intrinsic.
- * ACCEPT statement:                      TYPE and ACCEPT I/O Statements.
- * Access intrinsic:                      Access Intrinsic.
- * AChar intrinsic:                       AChar Intrinsic.
- * ACos intrinsic:                        ACos Intrinsic.
- * ACosD intrinsic:                       ACosD Intrinsic.
- * adding options:                        Adding Options.
- * adjustable arrays:                     Adjustable Arrays.
- * AdjustL intrinsic:                     AdjustL Intrinsic.
- * AdjustR intrinsic:                     AdjustR Intrinsic.
- * AImag intrinsic <1>:                   AImag Intrinsic.
- * AImag intrinsic:                       REAL() and AIMAG() of Complex.
- * AIMax0 intrinsic:                      AIMax0 Intrinsic.
- * AIMin0 intrinsic:                      AIMin0 Intrinsic.
- * AInt intrinsic:                        AInt Intrinsic.
- * AJMax0 intrinsic:                      AJMax0 Intrinsic.
- * AJMin0 intrinsic:                      AJMin0 Intrinsic.
- * Alarm intrinsic:                       Alarm Intrinsic.
- * aliasing <1>:                          Known Bugs.
- * aliasing:                              Aliasing Assumed To Work.
- * aligned data:                          Aligned Data.
- * aligned stack:                         Aligned Data.
- * alignment <1>:                         Aligned Data.
- * alignment <2>:                         Changes.
- * alignment:                             News.
- * alignment testing:                     Aligned Data.
- * All intrinsic:                         All Intrinsic.
- * all warnings:                          Warning Options.
- * Allocated intrinsic:                   Allocated Intrinsic.
- * ALog intrinsic:                        ALog Intrinsic.
- * ALog10 intrinsic:                      ALog10 Intrinsic.
- * Alpha, support:                        Known Bugs.
- * alternate entry points:                Alternate Entry Points.
- * alternate returns:                     Alternate Returns.
- * ALWAYS_FLUSH:                          Output Assumed To Flush.
- * AMax0 intrinsic:                       AMax0 Intrinsic.
- * AMax1 intrinsic:                       AMax1 Intrinsic.
- * AMin0 intrinsic:                       AMin0 Intrinsic.
- * AMin1 intrinsic:                       AMin1 Intrinsic.
- * AMod intrinsic:                        AMod Intrinsic.
- * ampersand:                             Character Set.
- * ampersand continuation line:           Ampersands.
- * And intrinsic <1>:                     Bit Operations on Floating-point Data.
- * And intrinsic:                         And Intrinsic.
- * ANInt intrinsic:                       ANInt Intrinsic.
- * ANS carriage control:                  OPEN CLOSE and INQUIRE Keywords.
- * ANSI FORTRAN 77 standard:              Language.
- * ANSI FORTRAN 77 support:               Standard Support.
- * anti-aliasing:                         Aliasing Assumed To Work.
- * Any intrinsic:                         Any Intrinsic.
- * arguments, null:                       Ugly Null Arguments.
- * arguments, omitting:                   Ugly Null Arguments.
- * arguments, unused <1>:                 Unused Arguments.
- * arguments, unused:                     Warning Options.
- * array bounds checking:                 Code Gen Options.
- * array bounds, adjustable:              Array Bounds Expressions.
- * array elements, in adjustable array bounds: Array Bounds Expressions.
- * array ordering:                        Arrays.
- * array performance:                     Code Gen Options.
- * array size:                            Array Size.
- * arrays:                                Arrays.
- * arrays, adjustable:                    Adjustable Arrays.
- * arrays, assumed-size:                  Ugly Assumed-Size Arrays.
- * arrays, automatic <1>:                 Large Automatic Arrays.
- * arrays, automatic <2>:                 Stack Overflow.
- * arrays, automatic <3>:                 Overly Convenient Options.
- * arrays, automatic:                     Adjustable Arrays.
- * arrays, dimensioning <1>:              Adjustable Arrays.
- * arrays, dimensioning:                  Array Size.
- * arrays, flattening:                    Code Gen Options.
- * as command:                            What is GNU Fortran?.
- * ASin intrinsic:                        ASin Intrinsic.
- * ASinD intrinsic:                       ASinD Intrinsic.
- * assembler:                             What is GNU Fortran?.
- * assembly code:                         What is GNU Fortran?.
- * assembly code, invalid:                Bug Criteria.
- * ASSIGN statement <1>:                  Assigned Statement Labels.
- * ASSIGN statement:                      Ugly Assigned Labels.
- * assigned labels:                       Ugly Assigned Labels.
- * assigned statement labels:             Assigned Statement Labels.
- * Associated intrinsic:                  Associated Intrinsic.
- * association, storage:                  Aliasing Assumed To Work.
- * assumed-size arrays:                   Ugly Assumed-Size Arrays.
- * asterisk:                              LEX.
- * ATan intrinsic:                        ATan Intrinsic.
- * ATan2 intrinsic:                       ATan2 Intrinsic.
- * ATan2D intrinsic:                      ATan2D Intrinsic.
- * ATanD intrinsic:                       ATanD Intrinsic.
- * automatic arrays <1>:                  Large Automatic Arrays.
- * automatic arrays <2>:                  Stack Overflow.
- * automatic arrays <3>:                  Overly Convenient Options.
- * automatic arrays:                      Adjustable Arrays.
- * AUTOMATIC statement:                   AUTOMATIC Statement.
- * automatic variables:                   AUTOMATIC Statement.
- * back end, gcc <1>:                     Philosophy of Code Generation.
- * back end, gcc:                         What is GNU Fortran?.
- * backslash <1>:                         Backslash in Constants.
- * backslash <2>:                         Character Set.
- * backslash:                             Fortran Dialect Options.
- * backtrace for bug reports:             Bug Reporting.
- * badu77 intrinsics:                     Fortran Dialect Options.
- * badu77 intrinsics group:               Intrinsic Groups.
- * basic concepts:                        What is GNU Fortran?.
- * Bear-poking:                           Philosophy of Code Generation.
- * beginners:                             Getting Started.
- * BesJ0 intrinsic:                       BesJ0 Intrinsic.
- * BesJ1 intrinsic:                       BesJ1 Intrinsic.
- * BesJN intrinsic:                       BesJN Intrinsic.
- * BesY0 intrinsic:                       BesY0 Intrinsic.
- * BesY1 intrinsic:                       BesY1 Intrinsic.
- * BesYN intrinsic:                       BesYN Intrinsic.
- * binary data:                           Portable Unformatted Files.
- * Bit_Size intrinsic:                    Bit_Size Intrinsic.
- * BITest intrinsic:                      BITest Intrinsic.
- * BJTest intrinsic:                      BJTest Intrinsic.
- * blank <1>:                             Lines.
- * blank:                                 Character Set.
- * block data:                            Multiple Definitions of External Names.
- * block data and libraries:              Block Data and Libraries.
- * BLOCK DATA statement <1>:              Multiple Definitions of External Names.
- * BLOCK DATA statement:                  Block Data and Libraries.
- * bounds checking:                       Code Gen Options.
- * BTest intrinsic:                       BTest Intrinsic.
- * bug criteria:                          Bug Criteria.
- * bug report mailing lists:              Bug Lists.
- * bugs:                                  Bugs.
- * bugs, finding:                         What is GNU Fortran?.
- * bugs, known:                           Trouble.
- * bus error <1>:                         Strange Behavior at Run Time.
- * bus error:                             NeXTStep Problems.
- * but-bugs:                              But-bugs.
- * byte ordering:                         Portable Unformatted Files.
- * C library:                             Strange Behavior at Run Time.
- * C preprocessor:                        Overall Options.
- * C routines calling Fortran:            Debugging and Interfacing.
- * C++:                                   C++ Considerations.
- * C++, linking with:                     Interoperating with C and C++.
- * C, linking with:                       Interoperating with C and C++.
- * CAbs intrinsic:                        CAbs Intrinsic.
- * calling C routines:                    Debugging and Interfacing.
- * card image:                            Fortran Dialect Options.
- * carriage control:                      OPEN CLOSE and INQUIRE Keywords.
- * carriage returns:                      Carriage Returns.
- * case sensitivity:                      Case Sensitivity.
- * cc1 program:                           What is GNU Fortran?.
- * cc1plus program:                       What is GNU Fortran?.
- * CCos intrinsic:                        CCos Intrinsic.
- * CDAbs intrinsic:                       CDAbs Intrinsic.
- * CDCos intrinsic:                       CDCos Intrinsic.
- * CDExp intrinsic:                       CDExp Intrinsic.
- * CDLog intrinsic:                       CDLog Intrinsic.
- * CDSin intrinsic:                       CDSin Intrinsic.
- * CDSqRt intrinsic:                      CDSqRt Intrinsic.
- * Ceiling intrinsic:                     Ceiling Intrinsic.
- * CExp intrinsic:                        CExp Intrinsic.
- * cfortran.h:                            C Interfacing Tools.
- * changes, user-visible:                 Changes.
- * Char intrinsic:                        Char Intrinsic.
- * character assignments:                 Fortran 90 Features.
- * character constants <1>:               Character and Hollerith Constants.
- * character constants <2>:               Ugly Conversion of Initializers.
- * character constants <3>:               Double Quote Meaning.
- * character constants:                   Fortran Dialect Options.
- * character set:                         Fortran Dialect Options.
- * CHARACTER*(*):                         Arbitrary Concatenation.
- * CHARACTER, null:                       Character Type.
- * character-variable length:             Character-variable Length.
- * characters:                            Character Set.
- * characters, comma:                     Ugly Null Arguments.
- * characters, comment <1>:               LEX.
- * characters, comment <2>:               Exclamation Point.
- * characters, comment <3>:               Trailing Comment.
- * characters, comment:                   Statements Comments Lines.
- * characters, continuation <1>:          LEX.
- * characters, continuation <2>:          Exclamation Point.
- * characters, continuation:              Statements Comments Lines.
- * ChDir intrinsic <1>:                   ChDir Intrinsic (function).
- * ChDir intrinsic:                       ChDir Intrinsic (subroutine).
- * checking subscripts:                   Code Gen Options.
- * checking substrings:                   Code Gen Options.
- * checks, of internal consistency:       Overall Options.
- * ChMod intrinsic <1>:                   ChMod Intrinsic (function).
- * ChMod intrinsic:                       ChMod Intrinsic (subroutine).
- * CLog intrinsic:                        CLog Intrinsic.
- * close angle:                           Character Set.
- * close bracket:                         Character Set.
- * CLOSE statement:                       OPEN CLOSE and INQUIRE Keywords.
- * Cmplx intrinsic <1>:                   Cmplx Intrinsic.
- * Cmplx intrinsic:                       CMPLX() of DOUBLE PRECISION.
- * code generation, conventions:          Code Gen Options.
- * code generation, improving:            Better Optimization.
- * code generator <1>:                    Philosophy of Code Generation.
- * code generator:                        What is GNU Fortran?.
- * code, assembly:                        What is GNU Fortran?.
- * code, displaying main source:          Known Bugs.
- * code, in-line:                         What is GNU Fortran?.
- * code, legacy:                          Collected Fortran Wisdom.
- * code, machine:                         What is GNU Fortran?.
- * code, source <1>:                      Case Sensitivity.
- * code, source <2>:                      Source Form.
- * code, source <3>:                      Lines.
- * code, source:                          What is GNU Fortran?.
- * code, user:                            Cannot Link Fortran Programs.
- * code, writing:                         Collected Fortran Wisdom.
- * column-major ordering:                 Arrays.
- * columns 73 through 80:                 Better Source Model.
- * comma, trailing:                       Ugly Null Arguments.
- * command options:                       Invoking G77.
- * commands, as:                          What is GNU Fortran?.
- * commands, g77 <1>:                     G77 and GCC.
- * commands, g77:                         What is GNU Fortran?.
- * commands, gcc <1>:                     G77 and GCC.
- * commands, gcc:                         What is GNU Fortran?.
- * commands, gdb:                         What is GNU Fortran?.
- * commands, ld:                          What is GNU Fortran?.
- * comment <1>:                           LEX.
- * comment <2>:                           Trailing Comment.
- * comment:                               Statements Comments Lines.
- * comment character:                     Exclamation Point.
- * comment line, debug <1>:               Enabling Debug Lines.
- * comment line, debug:                   Debug Line.
- * common blocks <1>:                     Mangling of Names.
- * common blocks <2>:                     Known Bugs.
- * common blocks:                         Common Blocks.
- * common blocks, large:                  Large Common Blocks.
- * COMMON layout:                         Aligned Data.
- * COMMON statement <1>:                  Multiple Definitions of External Names.
- * COMMON statement:                      Common Blocks.
- * comparing logical expressions:         Equivalence Versus Equality.
- * compatibility, f2c <1>:                Avoid f2c Compatibility.
- * compatibility, f2c <2>:                Block Data and Libraries.
- * compatibility, f2c <3>:                Code Gen Options.
- * compatibility, f2c <4>:                Shorthand Options.
- * compatibility, f2c:                    Overall Options.
- * compatibility, f77:                    Shorthand Options.
- * compatibility, FORTRAN 66 <1>:         Fortran Dialect Options.
- * compatibility, FORTRAN 66:             Shorthand Options.
- * compatibility, FORTRAN 77:             Standard Support.
- * compatibility, Fortran 90:             Fortran 90.
- * compilation, in-line <1>:              GLOBALS.
- * compilation, in-line <2>:              Code Gen Options.
- * compilation, in-line:                  Optimize Options.
- * compilation, pedantic:                 Pedantic Compilation.
- * compilation, status:                   Overall Options.
- * compiler bugs, reporting:              Bug Reporting.
- * compiler limits:                       Compiler Limits.
- * compiler memory usage:                 Known Bugs.
- * compiler speed:                        Known Bugs.
- * compilers:                             What is GNU Fortran?.
- * compiling programs:                    G77 and GCC.
- * Complex intrinsic:                     Complex Intrinsic.
- * COMPLEX intrinsics:                    Fortran Dialect Options.
- * complex performance:                   Known Bugs.
- * COMPLEX statement:                     Complex Variables.
- * complex values:                        Ugly Complex Part Extraction.
- * complex variables:                     Complex Variables.
- * COMPLEX(KIND=1) type:                  Compiler Types.
- * COMPLEX(KIND=2) type:                  Compiler Types.
- * components of g77:                     What is GNU Fortran?.
- * concatenation:                         Arbitrary Concatenation.
- * concepts, basic:                       What is GNU Fortran?.
- * conformance, IEEE 754 <1>:             Floating-point precision.
- * conformance, IEEE 754:                 Optimize Options.
- * Conjg intrinsic:                       Conjg Intrinsic.
- * consistency checks:                    Overall Options.
- * constants <1>:                         Compiler Constants.
- * constants:                             Constants.
- * constants, character <1>:              Character and Hollerith Constants.
- * constants, character <2>:              Ugly Conversion of Initializers.
- * constants, character:                  Double Quote Meaning.
- * constants, context-sensitive:          Context-Sensitive Constants.
- * constants, Hollerith <1>:              Character and Hollerith Constants.
- * constants, Hollerith <2>:              Ugly Conversion of Initializers.
- * constants, Hollerith:                  Ugly Implicit Argument Conversion.
- * constants, integer:                    Known Bugs.
- * constants, octal:                      Double Quote Meaning.
- * constants, prefix-radix:               Fortran Dialect Options.
- * constants, types:                      Fortran Dialect Options.
- * construct names:                       Construct Names.
- * context-sensitive constants:           Context-Sensitive Constants.
- * context-sensitive intrinsics:          Context-Sensitive Intrinsicness.
- * continuation character <1>:            LEX.
- * continuation character <2>:            Exclamation Point.
- * continuation character:                Statements Comments Lines.
- * continuation line, ampersand:          Ampersands.
- * continuation line, number of:          Continuation Line.
- * contributors:                          Contributors.
- * conversions, nonportable:              Nonportable Conversions.
- * core dump:                             Bug Criteria.
- * Cos intrinsic:                         Cos Intrinsic.
- * CosD intrinsic:                        CosD Intrinsic.
- * CosH intrinsic:                        CosH Intrinsic.
- * Count intrinsic:                       Count Intrinsic.
- * cpp preprocessor:                      Overall Options.
- * cpp program <1>:                       LEX.
- * cpp program <2>:                       Bug Reporting.
- * cpp program <3>:                       Preprocessor Options.
- * cpp program <4>:                       Overall Options.
- * cpp program:                           What is GNU Fortran?.
- * CPU_Time intrinsic:                    CPU_Time Intrinsic.
- * Cray pointers:                         POINTER Statements.
- * credits:                               Contributors.
- * CShift intrinsic:                      CShift Intrinsic.
- * CSin intrinsic:                        CSin Intrinsic.
- * CSqRt intrinsic:                       CSqRt Intrinsic.
- * CTime intrinsic <1>:                   CTime Intrinsic (function).
- * CTime intrinsic:                       CTime Intrinsic (subroutine).
- * CYCLE statement:                       CYCLE and EXIT.
- * DAbs intrinsic:                        DAbs Intrinsic.
- * DACos intrinsic:                       DACos Intrinsic.
- * DACosD intrinsic:                      DACosD Intrinsic.
- * DASin intrinsic:                       DASin Intrinsic.
- * DASinD intrinsic:                      DASinD Intrinsic.
- * DATA statement <1>:                    Known Bugs.
- * DATA statement:                        Code Gen Options.
- * data types:                            Compiler Types.
- * data, aligned:                         Aligned Data.
- * data, overwritten:                     Strange Behavior at Run Time.
- * DATan intrinsic:                       DATan Intrinsic.
- * DATan2 intrinsic:                      DATan2 Intrinsic.
- * DATan2D intrinsic:                     DATan2D Intrinsic.
- * DATanD intrinsic:                      DATanD Intrinsic.
- * Date intrinsic:                        Date Intrinsic.
- * Date_and_Time intrinsic:               Date_and_Time Intrinsic.
- * date_y2kbuggy_0:                       Year 2000 (Y2K) Problems.
- * DbesJ0 intrinsic:                      DbesJ0 Intrinsic.
- * DbesJ1 intrinsic:                      DbesJ1 Intrinsic.
- * DbesJN intrinsic:                      DbesJN Intrinsic.
- * DbesY0 intrinsic:                      DbesY0 Intrinsic.
- * DbesY1 intrinsic:                      DbesY1 Intrinsic.
- * DbesYN intrinsic:                      DbesYN Intrinsic.
- * Dble intrinsic:                        Dble Intrinsic.
- * DbleQ intrinsic:                       DbleQ Intrinsic.
- * DCmplx intrinsic:                      DCmplx Intrinsic.
- * DConjg intrinsic:                      DConjg Intrinsic.
- * DCos intrinsic:                        DCos Intrinsic.
- * DCosD intrinsic:                       DCosD Intrinsic.
- * DCosH intrinsic:                       DCosH Intrinsic.
- * DDiM intrinsic:                        DDiM Intrinsic.
- * debug line <1>:                        Enabling Debug Lines.
- * debug line:                            Debug Line.
- * debug_rtx:                             Bug Reporting.
- * debugger <1>:                          Known Bugs.
- * debugger:                              What is GNU Fortran?.
- * debugging <1>:                         Names.
- * debugging <2>:                         Main Program Unit.
- * debugging:                             Debugging and Interfacing.
- * debugging information options:         Debugging Options.
- * debugging main source code:            Known Bugs.
- * DECODE statement:                      ENCODE and DECODE.
- * deleted intrinsics:                    Intrinsic Groups.
- * DErF intrinsic:                        DErF Intrinsic.
- * DErFC intrinsic:                       DErFC Intrinsic.
- * DExp intrinsic:                        DExp Intrinsic.
- * DFloat intrinsic:                      DFloat Intrinsic.
- * DFlotI intrinsic:                      DFlotI Intrinsic.
- * DFlotJ intrinsic:                      DFlotJ Intrinsic.
- * diagnostics:                           Diagnostics.
- * diagnostics, incorrect:                What is GNU Fortran?.
- * dialect options:                       Fortran Dialect Options.
- * Digital Fortran features:              Fortran Dialect Options.
- * Digits intrinsic:                      Digits Intrinsic.
- * DiM intrinsic:                         DiM Intrinsic.
- * DImag intrinsic:                       DImag Intrinsic.
- * DIMENSION statement <1>:               Array Bounds Expressions.
- * DIMENSION statement <2>:               Adjustable Arrays.
- * DIMENSION statement:                   Arrays.
- * DIMENSION X(1):                        Ugly Assumed-Size Arrays.
- * dimensioning arrays:                   Adjustable Arrays.
- * DInt intrinsic:                        DInt Intrinsic.
- * direction of language development:     Direction of Language Development.
- * directive, #include:                   Bug Reporting.
- * directive, INCLUDE <1>:                Bug Reporting.
- * directive, INCLUDE <2>:                Directory Options.
- * directive, INCLUDE:                    Preprocessor Options.
- * directory, options:                    Directory Options.
- * directory, search paths for inclusion: Directory Options.
- * disabled intrinsics:                   Intrinsic Groups.
- * disk full:                             Output Assumed To Flush.
- * displaying main source code:           Known Bugs.
- * disposition of files:                  OPEN CLOSE and INQUIRE Keywords.
- * distensions:                           Distensions.
- * DLog intrinsic:                        DLog Intrinsic.
- * DLog10 intrinsic:                      DLog10 Intrinsic.
- * DMax1 intrinsic:                       DMax1 Intrinsic.
- * DMin1 intrinsic:                       DMin1 Intrinsic.
- * DMod intrinsic:                        DMod Intrinsic.
- * DNInt intrinsic:                       DNInt Intrinsic.
- * DNRM2:                                 News.
- * DO:                                    DO WHILE.
- * DO loops, one-trip:                    Fortran Dialect Options.
- * DO loops, zero-trip:                   Fortran Dialect Options.
- * DO statement <1>:                      Loops.
- * DO statement:                          Warning Options.
- * DO WHILE <1>:                          DO WHILE.
- * DO WHILE:                              Optimize Options.
- * dollar sign <1>:                       Dollar Signs.
- * dollar sign <2>:                       I/O.
- * dollar sign:                           Fortran Dialect Options.
- * Dot_Product intrinsic:                 Dot_Product Intrinsic.
- * DOUBLE COMPLEX:                        DOUBLE COMPLEX.
- * DOUBLE COMPLEX type:                   Compiler Types.
- * DOUBLE PRECISION type:                 Compiler Types.
- * double quote:                          Character Set.
- * double quoted character constants <1>: Fortran 90 Features.
- * double quoted character constants:     Character Type.
- * double quotes:                         Double Quote Meaning.
- * double-precision performance <1>:      Changes.
- * double-precision performance:          News.
- * DProd intrinsic:                       DProd Intrinsic.
- * DReal intrinsic:                       DReal Intrinsic.
- * driver, gcc command as:                What is GNU Fortran?.
- * DSign intrinsic:                       DSign Intrinsic.
- * DSin intrinsic:                        DSin Intrinsic.
- * DSinD intrinsic:                       DSinD Intrinsic.
- * DSinH intrinsic:                       DSinH Intrinsic.
- * DSqRt intrinsic:                       DSqRt Intrinsic.
- * DTan intrinsic:                        DTan Intrinsic.
- * DTanD intrinsic:                       DTanD Intrinsic.
- * DTanH intrinsic:                       DTanH Intrinsic.
- * DTime intrinsic <1>:                   DTime Intrinsic (function).
- * DTime intrinsic:                       DTime Intrinsic (subroutine).
- * dummies, unused:                       Warning Options.
- * edit descriptor, <>:                   I/O.
- * edit descriptor, O:                    I/O.
- * edit descriptor, Q:                    Q Edit Descriptor.
- * edit descriptor, Z <1>:                Fortran 90 Features.
- * edit descriptor, Z:                    I/O.
- * effecting IMPLICIT NONE:               Warning Options.
- * efficiency:                            Efficiency.
- * ELF support:                           News.
- * empty CHARACTER strings:               Character Type.
- * enabled intrinsics:                    Intrinsic Groups.
- * ENCODE statement:                      ENCODE and DECODE.
- * END DO:                                END DO.
- * entry points:                          Alternate Entry Points.
- * ENTRY statement:                       Alternate Entry Points.
- * environment variables:                 Environment Variables.
- * EOShift intrinsic:                     EOShift Intrinsic.
- * Epsilon intrinsic:                     Epsilon Intrinsic.
- * equivalence areas <1>:                 Known Bugs.
- * equivalence areas:                     Local Equivalence Areas.
- * EQUIVALENCE statement:                 Local Equivalence Areas.
- * ErF intrinsic:                         ErF Intrinsic.
- * ErFC intrinsic:                        ErFC Intrinsic.
- * error messages <1>:                    Warnings and Errors.
- * error messages:                        Run-time Library Errors.
- * error messages, incorrect:             What is GNU Fortran?.
- * error values:                          Run-time Library Errors.
- * errors, linker:                        Large Common Blocks.
- * ETime intrinsic <1>:                   ETime Intrinsic (function).
- * ETime intrinsic:                       ETime Intrinsic (subroutine).
- * exceptions, floating-point:            Floating-point Exception Handling.
- * exclamation point <1>:                 LEX.
- * exclamation point <2>:                 Exclamation Point.
- * exclamation point <3>:                 Trailing Comment.
- * exclamation point <4>:                 Character Set.
- * exclamation point:                     Statements Comments Lines.
- * executable file:                       What is GNU Fortran?.
- * Exit intrinsic:                        Exit Intrinsic.
- * EXIT statement:                        CYCLE and EXIT.
- * Exp intrinsic:                         Exp Intrinsic.
- * Exponent intrinsic:                    Exponent Intrinsic.
- * extended-source option:                Fortran Dialect Options.
- * extensions, file name:                 Overall Options.
- * extensions, from Fortran 90:           Fortran 90 Features.
- * extensions, more:                      More Extensions.
- * extensions, VXT:                       VXT Fortran.
- * external names:                        Mangling of Names.
- * extra warnings:                        Warning Options.
- * f2c:                                   Increasing Precision/Range.
- * f2c compatibility <1>:                 Avoid f2c Compatibility.
- * f2c compatibility <2>:                 Block Data and Libraries.
- * f2c compatibility <3>:                 Debugging and Interfacing.
- * f2c compatibility <4>:                 Code Gen Options.
- * f2c compatibility <5>:                 Shorthand Options.
- * f2c compatibility:                     Overall Options.
- * f2c intrinsics:                        Fortran Dialect Options.
- * f2c intrinsics group:                  Intrinsic Groups.
- * f77 compatibility:                     Shorthand Options.
- * f77 support:                           Backslash in Constants.
- * f771, program:                         What is GNU Fortran?.
- * f90 intrinsics group:                  Intrinsic Groups.
- * fatal signal:                          Bug Criteria.
- * FDate intrinsic <1>:                   FDate Intrinsic (function).
- * FDate intrinsic:                       FDate Intrinsic (subroutine).
- * FDL, GNU Free Documentation License:   GNU Free Documentation License.
- * features, language:                    Direction of Language Development.
- * features, ugly <1>:                    Distensions.
- * features, ugly:                        Shorthand Options.
- * FFE <1>:                               Front End.
- * FFE:                                   What is GNU Fortran?.
- * fflush():                              Output Assumed To Flush.
- * FGet intrinsic <1>:                    FGet Intrinsic (function).
- * FGet intrinsic:                        FGet Intrinsic (subroutine).
- * FGetC intrinsic <1>:                   FGetC Intrinsic (function).
- * FGetC intrinsic:                       FGetC Intrinsic (subroutine).
- * file format not recognized:            What is GNU Fortran?.
- * file formats:                          Portable Unformatted Files.
- * file name extension:                   Overall Options.
- * file name suffix:                      Overall Options.
- * file type:                             Overall Options.
- * file, source <1>:                      Source Form.
- * file, source <2>:                      Lines.
- * file, source:                          What is GNU Fortran?.
- * files, executable:                     What is GNU Fortran?.
- * fixed form <1>:                        Source Form.
- * fixed form <2>:                        Lines.
- * fixed form:                            Fortran Dialect Options.
- * Float intrinsic:                       Float Intrinsic.
- * FloatI intrinsic:                      FloatI Intrinsic.
- * floating-point errors:                 Floating-point Errors.
- * floating-point, errors:                Inconsistent Calling Sequences.
- * floating-point, exceptions:            Floating-point Exception Handling.
- * floating-point, precision <1>:         Floating-point precision.
- * floating-point, precision:             Optimize Options.
- * FloatJ intrinsic:                      FloatJ Intrinsic.
- * Floor intrinsic:                       Floor Intrinsic.
- * Flush intrinsic:                       Flush Intrinsic.
- * flushing output:                       Output Assumed To Flush.
- * FNum intrinsic:                        FNum Intrinsic.
- * FORM='PRINT':                          OPEN CLOSE and INQUIRE Keywords.
- * FORMAT descriptors <1>:                Fortran 90 Features.
- * FORMAT descriptors:                    I/O.
- * FORMAT statement <1>:                  Q Edit Descriptor.
- * FORMAT statement:                      Expressions in FORMAT Statements.
- * FORTRAN 66 <1>:                        Fortran Dialect Options.
- * FORTRAN 66:                            Shorthand Options.
- * FORTRAN 77 compatibility:              Standard Support.
- * Fortran 90:                            Fortran 90 Features.
- * Fortran 90, compatibility:             Fortran 90.
- * Fortran 90, features:                  Fortran Dialect Options.
- * Fortran 90, intrinsics:                Fortran Dialect Options.
- * Fortran 90, support:                   Fortran 90 Support.
- * Fortran preprocessor:                  Overall Options.
- * forward references:                    GLOBALS.
- * FPE handling:                          Floating-point Exception Handling.
- * FPut intrinsic <1>:                    FPut Intrinsic (function).
- * FPut intrinsic:                        FPut Intrinsic (subroutine).
- * FPutC intrinsic <1>:                   FPutC Intrinsic (function).
- * FPutC intrinsic:                       FPutC Intrinsic (subroutine).
- * Fraction intrinsic:                    Fraction Intrinsic.
- * free form <1>:                         Source Form.
- * free form <2>:                         Lines.
- * free form:                             Fortran Dialect Options.
- * front end, g77 <1>:                    Front End.
- * front end, g77:                        What is GNU Fortran?.
- * FSeek intrinsic:                       FSeek Intrinsic.
- * FSF, funding the:                      Funding GNU Fortran.
- * FStat intrinsic <1>:                   FStat Intrinsic (function).
- * FStat intrinsic:                       FStat Intrinsic (subroutine).
- * FTell intrinsic <1>:                   FTell Intrinsic (function).
- * FTell intrinsic:                       FTell Intrinsic (subroutine).
- * function references, in adjustable array bounds: Array Bounds Expressions.
- * FUNCTION statement <1>:                Functions.
- * FUNCTION statement:                    Procedures.
- * functions:                             Functions.
- * functions, mistyped:                   Not My Type.
- * funding improvements:                  Funding GNU Fortran.
- * funding the FSF:                       Funding GNU Fortran.
- * g77 options, --driver <1>:             Changes.
- * g77 options, --driver:                 News.
- * g77 options, -v:                       G77 and GCC.
- * g77, command <1>:                      G77 and GCC.
- * g77, command:                          What is GNU Fortran?.
- * g77, components of:                    What is GNU Fortran?.
- * g77, front end <1>:                    Front End.
- * g77, front end:                        What is GNU Fortran?.
- * g77, modifying:                        Overall Options.
- * G77_date_y2kbuggy_0:                   Year 2000 (Y2K) Problems.
- * G77_vxtidate_y2kbuggy_0:               Year 2000 (Y2K) Problems.
- * GBE <1>:                               Philosophy of Code Generation.
- * GBE:                                   What is GNU Fortran?.
- * GBEL:                                  Philosophy of Code Generation.
- * gcc, back end <1>:                     Philosophy of Code Generation.
- * gcc, back end:                         What is GNU Fortran?.
- * gcc, command <1>:                      G77 and GCC.
- * gcc, command:                          What is GNU Fortran?.
- * gcc, command as driver:                What is GNU Fortran?.
- * gcc, not recognizing Fortran source:   What is GNU Fortran?.
- * gdb, command:                          What is GNU Fortran?.
- * gdb, support:                          Debugger Problems.
- * generic intrinsics:                    Generics and Specifics.
- * GError intrinsic:                      GError Intrinsic.
- * GetArg intrinsic <1>:                  Main Program Unit.
- * GetArg intrinsic:                      GetArg Intrinsic.
- * GetCWD intrinsic <1>:                  GetCWD Intrinsic (function).
- * GetCWD intrinsic:                      GetCWD Intrinsic (subroutine).
- * GetEnv intrinsic:                      GetEnv Intrinsic.
- * GetGId intrinsic:                      GetGId Intrinsic.
- * GetLog intrinsic:                      GetLog Intrinsic.
- * GetPId intrinsic:                      GetPId Intrinsic.
- * getting started:                       Getting Started.
- * GetUId intrinsic:                      GetUId Intrinsic.
- * global names, warning <1>:             Code Gen Options.
- * global names, warning:                 Warning Options.
- * GMTime intrinsic:                      GMTime Intrinsic.
- * GNU Back End (GBE) <1>:                Philosophy of Code Generation.
- * GNU Back End (GBE):                    What is GNU Fortran?.
- * GNU Back End Language (GBEL):          Philosophy of Code Generation.
- * GNU Fortran command options:           Invoking G77.
- * GNU Fortran Front End (FFE) <1>:       Front End.
- * GNU Fortran Front End (FFE):           What is GNU Fortran?.
- * gnu intrinsics group:                  Intrinsic Groups.
- * GOTO statement:                        Assigned Statement Labels.
- * groups of intrinsics:                  Intrinsic Groups.
- * hardware errors:                       Signal 11 and Friends.
- * hash mark:                             Character Set.
- * HDF:                                   Portable Unformatted Files.
- * hidden intrinsics:                     Intrinsic Groups.
- * Hollerith constants <1>:               Character and Hollerith Constants.
- * Hollerith constants <2>:               Ugly Conversion of Initializers.
- * Hollerith constants <3>:               Ugly Implicit Argument Conversion.
- * Hollerith constants:                   Fortran Dialect Options.
- * horizontal tab:                        Tabs.
- * HostNm intrinsic <1>:                  HostNm Intrinsic (function).
- * HostNm intrinsic:                      HostNm Intrinsic (subroutine).
- * Huge intrinsic:                        Huge Intrinsic.
- * I/O, errors:                           Run-time Library Errors.
- * I/O, flushing:                         Output Assumed To Flush.
- * IAbs intrinsic:                        IAbs Intrinsic.
- * IAChar intrinsic:                      IAChar Intrinsic.
- * IAnd intrinsic:                        IAnd Intrinsic.
- * IArgC intrinsic <1>:                   Main Program Unit.
- * IArgC intrinsic:                       IArgC Intrinsic.
- * IBClr intrinsic:                       IBClr Intrinsic.
- * IBits intrinsic:                       IBits Intrinsic.
- * IBSet intrinsic:                       IBSet Intrinsic.
- * IChar intrinsic:                       IChar Intrinsic.
- * IDate intrinsic <1>:                   IDate Intrinsic (VXT).
- * IDate intrinsic:                       IDate Intrinsic (UNIX).
- * IDiM intrinsic:                        IDiM Intrinsic.
- * IDInt intrinsic:                       IDInt Intrinsic.
- * IDNInt intrinsic:                      IDNInt Intrinsic.
- * IEEE 754 conformance <1>:              Floating-point precision.
- * IEEE 754 conformance:                  Optimize Options.
- * IEOr intrinsic:                        IEOr Intrinsic.
- * IErrNo intrinsic:                      IErrNo Intrinsic.
- * IFix intrinsic:                        IFix Intrinsic.
- * IIAbs intrinsic:                       IIAbs Intrinsic.
- * IIAnd intrinsic:                       IIAnd Intrinsic.
- * IIBClr intrinsic:                      IIBClr Intrinsic.
- * IIBits intrinsic:                      IIBits Intrinsic.
- * IIBSet intrinsic:                      IIBSet Intrinsic.
- * IIDiM intrinsic:                       IIDiM Intrinsic.
- * IIDInt intrinsic:                      IIDInt Intrinsic.
- * IIDNnt intrinsic:                      IIDNnt Intrinsic.
- * IIEOr intrinsic:                       IIEOr Intrinsic.
- * IIFix intrinsic:                       IIFix Intrinsic.
- * IInt intrinsic:                        IInt Intrinsic.
- * IIOr intrinsic:                        IIOr Intrinsic.
- * IIQint intrinsic:                      IIQint Intrinsic.
- * IIQNnt intrinsic:                      IIQNnt Intrinsic.
- * IIShftC intrinsic:                     IIShftC Intrinsic.
- * IISign intrinsic:                      IISign Intrinsic.
- * illegal unit number:                   Large File Unit Numbers.
- * Imag intrinsic:                        Imag Intrinsic.
- * imaginary part <1>:                    Complex Variables.
- * imaginary part:                        Ugly Complex Part Extraction.
- * ImagPart intrinsic:                    ImagPart Intrinsic.
- * IMax0 intrinsic:                       IMax0 Intrinsic.
- * IMax1 intrinsic:                       IMax1 Intrinsic.
- * IMin0 intrinsic:                       IMin0 Intrinsic.
- * IMin1 intrinsic:                       IMin1 Intrinsic.
- * IMod intrinsic:                        IMod Intrinsic.
- * IMPLICIT CHARACTER*(*) statement:      Limitation on Implicit Declarations.
- * implicit declaration, warning:         Warning Options.
- * IMPLICIT NONE, similar effect:         Warning Options.
- * implicit typing:                       Not My Type.
- * improvements, funding:                 Funding GNU Fortran.
- * in-line code <1>:                      GLOBALS.
- * in-line code <2>:                      Code Gen Options.
- * in-line code <3>:                      Optimize Options.
- * in-line code:                          What is GNU Fortran?.
- * INCLUDE directive <1>:                 Bug Reporting.
- * INCLUDE directive <2>:                 INCLUDE.
- * INCLUDE directive <3>:                 Directory Options.
- * INCLUDE directive:                     Preprocessor Options.
- * included files:                        Bug Reporting.
- * inclusion, directory search paths for: Directory Options.
- * inconsistent floating-point results:   Floating-point Errors.
- * incorrect diagnostics:                 What is GNU Fortran?.
- * incorrect error messages:              What is GNU Fortran?.
- * incorrect use of language:             What is GNU Fortran?.
- * increasing maximum unit number:        Large File Unit Numbers.
- * increasing precision:                  Increasing Precision/Range.
- * increasing range:                      Increasing Precision/Range.
- * Index intrinsic:                       Index Intrinsic.
- * indexed (iterative) DO:                Optimize Options.
- * infinite spaces printed:               Strange Behavior at Run Time.
- * INInt intrinsic:                       INInt Intrinsic.
- * initialization, bug:                   Known Bugs.
- * initialization, of local variables:    Code Gen Options.
- * initialization, run-time:              Startup Code.
- * initialization, statement placement:   Initializing Before Specifying.
- * INot intrinsic:                        INot Intrinsic.
- * INQUIRE statement:                     OPEN CLOSE and INQUIRE Keywords.
- * installation trouble:                  Trouble.
- * Int intrinsic:                         Int Intrinsic.
- * Int2 intrinsic:                        Int2 Intrinsic.
- * Int8 intrinsic:                        Int8 Intrinsic.
- * integer constants:                     Known Bugs.
- * INTEGER(KIND=1) type:                  Compiler Types.
- * INTEGER(KIND=2) type:                  Compiler Types.
- * INTEGER(KIND=3) type:                  Compiler Types.
- * INTEGER(KIND=6) type:                  Compiler Types.
- * INTEGER*2 support:                     Popular Non-standard Types.
- * INTEGER*8 support:                     Full Support for Compiler Types.
- * Intel x86:                             News.
- * interfacing:                           Debugging and Interfacing.
- * internal consistency checks:           Overall Options.
- * intrinsics, Abort:                     Abort Intrinsic.
- * intrinsics, Abs:                       Abs Intrinsic.
- * intrinsics, Access:                    Access Intrinsic.
- * intrinsics, AChar:                     AChar Intrinsic.
- * intrinsics, ACos:                      ACos Intrinsic.
- * intrinsics, ACosD:                     ACosD Intrinsic.
- * intrinsics, AdjustL:                   AdjustL Intrinsic.
- * intrinsics, AdjustR:                   AdjustR Intrinsic.
- * intrinsics, AImag <1>:                 AImag Intrinsic.
- * intrinsics, AImag:                     REAL() and AIMAG() of Complex.
- * intrinsics, AIMax0:                    AIMax0 Intrinsic.
- * intrinsics, AIMin0:                    AIMin0 Intrinsic.
- * intrinsics, AInt:                      AInt Intrinsic.
- * intrinsics, AJMax0:                    AJMax0 Intrinsic.
- * intrinsics, AJMin0:                    AJMin0 Intrinsic.
- * intrinsics, Alarm:                     Alarm Intrinsic.
- * intrinsics, All:                       All Intrinsic.
- * intrinsics, Allocated:                 Allocated Intrinsic.
- * intrinsics, ALog:                      ALog Intrinsic.
- * intrinsics, ALog10:                    ALog10 Intrinsic.
- * intrinsics, AMax0:                     AMax0 Intrinsic.
- * intrinsics, AMax1:                     AMax1 Intrinsic.
- * intrinsics, AMin0:                     AMin0 Intrinsic.
- * intrinsics, AMin1:                     AMin1 Intrinsic.
- * intrinsics, AMod:                      AMod Intrinsic.
- * intrinsics, And <1>:                   Bit Operations on Floating-point Data.
- * intrinsics, And:                       And Intrinsic.
- * intrinsics, ANInt:                     ANInt Intrinsic.
- * intrinsics, Any:                       Any Intrinsic.
- * intrinsics, ASin:                      ASin Intrinsic.
- * intrinsics, ASinD:                     ASinD Intrinsic.
- * intrinsics, Associated:                Associated Intrinsic.
- * intrinsics, ATan:                      ATan Intrinsic.
- * intrinsics, ATan2:                     ATan2 Intrinsic.
- * intrinsics, ATan2D:                    ATan2D Intrinsic.
- * intrinsics, ATanD:                     ATanD Intrinsic.
- * intrinsics, badu77:                    Fortran Dialect Options.
- * intrinsics, BesJ0:                     BesJ0 Intrinsic.
- * intrinsics, BesJ1:                     BesJ1 Intrinsic.
- * intrinsics, BesJN:                     BesJN Intrinsic.
- * intrinsics, BesY0:                     BesY0 Intrinsic.
- * intrinsics, BesY1:                     BesY1 Intrinsic.
- * intrinsics, BesYN:                     BesYN Intrinsic.
- * intrinsics, Bit_Size:                  Bit_Size Intrinsic.
- * intrinsics, BITest:                    BITest Intrinsic.
- * intrinsics, BJTest:                    BJTest Intrinsic.
- * intrinsics, BTest:                     BTest Intrinsic.
- * intrinsics, CAbs:                      CAbs Intrinsic.
- * intrinsics, CCos:                      CCos Intrinsic.
- * intrinsics, CDAbs:                     CDAbs Intrinsic.
- * intrinsics, CDCos:                     CDCos Intrinsic.
- * intrinsics, CDExp:                     CDExp Intrinsic.
- * intrinsics, CDLog:                     CDLog Intrinsic.
- * intrinsics, CDSin:                     CDSin Intrinsic.
- * intrinsics, CDSqRt:                    CDSqRt Intrinsic.
- * intrinsics, Ceiling:                   Ceiling Intrinsic.
- * intrinsics, CExp:                      CExp Intrinsic.
- * intrinsics, Char:                      Char Intrinsic.
- * intrinsics, ChDir <1>:                 ChDir Intrinsic (function).
- * intrinsics, ChDir:                     ChDir Intrinsic (subroutine).
- * intrinsics, ChMod <1>:                 ChMod Intrinsic (function).
- * intrinsics, ChMod:                     ChMod Intrinsic (subroutine).
- * intrinsics, CLog:                      CLog Intrinsic.
- * intrinsics, Cmplx <1>:                 Cmplx Intrinsic.
- * intrinsics, Cmplx:                     CMPLX() of DOUBLE PRECISION.
- * intrinsics, Complex:                   Complex Intrinsic.
- * intrinsics, COMPLEX:                   Fortran Dialect Options.
- * intrinsics, Conjg:                     Conjg Intrinsic.
- * intrinsics, context-sensitive:         Context-Sensitive Intrinsicness.
- * intrinsics, Cos:                       Cos Intrinsic.
- * intrinsics, CosD:                      CosD Intrinsic.
- * intrinsics, CosH:                      CosH Intrinsic.
- * intrinsics, Count:                     Count Intrinsic.
- * intrinsics, CPU_Time:                  CPU_Time Intrinsic.
- * intrinsics, CShift:                    CShift Intrinsic.
- * intrinsics, CSin:                      CSin Intrinsic.
- * intrinsics, CSqRt:                     CSqRt Intrinsic.
- * intrinsics, CTime <1>:                 CTime Intrinsic (function).
- * intrinsics, CTime:                     CTime Intrinsic (subroutine).
- * intrinsics, DAbs:                      DAbs Intrinsic.
- * intrinsics, DACos:                     DACos Intrinsic.
- * intrinsics, DACosD:                    DACosD Intrinsic.
- * intrinsics, DASin:                     DASin Intrinsic.
- * intrinsics, DASinD:                    DASinD Intrinsic.
- * intrinsics, DATan:                     DATan Intrinsic.
- * intrinsics, DATan2:                    DATan2 Intrinsic.
- * intrinsics, DATan2D:                   DATan2D Intrinsic.
- * intrinsics, DATanD:                    DATanD Intrinsic.
- * intrinsics, Date:                      Date Intrinsic.
- * intrinsics, Date_and_Time:             Date_and_Time Intrinsic.
- * intrinsics, DbesJ0:                    DbesJ0 Intrinsic.
- * intrinsics, DbesJ1:                    DbesJ1 Intrinsic.
- * intrinsics, DbesJN:                    DbesJN Intrinsic.
- * intrinsics, DbesY0:                    DbesY0 Intrinsic.
- * intrinsics, DbesY1:                    DbesY1 Intrinsic.
- * intrinsics, DbesYN:                    DbesYN Intrinsic.
- * intrinsics, Dble:                      Dble Intrinsic.
- * intrinsics, DbleQ:                     DbleQ Intrinsic.
- * intrinsics, DCmplx:                    DCmplx Intrinsic.
- * intrinsics, DConjg:                    DConjg Intrinsic.
- * intrinsics, DCos:                      DCos Intrinsic.
- * intrinsics, DCosD:                     DCosD Intrinsic.
- * intrinsics, DCosH:                     DCosH Intrinsic.
- * intrinsics, DDiM:                      DDiM Intrinsic.
- * intrinsics, deleted:                   Intrinsic Groups.
- * intrinsics, DErF:                      DErF Intrinsic.
- * intrinsics, DErFC:                     DErFC Intrinsic.
- * intrinsics, DExp:                      DExp Intrinsic.
- * intrinsics, DFloat:                    DFloat Intrinsic.
- * intrinsics, DFlotI:                    DFlotI Intrinsic.
- * intrinsics, DFlotJ:                    DFlotJ Intrinsic.
- * intrinsics, Digits:                    Digits Intrinsic.
- * intrinsics, DiM:                       DiM Intrinsic.
- * intrinsics, DImag:                     DImag Intrinsic.
- * intrinsics, DInt:                      DInt Intrinsic.
- * intrinsics, disabled:                  Intrinsic Groups.
- * intrinsics, DLog:                      DLog Intrinsic.
- * intrinsics, DLog10:                    DLog10 Intrinsic.
- * intrinsics, DMax1:                     DMax1 Intrinsic.
- * intrinsics, DMin1:                     DMin1 Intrinsic.
- * intrinsics, DMod:                      DMod Intrinsic.
- * intrinsics, DNInt:                     DNInt Intrinsic.
- * intrinsics, Dot_Product:               Dot_Product Intrinsic.
- * intrinsics, DProd:                     DProd Intrinsic.
- * intrinsics, DReal:                     DReal Intrinsic.
- * intrinsics, DSign:                     DSign Intrinsic.
- * intrinsics, DSin:                      DSin Intrinsic.
- * intrinsics, DSinD:                     DSinD Intrinsic.
- * intrinsics, DSinH:                     DSinH Intrinsic.
- * intrinsics, DSqRt:                     DSqRt Intrinsic.
- * intrinsics, DTan:                      DTan Intrinsic.
- * intrinsics, DTanD:                     DTanD Intrinsic.
- * intrinsics, DTanH:                     DTanH Intrinsic.
- * intrinsics, DTime <1>:                 DTime Intrinsic (function).
- * intrinsics, DTime:                     DTime Intrinsic (subroutine).
- * intrinsics, enabled:                   Intrinsic Groups.
- * intrinsics, EOShift:                   EOShift Intrinsic.
- * intrinsics, Epsilon:                   Epsilon Intrinsic.
- * intrinsics, ErF:                       ErF Intrinsic.
- * intrinsics, ErFC:                      ErFC Intrinsic.
- * intrinsics, ETime <1>:                 ETime Intrinsic (function).
- * intrinsics, ETime:                     ETime Intrinsic (subroutine).
- * intrinsics, Exit:                      Exit Intrinsic.
- * intrinsics, Exp:                       Exp Intrinsic.
- * intrinsics, Exponent:                  Exponent Intrinsic.
- * intrinsics, f2c:                       Fortran Dialect Options.
- * intrinsics, FDate <1>:                 FDate Intrinsic (function).
- * intrinsics, FDate:                     FDate Intrinsic (subroutine).
- * intrinsics, FGet <1>:                  FGet Intrinsic (function).
- * intrinsics, FGet:                      FGet Intrinsic (subroutine).
- * intrinsics, FGetC <1>:                 FGetC Intrinsic (function).
- * intrinsics, FGetC:                     FGetC Intrinsic (subroutine).
- * intrinsics, Float:                     Float Intrinsic.
- * intrinsics, FloatI:                    FloatI Intrinsic.
- * intrinsics, FloatJ:                    FloatJ Intrinsic.
- * intrinsics, Floor:                     Floor Intrinsic.
- * intrinsics, Flush:                     Flush Intrinsic.
- * intrinsics, FNum:                      FNum Intrinsic.
- * intrinsics, Fortran 90:                Fortran Dialect Options.
- * intrinsics, FPut <1>:                  FPut Intrinsic (function).
- * intrinsics, FPut:                      FPut Intrinsic (subroutine).
- * intrinsics, FPutC <1>:                 FPutC Intrinsic (function).
- * intrinsics, FPutC:                     FPutC Intrinsic (subroutine).
- * intrinsics, Fraction:                  Fraction Intrinsic.
- * intrinsics, FSeek:                     FSeek Intrinsic.
- * intrinsics, FStat <1>:                 FStat Intrinsic (function).
- * intrinsics, FStat:                     FStat Intrinsic (subroutine).
- * intrinsics, FTell <1>:                 FTell Intrinsic (function).
- * intrinsics, FTell:                     FTell Intrinsic (subroutine).
- * intrinsics, generic:                   Generics and Specifics.
- * intrinsics, GError:                    GError Intrinsic.
- * intrinsics, GetArg <1>:                Main Program Unit.
- * intrinsics, GetArg:                    GetArg Intrinsic.
- * intrinsics, GetCWD <1>:                GetCWD Intrinsic (function).
- * intrinsics, GetCWD:                    GetCWD Intrinsic (subroutine).
- * intrinsics, GetEnv:                    GetEnv Intrinsic.
- * intrinsics, GetGId:                    GetGId Intrinsic.
- * intrinsics, GetLog:                    GetLog Intrinsic.
- * intrinsics, GetPId:                    GetPId Intrinsic.
- * intrinsics, GetUId:                    GetUId Intrinsic.
- * intrinsics, GMTime:                    GMTime Intrinsic.
- * intrinsics, groups:                    Intrinsic Groups.
- * intrinsics, groups of:                 Intrinsic Groups.
- * intrinsics, hidden:                    Intrinsic Groups.
- * intrinsics, HostNm <1>:                HostNm Intrinsic (function).
- * intrinsics, HostNm:                    HostNm Intrinsic (subroutine).
- * intrinsics, Huge:                      Huge Intrinsic.
- * intrinsics, IAbs:                      IAbs Intrinsic.
- * intrinsics, IAChar:                    IAChar Intrinsic.
- * intrinsics, IAnd:                      IAnd Intrinsic.
- * intrinsics, IArgC <1>:                 Main Program Unit.
- * intrinsics, IArgC:                     IArgC Intrinsic.
- * intrinsics, IBClr:                     IBClr Intrinsic.
- * intrinsics, IBits:                     IBits Intrinsic.
- * intrinsics, IBSet:                     IBSet Intrinsic.
- * intrinsics, IChar:                     IChar Intrinsic.
- * intrinsics, IDate <1>:                 IDate Intrinsic (VXT).
- * intrinsics, IDate:                     IDate Intrinsic (UNIX).
- * intrinsics, IDiM:                      IDiM Intrinsic.
- * intrinsics, IDInt:                     IDInt Intrinsic.
- * intrinsics, IDNInt:                    IDNInt Intrinsic.
- * intrinsics, IEOr:                      IEOr Intrinsic.
- * intrinsics, IErrNo:                    IErrNo Intrinsic.
- * intrinsics, IFix:                      IFix Intrinsic.
- * intrinsics, IIAbs:                     IIAbs Intrinsic.
- * intrinsics, IIAnd:                     IIAnd Intrinsic.
- * intrinsics, IIBClr:                    IIBClr Intrinsic.
- * intrinsics, IIBits:                    IIBits Intrinsic.
- * intrinsics, IIBSet:                    IIBSet Intrinsic.
- * intrinsics, IIDiM:                     IIDiM Intrinsic.
- * intrinsics, IIDInt:                    IIDInt Intrinsic.
- * intrinsics, IIDNnt:                    IIDNnt Intrinsic.
- * intrinsics, IIEOr:                     IIEOr Intrinsic.
- * intrinsics, IIFix:                     IIFix Intrinsic.
- * intrinsics, IInt:                      IInt Intrinsic.
- * intrinsics, IIOr:                      IIOr Intrinsic.
- * intrinsics, IIQint:                    IIQint Intrinsic.
- * intrinsics, IIQNnt:                    IIQNnt Intrinsic.
- * intrinsics, IIShftC:                   IIShftC Intrinsic.
- * intrinsics, IISign:                    IISign Intrinsic.
- * intrinsics, Imag:                      Imag Intrinsic.
- * intrinsics, ImagPart:                  ImagPart Intrinsic.
- * intrinsics, IMax0:                     IMax0 Intrinsic.
- * intrinsics, IMax1:                     IMax1 Intrinsic.
- * intrinsics, IMin0:                     IMin0 Intrinsic.
- * intrinsics, IMin1:                     IMin1 Intrinsic.
- * intrinsics, IMod:                      IMod Intrinsic.
- * intrinsics, Index:                     Index Intrinsic.
- * intrinsics, INInt:                     INInt Intrinsic.
- * intrinsics, INot:                      INot Intrinsic.
- * intrinsics, Int:                       Int Intrinsic.
- * intrinsics, Int2:                      Int2 Intrinsic.
- * intrinsics, Int8:                      Int8 Intrinsic.
- * intrinsics, IOr:                       IOr Intrinsic.
- * intrinsics, IRand:                     IRand Intrinsic.
- * intrinsics, IsaTty:                    IsaTty Intrinsic.
- * intrinsics, IShft:                     IShft Intrinsic.
- * intrinsics, IShftC:                    IShftC Intrinsic.
- * intrinsics, ISign:                     ISign Intrinsic.
- * intrinsics, ITime:                     ITime Intrinsic.
- * intrinsics, IZExt:                     IZExt Intrinsic.
- * intrinsics, JIAbs:                     JIAbs Intrinsic.
- * intrinsics, JIAnd:                     JIAnd Intrinsic.
- * intrinsics, JIBClr:                    JIBClr Intrinsic.
- * intrinsics, JIBits:                    JIBits Intrinsic.
- * intrinsics, JIBSet:                    JIBSet Intrinsic.
- * intrinsics, JIDiM:                     JIDiM Intrinsic.
- * intrinsics, JIDInt:                    JIDInt Intrinsic.
- * intrinsics, JIDNnt:                    JIDNnt Intrinsic.
- * intrinsics, JIEOr:                     JIEOr Intrinsic.
- * intrinsics, JIFix:                     JIFix Intrinsic.
- * intrinsics, JInt:                      JInt Intrinsic.
- * intrinsics, JIOr:                      JIOr Intrinsic.
- * intrinsics, JIQint:                    JIQint Intrinsic.
- * intrinsics, JIQNnt:                    JIQNnt Intrinsic.
- * intrinsics, JIShft:                    JIShft Intrinsic.
- * intrinsics, JIShftC:                   JIShftC Intrinsic.
- * intrinsics, JISign:                    JISign Intrinsic.
- * intrinsics, JMax0:                     JMax0 Intrinsic.
- * intrinsics, JMax1:                     JMax1 Intrinsic.
- * intrinsics, JMin0:                     JMin0 Intrinsic.
- * intrinsics, JMin1:                     JMin1 Intrinsic.
- * intrinsics, JMod:                      JMod Intrinsic.
- * intrinsics, JNInt:                     JNInt Intrinsic.
- * intrinsics, JNot:                      JNot Intrinsic.
- * intrinsics, JZExt:                     JZExt Intrinsic.
- * intrinsics, Kill <1>:                  Kill Intrinsic (function).
- * intrinsics, Kill:                      Kill Intrinsic (subroutine).
- * intrinsics, Kind:                      Kind Intrinsic.
- * intrinsics, LBound:                    LBound Intrinsic.
- * intrinsics, Len:                       Len Intrinsic.
- * intrinsics, Len_Trim:                  Len_Trim Intrinsic.
- * intrinsics, LGe:                       LGe Intrinsic.
- * intrinsics, LGt:                       LGt Intrinsic.
- * intrinsics, Link <1>:                  Link Intrinsic (function).
- * intrinsics, Link:                      Link Intrinsic (subroutine).
- * intrinsics, LLe:                       LLe Intrinsic.
- * intrinsics, LLt:                       LLt Intrinsic.
- * intrinsics, LnBlnk:                    LnBlnk Intrinsic.
- * intrinsics, Loc:                       Loc Intrinsic.
- * intrinsics, Log:                       Log Intrinsic.
- * intrinsics, Log10:                     Log10 Intrinsic.
- * intrinsics, Logical:                   Logical Intrinsic.
- * intrinsics, Long:                      Long Intrinsic.
- * intrinsics, LShift:                    LShift Intrinsic.
- * intrinsics, LStat <1>:                 LStat Intrinsic (function).
- * intrinsics, LStat:                     LStat Intrinsic (subroutine).
- * intrinsics, LTime:                     LTime Intrinsic.
- * intrinsics, MatMul:                    MatMul Intrinsic.
- * intrinsics, Max:                       Max Intrinsic.
- * intrinsics, Max0:                      Max0 Intrinsic.
- * intrinsics, Max1:                      Max1 Intrinsic.
- * intrinsics, MaxExponent:               MaxExponent Intrinsic.
- * intrinsics, MaxLoc:                    MaxLoc Intrinsic.
- * intrinsics, MaxVal:                    MaxVal Intrinsic.
- * intrinsics, MClock:                    MClock Intrinsic.
- * intrinsics, MClock8:                   MClock8 Intrinsic.
- * intrinsics, Merge:                     Merge Intrinsic.
- * intrinsics, MIL-STD 1753:              Fortran Dialect Options.
- * intrinsics, Min:                       Min Intrinsic.
- * intrinsics, Min0:                      Min0 Intrinsic.
- * intrinsics, Min1:                      Min1 Intrinsic.
- * intrinsics, MinExponent:               MinExponent Intrinsic.
- * intrinsics, MinLoc:                    MinLoc Intrinsic.
- * intrinsics, MinVal:                    MinVal Intrinsic.
- * intrinsics, Mod:                       Mod Intrinsic.
- * intrinsics, Modulo:                    Modulo Intrinsic.
- * intrinsics, MvBits:                    MvBits Intrinsic.
- * intrinsics, Nearest:                   Nearest Intrinsic.
- * intrinsics, NInt:                      NInt Intrinsic.
- * intrinsics, Not:                       Not Intrinsic.
- * intrinsics, Or <1>:                    Bit Operations on Floating-point Data.
- * intrinsics, Or:                        Or Intrinsic.
- * intrinsics, others:                    Other Intrinsics.
- * intrinsics, Pack:                      Pack Intrinsic.
- * intrinsics, PError:                    PError Intrinsic.
- * intrinsics, Precision:                 Precision Intrinsic.
- * intrinsics, Present:                   Present Intrinsic.
- * intrinsics, Product:                   Product Intrinsic.
- * intrinsics, QAbs:                      QAbs Intrinsic.
- * intrinsics, QACos:                     QACos Intrinsic.
- * intrinsics, QACosD:                    QACosD Intrinsic.
- * intrinsics, QASin:                     QASin Intrinsic.
- * intrinsics, QASinD:                    QASinD Intrinsic.
- * intrinsics, QATan:                     QATan Intrinsic.
- * intrinsics, QATan2:                    QATan2 Intrinsic.
- * intrinsics, QATan2D:                   QATan2D Intrinsic.
- * intrinsics, QATanD:                    QATanD Intrinsic.
- * intrinsics, QCos:                      QCos Intrinsic.
- * intrinsics, QCosD:                     QCosD Intrinsic.
- * intrinsics, QCosH:                     QCosH Intrinsic.
- * intrinsics, QDiM:                      QDiM Intrinsic.
- * intrinsics, QExp:                      QExp Intrinsic.
- * intrinsics, QExt:                      QExt Intrinsic.
- * intrinsics, QExtD:                     QExtD Intrinsic.
- * intrinsics, QFloat:                    QFloat Intrinsic.
- * intrinsics, QInt:                      QInt Intrinsic.
- * intrinsics, QLog:                      QLog Intrinsic.
- * intrinsics, QLog10:                    QLog10 Intrinsic.
- * intrinsics, QMax1:                     QMax1 Intrinsic.
- * intrinsics, QMin1:                     QMin1 Intrinsic.
- * intrinsics, QMod:                      QMod Intrinsic.
- * intrinsics, QNInt:                     QNInt Intrinsic.
- * intrinsics, QSin:                      QSin Intrinsic.
- * intrinsics, QSinD:                     QSinD Intrinsic.
- * intrinsics, QSinH:                     QSinH Intrinsic.
- * intrinsics, QSqRt:                     QSqRt Intrinsic.
- * intrinsics, QTan:                      QTan Intrinsic.
- * intrinsics, QTanD:                     QTanD Intrinsic.
- * intrinsics, QTanH:                     QTanH Intrinsic.
- * intrinsics, Radix:                     Radix Intrinsic.
- * intrinsics, Rand:                      Rand Intrinsic.
- * intrinsics, Random_Number:             Random_Number Intrinsic.
- * intrinsics, Random_Seed:               Random_Seed Intrinsic.
- * intrinsics, Range:                     Range Intrinsic.
- * intrinsics, Real <1>:                  Real Intrinsic.
- * intrinsics, Real:                      REAL() and AIMAG() of Complex.
- * intrinsics, RealPart:                  RealPart Intrinsic.
- * intrinsics, Rename <1>:                Rename Intrinsic (function).
- * intrinsics, Rename:                    Rename Intrinsic (subroutine).
- * intrinsics, Repeat:                    Repeat Intrinsic.
- * intrinsics, Reshape:                   Reshape Intrinsic.
- * intrinsics, RRSpacing:                 RRSpacing Intrinsic.
- * intrinsics, RShift:                    RShift Intrinsic.
- * intrinsics, Scale:                     Scale Intrinsic.
- * intrinsics, Scan:                      Scan Intrinsic.
- * intrinsics, Secnds:                    Secnds Intrinsic.
- * intrinsics, Second <1>:                Second Intrinsic (subroutine).
- * intrinsics, Second:                    Second Intrinsic (function).
- * intrinsics, Selected_Int_Kind:         Selected_Int_Kind Intrinsic.
- * intrinsics, Selected_Real_Kind:        Selected_Real_Kind Intrinsic.
- * intrinsics, Set_Exponent:              Set_Exponent Intrinsic.
- * intrinsics, Shape:                     Shape Intrinsic.
- * intrinsics, Shift:                     Bit Operations on Floating-point Data.
- * intrinsics, Short:                     Short Intrinsic.
- * intrinsics, Sign:                      Sign Intrinsic.
- * intrinsics, Signal <1>:                Signal Intrinsic (function).
- * intrinsics, Signal:                    Signal Intrinsic (subroutine).
- * intrinsics, Sin:                       Sin Intrinsic.
- * intrinsics, SinD:                      SinD Intrinsic.
- * intrinsics, SinH:                      SinH Intrinsic.
- * intrinsics, Sleep:                     Sleep Intrinsic.
- * intrinsics, Sngl:                      Sngl Intrinsic.
- * intrinsics, SnglQ:                     SnglQ Intrinsic.
- * intrinsics, Spacing:                   Spacing Intrinsic.
- * intrinsics, Spread:                    Spread Intrinsic.
- * intrinsics, SqRt:                      SqRt Intrinsic.
- * intrinsics, SRand:                     SRand Intrinsic.
- * intrinsics, Stat <1>:                  Stat Intrinsic (function).
- * intrinsics, Stat:                      Stat Intrinsic (subroutine).
- * intrinsics, Sum:                       Sum Intrinsic.
- * intrinsics, SymLnk <1>:                SymLnk Intrinsic (function).
- * intrinsics, SymLnk:                    SymLnk Intrinsic (subroutine).
- * intrinsics, System <1>:                System Intrinsic (function).
- * intrinsics, System:                    System Intrinsic (subroutine).
- * intrinsics, System_Clock:              System_Clock Intrinsic.
- * intrinsics, table of:                  Table of Intrinsic Functions.
- * intrinsics, Tan:                       Tan Intrinsic.
- * intrinsics, TanD:                      TanD Intrinsic.
- * intrinsics, TanH:                      TanH Intrinsic.
- * intrinsics, Time <1>:                  Time Intrinsic (VXT).
- * intrinsics, Time:                      Time Intrinsic (UNIX).
- * intrinsics, Time8:                     Time8 Intrinsic.
- * intrinsics, Tiny:                      Tiny Intrinsic.
- * intrinsics, Transfer:                  Transfer Intrinsic.
- * intrinsics, Transpose:                 Transpose Intrinsic.
- * intrinsics, Trim:                      Trim Intrinsic.
- * intrinsics, TtyNam <1>:                TtyNam Intrinsic (function).
- * intrinsics, TtyNam:                    TtyNam Intrinsic (subroutine).
- * intrinsics, UBound:                    UBound Intrinsic.
- * intrinsics, UMask <1>:                 UMask Intrinsic (function).
- * intrinsics, UMask:                     UMask Intrinsic (subroutine).
- * intrinsics, UNIX:                      Fortran Dialect Options.
- * intrinsics, Unlink <1>:                Unlink Intrinsic (function).
- * intrinsics, Unlink:                    Unlink Intrinsic (subroutine).
- * intrinsics, Unpack:                    Unpack Intrinsic.
- * intrinsics, Verify:                    Verify Intrinsic.
- * intrinsics, VXT:                       Fortran Dialect Options.
- * intrinsics, XOr:                       XOr Intrinsic.
- * intrinsics, ZAbs:                      ZAbs Intrinsic.
- * intrinsics, ZCos:                      ZCos Intrinsic.
- * intrinsics, ZExp:                      ZExp Intrinsic.
- * intrinsics, ZExt:                      ZExt Intrinsic.
- * intrinsics, ZLog:                      ZLog Intrinsic.
- * intrinsics, ZSin:                      ZSin Intrinsic.
- * intrinsics, ZSqRt:                     ZSqRt Intrinsic.
- * Introduction:                          Top.
- * invalid assembly code:                 Bug Criteria.
- * invalid input:                         Bug Criteria.
- * IOr intrinsic:                         IOr Intrinsic.
- * IOSTAT=:                               Run-time Library Errors.
- * IRand intrinsic:                       IRand Intrinsic.
- * IsaTty intrinsic:                      IsaTty Intrinsic.
- * IShft intrinsic:                       IShft Intrinsic.
- * IShftC intrinsic:                      IShftC Intrinsic.
- * ISign intrinsic:                       ISign Intrinsic.
- * iterative DO:                          Optimize Options.
- * ITime intrinsic:                       ITime Intrinsic.
- * ix86 floating-point:                   Floating-point precision.
- * ix86 FPU stack:                        Inconsistent Calling Sequences.
- * IZExt intrinsic:                       IZExt Intrinsic.
- * JCB002 program:                        Generics and Specifics.
- * JCB003 program:                        CMPAMBIG.
- * JIAbs intrinsic:                       JIAbs Intrinsic.
- * JIAnd intrinsic:                       JIAnd Intrinsic.
- * JIBClr intrinsic:                      JIBClr Intrinsic.
- * JIBits intrinsic:                      JIBits Intrinsic.
- * JIBSet intrinsic:                      JIBSet Intrinsic.
- * JIDiM intrinsic:                       JIDiM Intrinsic.
- * JIDInt intrinsic:                      JIDInt Intrinsic.
- * JIDNnt intrinsic:                      JIDNnt Intrinsic.
- * JIEOr intrinsic:                       JIEOr Intrinsic.
- * JIFix intrinsic:                       JIFix Intrinsic.
- * JInt intrinsic:                        JInt Intrinsic.
- * JIOr intrinsic:                        JIOr Intrinsic.
- * JIQint intrinsic:                      JIQint Intrinsic.
- * JIQNnt intrinsic:                      JIQNnt Intrinsic.
- * JIShft intrinsic:                      JIShft Intrinsic.
- * JIShftC intrinsic:                     JIShftC Intrinsic.
- * JISign intrinsic:                      JISign Intrinsic.
- * JMax0 intrinsic:                       JMax0 Intrinsic.
- * JMax1 intrinsic:                       JMax1 Intrinsic.
- * JMin0 intrinsic:                       JMin0 Intrinsic.
- * JMin1 intrinsic:                       JMin1 Intrinsic.
- * JMod intrinsic:                        JMod Intrinsic.
- * JNInt intrinsic:                       JNInt Intrinsic.
- * JNot intrinsic:                        JNot Intrinsic.
- * JZExt intrinsic:                       JZExt Intrinsic.
- * keywords, RECURSIVE:                   RECURSIVE Keyword.
- * Kill intrinsic <1>:                    Kill Intrinsic (function).
- * Kill intrinsic:                        Kill Intrinsic (subroutine).
- * Kind intrinsic:                        Kind Intrinsic.
- * KIND= notation:                        Kind Notation.
- * known causes of trouble:               Trouble.
- * lack of recursion:                     RECURSIVE Keyword.
- * language, dialect options:             Fortran Dialect Options.
- * language, features:                    Direction of Language Development.
- * language, incorrect use of:            What is GNU Fortran?.
- * large aggregate areas:                 Known Bugs.
- * large common blocks:                   Large Common Blocks.
- * layout of COMMON blocks:               Aligned Data.
- * LBound intrinsic:                      LBound Intrinsic.
- * ld command:                            What is GNU Fortran?.
- * ld, can't find _main:                  Cannot Link Fortran Programs.
- * ld, can't find strange names:          Cannot Link Fortran Programs.
- * ld, error linking user code:           Cannot Link Fortran Programs.
- * ld, errors:                            Large Common Blocks.
- * left angle:                            Character Set.
- * left bracket:                          Character Set.
- * legacy code:                           Collected Fortran Wisdom.
- * Len intrinsic:                         Len Intrinsic.
- * Len_Trim intrinsic:                    Len_Trim Intrinsic.
- * length of source lines:                Fortran Dialect Options.
- * letters, lowercase:                    Case Sensitivity.
- * letters, uppercase:                    Case Sensitivity.
- * LGe intrinsic:                         LGe Intrinsic.
- * LGt intrinsic:                         LGt Intrinsic.
- * libc, non-ANSI or non-default:         Strange Behavior at Run Time.
- * libf2c library:                        What is GNU Fortran?.
- * libg2c library:                        What is GNU Fortran?.
- * libraries:                             What is GNU Fortran?.
- * libraries, containing BLOCK DATA:      Block Data and Libraries.
- * libraries, libf2c:                     What is GNU Fortran?.
- * libraries, libg2c:                     What is GNU Fortran?.
- * limits, array dimensions:              Compiler Limits.
- * limits, array size:                    Array Size.
- * limits, compiler:                      Compiler Limits.
- * limits, continuation lines <1>:        Compiler Limits.
- * limits, continuation lines:            Continuation Line.
- * limits, lengths of names <1>:          Compiler Limits.
- * limits, lengths of names:              Syntactic Items.
- * limits, lengths of source lines:       Fortran Dialect Options.
- * limits, multi-dimension arrays:        Array Size.
- * limits, on character-variable length:  Character-variable Length.
- * limits, rank:                          Compiler Limits.
- * limits, run-time library:              Run-time Environment Limits.
- * limits, timings <1>:                   Secnds Intrinsic.
- * limits, timings <2>:                   DTime Intrinsic (function).
- * limits, timings <3>:                   Time8 Intrinsic.
- * limits, timings <4>:                   Time Intrinsic (UNIX).
- * limits, timings <5>:                   System_Clock Intrinsic.
- * limits, timings <6>:                   Second Intrinsic (subroutine).
- * limits, timings <7>:                   Second Intrinsic (function).
- * limits, timings <8>:                   MClock8 Intrinsic.
- * limits, timings <9>:                   MClock Intrinsic.
- * limits, timings <10>:                  ETime Intrinsic (function).
- * limits, timings <11>:                  ETime Intrinsic (subroutine).
- * limits, timings <12>:                  DTime Intrinsic (subroutine).
- * limits, timings:                       CPU_Time Intrinsic.
- * limits, Y10K <1>:                      Time Intrinsic (VXT).
- * limits, Y10K <2>:                      IDate Intrinsic (UNIX).
- * limits, Y10K <3>:                      FDate Intrinsic (function).
- * limits, Y10K <4>:                      FDate Intrinsic (subroutine).
- * limits, Y10K:                          Date_and_Time Intrinsic.
- * limits, Y2K:                           IDate Intrinsic (VXT).
- * lines:                                 Lines.
- * lines, continuation:                   Continuation Line.
- * lines, length:                         Fortran Dialect Options.
- * lines, long:                           Long Lines.
- * lines, short:                          Short Lines.
- * Link intrinsic <1>:                    Link Intrinsic (function).
- * Link intrinsic:                        Link Intrinsic (subroutine).
- * linking:                               What is GNU Fortran?.
- * linking against non-standard library:  Strange Behavior at Run Time.
- * linking error for user code:           Cannot Link Fortran Programs.
- * linking error, user code:              Cannot Link Fortran Programs.
- * linking with C:                        Interoperating with C and C++.
- * linking, errors:                       Large Common Blocks.
- * LLe intrinsic:                         LLe Intrinsic.
- * LLt intrinsic:                         LLt Intrinsic.
- * LnBlnk intrinsic:                      LnBlnk Intrinsic.
- * Loc intrinsic:                         Loc Intrinsic.
- * local equivalence areas:               Local Equivalence Areas.
- * Log intrinsic:                         Log Intrinsic.
- * Log10 intrinsic:                       Log10 Intrinsic.
- * logical expressions, comparing:        Equivalence Versus Equality.
- * Logical intrinsic:                     Logical Intrinsic.
- * LOGICAL(KIND=1) type:                  Compiler Types.
- * LOGICAL(KIND=2) type:                  Compiler Types.
- * LOGICAL(KIND=3) type:                  Compiler Types.
- * LOGICAL(KIND=6) type:                  Compiler Types.
- * LOGICAL*1 support:                     Popular Non-standard Types.
- * Long intrinsic:                        Long Intrinsic.
- * long source lines:                     Long Lines.
- * long time:                             Timer Wraparounds.
- * loops, optimizing:                     Optimize Options.
- * loops, speeding up:                    Optimize Options.
- * loops, unrolling:                      Optimize Options.
- * lowercase letters:                     Case Sensitivity.
- * LShift intrinsic:                      LShift Intrinsic.
- * LStat intrinsic <1>:                   LStat Intrinsic (function).
- * LStat intrinsic:                       LStat Intrinsic (subroutine).
- * LTime intrinsic:                       LTime Intrinsic.
- * machine code:                          What is GNU Fortran?.
- * macro options:                         Shorthand Options.
- * main program unit, debugging:          Main Program Unit.
- * main():                                Main Program Unit.
- * MAIN__():                              Main Program Unit.
- * Makefile example:                      Bug Criteria.
- * MAP statement:                         STRUCTURE UNION RECORD MAP.
- * MatMul intrinsic:                      MatMul Intrinsic.
- * Max intrinsic:                         Max Intrinsic.
- * Max0 intrinsic:                        Max0 Intrinsic.
- * Max1 intrinsic:                        Max1 Intrinsic.
- * MaxExponent intrinsic:                 MaxExponent Intrinsic.
- * maximum number of dimensions:          Compiler Limits.
- * maximum rank:                          Compiler Limits.
- * maximum unit number:                   Large File Unit Numbers.
- * MaxLoc intrinsic:                      MaxLoc Intrinsic.
- * MaxVal intrinsic:                      MaxVal Intrinsic.
- * MClock intrinsic:                      MClock Intrinsic.
- * MClock8 intrinsic:                     MClock8 Intrinsic.
- * memory usage, of compiler:             Known Bugs.
- * Merge intrinsic:                       Merge Intrinsic.
- * messages, run-time:                    Run-time Library Errors.
- * messages, warning:                     Warning Options.
- * messages, warning and error:           Warnings and Errors.
- * mil intrinsics group:                  Intrinsic Groups.
- * MIL-STD 1753 <1>:                      MIL-STD 1753.
- * MIL-STD 1753 <2>:                      END DO.
- * MIL-STD 1753 <3>:                      DO WHILE.
- * MIL-STD 1753:                          Fortran Dialect Options.
- * Min intrinsic:                         Min Intrinsic.
- * Min0 intrinsic:                        Min0 Intrinsic.
- * Min1 intrinsic:                        Min1 Intrinsic.
- * MinExponent intrinsic:                 MinExponent Intrinsic.
- * MinLoc intrinsic:                      MinLoc Intrinsic.
- * MinVal intrinsic:                      MinVal Intrinsic.
- * mistakes:                              What is GNU Fortran?.
- * mistyped functions:                    Not My Type.
- * mistyped variables:                    Not My Type.
- * Mod intrinsic:                         Mod Intrinsic.
- * modifying g77:                         Overall Options.
- * Modulo intrinsic:                      Modulo Intrinsic.
- * multi-dimension arrays:                Array Size.
- * MvBits intrinsic:                      MvBits Intrinsic.
- * MXUNIT:                                Large File Unit Numbers.
- * name space:                            Mangling of Names.
- * NAMELIST statement:                    NAMELIST.
- * naming conflicts:                      Multiple Definitions of External Names.
- * naming issues:                         Mangling of Names.
- * naming programs:                       Nothing Happens.
- * NaN values:                            Floating-point Exception Handling.
- * Nearest intrinsic:                     Nearest Intrinsic.
- * negative forms of options:             Invoking G77.
- * negative time:                         Timer Wraparounds.
- * Netlib <1>:                            Increasing Precision/Range.
- * Netlib:                                C Interfacing Tools.
- * network file system:                   Output Assumed To Flush.
- * new users:                             Getting Started.
- * newbies:                               Getting Started.
- * NeXTStep problems:                     NeXTStep Problems.
- * NFS:                                   Output Assumed To Flush.
- * NInt intrinsic:                        NInt Intrinsic.
- * nonportable conversions:               Nonportable Conversions.
- * Not intrinsic:                         Not Intrinsic.
- * nothing happens:                       Nothing Happens.
- * null arguments:                        Ugly Null Arguments.
- * null byte, trailing:                   Character and Hollerith Constants.
- * null CHARACTER strings:                Character Type.
- * number of continuation lines:          Continuation Line.
- * number of dimensions, maximum:         Compiler Limits.
- * number of trips:                       Loops.
- * O edit descriptor:                     I/O.
- * octal constants:                       Double Quote Meaning.
- * omitting arguments:                    Ugly Null Arguments.
- * one-trip DO loops:                     Fortran Dialect Options.
- * open angle:                            Character Set.
- * open bracket:                          Character Set.
- * OPEN statement:                        OPEN CLOSE and INQUIRE Keywords.
- * optimization, better:                  Better Optimization.
- * optimization, for Pentium:             Aligned Data.
- * optimize options:                      Optimize Options.
- * options, --driver <1>:                 Changes.
- * options, --driver:                     News.
- * options, -falias-check <1>:            Aliasing Assumed To Work.
- * options, -falias-check:                Code Gen Options.
- * options, -fargument-alias <1>:         Aliasing Assumed To Work.
- * options, -fargument-alias:             Code Gen Options.
- * options, -fargument-noalias <1>:       Aliasing Assumed To Work.
- * options, -fargument-noalias:           Code Gen Options.
- * options, -fbadu77-intrinsics-delete:   Fortran Dialect Options.
- * options, -fbadu77-intrinsics-disable:  Fortran Dialect Options.
- * options, -fbadu77-intrinsics-enable:   Fortran Dialect Options.
- * options, -fbadu77-intrinsics-hide:     Fortran Dialect Options.
- * options, -fcaller-saves:               Optimize Options.
- * options, -fcase-initcap:               Fortran Dialect Options.
- * options, -fcase-lower:                 Fortran Dialect Options.
- * options, -fcase-preserve:              Fortran Dialect Options.
- * options, -fcase-strict-lower:          Fortran Dialect Options.
- * options, -fcase-strict-upper:          Fortran Dialect Options.
- * options, -fcase-upper:                 Fortran Dialect Options.
- * options, -fdelayed-branch:             Optimize Options.
- * options, -fdollar-ok:                  Fortran Dialect Options.
- * options, -femulate-complex:            Code Gen Options.
- * options, -fexpensive-optimizations:    Optimize Options.
- * options, -ff2c-intrinsics-delete:      Fortran Dialect Options.
- * options, -ff2c-intrinsics-disable:     Fortran Dialect Options.
- * options, -ff2c-intrinsics-enable:      Fortran Dialect Options.
- * options, -ff2c-intrinsics-hide:        Fortran Dialect Options.
- * options, -ff2c-library:                Code Gen Options.
- * options, -ff66:                        Shorthand Options.
- * options, -ff77:                        Shorthand Options.
- * options, -ff90:                        Fortran Dialect Options.
- * options, -ff90-intrinsics-delete:      Fortran Dialect Options.
- * options, -ff90-intrinsics-disable:     Fortran Dialect Options.
- * options, -ff90-intrinsics-enable:      Fortran Dialect Options.
- * options, -ff90-intrinsics-hide:        Fortran Dialect Options.
- * options, -ffast-math:                  Optimize Options.
- * options, -ffixed-line-length-N:        Fortran Dialect Options.
- * options, -ffloat-store:                Optimize Options.
- * options, -fforce-addr:                 Optimize Options.
- * options, -fforce-mem:                  Optimize Options.
- * options, -ffree-form:                  Fortran Dialect Options.
- * options, -fgnu-intrinsics-delete:      Fortran Dialect Options.
- * options, -fgnu-intrinsics-disable:     Fortran Dialect Options.
- * options, -fgnu-intrinsics-enable:      Fortran Dialect Options.
- * options, -fgnu-intrinsics-hide:        Fortran Dialect Options.
- * options, -fGROUP-intrinsics-hide:      Overly Convenient Options.
- * options, -finit-local-zero <1>:        Overly Convenient Options.
- * options, -finit-local-zero:            Code Gen Options.
- * options, -fintrin-case-any:            Fortran Dialect Options.
- * options, -fintrin-case-initcap:        Fortran Dialect Options.
- * options, -fintrin-case-lower:          Fortran Dialect Options.
- * options, -fintrin-case-upper:          Fortran Dialect Options.
- * options, -fmatch-case-any:             Fortran Dialect Options.
- * options, -fmatch-case-initcap:         Fortran Dialect Options.
- * options, -fmatch-case-lower:           Fortran Dialect Options.
- * options, -fmatch-case-upper:           Fortran Dialect Options.
- * options, -fmil-intrinsics-delete:      Fortran Dialect Options.
- * options, -fmil-intrinsics-disable:     Fortran Dialect Options.
- * options, -fmil-intrinsics-enable:      Fortran Dialect Options.
- * options, -fmil-intrinsics-hide:        Fortran Dialect Options.
- * options, -fno-argument-noalias-global <1>: Aliasing Assumed To Work.
- * options, -fno-argument-noalias-global: Code Gen Options.
- * options, -fno-automatic <1>:           Overly Convenient Options.
- * options, -fno-automatic:               Code Gen Options.
- * options, -fno-backslash:               Fortran Dialect Options.
- * options, -fno-common:                  Code Gen Options.
- * options, -fno-f2c <1>:                 Avoid f2c Compatibility.
- * options, -fno-f2c:                     Code Gen Options.
- * options, -fno-f77:                     Shorthand Options.
- * options, -fno-fixed-form:              Fortran Dialect Options.
- * options, -fno-globals:                 Code Gen Options.
- * options, -fno-ident:                   Code Gen Options.
- * options, -fno-inline:                  Optimize Options.
- * options, -fno-move-all-movables:       Optimize Options.
- * options, -fno-reduce-all-givs:         Optimize Options.
- * options, -fno-rerun-loop-opt:          Optimize Options.
- * options, -fno-second-underscore:       Code Gen Options.
- * options, -fno-silent:                  Overall Options.
- * options, -fno-trapping-math:           Optimize Options.
- * options, -fno-ugly:                    Shorthand Options.
- * options, -fno-ugly-args:               Fortran Dialect Options.
- * options, -fno-ugly-init:               Fortran Dialect Options.
- * options, -fno-underscoring <1>:        Names.
- * options, -fno-underscoring:            Code Gen Options.
- * options, -fonetrip:                    Fortran Dialect Options.
- * options, -fpack-struct:                Code Gen Options.
- * options, -fpcc-struct-return:          Code Gen Options.
- * options, -fpedantic:                   Warning Options.
- * options, -fPIC:                        News.
- * options, -freg-struct-return:          Code Gen Options.
- * options, -frerun-cse-after-loop:       Optimize Options.
- * options, -fschedule-insns:             Optimize Options.
- * options, -fschedule-insns2:            Optimize Options.
- * options, -fset-g77-defaults:           Overall Options.
- * options, -fshort-double:               Code Gen Options.
- * options, -fsource-case-lower:          Fortran Dialect Options.
- * options, -fsource-case-preserve:       Fortran Dialect Options.
- * options, -fsource-case-upper:          Fortran Dialect Options.
- * options, -fstrength-reduce:            Optimize Options.
- * options, -fsymbol-case-any:            Fortran Dialect Options.
- * options, -fsymbol-case-initcap:        Fortran Dialect Options.
- * options, -fsymbol-case-lower:          Fortran Dialect Options.
- * options, -fsymbol-case-upper:          Fortran Dialect Options.
- * options, -fsyntax-only:                Warning Options.
- * options, -ftypeless-boz:               Fortran Dialect Options.
- * options, -fugly:                       Shorthand Options.
- * options, -fugly-assign:                Fortran Dialect Options.
- * options, -fugly-assumed:               Fortran Dialect Options.
- * options, -fugly-comma:                 Fortran Dialect Options.
- * options, -fugly-complex:               Fortran Dialect Options.
- * options, -fugly-logint:                Fortran Dialect Options.
- * options, -funix-intrinsics-delete:     Fortran Dialect Options.
- * options, -funix-intrinsics-disable:    Fortran Dialect Options.
- * options, -funix-intrinsics-enable:     Fortran Dialect Options.
- * options, -funix-intrinsics-hide:       Fortran Dialect Options.
- * options, -funroll-all-loops:           Optimize Options.
- * options, -funroll-loops:               Optimize Options.
- * options, -funsafe-math-optimizations:  Optimize Options.
- * options, -fversion:                    Overall Options.
- * options, -fvxt:                        Fortran Dialect Options.
- * options, -fvxt-intrinsics-delete:      Fortran Dialect Options.
- * options, -fvxt-intrinsics-disable:     Fortran Dialect Options.
- * options, -fvxt-intrinsics-enable:      Fortran Dialect Options.
- * options, -fvxt-intrinsics-hide:        Fortran Dialect Options.
- * options, -fzeros:                      Code Gen Options.
- * options, -g:                           Debugging Options.
- * options, -I-:                          Directory Options.
- * options, -Idir:                        Directory Options.
- * options, -malign-double <1>:           Aligned Data.
- * options, -malign-double:               Optimize Options.
- * options, -Nl:                          Compiler Limits.
- * options, -Nx:                          Compiler Limits.
- * options, -pedantic:                    Warning Options.
- * options, -pedantic-errors:             Warning Options.
- * options, -v:                           G77 and GCC.
- * options, -W:                           Warning Options.
- * options, -w:                           Warning Options.
- * options, -Waggregate-return:           Warning Options.
- * options, -Wall:                        Warning Options.
- * options, -Wcomment:                    Warning Options.
- * options, -Wconversion:                 Warning Options.
- * options, -Werror:                      Warning Options.
- * options, -Wformat:                     Warning Options.
- * options, -Wid-clash-LEN:               Warning Options.
- * options, -Wimplicit:                   Warning Options.
- * options, -Wlarger-than-LEN:            Warning Options.
- * options, -Wno-globals:                 Warning Options.
- * options, -Wparentheses:                Warning Options.
- * options, -Wredundant-decls:            Warning Options.
- * options, -Wshadow:                     Warning Options.
- * options, -Wsurprising:                 Warning Options.
- * options, -Wswitch:                     Warning Options.
- * options, -Wtraditional:                Warning Options.
- * options, -Wuninitialized:              Warning Options.
- * options, -Wunused:                     Warning Options.
- * options, -x f77-cpp-input:             LEX.
- * options, adding:                       Adding Options.
- * options, code generation:              Code Gen Options.
- * options, debugging:                    Debugging Options.
- * options, dialect:                      Fortran Dialect Options.
- * options, directory search:             Directory Options.
- * options, GNU Fortran command:          Invoking G77.
- * options, macro:                        Shorthand Options.
- * options, negative forms:               Invoking G77.
- * options, optimization:                 Optimize Options.
- * options, overall:                      Overall Options.
- * options, overly convenient:            Overly Convenient Options.
- * options, preprocessor:                 Preprocessor Options.
- * options, shorthand:                    Shorthand Options.
- * options, warnings:                     Warning Options.
- * Or intrinsic <1>:                      Bit Operations on Floating-point Data.
- * Or intrinsic:                          Or Intrinsic.
- * order of evaluation, side effects:     Order of Side Effects.
- * ordering, array:                       Arrays.
- * other intrinsics:                      Other Intrinsics.
- * output, flushing:                      Output Assumed To Flush.
- * overall options:                       Overall Options.
- * overflow:                              Warning Options.
- * overlapping arguments:                 Aliasing Assumed To Work.
- * overlays:                              Aliasing Assumed To Work.
- * overly convenient options:             Overly Convenient Options.
- * overwritten data:                      Strange Behavior at Run Time.
- * Pack intrinsic:                        Pack Intrinsic.
- * padding:                               Known Bugs.
- * parallel processing:                   Support for Threads.
- * PARAMETER statement <1>:               Old-style PARAMETER Statements.
- * PARAMETER statement:                   Intrinsics in PARAMETER Statements.
- * parameters, unused:                    Warning Options.
- * paths, search:                         Directory Options.
- * PDB:                                   Portable Unformatted Files.
- * pedantic compilation:                  Pedantic Compilation.
- * Pentium optimizations:                 Aligned Data.
- * percent sign:                          Character Set.
- * PError intrinsic:                      PError Intrinsic.
- * placing initialization statements:     Initializing Before Specifying.
- * POINTER statement:                     POINTER Statements.
- * pointers <1>:                          Ugly Assigned Labels.
- * pointers:                              Kind Notation.
- * Poking the bear:                       Philosophy of Code Generation.
- * porting, simplify:                     Simplify Porting.
- * pound sign:                            Character Set.
- * Precision intrinsic:                   Precision Intrinsic.
- * precision, increasing:                 Increasing Precision/Range.
- * prefix-radix constants:                Fortran Dialect Options.
- * preprocessor <1>:                      LEX.
- * preprocessor <2>:                      Bug Reporting.
- * preprocessor <3>:                      Cpp-style directives.
- * preprocessor <4>:                      Overall Options.
- * preprocessor:                          What is GNU Fortran?.
- * preprocessor options:                  Preprocessor Options.
- * Present intrinsic:                     Present Intrinsic.
- * printing compilation status:           Overall Options.
- * printing main source:                  Known Bugs.
- * printing version information <1>:      Overall Options.
- * printing version information:          What is GNU Fortran?.
- * procedures:                            Procedures.
- * Product intrinsic:                     Product Intrinsic.
- * PROGRAM statement:                     Main Program Unit.
- * programs, cc1:                         What is GNU Fortran?.
- * programs, cc1plus:                     What is GNU Fortran?.
- * programs, compiling:                   G77 and GCC.
- * programs, cpp <1>:                     LEX.
- * programs, cpp <2>:                     Bug Reporting.
- * programs, cpp <3>:                     Preprocessor Options.
- * programs, cpp <4>:                     Overall Options.
- * programs, cpp:                         What is GNU Fortran?.
- * programs, f771:                        What is GNU Fortran?.
- * programs, ratfor:                      Overall Options.
- * programs, speeding up:                 Faster Programs.
- * programs, test:                        Nothing Happens.
- * projects:                              Projects.
- * Q edit descriptor:                     Q Edit Descriptor.
- * QAbs intrinsic:                        QAbs Intrinsic.
- * QACos intrinsic:                       QACos Intrinsic.
- * QACosD intrinsic:                      QACosD Intrinsic.
- * QASin intrinsic:                       QASin Intrinsic.
- * QASinD intrinsic:                      QASinD Intrinsic.
- * QATan intrinsic:                       QATan Intrinsic.
- * QATan2 intrinsic:                      QATan2 Intrinsic.
- * QATan2D intrinsic:                     QATan2D Intrinsic.
- * QATanD intrinsic:                      QATanD Intrinsic.
- * QCos intrinsic:                        QCos Intrinsic.
- * QCosD intrinsic:                       QCosD Intrinsic.
- * QCosH intrinsic:                       QCosH Intrinsic.
- * QDiM intrinsic:                        QDiM Intrinsic.
- * QExp intrinsic:                        QExp Intrinsic.
- * QExt intrinsic:                        QExt Intrinsic.
- * QExtD intrinsic:                       QExtD Intrinsic.
- * QFloat intrinsic:                      QFloat Intrinsic.
- * QInt intrinsic:                        QInt Intrinsic.
- * QLog intrinsic:                        QLog Intrinsic.
- * QLog10 intrinsic:                      QLog10 Intrinsic.
- * QMax1 intrinsic:                       QMax1 Intrinsic.
- * QMin1 intrinsic:                       QMin1 Intrinsic.
- * QMod intrinsic:                        QMod Intrinsic.
- * QNInt intrinsic:                       QNInt Intrinsic.
- * QSin intrinsic:                        QSin Intrinsic.
- * QSinD intrinsic:                       QSinD Intrinsic.
- * QSinH intrinsic:                       QSinH Intrinsic.
- * QSqRt intrinsic:                       QSqRt Intrinsic.
- * QTan intrinsic:                        QTan Intrinsic.
- * QTanD intrinsic:                       QTanD Intrinsic.
- * QTanH intrinsic:                       QTanH Intrinsic.
- * question mark:                         Character Set.
- * questionable instructions:             What is GNU Fortran?.
- * Radix intrinsic:                       Radix Intrinsic.
- * Rand intrinsic:                        Rand Intrinsic.
- * Random_Number intrinsic:               Random_Number Intrinsic.
- * Random_Seed intrinsic:                 Random_Seed Intrinsic.
- * range checking:                        Code Gen Options.
- * Range intrinsic:                       Range Intrinsic.
- * range, increasing:                     Increasing Precision/Range.
- * rank, maximum:                         Compiler Limits.
- * ratfor:                                Overall Options.
- * Ratfor preprocessor:                   Overall Options.
- * READONLY:                              READONLY Keyword.
- * reads and writes, scheduling:          Aliasing Assumed To Work.
- * Real intrinsic <1>:                    Real Intrinsic.
- * Real intrinsic:                        REAL() and AIMAG() of Complex.
- * real part:                             Ugly Complex Part Extraction.
- * REAL(KIND=1) type:                     Compiler Types.
- * REAL(KIND=2) type:                     Compiler Types.
- * REAL*16 support:                       Full Support for Compiler Types.
- * RealPart intrinsic:                    RealPart Intrinsic.
- * recent versions <1>:                   Changes.
- * recent versions:                       News.
- * RECORD statement:                      STRUCTURE UNION RECORD MAP.
- * recursion, lack of:                    RECURSIVE Keyword.
- * RECURSIVE keyword:                     RECURSIVE Keyword.
- * reference works:                       Language.
- * Rename intrinsic <1>:                  Rename Intrinsic (function).
- * Rename intrinsic:                      Rename Intrinsic (subroutine).
- * Repeat intrinsic:                      Repeat Intrinsic.
- * reporting bugs:                        Bugs.
- * reporting compilation status:          Overall Options.
- * Reshape intrinsic:                     Reshape Intrinsic.
- * results, inconsistent:                 Floating-point Errors.
- * RETURN statement <1>:                  Alternate Returns.
- * RETURN statement:                      Functions.
- * return type of functions:              Functions.
- * right angle:                           Character Set.
- * right bracket:                         Character Set.
- * rounding errors:                       Floating-point Errors.
- * row-major ordering:                    Arrays.
- * RRSpacing intrinsic:                   RRSpacing Intrinsic.
- * RShift intrinsic:                      RShift Intrinsic.
- * run-time, dynamic allocation:          Arbitrary Concatenation.
- * run-time, initialization:              Startup Code.
- * run-time, library:                     What is GNU Fortran?.
- * run-time, options:                     Code Gen Options.
- * SAVE statement:                        Code Gen Options.
- * saved variables:                       Variables Assumed To Be Saved.
- * Scale intrinsic:                       Scale Intrinsic.
- * Scan intrinsic:                        Scan Intrinsic.
- * scheduling of reads and writes:        Aliasing Assumed To Work.
- * scope <1>:                             Scope and Classes of Names.
- * scope:                                 Scope of Names and Labels.
- * search path:                           Directory Options.
- * search paths, for included files:      Directory Options.
- * Secnds intrinsic:                      Secnds Intrinsic.
- * Second intrinsic <1>:                  Second Intrinsic (subroutine).
- * Second intrinsic:                      Second Intrinsic (function).
- * segmentation violation <1>:            Strange Behavior at Run Time.
- * segmentation violation <2>:            Stack Overflow.
- * segmentation violation:                NeXTStep Problems.
- * Selected_Int_Kind intrinsic:           Selected_Int_Kind Intrinsic.
- * Selected_Real_Kind intrinsic:          Selected_Real_Kind Intrinsic.
- * semicolon <1>:                         Character Set.
- * semicolon:                             Statements Comments Lines.
- * sequence numbers:                      Better Source Model.
- * Set_Exponent intrinsic:                Set_Exponent Intrinsic.
- * Shape intrinsic:                       Shape Intrinsic.
- * SHARED:                                READONLY Keyword.
- * Shift intrinsic:                       Bit Operations on Floating-point Data.
- * Short intrinsic:                       Short Intrinsic.
- * short source lines:                    Short Lines.
- * short time:                            Timer Wraparounds.
- * shorthand options:                     Shorthand Options.
- * side effects, order of evaluation:     Order of Side Effects.
- * Sign intrinsic:                        Sign Intrinsic.
- * signal 11:                             Signal 11 and Friends.
- * Signal intrinsic <1>:                  Signal Intrinsic (function).
- * Signal intrinsic:                      Signal Intrinsic (subroutine).
- * signature of procedures:               Procedures.
- * simplify porting:                      Simplify Porting.
- * Sin intrinsic:                         Sin Intrinsic.
- * SinD intrinsic:                        SinD Intrinsic.
- * SinH intrinsic:                        SinH Intrinsic.
- * Sleep intrinsic:                       Sleep Intrinsic.
- * Sngl intrinsic:                        Sngl Intrinsic.
- * SnglQ intrinsic:                       SnglQ Intrinsic.
- * Solaris:                               Strange Behavior at Run Time.
- * source code <1>:                       Case Sensitivity.
- * source code <2>:                       Source Form.
- * source code <3>:                       Lines.
- * source code:                           What is GNU Fortran?.
- * source file:                           What is GNU Fortran?.
- * source file format <1>:                Case Sensitivity.
- * source file format <2>:                Source Form.
- * source file format <3>:                Lines.
- * source file format:                    Fortran Dialect Options.
- * source format <1>:                     Source Form.
- * source format:                         Lines.
- * source lines, long:                    Long Lines.
- * source lines, short:                   Short Lines.
- * space <1>:                             Lines.
- * space:                                 Character Set.
- * space, endless printing of:            Strange Behavior at Run Time.
- * space, padding with:                   Short Lines.
- * Spacing intrinsic:                     Spacing Intrinsic.
- * SPC <1>:                               Lines.
- * SPC:                                   Character Set.
- * speed, of compiler:                    Known Bugs.
- * speed, of loops:                       Optimize Options.
- * speed, of programs:                    Faster Programs.
- * spills of floating-point results:      Floating-point Errors.
- * Spread intrinsic:                      Spread Intrinsic.
- * SqRt intrinsic:                        SqRt Intrinsic.
- * SRand intrinsic:                       SRand Intrinsic.
- * stack, 387 coprocessor:                News.
- * stack, aligned:                        Aligned Data.
- * stack, overflow:                       Stack Overflow.
- * standard, ANSI FORTRAN 77:             Language.
- * standard, support for:                 Standard Support.
- * startup code:                          Startup Code.
- * Stat intrinsic <1>:                    Stat Intrinsic (function).
- * Stat intrinsic:                        Stat Intrinsic (subroutine).
- * statement labels, assigned:            Assigned Statement Labels.
- * statements, ACCEPT:                    TYPE and ACCEPT I/O Statements.
- * statements, ASSIGN <1>:                Assigned Statement Labels.
- * statements, ASSIGN:                    Ugly Assigned Labels.
- * statements, AUTOMATIC:                 AUTOMATIC Statement.
- * statements, BLOCK DATA <1>:            Multiple Definitions of External Names.
- * statements, BLOCK DATA:                Block Data and Libraries.
- * statements, CLOSE:                     OPEN CLOSE and INQUIRE Keywords.
- * statements, COMMON <1>:                Multiple Definitions of External Names.
- * statements, COMMON:                    Common Blocks.
- * statements, COMPLEX:                   Complex Variables.
- * statements, CYCLE:                     CYCLE and EXIT.
- * statements, DATA <1>:                  Known Bugs.
- * statements, DATA:                      Code Gen Options.
- * statements, DECODE:                    ENCODE and DECODE.
- * statements, DIMENSION <1>:             Array Bounds Expressions.
- * statements, DIMENSION <2>:             Adjustable Arrays.
- * statements, DIMENSION:                 Arrays.
- * statements, DO <1>:                    Loops.
- * statements, DO:                        Warning Options.
- * statements, ENCODE:                    ENCODE and DECODE.
- * statements, ENTRY:                     Alternate Entry Points.
- * statements, EQUIVALENCE:               Local Equivalence Areas.
- * statements, EXIT:                      CYCLE and EXIT.
- * statements, FORMAT:                    Expressions in FORMAT Statements.
- * statements, FUNCTION <1>:              Functions.
- * statements, FUNCTION:                  Procedures.
- * statements, GOTO:                      Assigned Statement Labels.
- * statements, IMPLICIT CHARACTER*(*):    Limitation on Implicit Declarations.
- * statements, INQUIRE:                   OPEN CLOSE and INQUIRE Keywords.
- * statements, MAP:                       STRUCTURE UNION RECORD MAP.
- * statements, NAMELIST:                  NAMELIST.
- * statements, OPEN:                      OPEN CLOSE and INQUIRE Keywords.
- * statements, PARAMETER <1>:             Old-style PARAMETER Statements.
- * statements, PARAMETER:                 Intrinsics in PARAMETER Statements.
- * statements, POINTER:                   POINTER Statements.
- * statements, PROGRAM:                   Main Program Unit.
- * statements, RECORD:                    STRUCTURE UNION RECORD MAP.
- * statements, RETURN <1>:                Alternate Returns.
- * statements, RETURN:                    Functions.
- * statements, SAVE:                      Code Gen Options.
- * statements, separated by semicolon:    Statements Comments Lines.
- * statements, STRUCTURE:                 STRUCTURE UNION RECORD MAP.
- * statements, SUBROUTINE <1>:            Alternate Returns.
- * statements, SUBROUTINE:                Procedures.
- * statements, TYPE:                      TYPE and ACCEPT I/O Statements.
- * statements, UNION:                     STRUCTURE UNION RECORD MAP.
- * STATIC:                                AUTOMATIC Statement.
- * static variables:                      Variables Assumed To Be Saved.
- * status, compilation:                   Overall Options.
- * storage association:                   Aliasing Assumed To Work.
- * strings, empty:                        Character Type.
- * STRUCTURE statement:                   STRUCTURE UNION RECORD MAP.
- * structures:                            Known Bugs.
- * submodels:                             Use Submodel Options.
- * SUBROUTINE statement <1>:              Alternate Returns.
- * SUBROUTINE statement:                  Procedures.
- * subroutines:                           Alternate Returns.
- * subscript checking:                    Code Gen Options.
- * substring checking:                    Code Gen Options.
- * suffixes, file name:                   Overall Options.
- * Sum intrinsic:                         Sum Intrinsic.
- * support, Alpha:                        Known Bugs.
- * support, ELF:                          News.
- * support, f77:                          Backslash in Constants.
- * support, FORTRAN 77:                   Standard Support.
- * support, Fortran 90:                   Fortran 90 Support.
- * support, gdb:                          Debugger Problems.
- * suppressing warnings:                  Warning Options.
- * symbol names <1>:                      Names.
- * symbol names:                          Fortran Dialect Options.
- * symbol names, scope and classes:       Scope and Classes of Names.
- * symbol names, transforming:            Code Gen Options.
- * symbol names, underscores:             Code Gen Options.
- * SymLnk intrinsic <1>:                  SymLnk Intrinsic (function).
- * SymLnk intrinsic:                      SymLnk Intrinsic (subroutine).
- * synchronous write errors:              Output Assumed To Flush.
- * syntax checking:                       Warning Options.
- * System intrinsic <1>:                  System Intrinsic (function).
- * System intrinsic:                      System Intrinsic (subroutine).
- * System_Clock intrinsic:                System_Clock Intrinsic.
- * tab character:                         Tabs.
- * table of intrinsics:                   Table of Intrinsic Functions.
- * Tan intrinsic:                         Tan Intrinsic.
- * TanD intrinsic:                        TanD Intrinsic.
- * TanH intrinsic:                        TanH Intrinsic.
- * test programs:                         Nothing Happens.
- * testing alignment:                     Aligned Data.
- * textbooks:                             Language.
- * threads:                               Support for Threads.
- * Time intrinsic <1>:                    Time Intrinsic (VXT).
- * Time intrinsic:                        Time Intrinsic (UNIX).
- * Time8 intrinsic:                       Time8 Intrinsic.
- * Tiny intrinsic:                        Tiny Intrinsic.
- * Toolpack:                              Increasing Precision/Range.
- * trailing comma:                        Ugly Null Arguments.
- * trailing comment <1>:                  LEX.
- * trailing comment <2>:                  Trailing Comment.
- * trailing comment:                      Statements Comments Lines.
- * trailing null byte:                    Character and Hollerith Constants.
- * Transfer intrinsic:                    Transfer Intrinsic.
- * transforming symbol names <1>:         Names.
- * transforming symbol names:             Code Gen Options.
- * translation of user programs:          What is GNU Fortran?.
- * Transpose intrinsic:                   Transpose Intrinsic.
- * Trim intrinsic:                        Trim Intrinsic.
- * trips, number of:                      Loops.
- * truncation, of floating-point values:  Floating-point Errors.
- * truncation, of long lines:             Long Lines.
- * TtyNam intrinsic <1>:                  TtyNam Intrinsic (function).
- * TtyNam intrinsic:                      TtyNam Intrinsic (subroutine).
- * TYPE statement:                        TYPE and ACCEPT I/O Statements.
- * types, COMPLEX(KIND=1):                Compiler Types.
- * types, COMPLEX(KIND=2):                Compiler Types.
- * types, constants <1>:                  Compiler Constants.
- * types, constants <2>:                  Constants.
- * types, constants:                      Fortran Dialect Options.
- * types, DOUBLE COMPLEX:                 Compiler Types.
- * types, DOUBLE PRECISION:               Compiler Types.
- * types, file:                           Overall Options.
- * types, Fortran/C:                      C Access to Type Information.
- * types, INTEGER(KIND=1):                Compiler Types.
- * types, INTEGER(KIND=2):                Compiler Types.
- * types, INTEGER(KIND=3):                Compiler Types.
- * types, INTEGER(KIND=6):                Compiler Types.
- * types, INTEGER*2:                      Popular Non-standard Types.
- * types, INTEGER*8:                      Full Support for Compiler Types.
- * types, LOGICAL(KIND=1):                Compiler Types.
- * types, LOGICAL(KIND=2):                Compiler Types.
- * types, LOGICAL(KIND=3):                Compiler Types.
- * types, LOGICAL(KIND=6):                Compiler Types.
- * types, LOGICAL*1:                      Popular Non-standard Types.
- * types, of data:                        Compiler Types.
- * types, REAL(KIND=1):                   Compiler Types.
- * types, REAL(KIND=2):                   Compiler Types.
- * types, REAL*16:                        Full Support for Compiler Types.
- * UBound intrinsic:                      UBound Intrinsic.
- * ugly features <1>:                     Distensions.
- * ugly features:                         Shorthand Options.
- * UMask intrinsic <1>:                   UMask Intrinsic (function).
- * UMask intrinsic:                       UMask Intrinsic (subroutine).
- * undefined behavior:                    Bug Criteria.
- * undefined function value:              Bug Criteria.
- * undefined reference (_main):           Cannot Link Fortran Programs.
- * underscore <1>:                        Mangling of Names.
- * underscore <2>:                        Underscores in Symbol Names.
- * underscore <3>:                        Character Set.
- * underscore:                            Code Gen Options.
- * unformatted files:                     Portable Unformatted Files.
- * uninitialized variables <1>:           Variables Assumed To Be Zero.
- * uninitialized variables <2>:           Code Gen Options.
- * uninitialized variables:               Warning Options.
- * UNION statement:                       STRUCTURE UNION RECORD MAP.
- * unit numbers:                          Large File Unit Numbers.
- * UNIX f77:                              Shorthand Options.
- * UNIX intrinsics:                       Fortran Dialect Options.
- * Unlink intrinsic <1>:                  Unlink Intrinsic (function).
- * Unlink intrinsic:                      Unlink Intrinsic (subroutine).
- * Unpack intrinsic:                      Unpack Intrinsic.
- * unrecognized file format:              What is GNU Fortran?.
- * unresolved reference (various):        Cannot Link Fortran Programs.
- * unrolling loops:                       Optimize Options.
- * UNSAVE:                                AUTOMATIC Statement.
- * unsupported warnings:                  Warning Options.
- * unused arguments <1>:                  Unused Arguments.
- * unused arguments:                      Warning Options.
- * unused dummies:                        Warning Options.
- * unused parameters:                     Warning Options.
- * unused variables:                      Warning Options.
- * uppercase letters:                     Case Sensitivity.
- * user-visible changes:                  Changes.
- * variables, assumed to be zero:         Variables Assumed To Be Zero.
- * variables, automatic:                  AUTOMATIC Statement.
- * variables, initialization of:          Code Gen Options.
- * variables, mistyped:                   Not My Type.
- * variables, retaining values across calls: Variables Assumed To Be Saved.
- * variables, uninitialized <1>:          Code Gen Options.
- * variables, uninitialized:              Warning Options.
- * variables, unused:                     Warning Options.
- * Verify intrinsic:                      Verify Intrinsic.
- * version information, printing <1>:     Overall Options.
- * version information, printing:         What is GNU Fortran?.
- * versions, recent <1>:                  Changes.
- * versions, recent:                      News.
- * VXT extensions <1>:                    VXT Fortran.
- * VXT extensions:                        Fortran Dialect Options.
- * VXT intrinsics:                        Fortran Dialect Options.
- * vxtidate_y2kbuggy_0:                   Year 2000 (Y2K) Problems.
- * warnings:                              What is GNU Fortran?.
- * warnings vs errors:                    Warnings and Errors.
- * warnings, all:                         Warning Options.
- * warnings, extra:                       Warning Options.
- * warnings, global names <1>:            Code Gen Options.
- * warnings, global names:                Warning Options.
- * warnings, implicit declaration:        Warning Options.
- * warnings, suppressing:                 Warning Options.
- * warnings, unsupported:                 Warning Options.
- * wisdom:                                Collected Fortran Wisdom.
- * wraparound:                            Run-time Environment Limits.
- * wraparound, timings <1>:               Secnds Intrinsic.
- * wraparound, timings <2>:               DTime Intrinsic (function).
- * wraparound, timings <3>:               Time8 Intrinsic.
- * wraparound, timings <4>:               Time Intrinsic (UNIX).
- * wraparound, timings <5>:               System_Clock Intrinsic.
- * wraparound, timings <6>:               Second Intrinsic (subroutine).
- * wraparound, timings <7>:               Second Intrinsic (function).
- * wraparound, timings <8>:               MClock8 Intrinsic.
- * wraparound, timings <9>:               MClock Intrinsic.
- * wraparound, timings <10>:              ETime Intrinsic (function).
- * wraparound, timings <11>:              ETime Intrinsic (subroutine).
- * wraparound, timings <12>:              DTime Intrinsic (subroutine).
- * wraparound, timings:                   CPU_Time Intrinsic.
- * wraparound, Y10K <1>:                  Time Intrinsic (VXT).
- * wraparound, Y10K <2>:                  IDate Intrinsic (UNIX).
- * wraparound, Y10K <3>:                  FDate Intrinsic (function).
- * wraparound, Y10K <4>:                  FDate Intrinsic (subroutine).
- * wraparound, Y10K:                      Date_and_Time Intrinsic.
- * wraparound, Y2K:                       IDate Intrinsic (VXT).
- * writes, flushing:                      Output Assumed To Flush.
- * writing code:                          Collected Fortran Wisdom.
- * x86 floating-point:                    Floating-point precision.
- * x86 FPU stack:                         Inconsistent Calling Sequences.
- * XOr intrinsic:                         XOr Intrinsic.
- * Y10K compliance <1>:                   Time Intrinsic (VXT).
- * Y10K compliance <2>:                   Year 10000 (Y10K) Problems.
- * Y10K compliance <3>:                   IDate Intrinsic (UNIX).
- * Y10K compliance <4>:                   FDate Intrinsic (function).
- * Y10K compliance <5>:                   FDate Intrinsic (subroutine).
- * Y10K compliance:                       Date_and_Time Intrinsic.
- * Y2K compliance <1>:                    Y2KBAD.
- * Y2K compliance <2>:                    IDate Intrinsic (VXT).
- * Y2K compliance <3>:                    Date Intrinsic.
- * Y2K compliance:                        Year 2000 (Y2K) Problems.
- * y2kbuggy:                              Year 2000 (Y2K) Problems.
- * Year 10000 compliance <1>:             Time Intrinsic (VXT).
- * Year 10000 compliance <2>:             Year 10000 (Y10K) Problems.
- * Year 10000 compliance <3>:             IDate Intrinsic (UNIX).
- * Year 10000 compliance <4>:             FDate Intrinsic (function).
- * Year 10000 compliance <5>:             FDate Intrinsic (subroutine).
- * Year 10000 compliance:                 Date_and_Time Intrinsic.
- * Year 2000 compliance <1>:              Y2KBAD.
- * Year 2000 compliance <2>:              IDate Intrinsic (VXT).
- * Year 2000 compliance <3>:              Date Intrinsic.
- * Year 2000 compliance:                  Year 2000 (Y2K) Problems.
- * Z edit descriptor <1>:                 Fortran 90 Features.
- * Z edit descriptor:                     I/O.
- * ZAbs intrinsic:                        ZAbs Intrinsic.
- * ZCos intrinsic:                        ZCos Intrinsic.
- * zero byte, trailing:                   Character and Hollerith Constants.
- * zero-initialized variables:            Variables Assumed To Be Zero.
- * zero-length CHARACTER:                 Character Type.
- * zero-trip DO loops:                    Fortran Dialect Options.
- * ZExp intrinsic:                        ZExp Intrinsic.
- * ZExt intrinsic:                        ZExt Intrinsic.
- * ZLog intrinsic:                        ZLog Intrinsic.
- * ZSin intrinsic:                        ZSin Intrinsic.
- * ZSqRt intrinsic:                       ZSqRt Intrinsic.
- 
- 
--- 0 ----
diff -Nrc3pad gcc-3.2.3/gcc/f/g77.info-3 gcc-3.3/gcc/f/g77.info-3
*** gcc-3.2.3/gcc/f/g77.info-3	2003-04-22 07:07:23.000000000 +0000
--- gcc-3.3/gcc/f/g77.info-3	1970-01-01 00:00:00.000000000 +0000
***************
*** 1,656 ****
- This is g77.info, produced by makeinfo version 4.5 from g77.texi.
- 
- INFO-DIR-SECTION Programming
- START-INFO-DIR-ENTRY
- * g77: (g77).                  The GNU Fortran compiler.
- END-INFO-DIR-ENTRY
-    This file documents the use and the internals of the GNU Fortran
- (`g77') compiler.  It corresponds to the GCC-3.2.3 version of `g77'.
- 
-    Published by the Free Software Foundation 59 Temple Place - Suite 330
- Boston, MA 02111-1307 USA
- 
-    Copyright (C) 1995,1996,1997,1998,1999,2000,2001,2002 Free Software
- Foundation, Inc.
- 
-    Permission is granted to copy, distribute and/or modify this document
- under the terms of the GNU Free Documentation License, Version 1.1 or
- any later version published by the Free Software Foundation; with the
- Invariant Sections being "GNU General Public License" and "Funding Free
- Software", the Front-Cover texts being (a) (see below), and with the
- Back-Cover Texts being (b) (see below).  A copy of the license is
- included in the section entitled "GNU Free Documentation License".
- 
-    (a) The FSF's Front-Cover Text is:
- 
-    A GNU Manual
- 
-    (b) The FSF's Back-Cover Text is:
- 
-    You have freedom to copy and modify this GNU Manual, like GNU
- software.  Copies published by the Free Software Foundation raise
- funds for GNU development.
- 
-    Contributed by James Craig Burley (<craig@jcb-sc.com>).  Inspired by
- a first pass at translating `g77-0.5.16/f/DOC' that was contributed to
- Craig by David Ronis (<ronis@onsager.chem.mcgill.ca>).
- 
- 
- File: g77.info,  Node: Debugging Options,  Next: Optimize Options,  Prev: Warning Options,  Up: Invoking G77
- 
- Options for Debugging Your Program or GNU Fortran
- =================================================
- 
-    GNU Fortran has various special options that are used for debugging
- either your program or `g77'
- 
- `-g'
-      Produce debugging information in the operating system's native
-      format (stabs, COFF, XCOFF, or DWARF).  GDB can work with this
-      debugging information.
- 
-      A sample debugging session looks like this (note the use of the
-      breakpoint):
-           $ cat gdb.f
-                 PROGRAM PROG
-                 DIMENSION A(10)
-                 DATA A /1.,2.,3.,4.,5.,6.,7.,8.,9.,10./
-                 A(5) = 4.
-                 PRINT*,A
-                 END
-           $ g77 -g -O gdb.f
-           $ gdb a.out
-           ...
-           (gdb) break MAIN__
-           Breakpoint 1 at 0x8048e96: file gdb.f, line 4.
-           (gdb) run
-           Starting program: /home/toon/g77-bugs/./a.out
-           Breakpoint 1, MAIN__ () at gdb.f:4
-           4             A(5) = 4.
-           Current language:  auto; currently fortran
-           (gdb) print a(5)
-           $1 = 5
-           (gdb) step
-           5             PRINT*,A
-           (gdb) print a(5)
-           $2 = 4
-           ...
-      One could also add the setting of the breakpoint and the first run
-      command to the file `.gdbinit' in the current directory, to
-      simplify the debugging session.
- 
-    *Note Options for Debugging Your Program or GCC: (gcc)Debugging
- Options, for more information on debugging options.
- 
- 
- File: g77.info,  Node: Optimize Options,  Next: Preprocessor Options,  Prev: Debugging Options,  Up: Invoking G77
- 
- Options That Control Optimization
- =================================
- 
-    Most Fortran users will want to use no optimization when developing
- and testing programs, and use `-O' or `-O2' when compiling programs for
- late-cycle testing and for production use.  However, note that certain
- diagnostics--such as for uninitialized variables--depend on the flow
- analysis done by `-O', i.e. you must use `-O' or `-O2' to get such
- diagnostics.
- 
-    The following flags have particular applicability when compiling
- Fortran programs:
- 
- `-malign-double'
-      (Intel x86 architecture only.)
- 
-      Noticeably improves performance of `g77' programs making heavy use
-      of `REAL(KIND=2)' (`DOUBLE PRECISION') data on some systems.  In
-      particular, systems using Pentium, Pentium Pro, 586, and 686
-      implementations of the i386 architecture execute programs faster
-      when `REAL(KIND=2)' (`DOUBLE PRECISION') data are aligned on
-      64-bit boundaries in memory.
- 
-      This option can, at least, make benchmark results more consistent
-      across various system configurations, versions of the program, and
-      data sets.
- 
-      _Note:_ The warning in the `gcc' documentation about this option
-      does not apply, generally speaking, to Fortran code compiled by
-      `g77'
- 
-      *Note Aligned Data::, for more information on alignment issues.
- 
-      _Also also note:_ The negative form of `-malign-double' is
-      `-mno-align-double', not `-benign-double'.
- 
- `-ffloat-store'
-      Might help a Fortran program that depends on exact IEEE
-      conformance on some machines, but might slow down a program that
-      doesn't.
- 
-      This option is effective when the floating-point unit is set to
-      work in IEEE 854 `extended precision'--as it typically is on x86
-      and m68k GNU systems--rather than IEEE 754 double precision.
-      `-ffloat-store' tries to remove the extra precision by spilling
-      data from floating-point registers into memory and this typically
-      involves a big performance hit.  However, it doesn't affect
-      intermediate results, so that it is only partially effective.
-      `Excess precision' is avoided in code like:
-           a = b + c
-           d = a * e
-      but not in code like:
-                 d = (b + c) * e
- 
-      For another, potentially better, way of controlling the precision,
-      see *Note Floating-point precision::.
- 
- `-fforce-mem'
- 
- `-fforce-addr'
-      Might improve optimization of loops.
- 
- `-fno-inline'
-      Don't compile statement functions inline.  Might reduce the size
-      of a program unit--which might be at expense of some speed (though
-      it should compile faster).  Note that if you are not optimizing,
-      no functions can be expanded inline.
- 
- `-ffast-math'
-      Might allow some programs designed to not be too dependent on IEEE
-      behavior for floating-point to run faster, or die trying.  Sets
-      `-funsafe-math-optimizations', and `-fno-trapping-math'.
- 
- `-funsafe-math-optimizations'
-      Allow optimizations that may be give incorrect results for certain
-      IEEE inputs.
- 
- `-fno-trapping-math'
-      Allow the compiler to assume that floating-point arithmetic will
-      not generate traps on any inputs.  This is useful, for example,
-      when running a program using IEEE "non-stop" floating-point
-      arithmetic.
- 
- `-fstrength-reduce'
-      Might make some loops run faster.
- 
- `-frerun-cse-after-loop'
- 
- `-fexpensive-optimizations'
- 
- `-fdelayed-branch'
- 
- `-fschedule-insns'
- 
- `-fschedule-insns2'
- 
- `-fcaller-saves'
-      Might improve performance on some code.
- 
- `-funroll-loops'
-      Typically improves performance on code using iterative `DO' loops
-      by unrolling them and is probably generally appropriate for
-      Fortran, though it is not turned on at any optimization level.
-      Note that outer loop unrolling isn't done specifically; decisions
-      about whether to unroll a loop are made on the basis of its
-      instruction count.
- 
-      Also, no `loop discovery'(1) is done, so only loops written with
-      `DO' benefit from loop optimizations, including--but not limited
-      to--unrolling.  Loops written with `IF' and `GOTO' are not
-      currently recognized as such.  This option unrolls only iterative
-      `DO' loops, not `DO WHILE' loops.
- 
- `-funroll-all-loops'
-      Probably improves performance on code using `DO WHILE' loops by
-      unrolling them in addition to iterative `DO' loops.  In the absence
-      of `DO WHILE', this option is equivalent to `-funroll-loops' but
-      possibly slower.
- 
- `-fno-move-all-movables'
- 
- `-fno-reduce-all-givs'
- 
- `-fno-rerun-loop-opt'
-      In general, the optimizations enabled with these options will lead
-      to faster code being generated by GNU Fortran; hence they are
-      enabled by default when issuing the `g77' command.
- 
-      `-fmove-all-movables' and `-freduce-all-givs' will enable loop
-      optimization to move all loop-invariant index computations in
-      nested loops over multi-rank array dummy arguments out of these
-      loops.
- 
-      `-frerun-loop-opt' will move offset calculations resulting from
-      the fact that Fortran arrays by default have a lower bound of 1
-      out of the loops.
- 
-      These three options are intended to be removed someday, once loop
-      optimization is sufficiently advanced to perform all those
-      transformations without help from these options.
- 
-    *Note Options That Control Optimization: (gcc)Optimize Options, for
- more information on options to optimize the generated machine code.
- 
-    ---------- Footnotes ----------
- 
-    (1) "loop discovery" refers to the process by which a compiler, or
- indeed any reader of a program, determines which portions of the
- program are more likely to be executed repeatedly as it is being run.
- Such discovery typically is done early when compiling using
- optimization techniques, so the "discovered" loops get more
- attention--and more run-time resources, such as registers--from the
- compiler.  It is easy to "discover" loops that are constructed out of
- looping constructs in the language (such as Fortran's `DO').  For some
- programs, "discovering" loops constructed out of lower-level constructs
- (such as `IF' and `GOTO') can lead to generation of more optimal code
- than otherwise.
- 
- 
- File: g77.info,  Node: Preprocessor Options,  Next: Directory Options,  Prev: Optimize Options,  Up: Invoking G77
- 
- Options Controlling the Preprocessor
- ====================================
- 
-    These options control the C preprocessor, which is run on each C
- source file before actual compilation.
- 
-    *Note Options Controlling the Preprocessor: (gcc)Preprocessor
- Options, for information on C preprocessor options.
- 
-    Some of these options also affect how `g77' processes the `INCLUDE'
- directive.  Since this directive is processed even when preprocessing
- is not requested, it is not described in this section.  *Note Options
- for Directory Search: Directory Options, for information on how `g77'
- processes the `INCLUDE' directive.
- 
-    However, the `INCLUDE' directive does not apply preprocessing to the
- contents of the included file itself.
- 
-    Therefore, any file that contains preprocessor directives (such as
- `#include', `#define', and `#if') must be included via the `#include'
- directive, not via the `INCLUDE' directive.  Therefore, any file
- containing preprocessor directives, if included, is necessarily
- included by a file that itself contains preprocessor directives.
- 
- 
- File: g77.info,  Node: Directory Options,  Next: Code Gen Options,  Prev: Preprocessor Options,  Up: Invoking G77
- 
- Options for Directory Search
- ============================
- 
-    These options affect how the `cpp' preprocessor searches for files
- specified via the `#include' directive.  Therefore, when compiling
- Fortran programs, they are meaningful when the preprocessor is used.
- 
-    Some of these options also affect how `g77' searches for files
- specified via the `INCLUDE' directive, although files included by that
- directive are not, themselves, preprocessed.  These options are:
- 
- `-I-'
- 
- `-IDIR'
-      These affect interpretation of the `INCLUDE' directive (as well as
-      of the `#include' directive of the `cpp' preprocessor).
- 
-      Note that `-IDIR' must be specified _without_ any spaces between
-      `-I' and the directory name--that is, `-Ifoo/bar' is valid, but
-      `-I foo/bar' is rejected by the `g77' compiler (though the
-      preprocessor supports the latter form).  Also note that the
-      general behavior of `-I' and `INCLUDE' is pretty much the same as
-      of `-I' with `#include' in the `cpp' preprocessor, with regard to
-      looking for `header.gcc' files and other such things.
- 
-      *Note Options for Directory Search: (gcc)Directory Options, for
-      information on the `-I' option.
- 
- 
- File: g77.info,  Node: Code Gen Options,  Next: Environment Variables,  Prev: Directory Options,  Up: Invoking G77
- 
- Options for Code Generation Conventions
- =======================================
- 
-    These machine-independent options control the interface conventions
- used in code generation.
- 
-    Most of them have both positive and negative forms; the negative form
- of `-ffoo' would be `-fno-foo'.  In the table below, only one of the
- forms is listed--the one which is not the default.  You can figure out
- the other form by either removing `no-' or adding it.
- 
- `-fno-automatic'
-      Treat each program unit as if the `SAVE' statement was specified
-      for every local variable and array referenced in it.  Does not
-      affect common blocks.  (Some Fortran compilers provide this option
-      under the name `-static'.)
- 
- `-finit-local-zero'
-      Specify that variables and arrays that are local to a program unit
-      (not in a common block and not passed as an argument) are to be
-      initialized to binary zeros.
- 
-      Since there is a run-time penalty for initialization of variables
-      that are not given the `SAVE' attribute, it might be a good idea
-      to also use `-fno-automatic' with `-finit-local-zero'.
- 
- `-fno-f2c'
-      Do not generate code designed to be compatible with code generated
-      by `f2c' use the GNU calling conventions instead.
- 
-      The `f2c' calling conventions require functions that return type
-      `REAL(KIND=1)' to actually return the C type `double', and
-      functions that return type `COMPLEX' to return the values via an
-      extra argument in the calling sequence that points to where to
-      store the return value.  Under the GNU calling conventions, such
-      functions simply return their results as they would in GNU
-      C--`REAL(KIND=1)' functions return the C type `float', and
-      `COMPLEX' functions return the GNU C type `complex' (or its
-      `struct' equivalent).
- 
-      This does not affect the generation of code that interfaces with
-      the `libg2c' library.
- 
-      However, because the `libg2c' library uses `f2c' calling
-      conventions, `g77' rejects attempts to pass intrinsics implemented
-      by routines in this library as actual arguments when `-fno-f2c' is
-      used, to avoid bugs when they are actually called by code
-      expecting the GNU calling conventions to work.
- 
-      For example, `INTRINSIC ABS;CALL FOO(ABS)' is rejected when
-      `-fno-f2c' is in force.  (Future versions of the `g77' run-time
-      library might offer routines that provide GNU-callable versions of
-      the routines that implement the `f2c' intrinsics that may be
-      passed as actual arguments, so that valid programs need not be
-      rejected when `-fno-f2c' is used.)
- 
-      *Caution:* If `-fno-f2c' is used when compiling any source file
-      used in a program, it must be used when compiling _all_ Fortran
-      source files used in that program.
- 
- `-ff2c-library'
-      Specify that use of `libg2c' (or the original `libf2c') is
-      required.  This is the default for the current version of `g77'
- 
-      Currently it is not valid to specify `-fno-f2c-library'.  This
-      option is provided so users can specify it in shell scripts that
-      build programs and libraries that require the `libf2c' library,
-      even when being compiled by future versions of `g77' that might
-      otherwise default to generating code for an incompatible library.
- 
- `-fno-underscoring'
-      Do not transform names of entities specified in the Fortran source
-      file by appending underscores to them.
- 
-      With `-funderscoring' in effect, `g77' appends two underscores to
-      names with underscores and one underscore to external names with
-      no underscores.  (`g77' also appends two underscores to internal
-      names with underscores to avoid naming collisions with external
-      names.  The `-fno-second-underscore' option disables appending of
-      the second underscore in all cases.)
- 
-      This is done to ensure compatibility with code produced by many
-      UNIX Fortran compilers, including `f2c' which perform the same
-      transformations.
- 
-      Use of `-fno-underscoring' is not recommended unless you are
-      experimenting with issues such as integration of (GNU) Fortran into
-      existing system environments (vis-a-vis existing libraries, tools,
-      and so on).
- 
-      For example, with `-funderscoring', and assuming other defaults
-      like `-fcase-lower' and that `j()' and `max_count()' are external
-      functions while `my_var' and `lvar' are local variables, a
-      statement like
- 
-           I = J() + MAX_COUNT (MY_VAR, LVAR)
- 
-      is implemented as something akin to:
- 
-           i = j_() + max_count__(&my_var__, &lvar);
- 
-      With `-fno-underscoring', the same statement is implemented as:
- 
-           i = j() + max_count(&my_var, &lvar);
- 
-      Use of `-fno-underscoring' allows direct specification of
-      user-defined names while debugging and when interfacing `g77' code
-      with other languages.
- 
-      Note that just because the names match does _not_ mean that the
-      interface implemented by `g77' for an external name matches the
-      interface implemented by some other language for that same name.
-      That is, getting code produced by `g77' to link to code produced
-      by some other compiler using this or any other method can be only a
-      small part of the overall solution--getting the code generated by
-      both compilers to agree on issues other than naming can require
-      significant effort, and, unlike naming disagreements, linkers
-      normally cannot detect disagreements in these other areas.
- 
-      Also, note that with `-fno-underscoring', the lack of appended
-      underscores introduces the very real possibility that a
-      user-defined external name will conflict with a name in a system
-      library, which could make finding unresolved-reference bugs quite
-      difficult in some cases--they might occur at program run time, and
-      show up only as buggy behavior at run time.
- 
-      In future versions of `g77' we hope to improve naming and linking
-      issues so that debugging always involves using the names as they
-      appear in the source, even if the names as seen by the linker are
-      mangled to prevent accidental linking between procedures with
-      incompatible interfaces.
- 
- `-fno-second-underscore'
-      Do not append a second underscore to names of entities specified
-      in the Fortran source file.
- 
-      This option has no effect if `-fno-underscoring' is in effect.
- 
-      Otherwise, with this option, an external name such as `MAX_COUNT'
-      is implemented as a reference to the link-time external symbol
-      `max_count_', instead of `max_count__'.
- 
- `-fno-ident'
-      Ignore the `#ident' directive.
- 
- `-fzeros'
-      Treat initial values of zero as if they were any other value.
- 
-      As of version 0.5.18, `g77' normally treats `DATA' and other
-      statements that are used to specify initial values of zero for
-      variables and arrays as if no values were actually specified, in
-      the sense that no diagnostics regarding multiple initializations
-      are produced.
- 
-      This is done to speed up compiling of programs that initialize
-      large arrays to zeros.
- 
-      Use `-fzeros' to revert to the simpler, slower behavior that can
-      catch multiple initializations by keeping track of all
-      initializations, zero or otherwise.
- 
-      _Caution:_ Future versions of `g77' might disregard this option
-      (and its negative form, the default) or interpret it somewhat
-      differently.  The interpretation changes will affect only
-      non-standard programs; standard-conforming programs should not be
-      affected.
- 
- `-femulate-complex'
-      Implement `COMPLEX' arithmetic via emulation, instead of using the
-      facilities of the `gcc' back end that provide direct support of
-      `complex' arithmetic.
- 
-      (`gcc' had some bugs in its back-end support for `complex'
-      arithmetic, due primarily to the support not being completed as of
-      version 2.8.1 and `egcs' 1.1.2.)
- 
-      Use `-femulate-complex' if you suspect code-generation bugs, or
-      experience compiler crashes, that might result from `g77' using
-      the `COMPLEX' support in the `gcc' back end.  If using that option
-      fixes the bugs or crashes you are seeing, that indicates a likely
-      `g77' bugs (though, all compiler crashes are considered bugs), so,
-      please report it.  (Note that the known bugs, now believed fixed,
-      produced compiler crashes rather than causing the generation of
-      incorrect code.)
- 
-      Use of this option should not affect how Fortran code compiled by
-      `g77' works in terms of its interfaces to other code, e.g. that
-      compiled by `f2c'
- 
-      As of GCC version 3.0, this option is not necessary anymore.
- 
-      _Caution:_ Future versions of `g77' might ignore both forms of
-      this option.
- 
- `-falias-check'
- 
- `-fargument-alias'
- 
- `-fargument-noalias'
- 
- `-fno-argument-noalias-global'
-      _Version info:_ These options are not supported by versions of
-      `g77' based on `gcc' version 2.8.
- 
-      These options specify to what degree aliasing (overlap) is
-      permitted between arguments (passed as pointers) and `COMMON'
-      (external, or public) storage.
- 
-      The default for Fortran code, as mandated by the FORTRAN 77 and
-      Fortran 90 standards, is `-fargument-noalias-global'.  The default
-      for code written in the C language family is `-fargument-alias'.
- 
-      Note that, on some systems, compiling with `-fforce-addr' in
-      effect can produce more optimal code when the default aliasing
-      options are in effect (and when optimization is enabled).
- 
-      *Note Aliasing Assumed To Work::, for detailed information on the
-      implications of compiling Fortran code that depends on the ability
-      to alias dummy arguments.
- 
- `-fno-globals'
-      Disable diagnostics about inter-procedural analysis problems, such
-      as disagreements about the type of a function or a procedure's
-      argument, that might cause a compiler crash when attempting to
-      inline a reference to a procedure within a program unit.  (The
-      diagnostics themselves are still produced, but as warnings, unless
-      `-Wno-globals' is specified, in which case no relevant diagnostics
-      are produced.)
- 
-      Further, this option disables such inlining, to avoid compiler
-      crashes resulting from incorrect code that would otherwise be
-      diagnosed.
- 
-      As such, this option might be quite useful when compiling
-      existing, "working" code that happens to have a few bugs that do
-      not generally show themselves, but which `g77' diagnoses.
- 
-      Use of this option therefore has the effect of instructing `g77'
-      to behave more like it did up through version 0.5.19.1, when it
-      paid little or no attention to disagreements between program units
-      about a procedure's type and argument information, and when it
-      performed no inlining of procedures (except statement functions).
- 
-      Without this option, `g77' defaults to performing the potentially
-      inlining procedures as it started doing in version 0.5.20, but as
-      of version 0.5.21, it also diagnoses disagreements that might
-      cause such inlining to crash the compiler as (fatal) errors, and
-      warns about similar disagreements that are currently believed to
-      not likely to result in the compiler later crashing or producing
-      incorrect code.
- 
- `-fflatten-arrays'
-      Use back end's C-like constructs (pointer plus offset) instead of
-      its `ARRAY_REF' construct to handle all array references.
- 
-      _Note:_ This option is not supported.  It is intended for use only
-      by `g77' developers, to evaluate code-generation issues.  It might
-      be removed at any time.
- 
- `-fbounds-check'
- `-ffortran-bounds-check'
-      Enable generation of run-time checks for array subscripts and
-      substring start and end points against the (locally) declared
-      minimum and maximum values.
- 
-      The current implementation uses the `libf2c' library routine
-      `s_rnge' to print the diagnostic.
- 
-      However, whereas `f2c' generates a single check per reference for
-      a multi-dimensional array, of the computed offset against the
-      valid offset range (0 through the size of the array), `g77'
-      generates a single check per _subscript_ expression.  This catches
-      some cases of potential bugs that `f2c' does not, such as
-      references to below the beginning of an assumed-size array.
- 
-      `g77' also generates checks for `CHARACTER' substring references,
-      something `f2c' currently does not do.
- 
-      Use the new `-ffortran-bounds-check' option to specify
-      bounds-checking for only the Fortran code you are compiling, not
-      necessarily for code written in other languages.
- 
-      _Note:_ To provide more detailed information on the offending
-      subscript, `g77' provides the `libg2c' run-time library routine
-      `s_rnge' with somewhat differently-formatted information.  Here's
-      a sample diagnostic:
- 
-           Subscript out of range on file line 4, procedure rnge.f/bf.
-           Attempt to access the -6-th element of variable b[subscript-2-of-2].
-           Aborted
- 
-      The above message indicates that the offending source line is line
-      4 of the file `rnge.f', within the program unit (or statement
-      function) named `bf'.  The offended array is named `b'.  The
-      offended array dimension is the second for a two-dimensional array,
-      and the offending, computed subscript expression was `-6'.
- 
-      For a `CHARACTER' substring reference, the second line has this
-      appearance:
- 
-           Attempt to access the 11-th element of variable a[start-substring].
- 
-      This indicates that the offended `CHARACTER' variable or array is
-      named `a', the offended substring position is the starting
-      (leftmost) position, and the offending substring expression is
-      `11'.
- 
-      (Though the verbage of `s_rnge' is not ideal for the purpose of
-      the `g77' compiler, the above information should provide adequate
-      diagnostic abilities to it users.)
- 
-    *Note Options for Code Generation Conventions: (gcc)Code Gen
- Options, for information on more options offered by the GBE shared by
- `g77' `gcc' and other GNU compilers.
- 
-    Some of these do _not_ work when compiling programs written in
- Fortran:
- 
- `-fpcc-struct-return'
- 
- `-freg-struct-return'
-      You should not use these except strictly the same way as you used
-      them to build the version of `libg2c' with which you will be
-      linking all code compiled by `g77' with the same option.
- 
- `-fshort-double'
-      This probably either has no effect on Fortran programs, or makes
-      them act loopy.
- 
- `-fno-common'
-      Do not use this when compiling Fortran programs, or there will be
-      Trouble.
- 
- `-fpack-struct'
-      This probably will break any calls to the `libg2c' library, at the
-      very least, even if it is built with the same option.
- 
- 
- File: g77.info,  Node: Environment Variables,  Prev: Code Gen Options,  Up: Invoking G77
- 
- Environment Variables Affecting GNU Fortran
- ===========================================
- 
-    GNU Fortran currently does not make use of any environment variables
- to control its operation above and beyond those that affect the
- operation of `gcc'.
- 
-    *Note Environment Variables Affecting GCC: (gcc)Environment
- Variables, for information on environment variables.
- 
--- 0 ----
diff -Nrc3pad gcc-3.2.3/gcc/f/g77.info-4 gcc-3.3/gcc/f/g77.info-4
*** gcc-3.2.3/gcc/f/g77.info-4	2003-04-22 07:07:23.000000000 +0000
--- gcc-3.3/gcc/f/g77.info-4	1970-01-01 00:00:00.000000000 +0000
***************
*** 1,1288 ****
- This is g77.info, produced by makeinfo version 4.5 from g77.texi.
- 
- INFO-DIR-SECTION Programming
- START-INFO-DIR-ENTRY
- * g77: (g77).                  The GNU Fortran compiler.
- END-INFO-DIR-ENTRY
-    This file documents the use and the internals of the GNU Fortran
- (`g77') compiler.  It corresponds to the GCC-3.2.3 version of `g77'.
- 
-    Published by the Free Software Foundation 59 Temple Place - Suite 330
- Boston, MA 02111-1307 USA
- 
-    Copyright (C) 1995,1996,1997,1998,1999,2000,2001,2002 Free Software
- Foundation, Inc.
- 
-    Permission is granted to copy, distribute and/or modify this document
- under the terms of the GNU Free Documentation License, Version 1.1 or
- any later version published by the Free Software Foundation; with the
- Invariant Sections being "GNU General Public License" and "Funding Free
- Software", the Front-Cover texts being (a) (see below), and with the
- Back-Cover Texts being (b) (see below).  A copy of the license is
- included in the section entitled "GNU Free Documentation License".
- 
-    (a) The FSF's Front-Cover Text is:
- 
-    A GNU Manual
- 
-    (b) The FSF's Back-Cover Text is:
- 
-    You have freedom to copy and modify this GNU Manual, like GNU
- software.  Copies published by the Free Software Foundation raise
- funds for GNU development.
- 
-    Contributed by James Craig Burley (<craig@jcb-sc.com>).  Inspired by
- a first pass at translating `g77-0.5.16/f/DOC' that was contributed to
- Craig by David Ronis (<ronis@onsager.chem.mcgill.ca>).
- 
- 
- File: g77.info,  Node: News,  Next: Changes,  Prev: Invoking G77,  Up: Top
- 
- News About GNU Fortran
- **********************
- 
-    Changes made to recent versions of GNU Fortran are listed below,
- with the most recent version first.
- 
-    The changes are generally listed in order:
- 
-   1. Code-generation and run-time-library bug-fixes
- 
-   2. Compiler and run-time-library crashes involving valid code that
-      have been fixed
- 
-   3. New features
- 
-   4. Fixes and enhancements to existing features
- 
-   5. New diagnostics
- 
-   6. Internal improvements
- 
-   7. Miscellany
- 
-    This order is not strict--for example, some items involve a
- combination of these elements.
- 
-    Note that two variants of `g77' are tracked below.  The `egcs'
- variant is described vis-a-vis previous versions of `egcs' and/or an
- official FSF version, as appropriate.  Note that all such variants are
- obsolete _as of July 1999_ - the information is retained here only for
- its historical value.
- 
-    Therefore, `egcs' versions sometimes have multiple listings to help
- clarify how they differ from other versions, though this can make
- getting a complete picture of what a particular `egcs' version contains
- somewhat more difficult.
- 
-    For information on bugs in the GCC-3.2.3 version of `g77', see *Note
- Known Bugs In GNU Fortran: Known Bugs.
- 
-    An online, "live" version of this document (derived directly from
- the mainline, development version of `g77' within `gcc') is available at
- `http://www.gnu.org/software/gcc/onlinedocs/g77/News.html'.
- 
-    The following information was last updated on 2002-10-28:
- 
- In `GCC' 3.2 versus `GCC' 3.1:
- ==============================
- 
-    * Problem Reports fixed (in chronological order of submission):
-     `8308'
-           gcc-3.x does not compile files with suffix .r (RATFOR) [Fixed
-           in 3.2.1]
- 
- In `GCC' 3.1 (formerly known as g77-0.5.27) versus `GCC' 3.0:
- =============================================================
- 
-    * Problem Reports fixed (in chronological order of submission):
-     `947'
-           Data statement initialization with subscript of kind INTEGER*2
- 
-     `3743'
-           Reference to intrinsic `ISHFT' invalid
- 
-     `3807'
-           Function BESJN(integer,double) problems
- 
-     `3957'
-           g77 -pipe -xf77-cpp-input sends output to stdout
- 
-     `4279'
-           g77 -h" gives bogus output
- 
-     `4730'
-           ICE on valid input using CALL EXIT(%VAL(...))
- 
-     `4752'
-           g77 -v -c -xf77-version /dev/null -xnone causes ice
- 
-     `4885'
-           BACKSPACE example that doesn't work as of gcc/g77-3.0.x
- 
-     `5122'
-           g77 rejects accepted use of INTEGER*2 as type of DATA
-           statement loop index
- 
-     `5397'
-           ICE on compiling source with 540 000 000 REAL array
- 
-     `5473'
-           ICE on BESJN(integer*8,real)
- 
-     `5837'
-           bug in loop unrolling
- 
-    * `g77' now has its man page generated from the texinfo
-      documentation, to guarantee that it remains up to date.
- 
-    * `g77' used to reject the following program on 32-bit targets:
-           PROGRAM PROG
-           DIMENSION A(140 000 000)
-           END
-      with the message:
-           prog.f: In program `prog':
-           prog.f:2:
-                    DIMENSION A(140 000 000)
-                              ^
-           Array `a' at (^) is too large to handle
-      because 140 000 000 REALs is larger than the largest bit-extent
-      that can be expressed in 32 bits.  However, bit-sizes never play a
-      role after offsets have been converted to byte addresses.
-      Therefore this check has been removed, and the limit is now 2
-      Gbyte of memory (around 530 000 000 REALs).  Note: On GNU/Linux
-      systems one has to compile programs that occupy more than 1 Gbyte
-      statically, i.e. `g77 -static ...'.
- 
-    * Based on work done by Juergen Pfeifer (<juergen.pfeifer@gmx.net>)
-      libf2c is now a shared library.  One can still link in all objects
-      with the program by specifying the `-static' option.
- 
-    * Robert Anderson (<rwa@alumni.princeton.edu>) thought up a two line
-      change that enables g77 to compile such code as:
-           SUBROUTINE SUB(A, N)
-           DIMENSION N(2)
-           DIMENSION A(N(1),N(2))
-           A(1,1) = 1.
-           END
-      Note the use of array elements in the bounds of the adjustable
-      array A.
- 
-    * George Helffrich (<george@geo.titech.ac.jp>) implemented a change
-      in substring index checking (when specifying `-fbounds-check')
-      that permits the use of zero length substrings of the form
-      `string(1:0)'.
- 
-    * Based on code developed by Pedro Vazquez
-      (<vazquez@penelope.iqm.unicamp.br>), the `libf2c' library is now
-      able to read and write files larger than 2 Gbyte on 32-bit target
-      machines, if the operating system supports this.
- 
- In 0.5.26, `GCC' 3.0 versus `GCC' 2.95:
- =======================================
- 
-    * When a REWIND was issued after a WRITE statement on an unformatted
-      file, the implicit truncation was performed by copying the
-      truncated file to /tmp and copying the result back.  This has been
-      fixed by using the `ftruncate' OS function.  Thanks go to the
-      GAMESS developers for bringing this to our attention.
- 
-    * Using options `-g', `-ggdb' or `-gdwarf[-2]' (where appropriate
-      for your target) now also enables debugging information for COMMON
-      BLOCK and EQUIVALENCE items to be emitted.  Thanks go to Andrew
-      Vaught (<andy@xena.eas.asu.edu>) and George Helffrich
-      (<george@geology.bristol.ac.uk>) for fixing this longstanding
-      problem.
- 
-    * It is not necessary anymore to use the option `-femulate-complex'
-      to compile Fortran code using COMPLEX arithmetic, even on 64-bit
-      machines (like the Alpha).  This will improve code generation.
- 
-    * INTRINSIC arithmetic functions are now treated as routines that do
-      not depend on anything but their argument(s).  This enables
-      further instruction scheduling, because it is known that they
-      cannot read or modify arbitrary locations.
- 
-    * Upgrade to `libf2c' as of 2000-12-05.
- 
-      This fixes a bug where a namelist containing initialization of
-      LOGICAL items and a variable starting with T or F would be read
-      incorrectly.
- 
-    * The `TtyNam' intrinsics now set NAME to all spaces (at run time)
-      if the system has no `ttyname' implementation available.
- 
-    * Upgrade to `libf2c' as of 1999-06-28.
- 
-      This fixes a bug whereby input to a `NAMELIST' read involving a
-      repeat count, such as `K(5)=10*3', was not properly handled by
-      `libf2c'.  The first item was written to `K(5)', but the remaining
-      nine were written elsewhere (still within the array), not
-      necessarily starting at `K(6)'.
- 
- In 0.5.25, `GCC' 2.95 (`EGCS' 1.2) versus `EGCS' 1.1.2:
- =======================================================
- 
-    * `g77' no longer generates bad code for assignments, or other
-      conversions, of `REAL' or `COMPLEX' constant expressions to type
-      `INTEGER(KIND=2)' (often referred to as `INTEGER*8').
- 
-      For example, `INTEGER*8 J; J = 4E10' now works as documented.
- 
-    * `g77' no longer truncates `INTEGER(KIND=2)' (usually `INTEGER*8')
-      subscript expressions when evaluating array references on systems
-      with pointers widers than `INTEGER(KIND=1)' (such as Alphas).
- 
-    * `g77' no longer generates bad code for an assignment to a
-      `COMPLEX' variable or array that partially overlaps one or more of
-      the sources of the same assignment (a very rare construction).  It
-      now assigns through a temporary, in cases where such partial
-      overlap is deemed possible.
- 
-    * `libg2c' (`libf2c') no longer loses track of the file being worked
-      on during a `BACKSPACE' operation.
- 
-    * `libg2c' (`libf2c') fixes a bug whereby input to a `NAMELIST' read
-      involving a repeat count, such as `K(5)=10*3', was not properly
-      handled by `libf2c'.  The first item was written to `K(5)', but
-      the remaining nine were written elsewhere (still within the array),
-      not necessarily starting at `K(6)'.
- 
-    * Automatic arrays now seem to be working on HP-UX systems.
- 
-    * The `Date' intrinsic now returns the correct result on big-endian
-      systems.
- 
-    * Fix `g77' so it no longer crashes when compiling I/O statements
-      using keywords that define `INTEGER' values, such as `IOSTAT=J',
-      where J is other than default `INTEGER' (such as `INTEGER*2').
-      Instead, it issues a diagnostic.
- 
-    * Fix `g77' so it properly handles `DATA A/RPT*VAL/', where RPT is
-      not default `INTEGER', such as `INTEGER*2', instead of producing a
-      spurious diagnostic.  Also fix `DATA (A(I),I=1,N)', where `N' is
-      not default `INTEGER' to work instead of crashing `g77'.
- 
-    * The `-ax' option is now obeyed when compiling Fortran programs.
-      (It is passed to the `f771' driver.)
- 
-    * The new `-fbounds-check' option causes `g77' to compile run-time
-      bounds checks of array subscripts, as well as of substring start
-      and end points.
- 
-    * `libg2c' now supports building as multilibbed library, which
-      provides better support for systems that require options such as
-      `-mieee' to work properly.
- 
-    * Source file names with the suffixes `.FOR' and `.FPP' now are
-      recognized by `g77' as if they ended in `.for' and `.fpp',
-      respectively.
- 
-    * The order of arguments to the _subroutine_ forms of the `CTime',
-      `DTime', `ETime', and `TtyNam' intrinsics has been swapped.  The
-      argument serving as the returned value for the corresponding
-      function forms now is the _second_ argument, making these
-      consistent with the other subroutine forms of `libU77' intrinsics.
- 
-    * `g77' now warns about a reference to an intrinsic that has an
-      interface that is not Year 2000 (Y2K) compliant.  Also, `libg2c'
-      has been changed to increase the likelihood of catching references
-      to the implementations of these intrinsics using the `EXTERNAL'
-      mechanism (which would avoid the new warnings).
- 
-      *Note Year 2000 (Y2K) Problems::, for more information.
- 
-    * `g77' now warns about a reference to a function when the
-      corresponding _subsequent_ function program unit disagrees with
-      the reference concerning the type of the function.
- 
-    * `-fno-emulate-complex' is now the default option.  This should
-      result in improved performance of code that uses the `COMPLEX'
-      data type.
- 
-    * The `-malign-double' option now reliably aligns _all_
-      double-precision variables and arrays on Intel x86 targets.
- 
-    * Even without the `-malign-double' option, `g77' reliably aligns
-      local double-precision variables that are not in `EQUIVALENCE'
-      areas and not `SAVE''d.
- 
-    * `g77' now open-codes ("inlines") division of `COMPLEX' operands
-      instead of generating a run-time call to the `libf2c' routines
-      `c_div' or `z_div', unless the `-Os' option is specified.
- 
-    * `g77' no longer generates code to maintain `errno', a C-language
-      concept, when performing operations such as the `SqRt' intrinsic.
- 
-    * `g77' developers can temporarily use the `-fflatten-arrays' option
-      to compare how the compiler handles code generation using C-like
-      constructs as compared to the Fortran-like method constructs
-      normally used.
- 
-    * A substantial portion of the `g77' front end's code-generation
-      component was rewritten.  It now generates code using facilities
-      more robustly supported by the `gcc' back end.  One effect of this
-      rewrite is that some codes no longer produce a spurious "label LAB
-      used before containing binding contour" message.
- 
-    * Support for the `-fugly' option has been removed.
- 
-    * Improve documentation and indexing, including information on Year
-      2000 (Y2K) compliance, and providing more information on internals
-      of the front end.
- 
-    * Upgrade to `libf2c' as of 1999-05-10.
- 
- In 0.5.24 versus 0.5.23:
- ========================
- 
-    There is no `g77' version 0.5.24 at this time, or planned.  0.5.24
- is the version number designated for bug fixes and, perhaps, some new
- features added, to 0.5.23.  Version 0.5.23 requires `gcc' 2.8.1, as
- 0.5.24 was planned to require.
- 
-    Due to `EGCS' becoming `GCC' (which is now an acronym for "GNU
- Compiler Collection"), and `EGCS' 1.2 becoming officially designated
- `GCC' 2.95, there seems to be no need for an actual 0.5.24 release.
- 
-    To reduce the confusion already resulting from use of 0.5.24 to
- designate `g77' versions within `EGCS' versions 1.0 and 1.1, as well as
- in versions of `g77' documentation and notices during that period,
- "mainline" `g77' version numbering resumes at 0.5.25 with `GCC' 2.95
- (`EGCS' 1.2), skipping over 0.5.24 as a placeholder version number.
- 
-    To repeat, there is no `g77' 0.5.24, but there is now a 0.5.25.
- Please remain calm and return to your keypunch units.
- 
- In `EGCS' 1.1.2 versus `EGCS' 1.1.1:
- ====================================
- 
-    * Fix the `IDate' intrinsic (VXT) (in `libg2c') so the returned year
-      is in the documented, non-Y2K-compliant range of 0-99, instead of
-      being returned as 100 in the year 2000.
- 
-      *Note IDate Intrinsic (VXT)::, for more information.
- 
-    * Fix the `Date_and_Time' intrinsic (in `libg2c') to return the
-      milliseconds value properly in VALUES(8).
- 
-    * Fix the `LStat' intrinsic (in `libg2c') to return device-ID
-      information properly in SARRAY(7).
- 
-    * Improve documentation.
- 
- In `EGCS' 1.1.1 versus `EGCS' 1.1:
- ==================================
- 
-    * Fix `libg2c' so it performs an implicit `ENDFILE' operation (as
-      appropriate) whenever a `REWIND' is done.
- 
-      (This bug was introduced in 0.5.23 and `egcs' 1.1 in `g77''s
-      version of `libf2c'.)
- 
-    * Fix `libg2c' so it no longer crashes with a spurious diagnostic
-      upon doing any I/O following a direct formatted write.
- 
-      (This bug was introduced in 0.5.23 and `egcs' 1.1 in `g77''s
-      version of `libf2c'.)
- 
-    * Fix `g77' so it no longer crashes compiling references to the
-      `Rand' intrinsic on some systems.
- 
-    * Fix `g77' portion of installation process so it works better on
-      some systems (those with shells requiring `else true' clauses on
-      `if' constructs for the completion code to be set properly).
- 
- In `EGCS' 1.1 versus `EGCS' 1.0.3:
- ==================================
- 
-    * Fix bugs in the `libU77' intrinsic `HostNm' that wrote one byte
-      beyond the end of its `CHARACTER' argument, and in the `libU77'
-      intrinsics `GMTime' and `LTime' that overwrote their arguments.
- 
-    * Assumed arrays with negative bounds (such as `REAL A(-1:*)') no
-      longer elicit spurious diagnostics from `g77', even on systems
-      with pointers having different sizes than integers.
- 
-      This bug is not known to have existed in any recent version of
-      `gcc'.  It was introduced in an early release of `egcs'.
- 
-    * Valid combinations of `EXTERNAL', passing that external as a dummy
-      argument without explicitly giving it a type, and, in a subsequent
-      program unit, referencing that external as an external function
-      with a different type no longer crash `g77'.
- 
-    * `CASE DEFAULT' no longer crashes `g77'.
- 
-    * The `-Wunused' option no longer issues a spurious warning about
-      the "master" procedure generated by `g77' for procedures
-      containing `ENTRY' statements.
- 
-    * Support `FORMAT(I<EXPR>)' when EXPR is a compile-time constant
-      `INTEGER' expression.
- 
-    * Fix `g77' `-g' option so procedures that use `ENTRY' can be
-      stepped through, line by line, in `gdb'.
- 
-    * Allow any `REAL' argument to intrinsics `Second' and `CPU_Time'.
- 
-    * Use `tempnam', if available, to open scratch files (as in
-      `OPEN(STATUS='SCRATCH')') so that the `TMPDIR' environment
-      variable, if present, is used.
- 
-    * `g77''s version of `libf2c' separates out the setting of global
-      state (such as command-line arguments and signal handling) from
-      `main.o' into distinct, new library archive members.
- 
-      This should make it easier to write portable applications that
-      have their own (non-Fortran) `main()' routine properly set up the
-      `libf2c' environment, even when `libf2c' (now `libg2c') is a
-      shared library.
- 
-    * `g77' no longer installs the `f77' command and `f77.1' man page in
-      the `/usr' or `/usr/local' hierarchy, even if the `f77-install-ok'
-      file exists in the source or build directory.  See the
-      installation documentation for more information.
- 
-    * `g77' no longer installs the `libf2c.a' library and `f2c.h'
-      include file in the `/usr' or `/usr/local' hierarchy, even if the
-      `f2c-install-ok' or `f2c-exists-ok' files exist in the source or
-      build directory.  See the installation documentation for more
-      information.
- 
-    * The `libf2c.a' library produced by `g77' has been renamed to
-      `libg2c.a'.  It is installed only in the `gcc' "private" directory
-      hierarchy, `gcc-lib'.  This allows system administrators and users
-      to choose which version of the `libf2c' library from `netlib' they
-      wish to use on a case-by-case basis.  See the installation
-      documentation for more information.
- 
-    * The `f2c.h' include (header) file produced by `g77' has been
-      renamed to `g2c.h'.  It is installed only in the `gcc' "private"
-      directory hierarchy, `gcc-lib'.  This allows system administrators
-      and users to choose which version of the include file from
-      `netlib' they wish to use on a case-by-case basis.  See the
-      installation documentation for more information.
- 
-    * The `g77' command now expects the run-time library to be named
-      `libg2c.a' instead of `libf2c.a', to ensure that a version other
-      than the one built and installed as part of the same `g77' version
-      is picked up.
- 
-    * During the configuration and build process, `g77' creates
-      subdirectories it needs only as it needs them.  Other cleaning up
-      of the configuration and build process has been performed as well.
- 
-    * `install-info' now used to update the directory of Info
-      documentation to contain an entry for `g77' (during installation).
- 
-    * Some diagnostics have been changed from warnings to errors, to
-      prevent inadvertent use of the resulting, probably buggy, programs.
-      These mostly include diagnostics about use of unsupported features
-      in the `OPEN', `INQUIRE', `READ', and `WRITE' statements, and
-      about truncations of various sorts of constants.
- 
-    * Improve compilation of `FORMAT' expressions so that a null byte is
-      appended to the last operand if it is a constant.  This provides a
-      cleaner run-time diagnostic as provided by `libf2c' for statements
-      like `PRINT '(I1', 42'.
- 
-    * Improve documentation and indexing.
- 
-    * The upgrade to `libf2c' as of 1998-06-18 should fix a variety of
-      problems, including those involving some uses of the `T' format
-      specifier, and perhaps some build (porting) problems as well.
- 
- In `EGCS' 1.1 versus `g77' 0.5.23:
- ==================================
- 
-    * Fix a code-generation bug that afflicted Intel x86 targets when
-      `-O2' was specified compiling, for example, an old version of the
-      `DNRM2' routine.
- 
-      The x87 coprocessor stack was being mismanaged in cases involving
-      assigned `GOTO' and `ASSIGN'.
- 
-    * `g77' no longer produces incorrect code and initial values for
-      `EQUIVALENCE' and `COMMON' aggregates that, due to "unnatural"
-      ordering of members vis-a-vis their types, require initial padding.
- 
-    * Fix `g77' crash compiling code containing the construct
-      `CMPLX(0.)' or similar.
- 
-    * `g77' no longer crashes when compiling code containing
-      specification statements such as `INTEGER(KIND=7) PTR'.
- 
-    * `g77' no longer crashes when compiling code such as `J = SIGNAL(1,
-      2)'.
- 
-    * `g77' now treats `%LOC(EXPR)' and `LOC(EXPR)' as "ordinary"
-      expressions when they are used as arguments in procedure calls.
-      This change applies only to global (filewide) analysis, making it
-      consistent with how `g77' actually generates code for these cases.
- 
-      Previously, `g77' treated these expressions as denoting special
-      "pointer" arguments for the purposes of filewide analysis.
- 
-    * Fix `g77' crash (or apparently infinite run-time) when compiling
-      certain complicated expressions involving `COMPLEX' arithmetic
-      (especially multiplication).
- 
-    * Align static double-precision variables and arrays on Intel x86
-      targets regardless of whether `-malign-double' is specified.
- 
-      Generally, this affects only local variables and arrays having the
-      `SAVE' attribute or given initial values via `DATA'.
- 
-    * The `g77' driver now ensures that `-lg2c' is specified in the link
-      phase prior to any occurrence of `-lm'.  This prevents
-      accidentally linking to a routine in the SunOS4 `-lm' library when
-      the generated code wants to link to the one in `libf2c' (`libg2c').
- 
-    * `g77' emits more debugging information when `-g' is used.
- 
-      This new information allows, for example, `which __g77_length_a'
-      to be used in `gdb' to determine the type of the phantom length
-      argument supplied with `CHARACTER' variables.
- 
-      This information pertains to internally-generated type, variable,
-      and other information, not to the longstanding deficiencies
-      vis-a-vis `COMMON' and `EQUIVALENCE'.
- 
-    * The F90 `Date_and_Time' intrinsic now is supported.
- 
-    * The F90 `System_Clock' intrinsic allows the optional arguments
-      (except for the `Count' argument) to be omitted.
- 
-    * Upgrade to `libf2c' as of 1998-06-18.
- 
-    * Improve documentation and indexing.
- 
- In 0.5.23 versus 0.5.22:
- ========================
- 
-    * This release contains several regressions against version 0.5.22
-      of `g77', due to using the "vanilla" `gcc' back end instead of
-      patching it to fix a few bugs and improve performance in a few
-      cases.
- 
-      Features that have been dropped from this version of `g77' due to
-      their being implemented via `g77'-specific patches to the `gcc'
-      back end in previous releases include:
- 
-         - Support for `__restrict__' keyword, the options
-           `-fargument-alias', `-fargument-noalias', and
-           `-fargument-noalias-global', and the corresponding
-           alias-analysis code.
- 
-           (`egcs' has the alias-analysis code, but not the
-           `__restrict__' keyword.  `egcs' `g77' users benefit from the
-           alias-analysis code despite the lack of the `__restrict__'
-           keyword, which is a C-language construct.)
- 
-         - Support for the GNU compiler options `-fmove-all-movables',
-           `-freduce-all-givs', and `-frerun-loop-opt'.
- 
-           (`egcs' supports these options.  `g77' users of `egcs'
-           benefit from them even if they are not explicitly specified,
-           because the defaults are optimized for `g77' users.)
- 
-         - Support for the `-W' option warning about integer division by
-           zero.
- 
-         - The Intel x86-specific option `-malign-double' applying to
-           stack-allocated data as well as statically-allocate data.
- 
-      Note that the `gcc/f/gbe/' subdirectory has been removed from this
-      distribution as a result of `g77' no longer including patches for
-      the `gcc' back end.
- 
-    * Fix bugs in the `libU77' intrinsic `HostNm' that wrote one byte
-      beyond the end of its `CHARACTER' argument, and in the `libU77'
-      intrinsics `GMTime' and `LTime' that overwrote their arguments.
- 
-    * Support `gcc' version 2.8, and remove support for prior versions
-      of `gcc'.
- 
-    * Remove support for the `--driver' option, as `g77' now does all
-      the driving, just like `gcc'.
- 
-    * `CASE DEFAULT' no longer crashes `g77'.
- 
-    * Valid combinations of `EXTERNAL', passing that external as a dummy
-      argument without explicitly giving it a type, and, in a subsequent
-      program unit, referencing that external as an external function
-      with a different type no longer crash `g77'.
- 
-    * `g77' no longer installs the `f77' command and `f77.1' man page in
-      the `/usr' or `/usr/local' hierarchy, even if the `f77-install-ok'
-      file exists in the source or build directory.  See the
-      installation documentation for more information.
- 
-    * `g77' no longer installs the `libf2c.a' library and `f2c.h'
-      include file in the `/usr' or `/usr/local' hierarchy, even if the
-      `f2c-install-ok' or `f2c-exists-ok' files exist in the source or
-      build directory.  See the installation documentation for more
-      information.
- 
-    * The `libf2c.a' library produced by `g77' has been renamed to
-      `libg2c.a'.  It is installed only in the `gcc' "private" directory
-      hierarchy, `gcc-lib'.  This allows system administrators and users
-      to choose which version of the `libf2c' library from `netlib' they
-      wish to use on a case-by-case basis.  See the installation
-      documentation for more information.
- 
-    * The `f2c.h' include (header) file produced by `g77' has been
-      renamed to `g2c.h'.  It is installed only in the `gcc' "private"
-      directory hierarchy, `gcc-lib'.  This allows system administrators
-      and users to choose which version of the include file from
-      `netlib' they wish to use on a case-by-case basis.  See the
-      installation documentation for more information.
- 
-    * The `g77' command now expects the run-time library to be named
-      `libg2c.a' instead of `libf2c.a', to ensure that a version other
-      than the one built and installed as part of the same `g77' version
-      is picked up.
- 
-    * The `-Wunused' option no longer issues a spurious warning about
-      the "master" procedure generated by `g77' for procedures
-      containing `ENTRY' statements.
- 
-    * `g77''s version of `libf2c' separates out the setting of global
-      state (such as command-line arguments and signal handling) from
-      `main.o' into distinct, new library archive members.
- 
-      This should make it easier to write portable applications that
-      have their own (non-Fortran) `main()' routine properly set up the
-      `libf2c' environment, even when `libf2c' (now `libg2c') is a
-      shared library.
- 
-    * During the configuration and build process, `g77' creates
-      subdirectories it needs only as it needs them, thus avoiding
-      unnecessary creation of, for example, `stage1/f/runtime' when
-      doing a non-bootstrap build.  Other cleaning up of the
-      configuration and build process has been performed as well.
- 
-    * `install-info' now used to update the directory of Info
-      documentation to contain an entry for `g77' (during installation).
- 
-    * Some diagnostics have been changed from warnings to errors, to
-      prevent inadvertent use of the resulting, probably buggy, programs.
-      These mostly include diagnostics about use of unsupported features
-      in the `OPEN', `INQUIRE', `READ', and `WRITE' statements, and
-      about truncations of various sorts of constants.
- 
-    * Improve documentation and indexing.
- 
-    * Upgrade to `libf2c' as of 1998-04-20.
- 
-      This should fix a variety of problems, including those involving
-      some uses of the `T' format specifier, and perhaps some build
-      (porting) problems as well.
- 
- In 0.5.22 versus 0.5.21:
- ========================
- 
-    * Fix code generation for iterative `DO' loops that have one or more
-      references to the iteration variable, or to aliases of it, in
-      their control expressions.  For example, `DO 10 J=2,J' now is
-      compiled correctly.
- 
-    * Fix a code-generation bug that afflicted Intel x86 targets when
-      `-O2' was specified compiling, for example, an old version of the
-      `DNRM2' routine.
- 
-      The x87 coprocessor stack was being mismanaged in cases involving
-      assigned `GOTO' and `ASSIGN'.
- 
-    * Fix `DTime' intrinsic so as not to truncate results to integer
-      values (on some systems).
- 
-    * Fix `Signal' intrinsic so it offers portable support for 64-bit
-      systems (such as Digital Alphas running GNU/Linux).
- 
-    * Fix run-time crash involving `NAMELIST' on 64-bit machines such as
-      Alphas.
- 
-    * Fix `g77' version of `libf2c' so it no longer produces a spurious
-      `I/O recursion' diagnostic at run time when an I/O operation (such
-      as `READ *,I') is interrupted in a manner that causes the program
-      to be terminated via the `f_exit' routine (such as via `C-c').
- 
-    * Fix `g77' crash triggered by `CASE' statement with an omitted
-      lower or upper bound.
- 
-    * Fix `g77' crash compiling references to `CPU_Time' intrinsic.
- 
-    * Fix `g77' crash (or apparently infinite run-time) when compiling
-      certain complicated expressions involving `COMPLEX' arithmetic
-      (especially multiplication).
- 
-    * Fix `g77' crash on statements such as `PRINT *,
-      (REAL(Z(I)),I=1,2)', where `Z' is `DOUBLE COMPLEX'.
- 
-    * Fix a `g++' crash.
- 
-    * Support `FORMAT(I<EXPR>)' when EXPR is a compile-time constant
-      `INTEGER' expression.
- 
-    * Fix `g77' `-g' option so procedures that use `ENTRY' can be
-      stepped through, line by line, in `gdb'.
- 
-    * Fix a profiling-related bug in `gcc' back end for Intel x86
-      architecture.
- 
-    * Allow any `REAL' argument to intrinsics `Second' and `CPU_Time'.
- 
-    * Allow any numeric argument to intrinsics `Int2' and `Int8'.
- 
-    * Use `tempnam', if available, to open scratch files (as in
-      `OPEN(STATUS='SCRATCH')') so that the `TMPDIR' environment
-      variable, if present, is used.
- 
-    * Rename the `gcc' keyword `restrict' to `__restrict__', to avoid
-      rejecting valid, existing, C programs.  Support for `restrict' is
-      now more like support for `complex'.
- 
-    * Fix `-fpedantic' to not reject procedure invocations such as
-      `I=J()' and `CALL FOO()'.
- 
-    * Fix `-fugly-comma' to affect invocations of only external
-      procedures.  Restore rejection of gratuitous trailing omitted
-      arguments to intrinsics, as in `I=MAX(3,4,,)'.
- 
-    * Fix compiler so it accepts `-fgnu-intrinsics-*' and
-      `-fbadu77-intrinsics-*' options.
- 
-    * Improve diagnostic messages from `libf2c' so it is more likely
-      that the printing of the active format string is limited to the
-      string, with no trailing garbage being printed.
- 
-      (Unlike `f2c', `g77' did not append a null byte to its compiled
-      form of every format string specified via a `FORMAT' statement.
-      However, `f2c' would exhibit the problem anyway for a statement
-      like `PRINT '(I)garbage', 1' by printing `(I)garbage' as the
-      format string.)
- 
-    * Improve compilation of `FORMAT' expressions so that a null byte is
-      appended to the last operand if it is a constant.  This provides a
-      cleaner run-time diagnostic as provided by `libf2c' for statements
-      like `PRINT '(I1', 42'.
- 
-    * Fix various crashes involving code with diagnosed errors.
- 
-    * Fix cross-compilation bug when configuring `libf2c'.
- 
-    * Improve diagnostics.
- 
-    * Improve documentation and indexing.
- 
-    * Upgrade to `libf2c' as of 1997-09-23.  This fixes a formatted-I/O
-      bug that afflicted 64-bit systems with 32-bit integers (such as
-      Digital Alpha running GNU/Linux).
- 
- In `EGCS' 1.0.2 versus `EGCS' 1.0.1:
- ====================================
- 
-    * Fix `g77' crash triggered by `CASE' statement with an omitted
-      lower or upper bound.
- 
-    * Fix `g77' crash on statements such as `PRINT *,
-      (REAL(Z(I)),I=1,2)', where `Z' is `DOUBLE COMPLEX'.
- 
-    * Fix `-fPIC' (such as compiling for ELF targets) on the Intel x86
-      architecture target so invalid assembler code is no longer
-      produced.
- 
-    * Fix `-fpedantic' to not reject procedure invocations such as
-      `I=J()' and `CALL FOO()'.
- 
-    * Fix `-fugly-comma' to affect invocations of only external
-      procedures.  Restore rejection of gratuitous trailing omitted
-      arguments to intrinsics, as in `I=MAX(3,4,,)'.
- 
-    * Fix compiler so it accepts `-fgnu-intrinsics-*' and
-      `-fbadu77-intrinsics-*' options.
- 
- In `EGCS' 1.0.1 versus `EGCS' 1.0:
- ==================================
- 
-    * Fix run-time crash involving `NAMELIST' on 64-bit machines such as
-      Alphas.
- 
- In `EGCS' 1.0 versus `g77' 0.5.21:
- ==================================
- 
-    * Version 1.0 of `egcs' contains several regressions against version
-      0.5.21 of `g77', due to using the "vanilla" `gcc' back end instead
-      of patching it to fix a few bugs and improve performance in a few
-      cases.
- 
-      Features that have been dropped from this version of `g77' due to
-      their being implemented via `g77'-specific patches to the `gcc'
-      back end in previous releases include:
- 
-         - Support for the C-language `restrict' keyword.
- 
-         - Support for the `-W' option warning about integer division by
-           zero.
- 
-         - The Intel x86-specific option `-malign-double' applying to
-           stack-allocated data as well as statically-allocate data.
- 
-      Note that the `gcc/f/gbe/' subdirectory has been removed from this
-      distribution as a result of `g77' being fully integrated with the
-      `egcs' variant of the `gcc' back end.
- 
-    * Fix code generation for iterative `DO' loops that have one or more
-      references to the iteration variable, or to aliases of it, in
-      their control expressions.  For example, `DO 10 J=2,J' now is
-      compiled correctly.
- 
-    * Fix `DTime' intrinsic so as not to truncate results to integer
-      values (on some systems).
- 
-    * Some Fortran code, miscompiled by `g77' built on `gcc' version
-      2.8.1 on m68k-next-nextstep3 configurations when using the `-O2'
-      option, is now compiled correctly.  It is believed that a C
-      function known to miscompile on that configuration when using the
-      `-O2 -funroll-loops' options also is now compiled correctly.
- 
-    * Remove support for non-`egcs' versions of `gcc'.
- 
-    * Remove support for the `--driver' option, as `g77' now does all
-      the driving, just like `gcc'.
- 
-    * Allow any numeric argument to intrinsics `Int2' and `Int8'.
- 
-    * Improve diagnostic messages from `libf2c' so it is more likely
-      that the printing of the active format string is limited to the
-      string, with no trailing garbage being printed.
- 
-      (Unlike `f2c', `g77' did not append a null byte to its compiled
-      form of every format string specified via a `FORMAT' statement.
-      However, `f2c' would exhibit the problem anyway for a statement
-      like `PRINT '(I)garbage', 1' by printing `(I)garbage' as the
-      format string.)
- 
-    * Upgrade to `libf2c' as of 1997-09-23.  This fixes a formatted-I/O
-      bug that afflicted 64-bit systems with 32-bit integers (such as
-      Digital Alpha running GNU/Linux).
- 
- In 0.5.21:
- ==========
- 
-    * Fix a code-generation bug introduced by 0.5.20 caused by loop
-      unrolling (by specifying `-funroll-loops' or similar).  This bug
-      afflicted all code compiled by version 2.7.2.2.f.2 of `gcc' (C,
-      C++, Fortran, and so on).
- 
-    * Fix a code-generation bug manifested when combining local
-      `EQUIVALENCE' with a `DATA' statement that follows the first
-      executable statement (or is treated as an executable-context
-      statement as a result of using the `-fpedantic' option).
- 
-    * Fix a compiler crash that occurred when an integer division by a
-      constant zero is detected.  Instead, when the `-W' option is
-      specified, the `gcc' back end issues a warning about such a case.
-      This bug afflicted all code compiled by version 2.7.2.2.f.2 of
-      `gcc' (C, C++, Fortran, and so on).
- 
-    * Fix a compiler crash that occurred in some cases of procedure
-      inlining.  (Such cases became more frequent in 0.5.20.)
- 
-    * Fix a compiler crash resulting from using `DATA' or similar to
-      initialize a `COMPLEX' variable or array to zero.
- 
-    * Fix compiler crashes involving use of `AND', `OR', or `XOR'
-      intrinsics.
- 
-    * Fix compiler bug triggered when using a `COMMON' or `EQUIVALENCE'
-      variable as the target of an `ASSIGN' or assigned-`GOTO' statement.
- 
-    * Fix compiler crashes due to using the name of a some non-standard
-      intrinsics (such as `FTell' or `FPutC') as such and as the name of
-      a procedure or common block.  Such dual use of a name in a program
-      is allowed by the standard.
- 
-    * Place automatic arrays on the stack, even if `SAVE' or the
-      `-fno-automatic' option is in effect.  This avoids a compiler
-      crash in some cases.
- 
-    * The `-malign-double' option now reliably aligns `DOUBLE PRECISION'
-      optimally on Pentium and Pentium Pro architectures (586 and 686 in
-      `gcc').
- 
-    * New option `-Wno-globals' disables warnings about "suspicious" use
-      of a name both as a global name and as the implicit name of an
-      intrinsic, and warnings about disagreements over the number or
-      natures of arguments passed to global procedures, or the natures
-      of the procedures themselves.
- 
-      The default is to issue such warnings, which are new as of this
-      version of `g77'.
- 
-    * New option `-fno-globals' disables diagnostics about potentially
-      fatal disagreements analysis problems, such as disagreements over
-      the number or natures of arguments passed to global procedures, or
-      the natures of those procedures themselves.
- 
-      The default is to issue such diagnostics and flag the compilation
-      as unsuccessful.  With this option, the diagnostics are issued as
-      warnings, or, if `-Wno-globals' is specified, are not issued at
-      all.
- 
-      This option also disables inlining of global procedures, to avoid
-      compiler crashes resulting from coding errors that these
-      diagnostics normally would identify.
- 
-    * Diagnose cases where a reference to a procedure disagrees with the
-      type of that procedure, or where disagreements about the number or
-      nature of arguments exist.  This avoids a compiler crash.
- 
-    * Fix parsing bug whereby `g77' rejected a second initialization
-      specification immediately following the first's closing `/' without
-      an intervening comma in a `DATA' statement, and the second
-      specification was an implied-DO list.
- 
-    * Improve performance of the `gcc' back end so certain complicated
-      expressions involving `COMPLEX' arithmetic (especially
-      multiplication) don't appear to take forever to compile.
- 
-    * Fix a couple of profiling-related bugs in `gcc' back end.
- 
-    * Integrate GNU Ada's (GNAT's) changes to the back end, which
-      consist almost entirely of bug fixes.  These fixes are circa
-      version 3.10p of GNAT.
- 
-    * Include some other `gcc' fixes that seem useful in `g77''s version
-      of `gcc'.  (See `gcc/ChangeLog' for details--compare it to that
-      file in the vanilla `gcc-2.7.2.3.tar.gz' distribution.)
- 
-    * Fix `libU77' routines that accept file and other names to strip
-      trailing blanks from them, for consistency with other
-      implementations.  Blanks may be forcibly appended to such names by
-      appending a single null character (`CHAR(0)') to the significant
-      trailing blanks.
- 
-    * Fix `CHMOD' intrinsic to work with file names that have embedded
-      blanks, commas, and so on.
- 
-    * Fix `SIGNAL' intrinsic so it accepts an optional third `Status'
-      argument.
- 
-    * Fix `IDATE()' intrinsic subroutine (VXT form) so it accepts
-      arguments in the correct order.  Documentation fixed accordingly,
-      and for `GMTIME()' and `LTIME()' as well.
- 
-    * Make many changes to `libU77' intrinsics to support existing code
-      more directly.
- 
-      Such changes include allowing both subroutine and function forms
-      of many routines, changing `MCLOCK()' and `TIME()' to return
-      `INTEGER(KIND=1)' values, introducing `MCLOCK8()' and `TIME8()' to
-      return `INTEGER(KIND=2)' values, and placing functions that are
-      intended to perform side effects in a new intrinsic group,
-      `badu77'.
- 
-    * Improve `libU77' so it is more portable.
- 
-    * Add options `-fbadu77-intrinsics-delete',
-      `-fbadu77-intrinsics-hide', and so on.
- 
-    * Fix crashes involving diagnosed or invalid code.
- 
-    * `g77' and `gcc' now do a somewhat better job detecting and
-      diagnosing arrays that are too large to handle before these cause
-      diagnostics during the assembler or linker phase, a compiler
-      crash, or generation of incorrect code.
- 
-    * Make some fixes to alias analysis code.
- 
-    * Add support for `restrict' keyword in `gcc' front end.
- 
-    * Support `gcc' version 2.7.2.3 (modified by `g77' into version
-      2.7.2.3.f.1), and remove support for prior versions of `gcc'.
- 
-    * Incorporate GNAT's patches to the `gcc' back end into `g77''s, so
-      GNAT users do not need to apply GNAT's patches to build both GNAT
-      and `g77' from the same source tree.
- 
-    * Modify `make' rules and related code so that generation of Info
-      documentation doesn't require compilation using `gcc'.  Now, any
-      ANSI C compiler should be adequate to produce the `g77'
-      documentation (in particular, the tables of intrinsics) from
-      scratch.
- 
-    * Add `INT2' and `INT8' intrinsics.
- 
-    * Add `CPU_TIME' intrinsic.
- 
-    * Add `ALARM' intrinsic.
- 
-    * `CTIME' intrinsic now accepts any `INTEGER' argument, not just
-      `INTEGER(KIND=2)'.
- 
-    * Warn when explicit type declaration disagrees with the type of an
-      intrinsic invocation.
- 
-    * Support `*f771' entry in `gcc' `specs' file.
- 
-    * Fix typo in `make' rule `g77-cross', used only for cross-compiling.
- 
-    * Fix `libf2c' build procedure to re-archive library if previous
-      attempt to archive was interrupted.
- 
-    * Change `gcc' to unroll loops only during the last invocation (of
-      as many as two invocations) of loop optimization.
- 
-    * Improve handling of `-fno-f2c' so that code that attempts to pass
-      an intrinsic as an actual argument, such as `CALL FOO(ABS)', is
-      rejected due to the fact that the run-time-library routine is,
-      effectively, compiled with `-ff2c' in effect.
- 
-    * Fix `g77' driver to recognize `-fsyntax-only' as an option that
-      inhibits linking, just like `-c' or `-S', and to recognize and
-      properly handle the `-nostdlib', `-M', `-MM', `-nodefaultlibs',
-      and `-Xlinker' options.
- 
-    * Upgrade to `libf2c' as of 1997-08-16.
- 
-    * Modify `libf2c' to consistently and clearly diagnose recursive I/O
-      (at run time).
- 
-    * `g77' driver now prints version information (such as produced by
-      `g77 -v') to `stderr' instead of `stdout'.
- 
-    * The `.r' suffix now designates a Ratfor source file, to be
-      preprocessed via the `ratfor' command, available separately.
- 
-    * Fix some aspects of how `gcc' determines what kind of system is
-      being configured and what kinds are supported.  For example, GNU
-      Linux/Alpha ELF systems now are directly supported.
- 
-    * Improve diagnostics.
- 
-    * Improve documentation and indexing.
- 
-    * Include all pertinent files for `libf2c' that come from
-      `netlib.bell-labs.com'; give any such files that aren't quite
-      accurate in `g77''s version of `libf2c' the suffix `.netlib'.
- 
-    * Reserve `INTEGER(KIND=0)' for future use.
- 
- In 0.5.20:
- ==========
- 
-    * The `-fno-typeless-boz' option is now the default.
- 
-      This option specifies that non-decimal-radix constants using the
-      prefixed-radix form (such as `Z'1234'') are to be interpreted as
-      `INTEGER(KIND=1)' constants.  Specify `-ftypeless-boz' to cause
-      such constants to be interpreted as typeless.
- 
-      (Version 0.5.19 introduced `-fno-typeless-boz' and its inverse.)
- 
-      *Note Options Controlling Fortran Dialect: Fortran Dialect Options,
-      for information on the `-ftypeless-boz' option.
- 
-    * Options `-ff90-intrinsics-enable' and `-fvxt-intrinsics-enable'
-      now are the defaults.
- 
-      Some programs might use names that clash with intrinsic names
-      defined (and now enabled) by these options or by the new `libU77'
-      intrinsics.  Users of such programs might need to compile them
-      differently (using, for example, `-ff90-intrinsics-disable') or,
-      better yet, insert appropriate `EXTERNAL' statements specifying
-      that these names are not intended to be names of intrinsics.
- 
-    * The `ALWAYS_FLUSH' macro is no longer defined when building
-      `libf2c', which should result in improved I/O performance,
-      especially over NFS.
- 
-      _Note:_ If you have code that depends on the behavior of `libf2c'
-      when built with `ALWAYS_FLUSH' defined, you will have to modify
-      `libf2c' accordingly before building it from this and future
-      versions of `g77'.
- 
-      *Note Output Assumed To Flush::, for more information.
- 
-    * Dave Love's implementation of `libU77' has been added to the
-      version of `libf2c' distributed with and built as part of `g77'.
-      `g77' now knows about the routines in this library as intrinsics.
- 
-    * New option `-fvxt' specifies that the source file is written in
-      VXT Fortran, instead of GNU Fortran.
- 
-      *Note VXT Fortran::, for more information on the constructs
-      recognized when the `-fvxt' option is specified.
- 
-    * The `-fvxt-not-f90' option has been deleted, along with its
-      inverse, `-ff90-not-vxt'.
- 
-      If you used one of these deleted options, you should re-read the
-      pertinent documentation to determine which options, if any, are
-      appropriate for compiling your code with this version of `g77'.
- 
-      *Note Other Dialects::, for more information.
- 
-    * The `-fugly' option now issues a warning, as it likely will be
-      removed in a future version.
- 
-      (Enabling all the `-fugly-*' options is unlikely to be feasible,
-      or sensible, in the future, so users should learn to specify only
-      those `-fugly-*' options they really need for a particular source
-      file.)
- 
-    * The `-fugly-assumed' option, introduced in version 0.5.19, has
-      been changed to better accommodate old and new code.
- 
-      *Note Ugly Assumed-Size Arrays::, for more information.
- 
-    * Make a number of fixes to the `g77' front end and the `gcc' back
-      end to better support Alpha (AXP) machines.  This includes
-      providing at least one bug-fix to the `gcc' back end for Alphas.
- 
-    * Related to supporting Alpha (AXP) machines, the `LOC()' intrinsic
-      and `%LOC()' construct now return values of `INTEGER(KIND=0)' type,
-      as defined by the GNU Fortran language.
- 
-      This type is wide enough (holds the same number of bits) as the
-      character-pointer type on the machine.
- 
-      On most machines, this won't make a difference, whereas, on Alphas
-      and other systems with 64-bit pointers, the `INTEGER(KIND=0)' type
-      is equivalent to `INTEGER(KIND=2)' (often referred to as
-      `INTEGER*8') instead of the more common `INTEGER(KIND=1)' (often
-      referred to as `INTEGER*4').
- 
-    * Emulate `COMPLEX' arithmetic in the `g77' front end, to avoid bugs
-      in `complex' support in the `gcc' back end.  New option
-      `-fno-emulate-complex' causes `g77' to revert the 0.5.19 behavior.
- 
-    * Fix bug whereby `REAL A(1)', for example, caused a compiler crash
-      if `-fugly-assumed' was in effect and A was a local (automatic)
-      array.  That case is no longer affected by the new handling of
-      `-fugly-assumed'.
- 
-    * Fix `g77' command driver so that `g77 -o foo.f' no longer deletes
-      `foo.f' before issuing other diagnostics, and so the `-x' option
-      is properly handled.
- 
-    * Enable inlining of subroutines and functions by the `gcc' back end.
-      This works as it does for `gcc' itself--program units may be
-      inlined for invocations that follow them in the same program unit,
-      as long as the appropriate compile-time options are specified.
- 
-    * Dummy arguments are no longer assumed to potentially alias
-      (overlap) other dummy arguments or `COMMON' areas when any of
-      these are defined (assigned to) by Fortran code.
- 
-      This can result in faster and/or smaller programs when compiling
-      with optimization enabled, though on some systems this effect is
-      observed only when `-fforce-addr' also is specified.
- 
-      New options `-falias-check', `-fargument-alias',
-      `-fargument-noalias', and `-fno-argument-noalias-global' control
-      the way `g77' handles potential aliasing.
- 
-      *Note Aliasing Assumed To Work::, for detailed information on why
-      the new defaults might result in some programs no longer working
-      the way they did when compiled by previous versions of `g77'.
- 
-    * The `CONJG()' and `DCONJG()' intrinsics now are compiled in-line.
- 
-    * The bug-fix for 0.5.19.1 has been re-done.  The `g77' compiler has
-      been changed back to assume `libf2c' has no aliasing problems in
-      its implementations of the `COMPLEX' (and `DOUBLE COMPLEX')
-      intrinsics.  The `libf2c' has been changed to have no such
-      problems.
- 
-      As a result, 0.5.20 is expected to offer improved performance over
-      0.5.19.1, perhaps as good as 0.5.19 in most or all cases, due to
-      this change alone.
- 
-      _Note:_ This change requires version 0.5.20 of `libf2c', at least,
-      when linking code produced by any versions of `g77' other than
-      0.5.19.1.  Use `g77 -v' to determine the version numbers of the
-      `libF77', `libI77', and `libU77' components of the `libf2c'
-      library.  (If these version numbers are not printed--in
-      particular, if the linker complains about unresolved references to
-      names like `g77__fvers__'--that strongly suggests your
-      installation has an obsolete version of `libf2c'.)
- 
-    * New option `-fugly-assign' specifies that the same memory
-      locations are to be used to hold the values assigned by both
-      statements `I = 3' and `ASSIGN 10 TO I', for example.  (Normally,
-      `g77' uses a separate memory location to hold assigned statement
-      labels.)
- 
-      *Note Ugly Assigned Labels::, for more information.
- 
-    * `FORMAT' and `ENTRY' statements now are allowed to precede
-      `IMPLICIT NONE' statements.
- 
-    * Produce diagnostic for unsupported `SELECT CASE' on `CHARACTER'
-      type, instead of crashing, at compile time.
- 
-    * Fix crashes involving diagnosed or invalid code.
- 
-    * Change approach to building `libf2c' archive (`libf2c.a') so that
-      members are added to it only when truly necessary, so the user
-      that installs an already-built `g77' doesn't need to have write
-      access to the build tree (whereas the user doing the build might
-      not have access to install new software on the system).
- 
-    * Support `gcc' version 2.7.2.2 (modified by `g77' into version
-      2.7.2.2.f.2), and remove support for prior versions of `gcc'.
- 
-    * Upgrade to `libf2c' as of 1997-02-08, and fix up some of the build
-      procedures.
- 
-    * Improve general build procedures for `g77', fixing minor bugs
-      (such as deletion of any file named `f771' in the parent directory
-      of `gcc/').
- 
-    * Enable full support of `INTEGER(KIND=2)' (often referred to as
-      `INTEGER*8') available in `libf2c' and `f2c.h' so that `f2c' users
-      may make full use of its features via the `g77' version of `f2c.h'
-      and the `INTEGER(KIND=2)' support routines in the `g77' version of
-      `libf2c'.
- 
-    * Improve `g77' driver and `libf2c' so that `g77 -v' yields version
-      information on the library.
- 
-    * The `SNGL' and `FLOAT' intrinsics now are specific intrinsics,
-      instead of synonyms for the generic intrinsic `REAL'.
- 
-    * New intrinsics have been added.  These are `REALPART', `IMAGPART',
-      `COMPLEX', `LONG', and `SHORT'.
- 
-    * A new group of intrinsics, `gnu', has been added to contain the
-      new `REALPART', `IMAGPART', and `COMPLEX' intrinsics.  An old
-      group, `dcp', has been removed.
- 
-    * Complain about industry-wide ambiguous references `REAL(EXPR)' and
-      `AIMAG(EXPR)', where EXPR is `DOUBLE COMPLEX' (or any complex type
-      other than `COMPLEX'), unless `-ff90' option specifies Fortran 90
-      interpretation or new `-fugly-complex' option, in conjunction with
-      `-fnot-f90', specifies `f2c' interpretation.
- 
-    * Make improvements to diagnostics.
- 
-    * Speed up compiler a bit.
- 
-    * Improvements to documentation and indexing, including a new
-      chapter containing information on one, later more, diagnostics
-      that users are directed to pull up automatically via a message in
-      the diagnostic itself.
- 
-      (Hence the menu item `M' for the node `Diagnostics' in the
-      top-level menu of the Info documentation.)
- 
- In previous versions:
- =====================
- 
-    Information on previous versions is archived in `gcc/gcc/f/news.texi'
- following the test of the `DOC-OLDNEWS' macro.
- 
--- 0 ----
diff -Nrc3pad gcc-3.2.3/gcc/f/g77.info-5 gcc-3.3/gcc/f/g77.info-5
*** gcc-3.2.3/gcc/f/g77.info-5	2003-04-22 07:07:23.000000000 +0000
--- gcc-3.3/gcc/f/g77.info-5	1970-01-01 00:00:00.000000000 +0000
***************
*** 1,1256 ****
- This is g77.info, produced by makeinfo version 4.5 from g77.texi.
- 
- INFO-DIR-SECTION Programming
- START-INFO-DIR-ENTRY
- * g77: (g77).                  The GNU Fortran compiler.
- END-INFO-DIR-ENTRY
-    This file documents the use and the internals of the GNU Fortran
- (`g77') compiler.  It corresponds to the GCC-3.2.3 version of `g77'.
- 
-    Published by the Free Software Foundation 59 Temple Place - Suite 330
- Boston, MA 02111-1307 USA
- 
-    Copyright (C) 1995,1996,1997,1998,1999,2000,2001,2002 Free Software
- Foundation, Inc.
- 
-    Permission is granted to copy, distribute and/or modify this document
- under the terms of the GNU Free Documentation License, Version 1.1 or
- any later version published by the Free Software Foundation; with the
- Invariant Sections being "GNU General Public License" and "Funding Free
- Software", the Front-Cover texts being (a) (see below), and with the
- Back-Cover Texts being (b) (see below).  A copy of the license is
- included in the section entitled "GNU Free Documentation License".
- 
-    (a) The FSF's Front-Cover Text is:
- 
-    A GNU Manual
- 
-    (b) The FSF's Back-Cover Text is:
- 
-    You have freedom to copy and modify this GNU Manual, like GNU
- software.  Copies published by the Free Software Foundation raise
- funds for GNU development.
- 
-    Contributed by James Craig Burley (<craig@jcb-sc.com>).  Inspired by
- a first pass at translating `g77-0.5.16/f/DOC' that was contributed to
- Craig by David Ronis (<ronis@onsager.chem.mcgill.ca>).
- 
- 
- File: g77.info,  Node: Changes,  Next: Language,  Prev: News,  Up: Top
- 
- User-visible Changes
- ********************
- 
-    This chapter describes changes to `g77' that are visible to the
- programmers who actually write and maintain Fortran code they compile
- with `g77'.  Information on changes to installation procedures, changes
- to the documentation, and bug fixes is not provided here, unless it is
- likely to affect how users use `g77'.  *Note News About GNU Fortran:
- News, for information on such changes to `g77'.
- 
-    Note that two variants of `g77' are tracked below.  The `egcs'
- variant is described vis-a-vis previous versions of `egcs' and/or an
- official FSF version, as appropriate.  Note that all such variants are
- obsolete _as of July 1999_ - the information is retained here only for
- its historical value.
- 
-    Therefore, `egcs' versions sometimes have multiple listings to help
- clarify how they differ from other versions, though this can make
- getting a complete picture of what a particular `egcs' version contains
- somewhat more difficult.
- 
-    For information on bugs in the GCC-3.2.3 version of `g77', see *Note
- Known Bugs In GNU Fortran: Known Bugs.
- 
-    The following information was last updated on 2002-10-28:
- 
- In `GCC' 3.2 versus `GCC' 3.1:
- ==============================
- 
-    * Problem Reports fixed (in chronological order of submission):
-     `8308'
-           gcc-3.x does not compile files with suffix .r (RATFOR) [Fixed
-           in 3.2.1]
- 
- In `GCC' 3.1 (formerly known as g77-0.5.27) versus `GCC' 3.0:
- =============================================================
- 
-    * Problem Reports fixed (in chronological order of submission):
-     `947'
-           Data statement initialization with subscript of kind INTEGER*2
- 
-     `3743'
-           Reference to intrinsic `ISHFT' invalid
- 
-     `3807'
-           Function BESJN(integer,double) problems
- 
-     `3957'
-           g77 -pipe -xf77-cpp-input sends output to stdout
- 
-     `4279'
-           g77 -h" gives bogus output
- 
-     `4730'
-           ICE on valid input using CALL EXIT(%VAL(...))
- 
-     `4752'
-           g77 -v -c -xf77-version /dev/null -xnone causes ice
- 
-     `4885'
-           BACKSPACE example that doesn't work as of gcc/g77-3.0.x
- 
-     `5122'
-           g77 rejects accepted use of INTEGER*2 as type of DATA
-           statement loop index
- 
-     `5397'
-           ICE on compiling source with 540 000 000 REAL array
- 
-     `5473'
-           ICE on BESJN(integer*8,real)
- 
-     `5837'
-           bug in loop unrolling
- 
-    * `g77' now has its man page generated from the texinfo
-      documentation, to guarantee that it remains up to date.
- 
-    * `g77' used to reject the following program on 32-bit targets:
-           PROGRAM PROG
-           DIMENSION A(140 000 000)
-           END
-      with the message:
-           prog.f: In program `prog':
-           prog.f:2:
-                    DIMENSION A(140 000 000)
-                              ^
-           Array `a' at (^) is too large to handle
-      because 140 000 000 REALs is larger than the largest bit-extent
-      that can be expressed in 32 bits.  However, bit-sizes never play a
-      role after offsets have been converted to byte addresses.
-      Therefore this check has been removed, and the limit is now 2
-      Gbyte of memory (around 530 000 000 REALs).  Note: On GNU/Linux
-      systems one has to compile programs that occupy more than 1 Gbyte
-      statically, i.e. `g77 -static ...'.
- 
-    * Based on work done by Juergen Pfeifer (<juergen.pfeifer@gmx.net>)
-      libf2c is now a shared library.  One can still link in all objects
-      with the program by specifying the `-static' option.
- 
-    * Robert Anderson (<rwa@alumni.princeton.edu>) thought up a two line
-      change that enables g77 to compile such code as:
-           SUBROUTINE SUB(A, N)
-           DIMENSION N(2)
-           DIMENSION A(N(1),N(2))
-           A(1,1) = 1.
-           END
-      Note the use of array elements in the bounds of the adjustable
-      array A.
- 
-    * George Helffrich (<george@geo.titech.ac.jp>) implemented a change
-      in substring index checking (when specifying `-fbounds-check')
-      that permits the use of zero length substrings of the form
-      `string(1:0)'.
- 
-    * Based on code developed by Pedro Vazquez
-      (<vazquez@penelope.iqm.unicamp.br>), the `libf2c' library is now
-      able to read and write files larger than 2 Gbyte on 32-bit target
-      machines, if the operating system supports this.
- 
- In 0.5.26, `GCC' 3.0 versus `GCC' 2.95:
- =======================================
- 
-    * When a REWIND was issued after a WRITE statement on an unformatted
-      file, the implicit truncation was performed by copying the
-      truncated file to /tmp and copying the result back.  This has been
-      fixed by using the `ftruncate' OS function.  Thanks go to the
-      GAMESS developers for bringing this to our attention.
- 
-    * Using options `-g', `-ggdb' or `-gdwarf[-2]' (where appropriate
-      for your target) now also enables debugging information for COMMON
-      BLOCK and EQUIVALENCE items to be emitted.  Thanks go to Andrew
-      Vaught (<andy@xena.eas.asu.edu>) and George Helffrich
-      (<george@geology.bristol.ac.uk>) for fixing this longstanding
-      problem.
- 
-    * It is not necessary anymore to use the option `-femulate-complex'
-      to compile Fortran code using COMPLEX arithmetic, even on 64-bit
-      machines (like the Alpha).  This will improve code generation.
- 
-    * INTRINSIC arithmetic functions are now treated as routines that do
-      not depend on anything but their argument(s).  This enables
-      further instruction scheduling, because it is known that they
-      cannot read or modify arbitrary locations.
- 
- 
- In 0.5.25, `GCC' 2.95 (`EGCS' 1.2) versus `EGCS' 1.1.2:
- =======================================================
- 
-    * The new `-fbounds-check' option causes `g77' to compile run-time
-      bounds checks of array subscripts, as well as of substring start
-      and end points.
- 
-    * `libg2c' now supports building as multilibbed library, which
-      provides better support for systems that require options such as
-      `-mieee' to work properly.
- 
-    * Source file names with the suffixes `.FOR' and `.FPP' now are
-      recognized by `g77' as if they ended in `.for' and `.fpp',
-      respectively.
- 
-    * The order of arguments to the _subroutine_ forms of the `CTime',
-      `DTime', `ETime', and `TtyNam' intrinsics has been swapped.  The
-      argument serving as the returned value for the corresponding
-      function forms now is the _second_ argument, making these
-      consistent with the other subroutine forms of `libU77' intrinsics.
- 
-    * `g77' now warns about a reference to an intrinsic that has an
-      interface that is not Year 2000 (Y2K) compliant.  Also, `libg2c'
-      has been changed to increase the likelihood of catching references
-      to the implementations of these intrinsics using the `EXTERNAL'
-      mechanism (which would avoid the new warnings).
- 
-      *Note Year 2000 (Y2K) Problems::, for more information.
- 
-    * `-fno-emulate-complex' is now the default option.  This should
-      result in improved performance of code that uses the `COMPLEX'
-      data type.
- 
-    * The `-malign-double' option now reliably aligns _all_
-      double-precision variables and arrays on Intel x86 targets.
- 
-    * `g77' no longer generates code to maintain `errno', a C-language
-      concept, when performing operations such as the `SqRt' intrinsic.
- 
-    * Support for the `-fugly' option has been removed.
- 
- 
- In 0.5.24 versus 0.5.23:
- ========================
- 
-    There is no `g77' version 0.5.24 at this time, or planned.  0.5.24
- is the version number designated for bug fixes and, perhaps, some new
- features added, to 0.5.23.  Version 0.5.23 requires `gcc' 2.8.1, as
- 0.5.24 was planned to require.
- 
-    Due to `EGCS' becoming `GCC' (which is now an acronym for "GNU
- Compiler Collection"), and `EGCS' 1.2 becoming officially designated
- `GCC' 2.95, there seems to be no need for an actual 0.5.24 release.
- 
-    To reduce the confusion already resulting from use of 0.5.24 to
- designate `g77' versions within `EGCS' versions 1.0 and 1.1, as well as
- in versions of `g77' documentation and notices during that period,
- "mainline" `g77' version numbering resumes at 0.5.25 with `GCC' 2.95
- (`EGCS' 1.2), skipping over 0.5.24 as a placeholder version number.
- 
-    To repeat, there is no `g77' 0.5.24, but there is now a 0.5.25.
- Please remain calm and return to your keypunch units.
- 
- In `EGCS' 1.1.2 versus `EGCS' 1.1.1:
- ====================================
- 
- In `EGCS' 1.1.1 versus `EGCS' 1.1:
- ==================================
- 
- In `EGCS' 1.1 versus `EGCS' 1.0.3:
- ==================================
- 
-    * Support `FORMAT(I<EXPR>)' when EXPR is a compile-time constant
-      `INTEGER' expression.
- 
-    * Fix `g77' `-g' option so procedures that use `ENTRY' can be
-      stepped through, line by line, in `gdb'.
- 
-    * Allow any `REAL' argument to intrinsics `Second' and `CPU_Time'.
- 
-    * Use `tempnam', if available, to open scratch files (as in
-      `OPEN(STATUS='SCRATCH')') so that the `TMPDIR' environment
-      variable, if present, is used.
- 
-    * `g77''s version of `libf2c' separates out the setting of global
-      state (such as command-line arguments and signal handling) from
-      `main.o' into distinct, new library archive members.
- 
-      This should make it easier to write portable applications that
-      have their own (non-Fortran) `main()' routine properly set up the
-      `libf2c' environment, even when `libf2c' (now `libg2c') is a
-      shared library.
- 
-    * The `g77' command now expects the run-time library to be named
-      `libg2c.a' instead of `libf2c.a', to ensure that a version other
-      than the one built and installed as part of the same `g77' version
-      is picked up.
- 
-    * Some diagnostics have been changed from warnings to errors, to
-      prevent inadvertent use of the resulting, probably buggy, programs.
-      These mostly include diagnostics about use of unsupported features
-      in the `OPEN', `INQUIRE', `READ', and `WRITE' statements, and
-      about truncations of various sorts of constants.
- 
- 
- In `EGCS' 1.1 versus `g77' 0.5.23:
- ==================================
- 
-    * `g77' now treats `%LOC(EXPR)' and `LOC(EXPR)' as "ordinary"
-      expressions when they are used as arguments in procedure calls.
-      This change applies only to global (filewide) analysis, making it
-      consistent with how `g77' actually generates code for these cases.
- 
-      Previously, `g77' treated these expressions as denoting special
-      "pointer" arguments for the purposes of filewide analysis.
- 
-    * Align static double-precision variables and arrays on Intel x86
-      targets regardless of whether `-malign-double' is specified.
- 
-      Generally, this affects only local variables and arrays having the
-      `SAVE' attribute or given initial values via `DATA'.
- 
-    * The `g77' driver now ensures that `-lg2c' is specified in the link
-      phase prior to any occurrence of `-lm'.  This prevents
-      accidentally linking to a routine in the SunOS4 `-lm' library when
-      the generated code wants to link to the one in `libf2c' (`libg2c').
- 
-    * `g77' emits more debugging information when `-g' is used.
- 
-      This new information allows, for example, `which __g77_length_a'
-      to be used in `gdb' to determine the type of the phantom length
-      argument supplied with `CHARACTER' variables.
- 
-      This information pertains to internally-generated type, variable,
-      and other information, not to the longstanding deficiencies
-      vis-a-vis `COMMON' and `EQUIVALENCE'.
- 
-    * The F90 `Date_and_Time' intrinsic now is supported.
- 
-    * The F90 `System_Clock' intrinsic allows the optional arguments
-      (except for the `Count' argument) to be omitted.
- 
- 
- In 0.5.23 versus 0.5.22:
- ========================
- 
-    * This release contains several regressions against version 0.5.22
-      of `g77', due to using the "vanilla" `gcc' back end instead of
-      patching it to fix a few bugs and improve performance in a few
-      cases.
- 
-      Features that have been dropped from this version of `g77' due to
-      their being implemented via `g77'-specific patches to the `gcc'
-      back end in previous releases include:
- 
-         - Support for `__restrict__' keyword, the options
-           `-fargument-alias', `-fargument-noalias', and
-           `-fargument-noalias-global', and the corresponding
-           alias-analysis code.
- 
-           (`egcs' has the alias-analysis code, but not the
-           `__restrict__' keyword.  `egcs' `g77' users benefit from the
-           alias-analysis code despite the lack of the `__restrict__'
-           keyword, which is a C-language construct.)
- 
-         - Support for the GNU compiler options `-fmove-all-movables',
-           `-freduce-all-givs', and `-frerun-loop-opt'.
- 
-           (`egcs' supports these options.  `g77' users of `egcs'
-           benefit from them even if they are not explicitly specified,
-           because the defaults are optimized for `g77' users.)
- 
-         - Support for the `-W' option warning about integer division by
-           zero.
- 
-         - The Intel x86-specific option `-malign-double' applying to
-           stack-allocated data as well as statically-allocate data.
- 
-    * Support `gcc' version 2.8, and remove support for prior versions
-      of `gcc'.
- 
-    * Remove support for the `--driver' option, as `g77' now does all
-      the driving, just like `gcc'.
- 
-    * The `g77' command now expects the run-time library to be named
-      `libg2c.a' instead of `libf2c.a', to ensure that a version other
-      than the one built and installed as part of the same `g77' version
-      is picked up.
- 
-    * `g77''s version of `libf2c' separates out the setting of global
-      state (such as command-line arguments and signal handling) from
-      `main.o' into distinct, new library archive members.
- 
-      This should make it easier to write portable applications that
-      have their own (non-Fortran) `main()' routine properly set up the
-      `libf2c' environment, even when `libf2c' (now `libg2c') is a
-      shared library.
- 
-    * Some diagnostics have been changed from warnings to errors, to
-      prevent inadvertent use of the resulting, probably buggy, programs.
-      These mostly include diagnostics about use of unsupported features
-      in the `OPEN', `INQUIRE', `READ', and `WRITE' statements, and
-      about truncations of various sorts of constants.
- 
- 
- In 0.5.22 versus 0.5.21:
- ========================
- 
-    * Fix `Signal' intrinsic so it offers portable support for 64-bit
-      systems (such as Digital Alphas running GNU/Linux).
- 
-    * Support `FORMAT(I<EXPR>)' when EXPR is a compile-time constant
-      `INTEGER' expression.
- 
-    * Fix `g77' `-g' option so procedures that use `ENTRY' can be
-      stepped through, line by line, in `gdb'.
- 
-    * Allow any `REAL' argument to intrinsics `Second' and `CPU_Time'.
- 
-    * Allow any numeric argument to intrinsics `Int2' and `Int8'.
- 
-    * Use `tempnam', if available, to open scratch files (as in
-      `OPEN(STATUS='SCRATCH')') so that the `TMPDIR' environment
-      variable, if present, is used.
- 
-    * Rename the `gcc' keyword `restrict' to `__restrict__', to avoid
-      rejecting valid, existing, C programs.  Support for `restrict' is
-      now more like support for `complex'.
- 
-    * Fix `-fugly-comma' to affect invocations of only external
-      procedures.  Restore rejection of gratuitous trailing omitted
-      arguments to intrinsics, as in `I=MAX(3,4,,)'.
- 
-    * Fix compiler so it accepts `-fgnu-intrinsics-*' and
-      `-fbadu77-intrinsics-*' options.
- 
- 
- In `EGCS' 1.0.2 versus `EGCS' 1.0.1:
- ====================================
- 
-    * Fix compiler so it accepts `-fgnu-intrinsics-*' and
-      `-fbadu77-intrinsics-*' options.
- 
- In `EGCS' 1.0.1 versus `EGCS' 1.0:
- ==================================
- 
- In `EGCS' 1.0 versus `g77' 0.5.21:
- ==================================
- 
-    * Version 1.0 of `egcs' contains several regressions against version
-      0.5.21 of `g77', due to using the "vanilla" `gcc' back end instead
-      of patching it to fix a few bugs and improve performance in a few
-      cases.
- 
-      Features that have been dropped from this version of `g77' due to
-      their being implemented via `g77'-specific patches to the `gcc'
-      back end in previous releases include:
- 
-         - Support for the C-language `restrict' keyword.
- 
-         - Support for the `-W' option warning about integer division by
-           zero.
- 
-         - The Intel x86-specific option `-malign-double' applying to
-           stack-allocated data as well as statically-allocate data.
- 
-    * Remove support for the `--driver' option, as `g77' now does all
-      the driving, just like `gcc'.
- 
-    * Allow any numeric argument to intrinsics `Int2' and `Int8'.
- 
- 
- In 0.5.21:
- ==========
- 
-    * When the `-W' option is specified, `gcc', `g77', and other GNU
-      compilers that incorporate the `gcc' back end as modified by
-      `g77', issue a warning about integer division by constant zero.
- 
-    * New option `-Wno-globals' disables warnings about "suspicious" use
-      of a name both as a global name and as the implicit name of an
-      intrinsic, and warnings about disagreements over the number or
-      natures of arguments passed to global procedures, or the natures
-      of the procedures themselves.
- 
-      The default is to issue such warnings, which are new as of this
-      version of `g77'.
- 
-    * New option `-fno-globals' disables diagnostics about potentially
-      fatal disagreements analysis problems, such as disagreements over
-      the number or natures of arguments passed to global procedures, or
-      the natures of those procedures themselves.
- 
-      The default is to issue such diagnostics and flag the compilation
-      as unsuccessful.  With this option, the diagnostics are issued as
-      warnings, or, if `-Wno-globals' is specified, are not issued at
-      all.
- 
-      This option also disables inlining of global procedures, to avoid
-      compiler crashes resulting from coding errors that these
-      diagnostics normally would identify.
- 
-    * Fix `libU77' routines that accept file and other names to strip
-      trailing blanks from them, for consistency with other
-      implementations.  Blanks may be forcibly appended to such names by
-      appending a single null character (`CHAR(0)') to the significant
-      trailing blanks.
- 
-    * Fix `CHMOD' intrinsic to work with file names that have embedded
-      blanks, commas, and so on.
- 
-    * Fix `SIGNAL' intrinsic so it accepts an optional third `Status'
-      argument.
- 
-    * Make many changes to `libU77' intrinsics to support existing code
-      more directly.
- 
-      Such changes include allowing both subroutine and function forms
-      of many routines, changing `MCLOCK()' and `TIME()' to return
-      `INTEGER(KIND=1)' values, introducing `MCLOCK8()' and `TIME8()' to
-      return `INTEGER(KIND=2)' values, and placing functions that are
-      intended to perform side effects in a new intrinsic group,
-      `badu77'.
- 
-    * Add options `-fbadu77-intrinsics-delete',
-      `-fbadu77-intrinsics-hide', and so on.
- 
-    * Add `INT2' and `INT8' intrinsics.
- 
-    * Add `CPU_TIME' intrinsic.
- 
-    * Add `ALARM' intrinsic.
- 
-    * `CTIME' intrinsic now accepts any `INTEGER' argument, not just
-      `INTEGER(KIND=2)'.
- 
-    * `g77' driver now prints version information (such as produced by
-      `g77 -v') to `stderr' instead of `stdout'.
- 
-    * The `.r' suffix now designates a Ratfor source file, to be
-      preprocessed via the `ratfor' command, available separately.
- 
- 
- In 0.5.20:
- ==========
- 
-    * The `-fno-typeless-boz' option is now the default.
- 
-      This option specifies that non-decimal-radix constants using the
-      prefixed-radix form (such as `Z'1234'') are to be interpreted as
-      `INTEGER(KIND=1)' constants.  Specify `-ftypeless-boz' to cause
-      such constants to be interpreted as typeless.
- 
-      (Version 0.5.19 introduced `-fno-typeless-boz' and its inverse.)
- 
-      *Note Options Controlling Fortran Dialect: Fortran Dialect Options,
-      for information on the `-ftypeless-boz' option.
- 
-    * Options `-ff90-intrinsics-enable' and `-fvxt-intrinsics-enable'
-      now are the defaults.
- 
-      Some programs might use names that clash with intrinsic names
-      defined (and now enabled) by these options or by the new `libU77'
-      intrinsics.  Users of such programs might need to compile them
-      differently (using, for example, `-ff90-intrinsics-disable') or,
-      better yet, insert appropriate `EXTERNAL' statements specifying
-      that these names are not intended to be names of intrinsics.
- 
-    * The `ALWAYS_FLUSH' macro is no longer defined when building
-      `libf2c', which should result in improved I/O performance,
-      especially over NFS.
- 
-      _Note:_ If you have code that depends on the behavior of `libf2c'
-      when built with `ALWAYS_FLUSH' defined, you will have to modify
-      `libf2c' accordingly before building it from this and future
-      versions of `g77'.
- 
-      *Note Output Assumed To Flush::, for more information.
- 
-    * Dave Love's implementation of `libU77' has been added to the
-      version of `libf2c' distributed with and built as part of `g77'.
-      `g77' now knows about the routines in this library as intrinsics.
- 
-    * New option `-fvxt' specifies that the source file is written in
-      VXT Fortran, instead of GNU Fortran.
- 
-      *Note VXT Fortran::, for more information on the constructs
-      recognized when the `-fvxt' option is specified.
- 
-    * The `-fvxt-not-f90' option has been deleted, along with its
-      inverse, `-ff90-not-vxt'.
- 
-      If you used one of these deleted options, you should re-read the
-      pertinent documentation to determine which options, if any, are
-      appropriate for compiling your code with this version of `g77'.
- 
-      *Note Other Dialects::, for more information.
- 
-    * The `-fugly' option now issues a warning, as it likely will be
-      removed in a future version.
- 
-      (Enabling all the `-fugly-*' options is unlikely to be feasible,
-      or sensible, in the future, so users should learn to specify only
-      those `-fugly-*' options they really need for a particular source
-      file.)
- 
-    * The `-fugly-assumed' option, introduced in version 0.5.19, has
-      been changed to better accommodate old and new code.
- 
-      *Note Ugly Assumed-Size Arrays::, for more information.
- 
-    * Related to supporting Alpha (AXP) machines, the `LOC()' intrinsic
-      and `%LOC()' construct now return values of `INTEGER(KIND=0)' type,
-      as defined by the GNU Fortran language.
- 
-      This type is wide enough (holds the same number of bits) as the
-      character-pointer type on the machine.
- 
-      On most machines, this won't make a difference, whereas, on Alphas
-      and other systems with 64-bit pointers, the `INTEGER(KIND=0)' type
-      is equivalent to `INTEGER(KIND=2)' (often referred to as
-      `INTEGER*8') instead of the more common `INTEGER(KIND=1)' (often
-      referred to as `INTEGER*4').
- 
-    * Emulate `COMPLEX' arithmetic in the `g77' front end, to avoid bugs
-      in `complex' support in the `gcc' back end.  New option
-      `-fno-emulate-complex' causes `g77' to revert the 0.5.19 behavior.
- 
-    * Dummy arguments are no longer assumed to potentially alias
-      (overlap) other dummy arguments or `COMMON' areas when any of
-      these are defined (assigned to) by Fortran code.
- 
-      This can result in faster and/or smaller programs when compiling
-      with optimization enabled, though on some systems this effect is
-      observed only when `-fforce-addr' also is specified.
- 
-      New options `-falias-check', `-fargument-alias',
-      `-fargument-noalias', and `-fno-argument-noalias-global' control
-      the way `g77' handles potential aliasing.
- 
-      *Note Aliasing Assumed To Work::, for detailed information on why
-      the new defaults might result in some programs no longer working
-      the way they did when compiled by previous versions of `g77'.
- 
-    * New option `-fugly-assign' specifies that the same memory
-      locations are to be used to hold the values assigned by both
-      statements `I = 3' and `ASSIGN 10 TO I', for example.  (Normally,
-      `g77' uses a separate memory location to hold assigned statement
-      labels.)
- 
-      *Note Ugly Assigned Labels::, for more information.
- 
-    * `FORMAT' and `ENTRY' statements now are allowed to precede
-      `IMPLICIT NONE' statements.
- 
-    * Enable full support of `INTEGER(KIND=2)' (often referred to as
-      `INTEGER*8') available in `libf2c' and `f2c.h' so that `f2c' users
-      may make full use of its features via the `g77' version of `f2c.h'
-      and the `INTEGER(KIND=2)' support routines in the `g77' version of
-      `libf2c'.
- 
-    * Improve `g77' driver and `libf2c' so that `g77 -v' yields version
-      information on the library.
- 
-    * The `SNGL' and `FLOAT' intrinsics now are specific intrinsics,
-      instead of synonyms for the generic intrinsic `REAL'.
- 
-    * New intrinsics have been added.  These are `REALPART', `IMAGPART',
-      `COMPLEX', `LONG', and `SHORT'.
- 
-    * A new group of intrinsics, `gnu', has been added to contain the
-      new `REALPART', `IMAGPART', and `COMPLEX' intrinsics.  An old
-      group, `dcp', has been removed.
- 
-    * Complain about industry-wide ambiguous references `REAL(EXPR)' and
-      `AIMAG(EXPR)', where EXPR is `DOUBLE COMPLEX' (or any complex type
-      other than `COMPLEX'), unless `-ff90' option specifies Fortran 90
-      interpretation or new `-fugly-complex' option, in conjunction with
-      `-fnot-f90', specifies `f2c' interpretation.
- 
- 
- In previous versions:
- =====================
- 
-    Information on previous versions is archived in `gcc/gcc/f/news.texi'
- following the test of the `DOC-OLDNEWS' macro.
- 
- 
- File: g77.info,  Node: Language,  Next: Compiler,  Prev: Changes,  Up: Top
- 
- The GNU Fortran Language
- ************************
- 
-    GNU Fortran supports a variety of extensions to, and dialects of,
- the Fortran language.  Its primary base is the ANSI FORTRAN 77
- standard, currently available on the network at
- `http://www.fortran.com/fortran/F77_std/rjcnf0001.html' or as
- monolithic text at
- `http://www.fortran.com/fortran/F77_std/f77_std.html'.  It offers some
- extensions that are popular among users of UNIX `f77' and `f2c'
- compilers, some that are popular among users of other compilers (such
- as Digital products), some that are popular among users of the newer
- Fortran 90 standard, and some that are introduced by GNU Fortran.
- 
-    (If you need a text on Fortran, a few freely available electronic
- references have pointers from `http://www.fortran.com/fortran/Books/'.
- There is a `cooperative net project', `User Notes on Fortran
- Programming' at `ftp://vms.huji.ac.il/fortran/' and mirrors elsewhere;
- some of this material might not apply specifically to `g77'.)
- 
-    Part of what defines a particular implementation of a Fortran
- system, such as `g77', is the particular characteristics of how it
- supports types, constants, and so on.  Much of this is left up to the
- implementation by the various Fortran standards and accepted practice
- in the industry.
- 
-    The GNU Fortran _language_ is described below.  Much of the material
- is organized along the same lines as the ANSI FORTRAN 77 standard
- itself.
- 
-    *Note Other Dialects::, for information on features `g77' supports
- that are not part of the GNU Fortran language.
- 
-    _Note_: This portion of the documentation definitely needs a lot of
- work!
- 
- * Menu:
- 
- Relationship to the ANSI FORTRAN 77 standard:
- * Direction of Language Development::  Where GNU Fortran is headed.
- * Standard Support::  Degree of support for the standard.
- 
- Extensions to the ANSI FORTRAN 77 standard:
- * Conformance::
- * Notation Used::
- * Terms and Concepts::
- * Characters Lines Sequence::
- * Data Types and Constants::
- * Expressions::
- * Specification Statements::
- * Control Statements::
- * Functions and Subroutines::
- * Scope and Classes of Names::
- * I/O::
- * Fortran 90 Features::
- 
- 
- File: g77.info,  Node: Direction of Language Development,  Next: Standard Support,  Up: Language
- 
- Direction of Language Development
- =================================
- 
-    The purpose of the following description of the GNU Fortran language
- is to promote wide portability of GNU Fortran programs.
- 
-    GNU Fortran is an evolving language, due to the fact that `g77'
- itself is in beta test.  Some current features of the language might
- later be redefined as dialects of Fortran supported by `g77' when
- better ways to express these features are added to `g77', for example.
- Such features would still be supported by `g77', but would be available
- only when one or more command-line options were used.
- 
-    The GNU Fortran _language_ is distinct from the GNU Fortran
- _compilation system_ (`g77').
- 
-    For example, `g77' supports various dialects of Fortran--in a sense,
- these are languages other than GNU Fortran--though its primary purpose
- is to support the GNU Fortran language, which also is described in its
- documentation and by its implementation.
- 
-    On the other hand, non-GNU compilers might offer support for the GNU
- Fortran language, and are encouraged to do so.
- 
-    Currently, the GNU Fortran language is a fairly fuzzy object.  It
- represents something of a cross between what `g77' accepts when
- compiling using the prevailing defaults and what this document
- describes as being part of the language.
- 
-    Future versions of `g77' are expected to clarify the definition of
- the language in the documentation.  Often, this will mean adding new
- features to the language, in the form of both new documentation and new
- support in `g77'.  However, it might occasionally mean removing a
- feature from the language itself to "dialect" status.  In such a case,
- the documentation would be adjusted to reflect the change, and `g77'
- itself would likely be changed to require one or more command-line
- options to continue supporting the feature.
- 
-    The development of the GNU Fortran language is intended to strike a
- balance between:
- 
-    * Serving as a mostly-upwards-compatible language from the de facto
-      UNIX Fortran dialect as supported by `f77'.
- 
-    * Offering new, well-designed language features.  Attributes of such
-      features include not making existing code any harder to read (for
-      those who might be unaware that the new features are not in use)
-      and not making state-of-the-art compilers take longer to issue
-      diagnostics, among others.
- 
-    * Supporting existing, well-written code without gratuitously
-      rejecting non-standard constructs, regardless of the origin of the
-      code (its dialect).
- 
-    * Offering default behavior and command-line options to reduce and,
-      where reasonable, eliminate the need for programmers to make any
-      modifications to code that already works in existing production
-      environments.
- 
-    * Diagnosing constructs that have different meanings in different
-      systems, languages, and dialects, while offering clear, less
-      ambiguous ways to express each of the different meanings so
-      programmers can change their code appropriately.
- 
-    One of the biggest practical challenges for the developers of the
- GNU Fortran language is meeting the sometimes contradictory demands of
- the above items.
- 
-    For example, a feature might be widely used in one popular
- environment, but the exact same code that utilizes that feature might
- not work as expected--perhaps it might mean something entirely
- different--in another popular environment.
- 
-    Traditionally, Fortran compilers--even portable ones--have solved
- this problem by simply offering the appropriate feature to users of the
- respective systems.  This approach treats users of various Fortran
- systems and dialects as remote "islands", or camps, of programmers, and
- assume that these camps rarely come into contact with each other (or,
- especially, with each other's code).
- 
-    Project GNU takes a radically different approach to software and
- language design, in that it assumes that users of GNU software do not
- necessarily care what kind of underlying system they are using,
- regardless of whether they are using software (at the user-interface
- level) or writing it (for example, writing Fortran or C code).
- 
-    As such, GNU users rarely need consider just what kind of underlying
- hardware (or, in many cases, operating system) they are using at any
- particular time.  They can use and write software designed for a
- general-purpose, widely portable, heterogenous environment--the GNU
- environment.
- 
-    In line with this philosophy, GNU Fortran must evolve into a product
- that is widely ported and portable not only in the sense that it can be
- successfully built, installed, and run by users, but in the larger
- sense that its users can use it in the same way, and expect largely the
- same behaviors from it, regardless of the kind of system they are using
- at any particular time.
- 
-    This approach constrains the solutions `g77' can use to resolve
- conflicts between various camps of Fortran users.  If these two camps
- disagree about what a particular construct should mean, `g77' cannot
- simply be changed to treat that particular construct as having one
- meaning without comment (such as a warning), lest the users expecting
- it to have the other meaning are unpleasantly surprised that their code
- misbehaves when executed.
- 
-    The use of the ASCII backslash character in character constants is
- an excellent (and still somewhat unresolved) example of this kind of
- controversy.  *Note Backslash in Constants::.  Other examples are
- likely to arise in the future, as `g77' developers strive to improve
- its ability to accept an ever-wider variety of existing Fortran code
- without requiring significant modifications to said code.
- 
-    Development of GNU Fortran is further constrained by the desire to
- avoid requiring programmers to change their code.  This is important
- because it allows programmers, administrators, and others to more
- faithfully evaluate and validate `g77' (as an overall product and as
- new versions are distributed) without having to support multiple
- versions of their programs so that they continue to work the same way
- on their existing systems (non-GNU perhaps, but possibly also earlier
- versions of `g77').
- 
- 
- File: g77.info,  Node: Standard Support,  Next: Conformance,  Prev: Direction of Language Development,  Up: Language
- 
- ANSI FORTRAN 77 Standard Support
- ================================
- 
-    GNU Fortran supports ANSI FORTRAN 77 with the following caveats.  In
- summary, the only ANSI FORTRAN 77 features `g77' doesn't support are
- those that are probably rarely used in actual code, some of which are
- explicitly disallowed by the Fortran 90 standard.
- 
- * Menu:
- 
- * No Passing External Assumed-length::  CHAR*(*) CFUNC restriction.
- * No Passing Dummy Assumed-length::     CHAR*(*) CFUNC restriction.
- * No Pathological Implied-DO::          No `((..., I=...), I=...)'.
- * No Useless Implied-DO::               No `(A, I=1, 1)'.
- 
- 
- File: g77.info,  Node: No Passing External Assumed-length,  Next: No Passing Dummy Assumed-length,  Up: Standard Support
- 
- No Passing External Assumed-length
- ----------------------------------
- 
-    `g77' disallows passing of an external procedure as an actual
- argument if the procedure's type is declared `CHARACTER*(*)'.  For
- example:
- 
-      CHARACTER*(*) CFUNC
-      EXTERNAL CFUNC
-      CALL FOO(CFUNC)
-      END
- 
- It isn't clear whether the standard considers this conforming.
- 
- 
- File: g77.info,  Node: No Passing Dummy Assumed-length,  Next: No Pathological Implied-DO,  Prev: No Passing External Assumed-length,  Up: Standard Support
- 
- No Passing Dummy Assumed-length
- -------------------------------
- 
-    `g77' disallows passing of a dummy procedure as an actual argument
- if the procedure's type is declared `CHARACTER*(*)'.
- 
-      SUBROUTINE BAR(CFUNC)
-      CHARACTER*(*) CFUNC
-      EXTERNAL CFUNC
-      CALL FOO(CFUNC)
-      END
- 
- It isn't clear whether the standard considers this conforming.
- 
- 
- File: g77.info,  Node: No Pathological Implied-DO,  Next: No Useless Implied-DO,  Prev: No Passing Dummy Assumed-length,  Up: Standard Support
- 
- No Pathological Implied-DO
- --------------------------
- 
-    The `DO' variable for an implied-`DO' construct in a `DATA'
- statement may not be used as the `DO' variable for an outer
- implied-`DO' construct.  For example, this fragment is disallowed by
- `g77':
- 
-      DATA ((A(I, I), I= 1, 10), I= 1, 10) /.../
- 
- This also is disallowed by Fortran 90, as it offers no additional
- capabilities and would have a variety of possible meanings.
- 
-    Note that it is _very_ unlikely that any production Fortran code
- tries to use this unsupported construct.
- 
- 
- File: g77.info,  Node: No Useless Implied-DO,  Prev: No Pathological Implied-DO,  Up: Standard Support
- 
- No Useless Implied-DO
- ---------------------
- 
-    An array element initializer in an implied-`DO' construct in a
- `DATA' statement must contain at least one reference to the `DO'
- variables of each outer implied-`DO' construct.  For example, this
- fragment is disallowed by `g77':
- 
-      DATA (A, I= 1, 1) /1./
- 
- This also is disallowed by Fortran 90, as FORTRAN 77's more permissive
- requirements offer no additional capabilities.  However, `g77' doesn't
- necessarily diagnose all cases where this requirement is not met.
- 
-    Note that it is _very_ unlikely that any production Fortran code
- tries to use this unsupported construct.
- 
- 
- File: g77.info,  Node: Conformance,  Next: Notation Used,  Prev: Standard Support,  Up: Language
- 
- Conformance
- ===========
- 
-    (The following information augments or overrides the information in
- Section 1.4 of ANSI X3.9-1978 FORTRAN 77 in specifying the GNU Fortran
- language.  Chapter 1 of that document otherwise serves as the basis for
- the relevant aspects of GNU Fortran.)
- 
-    The definition of the GNU Fortran language is akin to that of the
- ANSI FORTRAN 77 language in that it does not generally require
- conforming implementations to diagnose cases where programs do not
- conform to the language.
- 
-    However, `g77' as a compiler is being developed in a way that is
- intended to enable it to diagnose such cases in an easy-to-understand
- manner.
- 
-    A program that conforms to the GNU Fortran language should, when
- compiled, linked, and executed using a properly installed `g77' system,
- perform as described by the GNU Fortran language definition.  Reasons
- for different behavior include, among others:
- 
-    * Use of resources (memory--heap, stack, and so on; disk space; CPU
-      time; etc.) exceeds those of the system.
- 
-    * Range and/or precision of calculations required by the program
-      exceeds that of the system.
- 
-    * Excessive reliance on behaviors that are system-dependent
-      (non-portable Fortran code).
- 
-    * Bugs in the program.
- 
-    * Bug in `g77'.
- 
-    * Bugs in the system.
- 
-    Despite these "loopholes", the availability of a clear specification
- of the language of programs submitted to `g77', as this document is
- intended to provide, is considered an important aspect of providing a
- robust, clean, predictable Fortran implementation.
- 
-    The definition of the GNU Fortran language, while having no special
- legal status, can therefore be viewed as a sort of contract, or
- agreement.  This agreement says, in essence, "if you write a program in
- this language, and run it in an environment (such as a `g77' system)
- that supports this language, the program should behave in a largely
- predictable way".
- 
- 
- File: g77.info,  Node: Notation Used,  Next: Terms and Concepts,  Prev: Conformance,  Up: Language
- 
- Notation Used in This Chapter
- =============================
- 
-    (The following information augments or overrides the information in
- Section 1.5 of ANSI X3.9-1978 FORTRAN 77 in specifying the GNU Fortran
- language.  Chapter 1 of that document otherwise serves as the basis for
- the relevant aspects of GNU Fortran.)
- 
-    In this chapter, "must" denotes a requirement, "may" denotes
- permission, and "must not" and "may not" denote prohibition.  Terms
- such as "might", "should", and "can" generally add little or nothing in
- the way of weight to the GNU Fortran language itself, but are used to
- explain or illustrate the language.
- 
-    For example:
- 
-      ``The `FROBNITZ' statement must precede all executable
-      statements in a program unit, and may not specify any dummy
-      arguments.  It may specify local or common variables and arrays.
-      Its use should be limited to portions of the program designed to
-      be non-portable and system-specific, because it might cause the
-      containing program unit to behave quite differently on different
-      systems.''
- 
-    Insofar as the GNU Fortran language is specified, the requirements
- and permissions denoted by the above sample statement are limited to
- the placement of the statement and the kinds of things it may specify.
- The rest of the statement--the content regarding non-portable portions
- of the program and the differing behavior of program units containing
- the `FROBNITZ' statement--does not pertain the GNU Fortran language
- itself.  That content offers advice and warnings about the `FROBNITZ'
- statement.
- 
-    _Remember:_ The GNU Fortran language definition specifies both what
- constitutes a valid GNU Fortran program and how, given such a program,
- a valid GNU Fortran implementation is to interpret that program.
- 
-    It is _not_ incumbent upon a valid GNU Fortran implementation to
- behave in any particular way, any consistent way, or any predictable
- way when it is asked to interpret input that is _not_ a valid GNU
- Fortran program.
- 
-    Such input is said to have "undefined" behavior when interpreted by
- a valid GNU Fortran implementation, though an implementation may choose
- to specify behaviors for some cases of inputs that are not valid GNU
- Fortran programs.
- 
-    Other notation used herein is that of the GNU texinfo format, which
- is used to generate printed hardcopy, on-line hypertext (Info), and
- on-line HTML versions, all from a single source document.  This
- notation is used as follows:
- 
-    * Keywords defined by the GNU Fortran language are shown in
-      uppercase, as in: `COMMON', `INTEGER', and `BLOCK DATA'.
- 
-      Note that, in practice, many Fortran programs are written in
-      lowercase--uppercase is used in this manual as a means to readily
-      distinguish keywords and sample Fortran-related text from the
-      prose in this document.
- 
-    * Portions of actual sample program, input, or output text look like
-      this: `Actual program text'.
- 
-      Generally, uppercase is used for all Fortran-specific and
-      Fortran-related text, though this does not always include literal
-      text within Fortran code.
- 
-      For example: `PRINT *, 'My name is Bob''.
- 
-    * A metasyntactic variable--that is, a name used in this document to
-      serve as a placeholder for whatever text is used by the user or
-      programmer--appears as shown in the following example:
- 
-      "The `INTEGER IVAR' statement specifies that IVAR is a variable or
-      array of type `INTEGER'."
- 
-      In the above example, any valid text may be substituted for the
-      metasyntactic variable IVAR to make the statement apply to a
-      specific instance, as long as the same text is substituted for
-      _both_ occurrences of IVAR.
- 
-    * Ellipses ("...") are used to indicate further text that is either
-      unimportant or expanded upon further, elsewhere.
- 
-    * Names of data types are in the style of Fortran 90, in most cases.
- 
-      *Note Kind Notation::, for information on the relationship between
-      Fortran 90 nomenclature (such as `INTEGER(KIND=1)') and the more
-      traditional, less portably concise nomenclature (such as
-      `INTEGER*4').
- 
- 
- File: g77.info,  Node: Terms and Concepts,  Next: Characters Lines Sequence,  Prev: Notation Used,  Up: Language
- 
- Fortran Terms and Concepts
- ==========================
- 
-    (The following information augments or overrides the information in
- Chapter 2 of ANSI X3.9-1978 FORTRAN 77 in specifying the GNU Fortran
- language.  Chapter 2 of that document otherwise serves as the basis for
- the relevant aspects of GNU Fortran.)
- 
- * Menu:
- 
- * Syntactic Items::
- * Statements Comments Lines::
- * Scope of Names and Labels::
- 
- 
- File: g77.info,  Node: Syntactic Items,  Next: Statements Comments Lines,  Up: Terms and Concepts
- 
- Syntactic Items
- ---------------
- 
-    (Corresponds to Section 2.2 of ANSI X3.9-1978 FORTRAN 77.)
- 
-    In GNU Fortran, a symbolic name is at least one character long, and
- has no arbitrary upper limit on length.  However, names of entities
- requiring external linkage (such as external functions, external
- subroutines, and `COMMON' areas) might be restricted to some arbitrary
- length by the system.  Such a restriction is no more constrained than
- that of one through six characters.
- 
-    Underscores (`_') are accepted in symbol names after the first
- character (which must be a letter).
- 
- 
- File: g77.info,  Node: Statements Comments Lines,  Next: Scope of Names and Labels,  Prev: Syntactic Items,  Up: Terms and Concepts
- 
- Statements, Comments, and Lines
- -------------------------------
- 
-    (Corresponds to Section 2.3 of ANSI X3.9-1978 FORTRAN 77.)
- 
-    Use of an exclamation point (`!') to begin a trailing comment (a
- comment that extends to the end of the same source line) is permitted
- under the following conditions:
- 
-    * The exclamation point does not appear in column 6.  Otherwise, it
-      is treated as an indicator of a continuation line.
- 
-    * The exclamation point appears outside a character or Hollerith
-      constant.  Otherwise, the exclamation point is considered part of
-      the constant.
- 
-    * The exclamation point appears to the left of any other possible
-      trailing comment.  That is, a trailing comment may contain
-      exclamation points in their commentary text.
- 
-    Use of a semicolon (`;') as a statement separator is permitted under
- the following conditions:
- 
-    * The semicolon appears outside a character or Hollerith constant.
-      Otherwise, the semicolon is considered part of the constant.
- 
-    * The semicolon appears to the left of a trailing comment.
-      Otherwise, the semicolon is considered part of that comment.
- 
-    * Neither a logical `IF' statement nor a non-construct `WHERE'
-      statement (a Fortran 90 feature) may be followed (in the same,
-      possibly continued, line) by a semicolon used as a statement
-      separator.
- 
-      This restriction avoids the confusion that can result when reading
-      a line such as:
- 
-           IF (VALIDP) CALL FOO; CALL BAR
- 
-      Some readers might think the `CALL BAR' is executed only if
-      `VALIDP' is `.TRUE.', while others might assume its execution is
-      unconditional.
- 
-      (At present, `g77' does not diagnose code that violates this
-      restriction.)
- 
- 
- File: g77.info,  Node: Scope of Names and Labels,  Prev: Statements Comments Lines,  Up: Terms and Concepts
- 
- Scope of Symbolic Names and Statement Labels
- --------------------------------------------
- 
-    (Corresponds to Section 2.9 of ANSI X3.9-1978 FORTRAN 77.)
- 
-    Included in the list of entities that have a scope of a program unit
- are construct names (a Fortran 90 feature).  *Note Construct Names::,
- for more information.
- 
- 
- File: g77.info,  Node: Characters Lines Sequence,  Next: Data Types and Constants,  Prev: Terms and Concepts,  Up: Language
- 
- Characters, Lines, and Execution Sequence
- =========================================
- 
-    (The following information augments or overrides the information in
- Chapter 3 of ANSI X3.9-1978 FORTRAN 77 in specifying the GNU Fortran
- language.  Chapter 3 of that document otherwise serves as the basis for
- the relevant aspects of GNU Fortran.)
- 
- * Menu:
- 
- * Character Set::
- * Lines::
- * Continuation Line::
- * Statements::
- * Statement Labels::
- * Order::
- * INCLUDE::
- * Cpp-style directives::
- 
- 
- File: g77.info,  Node: Character Set,  Next: Lines,  Up: Characters Lines Sequence
- 
- GNU Fortran Character Set
- -------------------------
- 
-    (Corresponds to Section 3.1 of ANSI X3.9-1978 FORTRAN 77.)
- 
-    Letters include uppercase letters (the twenty-six characters of the
- English alphabet) and lowercase letters (their lowercase equivalent).
- Generally, lowercase letters may be used in place of uppercase letters,
- though in character and Hollerith constants, they are distinct.
- 
-    Special characters include:
- 
-    * Semicolon (`;')
- 
-    * Exclamation point (`!')
- 
-    * Double quote (`"')
- 
-    * Backslash (`\')
- 
-    * Question mark (`?')
- 
-    * Hash mark (`#')
- 
-    * Ampersand (`&')
- 
-    * Percent sign (`%')
- 
-    * Underscore (`_')
- 
-    * Open angle (`<')
- 
-    * Close angle (`>')
- 
-    * The FORTRAN 77 special characters (<SPC>, `=', `+', `-', `*', `/',
-      `(', `)', `,', `.', `$', `'', and `:')
- 
-    Note that this document refers to <SPC> as "space", while X3.9-1978
- FORTRAN 77 refers to it as "blank".
- 
--- 0 ----
diff -Nrc3pad gcc-3.2.3/gcc/f/g77.info-6 gcc-3.3/gcc/f/g77.info-6
*** gcc-3.2.3/gcc/f/g77.info-6	2003-04-22 07:07:23.000000000 +0000
--- gcc-3.3/gcc/f/g77.info-6	1970-01-01 00:00:00.000000000 +0000
***************
*** 1,1203 ****
- This is g77.info, produced by makeinfo version 4.5 from g77.texi.
- 
- INFO-DIR-SECTION Programming
- START-INFO-DIR-ENTRY
- * g77: (g77).                  The GNU Fortran compiler.
- END-INFO-DIR-ENTRY
-    This file documents the use and the internals of the GNU Fortran
- (`g77') compiler.  It corresponds to the GCC-3.2.3 version of `g77'.
- 
-    Published by the Free Software Foundation 59 Temple Place - Suite 330
- Boston, MA 02111-1307 USA
- 
-    Copyright (C) 1995,1996,1997,1998,1999,2000,2001,2002 Free Software
- Foundation, Inc.
- 
-    Permission is granted to copy, distribute and/or modify this document
- under the terms of the GNU Free Documentation License, Version 1.1 or
- any later version published by the Free Software Foundation; with the
- Invariant Sections being "GNU General Public License" and "Funding Free
- Software", the Front-Cover texts being (a) (see below), and with the
- Back-Cover Texts being (b) (see below).  A copy of the license is
- included in the section entitled "GNU Free Documentation License".
- 
-    (a) The FSF's Front-Cover Text is:
- 
-    A GNU Manual
- 
-    (b) The FSF's Back-Cover Text is:
- 
-    You have freedom to copy and modify this GNU Manual, like GNU
- software.  Copies published by the Free Software Foundation raise
- funds for GNU development.
- 
-    Contributed by James Craig Burley (<craig@jcb-sc.com>).  Inspired by
- a first pass at translating `g77-0.5.16/f/DOC' that was contributed to
- Craig by David Ronis (<ronis@onsager.chem.mcgill.ca>).
- 
- 
- File: g77.info,  Node: Lines,  Next: Continuation Line,  Prev: Character Set,  Up: Characters Lines Sequence
- 
- Lines
- -----
- 
-    (Corresponds to Section 3.2 of ANSI X3.9-1978 FORTRAN 77.)
- 
-    The way a Fortran compiler views source files depends entirely on the
- implementation choices made for the compiler, since those choices are
- explicitly left to the implementation by the published Fortran
- standards.
- 
-    The GNU Fortran language mandates a view applicable to UNIX-like
- text files--files that are made up of an arbitrary number of lines,
- each with an arbitrary number of characters (sometimes called
- stream-based files).
- 
-    This view does not apply to types of files that are specified as
- having a particular number of characters on every single line (sometimes
- referred to as record-based files).
- 
-    Because a "line in a program unit is a sequence of 72 characters",
- to quote X3.9-1978, the GNU Fortran language specifies that a
- stream-based text file is translated to GNU Fortran lines as follows:
- 
-    * A newline in the file is the character that represents the end of
-      a line of text to the underlying system.  For example, on
-      ASCII-based systems, a newline is the <NL> character, which has
-      ASCII value 10 (decimal).
- 
-    * Each newline in the file serves to end the line of text that
-      precedes it (and that does not contain a newline).
- 
-    * The end-of-file marker (`EOF') also serves to end the line of text
-      that precedes it (and that does not contain a newline).
- 
-    * Any line of text that is shorter than 72 characters is padded to
-      that length with spaces (called "blanks" in the standard).
- 
-    * Any line of text that is longer than 72 characters is truncated to
-      that length, but the truncated remainder must consist entirely of
-      spaces.
- 
-    * Characters other than newline and the GNU Fortran character set
-      are invalid.
- 
-    For the purposes of the remainder of this description of the GNU
- Fortran language, the translation described above has already taken
- place, unless otherwise specified.
- 
-    The result of the above translation is that the source file appears,
- in terms of the remainder of this description of the GNU Fortran
- language, as if it had an arbitrary number of 72-character lines, each
- character being among the GNU Fortran character set.
- 
-    For example, if the source file itself has two newlines in a row,
- the second newline becomes, after the above translation, a single line
- containing 72 spaces.
- 
- 
- File: g77.info,  Node: Continuation Line,  Next: Statements,  Prev: Lines,  Up: Characters Lines Sequence
- 
- Continuation Line
- -----------------
- 
-    (Corresponds to Section 3.2.3 of ANSI X3.9-1978 FORTRAN 77.)
- 
-    A continuation line is any line that both
- 
-    * Contains a continuation character, and
- 
-    * Contains only spaces in columns 1 through 5
- 
-    A continuation character is any character of the GNU Fortran
- character set other than space (<SPC>) or zero (`0') in column 6, or a
- digit (`0' through `9') in column 7 through 72 of a line that has only
- spaces to the left of that digit.
- 
-    The continuation character is ignored as far as the content of the
- statement is concerned.
- 
-    The GNU Fortran language places no limit on the number of
- continuation lines in a statement.  In practice, the limit depends on a
- variety of factors, such as available memory, statement content, and so
- on, but no GNU Fortran system may impose an arbitrary limit.
- 
- 
- File: g77.info,  Node: Statements,  Next: Statement Labels,  Prev: Continuation Line,  Up: Characters Lines Sequence
- 
- Statements
- ----------
- 
-    (Corresponds to Section 3.3 of ANSI X3.9-1978 FORTRAN 77.)
- 
-    Statements may be written using an arbitrary number of continuation
- lines.
- 
-    Statements may be separated using the semicolon (`;'), except that
- the logical `IF' and non-construct `WHERE' statements may not be
- separated from subsequent statements using only a semicolon as
- statement separator.
- 
-    The `END PROGRAM', `END SUBROUTINE', `END FUNCTION', and `END BLOCK
- DATA' statements are alternatives to the `END' statement.  These
- alternatives may be written as normal statements--they are not subject
- to the restrictions of the `END' statement.
- 
-    However, no statement other than `END' may have an initial line that
- appears to be an `END' statement--even `END PROGRAM', for example, must
- not be written as:
- 
-            END
-           &PROGRAM
- 
- 
- File: g77.info,  Node: Statement Labels,  Next: Order,  Prev: Statements,  Up: Characters Lines Sequence
- 
- Statement Labels
- ----------------
- 
-    (Corresponds to Section 3.4 of ANSI X3.9-1978 FORTRAN 77.)
- 
-    A statement separated from its predecessor via a semicolon may be
- labeled as follows:
- 
-    * The semicolon is followed by the label for the statement, which in
-      turn follows the label.
- 
-    * The label must be no more than five digits in length.
- 
-    * The first digit of the label for the statement is not the first
-      non-space character on a line.  Otherwise, that character is
-      treated as a continuation character.
- 
-    A statement may have only one label defined for it.
- 
- 
- File: g77.info,  Node: Order,  Next: INCLUDE,  Prev: Statement Labels,  Up: Characters Lines Sequence
- 
- Order of Statements and Lines
- -----------------------------
- 
-    (Corresponds to Section 3.5 of ANSI X3.9-1978 FORTRAN 77.)
- 
-    Generally, `DATA' statements may precede executable statements.
- However, specification statements pertaining to any entities
- initialized by a `DATA' statement must precede that `DATA' statement.
- For example, after `DATA I/1/', `INTEGER I' is not permitted, but
- `INTEGER J' is permitted.
- 
-    The last line of a program unit may be an `END' statement, or may be:
- 
-    * An `END PROGRAM' statement, if the program unit is a main program.
- 
-    * An `END SUBROUTINE' statement, if the program unit is a subroutine.
- 
-    * An `END FUNCTION' statement, if the program unit is a function.
- 
-    * An `END BLOCK DATA' statement, if the program unit is a block data.
- 
- 
- File: g77.info,  Node: INCLUDE,  Next: Cpp-style directives,  Prev: Order,  Up: Characters Lines Sequence
- 
- Including Source Text
- ---------------------
- 
-    Additional source text may be included in the processing of the
- source file via the `INCLUDE' directive:
- 
-      INCLUDE FILENAME
- 
- The source text to be included is identified by FILENAME, which is a
- literal GNU Fortran character constant.  The meaning and interpretation
- of FILENAME depends on the implementation, but typically is a filename.
- 
-    (`g77' treats it as a filename that it searches for in the current
- directory and/or directories specified via the `-I' command-line
- option.)
- 
-    The effect of the `INCLUDE' directive is as if the included text
- directly replaced the directive in the source file prior to
- interpretation of the program.  Included text may itself use `INCLUDE'.
- The depth of nested `INCLUDE' references depends on the implementation,
- but typically is a positive integer.
- 
-    This virtual replacement treats the statements and `INCLUDE'
- directives in the included text as syntactically distinct from those in
- the including text.
- 
-    Therefore, the first non-comment line of the included text must not
- be a continuation line.  The included text must therefore have, after
- the non-comment lines, either an initial line (statement), an `INCLUDE'
- directive, or nothing (the end of the included text).
- 
-    Similarly, the including text may end the `INCLUDE' directive with a
- semicolon or the end of the line, but it cannot follow an `INCLUDE'
- directive at the end of its line with a continuation line.  Thus, the
- last statement in an included text may not be continued.
- 
-    Any statements between two `INCLUDE' directives on the same line are
- treated as if they appeared in between the respective included texts.
- For example:
- 
-      INCLUDE 'A'; PRINT *, 'B'; INCLUDE 'C'; END PROGRAM
- 
- If the text included by `INCLUDE 'A'' constitutes a `PRINT *, 'A''
- statement and the text included by `INCLUDE 'C'' constitutes a `PRINT
- *, 'C'' statement, then the output of the above sample program would be
- 
-      A
-      B
-      C
- 
- (with suitable allowances for how an implementation defines its
- handling of output).
- 
-    Included text must not include itself directly or indirectly,
- regardless of whether the FILENAME used to reference the text is the
- same.
- 
-    Note that `INCLUDE' is _not_ a statement.  As such, it is neither a
- non-executable or executable statement.  However, if the text it
- includes constitutes one or more executable statements, then the
- placement of `INCLUDE' is subject to effectively the same restrictions
- as those on executable statements.
- 
-    An `INCLUDE' directive may be continued across multiple lines as if
- it were a statement.  This permits long names to be used for FILENAME.
- 
- 
- File: g77.info,  Node: Cpp-style directives,  Prev: INCLUDE,  Up: Characters Lines Sequence
- 
- Cpp-style directives
- --------------------
- 
-    `cpp' output-style `#' directives (*note C Preprocessor Output:
- (cpp)C Preprocessor Output.)  are recognized by the compiler even when
- the preprocessor isn't run on the input (as it is when compiling `.F'
- files).  (Note the distinction between these `cpp' `#' _output_
- directives and `#line' _input_ directives.)
- 
- 
- File: g77.info,  Node: Data Types and Constants,  Next: Expressions,  Prev: Characters Lines Sequence,  Up: Language
- 
- Data Types and Constants
- ========================
- 
-    (The following information augments or overrides the information in
- Chapter 4 of ANSI X3.9-1978 FORTRAN 77 in specifying the GNU Fortran
- language.  Chapter 4 of that document otherwise serves as the basis for
- the relevant aspects of GNU Fortran.)
- 
-    To more concisely express the appropriate types for entities, this
- document uses the more concise Fortran 90 nomenclature such as
- `INTEGER(KIND=1)' instead of the more traditional, but less portably
- concise, byte-size-based nomenclature such as `INTEGER*4', wherever
- reasonable.
- 
-    When referring to generic types--in contexts where the specific
- precision and range of a type are not important--this document uses the
- generic type names `INTEGER', `LOGICAL', `REAL', `COMPLEX', and
- `CHARACTER'.
- 
-    In some cases, the context requires specification of a particular
- type.  This document uses the `KIND=' notation to accomplish this
- throughout, sometimes supplying the more traditional notation for
- clarification, though the traditional notation might not work the same
- way on all GNU Fortran implementations.
- 
-    Use of `KIND=' makes this document more concise because `g77' is
- able to define values for `KIND=' that have the same meanings on all
- systems, due to the way the Fortran 90 standard specifies these values
- are to be used.
- 
-    (In particular, that standard permits an implementation to
- arbitrarily assign nonnegative values.  There are four distinct sets of
- assignments: one to the `CHARACTER' type; one to the `INTEGER' type;
- one to the `LOGICAL' type; and the fourth to both the `REAL' and
- `COMPLEX' types.  Implementations are free to assign these values in
- any order, leave gaps in the ordering of assignments, and assign more
- than one value to a representation.)
- 
-    This makes `KIND=' values superior to the values used in
- non-standard statements such as `INTEGER*4', because the meanings of
- the values in those statements vary from machine to machine, compiler
- to compiler, even operating system to operating system.
- 
-    However, use of `KIND=' is _not_ generally recommended when writing
- portable code (unless, for example, the code is going to be compiled
- only via `g77', which is a widely ported compiler).  GNU Fortran does
- not yet have adequate language constructs to permit use of `KIND=' in a
- fashion that would make the code portable to Fortran 90
- implementations; and, this construct is known to _not_ be accepted by
- many popular FORTRAN 77 implementations, so it cannot be used in code
- that is to be ported to those.
- 
-    The distinction here is that this document is able to use specific
- values for `KIND=' to concisely document the types of various
- operations and operands.
- 
-    A Fortran program should use the FORTRAN 77 designations for the
- appropriate GNU Fortran types--such as `INTEGER' for `INTEGER(KIND=1)',
- `REAL' for `REAL(KIND=1)', and `DOUBLE COMPLEX' for
- `COMPLEX(KIND=2)'--and, where no such designations exist, make use of
- appropriate techniques (preprocessor macros, parameters, and so on) to
- specify the types in a fashion that may be easily adjusted to suit each
- particular implementation to which the program is ported.  (These types
- generally won't need to be adjusted for ports of `g77'.)
- 
-    Further details regarding GNU Fortran data types and constants are
- provided below.
- 
- * Menu:
- 
- * Types::
- * Constants::
- * Integer Type::
- * Character Type::
- 
- 
- File: g77.info,  Node: Types,  Next: Constants,  Up: Data Types and Constants
- 
- Data Types
- ----------
- 
-    (Corresponds to Section 4.1 of ANSI X3.9-1978 FORTRAN 77.)
- 
-    GNU Fortran supports these types:
- 
-   1. Integer (generic type `INTEGER')
- 
-   2. Real (generic type `REAL')
- 
-   3. Double precision
- 
-   4. Complex (generic type `COMPLEX')
- 
-   5. Logical (generic type `LOGICAL')
- 
-   6. Character (generic type `CHARACTER')
- 
-   7. Double Complex
- 
-    (The types numbered 1 through 6 above are standard FORTRAN 77 types.)
- 
-    The generic types shown above are referred to in this document using
- only their generic type names.  Such references usually indicate that
- any specific type (kind) of that generic type is valid.
- 
-    For example, a context described in this document as accepting the
- `COMPLEX' type also is likely to accept the `DOUBLE COMPLEX' type.
- 
-    The GNU Fortran language supports three ways to specify a specific
- kind of a generic type.
- 
- * Menu:
- 
- * Double Notation::  As in `DOUBLE COMPLEX'.
- * Star Notation::    As in `INTEGER*4'.
- * Kind Notation::    As in `INTEGER(KIND=1)'.
- 
- 
- File: g77.info,  Node: Double Notation,  Next: Star Notation,  Up: Types
- 
- Double Notation
- ...............
- 
-    The GNU Fortran language supports two uses of the keyword `DOUBLE'
- to specify a specific kind of type:
- 
-    * `DOUBLE PRECISION', equivalent to `REAL(KIND=2)'
- 
-    * `DOUBLE COMPLEX', equivalent to `COMPLEX(KIND=2)'
- 
-    Use one of the above forms where a type name is valid.
- 
-    While use of this notation is popular, it doesn't scale well in a
- language or dialect rich in intrinsic types, as is the case for the GNU
- Fortran language (especially planned future versions of it).
- 
-    After all, one rarely sees type names such as `DOUBLE INTEGER',
- `QUADRUPLE REAL', or `QUARTER INTEGER'.  Instead, `INTEGER*8',
- `REAL*16', and `INTEGER*1' often are substituted for these,
- respectively, even though they do not always have the same meanings on
- all systems.  (And, the fact that `DOUBLE REAL' does not exist as such
- is an inconsistency.)
- 
-    Therefore, this document uses "double notation" only on occasion for
- the benefit of those readers who are accustomed to it.
- 
- 
- File: g77.info,  Node: Star Notation,  Next: Kind Notation,  Prev: Double Notation,  Up: Types
- 
- Star Notation
- .............
- 
-    The following notation specifies the storage size for a type:
- 
-      GENERIC-TYPE*N
- 
- GENERIC-TYPE must be a generic type--one of `INTEGER', `REAL',
- `COMPLEX', `LOGICAL', or `CHARACTER'.  N must be one or more digits
- comprising a decimal integer number greater than zero.
- 
-    Use the above form where a type name is valid.
- 
-    The `*N' notation specifies that the amount of storage occupied by
- variables and array elements of that type is N times the storage
- occupied by a `CHARACTER*1' variable.
- 
-    This notation might indicate a different degree of precision and/or
- range for such variables and array elements, and the functions that
- return values of types using this notation.  It does not limit the
- precision or range of values of that type in any particular way--use
- explicit code to do that.
- 
-    Further, the GNU Fortran language requires no particular values for
- N to be supported by an implementation via the `*N' notation.  `g77'
- supports `INTEGER*1' (as `INTEGER(KIND=3)') on all systems, for example,
- but not all implementations are required to do so, and `g77' is known
- to not support `REAL*1' on most (or all) systems.
- 
-    As a result, except for GENERIC-TYPE of `CHARACTER', uses of this
- notation should be limited to isolated portions of a program that are
- intended to handle system-specific tasks and are expected to be
- non-portable.
- 
-    (Standard FORTRAN 77 supports the `*N' notation for only
- `CHARACTER', where it signifies not only the amount of storage
- occupied, but the number of characters in entities of that type.
- However, almost all Fortran compilers have supported this notation for
- generic types, though with a variety of meanings for N.)
- 
-    Specifications of types using the `*N' notation always are
- interpreted as specifications of the appropriate types described in
- this document using the `KIND=N' notation, described below.
- 
-    While use of this notation is popular, it doesn't serve well in the
- context of a widely portable dialect of Fortran, such as the GNU
- Fortran language.
- 
-    For example, even on one particular machine, two or more popular
- Fortran compilers might well disagree on the size of a type declared
- `INTEGER*2' or `REAL*16'.  Certainly there is known to be disagreement
- over such things among Fortran compilers on _different_ systems.
- 
-    Further, this notation offers no elegant way to specify sizes that
- are not even multiples of the "byte size" typically designated by
- `INTEGER*1'.  Use of "absurd" values (such as `INTEGER*1000') would
- certainly be possible, but would perhaps be stretching the original
- intent of this notation beyond the breaking point in terms of
- widespread readability of documentation and code making use of it.
- 
-    Therefore, this document uses "star notation" only on occasion for
- the benefit of those readers who are accustomed to it.
- 
- 
- File: g77.info,  Node: Kind Notation,  Prev: Star Notation,  Up: Types
- 
- Kind Notation
- .............
- 
-    The following notation specifies the kind-type selector of a type:
- 
-      GENERIC-TYPE(KIND=N)
- 
- Use the above form where a type name is valid.
- 
-    GENERIC-TYPE must be a generic type--one of `INTEGER', `REAL',
- `COMPLEX', `LOGICAL', or `CHARACTER'.  N must be an integer
- initialization expression that is a positive, nonzero value.
- 
-    Programmers are discouraged from writing these values directly into
- their code.  Future versions of the GNU Fortran language will offer
- facilities that will make the writing of code portable to `g77' _and_
- Fortran 90 implementations simpler.
- 
-    However, writing code that ports to existing FORTRAN 77
- implementations depends on avoiding the `KIND=' construct.
- 
-    The `KIND=' construct is thus useful in the context of GNU Fortran
- for two reasons:
- 
-    * It provides a means to specify a type in a fashion that is
-      portable across all GNU Fortran implementations (though not other
-      FORTRAN 77 and Fortran 90 implementations).
- 
-    * It provides a sort of Rosetta stone for this document to use to
-      concisely describe the types of various operations and operands.
- 
-    The values of N in the GNU Fortran language are assigned using a
- scheme that:
- 
-    * Attempts to maximize the ability of readers of this document to
-      quickly familiarize themselves with assignments for popular types
- 
-    * Provides a unique value for each specific desired meaning
- 
-    * Provides a means to automatically assign new values so they have a
-      "natural" relationship to existing values, if appropriate, or, if
-      no such relationship exists, will not interfere with future values
-      assigned on the basis of such relationships
- 
-    * Avoids using values that are similar to values used in the
-      existing, popular `*N' notation, to prevent readers from expecting
-      that these implied correspondences work on all GNU Fortran
-      implementations
- 
-    The assignment system accomplishes this by assigning to each
- "fundamental meaning" of a specific type a unique prime number.
- Combinations of fundamental meanings--for example, a type that is two
- times the size of some other type--are assigned values of N that are
- the products of the values for those fundamental meanings.
- 
-    A prime value of N is never given more than one fundamental meaning,
- to avoid situations where some code or system cannot reasonably provide
- those meanings in the form of a single type.
- 
-    The values of N assigned so far are:
- 
- `KIND=0'
-      This value is reserved for future use.
- 
-      The planned future use is for this value to designate, explicitly,
-      context-sensitive kind-type selection.  For example, the
-      expression `1D0 * 0.1_0' would be equivalent to `1D0 * 0.1D0'.
- 
- `KIND=1'
-      This corresponds to the default types for `REAL', `INTEGER',
-      `LOGICAL', `COMPLEX', and `CHARACTER', as appropriate.
- 
-      These are the "default" types described in the Fortran 90 standard,
-      though that standard does not assign any particular `KIND=' value
-      to these types.
- 
-      (Typically, these are `REAL*4', `INTEGER*4', `LOGICAL*4', and
-      `COMPLEX*8'.)
- 
- `KIND=2'
-      This corresponds to types that occupy twice as much storage as the
-      default types.  `REAL(KIND=2)' is `DOUBLE PRECISION' (typically
-      `REAL*8'), `COMPLEX(KIND=2)' is `DOUBLE COMPLEX' (typically
-      `COMPLEX*16'),
- 
-      These are the "double precision" types described in the Fortran 90
-      standard, though that standard does not assign any particular
-      `KIND=' value to these types.
- 
-      N of 4 thus corresponds to types that occupy four times as much
-      storage as the default types, N of 8 to types that occupy eight
-      times as much storage, and so on.
- 
-      The `INTEGER(KIND=2)' and `LOGICAL(KIND=2)' types are not
-      necessarily supported by every GNU Fortran implementation.
- 
- `KIND=3'
-      This corresponds to types that occupy as much storage as the
-      default `CHARACTER' type, which is the same effective type as
-      `CHARACTER(KIND=1)' (making that type effectively the same as
-      `CHARACTER(KIND=3)').
- 
-      (Typically, these are `INTEGER*1' and `LOGICAL*1'.)
- 
-      N of 6 thus corresponds to types that occupy twice as much storage
-      as the N=3 types, N of 12 to types that occupy four times as much
-      storage, and so on.
- 
-      These are not necessarily supported by every GNU Fortran
-      implementation.
- 
- `KIND=5'
-      This corresponds to types that occupy half the storage as the
-      default (N=1) types.
- 
-      (Typically, these are `INTEGER*2' and `LOGICAL*2'.)
- 
-      N of 25 thus corresponds to types that occupy one-quarter as much
-      storage as the default types.
- 
-      These are not necessarily supported by every GNU Fortran
-      implementation.
- 
- `KIND=7'
-      This is valid only as `INTEGER(KIND=7)' and denotes the `INTEGER'
-      type that has the smallest storage size that holds a pointer on
-      the system.
- 
-      A pointer representable by this type is capable of uniquely
-      addressing a `CHARACTER*1' variable, array, array element, or
-      substring.
- 
-      (Typically this is equivalent to `INTEGER*4' or, on 64-bit
-      systems, `INTEGER*8'.  In a compatible C implementation, it
-      typically would be the same size and semantics of the C type `void
-      *'.)
- 
-    Note that these are _proposed_ correspondences and might change in
- future versions of `g77'--avoid writing code depending on them while
- `g77', and therefore the GNU Fortran language it defines, is in beta
- testing.
- 
-    Values not specified in the above list are reserved to future
- versions of the GNU Fortran language.
- 
-    Implementation-dependent meanings will be assigned new, unique prime
- numbers so as to not interfere with other implementation-dependent
- meanings, and offer the possibility of increasing the portability of
- code depending on such types by offering support for them in other GNU
- Fortran implementations.
- 
-    Other meanings that might be given unique values are:
- 
-    * Types that make use of only half their storage size for
-      representing precision and range.
- 
-      For example, some compilers offer options that cause `INTEGER'
-      types to occupy the amount of storage that would be needed for
-      `INTEGER(KIND=2)' types, but the range remains that of
-      `INTEGER(KIND=1)'.
- 
-    * The IEEE single floating-point type.
- 
-    * Types with a specific bit pattern (endianness), such as the
-      little-endian form of `INTEGER(KIND=1)'.  These could permit,
-      conceptually, use of portable code and implementations on data
-      files written by existing systems.
- 
-    Future _prime_ numbers should be given meanings in as incremental a
- fashion as possible, to allow for flexibility and expressiveness in
- combining types.
- 
-    For example, instead of defining a prime number for little-endian
- IEEE doubles, one prime number might be assigned the meaning
- "little-endian", another the meaning "IEEE double", and the value of N
- for a little-endian IEEE double would thus naturally be the product of
- those two respective assigned values.  (It could even be reasonable to
- have IEEE values result from the products of prime values denoting
- exponent and fraction sizes and meanings, hidden bit usage,
- availability and representations of special values such as subnormals,
- infinities, and Not-A-Numbers (NaNs), and so on.)
- 
-    This assignment mechanism, while not inherently required for future
- versions of the GNU Fortran language, is worth using because it could
- ease management of the "space" of supported types much easier in the
- long run.
- 
-    The above approach suggests a mechanism for specifying inheritance
- of intrinsic (built-in) types for an entire, widely portable product
- line.  It is certainly reasonable that, unlike programmers of other
- languages offering inheritance mechanisms that employ verbose names for
- classes and subclasses, along with graphical browsers to elucidate the
- relationships, Fortran programmers would employ a mechanism that works
- by multiplying prime numbers together and finding the prime factors of
- such products.
- 
-    Most of the advantages for the above scheme have been explained
- above.  One disadvantage is that it could lead to the defining, by the
- GNU Fortran language, of some fairly large prime numbers.  This could
- lead to the GNU Fortran language being declared "munitions" by the
- United States Department of Defense.
- 
- 
- File: g77.info,  Node: Constants,  Next: Integer Type,  Prev: Types,  Up: Data Types and Constants
- 
- Constants
- ---------
- 
-    (Corresponds to Section 4.2 of ANSI X3.9-1978 FORTRAN 77.)
- 
-    A "typeless constant" has one of the following forms:
- 
-      'BINARY-DIGITS'B
-      'OCTAL-DIGITS'O
-      'HEXADECIMAL-DIGITS'Z
-      'HEXADECIMAL-DIGITS'X
- 
- BINARY-DIGITS, OCTAL-DIGITS, and HEXADECIMAL-DIGITS are nonempty
- strings of characters in the set `01', `01234567', and
- `0123456789ABCDEFabcdef', respectively.  (The value for `A' (and `a')
- is 10, for `B' and `b' is 11, and so on.)
- 
-    A prefix-radix constant, such as `Z'ABCD'', can optionally be
- treated as typeless.  *Note Options Controlling Fortran Dialect:
- Fortran Dialect Options, for information on the `-ftypeless-boz' option.
- 
-    Typeless constants have values that depend on the context in which
- they are used.
- 
-    All other constants, called "typed constants", are
- interpreted--converted to internal form--according to their inherent
- type.  Thus, context is _never_ a determining factor for the type, and
- hence the interpretation, of a typed constant.  (All constants in the
- ANSI FORTRAN 77 language are typed constants.)
- 
-    For example, `1' is always type `INTEGER(KIND=1)' in GNU Fortran
- (called default INTEGER in Fortran 90), `9.435784839284958' is always
- type `REAL(KIND=1)' (even if the additional precision specified is
- lost, and even when used in a `REAL(KIND=2)' context), `1E0' is always
- type `REAL(KIND=2)', and `1D0' is always type `REAL(KIND=2)'.
- 
- 
- File: g77.info,  Node: Integer Type,  Next: Character Type,  Prev: Constants,  Up: Data Types and Constants
- 
- Integer Type
- ------------
- 
-    (Corresponds to Section 4.3 of ANSI X3.9-1978 FORTRAN 77.)
- 
-    An integer constant also may have one of the following forms:
- 
-      B'BINARY-DIGITS'
-      O'OCTAL-DIGITS'
-      Z'HEXADECIMAL-DIGITS'
-      X'HEXADECIMAL-DIGITS'
- 
- BINARY-DIGITS, OCTAL-DIGITS, and HEXADECIMAL-DIGITS are nonempty
- strings of characters in the set `01', `01234567', and
- `0123456789ABCDEFabcdef', respectively.  (The value for `A' (and `a')
- is 10, for `B' and `b' is 11, and so on.)
- 
- 
- File: g77.info,  Node: Character Type,  Prev: Integer Type,  Up: Data Types and Constants
- 
- Character Type
- --------------
- 
-    (Corresponds to Section 4.8 of ANSI X3.9-1978 FORTRAN 77.)
- 
-    A character constant may be delimited by a pair of double quotes
- (`"') instead of apostrophes.  In this case, an apostrophe within the
- constant represents a single apostrophe, while a double quote is
- represented in the source text of the constant by two consecutive double
- quotes with no intervening spaces.
- 
-    A character constant may be empty (have a length of zero).
- 
-    A character constant may include a substring specification, The
- value of such a constant is the value of the substring--for example,
- the value of `'hello'(3:5)' is the same as the value of `'llo''.
- 
- 
- File: g77.info,  Node: Expressions,  Next: Specification Statements,  Prev: Data Types and Constants,  Up: Language
- 
- Expressions
- ===========
- 
-    (The following information augments or overrides the information in
- Chapter 6 of ANSI X3.9-1978 FORTRAN 77 in specifying the GNU Fortran
- language.  Chapter 6 of that document otherwise serves as the basis for
- the relevant aspects of GNU Fortran.)
- 
- * Menu:
- 
- * %LOC()::
- 
- 
- File: g77.info,  Node: %LOC(),  Up: Expressions
- 
- The `%LOC()' Construct
- ----------------------
- 
-      %LOC(ARG)
- 
-    The `%LOC()' construct is an expression that yields the value of the
- location of its argument, ARG, in memory.  The size of the type of the
- expression depends on the system--typically, it is equivalent to either
- `INTEGER(KIND=1)' or `INTEGER(KIND=2)', though it is actually type
- `INTEGER(KIND=7)'.
- 
-    The argument to `%LOC()' must be suitable as the left-hand side of
- an assignment statement.  That is, it may not be a general expression
- involving operators such as addition, subtraction, and so on, nor may
- it be a constant.
- 
-    Use of `%LOC()' is recommended only for code that is accessing
- facilities outside of GNU Fortran, such as operating system or
- windowing facilities.  It is best to constrain such uses to isolated
- portions of a program--portions that deal specifically and exclusively
- with low-level, system-dependent facilities.  Such portions might well
- provide a portable interface for use by the program as a whole, but are
- themselves not portable, and should be thoroughly tested each time they
- are rebuilt using a new compiler or version of a compiler.
- 
-    Do not depend on `%LOC()' returning a pointer that can be safely
- used to _define_ (change) the argument.  While this might work in some
- circumstances, it is hard to predict whether it will continue to work
- when a program (that works using this unsafe behavior) is recompiled
- using different command-line options or a different version of `g77'.
- 
-    Generally, `%LOC()' is safe when used as an argument to a procedure
- that makes use of the value of the corresponding dummy argument only
- during its activation, and only when such use is restricted to
- referencing (reading) the value of the argument to `%LOC()'.
- 
-    _Implementation Note:_ Currently, `g77' passes arguments (those not
- passed using a construct such as `%VAL()') by reference or descriptor,
- depending on the type of the actual argument.  Thus, given `INTEGER I',
- `CALL FOO(I)' would seem to mean the same thing as `CALL
- FOO(%VAL(%LOC(I)))', and in fact might compile to identical code.
- 
-    However, `CALL FOO(%VAL(%LOC(I)))' emphatically means "pass, by
- value, the address of `I' in memory".  While `CALL FOO(I)' might use
- that same approach in a particular version of `g77', another version or
- compiler might choose a different implementation, such as
- copy-in/copy-out, to effect the desired behavior--and which will
- therefore not necessarily compile to the same code as would `CALL
- FOO(%VAL(%LOC(I)))' using the same version or compiler.
- 
-    *Note Debugging and Interfacing::, for detailed information on how
- this particular version of `g77' implements various constructs.
- 
- 
- File: g77.info,  Node: Specification Statements,  Next: Control Statements,  Prev: Expressions,  Up: Language
- 
- Specification Statements
- ========================
- 
-    (The following information augments or overrides the information in
- Chapter 8 of ANSI X3.9-1978 FORTRAN 77 in specifying the GNU Fortran
- language.  Chapter 8 of that document otherwise serves as the basis for
- the relevant aspects of GNU Fortran.)
- 
- * Menu:
- 
- * NAMELIST::
- * DOUBLE COMPLEX::
- 
- 
- File: g77.info,  Node: NAMELIST,  Next: DOUBLE COMPLEX,  Up: Specification Statements
- 
- `NAMELIST' Statement
- --------------------
- 
-    The `NAMELIST' statement, and related I/O constructs, are supported
- by the GNU Fortran language in essentially the same way as they are by
- `f2c'.
- 
-    This follows Fortran 90 with the restriction that on `NAMELIST'
- input, subscripts must have the form
-      SUBSCRIPT [ `:' SUBSCRIPT [ `:' STRIDE]]
-    i.e.
-      &xx x(1:3,8:10:2)=1,2,3,4,5,6/
-    is allowed, but not, say,
-      &xx x(:3,8::2)=1,2,3,4,5,6/
- 
-    As an extension of the Fortran 90 form, `$' and `$END' may be used
- in place of `&' and `/' in `NAMELIST' input, so that
-      $&xx x(1:3,8:10:2)=1,2,3,4,5,6 $end
-    could be used instead of the example above.
- 
- 
- File: g77.info,  Node: DOUBLE COMPLEX,  Prev: NAMELIST,  Up: Specification Statements
- 
- `DOUBLE COMPLEX' Statement
- --------------------------
- 
-    `DOUBLE COMPLEX' is a type-statement (and type) that specifies the
- type `COMPLEX(KIND=2)' in GNU Fortran.
- 
- 
- File: g77.info,  Node: Control Statements,  Next: Functions and Subroutines,  Prev: Specification Statements,  Up: Language
- 
- Control Statements
- ==================
- 
-    (The following information augments or overrides the information in
- Chapter 11 of ANSI X3.9-1978 FORTRAN 77 in specifying the GNU Fortran
- language.  Chapter 11 of that document otherwise serves as the basis
- for the relevant aspects of GNU Fortran.)
- 
- * Menu:
- 
- * DO WHILE::
- * END DO::
- * Construct Names::
- * CYCLE and EXIT::
- 
- 
- File: g77.info,  Node: DO WHILE,  Next: END DO,  Up: Control Statements
- 
- DO WHILE
- --------
- 
-    The `DO WHILE' statement, a feature of both the MIL-STD 1753 and
- Fortran 90 standards, is provided by the GNU Fortran language.  The
- Fortran 90 "do forever" statement comprising just `DO' is also
- supported.
- 
- 
- File: g77.info,  Node: END DO,  Next: Construct Names,  Prev: DO WHILE,  Up: Control Statements
- 
- END DO
- ------
- 
-    The `END DO' statement is provided by the GNU Fortran language.
- 
-    This statement is used in one of two ways:
- 
-    * The Fortran 90 meaning, in which it specifies the termination
-      point of a single `DO' loop started with a `DO' statement that
-      specifies no termination label.
- 
-    * The MIL-STD 1753 meaning, in which it specifies the termination
-      point of one or more `DO' loops, all of which start with a `DO'
-      statement that specify the label defined for the `END DO'
-      statement.
- 
-      This kind of `END DO' statement is merely a synonym for
-      `CONTINUE', except it is permitted only when the statement is
-      labeled and a target of one or more labeled `DO' loops.
- 
-      It is expected that this use of `END DO' will be removed from the
-      GNU Fortran language in the future, though it is likely that it
-      will long be supported by `g77' as a dialect form.
- 
- 
- File: g77.info,  Node: Construct Names,  Next: CYCLE and EXIT,  Prev: END DO,  Up: Control Statements
- 
- Construct Names
- ---------------
- 
-    The GNU Fortran language supports construct names as defined by the
- Fortran 90 standard.  These names are local to the program unit and are
- defined as follows:
- 
-      CONSTRUCT-NAME: BLOCK-STATEMENT
- 
- Here, CONSTRUCT-NAME is the construct name itself; its definition is
- connoted by the single colon (`:'); and BLOCK-STATEMENT is an `IF',
- `DO', or `SELECT CASE' statement that begins a block.
- 
-    A block that is given a construct name must also specify the same
- construct name in its termination statement:
- 
-      END BLOCK CONSTRUCT-NAME
- 
- Here, BLOCK must be `IF', `DO', or `SELECT', as appropriate.
- 
- 
- File: g77.info,  Node: CYCLE and EXIT,  Prev: Construct Names,  Up: Control Statements
- 
- The `CYCLE' and `EXIT' Statements
- ---------------------------------
- 
-    The `CYCLE' and `EXIT' statements specify that the remaining
- statements in the current iteration of a particular active (enclosing)
- `DO' loop are to be skipped.
- 
-    `CYCLE' specifies that these statements are skipped, but the `END
- DO' statement that marks the end of the `DO' loop be executed--that is,
- the next iteration, if any, is to be started.  If the statement marking
- the end of the `DO' loop is not `END DO'--in other words, if the loop
- is not a block `DO'--the `CYCLE' statement does not execute that
- statement, but does start the next iteration (if any).
- 
-    `EXIT' specifies that the loop specified by the `DO' construct is
- terminated.
- 
-    The `DO' loop affected by `CYCLE' and `EXIT' is the innermost
- enclosing `DO' loop when the following forms are used:
- 
-      CYCLE
-      EXIT
- 
-    Otherwise, the following forms specify the construct name of the
- pertinent `DO' loop:
- 
-      CYCLE CONSTRUCT-NAME
-      EXIT CONSTRUCT-NAME
- 
-    `CYCLE' and `EXIT' can be viewed as glorified `GO TO' statements.
- However, they cannot be easily thought of as `GO TO' statements in
- obscure cases involving FORTRAN 77 loops.  For example:
- 
-            DO 10 I = 1, 5
-            DO 10 J = 1, 5
-               IF (J .EQ. 5) EXIT
-            DO 10 K = 1, 5
-               IF (K .EQ. 3) CYCLE
-      10    PRINT *, 'I=', I, ' J=', J, ' K=', K
-      20    CONTINUE
- 
- In particular, neither the `EXIT' nor `CYCLE' statements above are
- equivalent to a `GO TO' statement to either label `10' or `20'.
- 
-    To understand the effect of `CYCLE' and `EXIT' in the above
- fragment, it is helpful to first translate it to its equivalent using
- only block `DO' loops:
- 
-            DO I = 1, 5
-               DO J = 1, 5
-                  IF (J .EQ. 5) EXIT
-                  DO K = 1, 5
-                     IF (K .EQ. 3) CYCLE
-      10             PRINT *, 'I=', I, ' J=', J, ' K=', K
-                  END DO
-               END DO
-            END DO
-      20    CONTINUE
- 
-    Adding new labels allows translation of `CYCLE' and `EXIT' to `GO
- TO' so they may be more easily understood by programmers accustomed to
- FORTRAN coding:
- 
-            DO I = 1, 5
-               DO J = 1, 5
-                  IF (J .EQ. 5) GOTO 18
-                  DO K = 1, 5
-                     IF (K .EQ. 3) GO TO 12
-      10             PRINT *, 'I=', I, ' J=', J, ' K=', K
-      12          END DO
-               END DO
-      18    END DO
-      20    CONTINUE
- 
- Thus, the `CYCLE' statement in the innermost loop skips over the
- `PRINT' statement as it begins the next iteration of the loop, while
- the `EXIT' statement in the middle loop ends that loop but _not_ the
- outermost loop.
- 
- 
- File: g77.info,  Node: Functions and Subroutines,  Next: Scope and Classes of Names,  Prev: Control Statements,  Up: Language
- 
- Functions and Subroutines
- =========================
- 
-    (The following information augments or overrides the information in
- Chapter 15 of ANSI X3.9-1978 FORTRAN 77 in specifying the GNU Fortran
- language.  Chapter 15 of that document otherwise serves as the basis
- for the relevant aspects of GNU Fortran.)
- 
- * Menu:
- 
- * %VAL()::
- * %REF()::
- * %DESCR()::
- * Generics and Specifics::
- * REAL() and AIMAG() of Complex::
- * CMPLX() of DOUBLE PRECISION::
- * MIL-STD 1753::
- * f77/f2c Intrinsics::
- * Table of Intrinsic Functions::
- 
- 
- File: g77.info,  Node: %VAL(),  Next: %REF(),  Up: Functions and Subroutines
- 
- The `%VAL()' Construct
- ----------------------
- 
-      %VAL(ARG)
- 
-    The `%VAL()' construct specifies that an argument, ARG, is to be
- passed by value, instead of by reference or descriptor.
- 
-    `%VAL()' is restricted to actual arguments in invocations of
- external procedures.
- 
-    Use of `%VAL()' is recommended only for code that is accessing
- facilities outside of GNU Fortran, such as operating system or
- windowing facilities.  It is best to constrain such uses to isolated
- portions of a program--portions the deal specifically and exclusively
- with low-level, system-dependent facilities.  Such portions might well
- provide a portable interface for use by the program as a whole, but are
- themselves not portable, and should be thoroughly tested each time they
- are rebuilt using a new compiler or version of a compiler.
- 
-    _Implementation Note:_ Currently, `g77' passes all arguments either
- by reference or by descriptor.
- 
-    Thus, use of `%VAL()' tends to be restricted to cases where the
- called procedure is written in a language other than Fortran that
- supports call-by-value semantics.  (C is an example of such a language.)
- 
-    *Note Procedures (SUBROUTINE and FUNCTION): Procedures, for detailed
- information on how this particular version of `g77' passes arguments to
- procedures.
- 
- 
- File: g77.info,  Node: %REF(),  Next: %DESCR(),  Prev: %VAL(),  Up: Functions and Subroutines
- 
- The `%REF()' Construct
- ----------------------
- 
-      %REF(ARG)
- 
-    The `%REF()' construct specifies that an argument, ARG, is to be
- passed by reference, instead of by value or descriptor.
- 
-    `%REF()' is restricted to actual arguments in invocations of
- external procedures.
- 
-    Use of `%REF()' is recommended only for code that is accessing
- facilities outside of GNU Fortran, such as operating system or
- windowing facilities.  It is best to constrain such uses to isolated
- portions of a program--portions the deal specifically and exclusively
- with low-level, system-dependent facilities.  Such portions might well
- provide a portable interface for use by the program as a whole, but are
- themselves not portable, and should be thoroughly tested each time they
- are rebuilt using a new compiler or version of a compiler.
- 
-    Do not depend on `%REF()' supplying a pointer to the procedure being
- invoked.  While that is a likely implementation choice, other
- implementation choices are available that preserve Fortran
- pass-by-reference semantics without passing a pointer to the argument,
- ARG.  (For example, a copy-in/copy-out implementation.)
- 
-    _Implementation Note:_ Currently, `g77' passes all arguments (other
- than variables and arrays of type `CHARACTER') by reference.  Future
- versions of, or dialects supported by, `g77' might not pass `CHARACTER'
- functions by reference.
- 
-    Thus, use of `%REF()' tends to be restricted to cases where ARG is
- type `CHARACTER' but the called procedure accesses it via a means other
- than the method used for Fortran `CHARACTER' arguments.
- 
-    *Note Procedures (SUBROUTINE and FUNCTION): Procedures, for detailed
- information on how this particular version of `g77' passes arguments to
- procedures.
- 
- 
- File: g77.info,  Node: %DESCR(),  Next: Generics and Specifics,  Prev: %REF(),  Up: Functions and Subroutines
- 
- The `%DESCR()' Construct
- ------------------------
- 
-      %DESCR(ARG)
- 
-    The `%DESCR()' construct specifies that an argument, ARG, is to be
- passed by descriptor, instead of by value or reference.
- 
-    `%DESCR()' is restricted to actual arguments in invocations of
- external procedures.
- 
-    Use of `%DESCR()' is recommended only for code that is accessing
- facilities outside of GNU Fortran, such as operating system or
- windowing facilities.  It is best to constrain such uses to isolated
- portions of a program--portions the deal specifically and exclusively
- with low-level, system-dependent facilities.  Such portions might well
- provide a portable interface for use by the program as a whole, but are
- themselves not portable, and should be thoroughly tested each time they
- are rebuilt using a new compiler or version of a compiler.
- 
-    Do not depend on `%DESCR()' supplying a pointer and/or a length
- passed by value to the procedure being invoked.  While that is a likely
- implementation choice, other implementation choices are available that
- preserve the pass-by-reference semantics without passing a pointer to
- the argument, ARG.  (For example, a copy-in/copy-out implementation.)
- And, future versions of `g77' might change the way descriptors are
- implemented, such as passing a single argument pointing to a record
- containing the pointer/length information instead of passing that same
- information via two arguments as it currently does.
- 
-    _Implementation Note:_ Currently, `g77' passes all variables and
- arrays of type `CHARACTER' by descriptor.  Future versions of, or
- dialects supported by, `g77' might pass `CHARACTER' functions by
- descriptor as well.
- 
-    Thus, use of `%DESCR()' tends to be restricted to cases where ARG is
- not type `CHARACTER' but the called procedure accesses it via a means
- similar to the method used for Fortran `CHARACTER' arguments.
- 
-    *Note Procedures (SUBROUTINE and FUNCTION): Procedures, for detailed
- information on how this particular version of `g77' passes arguments to
- procedures.
- 
--- 0 ----
diff -Nrc3pad gcc-3.2.3/gcc/f/g77.info-7 gcc-3.3/gcc/f/g77.info-7
*** gcc-3.2.3/gcc/f/g77.info-7	2003-04-22 07:07:24.000000000 +0000
--- gcc-3.3/gcc/f/g77.info-7	1970-01-01 00:00:00.000000000 +0000
***************
*** 1,1678 ****
- This is g77.info, produced by makeinfo version 4.5 from g77.texi.
- 
- INFO-DIR-SECTION Programming
- START-INFO-DIR-ENTRY
- * g77: (g77).                  The GNU Fortran compiler.
- END-INFO-DIR-ENTRY
-    This file documents the use and the internals of the GNU Fortran
- (`g77') compiler.  It corresponds to the GCC-3.2.3 version of `g77'.
- 
-    Published by the Free Software Foundation 59 Temple Place - Suite 330
- Boston, MA 02111-1307 USA
- 
-    Copyright (C) 1995,1996,1997,1998,1999,2000,2001,2002 Free Software
- Foundation, Inc.
- 
-    Permission is granted to copy, distribute and/or modify this document
- under the terms of the GNU Free Documentation License, Version 1.1 or
- any later version published by the Free Software Foundation; with the
- Invariant Sections being "GNU General Public License" and "Funding Free
- Software", the Front-Cover texts being (a) (see below), and with the
- Back-Cover Texts being (b) (see below).  A copy of the license is
- included in the section entitled "GNU Free Documentation License".
- 
-    (a) The FSF's Front-Cover Text is:
- 
-    A GNU Manual
- 
-    (b) The FSF's Back-Cover Text is:
- 
-    You have freedom to copy and modify this GNU Manual, like GNU
- software.  Copies published by the Free Software Foundation raise
- funds for GNU development.
- 
-    Contributed by James Craig Burley (<craig@jcb-sc.com>).  Inspired by
- a first pass at translating `g77-0.5.16/f/DOC' that was contributed to
- Craig by David Ronis (<ronis@onsager.chem.mcgill.ca>).
- 
- 
- File: g77.info,  Node: Generics and Specifics,  Next: REAL() and AIMAG() of Complex,  Prev: %DESCR(),  Up: Functions and Subroutines
- 
- Generics and Specifics
- ----------------------
- 
-    The ANSI FORTRAN 77 language defines generic and specific intrinsics.
- In short, the distinctions are:
- 
-    * _Specific_ intrinsics have specific types for their arguments and
-      a specific return type.
- 
-    * _Generic_ intrinsics are treated, on a case-by-case basis in the
-      program's source code, as one of several possible specific
-      intrinsics.
- 
-      Typically, a generic intrinsic has a return type that is
-      determined by the type of one or more of its arguments.
- 
-    The GNU Fortran language generalizes these concepts somewhat,
- especially by providing intrinsic subroutines and generic intrinsics
- that are treated as either a specific intrinsic subroutine or a
- specific intrinsic function (e.g. `SECOND').
- 
-    However, GNU Fortran avoids generalizing this concept to the point
- where existing code would be accepted as meaning something possibly
- different than what was intended.
- 
-    For example, `ABS' is a generic intrinsic, so all working code
- written using `ABS' of an `INTEGER' argument expects an `INTEGER'
- return value.  Similarly, all such code expects that `ABS' of an
- `INTEGER*2' argument returns an `INTEGER*2' return value.
- 
-    Yet, `IABS' is a _specific_ intrinsic that accepts only an
- `INTEGER(KIND=1)' argument.  Code that passes something other than an
- `INTEGER(KIND=1)' argument to `IABS' is not valid GNU Fortran code,
- because it is not clear what the author intended.
- 
-    For example, if `J' is `INTEGER(KIND=6)', `IABS(J)' is not defined
- by the GNU Fortran language, because the programmer might have used
- that construct to mean any of the following, subtly different, things:
- 
-    * Convert `J' to `INTEGER(KIND=1)' first (as if `IABS(INT(J))' had
-      been written).
- 
-    * Convert the result of the intrinsic to `INTEGER(KIND=1)' (as if
-      `INT(ABS(J))' had been written).
- 
-    * No conversion (as if `ABS(J)' had been written).
- 
-    The distinctions matter especially when types and values wider than
- `INTEGER(KIND=1)' (such as `INTEGER(KIND=2)'), or when operations
- performing more "arithmetic" than absolute-value, are involved.
- 
-    The following sample program is not a valid GNU Fortran program, but
- might be accepted by other compilers.  If so, the output is likely to
- be revealing in terms of how a given compiler treats intrinsics (that
- normally are specific) when they are given arguments that do not
- conform to their stated requirements:
- 
-            PROGRAM JCB002
-      C Version 1:
-      C Modified 1999-02-15 (Burley) to delete my email address.
-      C Modified 1997-05-21 (Burley) to accommodate compilers that implement
-      C INT(I1-I2) as INT(I1)-INT(I2) given INTEGER*2 I1,I2.
-      C
-      C Version 0:
-      C Written by James Craig Burley 1997-02-20.
-      C
-      C Purpose:
-      C Determine how compilers handle non-standard IDIM
-      C on INTEGER*2 operands, which presumably can be
-      C extrapolated into understanding how the compiler
-      C generally treats specific intrinsics that are passed
-      C arguments not of the correct types.
-      C
-      C If your compiler implements INTEGER*2 and INTEGER
-      C as the same type, change all INTEGER*2 below to
-      C INTEGER*1.
-      C
-            INTEGER*2 I0, I4
-            INTEGER I1, I2, I3
-            INTEGER*2 ISMALL, ILARGE
-            INTEGER*2 ITOOLG, ITWO
-            INTEGER*2 ITMP
-            LOGICAL L2, L3, L4
-      C
-      C Find smallest INTEGER*2 number.
-      C
-            ISMALL=0
-       10   I0 = ISMALL-1
-            IF ((I0 .GE. ISMALL) .OR. (I0+1 .NE. ISMALL)) GOTO 20
-            ISMALL = I0
-            GOTO 10
-       20   CONTINUE
-      C
-      C Find largest INTEGER*2 number.
-      C
-            ILARGE=0
-       30   I0 = ILARGE+1
-            IF ((I0 .LE. ILARGE) .OR. (I0-1 .NE. ILARGE)) GOTO 40
-            ILARGE = I0
-            GOTO 30
-       40   CONTINUE
-      C
-      C Multiplying by two adds stress to the situation.
-      C
-            ITWO = 2
-      C
-      C Need a number that, added to -2, is too wide to fit in I*2.
-      C
-            ITOOLG = ISMALL
-      C
-      C Use IDIM the straightforward way.
-      C
-            I1 = IDIM (ILARGE, ISMALL) * ITWO + ITOOLG
-      C
-      C Calculate result for first interpretation.
-      C
-            I2 = (INT (ILARGE) - INT (ISMALL)) * ITWO + ITOOLG
-      C
-      C Calculate result for second interpretation.
-      C
-            ITMP = ILARGE - ISMALL
-            I3 = (INT (ITMP)) * ITWO + ITOOLG
-      C
-      C Calculate result for third interpretation.
-      C
-            I4 = (ILARGE - ISMALL) * ITWO + ITOOLG
-      C
-      C Print results.
-      C
-            PRINT *, 'ILARGE=', ILARGE
-            PRINT *, 'ITWO=', ITWO
-            PRINT *, 'ITOOLG=', ITOOLG
-            PRINT *, 'ISMALL=', ISMALL
-            PRINT *, 'I1=', I1
-            PRINT *, 'I2=', I2
-            PRINT *, 'I3=', I3
-            PRINT *, 'I4=', I4
-            PRINT *
-            L2 = (I1 .EQ. I2)
-            L3 = (I1 .EQ. I3)
-            L4 = (I1 .EQ. I4)
-            IF (L2 .AND. .NOT.L3 .AND. .NOT.L4) THEN
-               PRINT *, 'Interp 1: IDIM(I*2,I*2) => IDIM(INT(I*2),INT(I*2))'
-               STOP
-            END IF
-            IF (L3 .AND. .NOT.L2 .AND. .NOT.L4) THEN
-               PRINT *, 'Interp 2: IDIM(I*2,I*2) => INT(DIM(I*2,I*2))'
-               STOP
-            END IF
-            IF (L4 .AND. .NOT.L2 .AND. .NOT.L3) THEN
-               PRINT *, 'Interp 3: IDIM(I*2,I*2) => DIM(I*2,I*2)'
-               STOP
-            END IF
-            PRINT *, 'Results need careful analysis.'
-            END
- 
-    No future version of the GNU Fortran language will likely permit
- specific intrinsic invocations with wrong-typed arguments (such as
- `IDIM' in the above example), since it has been determined that
- disagreements exist among many production compilers on the
- interpretation of such invocations.  These disagreements strongly
- suggest that Fortran programmers, and certainly existing Fortran
- programs, disagree about the meaning of such invocations.
- 
-    The first version of `JCB002' didn't accommodate some compilers'
- treatment of `INT(I1-I2)' where `I1' and `I2' are `INTEGER*2'.  In such
- a case, these compilers apparently convert both operands to `INTEGER*4'
- and then do an `INTEGER*4' subtraction, instead of doing an `INTEGER*2'
- subtraction on the original values in `I1' and `I2'.
- 
-    However, the results of the careful analyses done on the outputs of
- programs compiled by these various compilers show that they all
- implement either `Interp 1' or `Interp 2' above.
- 
-    Specifically, it is believed that the new version of `JCB002' above
- will confirm that:
- 
-    * Digital Semiconductor ("DEC") Alpha OSF/1, HP-UX 10.0.1, AIX 3.2.5
-      `f77' compilers all implement `Interp 1'.
- 
-    * IRIX 5.3 `f77' compiler implements `Interp 2'.
- 
-    * Solaris 2.5, SunOS 4.1.3, DECstation ULTRIX 4.3, and IRIX 6.1
-      `f77' compilers all implement `Interp 3'.
- 
-    If you get different results than the above for the stated
- compilers, or have results for other compilers that might be worth
- adding to the above list, please let us know the details (compiler
- product, version, machine, results, and so on).
- 
- 
- File: g77.info,  Node: REAL() and AIMAG() of Complex,  Next: CMPLX() of DOUBLE PRECISION,  Prev: Generics and Specifics,  Up: Functions and Subroutines
- 
- `REAL()' and `AIMAG()' of Complex
- ---------------------------------
- 
-    The GNU Fortran language disallows `REAL(EXPR)' and `AIMAG(EXPR)',
- where EXPR is any `COMPLEX' type other than `COMPLEX(KIND=1)', except
- when they are used in the following way:
- 
-      REAL(REAL(EXPR))
-      REAL(AIMAG(EXPR))
- 
- The above forms explicitly specify that the desired effect is to
- convert the real or imaginary part of EXPR, which might be some `REAL'
- type other than `REAL(KIND=1)', to type `REAL(KIND=1)', and have that
- serve as the value of the expression.
- 
-    The GNU Fortran language offers clearly named intrinsics to extract
- the real and imaginary parts of a complex entity without any conversion:
- 
-      REALPART(EXPR)
-      IMAGPART(EXPR)
- 
-    To express the above using typical extended FORTRAN 77, use the
- following constructs (when EXPR is `COMPLEX(KIND=2)'):
- 
-      DBLE(EXPR)
-      DIMAG(EXPR)
- 
-    The FORTRAN 77 language offers no way to explicitly specify the real
- and imaginary parts of a complex expression of arbitrary type,
- apparently as a result of requiring support for only one `COMPLEX' type
- (`COMPLEX(KIND=1)').  The concepts of converting an expression to type
- `REAL(KIND=1)' and of extracting the real part of a complex expression
- were thus "smooshed" by FORTRAN 77 into a single intrinsic, since they
- happened to have the exact same effect in that language (due to having
- only one `COMPLEX' type).
- 
-    _Note:_ When `-ff90' is in effect, `g77' treats `REAL(EXPR)', where
- EXPR is of type `COMPLEX', as `REALPART(EXPR)', whereas with
- `-fugly-complex -fno-f90' in effect, it is treated as
- `REAL(REALPART(EXPR))'.
- 
-    *Note Ugly Complex Part Extraction::, for more information.
- 
- 
- File: g77.info,  Node: CMPLX() of DOUBLE PRECISION,  Next: MIL-STD 1753,  Prev: REAL() and AIMAG() of Complex,  Up: Functions and Subroutines
- 
- `CMPLX()' of `DOUBLE PRECISION'
- -------------------------------
- 
-    In accordance with Fortran 90 and at least some (perhaps all) other
- compilers, the GNU Fortran language defines `CMPLX()' as always
- returning a result that is type `COMPLEX(KIND=1)'.
- 
-    This means `CMPLX(D1,D2)', where `D1' and `D2' are `REAL(KIND=2)'
- (`DOUBLE PRECISION'), is treated as:
- 
-      CMPLX(SNGL(D1), SNGL(D2))
- 
-    (It was necessary for Fortran 90 to specify this behavior for
- `DOUBLE PRECISION' arguments, since that is the behavior mandated by
- FORTRAN 77.)
- 
-    The GNU Fortran language also provides the `DCMPLX()' intrinsic,
- which is provided by some FORTRAN 77 compilers to construct a `DOUBLE
- COMPLEX' entity from of `DOUBLE PRECISION' operands.  However, this
- solution does not scale well when more `COMPLEX' types (having various
- precisions and ranges) are offered by Fortran implementations.
- 
-    Fortran 90 extends the `CMPLX()' intrinsic by adding an extra
- argument used to specify the desired kind of complex result.  However,
- this solution is somewhat awkward to use, and `g77' currently does not
- support it.
- 
-    The GNU Fortran language provides a simple way to build a complex
- value out of two numbers, with the precise type of the value determined
- by the types of the two numbers (via the usual type-promotion
- mechanism):
- 
-      COMPLEX(REAL, IMAG)
- 
-    When REAL and IMAG are the same `REAL' types, `COMPLEX()' performs
- no conversion other than to put them together to form a complex result
- of the same (complex version of real) type.
- 
-    *Note Complex Intrinsic::, for more information.
- 
- 
- File: g77.info,  Node: MIL-STD 1753,  Next: f77/f2c Intrinsics,  Prev: CMPLX() of DOUBLE PRECISION,  Up: Functions and Subroutines
- 
- MIL-STD 1753 Support
- --------------------
- 
-    The GNU Fortran language includes the MIL-STD 1753 intrinsics
- `BTEST', `IAND', `IBCLR', `IBITS', `IBSET', `IEOR', `IOR', `ISHFT',
- `ISHFTC', `MVBITS', and `NOT'.
- 
- 
- File: g77.info,  Node: f77/f2c Intrinsics,  Next: Table of Intrinsic Functions,  Prev: MIL-STD 1753,  Up: Functions and Subroutines
- 
- `f77'/`f2c' Intrinsics
- ----------------------
- 
-    The bit-manipulation intrinsics supported by traditional `f77' and
- by `f2c' are available in the GNU Fortran language.  These include
- `AND', `LSHIFT', `OR', `RSHIFT', and `XOR'.
- 
-    Also supported are the intrinsics `CDABS', `CDCOS', `CDEXP',
- `CDLOG', `CDSIN', `CDSQRT', `DCMPLX', `DCONJG', `DFLOAT', `DIMAG',
- `DREAL', and `IMAG', `ZABS', `ZCOS', `ZEXP', `ZLOG', `ZSIN', and
- `ZSQRT'.
- 
- 
- File: g77.info,  Node: Table of Intrinsic Functions,  Prev: f77/f2c Intrinsics,  Up: Functions and Subroutines
- 
- Table of Intrinsic Functions
- ----------------------------
- 
-    (Corresponds to Section 15.10 of ANSI X3.9-1978 FORTRAN 77.)
- 
-    The GNU Fortran language adds various functions, subroutines, types,
- and arguments to the set of intrinsic functions in ANSI FORTRAN 77.
- The complete set of intrinsics supported by the GNU Fortran language is
- described below.
- 
-    Note that a name is not treated as that of an intrinsic if it is
- specified in an `EXTERNAL' statement in the same program unit; if a
- command-line option is used to disable the groups to which the
- intrinsic belongs; or if the intrinsic is not named in an `INTRINSIC'
- statement and a command-line option is used to hide the groups to which
- the intrinsic belongs.
- 
-    So, it is recommended that any reference in a program unit to an
- intrinsic procedure that is not a standard FORTRAN 77 intrinsic be
- accompanied by an appropriate `INTRINSIC' statement in that program
- unit.  This sort of defensive programming makes it more likely that an
- implementation will issue a diagnostic rather than generate incorrect
- code for such a reference.
- 
-    The terminology used below is based on that of the Fortran 90
- standard, so that the text may be more concise and accurate:
- 
-    * `OPTIONAL' means the argument may be omitted.
- 
-    * `A-1, A-2, ..., A-n' means more than one argument (generally named
-      `A') may be specified.
- 
-    * `scalar' means the argument must not be an array (must be a
-      variable or array element, or perhaps a constant if expressions
-      are permitted).
- 
-    * `DIMENSION(4)' means the argument must be an array having 4
-      elements.
- 
-    * `INTENT(IN)' means the argument must be an expression (such as a
-      constant or a variable that is defined upon invocation of the
-      intrinsic).
- 
-    * `INTENT(OUT)' means the argument must be definable by the
-      invocation of the intrinsic (that is, must not be a constant nor
-      an expression involving operators other than array reference and
-      substring reference).
- 
-    * `INTENT(INOUT)' means the argument must be defined prior to, and
-      definable by, invocation of the intrinsic (a combination of the
-      requirements of `INTENT(IN)' and `INTENT(OUT)'.
- 
-    * *Note Kind Notation::, for an explanation of `KIND'.
- 
-    (Note that the empty lines appearing in the menu below are not
- intentional--they result from a bug in the GNU `makeinfo' program...a
- program that, if it did not exist, would leave this document in far
- worse shape!)
- 
- * Menu:
- 
- 
- * Abort Intrinsic::     Abort the program.
- 
- * Abs Intrinsic::       Absolute value.
- 
- * Access Intrinsic::    Check file accessibility.
- 
- * AChar Intrinsic::     ASCII character from code.
- 
- * ACos Intrinsic::      Arc cosine.
- 
- * AdjustL Intrinsic::   (Reserved for future use.)
- * AdjustR Intrinsic::   (Reserved for future use.)
- 
- * AImag Intrinsic::     Convert/extract imaginary part of complex.
- 
- * AInt Intrinsic::      Truncate to whole number.
- 
- * Alarm Intrinsic::     Execute a routine after a given delay.
- 
- * All Intrinsic::       (Reserved for future use.)
- * Allocated Intrinsic:: (Reserved for future use.)
- 
- * ALog Intrinsic::      Natural logarithm (archaic).
- * ALog10 Intrinsic::    Common logarithm (archaic).
- * AMax0 Intrinsic::     Maximum value (archaic).
- * AMax1 Intrinsic::     Maximum value (archaic).
- * AMin0 Intrinsic::     Minimum value (archaic).
- * AMin1 Intrinsic::     Minimum value (archaic).
- * AMod Intrinsic::      Remainder (archaic).
- 
- * And Intrinsic::       Boolean AND.
- 
- * ANInt Intrinsic::     Round to nearest whole number.
- 
- * Any Intrinsic::       (Reserved for future use.)
- 
- * ASin Intrinsic::      Arc sine.
- 
- * Associated Intrinsic:: (Reserved for future use.)
- 
- * ATan Intrinsic::      Arc tangent.
- * ATan2 Intrinsic::     Arc tangent.
- 
- * BesJ0 Intrinsic::     Bessel function.
- * BesJ1 Intrinsic::     Bessel function.
- * BesJN Intrinsic::     Bessel function.
- * BesY0 Intrinsic::     Bessel function.
- * BesY1 Intrinsic::     Bessel function.
- * BesYN Intrinsic::     Bessel function.
- 
- * Bit_Size Intrinsic::  Number of bits in argument's type.
- 
- * BTest Intrinsic::     Test bit.
- 
- * CAbs Intrinsic::      Absolute value (archaic).
- * CCos Intrinsic::      Cosine (archaic).
- 
- * Ceiling Intrinsic::   (Reserved for future use.)
- 
- * CExp Intrinsic::      Exponential (archaic).
- * Char Intrinsic::      Character from code.
- 
- * ChDir Intrinsic (subroutine):: Change directory.
- 
- * ChMod Intrinsic (subroutine):: Change file modes.
- 
- * CLog Intrinsic::      Natural logarithm (archaic).
- * Cmplx Intrinsic::     Construct `COMPLEX(KIND=1)' value.
- 
- * Complex Intrinsic::   Build complex value from real and
-                          imaginary parts.
- 
- * Conjg Intrinsic::     Complex conjugate.
- * Cos Intrinsic::       Cosine.
- 
- * CosH Intrinsic::      Hyperbolic cosine.
- 
- * Count Intrinsic::     (Reserved for future use.)
- * CPU_Time Intrinsic::  Get current CPU time.
- * CShift Intrinsic::    (Reserved for future use.)
- 
- * CSin Intrinsic::      Sine (archaic).
- * CSqRt Intrinsic::     Square root (archaic).
- 
- * CTime Intrinsic (subroutine):: Convert time to Day Mon dd hh:mm:ss yyyy.
- * CTime Intrinsic (function):: Convert time to Day Mon dd hh:mm:ss yyyy.
- 
- * DAbs Intrinsic::      Absolute value (archaic).
- * DACos Intrinsic::     Arc cosine (archaic).
- 
- * DASin Intrinsic::     Arc sine (archaic).
- 
- * DATan Intrinsic::     Arc tangent (archaic).
- * DATan2 Intrinsic::    Arc tangent (archaic).
- 
- * Date_and_Time Intrinsic:: Get the current date and time.
- 
- * DbesJ0 Intrinsic::    Bessel function (archaic).
- * DbesJ1 Intrinsic::    Bessel function (archaic).
- * DbesJN Intrinsic::    Bessel function (archaic).
- * DbesY0 Intrinsic::    Bessel function (archaic).
- * DbesY1 Intrinsic::    Bessel function (archaic).
- * DbesYN Intrinsic::    Bessel function (archaic).
- 
- * Dble Intrinsic::      Convert to double precision.
- 
- * DCos Intrinsic::      Cosine (archaic).
- 
- * DCosH Intrinsic::     Hyperbolic cosine (archaic).
- * DDiM Intrinsic::      Difference magnitude (archaic).
- 
- * DErF Intrinsic::      Error function (archaic).
- * DErFC Intrinsic::     Complementary error function (archaic).
- 
- * DExp Intrinsic::      Exponential (archaic).
- 
- * Digits Intrinsic::    (Reserved for future use.)
- 
- * DiM Intrinsic::       Difference magnitude (non-negative subtract).
- 
- * DInt Intrinsic::      Truncate to whole number (archaic).
- * DLog Intrinsic::      Natural logarithm (archaic).
- * DLog10 Intrinsic::    Common logarithm (archaic).
- * DMax1 Intrinsic::     Maximum value (archaic).
- * DMin1 Intrinsic::     Minimum value (archaic).
- * DMod Intrinsic::      Remainder (archaic).
- * DNInt Intrinsic::     Round to nearest whole number (archaic).
- 
- * Dot_Product Intrinsic:: (Reserved for future use.)
- 
- * DProd Intrinsic::     Double-precision product.
- 
- * DSign Intrinsic::     Apply sign to magnitude (archaic).
- * DSin Intrinsic::      Sine (archaic).
- 
- * DSinH Intrinsic::     Hyperbolic sine (archaic).
- * DSqRt Intrinsic::     Square root (archaic).
- * DTan Intrinsic::      Tangent (archaic).
- 
- * DTanH Intrinsic::     Hyperbolic tangent (archaic).
- 
- * DTime Intrinsic (subroutine):: Get elapsed time since last time.
- 
- * EOShift Intrinsic::   (Reserved for future use.)
- * Epsilon Intrinsic::   (Reserved for future use.)
- 
- * ErF Intrinsic::       Error function.
- * ErFC Intrinsic::      Complementary error function.
- * ETime Intrinsic (subroutine):: Get elapsed time for process.
- * ETime Intrinsic (function):: Get elapsed time for process.
- * Exit Intrinsic::      Terminate the program.
- 
- * Exp Intrinsic::       Exponential.
- 
- * Exponent Intrinsic::  (Reserved for future use.)
- 
- * FDate Intrinsic (subroutine):: Get current time as Day Mon dd hh:mm:ss yyyy.
- * FDate Intrinsic (function):: Get current time as Day Mon dd hh:mm:ss yyyy.
- * FGet Intrinsic (subroutine):: Read a character from unit 5 stream-wise.
- 
- * FGetC Intrinsic (subroutine):: Read a character stream-wise.
- 
- * Float Intrinsic::     Conversion (archaic).
- 
- * Floor Intrinsic::     (Reserved for future use.)
- 
- * Flush Intrinsic::     Flush buffered output.
- * FNum Intrinsic::      Get file descriptor from Fortran unit number.
- * FPut Intrinsic (subroutine):: Write a character to unit 6 stream-wise.
- 
- * FPutC Intrinsic (subroutine):: Write a character stream-wise.
- 
- * Fraction Intrinsic::  (Reserved for future use.)
- 
- * FSeek Intrinsic::     Position file (low-level).
- * FStat Intrinsic (subroutine):: Get file information.
- * FStat Intrinsic (function):: Get file information.
- * FTell Intrinsic (subroutine):: Get file position (low-level).
- * FTell Intrinsic (function):: Get file position (low-level).
- * GError Intrinsic::    Get error message for last error.
- * GetArg Intrinsic::    Obtain command-line argument.
- * GetCWD Intrinsic (subroutine):: Get current working directory.
- * GetCWD Intrinsic (function):: Get current working directory.
- * GetEnv Intrinsic::    Get environment variable.
- * GetGId Intrinsic::    Get process group id.
- * GetLog Intrinsic::    Get login name.
- * GetPId Intrinsic::    Get process id.
- * GetUId Intrinsic::    Get process user id.
- * GMTime Intrinsic::    Convert time to GMT time info.
- * HostNm Intrinsic (subroutine):: Get host name.
- * HostNm Intrinsic (function):: Get host name.
- 
- * Huge Intrinsic::      (Reserved for future use.)
- 
- * IAbs Intrinsic::      Absolute value (archaic).
- 
- * IAChar Intrinsic::    ASCII code for character.
- 
- * IAnd Intrinsic::      Boolean AND.
- 
- * IArgC Intrinsic::     Obtain count of command-line arguments.
- 
- * IBClr Intrinsic::     Clear a bit.
- * IBits Intrinsic::     Extract a bit subfield of a variable.
- * IBSet Intrinsic::     Set a bit.
- 
- * IChar Intrinsic::     Code for character.
- 
- * IDate Intrinsic (UNIX):: Get local time info.
- 
- * IDiM Intrinsic::      Difference magnitude (archaic).
- * IDInt Intrinsic::     Convert to `INTEGER' value truncated
-                          to whole number (archaic).
- * IDNInt Intrinsic::    Convert to `INTEGER' value rounded
-                          to nearest whole number (archaic).
- 
- * IEOr Intrinsic::      Boolean XOR.
- 
- * IErrNo Intrinsic::    Get error number for last error.
- 
- * IFix Intrinsic::      Conversion (archaic).
- 
- * Imag Intrinsic::      Extract imaginary part of complex.
- 
- * ImagPart Intrinsic::  Extract imaginary part of complex.
- 
- * Index Intrinsic::     Locate a CHARACTER substring.
- 
- * Int Intrinsic::       Convert to `INTEGER' value truncated
-                          to whole number.
- 
- * Int2 Intrinsic::      Convert to `INTEGER(KIND=6)' value
-                          truncated to whole number.
- * Int8 Intrinsic::      Convert to `INTEGER(KIND=2)' value
-                          truncated to whole number.
- 
- * IOr Intrinsic::       Boolean OR.
- 
- * IRand Intrinsic::     Random number.
- * IsaTty Intrinsic::    Is unit connected to a terminal?
- 
- * IShft Intrinsic::     Logical bit shift.
- * IShftC Intrinsic::    Circular bit shift.
- 
- * ISign Intrinsic::     Apply sign to magnitude (archaic).
- 
- * ITime Intrinsic::     Get local time of day.
- 
- * Kill Intrinsic (subroutine):: Signal a process.
- 
- * Kind Intrinsic::      (Reserved for future use.)
- * LBound Intrinsic::    (Reserved for future use.)
- 
- * Len Intrinsic::       Length of character entity.
- 
- * Len_Trim Intrinsic::  Get last non-blank character in string.
- 
- * LGe Intrinsic::       Lexically greater than or equal.
- * LGt Intrinsic::       Lexically greater than.
- 
- * Link Intrinsic (subroutine):: Make hard link in file system.
- 
- * LLe Intrinsic::       Lexically less than or equal.
- * LLt Intrinsic::       Lexically less than.
- 
- * LnBlnk Intrinsic::    Get last non-blank character in string.
- * Loc Intrinsic::       Address of entity in core.
- 
- * Log Intrinsic::       Natural logarithm.
- * Log10 Intrinsic::     Common logarithm.
- 
- * Logical Intrinsic::   (Reserved for future use.)
- 
- * Long Intrinsic::      Conversion to `INTEGER(KIND=1)' (archaic).
- 
- * LShift Intrinsic::    Left-shift bits.
- 
- * LStat Intrinsic (subroutine):: Get file information.
- * LStat Intrinsic (function):: Get file information.
- * LTime Intrinsic::     Convert time to local time info.
- 
- * MatMul Intrinsic::    (Reserved for future use.)
- 
- * Max Intrinsic::       Maximum value.
- * Max0 Intrinsic::      Maximum value (archaic).
- * Max1 Intrinsic::      Maximum value (archaic).
- 
- * MaxExponent Intrinsic:: (Reserved for future use.)
- * MaxLoc Intrinsic::    (Reserved for future use.)
- * MaxVal Intrinsic::    (Reserved for future use.)
- 
- * MClock Intrinsic::    Get number of clock ticks for process.
- * MClock8 Intrinsic::   Get number of clock ticks for process.
- 
- * Merge Intrinsic::     (Reserved for future use.)
- 
- * Min Intrinsic::       Minimum value.
- * Min0 Intrinsic::      Minimum value (archaic).
- * Min1 Intrinsic::      Minimum value (archaic).
- 
- * MinExponent Intrinsic:: (Reserved for future use.)
- * MinLoc Intrinsic::    (Reserved for future use.)
- * MinVal Intrinsic::    (Reserved for future use.)
- 
- * Mod Intrinsic::       Remainder.
- 
- * Modulo Intrinsic::    (Reserved for future use.)
- 
- * MvBits Intrinsic::    Moving a bit field.
- 
- * Nearest Intrinsic::   (Reserved for future use.)
- 
- * NInt Intrinsic::      Convert to `INTEGER' value rounded
-                          to nearest whole number.
- 
- * Not Intrinsic::       Boolean NOT.
- 
- * Or Intrinsic::        Boolean OR.
- 
- * Pack Intrinsic::      (Reserved for future use.)
- 
- * PError Intrinsic::    Print error message for last error.
- 
- * Precision Intrinsic:: (Reserved for future use.)
- * Present Intrinsic::   (Reserved for future use.)
- * Product Intrinsic::   (Reserved for future use.)
- 
- * Radix Intrinsic::     (Reserved for future use.)
- 
- * Rand Intrinsic::      Random number.
- 
- * Random_Number Intrinsic:: (Reserved for future use.)
- * Random_Seed Intrinsic:: (Reserved for future use.)
- * Range Intrinsic::     (Reserved for future use.)
- 
- * Real Intrinsic::      Convert value to type `REAL(KIND=1)'.
- 
- * RealPart Intrinsic::  Extract real part of complex.
- 
- * Rename Intrinsic (subroutine):: Rename file.
- 
- * Repeat Intrinsic::    (Reserved for future use.)
- * Reshape Intrinsic::   (Reserved for future use.)
- * RRSpacing Intrinsic:: (Reserved for future use.)
- 
- * RShift Intrinsic::    Right-shift bits.
- 
- * Scale Intrinsic::     (Reserved for future use.)
- * Scan Intrinsic::      (Reserved for future use.)
- 
- * Second Intrinsic (function):: Get CPU time for process in seconds.
- * Second Intrinsic (subroutine):: Get CPU time for process
-                          in seconds.
- 
- * Selected_Int_Kind Intrinsic:: (Reserved for future use.)
- * Selected_Real_Kind Intrinsic:: (Reserved for future use.)
- * Set_Exponent Intrinsic:: (Reserved for future use.)
- * Shape Intrinsic::     (Reserved for future use.)
- 
- * Short Intrinsic::     Convert to `INTEGER(KIND=6)' value
-                          truncated to whole number.
- 
- * Sign Intrinsic::      Apply sign to magnitude.
- 
- * Signal Intrinsic (subroutine):: Muck with signal handling.
- 
- * Sin Intrinsic::       Sine.
- 
- * SinH Intrinsic::      Hyperbolic sine.
- 
- * Sleep Intrinsic::     Sleep for a specified time.
- 
- * Sngl Intrinsic::      Convert (archaic).
- 
- * Spacing Intrinsic::   (Reserved for future use.)
- * Spread Intrinsic::    (Reserved for future use.)
- 
- * SqRt Intrinsic::      Square root.
- 
- * SRand Intrinsic::     Random seed.
- * Stat Intrinsic (subroutine):: Get file information.
- * Stat Intrinsic (function):: Get file information.
- 
- * Sum Intrinsic::       (Reserved for future use.)
- 
- * SymLnk Intrinsic (subroutine):: Make symbolic link in file system.
- 
- * System Intrinsic (subroutine):: Invoke shell (system) command.
- 
- * System_Clock Intrinsic:: Get current system clock value.
- 
- * Tan Intrinsic::       Tangent.
- 
- * TanH Intrinsic::      Hyperbolic tangent.
- 
- * Time Intrinsic (UNIX):: Get current time as time value.
- 
- * Time8 Intrinsic::     Get current time as time value.
- 
- * Tiny Intrinsic::      (Reserved for future use.)
- * Transfer Intrinsic::  (Reserved for future use.)
- * Transpose Intrinsic:: (Reserved for future use.)
- * Trim Intrinsic::      (Reserved for future use.)
- 
- * TtyNam Intrinsic (subroutine):: Get name of terminal device for unit.
- * TtyNam Intrinsic (function):: Get name of terminal device for unit.
- 
- * UBound Intrinsic::    (Reserved for future use.)
- 
- * UMask Intrinsic (subroutine):: Set file creation permissions mask.
- 
- * Unlink Intrinsic (subroutine):: Unlink file.
- 
- * Unpack Intrinsic::    (Reserved for future use.)
- * Verify Intrinsic::    (Reserved for future use.)
- 
- * XOr Intrinsic::       Boolean XOR.
- * ZAbs Intrinsic::      Absolute value (archaic).
- * ZCos Intrinsic::      Cosine (archaic).
- * ZExp Intrinsic::      Exponential (archaic).
- 
- * ZLog Intrinsic::      Natural logarithm (archaic).
- * ZSin Intrinsic::      Sine (archaic).
- * ZSqRt Intrinsic::     Square root (archaic).
- 
- 
- File: g77.info,  Node: Abort Intrinsic,  Next: Abs Intrinsic,  Up: Table of Intrinsic Functions
- 
- Abort Intrinsic
- ...............
- 
-      CALL Abort()
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Prints a message and potentially causes a core dump via `abort(3)'.
- 
- 
- File: g77.info,  Node: Abs Intrinsic,  Next: Access Intrinsic,  Prev: Abort Intrinsic,  Up: Table of Intrinsic Functions
- 
- Abs Intrinsic
- .............
- 
-      Abs(A)
- 
- Abs: `INTEGER' or `REAL' function.  The exact type depends on that of
- argument A--if A is `COMPLEX', this function's type is `REAL' with the
- same `KIND=' value as the type of A.  Otherwise, this function's type
- is the same as that of A.
- 
- A: `INTEGER', `REAL', or `COMPLEX'; scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Returns the absolute value of A.
- 
-    If A is type `COMPLEX', the absolute value is computed as:
- 
-      SQRT(REALPART(A)**2+IMAGPART(A)**2)
- 
- Otherwise, it is computed by negating A if it is negative, or returning
- A.
- 
-    *Note Sign Intrinsic::, for how to explicitly compute the positive
- or negative form of the absolute value of an expression.
- 
- 
- File: g77.info,  Node: Access Intrinsic,  Next: AChar Intrinsic,  Prev: Abs Intrinsic,  Up: Table of Intrinsic Functions
- 
- Access Intrinsic
- ................
- 
-      Access(NAME, MODE)
- 
- Access: `INTEGER(KIND=1)' function.
- 
- NAME: `CHARACTER'; scalar; INTENT(IN).
- 
- MODE: `CHARACTER'; scalar; INTENT(IN).
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Checks file NAME for accessibility in the mode specified by MODE and
- returns 0 if the file is accessible in that mode, otherwise an error
- code if the file is inaccessible or MODE is invalid.  See `access(2)'.
- A null character (`CHAR(0)') marks the end of the name in
- NAME--otherwise, trailing blanks in NAME are ignored.  MODE may be a
- concatenation of any of the following characters:
- 
- `r'
-      Read permission
- 
- `w'
-      Write permission
- 
- `x'
-      Execute permission
- 
- `SPC'
-      Existence
- 
- 
- File: g77.info,  Node: AChar Intrinsic,  Next: ACos Intrinsic,  Prev: Access Intrinsic,  Up: Table of Intrinsic Functions
- 
- AChar Intrinsic
- ...............
- 
-      AChar(I)
- 
- AChar: `CHARACTER*1' function.
- 
- I: `INTEGER'; scalar; INTENT(IN).
- 
- Intrinsic groups: `f2c', `f90'.
- 
- Description:
- 
-    Returns the ASCII character corresponding to the code specified by I.
- 
-    *Note IAChar Intrinsic::, for the inverse of this function.
- 
-    *Note Char Intrinsic::, for the function corresponding to the
- system's native character set.
- 
- 
- File: g77.info,  Node: ACos Intrinsic,  Next: AdjustL Intrinsic,  Prev: AChar Intrinsic,  Up: Table of Intrinsic Functions
- 
- ACos Intrinsic
- ..............
- 
-      ACos(X)
- 
- ACos: `REAL' function, the `KIND=' value of the type being that of
- argument X.
- 
- X: `REAL'; scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Returns the arc-cosine (inverse cosine) of X in radians.
- 
-    *Note Cos Intrinsic::, for the inverse of this function.
- 
- 
- File: g77.info,  Node: AdjustL Intrinsic,  Next: AdjustR Intrinsic,  Prev: ACos Intrinsic,  Up: Table of Intrinsic Functions
- 
- AdjustL Intrinsic
- .................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL AdjustL' to use this name for
- an external procedure.
- 
- 
- File: g77.info,  Node: AdjustR Intrinsic,  Next: AImag Intrinsic,  Prev: AdjustL Intrinsic,  Up: Table of Intrinsic Functions
- 
- AdjustR Intrinsic
- .................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL AdjustR' to use this name for
- an external procedure.
- 
- 
- File: g77.info,  Node: AImag Intrinsic,  Next: AInt Intrinsic,  Prev: AdjustR Intrinsic,  Up: Table of Intrinsic Functions
- 
- AImag Intrinsic
- ...............
- 
-      AImag(Z)
- 
- AImag: `REAL' function.  This intrinsic is valid when argument Z is
- `COMPLEX(KIND=1)'.  When Z is any other `COMPLEX' type, this intrinsic
- is valid only when used as the argument to `REAL()', as explained below.
- 
- Z: `COMPLEX'; scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Returns the (possibly converted) imaginary part of Z.
- 
-    Use of `AIMAG()' with an argument of a type other than
- `COMPLEX(KIND=1)' is restricted to the following case:
- 
-      REAL(AIMAG(Z))
- 
- This expression converts the imaginary part of Z to `REAL(KIND=1)'.
- 
-    *Note REAL() and AIMAG() of Complex::, for more information.
- 
- 
- File: g77.info,  Node: AInt Intrinsic,  Next: Alarm Intrinsic,  Prev: AImag Intrinsic,  Up: Table of Intrinsic Functions
- 
- AInt Intrinsic
- ..............
- 
-      AInt(A)
- 
- AInt: `REAL' function, the `KIND=' value of the type being that of
- argument A.
- 
- A: `REAL'; scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Returns A with the fractional portion of its magnitude truncated and
- its sign preserved.  (Also called "truncation towards zero".)
- 
-    *Note ANInt Intrinsic::, for how to round to nearest whole number.
- 
-    *Note Int Intrinsic::, for how to truncate and then convert number
- to `INTEGER'.
- 
- 
- File: g77.info,  Node: Alarm Intrinsic,  Next: All Intrinsic,  Prev: AInt Intrinsic,  Up: Table of Intrinsic Functions
- 
- Alarm Intrinsic
- ...............
- 
-      CALL Alarm(SECONDS, HANDLER, STATUS)
- 
- SECONDS: `INTEGER'; scalar; INTENT(IN).
- 
- HANDLER: Signal handler (`INTEGER FUNCTION' or `SUBROUTINE') or
- dummy/global `INTEGER(KIND=1)' scalar.
- 
- STATUS: `INTEGER(KIND=1)'; OPTIONAL; scalar; INTENT(OUT).
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Causes external subroutine HANDLER to be executed after a delay of
- SECONDS seconds by using `alarm(1)' to set up a signal and `signal(2)'
- to catch it.  If STATUS is supplied, it will be returned with the
- number of seconds remaining until any previously scheduled alarm was
- due to be delivered, or zero if there was no previously scheduled alarm.
- *Note Signal Intrinsic (subroutine)::.
- 
- 
- File: g77.info,  Node: All Intrinsic,  Next: Allocated Intrinsic,  Prev: Alarm Intrinsic,  Up: Table of Intrinsic Functions
- 
- All Intrinsic
- .............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL All' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: Allocated Intrinsic,  Next: ALog Intrinsic,  Prev: All Intrinsic,  Up: Table of Intrinsic Functions
- 
- Allocated Intrinsic
- ...................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL Allocated' to use this name
- for an external procedure.
- 
- 
- File: g77.info,  Node: ALog Intrinsic,  Next: ALog10 Intrinsic,  Prev: Allocated Intrinsic,  Up: Table of Intrinsic Functions
- 
- ALog Intrinsic
- ..............
- 
-      ALog(X)
- 
- ALog: `REAL(KIND=1)' function.
- 
- X: `REAL(KIND=1)'; scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Archaic form of `LOG()' that is specific to one type for X.  *Note
- Log Intrinsic::.
- 
- 
- File: g77.info,  Node: ALog10 Intrinsic,  Next: AMax0 Intrinsic,  Prev: ALog Intrinsic,  Up: Table of Intrinsic Functions
- 
- ALog10 Intrinsic
- ................
- 
-      ALog10(X)
- 
- ALog10: `REAL(KIND=1)' function.
- 
- X: `REAL(KIND=1)'; scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Archaic form of `LOG10()' that is specific to one type for X.  *Note
- Log10 Intrinsic::.
- 
- 
- File: g77.info,  Node: AMax0 Intrinsic,  Next: AMax1 Intrinsic,  Prev: ALog10 Intrinsic,  Up: Table of Intrinsic Functions
- 
- AMax0 Intrinsic
- ...............
- 
-      AMax0(A-1, A-2, ..., A-n)
- 
- AMax0: `REAL(KIND=1)' function.
- 
- A: `INTEGER(KIND=1)'; at least two such arguments must be provided;
- scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Archaic form of `MAX()' that is specific to one type for A and a
- different return type.  *Note Max Intrinsic::.
- 
- 
- File: g77.info,  Node: AMax1 Intrinsic,  Next: AMin0 Intrinsic,  Prev: AMax0 Intrinsic,  Up: Table of Intrinsic Functions
- 
- AMax1 Intrinsic
- ...............
- 
-      AMax1(A-1, A-2, ..., A-n)
- 
- AMax1: `REAL(KIND=1)' function.
- 
- A: `REAL(KIND=1)'; at least two such arguments must be provided;
- scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Archaic form of `MAX()' that is specific to one type for A.  *Note
- Max Intrinsic::.
- 
- 
- File: g77.info,  Node: AMin0 Intrinsic,  Next: AMin1 Intrinsic,  Prev: AMax1 Intrinsic,  Up: Table of Intrinsic Functions
- 
- AMin0 Intrinsic
- ...............
- 
-      AMin0(A-1, A-2, ..., A-n)
- 
- AMin0: `REAL(KIND=1)' function.
- 
- A: `INTEGER(KIND=1)'; at least two such arguments must be provided;
- scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Archaic form of `MIN()' that is specific to one type for A and a
- different return type.  *Note Min Intrinsic::.
- 
- 
- File: g77.info,  Node: AMin1 Intrinsic,  Next: AMod Intrinsic,  Prev: AMin0 Intrinsic,  Up: Table of Intrinsic Functions
- 
- AMin1 Intrinsic
- ...............
- 
-      AMin1(A-1, A-2, ..., A-n)
- 
- AMin1: `REAL(KIND=1)' function.
- 
- A: `REAL(KIND=1)'; at least two such arguments must be provided;
- scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Archaic form of `MIN()' that is specific to one type for A.  *Note
- Min Intrinsic::.
- 
- 
- File: g77.info,  Node: AMod Intrinsic,  Next: And Intrinsic,  Prev: AMin1 Intrinsic,  Up: Table of Intrinsic Functions
- 
- AMod Intrinsic
- ..............
- 
-      AMod(A, P)
- 
- AMod: `REAL(KIND=1)' function.
- 
- A: `REAL(KIND=1)'; scalar; INTENT(IN).
- 
- P: `REAL(KIND=1)'; scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Archaic form of `MOD()' that is specific to one type for A.  *Note
- Mod Intrinsic::.
- 
- 
- File: g77.info,  Node: And Intrinsic,  Next: ANInt Intrinsic,  Prev: AMod Intrinsic,  Up: Table of Intrinsic Functions
- 
- And Intrinsic
- .............
- 
-      And(I, J)
- 
- And: `INTEGER' or `LOGICAL' function, the exact type being the result
- of cross-promoting the types of all the arguments.
- 
- I: `INTEGER' or `LOGICAL'; scalar; INTENT(IN).
- 
- J: `INTEGER' or `LOGICAL'; scalar; INTENT(IN).
- 
- Intrinsic groups: `f2c'.
- 
- Description:
- 
-    Returns value resulting from boolean AND of pair of bits in each of
- I and J.
- 
- 
- File: g77.info,  Node: ANInt Intrinsic,  Next: Any Intrinsic,  Prev: And Intrinsic,  Up: Table of Intrinsic Functions
- 
- ANInt Intrinsic
- ...............
- 
-      ANInt(A)
- 
- ANInt: `REAL' function, the `KIND=' value of the type being that of
- argument A.
- 
- A: `REAL'; scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Returns A with the fractional portion of its magnitude eliminated by
- rounding to the nearest whole number and with its sign preserved.
- 
-    A fractional portion exactly equal to `.5' is rounded to the whole
- number that is larger in magnitude.  (Also called "Fortran round".)
- 
-    *Note AInt Intrinsic::, for how to truncate to whole number.
- 
-    *Note NInt Intrinsic::, for how to round and then convert number to
- `INTEGER'.
- 
- 
- File: g77.info,  Node: Any Intrinsic,  Next: ASin Intrinsic,  Prev: ANInt Intrinsic,  Up: Table of Intrinsic Functions
- 
- Any Intrinsic
- .............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL Any' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: ASin Intrinsic,  Next: Associated Intrinsic,  Prev: Any Intrinsic,  Up: Table of Intrinsic Functions
- 
- ASin Intrinsic
- ..............
- 
-      ASin(X)
- 
- ASin: `REAL' function, the `KIND=' value of the type being that of
- argument X.
- 
- X: `REAL'; scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Returns the arc-sine (inverse sine) of X in radians.
- 
-    *Note Sin Intrinsic::, for the inverse of this function.
- 
- 
- File: g77.info,  Node: Associated Intrinsic,  Next: ATan Intrinsic,  Prev: ASin Intrinsic,  Up: Table of Intrinsic Functions
- 
- Associated Intrinsic
- ....................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL Associated' to use this name
- for an external procedure.
- 
- 
- File: g77.info,  Node: ATan Intrinsic,  Next: ATan2 Intrinsic,  Prev: Associated Intrinsic,  Up: Table of Intrinsic Functions
- 
- ATan Intrinsic
- ..............
- 
-      ATan(X)
- 
- ATan: `REAL' function, the `KIND=' value of the type being that of
- argument X.
- 
- X: `REAL'; scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Returns the arc-tangent (inverse tangent) of X in radians.
- 
-    *Note Tan Intrinsic::, for the inverse of this function.
- 
- 
- File: g77.info,  Node: ATan2 Intrinsic,  Next: BesJ0 Intrinsic,  Prev: ATan Intrinsic,  Up: Table of Intrinsic Functions
- 
- ATan2 Intrinsic
- ...............
- 
-      ATan2(Y, X)
- 
- ATan2: `REAL' function, the exact type being the result of
- cross-promoting the types of all the arguments.
- 
- Y: `REAL'; scalar; INTENT(IN).
- 
- X: `REAL'; scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Returns the arc-tangent (inverse tangent) of the complex number (Y,
- X) in radians.
- 
-    *Note Tan Intrinsic::, for the inverse of this function.
- 
- 
- File: g77.info,  Node: BesJ0 Intrinsic,  Next: BesJ1 Intrinsic,  Prev: ATan2 Intrinsic,  Up: Table of Intrinsic Functions
- 
- BesJ0 Intrinsic
- ...............
- 
-      BesJ0(X)
- 
- BesJ0: `REAL' function, the `KIND=' value of the type being that of
- argument X.
- 
- X: `REAL'; scalar; INTENT(IN).
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Calculates the Bessel function of the first kind of order 0 of X.
- See `bessel(3m)', on whose implementation the function depends.
- 
- 
- File: g77.info,  Node: BesJ1 Intrinsic,  Next: BesJN Intrinsic,  Prev: BesJ0 Intrinsic,  Up: Table of Intrinsic Functions
- 
- BesJ1 Intrinsic
- ...............
- 
-      BesJ1(X)
- 
- BesJ1: `REAL' function, the `KIND=' value of the type being that of
- argument X.
- 
- X: `REAL'; scalar; INTENT(IN).
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Calculates the Bessel function of the first kind of order 1 of X.
- See `bessel(3m)', on whose implementation the function depends.
- 
- 
- File: g77.info,  Node: BesJN Intrinsic,  Next: BesY0 Intrinsic,  Prev: BesJ1 Intrinsic,  Up: Table of Intrinsic Functions
- 
- BesJN Intrinsic
- ...............
- 
-      BesJN(N, X)
- 
- BesJN: `REAL' function, the `KIND=' value of the type being that of
- argument X.
- 
- N: `INTEGER' not wider than the default kind; scalar; INTENT(IN).
- 
- X: `REAL'; scalar; INTENT(IN).
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Calculates the Bessel function of the first kind of order N of X.
- See `bessel(3m)', on whose implementation the function depends.
- 
- 
- File: g77.info,  Node: BesY0 Intrinsic,  Next: BesY1 Intrinsic,  Prev: BesJN Intrinsic,  Up: Table of Intrinsic Functions
- 
- BesY0 Intrinsic
- ...............
- 
-      BesY0(X)
- 
- BesY0: `REAL' function, the `KIND=' value of the type being that of
- argument X.
- 
- X: `REAL'; scalar; INTENT(IN).
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Calculates the Bessel function of the second kind of order 0 of X.
- See `bessel(3m)', on whose implementation the function depends.
- 
- 
- File: g77.info,  Node: BesY1 Intrinsic,  Next: BesYN Intrinsic,  Prev: BesY0 Intrinsic,  Up: Table of Intrinsic Functions
- 
- BesY1 Intrinsic
- ...............
- 
-      BesY1(X)
- 
- BesY1: `REAL' function, the `KIND=' value of the type being that of
- argument X.
- 
- X: `REAL'; scalar; INTENT(IN).
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Calculates the Bessel function of the second kind of order 1 of X.
- See `bessel(3m)', on whose implementation the function depends.
- 
- 
- File: g77.info,  Node: BesYN Intrinsic,  Next: Bit_Size Intrinsic,  Prev: BesY1 Intrinsic,  Up: Table of Intrinsic Functions
- 
- BesYN Intrinsic
- ...............
- 
-      BesYN(N, X)
- 
- BesYN: `REAL' function, the `KIND=' value of the type being that of
- argument X.
- 
- N: `INTEGER' not wider than the default kind; scalar; INTENT(IN).
- 
- X: `REAL'; scalar; INTENT(IN).
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Calculates the Bessel function of the second kind of order N of X.
- See `bessel(3m)', on whose implementation the function depends.
- 
- 
- File: g77.info,  Node: Bit_Size Intrinsic,  Next: BTest Intrinsic,  Prev: BesYN Intrinsic,  Up: Table of Intrinsic Functions
- 
- Bit_Size Intrinsic
- ..................
- 
-      Bit_Size(I)
- 
- Bit_Size: `INTEGER' function, the `KIND=' value of the type being that
- of argument I.
- 
- I: `INTEGER'; scalar.
- 
- Intrinsic groups: `f90'.
- 
- Description:
- 
-    Returns the number of bits (integer precision plus sign bit)
- represented by the type for I.
- 
-    *Note BTest Intrinsic::, for how to test the value of a bit in a
- variable or array.
- 
-    *Note IBSet Intrinsic::, for how to set a bit in a variable to 1.
- 
-    *Note IBClr Intrinsic::, for how to set a bit in a variable to 0.
- 
- 
- File: g77.info,  Node: BTest Intrinsic,  Next: CAbs Intrinsic,  Prev: Bit_Size Intrinsic,  Up: Table of Intrinsic Functions
- 
- BTest Intrinsic
- ...............
- 
-      BTest(I, POS)
- 
- BTest: `LOGICAL(KIND=1)' function.
- 
- I: `INTEGER'; scalar; INTENT(IN).
- 
- POS: `INTEGER'; scalar; INTENT(IN).
- 
- Intrinsic groups: `mil', `f90', `vxt'.
- 
- Description:
- 
-    Returns `.TRUE.' if bit POS in I is 1, `.FALSE.' otherwise.
- 
-    (Bit 0 is the low-order (rightmost) bit, adding the value 2**0, or 1,
- to the number if set to 1; bit 1 is the next-higher-order bit, adding
- 2**1, or 2; bit 2 adds 2**2, or 4; and so on.)
- 
-    *Note Bit_Size Intrinsic::, for how to obtain the number of bits in
- a type.  The leftmost bit of I is `BIT_SIZE(I-1)'.
- 
- 
- File: g77.info,  Node: CAbs Intrinsic,  Next: CCos Intrinsic,  Prev: BTest Intrinsic,  Up: Table of Intrinsic Functions
- 
- CAbs Intrinsic
- ..............
- 
-      CAbs(A)
- 
- CAbs: `REAL(KIND=1)' function.
- 
- A: `COMPLEX(KIND=1)'; scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Archaic form of `ABS()' that is specific to one type for A.  *Note
- Abs Intrinsic::.
- 
- 
- File: g77.info,  Node: CCos Intrinsic,  Next: Ceiling Intrinsic,  Prev: CAbs Intrinsic,  Up: Table of Intrinsic Functions
- 
- CCos Intrinsic
- ..............
- 
-      CCos(X)
- 
- CCos: `COMPLEX(KIND=1)' function.
- 
- X: `COMPLEX(KIND=1)'; scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Archaic form of `COS()' that is specific to one type for X.  *Note
- Cos Intrinsic::.
- 
- 
- File: g77.info,  Node: Ceiling Intrinsic,  Next: CExp Intrinsic,  Prev: CCos Intrinsic,  Up: Table of Intrinsic Functions
- 
- Ceiling Intrinsic
- .................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL Ceiling' to use this name for
- an external procedure.
- 
- 
- File: g77.info,  Node: CExp Intrinsic,  Next: Char Intrinsic,  Prev: Ceiling Intrinsic,  Up: Table of Intrinsic Functions
- 
- CExp Intrinsic
- ..............
- 
-      CExp(X)
- 
- CExp: `COMPLEX(KIND=1)' function.
- 
- X: `COMPLEX(KIND=1)'; scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Archaic form of `EXP()' that is specific to one type for X.  *Note
- Exp Intrinsic::.
- 
- 
- File: g77.info,  Node: Char Intrinsic,  Next: ChDir Intrinsic (subroutine),  Prev: CExp Intrinsic,  Up: Table of Intrinsic Functions
- 
- Char Intrinsic
- ..............
- 
-      Char(I)
- 
- Char: `CHARACTER*1' function.
- 
- I: `INTEGER'; scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Returns the character corresponding to the code specified by I,
- using the system's native character set.
- 
-    Because the system's native character set is used, the
- correspondence between character and their codes is not necessarily the
- same between GNU Fortran implementations.
- 
-    Note that no intrinsic exists to convert a numerical value to a
- printable character string.  For example, there is no intrinsic that,
- given an `INTEGER' or `REAL' argument with the value `154', returns the
- `CHARACTER' result `'154''.
- 
-    Instead, you can use internal-file I/O to do this kind of conversion.
- For example:
- 
-      INTEGER VALUE
-      CHARACTER*10 STRING
-      VALUE = 154
-      WRITE (STRING, '(I10)'), VALUE
-      PRINT *, STRING
-      END
- 
-    The above program, when run, prints:
- 
-              154
- 
-    *Note IChar Intrinsic::, for the inverse of the `CHAR' function.
- 
-    *Note AChar Intrinsic::, for the function corresponding to the ASCII
- character set.
- 
- 
- File: g77.info,  Node: ChDir Intrinsic (subroutine),  Next: ChMod Intrinsic (subroutine),  Prev: Char Intrinsic,  Up: Table of Intrinsic Functions
- 
- ChDir Intrinsic (subroutine)
- ............................
- 
-      CALL ChDir(DIR, STATUS)
- 
- DIR: `CHARACTER'; scalar; INTENT(IN).
- 
- STATUS: `INTEGER(KIND=1)'; OPTIONAL; scalar; INTENT(OUT).
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Sets the current working directory to be DIR.  If the STATUS
- argument is supplied, it contains 0 on success or a non-zero error code
- otherwise upon return.  See `chdir(3)'.
- 
-    _Caution:_ Using this routine during I/O to a unit connected with a
- non-absolute file name can cause subsequent I/O on such a unit to fail
- because the I/O library might reopen files by name.
- 
-    Some non-GNU implementations of Fortran provide this intrinsic as
- only a function, not as a subroutine, or do not support the (optional)
- STATUS argument.
- 
-    For information on other intrinsics with the same name: *Note ChDir
- Intrinsic (function)::.
- 
--- 0 ----
diff -Nrc3pad gcc-3.2.3/gcc/f/g77.info-8 gcc-3.3/gcc/f/g77.info-8
*** gcc-3.2.3/gcc/f/g77.info-8	2003-04-22 07:07:24.000000000 +0000
--- gcc-3.3/gcc/f/g77.info-8	1970-01-01 00:00:00.000000000 +0000
***************
*** 1,1995 ****
- This is g77.info, produced by makeinfo version 4.5 from g77.texi.
- 
- INFO-DIR-SECTION Programming
- START-INFO-DIR-ENTRY
- * g77: (g77).                  The GNU Fortran compiler.
- END-INFO-DIR-ENTRY
-    This file documents the use and the internals of the GNU Fortran
- (`g77') compiler.  It corresponds to the GCC-3.2.3 version of `g77'.
- 
-    Published by the Free Software Foundation 59 Temple Place - Suite 330
- Boston, MA 02111-1307 USA
- 
-    Copyright (C) 1995,1996,1997,1998,1999,2000,2001,2002 Free Software
- Foundation, Inc.
- 
-    Permission is granted to copy, distribute and/or modify this document
- under the terms of the GNU Free Documentation License, Version 1.1 or
- any later version published by the Free Software Foundation; with the
- Invariant Sections being "GNU General Public License" and "Funding Free
- Software", the Front-Cover texts being (a) (see below), and with the
- Back-Cover Texts being (b) (see below).  A copy of the license is
- included in the section entitled "GNU Free Documentation License".
- 
-    (a) The FSF's Front-Cover Text is:
- 
-    A GNU Manual
- 
-    (b) The FSF's Back-Cover Text is:
- 
-    You have freedom to copy and modify this GNU Manual, like GNU
- software.  Copies published by the Free Software Foundation raise
- funds for GNU development.
- 
-    Contributed by James Craig Burley (<craig@jcb-sc.com>).  Inspired by
- a first pass at translating `g77-0.5.16/f/DOC' that was contributed to
- Craig by David Ronis (<ronis@onsager.chem.mcgill.ca>).
- 
- 
- File: g77.info,  Node: ChMod Intrinsic (subroutine),  Next: CLog Intrinsic,  Prev: ChDir Intrinsic (subroutine),  Up: Table of Intrinsic Functions
- 
- ChMod Intrinsic (subroutine)
- ............................
- 
-      CALL ChMod(NAME, MODE, STATUS)
- 
- NAME: `CHARACTER'; scalar; INTENT(IN).
- 
- MODE: `CHARACTER'; scalar; INTENT(IN).
- 
- STATUS: `INTEGER(KIND=1)'; OPTIONAL; scalar; INTENT(OUT).
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Changes the access mode of file NAME according to the specification
- MODE, which is given in the format of `chmod(1)'.  A null character
- (`CHAR(0)') marks the end of the name in NAME--otherwise, trailing
- blanks in NAME are ignored.  Currently, NAME must not contain the
- single quote character.
- 
-    If the STATUS argument is supplied, it contains 0 on success or a
- non-zero error code upon return.
- 
-    Note that this currently works by actually invoking `/bin/chmod' (or
- the `chmod' found when the library was configured) and so might fail in
- some circumstances and will, anyway, be slow.
- 
-    Some non-GNU implementations of Fortran provide this intrinsic as
- only a function, not as a subroutine, or do not support the (optional)
- STATUS argument.
- 
-    For information on other intrinsics with the same name: *Note ChMod
- Intrinsic (function)::.
- 
- 
- File: g77.info,  Node: CLog Intrinsic,  Next: Cmplx Intrinsic,  Prev: ChMod Intrinsic (subroutine),  Up: Table of Intrinsic Functions
- 
- CLog Intrinsic
- ..............
- 
-      CLog(X)
- 
- CLog: `COMPLEX(KIND=1)' function.
- 
- X: `COMPLEX(KIND=1)'; scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Archaic form of `LOG()' that is specific to one type for X.  *Note
- Log Intrinsic::.
- 
- 
- File: g77.info,  Node: Cmplx Intrinsic,  Next: Complex Intrinsic,  Prev: CLog Intrinsic,  Up: Table of Intrinsic Functions
- 
- Cmplx Intrinsic
- ...............
- 
-      Cmplx(X, Y)
- 
- Cmplx: `COMPLEX(KIND=1)' function.
- 
- X: `INTEGER', `REAL', or `COMPLEX'; scalar; INTENT(IN).
- 
- Y: `INTEGER' or `REAL'; OPTIONAL (must be omitted if X is `COMPLEX');
- scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    If X is not type `COMPLEX', constructs a value of type
- `COMPLEX(KIND=1)' from the real and imaginary values specified by X and
- Y, respectively.  If Y is omitted, `0.' is assumed.
- 
-    If X is type `COMPLEX', converts it to type `COMPLEX(KIND=1)'.
- 
-    *Note Complex Intrinsic::, for information on easily constructing a
- `COMPLEX' value of arbitrary precision from `REAL' arguments.
- 
- 
- File: g77.info,  Node: Complex Intrinsic,  Next: Conjg Intrinsic,  Prev: Cmplx Intrinsic,  Up: Table of Intrinsic Functions
- 
- Complex Intrinsic
- .................
- 
-      Complex(REAL, IMAG)
- 
- Complex: `COMPLEX' function, the exact type being the result of
- cross-promoting the types of all the arguments.
- 
- REAL: `INTEGER' or `REAL'; scalar; INTENT(IN).
- 
- IMAG: `INTEGER' or `REAL'; scalar; INTENT(IN).
- 
- Intrinsic groups: `gnu'.
- 
- Description:
- 
-    Returns a `COMPLEX' value that has `Real' and `Imag' as its real and
- imaginary parts, respectively.
- 
-    If REAL and IMAG are the same type, and that type is not `INTEGER',
- no data conversion is performed, and the type of the resulting value
- has the same kind value as the types of REAL and IMAG.
- 
-    If REAL and IMAG are not the same type, the usual type-promotion
- rules are applied to both, converting either or both to the appropriate
- `REAL' type.  The type of the resulting value has the same kind value
- as the type to which both REAL and IMAG were converted, in this case.
- 
-    If REAL and IMAG are both `INTEGER', they are both converted to
- `REAL(KIND=1)', and the result of the `COMPLEX()' invocation is type
- `COMPLEX(KIND=1)'.
- 
-    _Note:_ The way to do this in standard Fortran 90 is too hairy to
- describe here, but it is important to note that `CMPLX(D1,D2)' returns
- a `COMPLEX(KIND=1)' result even if `D1' and `D2' are type
- `REAL(KIND=2)'.  Hence the availability of `COMPLEX()' in GNU Fortran.
- 
- 
- File: g77.info,  Node: Conjg Intrinsic,  Next: Cos Intrinsic,  Prev: Complex Intrinsic,  Up: Table of Intrinsic Functions
- 
- Conjg Intrinsic
- ...............
- 
-      Conjg(Z)
- 
- Conjg: `COMPLEX' function, the `KIND=' value of the type being that of
- argument Z.
- 
- Z: `COMPLEX'; scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Returns the complex conjugate:
- 
-      COMPLEX(REALPART(Z), -IMAGPART(Z))
- 
- 
- File: g77.info,  Node: Cos Intrinsic,  Next: CosH Intrinsic,  Prev: Conjg Intrinsic,  Up: Table of Intrinsic Functions
- 
- Cos Intrinsic
- .............
- 
-      Cos(X)
- 
- Cos: `REAL' or `COMPLEX' function, the exact type being that of
- argument X.
- 
- X: `REAL' or `COMPLEX'; scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Returns the cosine of X, an angle measured in radians.
- 
-    *Note ACos Intrinsic::, for the inverse of this function.
- 
- 
- File: g77.info,  Node: CosH Intrinsic,  Next: Count Intrinsic,  Prev: Cos Intrinsic,  Up: Table of Intrinsic Functions
- 
- CosH Intrinsic
- ..............
- 
-      CosH(X)
- 
- CosH: `REAL' function, the `KIND=' value of the type being that of
- argument X.
- 
- X: `REAL'; scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Returns the hyperbolic cosine of X.
- 
- 
- File: g77.info,  Node: Count Intrinsic,  Next: CPU_Time Intrinsic,  Prev: CosH Intrinsic,  Up: Table of Intrinsic Functions
- 
- Count Intrinsic
- ...............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL Count' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: CPU_Time Intrinsic,  Next: CShift Intrinsic,  Prev: Count Intrinsic,  Up: Table of Intrinsic Functions
- 
- CPU_Time Intrinsic
- ..................
- 
-      CALL CPU_Time(SECONDS)
- 
- SECONDS: `REAL'; scalar; INTENT(OUT).
- 
- Intrinsic groups: `f90'.
- 
- Description:
- 
-    Returns in SECONDS the current value of the system time.  This
- implementation of the Fortran 95 intrinsic is just an alias for
- `second' *Note Second Intrinsic (subroutine)::.
- 
-    On some systems, the underlying timings are represented using types
- with sufficiently small limits that overflows (wraparounds) are
- possible, such as 32-bit types.  Therefore, the values returned by this
- intrinsic might be, or become, negative, or numerically less than
- previous values, during a single run of the compiled program.
- 
- 
- File: g77.info,  Node: CShift Intrinsic,  Next: CSin Intrinsic,  Prev: CPU_Time Intrinsic,  Up: Table of Intrinsic Functions
- 
- CShift Intrinsic
- ................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL CShift' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: CSin Intrinsic,  Next: CSqRt Intrinsic,  Prev: CShift Intrinsic,  Up: Table of Intrinsic Functions
- 
- CSin Intrinsic
- ..............
- 
-      CSin(X)
- 
- CSin: `COMPLEX(KIND=1)' function.
- 
- X: `COMPLEX(KIND=1)'; scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Archaic form of `SIN()' that is specific to one type for X.  *Note
- Sin Intrinsic::.
- 
- 
- File: g77.info,  Node: CSqRt Intrinsic,  Next: CTime Intrinsic (subroutine),  Prev: CSin Intrinsic,  Up: Table of Intrinsic Functions
- 
- CSqRt Intrinsic
- ...............
- 
-      CSqRt(X)
- 
- CSqRt: `COMPLEX(KIND=1)' function.
- 
- X: `COMPLEX(KIND=1)'; scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Archaic form of `SQRT()' that is specific to one type for X.  *Note
- SqRt Intrinsic::.
- 
- 
- File: g77.info,  Node: CTime Intrinsic (subroutine),  Next: CTime Intrinsic (function),  Prev: CSqRt Intrinsic,  Up: Table of Intrinsic Functions
- 
- CTime Intrinsic (subroutine)
- ............................
- 
-      CALL CTime(STIME, RESULT)
- 
- STIME: `INTEGER'; scalar; INTENT(IN).
- 
- RESULT: `CHARACTER'; scalar; INTENT(OUT).
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Converts STIME, a system time value, such as returned by `TIME8()',
- to a string of the form `Sat Aug 19 18:13:14 1995', and returns that
- string in RESULT.
- 
-    *Note Time8 Intrinsic::.
- 
-    Some non-GNU implementations of Fortran provide this intrinsic as
- only a function, not as a subroutine.
- 
-    For information on other intrinsics with the same name: *Note CTime
- Intrinsic (function)::.
- 
- 
- File: g77.info,  Node: CTime Intrinsic (function),  Next: DAbs Intrinsic,  Prev: CTime Intrinsic (subroutine),  Up: Table of Intrinsic Functions
- 
- CTime Intrinsic (function)
- ..........................
- 
-      CTime(STIME)
- 
- CTime: `CHARACTER*(*)' function.
- 
- STIME: `INTEGER'; scalar; INTENT(IN).
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Converts STIME, a system time value, such as returned by `TIME8()',
- to a string of the form `Sat Aug 19 18:13:14 1995', and returns that
- string as the function value.
- 
-    *Note Time8 Intrinsic::.
- 
-    For information on other intrinsics with the same name: *Note CTime
- Intrinsic (subroutine)::.
- 
- 
- File: g77.info,  Node: DAbs Intrinsic,  Next: DACos Intrinsic,  Prev: CTime Intrinsic (function),  Up: Table of Intrinsic Functions
- 
- DAbs Intrinsic
- ..............
- 
-      DAbs(A)
- 
- DAbs: `REAL(KIND=2)' function.
- 
- A: `REAL(KIND=2)'; scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Archaic form of `ABS()' that is specific to one type for A.  *Note
- Abs Intrinsic::.
- 
- 
- File: g77.info,  Node: DACos Intrinsic,  Next: DASin Intrinsic,  Prev: DAbs Intrinsic,  Up: Table of Intrinsic Functions
- 
- DACos Intrinsic
- ...............
- 
-      DACos(X)
- 
- DACos: `REAL(KIND=2)' function.
- 
- X: `REAL(KIND=2)'; scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Archaic form of `ACOS()' that is specific to one type for X.  *Note
- ACos Intrinsic::.
- 
- 
- File: g77.info,  Node: DASin Intrinsic,  Next: DATan Intrinsic,  Prev: DACos Intrinsic,  Up: Table of Intrinsic Functions
- 
- DASin Intrinsic
- ...............
- 
-      DASin(X)
- 
- DASin: `REAL(KIND=2)' function.
- 
- X: `REAL(KIND=2)'; scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Archaic form of `ASIN()' that is specific to one type for X.  *Note
- ASin Intrinsic::.
- 
- 
- File: g77.info,  Node: DATan Intrinsic,  Next: DATan2 Intrinsic,  Prev: DASin Intrinsic,  Up: Table of Intrinsic Functions
- 
- DATan Intrinsic
- ...............
- 
-      DATan(X)
- 
- DATan: `REAL(KIND=2)' function.
- 
- X: `REAL(KIND=2)'; scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Archaic form of `ATAN()' that is specific to one type for X.  *Note
- ATan Intrinsic::.
- 
- 
- File: g77.info,  Node: DATan2 Intrinsic,  Next: Date_and_Time Intrinsic,  Prev: DATan Intrinsic,  Up: Table of Intrinsic Functions
- 
- DATan2 Intrinsic
- ................
- 
-      DATan2(Y, X)
- 
- DATan2: `REAL(KIND=2)' function.
- 
- Y: `REAL(KIND=2)'; scalar; INTENT(IN).
- 
- X: `REAL(KIND=2)'; scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Archaic form of `ATAN2()' that is specific to one type for Y and X.
- *Note ATan2 Intrinsic::.
- 
- 
- File: g77.info,  Node: Date_and_Time Intrinsic,  Next: DbesJ0 Intrinsic,  Prev: DATan2 Intrinsic,  Up: Table of Intrinsic Functions
- 
- Date_and_Time Intrinsic
- .......................
- 
-      CALL Date_and_Time(DATE, TIME, ZONE, VALUES)
- 
- DATE: `CHARACTER'; scalar; INTENT(OUT).
- 
- TIME: `CHARACTER'; OPTIONAL; scalar; INTENT(OUT).
- 
- ZONE: `CHARACTER'; OPTIONAL; scalar; INTENT(OUT).
- 
- VALUES: `INTEGER(KIND=1)'; OPTIONAL; DIMENSION(8); INTENT(OUT).
- 
- Intrinsic groups: `f90'.
- 
- Description:
- 
-    Returns:
- DATE
-      The date in the form CCYYMMDD: century, year, month and day;
- 
- TIME
-      The time in the form `HHMMSS.SS': hours, minutes, seconds and
-      milliseconds;
- 
- ZONE
-      The difference between local time and UTC (GMT) in the form SHHMM:
-      sign, hours and minutes, e.g. `-0500' (winter in New York);
- 
- VALUES
-      The year, month of the year, day of the month, time difference in
-      minutes from UTC, hour of the day, minutes of the hour, seconds of
-      the minute, and milliseconds of the second in successive values of
-      the array.
- 
-    Programs making use of this intrinsic might not be Year 10000 (Y10K)
- compliant.  For example, the date might appear, to such programs, to
- wrap around (change from a larger value to a smaller one) as of the
- Year 10000.
- 
-    On systems where a millisecond timer isn't available, the millisecond
- value is returned as zero.
- 
- 
- File: g77.info,  Node: DbesJ0 Intrinsic,  Next: DbesJ1 Intrinsic,  Prev: Date_and_Time Intrinsic,  Up: Table of Intrinsic Functions
- 
- DbesJ0 Intrinsic
- ................
- 
-      DbesJ0(X)
- 
- DbesJ0: `REAL(KIND=2)' function.
- 
- X: `REAL(KIND=2)'; scalar; INTENT(IN).
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Archaic form of `BESJ0()' that is specific to one type for X.  *Note
- BesJ0 Intrinsic::.
- 
- 
- File: g77.info,  Node: DbesJ1 Intrinsic,  Next: DbesJN Intrinsic,  Prev: DbesJ0 Intrinsic,  Up: Table of Intrinsic Functions
- 
- DbesJ1 Intrinsic
- ................
- 
-      DbesJ1(X)
- 
- DbesJ1: `REAL(KIND=2)' function.
- 
- X: `REAL(KIND=2)'; scalar; INTENT(IN).
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Archaic form of `BESJ1()' that is specific to one type for X.  *Note
- BesJ1 Intrinsic::.
- 
- 
- File: g77.info,  Node: DbesJN Intrinsic,  Next: DbesY0 Intrinsic,  Prev: DbesJ1 Intrinsic,  Up: Table of Intrinsic Functions
- 
- DbesJN Intrinsic
- ................
- 
-      DbesJN(N, X)
- 
- DbesJN: `REAL(KIND=2)' function.
- 
- N: `INTEGER' not wider than the default kind; scalar; INTENT(IN).
- 
- X: `REAL(KIND=2)'; scalar; INTENT(IN).
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Archaic form of `BESJN()' that is specific to one type for X.  *Note
- BesJN Intrinsic::.
- 
- 
- File: g77.info,  Node: DbesY0 Intrinsic,  Next: DbesY1 Intrinsic,  Prev: DbesJN Intrinsic,  Up: Table of Intrinsic Functions
- 
- DbesY0 Intrinsic
- ................
- 
-      DbesY0(X)
- 
- DbesY0: `REAL(KIND=2)' function.
- 
- X: `REAL(KIND=2)'; scalar; INTENT(IN).
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Archaic form of `BESY0()' that is specific to one type for X.  *Note
- BesY0 Intrinsic::.
- 
- 
- File: g77.info,  Node: DbesY1 Intrinsic,  Next: DbesYN Intrinsic,  Prev: DbesY0 Intrinsic,  Up: Table of Intrinsic Functions
- 
- DbesY1 Intrinsic
- ................
- 
-      DbesY1(X)
- 
- DbesY1: `REAL(KIND=2)' function.
- 
- X: `REAL(KIND=2)'; scalar; INTENT(IN).
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Archaic form of `BESY1()' that is specific to one type for X.  *Note
- BesY1 Intrinsic::.
- 
- 
- File: g77.info,  Node: DbesYN Intrinsic,  Next: Dble Intrinsic,  Prev: DbesY1 Intrinsic,  Up: Table of Intrinsic Functions
- 
- DbesYN Intrinsic
- ................
- 
-      DbesYN(N, X)
- 
- DbesYN: `REAL(KIND=2)' function.
- 
- N: `INTEGER' not wider than the default kind; scalar; INTENT(IN).
- 
- X: `REAL(KIND=2)'; scalar; INTENT(IN).
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Archaic form of `BESYN()' that is specific to one type for X.  *Note
- BesYN Intrinsic::.
- 
- 
- File: g77.info,  Node: Dble Intrinsic,  Next: DCos Intrinsic,  Prev: DbesYN Intrinsic,  Up: Table of Intrinsic Functions
- 
- Dble Intrinsic
- ..............
- 
-      Dble(A)
- 
- Dble: `REAL(KIND=2)' function.
- 
- A: `INTEGER', `REAL', or `COMPLEX'; scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Returns A converted to double precision (`REAL(KIND=2)').  If A is
- `COMPLEX', the real part of A is used for the conversion and the
- imaginary part disregarded.
- 
-    *Note Sngl Intrinsic::, for the function that converts to single
- precision.
- 
-    *Note Int Intrinsic::, for the function that converts to `INTEGER'.
- 
-    *Note Complex Intrinsic::, for the function that converts to
- `COMPLEX'.
- 
- 
- File: g77.info,  Node: DCos Intrinsic,  Next: DCosH Intrinsic,  Prev: Dble Intrinsic,  Up: Table of Intrinsic Functions
- 
- DCos Intrinsic
- ..............
- 
-      DCos(X)
- 
- DCos: `REAL(KIND=2)' function.
- 
- X: `REAL(KIND=2)'; scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Archaic form of `COS()' that is specific to one type for X.  *Note
- Cos Intrinsic::.
- 
- 
- File: g77.info,  Node: DCosH Intrinsic,  Next: DDiM Intrinsic,  Prev: DCos Intrinsic,  Up: Table of Intrinsic Functions
- 
- DCosH Intrinsic
- ...............
- 
-      DCosH(X)
- 
- DCosH: `REAL(KIND=2)' function.
- 
- X: `REAL(KIND=2)'; scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Archaic form of `COSH()' that is specific to one type for X.  *Note
- CosH Intrinsic::.
- 
- 
- File: g77.info,  Node: DDiM Intrinsic,  Next: DErF Intrinsic,  Prev: DCosH Intrinsic,  Up: Table of Intrinsic Functions
- 
- DDiM Intrinsic
- ..............
- 
-      DDiM(X, Y)
- 
- DDiM: `REAL(KIND=2)' function.
- 
- X: `REAL(KIND=2)'; scalar; INTENT(IN).
- 
- Y: `REAL(KIND=2)'; scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Archaic form of `DIM()' that is specific to one type for X and Y.
- *Note DiM Intrinsic::.
- 
- 
- File: g77.info,  Node: DErF Intrinsic,  Next: DErFC Intrinsic,  Prev: DDiM Intrinsic,  Up: Table of Intrinsic Functions
- 
- DErF Intrinsic
- ..............
- 
-      DErF(X)
- 
- DErF: `REAL(KIND=2)' function.
- 
- X: `REAL(KIND=2)'; scalar; INTENT(IN).
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Archaic form of `ERF()' that is specific to one type for X.  *Note
- ErF Intrinsic::.
- 
- 
- File: g77.info,  Node: DErFC Intrinsic,  Next: DExp Intrinsic,  Prev: DErF Intrinsic,  Up: Table of Intrinsic Functions
- 
- DErFC Intrinsic
- ...............
- 
-      DErFC(X)
- 
- DErFC: `REAL(KIND=2)' function.
- 
- X: `REAL(KIND=2)'; scalar; INTENT(IN).
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Archaic form of `ERFC()' that is specific to one type for X.  *Note
- ErFC Intrinsic::.
- 
- 
- File: g77.info,  Node: DExp Intrinsic,  Next: Digits Intrinsic,  Prev: DErFC Intrinsic,  Up: Table of Intrinsic Functions
- 
- DExp Intrinsic
- ..............
- 
-      DExp(X)
- 
- DExp: `REAL(KIND=2)' function.
- 
- X: `REAL(KIND=2)'; scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Archaic form of `EXP()' that is specific to one type for X.  *Note
- Exp Intrinsic::.
- 
- 
- File: g77.info,  Node: Digits Intrinsic,  Next: DiM Intrinsic,  Prev: DExp Intrinsic,  Up: Table of Intrinsic Functions
- 
- Digits Intrinsic
- ................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL Digits' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: DiM Intrinsic,  Next: DInt Intrinsic,  Prev: Digits Intrinsic,  Up: Table of Intrinsic Functions
- 
- DiM Intrinsic
- .............
- 
-      DiM(X, Y)
- 
- DiM: `INTEGER' or `REAL' function, the exact type being the result of
- cross-promoting the types of all the arguments.
- 
- X: `INTEGER' or `REAL'; scalar; INTENT(IN).
- 
- Y: `INTEGER' or `REAL'; scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Returns `X-Y' if X is greater than Y; otherwise returns zero.
- 
- 
- File: g77.info,  Node: DInt Intrinsic,  Next: DLog Intrinsic,  Prev: DiM Intrinsic,  Up: Table of Intrinsic Functions
- 
- DInt Intrinsic
- ..............
- 
-      DInt(A)
- 
- DInt: `REAL(KIND=2)' function.
- 
- A: `REAL(KIND=2)'; scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Archaic form of `AINT()' that is specific to one type for A.  *Note
- AInt Intrinsic::.
- 
- 
- File: g77.info,  Node: DLog Intrinsic,  Next: DLog10 Intrinsic,  Prev: DInt Intrinsic,  Up: Table of Intrinsic Functions
- 
- DLog Intrinsic
- ..............
- 
-      DLog(X)
- 
- DLog: `REAL(KIND=2)' function.
- 
- X: `REAL(KIND=2)'; scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Archaic form of `LOG()' that is specific to one type for X.  *Note
- Log Intrinsic::.
- 
- 
- File: g77.info,  Node: DLog10 Intrinsic,  Next: DMax1 Intrinsic,  Prev: DLog Intrinsic,  Up: Table of Intrinsic Functions
- 
- DLog10 Intrinsic
- ................
- 
-      DLog10(X)
- 
- DLog10: `REAL(KIND=2)' function.
- 
- X: `REAL(KIND=2)'; scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Archaic form of `LOG10()' that is specific to one type for X.  *Note
- Log10 Intrinsic::.
- 
- 
- File: g77.info,  Node: DMax1 Intrinsic,  Next: DMin1 Intrinsic,  Prev: DLog10 Intrinsic,  Up: Table of Intrinsic Functions
- 
- DMax1 Intrinsic
- ...............
- 
-      DMax1(A-1, A-2, ..., A-n)
- 
- DMax1: `REAL(KIND=2)' function.
- 
- A: `REAL(KIND=2)'; at least two such arguments must be provided;
- scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Archaic form of `MAX()' that is specific to one type for A.  *Note
- Max Intrinsic::.
- 
- 
- File: g77.info,  Node: DMin1 Intrinsic,  Next: DMod Intrinsic,  Prev: DMax1 Intrinsic,  Up: Table of Intrinsic Functions
- 
- DMin1 Intrinsic
- ...............
- 
-      DMin1(A-1, A-2, ..., A-n)
- 
- DMin1: `REAL(KIND=2)' function.
- 
- A: `REAL(KIND=2)'; at least two such arguments must be provided;
- scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Archaic form of `MIN()' that is specific to one type for A.  *Note
- Min Intrinsic::.
- 
- 
- File: g77.info,  Node: DMod Intrinsic,  Next: DNInt Intrinsic,  Prev: DMin1 Intrinsic,  Up: Table of Intrinsic Functions
- 
- DMod Intrinsic
- ..............
- 
-      DMod(A, P)
- 
- DMod: `REAL(KIND=2)' function.
- 
- A: `REAL(KIND=2)'; scalar; INTENT(IN).
- 
- P: `REAL(KIND=2)'; scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Archaic form of `MOD()' that is specific to one type for A.  *Note
- Mod Intrinsic::.
- 
- 
- File: g77.info,  Node: DNInt Intrinsic,  Next: Dot_Product Intrinsic,  Prev: DMod Intrinsic,  Up: Table of Intrinsic Functions
- 
- DNInt Intrinsic
- ...............
- 
-      DNInt(A)
- 
- DNInt: `REAL(KIND=2)' function.
- 
- A: `REAL(KIND=2)'; scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Archaic form of `ANINT()' that is specific to one type for A.  *Note
- ANInt Intrinsic::.
- 
- 
- File: g77.info,  Node: Dot_Product Intrinsic,  Next: DProd Intrinsic,  Prev: DNInt Intrinsic,  Up: Table of Intrinsic Functions
- 
- Dot_Product Intrinsic
- .....................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL Dot_Product' to use this name
- for an external procedure.
- 
- 
- File: g77.info,  Node: DProd Intrinsic,  Next: DSign Intrinsic,  Prev: Dot_Product Intrinsic,  Up: Table of Intrinsic Functions
- 
- DProd Intrinsic
- ...............
- 
-      DProd(X, Y)
- 
- DProd: `REAL(KIND=2)' function.
- 
- X: `REAL(KIND=1)'; scalar; INTENT(IN).
- 
- Y: `REAL(KIND=1)'; scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Returns `DBLE(X)*DBLE(Y)'.
- 
- 
- File: g77.info,  Node: DSign Intrinsic,  Next: DSin Intrinsic,  Prev: DProd Intrinsic,  Up: Table of Intrinsic Functions
- 
- DSign Intrinsic
- ...............
- 
-      DSign(A, B)
- 
- DSign: `REAL(KIND=2)' function.
- 
- A: `REAL(KIND=2)'; scalar; INTENT(IN).
- 
- B: `REAL(KIND=2)'; scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Archaic form of `SIGN()' that is specific to one type for A and B.
- *Note Sign Intrinsic::.
- 
- 
- File: g77.info,  Node: DSin Intrinsic,  Next: DSinH Intrinsic,  Prev: DSign Intrinsic,  Up: Table of Intrinsic Functions
- 
- DSin Intrinsic
- ..............
- 
-      DSin(X)
- 
- DSin: `REAL(KIND=2)' function.
- 
- X: `REAL(KIND=2)'; scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Archaic form of `SIN()' that is specific to one type for X.  *Note
- Sin Intrinsic::.
- 
- 
- File: g77.info,  Node: DSinH Intrinsic,  Next: DSqRt Intrinsic,  Prev: DSin Intrinsic,  Up: Table of Intrinsic Functions
- 
- DSinH Intrinsic
- ...............
- 
-      DSinH(X)
- 
- DSinH: `REAL(KIND=2)' function.
- 
- X: `REAL(KIND=2)'; scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Archaic form of `SINH()' that is specific to one type for X.  *Note
- SinH Intrinsic::.
- 
- 
- File: g77.info,  Node: DSqRt Intrinsic,  Next: DTan Intrinsic,  Prev: DSinH Intrinsic,  Up: Table of Intrinsic Functions
- 
- DSqRt Intrinsic
- ...............
- 
-      DSqRt(X)
- 
- DSqRt: `REAL(KIND=2)' function.
- 
- X: `REAL(KIND=2)'; scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Archaic form of `SQRT()' that is specific to one type for X.  *Note
- SqRt Intrinsic::.
- 
- 
- File: g77.info,  Node: DTan Intrinsic,  Next: DTanH Intrinsic,  Prev: DSqRt Intrinsic,  Up: Table of Intrinsic Functions
- 
- DTan Intrinsic
- ..............
- 
-      DTan(X)
- 
- DTan: `REAL(KIND=2)' function.
- 
- X: `REAL(KIND=2)'; scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Archaic form of `TAN()' that is specific to one type for X.  *Note
- Tan Intrinsic::.
- 
- 
- File: g77.info,  Node: DTanH Intrinsic,  Next: DTime Intrinsic (subroutine),  Prev: DTan Intrinsic,  Up: Table of Intrinsic Functions
- 
- DTanH Intrinsic
- ...............
- 
-      DTanH(X)
- 
- DTanH: `REAL(KIND=2)' function.
- 
- X: `REAL(KIND=2)'; scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Archaic form of `TANH()' that is specific to one type for X.  *Note
- TanH Intrinsic::.
- 
- 
- File: g77.info,  Node: DTime Intrinsic (subroutine),  Next: EOShift Intrinsic,  Prev: DTanH Intrinsic,  Up: Table of Intrinsic Functions
- 
- DTime Intrinsic (subroutine)
- ............................
- 
-      CALL DTime(TARRAY, RESULT)
- 
- TARRAY: `REAL(KIND=1)'; DIMENSION(2); INTENT(OUT).
- 
- RESULT: `REAL(KIND=1)'; scalar; INTENT(OUT).
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Initially, return the number of seconds of runtime since the start
- of the process's execution in RESULT, and the user and system
- components of this in `TARRAY(1)' and `TARRAY(2)' respectively.  The
- value of RESULT is equal to `TARRAY(1) + TARRAY(2)'.
- 
-    Subsequent invocations of `DTIME()' set values based on accumulations
- since the previous invocation.
- 
-    On some systems, the underlying timings are represented using types
- with sufficiently small limits that overflows (wraparounds) are
- possible, such as 32-bit types.  Therefore, the values returned by this
- intrinsic might be, or become, negative, or numerically less than
- previous values, during a single run of the compiled program.
- 
-    Some non-GNU implementations of Fortran provide this intrinsic as
- only a function, not as a subroutine.
- 
-    For information on other intrinsics with the same name: *Note DTime
- Intrinsic (function)::.
- 
- 
- File: g77.info,  Node: EOShift Intrinsic,  Next: Epsilon Intrinsic,  Prev: DTime Intrinsic (subroutine),  Up: Table of Intrinsic Functions
- 
- EOShift Intrinsic
- .................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL EOShift' to use this name for
- an external procedure.
- 
- 
- File: g77.info,  Node: Epsilon Intrinsic,  Next: ErF Intrinsic,  Prev: EOShift Intrinsic,  Up: Table of Intrinsic Functions
- 
- Epsilon Intrinsic
- .................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL Epsilon' to use this name for
- an external procedure.
- 
- 
- File: g77.info,  Node: ErF Intrinsic,  Next: ErFC Intrinsic,  Prev: Epsilon Intrinsic,  Up: Table of Intrinsic Functions
- 
- ErF Intrinsic
- .............
- 
-      ErF(X)
- 
- ErF: `REAL' function, the `KIND=' value of the type being that of
- argument X.
- 
- X: `REAL'; scalar; INTENT(IN).
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Returns the error function of X.  See `erf(3m)', which provides the
- implementation.
- 
- 
- File: g77.info,  Node: ErFC Intrinsic,  Next: ETime Intrinsic (subroutine),  Prev: ErF Intrinsic,  Up: Table of Intrinsic Functions
- 
- ErFC Intrinsic
- ..............
- 
-      ErFC(X)
- 
- ErFC: `REAL' function, the `KIND=' value of the type being that of
- argument X.
- 
- X: `REAL'; scalar; INTENT(IN).
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Returns the complementary error function of X: `ERFC(R) = 1 -
- ERF(R)' (except that the result might be more accurate than explicitly
- evaluating that formulae would give).  See `erfc(3m)', which provides
- the implementation.
- 
- 
- File: g77.info,  Node: ETime Intrinsic (subroutine),  Next: ETime Intrinsic (function),  Prev: ErFC Intrinsic,  Up: Table of Intrinsic Functions
- 
- ETime Intrinsic (subroutine)
- ............................
- 
-      CALL ETime(TARRAY, RESULT)
- 
- TARRAY: `REAL(KIND=1)'; DIMENSION(2); INTENT(OUT).
- 
- RESULT: `REAL(KIND=1)'; scalar; INTENT(OUT).
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Return the number of seconds of runtime since the start of the
- process's execution in RESULT, and the user and system components of
- this in `TARRAY(1)' and `TARRAY(2)' respectively.  The value of RESULT
- is equal to `TARRAY(1) + TARRAY(2)'.
- 
-    On some systems, the underlying timings are represented using types
- with sufficiently small limits that overflows (wraparounds) are
- possible, such as 32-bit types.  Therefore, the values returned by this
- intrinsic might be, or become, negative, or numerically less than
- previous values, during a single run of the compiled program.
- 
-    Some non-GNU implementations of Fortran provide this intrinsic as
- only a function, not as a subroutine.
- 
-    For information on other intrinsics with the same name: *Note ETime
- Intrinsic (function)::.
- 
- 
- File: g77.info,  Node: ETime Intrinsic (function),  Next: Exit Intrinsic,  Prev: ETime Intrinsic (subroutine),  Up: Table of Intrinsic Functions
- 
- ETime Intrinsic (function)
- ..........................
- 
-      ETime(TARRAY)
- 
- ETime: `REAL(KIND=1)' function.
- 
- TARRAY: `REAL(KIND=1)'; DIMENSION(2); INTENT(OUT).
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Return the number of seconds of runtime since the start of the
- process's execution as the function value, and the user and system
- components of this in `TARRAY(1)' and `TARRAY(2)' respectively.  The
- functions' value is equal to `TARRAY(1) + TARRAY(2)'.
- 
-    On some systems, the underlying timings are represented using types
- with sufficiently small limits that overflows (wraparounds) are
- possible, such as 32-bit types.  Therefore, the values returned by this
- intrinsic might be, or become, negative, or numerically less than
- previous values, during a single run of the compiled program.
- 
-    For information on other intrinsics with the same name: *Note ETime
- Intrinsic (subroutine)::.
- 
- 
- File: g77.info,  Node: Exit Intrinsic,  Next: Exp Intrinsic,  Prev: ETime Intrinsic (function),  Up: Table of Intrinsic Functions
- 
- Exit Intrinsic
- ..............
- 
-      CALL Exit(STATUS)
- 
- STATUS: `INTEGER' not wider than the default kind; OPTIONAL; scalar;
- INTENT(IN).
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Exit the program with status STATUS after closing open Fortran I/O
- units and otherwise behaving as `exit(2)'.  If STATUS is omitted the
- canonical `success' value will be returned to the system.
- 
- 
- File: g77.info,  Node: Exp Intrinsic,  Next: Exponent Intrinsic,  Prev: Exit Intrinsic,  Up: Table of Intrinsic Functions
- 
- Exp Intrinsic
- .............
- 
-      Exp(X)
- 
- Exp: `REAL' or `COMPLEX' function, the exact type being that of
- argument X.
- 
- X: `REAL' or `COMPLEX'; scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Returns `E**X', where E is approximately 2.7182818.
- 
-    *Note Log Intrinsic::, for the inverse of this function.
- 
- 
- File: g77.info,  Node: Exponent Intrinsic,  Next: FDate Intrinsic (subroutine),  Prev: Exp Intrinsic,  Up: Table of Intrinsic Functions
- 
- Exponent Intrinsic
- ..................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL Exponent' to use this name for
- an external procedure.
- 
- 
- File: g77.info,  Node: FDate Intrinsic (subroutine),  Next: FDate Intrinsic (function),  Prev: Exponent Intrinsic,  Up: Table of Intrinsic Functions
- 
- FDate Intrinsic (subroutine)
- ............................
- 
-      CALL FDate(DATE)
- 
- DATE: `CHARACTER'; scalar; INTENT(OUT).
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Returns the current date (using the same format as `CTIME()') in
- DATE.
- 
-    Equivalent to:
- 
-      CALL CTIME(DATE, TIME8())
- 
-    Programs making use of this intrinsic might not be Year 10000 (Y10K)
- compliant.  For example, the date might appear, to such programs, to
- wrap around (change from a larger value to a smaller one) as of the
- Year 10000.
- 
-    *Note CTime Intrinsic (subroutine)::.
- 
-    Some non-GNU implementations of Fortran provide this intrinsic as
- only a function, not as a subroutine.
- 
-    For information on other intrinsics with the same name: *Note FDate
- Intrinsic (function)::.
- 
- 
- File: g77.info,  Node: FDate Intrinsic (function),  Next: FGet Intrinsic (subroutine),  Prev: FDate Intrinsic (subroutine),  Up: Table of Intrinsic Functions
- 
- FDate Intrinsic (function)
- ..........................
- 
-      FDate()
- 
- FDate: `CHARACTER*(*)' function.
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Returns the current date (using the same format as `CTIME()').
- 
-    Equivalent to:
- 
-      CTIME(TIME8())
- 
-    Programs making use of this intrinsic might not be Year 10000 (Y10K)
- compliant.  For example, the date might appear, to such programs, to
- wrap around (change from a larger value to a smaller one) as of the
- Year 10000.
- 
-    *Note CTime Intrinsic (function)::.
- 
-    For information on other intrinsics with the same name: *Note FDate
- Intrinsic (subroutine)::.
- 
- 
- File: g77.info,  Node: FGet Intrinsic (subroutine),  Next: FGetC Intrinsic (subroutine),  Prev: FDate Intrinsic (function),  Up: Table of Intrinsic Functions
- 
- FGet Intrinsic (subroutine)
- ...........................
- 
-      CALL FGet(C, STATUS)
- 
- C: `CHARACTER'; scalar; INTENT(OUT).
- 
- STATUS: `INTEGER(KIND=1)'; OPTIONAL; scalar; INTENT(OUT).
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Reads a single character into C in stream mode from unit 5
- (by-passing normal formatted output) using `getc(3)'.  Returns in
- STATUS 0 on success, -1 on end-of-file, and the error code from
- `ferror(3)' otherwise.
- 
-    Stream I/O should not be mixed with normal record-oriented
- (formatted or unformatted) I/O on the same unit; the results are
- unpredictable.
- 
-    For information on other intrinsics with the same name: *Note FGet
- Intrinsic (function)::.
- 
- 
- File: g77.info,  Node: FGetC Intrinsic (subroutine),  Next: Float Intrinsic,  Prev: FGet Intrinsic (subroutine),  Up: Table of Intrinsic Functions
- 
- FGetC Intrinsic (subroutine)
- ............................
- 
-      CALL FGetC(UNIT, C, STATUS)
- 
- UNIT: `INTEGER'; scalar; INTENT(IN).
- 
- C: `CHARACTER'; scalar; INTENT(OUT).
- 
- STATUS: `INTEGER(KIND=1)'; OPTIONAL; scalar; INTENT(OUT).
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Reads a single character into C in stream mode from unit UNIT
- (by-passing normal formatted output) using `getc(3)'.  Returns in
- STATUS 0 on success, -1 on end-of-file, and the error code from
- `ferror(3)' otherwise.
- 
-    Stream I/O should not be mixed with normal record-oriented
- (formatted or unformatted) I/O on the same unit; the results are
- unpredictable.
- 
-    For information on other intrinsics with the same name: *Note FGetC
- Intrinsic (function)::.
- 
- 
- File: g77.info,  Node: Float Intrinsic,  Next: Floor Intrinsic,  Prev: FGetC Intrinsic (subroutine),  Up: Table of Intrinsic Functions
- 
- Float Intrinsic
- ...............
- 
-      Float(A)
- 
- Float: `REAL(KIND=1)' function.
- 
- A: `INTEGER'; scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Archaic form of `REAL()' that is specific to one type for A.  *Note
- Real Intrinsic::.
- 
- 
- File: g77.info,  Node: Floor Intrinsic,  Next: Flush Intrinsic,  Prev: Float Intrinsic,  Up: Table of Intrinsic Functions
- 
- Floor Intrinsic
- ...............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL Floor' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: Flush Intrinsic,  Next: FNum Intrinsic,  Prev: Floor Intrinsic,  Up: Table of Intrinsic Functions
- 
- Flush Intrinsic
- ...............
- 
-      CALL Flush(UNIT)
- 
- UNIT: `INTEGER'; OPTIONAL; scalar; INTENT(IN).
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Flushes Fortran unit(s) currently open for output.  Without the
- optional argument, all such units are flushed, otherwise just the unit
- specified by UNIT.
- 
-    Some non-GNU implementations of Fortran provide this intrinsic as a
- library procedure that might or might not support the (optional) UNIT
- argument.
- 
- 
- File: g77.info,  Node: FNum Intrinsic,  Next: FPut Intrinsic (subroutine),  Prev: Flush Intrinsic,  Up: Table of Intrinsic Functions
- 
- FNum Intrinsic
- ..............
- 
-      FNum(UNIT)
- 
- FNum: `INTEGER(KIND=1)' function.
- 
- UNIT: `INTEGER'; scalar; INTENT(IN).
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Returns the Unix file descriptor number corresponding to the open
- Fortran I/O unit UNIT.  This could be passed to an interface to C I/O
- routines.
- 
- 
- File: g77.info,  Node: FPut Intrinsic (subroutine),  Next: FPutC Intrinsic (subroutine),  Prev: FNum Intrinsic,  Up: Table of Intrinsic Functions
- 
- FPut Intrinsic (subroutine)
- ...........................
- 
-      CALL FPut(C, STATUS)
- 
- C: `CHARACTER'; scalar; INTENT(IN).
- 
- STATUS: `INTEGER(KIND=1)'; OPTIONAL; scalar; INTENT(OUT).
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Writes the single character C in stream mode to unit 6 (by-passing
- normal formatted output) using `putc(3)'.  Returns in STATUS 0 on
- success, the error code from `ferror(3)' otherwise.
- 
-    Stream I/O should not be mixed with normal record-oriented
- (formatted or unformatted) I/O on the same unit; the results are
- unpredictable.
- 
-    For information on other intrinsics with the same name: *Note FPut
- Intrinsic (function)::.
- 
- 
- File: g77.info,  Node: FPutC Intrinsic (subroutine),  Next: Fraction Intrinsic,  Prev: FPut Intrinsic (subroutine),  Up: Table of Intrinsic Functions
- 
- FPutC Intrinsic (subroutine)
- ............................
- 
-      CALL FPutC(UNIT, C, STATUS)
- 
- UNIT: `INTEGER'; scalar; INTENT(IN).
- 
- C: `CHARACTER'; scalar; INTENT(IN).
- 
- STATUS: `INTEGER(KIND=1)'; OPTIONAL; scalar; INTENT(OUT).
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Writes the single character UNIT in stream mode to unit 6
- (by-passing normal formatted output) using `putc(3)'.  Returns in C 0
- on success, the error code from `ferror(3)' otherwise.
- 
-    Stream I/O should not be mixed with normal record-oriented
- (formatted or unformatted) I/O on the same unit; the results are
- unpredictable.
- 
-    For information on other intrinsics with the same name: *Note FPutC
- Intrinsic (function)::.
- 
- 
- File: g77.info,  Node: Fraction Intrinsic,  Next: FSeek Intrinsic,  Prev: FPutC Intrinsic (subroutine),  Up: Table of Intrinsic Functions
- 
- Fraction Intrinsic
- ..................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL Fraction' to use this name for
- an external procedure.
- 
- 
- File: g77.info,  Node: FSeek Intrinsic,  Next: FStat Intrinsic (subroutine),  Prev: Fraction Intrinsic,  Up: Table of Intrinsic Functions
- 
- FSeek Intrinsic
- ...............
- 
-      CALL FSeek(UNIT, OFFSET, WHENCE, ERRLAB)
- 
- UNIT: `INTEGER'; scalar; INTENT(IN).
- 
- OFFSET: `INTEGER'; scalar; INTENT(IN).
- 
- WHENCE: `INTEGER'; scalar; INTENT(IN).
- 
- ERRLAB: `*LABEL', where LABEL is the label of an executable statement;
- OPTIONAL.
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Attempts to move Fortran unit UNIT to the specified OFFSET: absolute
- offset if WHENCE=0; relative to the current offset if WHENCE=1;
- relative to the end of the file if WHENCE=2.  It branches to label
- ERRLAB if UNIT is not open or if the call otherwise fails.
- 
- 
- File: g77.info,  Node: FStat Intrinsic (subroutine),  Next: FStat Intrinsic (function),  Prev: FSeek Intrinsic,  Up: Table of Intrinsic Functions
- 
- FStat Intrinsic (subroutine)
- ............................
- 
-      CALL FStat(UNIT, SARRAY, STATUS)
- 
- UNIT: `INTEGER'; scalar; INTENT(IN).
- 
- SARRAY: `INTEGER(KIND=1)'; DIMENSION(13); INTENT(OUT).
- 
- STATUS: `INTEGER(KIND=1)'; OPTIONAL; scalar; INTENT(OUT).
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Obtains data about the file open on Fortran I/O unit UNIT and places
- them in the array SARRAY.  The values in this array are extracted from
- the `stat' structure as returned by `fstat(2)' q.v., as follows:
- 
-   1. Device ID
- 
-   2. Inode number
- 
-   3. File mode
- 
-   4. Number of links
- 
-   5. Owner's uid
- 
-   6. Owner's gid
- 
-   7. ID of device containing directory entry for file (0 if not
-      available)
- 
-   8. File size (bytes)
- 
-   9. Last access time
- 
-  10. Last modification time
- 
-  11. Last file status change time
- 
-  12. Preferred I/O block size (-1 if not available)
- 
-  13. Number of blocks allocated (-1 if not available)
- 
-    Not all these elements are relevant on all systems.  If an element
- is not relevant, it is returned as 0.
- 
-    If the STATUS argument is supplied, it contains 0 on success or a
- non-zero error code upon return.
- 
-    Some non-GNU implementations of Fortran provide this intrinsic as
- only a function, not as a subroutine, or do not support the (optional)
- STATUS argument.
- 
-    For information on other intrinsics with the same name: *Note FStat
- Intrinsic (function)::.
- 
- 
- File: g77.info,  Node: FStat Intrinsic (function),  Next: FTell Intrinsic (subroutine),  Prev: FStat Intrinsic (subroutine),  Up: Table of Intrinsic Functions
- 
- FStat Intrinsic (function)
- ..........................
- 
-      FStat(UNIT, SARRAY)
- 
- FStat: `INTEGER(KIND=1)' function.
- 
- UNIT: `INTEGER'; scalar; INTENT(IN).
- 
- SARRAY: `INTEGER(KIND=1)'; DIMENSION(13); INTENT(OUT).
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Obtains data about the file open on Fortran I/O unit UNIT and places
- them in the array SARRAY.  The values in this array are extracted from
- the `stat' structure as returned by `fstat(2)' q.v., as follows:
- 
-   1. Device ID
- 
-   2. Inode number
- 
-   3. File mode
- 
-   4. Number of links
- 
-   5. Owner's uid
- 
-   6. Owner's gid
- 
-   7. ID of device containing directory entry for file (0 if not
-      available)
- 
-   8. File size (bytes)
- 
-   9. Last access time
- 
-  10. Last modification time
- 
-  11. Last file status change time
- 
-  12. Preferred I/O block size (-1 if not available)
- 
-  13. Number of blocks allocated (-1 if not available)
- 
-    Not all these elements are relevant on all systems.  If an element
- is not relevant, it is returned as 0.
- 
-    Returns 0 on success or a non-zero error code.
- 
-    For information on other intrinsics with the same name: *Note FStat
- Intrinsic (subroutine)::.
- 
- 
- File: g77.info,  Node: FTell Intrinsic (subroutine),  Next: FTell Intrinsic (function),  Prev: FStat Intrinsic (function),  Up: Table of Intrinsic Functions
- 
- FTell Intrinsic (subroutine)
- ............................
- 
-      CALL FTell(UNIT, OFFSET)
- 
- UNIT: `INTEGER'; scalar; INTENT(IN).
- 
- OFFSET: `INTEGER(KIND=1)'; scalar; INTENT(OUT).
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Sets OFFSET to the current offset of Fortran unit UNIT (or to -1 if
- UNIT is not open).
- 
-    Some non-GNU implementations of Fortran provide this intrinsic as
- only a function, not as a subroutine.
- 
-    For information on other intrinsics with the same name: *Note FTell
- Intrinsic (function)::.
- 
- 
- File: g77.info,  Node: FTell Intrinsic (function),  Next: GError Intrinsic,  Prev: FTell Intrinsic (subroutine),  Up: Table of Intrinsic Functions
- 
- FTell Intrinsic (function)
- ..........................
- 
-      FTell(UNIT)
- 
- FTell: `INTEGER(KIND=1)' function.
- 
- UNIT: `INTEGER'; scalar; INTENT(IN).
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Returns the current offset of Fortran unit UNIT (or -1 if UNIT is
- not open).
- 
-    For information on other intrinsics with the same name: *Note FTell
- Intrinsic (subroutine)::.
- 
- 
- File: g77.info,  Node: GError Intrinsic,  Next: GetArg Intrinsic,  Prev: FTell Intrinsic (function),  Up: Table of Intrinsic Functions
- 
- GError Intrinsic
- ................
- 
-      CALL GError(MESSAGE)
- 
- MESSAGE: `CHARACTER'; scalar; INTENT(OUT).
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Returns the system error message corresponding to the last system
- error (C `errno').
- 
- 
- File: g77.info,  Node: GetArg Intrinsic,  Next: GetCWD Intrinsic (subroutine),  Prev: GError Intrinsic,  Up: Table of Intrinsic Functions
- 
- GetArg Intrinsic
- ................
- 
-      CALL GetArg(POS, VALUE)
- 
- POS: `INTEGER' not wider than the default kind; scalar; INTENT(IN).
- 
- VALUE: `CHARACTER'; scalar; INTENT(OUT).
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Sets VALUE to the POS-th command-line argument (or to all blanks if
- there are fewer than VALUE command-line arguments); `CALL GETARG(0,
- VALUE)' sets VALUE to the name of the program (on systems that support
- this feature).
- 
-    *Note IArgC Intrinsic::, for information on how to get the number of
- arguments.
- 
- 
- File: g77.info,  Node: GetCWD Intrinsic (subroutine),  Next: GetCWD Intrinsic (function),  Prev: GetArg Intrinsic,  Up: Table of Intrinsic Functions
- 
- GetCWD Intrinsic (subroutine)
- .............................
- 
-      CALL GetCWD(NAME, STATUS)
- 
- NAME: `CHARACTER'; scalar; INTENT(OUT).
- 
- STATUS: `INTEGER(KIND=1)'; OPTIONAL; scalar; INTENT(OUT).
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Places the current working directory in NAME.  If the STATUS
- argument is supplied, it contains 0 success or a non-zero error code
- upon return (`ENOSYS' if the system does not provide `getcwd(3)' or
- `getwd(3)').
- 
-    Some non-GNU implementations of Fortran provide this intrinsic as
- only a function, not as a subroutine, or do not support the (optional)
- STATUS argument.
- 
-    For information on other intrinsics with the same name: *Note GetCWD
- Intrinsic (function)::.
- 
- 
- File: g77.info,  Node: GetCWD Intrinsic (function),  Next: GetEnv Intrinsic,  Prev: GetCWD Intrinsic (subroutine),  Up: Table of Intrinsic Functions
- 
- GetCWD Intrinsic (function)
- ...........................
- 
-      GetCWD(NAME)
- 
- GetCWD: `INTEGER(KIND=1)' function.
- 
- NAME: `CHARACTER'; scalar; INTENT(OUT).
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Places the current working directory in NAME.  Returns 0 on success,
- otherwise a non-zero error code (`ENOSYS' if the system does not
- provide `getcwd(3)' or `getwd(3)').
- 
-    For information on other intrinsics with the same name: *Note GetCWD
- Intrinsic (subroutine)::.
- 
- 
- File: g77.info,  Node: GetEnv Intrinsic,  Next: GetGId Intrinsic,  Prev: GetCWD Intrinsic (function),  Up: Table of Intrinsic Functions
- 
- GetEnv Intrinsic
- ................
- 
-      CALL GetEnv(NAME, VALUE)
- 
- NAME: `CHARACTER'; scalar; INTENT(IN).
- 
- VALUE: `CHARACTER'; scalar; INTENT(OUT).
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Sets VALUE to the value of environment variable given by the value
- of NAME (`$name' in shell terms) or to blanks if `$name' has not been
- set.  A null character (`CHAR(0)') marks the end of the name in
- NAME--otherwise, trailing blanks in NAME are ignored.
- 
- 
- File: g77.info,  Node: GetGId Intrinsic,  Next: GetLog Intrinsic,  Prev: GetEnv Intrinsic,  Up: Table of Intrinsic Functions
- 
- GetGId Intrinsic
- ................
- 
-      GetGId()
- 
- GetGId: `INTEGER(KIND=1)' function.
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Returns the group id for the current process.
- 
- 
- File: g77.info,  Node: GetLog Intrinsic,  Next: GetPId Intrinsic,  Prev: GetGId Intrinsic,  Up: Table of Intrinsic Functions
- 
- GetLog Intrinsic
- ................
- 
-      CALL GetLog(LOGIN)
- 
- LOGIN: `CHARACTER'; scalar; INTENT(OUT).
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Returns the login name for the process in LOGIN.
- 
-    _Caution:_ On some systems, the `getlogin(3)' function, which this
- intrinsic calls at run time, is either not implemented or returns a
- null pointer.  In the latter case, this intrinsic returns blanks in
- LOGIN.
- 
- 
- File: g77.info,  Node: GetPId Intrinsic,  Next: GetUId Intrinsic,  Prev: GetLog Intrinsic,  Up: Table of Intrinsic Functions
- 
- GetPId Intrinsic
- ................
- 
-      GetPId()
- 
- GetPId: `INTEGER(KIND=1)' function.
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Returns the process id for the current process.
- 
- 
- File: g77.info,  Node: GetUId Intrinsic,  Next: GMTime Intrinsic,  Prev: GetPId Intrinsic,  Up: Table of Intrinsic Functions
- 
- GetUId Intrinsic
- ................
- 
-      GetUId()
- 
- GetUId: `INTEGER(KIND=1)' function.
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Returns the user id for the current process.
- 
- 
- File: g77.info,  Node: GMTime Intrinsic,  Next: HostNm Intrinsic (subroutine),  Prev: GetUId Intrinsic,  Up: Table of Intrinsic Functions
- 
- GMTime Intrinsic
- ................
- 
-      CALL GMTime(STIME, TARRAY)
- 
- STIME: `INTEGER(KIND=1)'; scalar; INTENT(IN).
- 
- TARRAY: `INTEGER(KIND=1)'; DIMENSION(9); INTENT(OUT).
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Given a system time value STIME, fills TARRAY with values extracted
- from it appropriate to the GMT time zone using `gmtime(3)'.
- 
-    The array elements are as follows:
- 
-   1. Seconds after the minute, range 0-59 or 0-61 to allow for leap
-      seconds
- 
-   2. Minutes after the hour, range 0-59
- 
-   3. Hours past midnight, range 0-23
- 
-   4. Day of month, range 0-31
- 
-   5. Number of months since January, range 0-12
- 
-   6. Years since 1900
- 
-   7. Number of days since Sunday, range 0-6
- 
-   8. Days since January 1
- 
-   9. Daylight savings indicator: positive if daylight savings is in
-      effect, zero if not, and negative if the information isn't
-      available.
- 
- 
- File: g77.info,  Node: HostNm Intrinsic (subroutine),  Next: HostNm Intrinsic (function),  Prev: GMTime Intrinsic,  Up: Table of Intrinsic Functions
- 
- HostNm Intrinsic (subroutine)
- .............................
- 
-      CALL HostNm(NAME, STATUS)
- 
- NAME: `CHARACTER'; scalar; INTENT(OUT).
- 
- STATUS: `INTEGER(KIND=1)'; OPTIONAL; scalar; INTENT(OUT).
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Fills NAME with the system's host name returned by `gethostname(2)'.
- If the STATUS argument is supplied, it contains 0 on success or a
- non-zero error code upon return (`ENOSYS' if the system does not
- provide `gethostname(2)').
- 
-    Some non-GNU implementations of Fortran provide this intrinsic as
- only a function, not as a subroutine, or do not support the (optional)
- STATUS argument.
- 
-    On some systems (specifically SCO) it might be necessary to link the
- "socket" library if you call this routine.  Typically this means adding
- `-lg2c -lsocket -lm' to the `g77' command line when linking the program.
- 
-    For information on other intrinsics with the same name: *Note HostNm
- Intrinsic (function)::.
- 
--- 0 ----
diff -Nrc3pad gcc-3.2.3/gcc/f/g77.info-9 gcc-3.3/gcc/f/g77.info-9
*** gcc-3.2.3/gcc/f/g77.info-9	2003-04-22 07:07:24.000000000 +0000
--- gcc-3.3/gcc/f/g77.info-9	1970-01-01 00:00:00.000000000 +0000
***************
*** 1,1883 ****
- This is g77.info, produced by makeinfo version 4.5 from g77.texi.
- 
- INFO-DIR-SECTION Programming
- START-INFO-DIR-ENTRY
- * g77: (g77).                  The GNU Fortran compiler.
- END-INFO-DIR-ENTRY
-    This file documents the use and the internals of the GNU Fortran
- (`g77') compiler.  It corresponds to the GCC-3.2.3 version of `g77'.
- 
-    Published by the Free Software Foundation 59 Temple Place - Suite 330
- Boston, MA 02111-1307 USA
- 
-    Copyright (C) 1995,1996,1997,1998,1999,2000,2001,2002 Free Software
- Foundation, Inc.
- 
-    Permission is granted to copy, distribute and/or modify this document
- under the terms of the GNU Free Documentation License, Version 1.1 or
- any later version published by the Free Software Foundation; with the
- Invariant Sections being "GNU General Public License" and "Funding Free
- Software", the Front-Cover texts being (a) (see below), and with the
- Back-Cover Texts being (b) (see below).  A copy of the license is
- included in the section entitled "GNU Free Documentation License".
- 
-    (a) The FSF's Front-Cover Text is:
- 
-    A GNU Manual
- 
-    (b) The FSF's Back-Cover Text is:
- 
-    You have freedom to copy and modify this GNU Manual, like GNU
- software.  Copies published by the Free Software Foundation raise
- funds for GNU development.
- 
-    Contributed by James Craig Burley (<craig@jcb-sc.com>).  Inspired by
- a first pass at translating `g77-0.5.16/f/DOC' that was contributed to
- Craig by David Ronis (<ronis@onsager.chem.mcgill.ca>).
- 
- 
- File: g77.info,  Node: HostNm Intrinsic (function),  Next: Huge Intrinsic,  Prev: HostNm Intrinsic (subroutine),  Up: Table of Intrinsic Functions
- 
- HostNm Intrinsic (function)
- ...........................
- 
-      HostNm(NAME)
- 
- HostNm: `INTEGER(KIND=1)' function.
- 
- NAME: `CHARACTER'; scalar; INTENT(OUT).
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Fills NAME with the system's host name returned by `gethostname(2)',
- returning 0 on success or a non-zero error code (`ENOSYS' if the system
- does not provide `gethostname(2)').
- 
-    On some systems (specifically SCO) it might be necessary to link the
- "socket" library if you call this routine.  Typically this means adding
- `-lg2c -lsocket -lm' to the `g77' command line when linking the program.
- 
-    For information on other intrinsics with the same name: *Note HostNm
- Intrinsic (subroutine)::.
- 
- 
- File: g77.info,  Node: Huge Intrinsic,  Next: IAbs Intrinsic,  Prev: HostNm Intrinsic (function),  Up: Table of Intrinsic Functions
- 
- Huge Intrinsic
- ..............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL Huge' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: IAbs Intrinsic,  Next: IAChar Intrinsic,  Prev: Huge Intrinsic,  Up: Table of Intrinsic Functions
- 
- IAbs Intrinsic
- ..............
- 
-      IAbs(A)
- 
- IAbs: `INTEGER(KIND=1)' function.
- 
- A: `INTEGER(KIND=1)'; scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Archaic form of `ABS()' that is specific to one type for A.  *Note
- Abs Intrinsic::.
- 
- 
- File: g77.info,  Node: IAChar Intrinsic,  Next: IAnd Intrinsic,  Prev: IAbs Intrinsic,  Up: Table of Intrinsic Functions
- 
- IAChar Intrinsic
- ................
- 
-      IAChar(C)
- 
- IAChar: `INTEGER(KIND=1)' function.
- 
- C: `CHARACTER'; scalar; INTENT(IN).
- 
- Intrinsic groups: `f2c', `f90'.
- 
- Description:
- 
-    Returns the code for the ASCII character in the first character
- position of C.
- 
-    *Note AChar Intrinsic::, for the inverse of this function.
- 
-    *Note IChar Intrinsic::, for the function corresponding to the
- system's native character set.
- 
- 
- File: g77.info,  Node: IAnd Intrinsic,  Next: IArgC Intrinsic,  Prev: IAChar Intrinsic,  Up: Table of Intrinsic Functions
- 
- IAnd Intrinsic
- ..............
- 
-      IAnd(I, J)
- 
- IAnd: `INTEGER' function, the exact type being the result of
- cross-promoting the types of all the arguments.
- 
- I: `INTEGER'; scalar; INTENT(IN).
- 
- J: `INTEGER'; scalar; INTENT(IN).
- 
- Intrinsic groups: `mil', `f90', `vxt'.
- 
- Description:
- 
-    Returns value resulting from boolean AND of pair of bits in each of
- I and J.
- 
- 
- File: g77.info,  Node: IArgC Intrinsic,  Next: IBClr Intrinsic,  Prev: IAnd Intrinsic,  Up: Table of Intrinsic Functions
- 
- IArgC Intrinsic
- ...............
- 
-      IArgC()
- 
- IArgC: `INTEGER(KIND=1)' function.
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Returns the number of command-line arguments.
- 
-    This count does not include the specification of the program name
- itself.
- 
- 
- File: g77.info,  Node: IBClr Intrinsic,  Next: IBits Intrinsic,  Prev: IArgC Intrinsic,  Up: Table of Intrinsic Functions
- 
- IBClr Intrinsic
- ...............
- 
-      IBClr(I, POS)
- 
- IBClr: `INTEGER' function, the `KIND=' value of the type being that of
- argument I.
- 
- I: `INTEGER'; scalar; INTENT(IN).
- 
- POS: `INTEGER'; scalar; INTENT(IN).
- 
- Intrinsic groups: `mil', `f90', `vxt'.
- 
- Description:
- 
-    Returns the value of I with bit POS cleared (set to zero).  *Note
- BTest Intrinsic::, for information on bit positions.
- 
- 
- File: g77.info,  Node: IBits Intrinsic,  Next: IBSet Intrinsic,  Prev: IBClr Intrinsic,  Up: Table of Intrinsic Functions
- 
- IBits Intrinsic
- ...............
- 
-      IBits(I, POS, LEN)
- 
- IBits: `INTEGER' function, the `KIND=' value of the type being that of
- argument I.
- 
- I: `INTEGER'; scalar; INTENT(IN).
- 
- POS: `INTEGER'; scalar; INTENT(IN).
- 
- LEN: `INTEGER'; scalar; INTENT(IN).
- 
- Intrinsic groups: `mil', `f90', `vxt'.
- 
- Description:
- 
-    Extracts a subfield of length LEN from I, starting from bit position
- POS and extending left for LEN bits.  The result is right-justified and
- the remaining bits are zeroed.  The value of `POS+LEN' must be less
- than or equal to the value `BIT_SIZE(I)'.  *Note Bit_Size Intrinsic::.
- 
- 
- File: g77.info,  Node: IBSet Intrinsic,  Next: IChar Intrinsic,  Prev: IBits Intrinsic,  Up: Table of Intrinsic Functions
- 
- IBSet Intrinsic
- ...............
- 
-      IBSet(I, POS)
- 
- IBSet: `INTEGER' function, the `KIND=' value of the type being that of
- argument I.
- 
- I: `INTEGER'; scalar; INTENT(IN).
- 
- POS: `INTEGER'; scalar; INTENT(IN).
- 
- Intrinsic groups: `mil', `f90', `vxt'.
- 
- Description:
- 
-    Returns the value of I with bit POS set (to one).  *Note BTest
- Intrinsic::, for information on bit positions.
- 
- 
- File: g77.info,  Node: IChar Intrinsic,  Next: IDate Intrinsic (UNIX),  Prev: IBSet Intrinsic,  Up: Table of Intrinsic Functions
- 
- IChar Intrinsic
- ...............
- 
-      IChar(C)
- 
- IChar: `INTEGER(KIND=1)' function.
- 
- C: `CHARACTER'; scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Returns the code for the character in the first character position
- of C.
- 
-    Because the system's native character set is used, the
- correspondence between character and their codes is not necessarily the
- same between GNU Fortran implementations.
- 
-    Note that no intrinsic exists to convert a printable character
- string to a numerical value.  For example, there is no intrinsic that,
- given the `CHARACTER' value `'154'', returns an `INTEGER' or `REAL'
- value with the value `154'.
- 
-    Instead, you can use internal-file I/O to do this kind of conversion.
- For example:
- 
-      INTEGER VALUE
-      CHARACTER*10 STRING
-      STRING = '154'
-      READ (STRING, '(I10)'), VALUE
-      PRINT *, VALUE
-      END
- 
-    The above program, when run, prints:
- 
-       154
- 
-    *Note Char Intrinsic::, for the inverse of the `ICHAR' function.
- 
-    *Note IAChar Intrinsic::, for the function corresponding to the
- ASCII character set.
- 
- 
- File: g77.info,  Node: IDate Intrinsic (UNIX),  Next: IDiM Intrinsic,  Prev: IChar Intrinsic,  Up: Table of Intrinsic Functions
- 
- IDate Intrinsic (UNIX)
- ......................
- 
-      CALL IDate(TARRAY)
- 
- TARRAY: `INTEGER(KIND=1)'; DIMENSION(3); INTENT(OUT).
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Fills TARRAY with the numerical values at the current local time of
- day, month (in the range 1-12), and year in elements 1, 2, and 3,
- respectively.  The year has four significant digits.
- 
-    Programs making use of this intrinsic might not be Year 10000 (Y10K)
- compliant.  For example, the date might appear, to such programs, to
- wrap around (change from a larger value to a smaller one) as of the
- Year 10000.
- 
-    For information on other intrinsics with the same name: *Note IDate
- Intrinsic (VXT)::.
- 
- 
- File: g77.info,  Node: IDiM Intrinsic,  Next: IDInt Intrinsic,  Prev: IDate Intrinsic (UNIX),  Up: Table of Intrinsic Functions
- 
- IDiM Intrinsic
- ..............
- 
-      IDiM(X, Y)
- 
- IDiM: `INTEGER(KIND=1)' function.
- 
- X: `INTEGER(KIND=1)'; scalar; INTENT(IN).
- 
- Y: `INTEGER(KIND=1)'; scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Archaic form of `DIM()' that is specific to one type for X and Y.
- *Note DiM Intrinsic::.
- 
- 
- File: g77.info,  Node: IDInt Intrinsic,  Next: IDNInt Intrinsic,  Prev: IDiM Intrinsic,  Up: Table of Intrinsic Functions
- 
- IDInt Intrinsic
- ...............
- 
-      IDInt(A)
- 
- IDInt: `INTEGER(KIND=1)' function.
- 
- A: `REAL(KIND=2)'; scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Archaic form of `INT()' that is specific to one type for A.  *Note
- Int Intrinsic::.
- 
- 
- File: g77.info,  Node: IDNInt Intrinsic,  Next: IEOr Intrinsic,  Prev: IDInt Intrinsic,  Up: Table of Intrinsic Functions
- 
- IDNInt Intrinsic
- ................
- 
-      IDNInt(A)
- 
- IDNInt: `INTEGER(KIND=1)' function.
- 
- A: `REAL(KIND=2)'; scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Archaic form of `NINT()' that is specific to one type for A.  *Note
- NInt Intrinsic::.
- 
- 
- File: g77.info,  Node: IEOr Intrinsic,  Next: IErrNo Intrinsic,  Prev: IDNInt Intrinsic,  Up: Table of Intrinsic Functions
- 
- IEOr Intrinsic
- ..............
- 
-      IEOr(I, J)
- 
- IEOr: `INTEGER' function, the exact type being the result of
- cross-promoting the types of all the arguments.
- 
- I: `INTEGER'; scalar; INTENT(IN).
- 
- J: `INTEGER'; scalar; INTENT(IN).
- 
- Intrinsic groups: `mil', `f90', `vxt'.
- 
- Description:
- 
-    Returns value resulting from boolean exclusive-OR of pair of bits in
- each of I and J.
- 
- 
- File: g77.info,  Node: IErrNo Intrinsic,  Next: IFix Intrinsic,  Prev: IEOr Intrinsic,  Up: Table of Intrinsic Functions
- 
- IErrNo Intrinsic
- ................
- 
-      IErrNo()
- 
- IErrNo: `INTEGER(KIND=1)' function.
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Returns the last system error number (corresponding to the C
- `errno').
- 
- 
- File: g77.info,  Node: IFix Intrinsic,  Next: Imag Intrinsic,  Prev: IErrNo Intrinsic,  Up: Table of Intrinsic Functions
- 
- IFix Intrinsic
- ..............
- 
-      IFix(A)
- 
- IFix: `INTEGER(KIND=1)' function.
- 
- A: `REAL(KIND=1)'; scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Archaic form of `INT()' that is specific to one type for A.  *Note
- Int Intrinsic::.
- 
- 
- File: g77.info,  Node: Imag Intrinsic,  Next: ImagPart Intrinsic,  Prev: IFix Intrinsic,  Up: Table of Intrinsic Functions
- 
- Imag Intrinsic
- ..............
- 
-      Imag(Z)
- 
- Imag: `REAL' function, the `KIND=' value of the type being that of
- argument Z.
- 
- Z: `COMPLEX'; scalar; INTENT(IN).
- 
- Intrinsic groups: `f2c'.
- 
- Description:
- 
-    The imaginary part of Z is returned, without conversion.
- 
-    _Note:_ The way to do this in standard Fortran 90 is `AIMAG(Z)'.
- However, when, for example, Z is `DOUBLE COMPLEX', `AIMAG(Z)' means
- something different for some compilers that are not true Fortran 90
- compilers but offer some extensions standardized by Fortran 90 (such as
- the `DOUBLE COMPLEX' type, also known as `COMPLEX(KIND=2)').
- 
-    The advantage of `IMAG()' is that, while not necessarily more or
- less portable than `AIMAG()', it is more likely to cause a compiler
- that doesn't support it to produce a diagnostic than generate incorrect
- code.
- 
-    *Note REAL() and AIMAG() of Complex::, for more information.
- 
- 
- File: g77.info,  Node: ImagPart Intrinsic,  Next: Index Intrinsic,  Prev: Imag Intrinsic,  Up: Table of Intrinsic Functions
- 
- ImagPart Intrinsic
- ..................
- 
-      ImagPart(Z)
- 
- ImagPart: `REAL' function, the `KIND=' value of the type being that of
- argument Z.
- 
- Z: `COMPLEX'; scalar; INTENT(IN).
- 
- Intrinsic groups: `gnu'.
- 
- Description:
- 
-    The imaginary part of Z is returned, without conversion.
- 
-    _Note:_ The way to do this in standard Fortran 90 is `AIMAG(Z)'.
- However, when, for example, Z is `DOUBLE COMPLEX', `AIMAG(Z)' means
- something different for some compilers that are not true Fortran 90
- compilers but offer some extensions standardized by Fortran 90 (such as
- the `DOUBLE COMPLEX' type, also known as `COMPLEX(KIND=2)').
- 
-    The advantage of `IMAGPART()' is that, while not necessarily more or
- less portable than `AIMAG()', it is more likely to cause a compiler
- that doesn't support it to produce a diagnostic than generate incorrect
- code.
- 
-    *Note REAL() and AIMAG() of Complex::, for more information.
- 
- 
- File: g77.info,  Node: Index Intrinsic,  Next: Int Intrinsic,  Prev: ImagPart Intrinsic,  Up: Table of Intrinsic Functions
- 
- Index Intrinsic
- ...............
- 
-      Index(STRING, SUBSTRING)
- 
- Index: `INTEGER(KIND=1)' function.
- 
- STRING: `CHARACTER'; scalar; INTENT(IN).
- 
- SUBSTRING: `CHARACTER'; scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Returns the position of the start of the first occurrence of string
- SUBSTRING as a substring in STRING, counting from one.  If SUBSTRING
- doesn't occur in STRING, zero is returned.
- 
- 
- File: g77.info,  Node: Int Intrinsic,  Next: Int2 Intrinsic,  Prev: Index Intrinsic,  Up: Table of Intrinsic Functions
- 
- Int Intrinsic
- .............
- 
-      Int(A)
- 
- Int: `INTEGER(KIND=1)' function.
- 
- A: `INTEGER', `REAL', or `COMPLEX'; scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Returns A with the fractional portion of its magnitude truncated and
- its sign preserved, converted to type `INTEGER(KIND=1)'.
- 
-    If A is type `COMPLEX', its real part is truncated and converted,
- and its imaginary part is disregarded.
- 
-    *Note NInt Intrinsic::, for how to convert, rounded to nearest whole
- number.
- 
-    *Note AInt Intrinsic::, for how to truncate to whole number without
- converting.
- 
- 
- File: g77.info,  Node: Int2 Intrinsic,  Next: Int8 Intrinsic,  Prev: Int Intrinsic,  Up: Table of Intrinsic Functions
- 
- Int2 Intrinsic
- ..............
- 
-      Int2(A)
- 
- Int2: `INTEGER(KIND=6)' function.
- 
- A: `INTEGER', `REAL', or `COMPLEX'; scalar; INTENT(IN).
- 
- Intrinsic groups: `gnu'.
- 
- Description:
- 
-    Returns A with the fractional portion of its magnitude truncated and
- its sign preserved, converted to type `INTEGER(KIND=6)'.
- 
-    If A is type `COMPLEX', its real part is truncated and converted,
- and its imaginary part is disgregarded.
- 
-    *Note Int Intrinsic::.
- 
-    The precise meaning of this intrinsic might change in a future
- version of the GNU Fortran language, as more is learned about how it is
- used.
- 
- 
- File: g77.info,  Node: Int8 Intrinsic,  Next: IOr Intrinsic,  Prev: Int2 Intrinsic,  Up: Table of Intrinsic Functions
- 
- Int8 Intrinsic
- ..............
- 
-      Int8(A)
- 
- Int8: `INTEGER(KIND=2)' function.
- 
- A: `INTEGER', `REAL', or `COMPLEX'; scalar; INTENT(IN).
- 
- Intrinsic groups: `gnu'.
- 
- Description:
- 
-    Returns A with the fractional portion of its magnitude truncated and
- its sign preserved, converted to type `INTEGER(KIND=2)'.
- 
-    If A is type `COMPLEX', its real part is truncated and converted,
- and its imaginary part is disgregarded.
- 
-    *Note Int Intrinsic::.
- 
-    The precise meaning of this intrinsic might change in a future
- version of the GNU Fortran language, as more is learned about how it is
- used.
- 
- 
- File: g77.info,  Node: IOr Intrinsic,  Next: IRand Intrinsic,  Prev: Int8 Intrinsic,  Up: Table of Intrinsic Functions
- 
- IOr Intrinsic
- .............
- 
-      IOr(I, J)
- 
- IOr: `INTEGER' function, the exact type being the result of
- cross-promoting the types of all the arguments.
- 
- I: `INTEGER'; scalar; INTENT(IN).
- 
- J: `INTEGER'; scalar; INTENT(IN).
- 
- Intrinsic groups: `mil', `f90', `vxt'.
- 
- Description:
- 
-    Returns value resulting from boolean OR of pair of bits in each of I
- and J.
- 
- 
- File: g77.info,  Node: IRand Intrinsic,  Next: IsaTty Intrinsic,  Prev: IOr Intrinsic,  Up: Table of Intrinsic Functions
- 
- IRand Intrinsic
- ...............
- 
-      IRand(FLAG)
- 
- IRand: `INTEGER(KIND=1)' function.
- 
- FLAG: `INTEGER'; OPTIONAL; scalar; INTENT(IN).
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Returns a uniform quasi-random number up to a system-dependent limit.
- If FLAG is 0, the next number in sequence is returned; if FLAG is 1,
- the generator is restarted by calling the UNIX function `srand(0)'; if
- FLAG has any other value, it is used as a new seed with `srand()'.
- 
-    *Note SRand Intrinsic::.
- 
-    _Note:_ As typically implemented (by the routine of the same name in
- the C library), this random number generator is a very poor one, though
- the BSD and GNU libraries provide a much better implementation than the
- `traditional' one.  On a different system you almost certainly want to
- use something better.
- 
- 
- File: g77.info,  Node: IsaTty Intrinsic,  Next: IShft Intrinsic,  Prev: IRand Intrinsic,  Up: Table of Intrinsic Functions
- 
- IsaTty Intrinsic
- ................
- 
-      IsaTty(UNIT)
- 
- IsaTty: `LOGICAL(KIND=1)' function.
- 
- UNIT: `INTEGER'; scalar; INTENT(IN).
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Returns `.TRUE.' if and only if the Fortran I/O unit specified by
- UNIT is connected to a terminal device.  See `isatty(3)'.
- 
- 
- File: g77.info,  Node: IShft Intrinsic,  Next: IShftC Intrinsic,  Prev: IsaTty Intrinsic,  Up: Table of Intrinsic Functions
- 
- IShft Intrinsic
- ...............
- 
-      IShft(I, SHIFT)
- 
- IShft: `INTEGER' function, the `KIND=' value of the type being that of
- argument I.
- 
- I: `INTEGER'; scalar; INTENT(IN).
- 
- SHIFT: `INTEGER'; scalar; INTENT(IN).
- 
- Intrinsic groups: `mil', `f90', `vxt'.
- 
- Description:
- 
-    All bits representing I are shifted SHIFT places.  `SHIFT.GT.0'
- indicates a left shift, `SHIFT.EQ.0' indicates no shift and
- `SHIFT.LT.0' indicates a right shift.  If the absolute value of the
- shift count is greater than `BIT_SIZE(I)', the result is undefined.
- Bits shifted out from the left end or the right end are lost.  Zeros
- are shifted in from the opposite end.
- 
-    *Note IShftC Intrinsic::, for the circular-shift equivalent.
- 
- 
- File: g77.info,  Node: IShftC Intrinsic,  Next: ISign Intrinsic,  Prev: IShft Intrinsic,  Up: Table of Intrinsic Functions
- 
- IShftC Intrinsic
- ................
- 
-      IShftC(I, SHIFT, SIZE)
- 
- IShftC: `INTEGER' function, the `KIND=' value of the type being that of
- argument I.
- 
- I: `INTEGER'; scalar; INTENT(IN).
- 
- SHIFT: `INTEGER'; scalar; INTENT(IN).
- 
- SIZE: `INTEGER'; scalar; INTENT(IN).
- 
- Intrinsic groups: `mil', `f90', `vxt'.
- 
- Description:
- 
-    The rightmost SIZE bits of the argument I are shifted circularly
- SHIFT places, i.e. the bits shifted out of one end are shifted into the
- opposite end.  No bits are lost.  The unshifted bits of the result are
- the same as the unshifted bits of I.  The  absolute value of the
- argument SHIFT must be less than or equal to SIZE.  The value of SIZE
- must be greater than or equal to one and less than or equal to
- `BIT_SIZE(I)'.
- 
-    *Note IShft Intrinsic::, for the logical shift equivalent.
- 
- 
- File: g77.info,  Node: ISign Intrinsic,  Next: ITime Intrinsic,  Prev: IShftC Intrinsic,  Up: Table of Intrinsic Functions
- 
- ISign Intrinsic
- ...............
- 
-      ISign(A, B)
- 
- ISign: `INTEGER(KIND=1)' function.
- 
- A: `INTEGER(KIND=1)'; scalar; INTENT(IN).
- 
- B: `INTEGER(KIND=1)'; scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Archaic form of `SIGN()' that is specific to one type for A and B.
- *Note Sign Intrinsic::.
- 
- 
- File: g77.info,  Node: ITime Intrinsic,  Next: Kill Intrinsic (subroutine),  Prev: ISign Intrinsic,  Up: Table of Intrinsic Functions
- 
- ITime Intrinsic
- ...............
- 
-      CALL ITime(TARRAY)
- 
- TARRAY: `INTEGER(KIND=1)'; DIMENSION(3); INTENT(OUT).
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Returns the current local time hour, minutes, and seconds in elements
- 1, 2, and 3 of TARRAY, respectively.
- 
- 
- File: g77.info,  Node: Kill Intrinsic (subroutine),  Next: Kind Intrinsic,  Prev: ITime Intrinsic,  Up: Table of Intrinsic Functions
- 
- Kill Intrinsic (subroutine)
- ...........................
- 
-      CALL Kill(PID, SIGNAL, STATUS)
- 
- PID: `INTEGER'; scalar; INTENT(IN).
- 
- SIGNAL: `INTEGER'; scalar; INTENT(IN).
- 
- STATUS: `INTEGER(KIND=1)'; OPTIONAL; scalar; INTENT(OUT).
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Sends the signal specified by SIGNAL to the process PID.  If the
- STATUS argument is supplied, it contains 0 on success or a non-zero
- error code upon return.  See `kill(2)'.
- 
-    Some non-GNU implementations of Fortran provide this intrinsic as
- only a function, not as a subroutine, or do not support the (optional)
- STATUS argument.
- 
-    For information on other intrinsics with the same name: *Note Kill
- Intrinsic (function)::.
- 
- 
- File: g77.info,  Node: Kind Intrinsic,  Next: LBound Intrinsic,  Prev: Kill Intrinsic (subroutine),  Up: Table of Intrinsic Functions
- 
- Kind Intrinsic
- ..............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL Kind' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: LBound Intrinsic,  Next: Len Intrinsic,  Prev: Kind Intrinsic,  Up: Table of Intrinsic Functions
- 
- LBound Intrinsic
- ................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL LBound' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: Len Intrinsic,  Next: Len_Trim Intrinsic,  Prev: LBound Intrinsic,  Up: Table of Intrinsic Functions
- 
- Len Intrinsic
- .............
- 
-      Len(STRING)
- 
- Len: `INTEGER(KIND=1)' function.
- 
- STRING: `CHARACTER'; scalar.
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Returns the length of STRING.
- 
-    If STRING is an array, the length of an element of STRING is
- returned.
- 
-    Note that STRING need not be defined when this intrinsic is invoked,
- since only the length, not the content, of STRING is needed.
- 
-    *Note Bit_Size Intrinsic::, for the function that determines the
- size of its argument in bits.
- 
- 
- File: g77.info,  Node: Len_Trim Intrinsic,  Next: LGe Intrinsic,  Prev: Len Intrinsic,  Up: Table of Intrinsic Functions
- 
- Len_Trim Intrinsic
- ..................
- 
-      Len_Trim(STRING)
- 
- Len_Trim: `INTEGER(KIND=1)' function.
- 
- STRING: `CHARACTER'; scalar; INTENT(IN).
- 
- Intrinsic groups: `f90'.
- 
- Description:
- 
-    Returns the index of the last non-blank character in STRING.
- `LNBLNK' and `LEN_TRIM' are equivalent.
- 
- 
- File: g77.info,  Node: LGe Intrinsic,  Next: LGt Intrinsic,  Prev: Len_Trim Intrinsic,  Up: Table of Intrinsic Functions
- 
- LGe Intrinsic
- .............
- 
-      LGe(STRING_A, STRING_B)
- 
- LGe: `LOGICAL(KIND=1)' function.
- 
- STRING_A: `CHARACTER'; scalar; INTENT(IN).
- 
- STRING_B: `CHARACTER'; scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Returns `.TRUE.' if `STRING_A.GE.STRING_B', `.FALSE.' otherwise.
- STRING_A and STRING_B are interpreted as containing ASCII character
- codes.  If either value contains a character not in the ASCII character
- set, the result is processor dependent.
- 
-    If the STRING_A and STRING_B are not the same length, the shorter is
- compared as if spaces were appended to it to form a value that has the
- same length as the longer.
- 
-    The lexical comparison intrinsics `LGe', `LGt', `LLe', and `LLt'
- differ from the corresponding intrinsic operators `.GE.', `.GT.',
- `.LE.', `.LT.'.  Because the ASCII collating sequence is assumed, the
- following expressions always return `.TRUE.':
- 
-      LGE ('0', ' ')
-      LGE ('A', '0')
-      LGE ('a', 'A')
- 
-    The following related expressions do _not_ always return `.TRUE.',
- as they are not necessarily evaluated assuming the arguments use ASCII
- encoding:
- 
-      '0' .GE. ' '
-      'A' .GE. '0'
-      'a' .GE. 'A'
- 
-    The same difference exists between `LGt' and `.GT.'; between `LLe'
- and `.LE.'; and between `LLt' and `.LT.'.
- 
- 
- File: g77.info,  Node: LGt Intrinsic,  Next: Link Intrinsic (subroutine),  Prev: LGe Intrinsic,  Up: Table of Intrinsic Functions
- 
- LGt Intrinsic
- .............
- 
-      LGt(STRING_A, STRING_B)
- 
- LGt: `LOGICAL(KIND=1)' function.
- 
- STRING_A: `CHARACTER'; scalar; INTENT(IN).
- 
- STRING_B: `CHARACTER'; scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Returns `.TRUE.' if `STRING_A.GT.STRING_B', `.FALSE.' otherwise.
- STRING_A and STRING_B are interpreted as containing ASCII character
- codes.  If either value contains a character not in the ASCII character
- set, the result is processor dependent.
- 
-    If the STRING_A and STRING_B are not the same length, the shorter is
- compared as if spaces were appended to it to form a value that has the
- same length as the longer.
- 
-    *Note LGe Intrinsic::, for information on the distinction between
- the `LGT' intrinsic and the `.GT.' operator.
- 
- 
- File: g77.info,  Node: Link Intrinsic (subroutine),  Next: LLe Intrinsic,  Prev: LGt Intrinsic,  Up: Table of Intrinsic Functions
- 
- Link Intrinsic (subroutine)
- ...........................
- 
-      CALL Link(PATH1, PATH2, STATUS)
- 
- PATH1: `CHARACTER'; scalar; INTENT(IN).
- 
- PATH2: `CHARACTER'; scalar; INTENT(IN).
- 
- STATUS: `INTEGER(KIND=1)'; OPTIONAL; scalar; INTENT(OUT).
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Makes a (hard) link from file PATH1 to PATH2.  A null character
- (`CHAR(0)') marks the end of the names in PATH1 and PATH2--otherwise,
- trailing blanks in PATH1 and PATH2 are ignored.  If the STATUS argument
- is supplied, it contains 0 on success or a non-zero error code upon
- return.  See `link(2)'.
- 
-    Some non-GNU implementations of Fortran provide this intrinsic as
- only a function, not as a subroutine, or do not support the (optional)
- STATUS argument.
- 
-    For information on other intrinsics with the same name: *Note Link
- Intrinsic (function)::.
- 
- 
- File: g77.info,  Node: LLe Intrinsic,  Next: LLt Intrinsic,  Prev: Link Intrinsic (subroutine),  Up: Table of Intrinsic Functions
- 
- LLe Intrinsic
- .............
- 
-      LLe(STRING_A, STRING_B)
- 
- LLe: `LOGICAL(KIND=1)' function.
- 
- STRING_A: `CHARACTER'; scalar; INTENT(IN).
- 
- STRING_B: `CHARACTER'; scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Returns `.TRUE.' if `STRING_A.LE.STRING_B', `.FALSE.' otherwise.
- STRING_A and STRING_B are interpreted as containing ASCII character
- codes.  If either value contains a character not in the ASCII character
- set, the result is processor dependent.
- 
-    If the STRING_A and STRING_B are not the same length, the shorter is
- compared as if spaces were appended to it to form a value that has the
- same length as the longer.
- 
-    *Note LGe Intrinsic::, for information on the distinction between
- the `LLE' intrinsic and the `.LE.' operator.
- 
- 
- File: g77.info,  Node: LLt Intrinsic,  Next: LnBlnk Intrinsic,  Prev: LLe Intrinsic,  Up: Table of Intrinsic Functions
- 
- LLt Intrinsic
- .............
- 
-      LLt(STRING_A, STRING_B)
- 
- LLt: `LOGICAL(KIND=1)' function.
- 
- STRING_A: `CHARACTER'; scalar; INTENT(IN).
- 
- STRING_B: `CHARACTER'; scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Returns `.TRUE.' if `STRING_A.LT.STRING_B', `.FALSE.' otherwise.
- STRING_A and STRING_B are interpreted as containing ASCII character
- codes.  If either value contains a character not in the ASCII character
- set, the result is processor dependent.
- 
-    If the STRING_A and STRING_B are not the same length, the shorter is
- compared as if spaces were appended to it to form a value that has the
- same length as the longer.
- 
-    *Note LGe Intrinsic::, for information on the distinction between
- the `LLT' intrinsic and the `.LT.' operator.
- 
- 
- File: g77.info,  Node: LnBlnk Intrinsic,  Next: Loc Intrinsic,  Prev: LLt Intrinsic,  Up: Table of Intrinsic Functions
- 
- LnBlnk Intrinsic
- ................
- 
-      LnBlnk(STRING)
- 
- LnBlnk: `INTEGER(KIND=1)' function.
- 
- STRING: `CHARACTER'; scalar; INTENT(IN).
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Returns the index of the last non-blank character in STRING.
- `LNBLNK' and `LEN_TRIM' are equivalent.
- 
- 
- File: g77.info,  Node: Loc Intrinsic,  Next: Log Intrinsic,  Prev: LnBlnk Intrinsic,  Up: Table of Intrinsic Functions
- 
- Loc Intrinsic
- .............
- 
-      Loc(ENTITY)
- 
- Loc: `INTEGER(KIND=7)' function.
- 
- ENTITY: Any type; cannot be a constant or expression.
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    The `LOC()' intrinsic works the same way as the `%LOC()' construct.
- *Note The `%LOC()' Construct: %LOC(), for more information.
- 
- 
- File: g77.info,  Node: Log Intrinsic,  Next: Log10 Intrinsic,  Prev: Loc Intrinsic,  Up: Table of Intrinsic Functions
- 
- Log Intrinsic
- .............
- 
-      Log(X)
- 
- Log: `REAL' or `COMPLEX' function, the exact type being that of
- argument X.
- 
- X: `REAL' or `COMPLEX'; scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Returns the natural logarithm of X, which must be greater than zero
- or, if type `COMPLEX', must not be zero.
- 
-    *Note Exp Intrinsic::, for the inverse of this function.
- 
-    *Note Log10 Intrinsic::, for the `common' (base-10) logarithm
- function.
- 
- 
- File: g77.info,  Node: Log10 Intrinsic,  Next: Logical Intrinsic,  Prev: Log Intrinsic,  Up: Table of Intrinsic Functions
- 
- Log10 Intrinsic
- ...............
- 
-      Log10(X)
- 
- Log10: `REAL' function, the `KIND=' value of the type being that of
- argument X.
- 
- X: `REAL'; scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Returns the common logarithm (base 10) of X, which must be greater
- than zero.
- 
-    The inverse of this function is `10. ** LOG10(X)'.
- 
-    *Note Log Intrinsic::, for the natural logarithm function.
- 
- 
- File: g77.info,  Node: Logical Intrinsic,  Next: Long Intrinsic,  Prev: Log10 Intrinsic,  Up: Table of Intrinsic Functions
- 
- Logical Intrinsic
- .................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL Logical' to use this name for
- an external procedure.
- 
- 
- File: g77.info,  Node: Long Intrinsic,  Next: LShift Intrinsic,  Prev: Logical Intrinsic,  Up: Table of Intrinsic Functions
- 
- Long Intrinsic
- ..............
- 
-      Long(A)
- 
- Long: `INTEGER(KIND=1)' function.
- 
- A: `INTEGER(KIND=6)'; scalar; INTENT(IN).
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Archaic form of `INT()' that is specific to one type for A.  *Note
- Int Intrinsic::.
- 
-    The precise meaning of this intrinsic might change in a future
- version of the GNU Fortran language, as more is learned about how it is
- used.
- 
- 
- File: g77.info,  Node: LShift Intrinsic,  Next: LStat Intrinsic (subroutine),  Prev: Long Intrinsic,  Up: Table of Intrinsic Functions
- 
- LShift Intrinsic
- ................
- 
-      LShift(I, SHIFT)
- 
- LShift: `INTEGER' function, the `KIND=' value of the type being that of
- argument I.
- 
- I: `INTEGER'; scalar; INTENT(IN).
- 
- SHIFT: `INTEGER'; scalar; INTENT(IN).
- 
- Intrinsic groups: `f2c'.
- 
- Description:
- 
-    Returns I shifted to the left SHIFT bits.
- 
-    Although similar to the expression `I*(2**SHIFT)', there are
- important differences.  For example, the sign of the result is not
- necessarily the same as the sign of I.
- 
-    Currently this intrinsic is defined assuming the underlying
- representation of I is as a two's-complement integer.  It is unclear at
- this point whether that definition will apply when a different
- representation is involved.
- 
-    *Note LShift Intrinsic::, for the inverse of this function.
- 
-    *Note IShft Intrinsic::, for information on a more widely available
- left-shifting intrinsic that is also more precisely defined.
- 
- 
- File: g77.info,  Node: LStat Intrinsic (subroutine),  Next: LStat Intrinsic (function),  Prev: LShift Intrinsic,  Up: Table of Intrinsic Functions
- 
- LStat Intrinsic (subroutine)
- ............................
- 
-      CALL LStat(FILE, SARRAY, STATUS)
- 
- FILE: `CHARACTER'; scalar; INTENT(IN).
- 
- SARRAY: `INTEGER(KIND=1)'; DIMENSION(13); INTENT(OUT).
- 
- STATUS: `INTEGER(KIND=1)'; OPTIONAL; scalar; INTENT(OUT).
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Obtains data about the given file FILE and places them in the array
- SARRAY.  A null character (`CHAR(0)') marks the end of the name in
- FILE--otherwise, trailing blanks in FILE are ignored.  If FILE is a
- symbolic link it returns data on the link itself, so the routine is
- available only on systems that support symbolic links.  The values in
- this array are extracted from the `stat' structure as returned by
- `fstat(2)' q.v., as follows:
- 
-   1. Device ID
- 
-   2. Inode number
- 
-   3. File mode
- 
-   4. Number of links
- 
-   5. Owner's uid
- 
-   6. Owner's gid
- 
-   7. ID of device containing directory entry for file (0 if not
-      available)
- 
-   8. File size (bytes)
- 
-   9. Last access time
- 
-  10. Last modification time
- 
-  11. Last file status change time
- 
-  12. Preferred I/O block size (-1 if not available)
- 
-  13. Number of blocks allocated (-1 if not available)
- 
-    Not all these elements are relevant on all systems.  If an element
- is not relevant, it is returned as 0.
- 
-    If the STATUS argument is supplied, it contains 0 on success or a
- non-zero error code upon return (`ENOSYS' if the system does not
- provide `lstat(2)').
- 
-    Some non-GNU implementations of Fortran provide this intrinsic as
- only a function, not as a subroutine, or do not support the (optional)
- STATUS argument.
- 
-    For information on other intrinsics with the same name: *Note LStat
- Intrinsic (function)::.
- 
- 
- File: g77.info,  Node: LStat Intrinsic (function),  Next: LTime Intrinsic,  Prev: LStat Intrinsic (subroutine),  Up: Table of Intrinsic Functions
- 
- LStat Intrinsic (function)
- ..........................
- 
-      LStat(FILE, SARRAY)
- 
- LStat: `INTEGER(KIND=1)' function.
- 
- FILE: `CHARACTER'; scalar; INTENT(IN).
- 
- SARRAY: `INTEGER(KIND=1)'; DIMENSION(13); INTENT(OUT).
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Obtains data about the given file FILE and places them in the array
- SARRAY.  A null character (`CHAR(0)') marks the end of the name in
- FILE--otherwise, trailing blanks in FILE are ignored.  If FILE is a
- symbolic link it returns data on the link itself, so the routine is
- available only on systems that support symbolic links.  The values in
- this array are extracted from the `stat' structure as returned by
- `fstat(2)' q.v., as follows:
- 
-   1. Device ID
- 
-   2. Inode number
- 
-   3. File mode
- 
-   4. Number of links
- 
-   5. Owner's uid
- 
-   6. Owner's gid
- 
-   7. ID of device containing directory entry for file (0 if not
-      available)
- 
-   8. File size (bytes)
- 
-   9. Last access time
- 
-  10. Last modification time
- 
-  11. Last file status change time
- 
-  12. Preferred I/O block size (-1 if not available)
- 
-  13. Number of blocks allocated (-1 if not available)
- 
-    Not all these elements are relevant on all systems.  If an element
- is not relevant, it is returned as 0.
- 
-    Returns 0 on success or a non-zero error code (`ENOSYS' if the
- system does not provide `lstat(2)').
- 
-    For information on other intrinsics with the same name: *Note LStat
- Intrinsic (subroutine)::.
- 
- 
- File: g77.info,  Node: LTime Intrinsic,  Next: MatMul Intrinsic,  Prev: LStat Intrinsic (function),  Up: Table of Intrinsic Functions
- 
- LTime Intrinsic
- ...............
- 
-      CALL LTime(STIME, TARRAY)
- 
- STIME: `INTEGER(KIND=1)'; scalar; INTENT(IN).
- 
- TARRAY: `INTEGER(KIND=1)'; DIMENSION(9); INTENT(OUT).
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Given a system time value STIME, fills TARRAY with values extracted
- from it appropriate to the GMT time zone using `localtime(3)'.
- 
-    The array elements are as follows:
- 
-   1. Seconds after the minute, range 0-59 or 0-61 to allow for leap
-      seconds
- 
-   2. Minutes after the hour, range 0-59
- 
-   3. Hours past midnight, range 0-23
- 
-   4. Day of month, range 0-31
- 
-   5. Number of months since January, range 0-12
- 
-   6. Years since 1900
- 
-   7. Number of days since Sunday, range 0-6
- 
-   8. Days since January 1
- 
-   9. Daylight savings indicator: positive if daylight savings is in
-      effect, zero if not, and negative if the information isn't
-      available.
- 
- 
- File: g77.info,  Node: MatMul Intrinsic,  Next: Max Intrinsic,  Prev: LTime Intrinsic,  Up: Table of Intrinsic Functions
- 
- MatMul Intrinsic
- ................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL MatMul' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: Max Intrinsic,  Next: Max0 Intrinsic,  Prev: MatMul Intrinsic,  Up: Table of Intrinsic Functions
- 
- Max Intrinsic
- .............
- 
-      Max(A-1, A-2, ..., A-n)
- 
- Max: `INTEGER' or `REAL' function, the exact type being the result of
- cross-promoting the types of all the arguments.
- 
- A: `INTEGER' or `REAL'; at least two such arguments must be provided;
- scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Returns the argument with the largest value.
- 
-    *Note Min Intrinsic::, for the opposite function.
- 
- 
- File: g77.info,  Node: Max0 Intrinsic,  Next: Max1 Intrinsic,  Prev: Max Intrinsic,  Up: Table of Intrinsic Functions
- 
- Max0 Intrinsic
- ..............
- 
-      Max0(A-1, A-2, ..., A-n)
- 
- Max0: `INTEGER(KIND=1)' function.
- 
- A: `INTEGER(KIND=1)'; at least two such arguments must be provided;
- scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Archaic form of `MAX()' that is specific to one type for A.  *Note
- Max Intrinsic::.
- 
- 
- File: g77.info,  Node: Max1 Intrinsic,  Next: MaxExponent Intrinsic,  Prev: Max0 Intrinsic,  Up: Table of Intrinsic Functions
- 
- Max1 Intrinsic
- ..............
- 
-      Max1(A-1, A-2, ..., A-n)
- 
- Max1: `INTEGER(KIND=1)' function.
- 
- A: `REAL(KIND=1)'; at least two such arguments must be provided;
- scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Archaic form of `MAX()' that is specific to one type for A and a
- different return type.  *Note Max Intrinsic::.
- 
- 
- File: g77.info,  Node: MaxExponent Intrinsic,  Next: MaxLoc Intrinsic,  Prev: Max1 Intrinsic,  Up: Table of Intrinsic Functions
- 
- MaxExponent Intrinsic
- .....................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL MaxExponent' to use this name
- for an external procedure.
- 
- 
- File: g77.info,  Node: MaxLoc Intrinsic,  Next: MaxVal Intrinsic,  Prev: MaxExponent Intrinsic,  Up: Table of Intrinsic Functions
- 
- MaxLoc Intrinsic
- ................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL MaxLoc' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: MaxVal Intrinsic,  Next: MClock Intrinsic,  Prev: MaxLoc Intrinsic,  Up: Table of Intrinsic Functions
- 
- MaxVal Intrinsic
- ................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL MaxVal' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: MClock Intrinsic,  Next: MClock8 Intrinsic,  Prev: MaxVal Intrinsic,  Up: Table of Intrinsic Functions
- 
- MClock Intrinsic
- ................
- 
-      MClock()
- 
- MClock: `INTEGER(KIND=1)' function.
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Returns the number of clock ticks since the start of the process.
- Supported on systems with `clock(3)' (q.v.).
- 
-    This intrinsic is not fully portable, such as to systems with 32-bit
- `INTEGER' types but supporting times wider than 32 bits.  Therefore,
- the values returned by this intrinsic might be, or become, negative, or
- numerically less than previous values, during a single run of the
- compiled program.
- 
-    *Note MClock8 Intrinsic::, for information on a similar intrinsic
- that might be portable to more GNU Fortran implementations, though to
- fewer Fortran compilers.
- 
-    If the system does not support `clock(3)', -1 is returned.
- 
- 
- File: g77.info,  Node: MClock8 Intrinsic,  Next: Merge Intrinsic,  Prev: MClock Intrinsic,  Up: Table of Intrinsic Functions
- 
- MClock8 Intrinsic
- .................
- 
-      MClock8()
- 
- MClock8: `INTEGER(KIND=2)' function.
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Returns the number of clock ticks since the start of the process.
- Supported on systems with `clock(3)' (q.v.).
- 
-    _Warning:_ this intrinsic does not increase the range of the timing
- values over that returned by `clock(3)'.  On a system with a 32-bit
- `clock(3)', `MCLOCK8' will return a 32-bit value, even though converted
- to an `INTEGER(KIND=2)' value.  That means overflows of the 32-bit
- value can still occur.  Therefore, the values returned by this intrinsic
- might be, or become, negative, or numerically less than previous values,
- during a single run of the compiled program.
- 
-    No Fortran implementations other than GNU Fortran are known to
- support this intrinsic at the time of this writing.  *Note MClock
- Intrinsic::, for information on a similar intrinsic that might be
- portable to more Fortran compilers, though to fewer GNU Fortran
- implementations.
- 
-    If the system does not support `clock(3)', -1 is returned.
- 
- 
- File: g77.info,  Node: Merge Intrinsic,  Next: Min Intrinsic,  Prev: MClock8 Intrinsic,  Up: Table of Intrinsic Functions
- 
- Merge Intrinsic
- ...............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL Merge' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: Min Intrinsic,  Next: Min0 Intrinsic,  Prev: Merge Intrinsic,  Up: Table of Intrinsic Functions
- 
- Min Intrinsic
- .............
- 
-      Min(A-1, A-2, ..., A-n)
- 
- Min: `INTEGER' or `REAL' function, the exact type being the result of
- cross-promoting the types of all the arguments.
- 
- A: `INTEGER' or `REAL'; at least two such arguments must be provided;
- scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Returns the argument with the smallest value.
- 
-    *Note Max Intrinsic::, for the opposite function.
- 
- 
- File: g77.info,  Node: Min0 Intrinsic,  Next: Min1 Intrinsic,  Prev: Min Intrinsic,  Up: Table of Intrinsic Functions
- 
- Min0 Intrinsic
- ..............
- 
-      Min0(A-1, A-2, ..., A-n)
- 
- Min0: `INTEGER(KIND=1)' function.
- 
- A: `INTEGER(KIND=1)'; at least two such arguments must be provided;
- scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Archaic form of `MIN()' that is specific to one type for A.  *Note
- Min Intrinsic::.
- 
- 
- File: g77.info,  Node: Min1 Intrinsic,  Next: MinExponent Intrinsic,  Prev: Min0 Intrinsic,  Up: Table of Intrinsic Functions
- 
- Min1 Intrinsic
- ..............
- 
-      Min1(A-1, A-2, ..., A-n)
- 
- Min1: `INTEGER(KIND=1)' function.
- 
- A: `REAL(KIND=1)'; at least two such arguments must be provided;
- scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Archaic form of `MIN()' that is specific to one type for A and a
- different return type.  *Note Min Intrinsic::.
- 
- 
- File: g77.info,  Node: MinExponent Intrinsic,  Next: MinLoc Intrinsic,  Prev: Min1 Intrinsic,  Up: Table of Intrinsic Functions
- 
- MinExponent Intrinsic
- .....................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL MinExponent' to use this name
- for an external procedure.
- 
- 
- File: g77.info,  Node: MinLoc Intrinsic,  Next: MinVal Intrinsic,  Prev: MinExponent Intrinsic,  Up: Table of Intrinsic Functions
- 
- MinLoc Intrinsic
- ................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL MinLoc' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: MinVal Intrinsic,  Next: Mod Intrinsic,  Prev: MinLoc Intrinsic,  Up: Table of Intrinsic Functions
- 
- MinVal Intrinsic
- ................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL MinVal' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: Mod Intrinsic,  Next: Modulo Intrinsic,  Prev: MinVal Intrinsic,  Up: Table of Intrinsic Functions
- 
- Mod Intrinsic
- .............
- 
-      Mod(A, P)
- 
- Mod: `INTEGER' or `REAL' function, the exact type being the result of
- cross-promoting the types of all the arguments.
- 
- A: `INTEGER' or `REAL'; scalar; INTENT(IN).
- 
- P: `INTEGER' or `REAL'; scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Returns remainder calculated as:
- 
-      A - (INT(A / P) * P)
- 
-    P must not be zero.
- 
- 
- File: g77.info,  Node: Modulo Intrinsic,  Next: MvBits Intrinsic,  Prev: Mod Intrinsic,  Up: Table of Intrinsic Functions
- 
- Modulo Intrinsic
- ................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL Modulo' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: MvBits Intrinsic,  Next: Nearest Intrinsic,  Prev: Modulo Intrinsic,  Up: Table of Intrinsic Functions
- 
- MvBits Intrinsic
- ................
- 
-      CALL MvBits(FROM, FROMPOS, LEN, TO, TOPOS)
- 
- FROM: `INTEGER'; scalar; INTENT(IN).
- 
- FROMPOS: `INTEGER'; scalar; INTENT(IN).
- 
- LEN: `INTEGER'; scalar; INTENT(IN).
- 
- TO: `INTEGER' with same `KIND=' value as for FROM; scalar;
- INTENT(INOUT).
- 
- TOPOS: `INTEGER'; scalar; INTENT(IN).
- 
- Intrinsic groups: `mil', `f90', `vxt'.
- 
- Description:
- 
-    Moves LEN bits from positions FROMPOS through `FROMPOS+LEN-1' of
- FROM to positions TOPOS through `FROMPOS+LEN-1' of TO.  The portion of
- argument TO not affected by the movement of bits is unchanged.
- Arguments FROM and TO are permitted to be the same numeric storage
- unit.  The values of `FROMPOS+LEN' and `TOPOS+LEN' must be less than or
- equal to `BIT_SIZE(FROM)'.
- 
- 
- File: g77.info,  Node: Nearest Intrinsic,  Next: NInt Intrinsic,  Prev: MvBits Intrinsic,  Up: Table of Intrinsic Functions
- 
- Nearest Intrinsic
- .................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL Nearest' to use this name for
- an external procedure.
- 
- 
- File: g77.info,  Node: NInt Intrinsic,  Next: Not Intrinsic,  Prev: Nearest Intrinsic,  Up: Table of Intrinsic Functions
- 
- NInt Intrinsic
- ..............
- 
-      NInt(A)
- 
- NInt: `INTEGER(KIND=1)' function.
- 
- A: `REAL'; scalar; INTENT(IN).
- 
- Intrinsic groups: (standard FORTRAN 77).
- 
- Description:
- 
-    Returns A with the fractional portion of its magnitude eliminated by
- rounding to the nearest whole number and with its sign preserved,
- converted to type `INTEGER(KIND=1)'.
- 
-    If A is type `COMPLEX', its real part is rounded and converted.
- 
-    A fractional portion exactly equal to `.5' is rounded to the whole
- number that is larger in magnitude.  (Also called "Fortran round".)
- 
-    *Note Int Intrinsic::, for how to convert, truncate to whole number.
- 
-    *Note ANInt Intrinsic::, for how to round to nearest whole number
- without converting.
- 
- 
- File: g77.info,  Node: Not Intrinsic,  Next: Or Intrinsic,  Prev: NInt Intrinsic,  Up: Table of Intrinsic Functions
- 
- Not Intrinsic
- .............
- 
-      Not(I)
- 
- Not: `INTEGER' function, the `KIND=' value of the type being that of
- argument I.
- 
- I: `INTEGER'; scalar; INTENT(IN).
- 
- Intrinsic groups: `mil', `f90', `vxt'.
- 
- Description:
- 
-    Returns value resulting from boolean NOT of each bit in I.
- 
- 
- File: g77.info,  Node: Or Intrinsic,  Next: Pack Intrinsic,  Prev: Not Intrinsic,  Up: Table of Intrinsic Functions
- 
- Or Intrinsic
- ............
- 
-      Or(I, J)
- 
- Or: `INTEGER' or `LOGICAL' function, the exact type being the result of
- cross-promoting the types of all the arguments.
- 
- I: `INTEGER' or `LOGICAL'; scalar; INTENT(IN).
- 
- J: `INTEGER' or `LOGICAL'; scalar; INTENT(IN).
- 
- Intrinsic groups: `f2c'.
- 
- Description:
- 
-    Returns value resulting from boolean OR of pair of bits in each of I
- and J.
- 
- 
- File: g77.info,  Node: Pack Intrinsic,  Next: PError Intrinsic,  Prev: Or Intrinsic,  Up: Table of Intrinsic Functions
- 
- Pack Intrinsic
- ..............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL Pack' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: PError Intrinsic,  Next: Precision Intrinsic,  Prev: Pack Intrinsic,  Up: Table of Intrinsic Functions
- 
- PError Intrinsic
- ................
- 
-      CALL PError(STRING)
- 
- STRING: `CHARACTER'; scalar; INTENT(IN).
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Prints (on the C `stderr' stream) a newline-terminated error message
- corresponding to the last system error.  This is prefixed by STRING, a
- colon and a space.  See `perror(3)'.
- 
- 
- File: g77.info,  Node: Precision Intrinsic,  Next: Present Intrinsic,  Prev: PError Intrinsic,  Up: Table of Intrinsic Functions
- 
- Precision Intrinsic
- ...................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL Precision' to use this name
- for an external procedure.
- 
- 
- File: g77.info,  Node: Present Intrinsic,  Next: Product Intrinsic,  Prev: Precision Intrinsic,  Up: Table of Intrinsic Functions
- 
- Present Intrinsic
- .................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL Present' to use this name for
- an external procedure.
- 
- 
- File: g77.info,  Node: Product Intrinsic,  Next: Radix Intrinsic,  Prev: Present Intrinsic,  Up: Table of Intrinsic Functions
- 
- Product Intrinsic
- .................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL Product' to use this name for
- an external procedure.
- 
- 
- File: g77.info,  Node: Radix Intrinsic,  Next: Rand Intrinsic,  Prev: Product Intrinsic,  Up: Table of Intrinsic Functions
- 
- Radix Intrinsic
- ...............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL Radix' to use this name for an
- external procedure.
- 
- 
- File: g77.info,  Node: Rand Intrinsic,  Next: Random_Number Intrinsic,  Prev: Radix Intrinsic,  Up: Table of Intrinsic Functions
- 
- Rand Intrinsic
- ..............
- 
-      Rand(FLAG)
- 
- Rand: `REAL(KIND=1)' function.
- 
- FLAG: `INTEGER'; OPTIONAL; scalar; INTENT(IN).
- 
- Intrinsic groups: `unix'.
- 
- Description:
- 
-    Returns a uniform quasi-random number between 0 and 1.  If FLAG is
- 0, the next number in sequence is returned; if FLAG is 1, the generator
- is restarted by calling `srand(0)'; if FLAG has any other value, it is
- used as a new seed with `srand'.
- 
-    *Note SRand Intrinsic::.
- 
-    _Note:_ As typically implemented (by the routine of the same name in
- the C library), this random number generator is a very poor one, though
- the BSD and GNU libraries provide a much better implementation than the
- `traditional' one.  On a different system you almost certainly want to
- use something better.
- 
- 
- File: g77.info,  Node: Random_Number Intrinsic,  Next: Random_Seed Intrinsic,  Prev: Rand Intrinsic,  Up: Table of Intrinsic Functions
- 
- Random_Number Intrinsic
- .......................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL Random_Number' to use this
- name for an external procedure.
- 
- 
- File: g77.info,  Node: Random_Seed Intrinsic,  Next: Range Intrinsic,  Prev: Random_Number Intrinsic,  Up: Table of Intrinsic Functions
- 
- Random_Seed Intrinsic
- .....................
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL Random_Seed' to use this name
- for an external procedure.
- 
- 
- File: g77.info,  Node: Range Intrinsic,  Next: Real Intrinsic,  Prev: Random_Seed Intrinsic,  Up: Table of Intrinsic Functions
- 
- Range Intrinsic
- ...............
- 
-    This intrinsic is not yet implemented.  The name is, however,
- reserved as an intrinsic.  Use `EXTERNAL Range' to use this name for an
- external procedure.
- 
--- 0 ----
diff -Nrc3pad gcc-3.2.3/gcc/f/g77spec.c gcc-3.3/gcc/f/g77spec.c
*** gcc-3.2.3/gcc/f/g77spec.c	2002-01-31 19:36:24.000000000 +0000
--- gcc-3.3/gcc/f/g77spec.c	2003-03-15 10:03:23.000000000 +0000
***************
*** 1,5 ****
  /* Specific flags and argument handling of the Fortran front-end.
!    Copyright (C) 1997, 1999, 2000, 2001, 2002 Free Software Foundation, Inc.
  
  This file is part of GNU CC.
  
--- 1,6 ----
  /* Specific flags and argument handling of the Fortran front-end.
!    Copyright (C) 1997, 1999, 2000, 2001, 2002, 2003
!    Free Software Foundation, Inc.
  
  This file is part of GNU CC.
  
*************** Boston, MA 02111-1307, USA.  */
*** 47,53 ****
  #include "config.h"
  #include "system.h"
  #include "gcc.h"
- #include <f/version.h>
  
  #ifndef MATH_LIBRARY
  #define MATH_LIBRARY "-lm"
--- 48,53 ----
*************** static void append_arg PARAMS ((const ch
*** 99,134 ****
  static int g77_newargc;
  static const char **g77_newargv;
  
- /* --- This comes from gcc.c (2.8.1) verbatim: */
- 
- /* This defines which switch letters take arguments.  */
- 
- #define DEFAULT_SWITCH_TAKES_ARG(CHAR)      \
-   ((CHAR) == 'D' || (CHAR) == 'U' || (CHAR) == 'o' \
-    || (CHAR) == 'e' || (CHAR) == 'T' || (CHAR) == 'u' \
-    || (CHAR) == 'I' || (CHAR) == 'm' || (CHAR) == 'x' \
-    || (CHAR) == 'L' || (CHAR) == 'A')
- 
  #ifndef SWITCH_TAKES_ARG
  #define SWITCH_TAKES_ARG(CHAR) DEFAULT_SWITCH_TAKES_ARG(CHAR)
  #endif
  
- /* This defines which multi-letter switches take arguments.  */
- 
- #define DEFAULT_WORD_SWITCH_TAKES_ARG(STR)		\
-  (!strcmp (STR, "Tdata") || !strcmp (STR, "Ttext")	\
-   || !strcmp (STR, "Tbss") || !strcmp (STR, "include")	\
-   || !strcmp (STR, "imacros") || !strcmp (STR, "aux-info") \
-   || !strcmp (STR, "idirafter") || !strcmp (STR, "iprefix") \
-   || !strcmp (STR, "iwithprefix") || !strcmp (STR, "iwithprefixbefore") \
-   || !strcmp (STR, "isystem") || !strcmp (STR, "specs"))
- 
  #ifndef WORD_SWITCH_TAKES_ARG
  #define WORD_SWITCH_TAKES_ARG(STR) DEFAULT_WORD_SWITCH_TAKES_ARG (STR)
  #endif
  
- /* --- End of verbatim.  */
- 
  /* Assumes text[0] == '-'.  Returns number of argv items that belong to
     (and follow) this one, an option id for options important to the
     caller, and a pointer to the first char of the arg, if embedded (else
--- 99,112 ----
*************** lang_specific_driver (in_argc, in_argv, 
*** 374,380 ****
  
  	case OPTION_version:
  	  printf ("\
! GNU Fortran (GCC %s) %s\n\
  Copyright (C) 2002 Free Software Foundation, Inc.\n\
  \n\
  GNU Fortran comes with NO WARRANTY, to the extent permitted by law.\n\
--- 352,358 ----
  
  	case OPTION_version:
  	  printf ("\
! GNU Fortran (GCC) %s\n\
  Copyright (C) 2002 Free Software Foundation, Inc.\n\
  \n\
  GNU Fortran comes with NO WARRANTY, to the extent permitted by law.\n\
*************** You may redistribute copies of GNU Fortr
*** 382,388 ****
  under the terms of the GNU General Public License.\n\
  For more information about these matters, see the file named COPYING\n\
  or type the command `info -f g77 Copying'.\n\
! ", version_string, ffe_version_string);
  	  exit (0);
  	  break;
  
--- 360,366 ----
  under the terms of the GNU General Public License.\n\
  For more information about these matters, see the file named COPYING\n\
  or type the command `info -f g77 Copying'.\n\
! ", version_string);
  	  exit (0);
  	  break;
  
*************** int lang_specific_pre_link ()  /* Not us
*** 563,565 ****
--- 541,549 ----
  
  /* Number of extra output files that lang_specific_pre_link may generate. */
  int lang_specific_extra_outfiles = 0;  /* Not used for F77. */
+ 
+ /* Table of language-specific spec functions.  */ 
+ const struct spec_function lang_specific_spec_functions[] =
+ {
+   { 0, 0 }
+ };
diff -Nrc3pad gcc-3.2.3/gcc/f/g77.texi gcc-3.3/gcc/f/g77.texi
*** gcc-3.2.3/gcc/f/g77.texi	2002-04-29 07:58:32.000000000 +0000
--- gcc-3.3/gcc/f/g77.texi	2003-02-04 01:55:40.000000000 +0000
***************
*** 24,56 ****
  @c and make sure the following does NOT begin with '@c':
  @c @clear USING
  
- @c 6/27/96 FSF DO wants smallbook fmt for 1st bound edition. (from gcc.texi)
- @c @smallbook
- 
- @c i also commented out the finalout command, so if there *are* any
- @c overfulls, you'll (hopefully) see the rectangle in the right hand
- @c margin. -- burley 1999-03-13 (from mew's comment in gcc.texi).
- @c @finalout
- 
- @macro gcctabopt{body}
- @code{\body\}
- @end macro
- @macro gccoptlist{body}
- @smallexample
- \body\
- @end smallexample
- @end macro
- @c Makeinfo handles the above macro OK, TeX needs manual line breaks;
- @c they get lost at some point in handling the macro.  But if @macro is
- @c used here rather than @alias, it produces double line breaks.
- @iftex
- @alias gol = *
- @end iftex
- @ifnottex
- @macro gol
- @end macro
- @end ifnottex
- 
  @ifset INTERNALS
  @ifset USING
  @settitle Using and Porting GNU Fortran
--- 24,29 ----
***************
*** 89,94 ****
--- 62,90 ----
  @c \global\normaloffset =0.75in
  @c @end tex
  
+ @copying
+ Copyright @copyright{} @value{copyrights-g77} Free Software Foundation, Inc.
+ 
+ Permission is granted to copy, distribute and/or modify this document
+ under the terms of the GNU Free Documentation License, Version 1.2 or
+ any later version published by the Free Software Foundation; with the
+ Invariant Sections being ``GNU General Public License'' and ``Funding
+ Free Software'', the Front-Cover
+ texts being (a) (see below), and with the Back-Cover Texts being (b)
+ (see below).  A copy of the license is included in the section entitled
+ ``GNU Free Documentation License''.
+ 
+ (a) The FSF's Front-Cover Text is:
+ 
+      A GNU Manual
+ 
+ (b) The FSF's Back-Cover Text is:
+ 
+      You have freedom to copy and modify this GNU Manual, like GNU
+      software.  Copies published by the Free Software Foundation raise
+      funds for GNU development.
+ @end copying
+ 
  @ifinfo
  @dircategory Programming
  @direntry
*************** Published by the Free Software Foundatio
*** 114,140 ****
  59 Temple Place - Suite 330
  Boston, MA 02111-1307 USA
  
! Copyright (C) @value{copyrights-g77} Free Software Foundation, Inc.
! 
! 
! Permission is granted to copy, distribute and/or modify this document
! under the terms of the GNU Free Documentation License, Version 1.1 or
! any later version published by the Free Software Foundation; with the
! Invariant Sections being ``GNU General Public License'' and ``Funding
! Free Software'', the Front-Cover
! texts being (a) (see below), and with the Back-Cover Texts being (b)
! (see below).  A copy of the license is included in the section entitled
! ``GNU Free Documentation License''.
! 
! (a) The FSF's Front-Cover Text is:
! 
!      A GNU Manual
! 
! (b) The FSF's Back-Cover Text is:
! 
!      You have freedom to copy and modify this GNU Manual, like GNU
!      software.  Copies published by the Free Software Foundation raise
!      funds for GNU development.
  @end ifinfo
  
  Contributed by James Craig Burley (@email{@value{email-burley}}).
--- 110,116 ----
  59 Temple Place - Suite 330
  Boston, MA 02111-1307 USA
  
! @insertcopying
  @end ifinfo
  
  Contributed by James Craig Burley (@email{@value{email-burley}}).
*************** Inspired by a first pass at translating 
*** 142,148 ****
  was contributed to Craig by David Ronis (@email{ronis@@onsager.chem.mcgill.ca}).
  
  @setchapternewpage odd
- @c @finalout
  @titlepage
  @ifset INTERNALS
  @ifset USING
--- 118,123 ----
*************** was contributed to Craig by David Ronis 
*** 164,171 ****
  @center for version @value{which-g77}
  @page
  @vskip 0pt plus 1filll
- Copyright @copyright{} @value{copyrights-g77} Free Software Foundation, Inc.
- @sp 2
  For the @value{which-g77} Version*
  @sp 1
  Published by the Free Software Foundation @*
--- 139,144 ----
*************** Boston, MA 02111-1307, USA@*
*** 175,198 ****
  @c Printed copies are available for $? each.@*
  @c ISBN ???
  @sp 1
! Permission is granted to copy, distribute and/or modify this document
! under the terms of the GNU Free Documentation License, Version 1.1 or
! any later version published by the Free Software Foundation; with the
! Invariant Sections being ``GNU General Public License'' and ``Funding
! Free Software'', the Front-Cover
! texts being (a) (see below), and with the Back-Cover Texts being (b)
! (see below).  A copy of the license is included in the section entitled
! ``GNU Free Documentation License''.
! 
! (a) The FSF's Front-Cover Text is:
! 
!      A GNU Manual
! 
! (b) The FSF's Back-Cover Text is:
! 
!      You have freedom to copy and modify this GNU Manual, like GNU
!      software.  Copies published by the Free Software Foundation raise
!      funds for GNU development.
  @end titlepage
  @summarycontents
  @contents
--- 148,154 ----
  @c Printed copies are available for $? each.@*
  @c ISBN ???
  @sp 1
! @insertcopying
  @end titlepage
  @summarycontents
  @contents
*************** most consistent with the @command{g77} p
*** 275,281 ****
  
  * M: Diagnostics.   Diagnostics produced by @command{g77}.
  
! * Index::           Index of concepts and symbol names.
  @end menu
  @c yes, the "M: " @emph{is} intentional -- bad.def references it (CMPAMBIG)!
  
--- 231,237 ----
  
  * M: Diagnostics.   Diagnostics produced by @command{g77}.
  
! * Keyword Index::   Index of concepts and symbol names.
  @end menu
  @c yes, the "M: " @emph{is} intentional -- bad.def references it (CMPAMBIG)!
  
*************** As such, GNU users rarely need consider 
*** 1045,1051 ****
  hardware (or, in many cases, operating system) they are using at any
  particular time.
  They can use and write software designed for a general-purpose,
! widely portable, heterogenous environment---the GNU environment.
  
  In line with this philosophy, GNU Fortran must evolve into a product
  that is widely ported and portable not only in the sense that it can
--- 1001,1007 ----
  hardware (or, in many cases, operating system) they are using at any
  particular time.
  They can use and write software designed for a general-purpose,
! widely portable, heterogeneous environment---the GNU environment.
  
  In line with this philosophy, GNU Fortran must evolve into a product
  that is widely ported and portable not only in the sense that it can
*************** The important thing about linking @comma
*** 5643,5651 ****
  code with C++ is that the prototypes for the @command{g77}
  routines must specify C linkage to avoid name mangling.
  So, use an @samp{extern "C"} declaration.
! @command{f2c}'s @option{-C++} option will take care
! of this when generating skeletons or prototype files as above, and also
! avoid clashes with C++ reserved words in addition to those in C@.
  
  @node Startup Code
  @subsection Startup Code
--- 5599,5607 ----
  code with C++ is that the prototypes for the @command{g77}
  routines must specify C linkage to avoid name mangling.
  So, use an @samp{extern "C"} declaration.
! @command{f2c}'s @option{-C++} option will not take care
! of this when generating skeletons or prototype files as above, however,
! it will avoid clashes with C++ reserved words in addition to those in C@.
  
  @node Startup Code
  @subsection Startup Code
*************** single-dimensional array, so at least th
*** 6283,6289 ****
  is preserved.
  
  Debuggers that understand Fortran should have no trouble with
! non-zero low bounds, but for non-Fortran debuggers, especially
  C debuggers, the above example might have a C equivalent of
  @samp{a[4305]}.
  This calculation is arrived at by eliminating the subtraction
--- 6239,6245 ----
  is preserved.
  
  Debuggers that understand Fortran should have no trouble with
! nonzero low bounds, but for non-Fortran debuggers, especially
  C debuggers, the above example might have a C equivalent of
  @samp{a[4305]}.
  This calculation is arrived at by eliminating the subtraction
*************** set up this kind of aliasing.
*** 7512,7518 ****
  
  (The FORTRAN 77 standard's prohibition of this sort of
  overlap, generally referred to therein as ``storage
! assocation'', appears in Sections 15.9.3.6.
  This prohibition allows implementations, such as @command{g77},
  to, for example, implement the passing of procedures and
  even values in @code{COMMON} via copy operations into local,
--- 7468,7474 ----
  
  (The FORTRAN 77 standard's prohibition of this sort of
  overlap, generally referred to therein as ``storage
! association'', appears in Sections 15.9.3.6.
  This prohibition allows implementations, such as @command{g77},
  to, for example, implement the passing of procedures and
  even values in @code{COMMON} via copy operations into local,
*************** If a formatted @code{WRITE} produces an 
*** 8547,8553 ****
  that your program is linked against the correct version of the C library.
  The configuration process takes care to account for your
  system's normal @file{libc} not being ANSI-standard, which will
! otherwise cause this behaviour.
  If your system's default library is
  ANSI-standard and you subsequently link against a non-ANSI one, there
  might be problems such as this one.
--- 8503,8509 ----
  that your program is linked against the correct version of the C library.
  The configuration process takes care to account for your
  system's normal @file{libc} not being ANSI-standard, which will
! otherwise cause this behavior.
  If your system's default library is
  ANSI-standard and you subsequently link against a non-ANSI one, there
  might be problems such as this one.
*************** general control over whether or not floa
*** 9460,9468 ****
  ignored.
  (Ignoring them typically results in NaN values being
  propagated in systems that conform to IEEE 754.)
! The behaviour is normally inherited from the system-dependent startup
  code, though some targets, such as the Alpha, have code generation
! options which change the behaviour.
  
  Most systems provide some C-callable mechanism to change this; this can
  be invoked at startup using @command{gcc}'s @code{constructor} attribute.
--- 9416,9424 ----
  ignored.
  (Ignoring them typically results in NaN values being
  propagated in systems that conform to IEEE 754.)
! The behavior is normally inherited from the system-dependent startup
  code, though some targets, such as the Alpha, have code generation
! options which change the behavior.
  
  Most systems provide some C-callable mechanism to change this; this can
  be invoked at startup using @command{gcc}'s @code{constructor} attribute.
*************** that is not Year-2000 (Y2K) compliant.
*** 12262,12269 ****
  
  @end ifset
  
! @node Index
! @unnumbered Index
  
  @printindex cp
  @bye
--- 12218,12225 ----
  
  @end ifset
  
! @node Keyword Index
! @unnumbered Keyword Index
  
  @printindex cp
  @bye
diff -Nrc3pad gcc-3.2.3/gcc/f/intdoc.in gcc-3.3/gcc/f/intdoc.in
*** gcc-3.2.3/gcc/f/intdoc.in	2001-07-10 09:41:04.000000000 +0000
--- gcc-3.3/gcc/f/intdoc.in	2002-12-19 14:27:09.000000000 +0000
*************** magnitude truncated and its sign preserv
*** 646,652 ****
  to type @code{INTEGER(KIND=6)}.
  
  If @var{@1@} is type @code{COMPLEX}, its real part
! is truncated and converted, and its imaginary part is disgregarded.
  
  @xref{Int Intrinsic}.
  
--- 646,652 ----
  to type @code{INTEGER(KIND=6)}.
  
  If @var{@1@} is type @code{COMPLEX}, its real part
! is truncated and converted, and its imaginary part is disregarded.
  
  @xref{Int Intrinsic}.
  
*************** magnitude truncated and its sign preserv
*** 661,667 ****
  to type @code{INTEGER(KIND=6)}.
  
  If @var{@1@} is type @code{COMPLEX}, its real part
! is truncated and converted, and its imaginary part is disgregarded.
  
  @xref{Int Intrinsic}.
  
--- 661,667 ----
  to type @code{INTEGER(KIND=6)}.
  
  If @var{@1@} is type @code{COMPLEX}, its real part
! is truncated and converted, and its imaginary part is disregarded.
  
  @xref{Int Intrinsic}.
  
*************** magnitude truncated and its sign preserv
*** 676,682 ****
  to type @code{INTEGER(KIND=2)}.
  
  If @var{@1@} is type @code{COMPLEX}, its real part
! is truncated and converted, and its imaginary part is disgregarded.
  
  @xref{Int Intrinsic}.
  
--- 676,682 ----
  to type @code{INTEGER(KIND=2)}.
  
  If @var{@1@} is type @code{COMPLEX}, its real part
! is truncated and converted, and its imaginary part is disregarded.
  
  @xref{Int Intrinsic}.
  
*************** almost certainly want to use something b
*** 1584,1590 ****
  ")
  
  DEFDOC (SRAND, "Random seed.", "\
! Reinitialises the generator with the seed in @var{@1@}.
  @xref{IRand Intrinsic}.
  @xref{Rand Intrinsic}.
  ")
--- 1584,1590 ----
  ")
  
  DEFDOC (SRAND, "Random seed.", "\
! Reinitializes the generator with the seed in @var{@1@}.
  @xref{IRand Intrinsic}.
  @xref{Rand Intrinsic}.
  ")
*************** Existence
*** 1617,1623 ****
  DEFDOC (CHDIR_subr, "Change directory.", "\
  Sets the current working directory to be @var{@1@}.
  If the @var{@2@} argument is supplied, it contains 0
! on success or a non-zero error code otherwise upon return.
  See @code{chdir(3)}.
  
  @emph{Caution:} Using this routine during I/O to a unit connected with a
--- 1617,1623 ----
  DEFDOC (CHDIR_subr, "Change directory.", "\
  Sets the current working directory to be @var{@1@}.
  If the @var{@2@} argument is supplied, it contains 0
! on success or a nonzero error code otherwise upon return.
  See @code{chdir(3)}.
  
  @emph{Caution:} Using this routine during I/O to a unit connected with a
*************** only a function, not as a subroutine, or
*** 1631,1637 ****
  
  DEFDOC (CHDIR_func, "Change directory.", "\
  Sets the current working directory to be @var{@1@}.
! Returns 0 on success or a non-zero error code.
  See @code{chdir(3)}.
  
  @emph{Caution:} Using this routine during I/O to a unit connected with a
--- 1631,1637 ----
  
  DEFDOC (CHDIR_func, "Change directory.", "\
  Sets the current working directory to be @var{@1@}.
! Returns 0 on success or a nonzero error code.
  See @code{chdir(3)}.
  
  @emph{Caution:} Using this routine during I/O to a unit connected with a
*************** trailing blanks in @var{@1@} are ignored
*** 1652,1658 ****
  Currently, @var{@1@} must not contain the single quote
  character.
  
! Returns 0 on success or a non-zero error code otherwise.
  
  Note that this currently works
  by actually invoking @code{/bin/chmod} (or the @code{chmod} found when
--- 1652,1658 ----
  Currently, @var{@1@} must not contain the single quote
  character.
  
! Returns 0 on success or a nonzero error code otherwise.
  
  Note that this currently works
  by actually invoking @code{/bin/chmod} (or the @code{chmod} found when
*************** Currently, @var{@1@} must not contain th
*** 1674,1680 ****
  character.
  
  If the @var{@3@} argument is supplied, it contains
! 0 on success or a non-zero error code upon return.
  
  Note that this currently works
  by actually invoking @code{/bin/chmod} (or the @code{chmod} found when
--- 1674,1680 ----
  character.
  
  If the @var{@3@} argument is supplied, it contains
! 0 on success or a nonzero error code upon return.
  
  Note that this currently works
  by actually invoking @code{/bin/chmod} (or the @code{chmod} found when
*************** only a function, not as a subroutine, or
*** 1689,1695 ****
  DEFDOC (GETCWD_func, "Get current working directory.", "\
  Places the current working directory in @var{@1@}.
  Returns 0 on
! success, otherwise a non-zero error code
  (@code{ENOSYS} if the system does not provide @code{getcwd(3)}
  or @code{getwd(3)}).
  ")
--- 1689,1695 ----
  DEFDOC (GETCWD_func, "Get current working directory.", "\
  Places the current working directory in @var{@1@}.
  Returns 0 on
! success, otherwise a nonzero error code
  (@code{ENOSYS} if the system does not provide @code{getcwd(3)}
  or @code{getwd(3)}).
  ")
*************** or @code{getwd(3)}).
*** 1697,1703 ****
  DEFDOC (GETCWD_subr, "Get current working directory.", "\
  Places the current working directory in @var{@1@}.
  If the @var{@2@} argument is supplied, it contains 0
! success or a non-zero error code upon return
  (@code{ENOSYS} if the system does not provide @code{getcwd(3)}
  or @code{getwd(3)}).
  
--- 1697,1703 ----
  DEFDOC (GETCWD_subr, "Get current working directory.", "\
  Places the current working directory in @var{@1@}.
  If the @var{@2@} argument is supplied, it contains 0
! success or a nonzero error code upon return
  (@code{ENOSYS} if the system does not provide @code{getcwd(3)}
  or @code{getwd(3)}).
  
*************** Number of blocks allocated (-1 if not av
*** 1758,1764 ****
  Not all these elements are relevant on all systems.
  If an element is not relevant, it is returned as 0.
  
! Returns 0 on success or a non-zero error code.
  ")
  
  DEFDOC (FSTAT_subr, "Get file information.", "\
--- 1758,1764 ----
  Not all these elements are relevant on all systems.
  If an element is not relevant, it is returned as 0.
  
! Returns 0 on success or a nonzero error code.
  ")
  
  DEFDOC (FSTAT_subr, "Get file information.", "\
*************** Not all these elements are relevant on a
*** 1814,1820 ****
  If an element is not relevant, it is returned as 0.
  
  If the @var{@3@} argument is supplied, it contains
! 0 on success or a non-zero error code upon return.
  
  Some non-GNU implementations of Fortran provide this intrinsic as
  only a function, not as a subroutine, or do not support the
--- 1814,1820 ----
  If an element is not relevant, it is returned as 0.
  
  If the @var{@3@} argument is supplied, it contains
! 0 on success or a nonzero error code upon return.
  
  Some non-GNU implementations of Fortran provide this intrinsic as
  only a function, not as a subroutine, or do not support the
*************** Number of blocks allocated (-1 if not av
*** 1878,1884 ****
  Not all these elements are relevant on all systems.
  If an element is not relevant, it is returned as 0.
  
! Returns 0 on success or a non-zero error code
  (@code{ENOSYS} if the system does not provide @code{lstat(2)}).
  ")
  
--- 1878,1884 ----
  Not all these elements are relevant on all systems.
  If an element is not relevant, it is returned as 0.
  
! Returns 0 on success or a nonzero error code
  (@code{ENOSYS} if the system does not provide @code{lstat(2)}).
  ")
  
*************** Not all these elements are relevant on a
*** 1940,1946 ****
  If an element is not relevant, it is returned as 0.
  
  If the @var{@3@} argument is supplied, it contains
! 0 on success or a non-zero error code upon return
  (@code{ENOSYS} if the system does not provide @code{lstat(2)}).
  
  Some non-GNU implementations of Fortran provide this intrinsic as
--- 1940,1946 ----
  If an element is not relevant, it is returned as 0.
  
  If the @var{@3@} argument is supplied, it contains
! 0 on success or a nonzero error code upon return
  (@code{ENOSYS} if the system does not provide @code{lstat(2)}).
  
  Some non-GNU implementations of Fortran provide this intrinsic as
*************** Number of blocks allocated (-1 if not av
*** 2002,2008 ****
  Not all these elements are relevant on all systems.
  If an element is not relevant, it is returned as 0.
  
! Returns 0 on success or a non-zero error code.
  ")
  
  DEFDOC (STAT_subr, "Get file information.", "\
--- 2002,2008 ----
  Not all these elements are relevant on all systems.
  If an element is not relevant, it is returned as 0.
  
! Returns 0 on success or a nonzero error code.
  ")
  
  DEFDOC (STAT_subr, "Get file information.", "\
*************** Not all these elements are relevant on a
*** 2060,2066 ****
  If an element is not relevant, it is returned as 0.
  
  If the @var{@3@} argument is supplied, it contains
! 0 on success or a non-zero error code upon return.
  
  Some non-GNU implementations of Fortran provide this intrinsic as
  only a function, not as a subroutine, or do not support the
--- 2060,2066 ----
  If an element is not relevant, it is returned as 0.
  
  If the @var{@3@} argument is supplied, it contains
! 0 on success or a nonzero error code upon return.
  
  Some non-GNU implementations of Fortran provide this intrinsic as
  only a function, not as a subroutine, or do not support the
*************** A null character (@samp{CHAR(0)}) marks 
*** 2073,2079 ****
  the names in @var{@1@} and @var{@2@}---otherwise,
  trailing blanks in @var{@1@} and @var{@2@} are ignored.
  If the @var{@3@} argument is supplied, it contains
! 0 on success or a non-zero error code upon return.
  See @code{link(2)}.
  
  Some non-GNU implementations of Fortran provide this intrinsic as
--- 2073,2079 ----
  the names in @var{@1@} and @var{@2@}---otherwise,
  trailing blanks in @var{@1@} and @var{@2@} are ignored.
  If the @var{@3@} argument is supplied, it contains
! 0 on success or a nonzero error code upon return.
  See @code{link(2)}.
  
  Some non-GNU implementations of Fortran provide this intrinsic as
*************** Makes a (hard) link from file @var{@1@} 
*** 2086,2092 ****
  A null character (@samp{CHAR(0)}) marks the end of
  the names in @var{@1@} and @var{@2@}---otherwise,
  trailing blanks in @var{@1@} and @var{@2@} are ignored.
! Returns 0 on success or a non-zero error code.
  See @code{link(2)}.
  
  Due to the side effects performed by this intrinsic, the function
--- 2086,2092 ----
  A null character (@samp{CHAR(0)}) marks the end of
  the names in @var{@1@} and @var{@2@}---otherwise,
  trailing blanks in @var{@1@} and @var{@2@} are ignored.
! Returns 0 on success or a nonzero error code.
  See @code{link(2)}.
  
  Due to the side effects performed by this intrinsic, the function
*************** A null character (@samp{CHAR(0)}) marks 
*** 2099,2105 ****
  the names in @var{@1@} and @var{@2@}---otherwise,
  trailing blanks in @var{@1@} and @var{@2@} are ignored.
  If the @var{@3@} argument is supplied, it contains
! 0 on success or a non-zero error code upon return
  (@code{ENOSYS} if the system does not provide @code{symlink(2)}).
  
  Some non-GNU implementations of Fortran provide this intrinsic as
--- 2099,2105 ----
  the names in @var{@1@} and @var{@2@}---otherwise,
  trailing blanks in @var{@1@} and @var{@2@} are ignored.
  If the @var{@3@} argument is supplied, it contains
! 0 on success or a nonzero error code upon return
  (@code{ENOSYS} if the system does not provide @code{symlink(2)}).
  
  Some non-GNU implementations of Fortran provide this intrinsic as
*************** Makes a symbolic link from file @var{@1@
*** 2112,2118 ****
  A null character (@samp{CHAR(0)}) marks the end of
  the names in @var{@1@} and @var{@2@}---otherwise,
  trailing blanks in @var{@1@} and @var{@2@} are ignored.
! Returns 0 on success or a non-zero error code
  (@code{ENOSYS} if the system does not provide @code{symlink(2)}).
  
  Due to the side effects performed by this intrinsic, the function
--- 2112,2118 ----
  A null character (@samp{CHAR(0)}) marks the end of
  the names in @var{@1@} and @var{@2@}---otherwise,
  trailing blanks in @var{@1@} and @var{@2@} are ignored.
! Returns 0 on success or a nonzero error code
  (@code{ENOSYS} if the system does not provide @code{symlink(2)}).
  
  Due to the side effects performed by this intrinsic, the function
*************** the names in @var{@1@} and @var{@2@}---o
*** 2126,2132 ****
  trailing blanks in @var{@1@} and @var{@2@} are ignored.
  See @code{rename(2)}.
  If the @var{@3@} argument is supplied, it contains
! 0 on success or a non-zero error code upon return.
  
  Some non-GNU implementations of Fortran provide this intrinsic as
  only a function, not as a subroutine, or do not support the
--- 2126,2132 ----
  trailing blanks in @var{@1@} and @var{@2@} are ignored.
  See @code{rename(2)}.
  If the @var{@3@} argument is supplied, it contains
! 0 on success or a nonzero error code upon return.
  
  Some non-GNU implementations of Fortran provide this intrinsic as
  only a function, not as a subroutine, or do not support the
*************** A null character (@samp{CHAR(0)}) marks 
*** 2139,2145 ****
  the names in @var{@1@} and @var{@2@}---otherwise,
  trailing blanks in @var{@1@} and @var{@2@} are ignored.
  See @code{rename(2)}.
! Returns 0 on success or a non-zero error code.
  
  Due to the side effects performed by this intrinsic, the function
  form is not recommended.
--- 2139,2145 ----
  the names in @var{@1@} and @var{@2@}---otherwise,
  trailing blanks in @var{@1@} and @var{@2@} are ignored.
  See @code{rename(2)}.
! Returns 0 on success or a nonzero error code.
  
  Due to the side effects performed by this intrinsic, the function
  form is not recommended.
*************** A null character (@samp{CHAR(0)}) marks 
*** 2168,2174 ****
  the name in @var{@1@}---otherwise,
  trailing blanks in @var{@1@} are ignored.
  If the @var{@2@} argument is supplied, it contains
! 0 on success or a non-zero error code upon return.
  See @code{unlink(2)}.
  
  Some non-GNU implementations of Fortran provide this intrinsic as
--- 2168,2174 ----
  the name in @var{@1@}---otherwise,
  trailing blanks in @var{@1@} are ignored.
  If the @var{@2@} argument is supplied, it contains
! 0 on success or a nonzero error code upon return.
  See @code{unlink(2)}.
  
  Some non-GNU implementations of Fortran provide this intrinsic as
*************** Unlink the file @var{@1@}.
*** 2181,2187 ****
  A null character (@samp{CHAR(0)}) marks the end of
  the name in @var{@1@}---otherwise,
  trailing blanks in @var{@1@} are ignored.
! Returns 0 on success or a non-zero error code.
  See @code{unlink(2)}.
  
  Due to the side effects performed by this intrinsic, the function
--- 2181,2187 ----
  A null character (@samp{CHAR(0)}) marks the end of
  the name in @var{@1@}---otherwise,
  trailing blanks in @var{@1@} are ignored.
! Returns 0 on success or a nonzero error code.
  See @code{unlink(2)}.
  
  Due to the side effects performed by this intrinsic, the function
*************** in @var{@1@}.
*** 2238,2244 ****
  
  DEFDOC (HOSTNM_func, "Get host name.", "\
  Fills @var{@1@} with the system's host name returned by
! @code{gethostname(2)}, returning 0 on success or a non-zero error code
  (@code{ENOSYS} if the system does not provide @code{gethostname(2)}).
  
  On some systems (specifically SCO) it might be necessary to link the
--- 2238,2244 ----
  
  DEFDOC (HOSTNM_func, "Get host name.", "\
  Fills @var{@1@} with the system's host name returned by
! @code{gethostname(2)}, returning 0 on success or a nonzero error code
  (@code{ENOSYS} if the system does not provide @code{gethostname(2)}).
  
  On some systems (specifically SCO) it might be necessary to link the
*************** DEFDOC (HOSTNM_subr, "Get host name.", "
*** 2251,2257 ****
  Fills @var{@1@} with the system's host name returned by
  @code{gethostname(2)}.
  If the @var{@2@} argument is supplied, it contains
! 0 on success or a non-zero error code upon return
  (@code{ENOSYS} if the system does not provide @code{gethostname(2)}).
  
  Some non-GNU implementations of Fortran provide this intrinsic as
--- 2251,2257 ----
  Fills @var{@1@} with the system's host name returned by
  @code{gethostname(2)}.
  If the @var{@2@} argument is supplied, it contains
! 0 on success or a nonzero error code upon return
  (@code{ENOSYS} if the system does not provide @code{gethostname(2)}).
  
  Some non-GNU implementations of Fortran provide this intrinsic as
*************** allowing you to take appropriate action.
*** 2513,2519 ****
  
  DEFDOC (KILL_func, "Signal a process.", "\
  Sends the signal specified by @var{@2@} to the process @var{@1@}.
! Returns 0 on success or a non-zero error code.
  See @code{kill(2)}.
  
  Due to the side effects performed by this intrinsic, the function
--- 2513,2519 ----
  
  DEFDOC (KILL_func, "Signal a process.", "\
  Sends the signal specified by @var{@2@} to the process @var{@1@}.
! Returns 0 on success or a nonzero error code.
  See @code{kill(2)}.
  
  Due to the side effects performed by this intrinsic, the function
*************** form is not recommended.
*** 2523,2529 ****
  DEFDOC (KILL_subr, "Signal a process.", "\
  Sends the signal specified by @var{@2@} to the process @var{@1@}.
  If the @var{@3@} argument is supplied, it contains
! 0 on success or a non-zero error code upon return.
  See @code{kill(2)}.
  
  Some non-GNU implementations of Fortran provide this intrinsic as
--- 2523,2529 ----
  DEFDOC (KILL_subr, "Signal a process.", "\
  Sends the signal specified by @var{@2@} to the process @var{@1@}.
  If the @var{@3@} argument is supplied, it contains
! 0 on success or a nonzero error code upon return.
  See @code{kill(2)}.
  
  Some non-GNU implementations of Fortran provide this intrinsic as
diff -Nrc3pad gcc-3.2.3/gcc/f/intdoc.texi gcc-3.3/gcc/f/intdoc.texi
*** gcc-3.2.3/gcc/f/intdoc.texi	2002-02-06 21:49:42.000000000 +0000
--- gcc-3.3/gcc/f/intdoc.texi	2003-05-14 00:18:14.000000000 +0000
*************** Description:
*** 2226,2232 ****
  
  Sets the current working directory to be @var{Dir}.
  If the @var{Status} argument is supplied, it contains 0
! on success or a non-zero error code otherwise upon return.
  See @code{chdir(3)}.
  
  @emph{Caution:} Using this routine during I/O to a unit connected with a
--- 2226,2232 ----
  
  Sets the current working directory to be @var{Dir}.
  If the @var{Status} argument is supplied, it contains 0
! on success or a nonzero error code otherwise upon return.
  See @code{chdir(3)}.
  
  @emph{Caution:} Using this routine during I/O to a unit connected with a
*************** Intrinsic groups: @code{badu77}.
*** 2265,2271 ****
  Description:
  
  Sets the current working directory to be @var{Dir}.
! Returns 0 on success or a non-zero error code.
  See @code{chdir(3)}.
  
  @emph{Caution:} Using this routine during I/O to a unit connected with a
--- 2265,2271 ----
  Description:
  
  Sets the current working directory to be @var{Dir}.
! Returns 0 on success or a nonzero error code.
  See @code{chdir(3)}.
  
  @emph{Caution:} Using this routine during I/O to a unit connected with a
*************** Currently, @var{Name} must not contain t
*** 2315,2321 ****
  character.
  
  If the @var{Status} argument is supplied, it contains
! 0 on success or a non-zero error code upon return.
  
  Note that this currently works
  by actually invoking @code{/bin/chmod} (or the @code{chmod} found when
--- 2315,2321 ----
  character.
  
  If the @var{Status} argument is supplied, it contains
! 0 on success or a nonzero error code upon return.
  
  Note that this currently works
  by actually invoking @code{/bin/chmod} (or the @code{chmod} found when
*************** trailing blanks in @var{Name} are ignore
*** 2365,2371 ****
  Currently, @var{Name} must not contain the single quote
  character.
  
! Returns 0 on success or a non-zero error code otherwise.
  
  Note that this currently works
  by actually invoking @code{/bin/chmod} (or the @code{chmod} found when
--- 2365,2371 ----
  Currently, @var{Name} must not contain the single quote
  character.
  
! Returns 0 on success or a nonzero error code otherwise.
  
  Note that this currently works
  by actually invoking @code{/bin/chmod} (or the @code{chmod} found when
*************** Not all these elements are relevant on a
*** 5067,5073 ****
  If an element is not relevant, it is returned as 0.
  
  If the @var{Status} argument is supplied, it contains
! 0 on success or a non-zero error code upon return.
  
  Some non-GNU implementations of Fortran provide this intrinsic as
  only a function, not as a subroutine, or do not support the
--- 5067,5073 ----
  If an element is not relevant, it is returned as 0.
  
  If the @var{Status} argument is supplied, it contains
! 0 on success or a nonzero error code upon return.
  
  Some non-GNU implementations of Fortran provide this intrinsic as
  only a function, not as a subroutine, or do not support the
*************** Number of blocks allocated (-1 if not av
*** 5152,5158 ****
  Not all these elements are relevant on all systems.
  If an element is not relevant, it is returned as 0.
  
! Returns 0 on success or a non-zero error code.
  
  For information on other intrinsics with the same name:
  @xref{FStat Intrinsic (subroutine)}.
--- 5152,5158 ----
  Not all these elements are relevant on all systems.
  If an element is not relevant, it is returned as 0.
  
! Returns 0 on success or a nonzero error code.
  
  For information on other intrinsics with the same name:
  @xref{FStat Intrinsic (subroutine)}.
*************** Description:
*** 5292,5298 ****
  
  Places the current working directory in @var{Name}.
  If the @var{Status} argument is supplied, it contains 0
! success or a non-zero error code upon return
  (@code{ENOSYS} if the system does not provide @code{getcwd(3)}
  or @code{getwd(3)}).
  
--- 5292,5298 ----
  
  Places the current working directory in @var{Name}.
  If the @var{Status} argument is supplied, it contains 0
! success or a nonzero error code upon return
  (@code{ENOSYS} if the system does not provide @code{getcwd(3)}
  or @code{getwd(3)}).
  
*************** Description:
*** 5327,5333 ****
  
  Places the current working directory in @var{Name}.
  Returns 0 on
! success, otherwise a non-zero error code
  (@code{ENOSYS} if the system does not provide @code{getcwd(3)}
  or @code{getwd(3)}).
  
--- 5327,5333 ----
  
  Places the current working directory in @var{Name}.
  Returns 0 on
! success, otherwise a nonzero error code
  (@code{ENOSYS} if the system does not provide @code{getcwd(3)}
  or @code{getwd(3)}).
  
*************** Description:
*** 5537,5543 ****
  Fills @var{Name} with the system's host name returned by
  @code{gethostname(2)}.
  If the @var{Status} argument is supplied, it contains
! 0 on success or a non-zero error code upon return
  (@code{ENOSYS} if the system does not provide @code{gethostname(2)}).
  
  Some non-GNU implementations of Fortran provide this intrinsic as
--- 5537,5543 ----
  Fills @var{Name} with the system's host name returned by
  @code{gethostname(2)}.
  If the @var{Status} argument is supplied, it contains
! 0 on success or a nonzero error code upon return
  (@code{ENOSYS} if the system does not provide @code{gethostname(2)}).
  
  Some non-GNU implementations of Fortran provide this intrinsic as
*************** Intrinsic groups: @code{unix}.
*** 5575,5581 ****
  Description:
  
  Fills @var{Name} with the system's host name returned by
! @code{gethostname(2)}, returning 0 on success or a non-zero error code
  (@code{ENOSYS} if the system does not provide @code{gethostname(2)}).
  
  On some systems (specifically SCO) it might be necessary to link the
--- 5575,5581 ----
  Description:
  
  Fills @var{Name} with the system's host name returned by
! @code{gethostname(2)}, returning 0 on success or a nonzero error code
  (@code{ENOSYS} if the system does not provide @code{gethostname(2)}).
  
  On some systems (specifically SCO) it might be necessary to link the
*************** magnitude truncated and its sign preserv
*** 6543,6549 ****
  to type @code{INTEGER(KIND=6)}.
  
  If @var{A} is type @code{COMPLEX}, its real part
! is truncated and converted, and its imaginary part is disgregarded.
  
  @xref{Int Intrinsic}.
  
--- 6543,6549 ----
  to type @code{INTEGER(KIND=6)}.
  
  If @var{A} is type @code{COMPLEX}, its real part
! is truncated and converted, and its imaginary part is disregarded.
  
  @xref{Int Intrinsic}.
  
*************** magnitude truncated and its sign preserv
*** 6578,6584 ****
  to type @code{INTEGER(KIND=2)}.
  
  If @var{A} is type @code{COMPLEX}, its real part
! is truncated and converted, and its imaginary part is disgregarded.
  
  @xref{Int Intrinsic}.
  
--- 6578,6584 ----
  to type @code{INTEGER(KIND=2)}.
  
  If @var{A} is type @code{COMPLEX}, its real part
! is truncated and converted, and its imaginary part is disregarded.
  
  @xref{Int Intrinsic}.
  
*************** Description:
*** 7107,7113 ****
  
  Sends the signal specified by @var{Signal} to the process @var{Pid}.
  If the @var{Status} argument is supplied, it contains
! 0 on success or a non-zero error code upon return.
  See @code{kill(2)}.
  
  Some non-GNU implementations of Fortran provide this intrinsic as
--- 7107,7113 ----
  
  Sends the signal specified by @var{Signal} to the process @var{Pid}.
  If the @var{Status} argument is supplied, it contains
! 0 on success or a nonzero error code upon return.
  See @code{kill(2)}.
  
  Some non-GNU implementations of Fortran provide this intrinsic as
*************** Intrinsic groups: @code{badu77}.
*** 7145,7151 ****
  Description:
  
  Sends the signal specified by @var{Signal} to the process @var{Pid}.
! Returns 0 on success or a non-zero error code.
  See @code{kill(2)}.
  
  Due to the side effects performed by this intrinsic, the function
--- 7145,7151 ----
  Description:
  
  Sends the signal specified by @var{Signal} to the process @var{Pid}.
! Returns 0 on success or a nonzero error code.
  See @code{kill(2)}.
  
  Due to the side effects performed by this intrinsic, the function
*************** A null character (@samp{CHAR(0)}) marks 
*** 7377,7383 ****
  the names in @var{Path1} and @var{Path2}---otherwise,
  trailing blanks in @var{Path1} and @var{Path2} are ignored.
  If the @var{Status} argument is supplied, it contains
! 0 on success or a non-zero error code upon return.
  See @code{link(2)}.
  
  Some non-GNU implementations of Fortran provide this intrinsic as
--- 7377,7383 ----
  the names in @var{Path1} and @var{Path2}---otherwise,
  trailing blanks in @var{Path1} and @var{Path2} are ignored.
  If the @var{Status} argument is supplied, it contains
! 0 on success or a nonzero error code upon return.
  See @code{link(2)}.
  
  Some non-GNU implementations of Fortran provide this intrinsic as
*************** Makes a (hard) link from file @var{Path1
*** 7418,7424 ****
  A null character (@samp{CHAR(0)}) marks the end of
  the names in @var{Path1} and @var{Path2}---otherwise,
  trailing blanks in @var{Path1} and @var{Path2} are ignored.
! Returns 0 on success or a non-zero error code.
  See @code{link(2)}.
  
  Due to the side effects performed by this intrinsic, the function
--- 7418,7424 ----
  A null character (@samp{CHAR(0)}) marks the end of
  the names in @var{Path1} and @var{Path2}---otherwise,
  trailing blanks in @var{Path1} and @var{Path2} are ignored.
! Returns 0 on success or a nonzero error code.
  See @code{link(2)}.
  
  Due to the side effects performed by this intrinsic, the function
*************** Not all these elements are relevant on a
*** 7802,7808 ****
  If an element is not relevant, it is returned as 0.
  
  If the @var{Status} argument is supplied, it contains
! 0 on success or a non-zero error code upon return
  (@code{ENOSYS} if the system does not provide @code{lstat(2)}).
  
  Some non-GNU implementations of Fortran provide this intrinsic as
--- 7802,7808 ----
  If an element is not relevant, it is returned as 0.
  
  If the @var{Status} argument is supplied, it contains
! 0 on success or a nonzero error code upon return
  (@code{ENOSYS} if the system does not provide @code{lstat(2)}).
  
  Some non-GNU implementations of Fortran provide this intrinsic as
*************** Number of blocks allocated (-1 if not av
*** 7893,7899 ****
  Not all these elements are relevant on all systems.
  If an element is not relevant, it is returned as 0.
  
! Returns 0 on success or a non-zero error code
  (@code{ENOSYS} if the system does not provide @code{lstat(2)}).
  
  For information on other intrinsics with the same name:
--- 7893,7899 ----
  Not all these elements are relevant on all systems.
  If an element is not relevant, it is returned as 0.
  
! Returns 0 on success or a nonzero error code
  (@code{ENOSYS} if the system does not provide @code{lstat(2)}).
  
  For information on other intrinsics with the same name:
*************** the names in @var{Path1} and @var{Path2}
*** 9085,9091 ****
  trailing blanks in @var{Path1} and @var{Path2} are ignored.
  See @code{rename(2)}.
  If the @var{Status} argument is supplied, it contains
! 0 on success or a non-zero error code upon return.
  
  Some non-GNU implementations of Fortran provide this intrinsic as
  only a function, not as a subroutine, or do not support the
--- 9085,9091 ----
  trailing blanks in @var{Path1} and @var{Path2} are ignored.
  See @code{rename(2)}.
  If the @var{Status} argument is supplied, it contains
! 0 on success or a nonzero error code upon return.
  
  Some non-GNU implementations of Fortran provide this intrinsic as
  only a function, not as a subroutine, or do not support the
*************** A null character (@samp{CHAR(0)}) marks 
*** 9126,9132 ****
  the names in @var{Path1} and @var{Path2}---otherwise,
  trailing blanks in @var{Path1} and @var{Path2} are ignored.
  See @code{rename(2)}.
! Returns 0 on success or a non-zero error code.
  
  Due to the side effects performed by this intrinsic, the function
  form is not recommended.
--- 9126,9132 ----
  the names in @var{Path1} and @var{Path2}---otherwise,
  trailing blanks in @var{Path1} and @var{Path2} are ignored.
  See @code{rename(2)}.
! Returns 0 on success or a nonzero error code.
  
  Due to the side effects performed by this intrinsic, the function
  form is not recommended.
*************** magnitude truncated and its sign preserv
*** 9418,9424 ****
  to type @code{INTEGER(KIND=6)}.
  
  If @var{A} is type @code{COMPLEX}, its real part
! is truncated and converted, and its imaginary part is disgregarded.
  
  @xref{Int Intrinsic}.
  
--- 9418,9424 ----
  to type @code{INTEGER(KIND=6)}.
  
  If @var{A} is type @code{COMPLEX}, its real part
! is truncated and converted, and its imaginary part is disregarded.
  
  @xref{Int Intrinsic}.
  
*************** Intrinsic groups: @code{unix}.
*** 9848,9854 ****
  @noindent
  Description:
  
! Reinitialises the generator with the seed in @var{Seed}.
  @xref{IRand Intrinsic}.
  @xref{Rand Intrinsic}.
  
--- 9848,9854 ----
  @noindent
  Description:
  
! Reinitializes the generator with the seed in @var{Seed}.
  @xref{IRand Intrinsic}.
  @xref{Rand Intrinsic}.
  
*************** Not all these elements are relevant on a
*** 9931,9937 ****
  If an element is not relevant, it is returned as 0.
  
  If the @var{Status} argument is supplied, it contains
! 0 on success or a non-zero error code upon return.
  
  Some non-GNU implementations of Fortran provide this intrinsic as
  only a function, not as a subroutine, or do not support the
--- 9931,9937 ----
  If an element is not relevant, it is returned as 0.
  
  If the @var{Status} argument is supplied, it contains
! 0 on success or a nonzero error code upon return.
  
  Some non-GNU implementations of Fortran provide this intrinsic as
  only a function, not as a subroutine, or do not support the
*************** Number of blocks allocated (-1 if not av
*** 10018,10024 ****
  Not all these elements are relevant on all systems.
  If an element is not relevant, it is returned as 0.
  
! Returns 0 on success or a non-zero error code.
  
  For information on other intrinsics with the same name:
  @xref{Stat Intrinsic (subroutine)}.
--- 10018,10024 ----
  Not all these elements are relevant on all systems.
  If an element is not relevant, it is returned as 0.
  
! Returns 0 on success or a nonzero error code.
  
  For information on other intrinsics with the same name:
  @xref{Stat Intrinsic (subroutine)}.
*************** A null character (@samp{CHAR(0)}) marks 
*** 10067,10073 ****
  the names in @var{Path1} and @var{Path2}---otherwise,
  trailing blanks in @var{Path1} and @var{Path2} are ignored.
  If the @var{Status} argument is supplied, it contains
! 0 on success or a non-zero error code upon return
  (@code{ENOSYS} if the system does not provide @code{symlink(2)}).
  
  Some non-GNU implementations of Fortran provide this intrinsic as
--- 10067,10073 ----
  the names in @var{Path1} and @var{Path2}---otherwise,
  trailing blanks in @var{Path1} and @var{Path2} are ignored.
  If the @var{Status} argument is supplied, it contains
! 0 on success or a nonzero error code upon return
  (@code{ENOSYS} if the system does not provide @code{symlink(2)}).
  
  Some non-GNU implementations of Fortran provide this intrinsic as
*************** Makes a symbolic link from file @var{Pat
*** 10108,10114 ****
  A null character (@samp{CHAR(0)}) marks the end of
  the names in @var{Path1} and @var{Path2}---otherwise,
  trailing blanks in @var{Path1} and @var{Path2} are ignored.
! Returns 0 on success or a non-zero error code
  (@code{ENOSYS} if the system does not provide @code{symlink(2)}).
  
  Due to the side effects performed by this intrinsic, the function
--- 10108,10114 ----
  A null character (@samp{CHAR(0)}) marks the end of
  the names in @var{Path1} and @var{Path2}---otherwise,
  trailing blanks in @var{Path1} and @var{Path2} are ignored.
! Returns 0 on success or a nonzero error code
  (@code{ENOSYS} if the system does not provide @code{symlink(2)}).
  
  Due to the side effects performed by this intrinsic, the function
*************** A null character (@samp{CHAR(0)}) marks 
*** 10657,10663 ****
  the name in @var{File}---otherwise,
  trailing blanks in @var{File} are ignored.
  If the @var{Status} argument is supplied, it contains
! 0 on success or a non-zero error code upon return.
  See @code{unlink(2)}.
  
  Some non-GNU implementations of Fortran provide this intrinsic as
--- 10657,10663 ----
  the name in @var{File}---otherwise,
  trailing blanks in @var{File} are ignored.
  If the @var{Status} argument is supplied, it contains
! 0 on success or a nonzero error code upon return.
  See @code{unlink(2)}.
  
  Some non-GNU implementations of Fortran provide this intrinsic as
*************** Unlink the file @var{File}.
*** 10695,10701 ****
  A null character (@samp{CHAR(0)}) marks the end of
  the name in @var{File}---otherwise,
  trailing blanks in @var{File} are ignored.
! Returns 0 on success or a non-zero error code.
  See @code{unlink(2)}.
  
  Due to the side effects performed by this intrinsic, the function
--- 10695,10701 ----
  A null character (@samp{CHAR(0)}) marks the end of
  the name in @var{File}---otherwise,
  trailing blanks in @var{File} are ignored.
! Returns 0 on success or a nonzero error code.
  See @code{unlink(2)}.
  
  Due to the side effects performed by this intrinsic, the function
diff -Nrc3pad gcc-3.2.3/gcc/f/invoke.texi gcc-3.3/gcc/f/invoke.texi
*** gcc-3.2.3/gcc/f/invoke.texi	2002-11-22 23:57:18.000000000 +0000
--- gcc-3.3/gcc/f/invoke.texi	2003-02-04 01:55:41.000000000 +0000
*************** Copyright @copyright{} 1996, 1997, 1998,
*** 9,15 ****
  Free Software Foundation, Inc.
  
  Permission is granted to copy, distribute and/or modify this document
! under the terms of the GNU Free Documentation License, Version 1.1 or
  any later version published by the Free Software Foundation; with the
  Invariant Sections being ``GNU General Public License'' and ``Funding
  Free Software'', the Front-Cover texts being (a) (see below), and with
--- 9,15 ----
  Free Software Foundation, Inc.
  
  Permission is granted to copy, distribute and/or modify this document
! under the terms of the GNU Free Documentation License, Version 1.2 or
  any later version published by the Free Software Foundation; with the
  Invariant Sections being ``GNU General Public License'' and ``Funding
  Free Software'', the Front-Cover texts being (a) (see below), and with
*************** by type.  Explanations are in the follow
*** 182,188 ****
  -malign-double @gol
  -ffloat-store  -fforce-mem  -fforce-addr  -fno-inline @gol
  -ffast-math  -fstrength-reduce  -frerun-cse-after-loop @gol
! -funsafe-math-optimizations -fno-trapping-math @gol
  -fexpensive-optimizations  -fdelayed-branch @gol
  -fschedule-insns  -fschedule-insn2  -fcaller-saves @gol
  -funroll-loops  -funroll-all-loops @gol
--- 182,188 ----
  -malign-double @gol
  -ffloat-store  -fforce-mem  -fforce-addr  -fno-inline @gol
  -ffast-math  -fstrength-reduce  -frerun-cse-after-loop @gol
! -funsafe-math-optimizations -ffinite-math-only -fno-trapping-math @gol
  -fexpensive-optimizations  -fdelayed-branch @gol
  -fschedule-insns  -fschedule-insn2  -fcaller-saves @gol
  -funroll-loops  -funroll-all-loops @gol
*************** This option is supplied automatically wh
*** 389,395 ****
  is specified as a command-line option for @command{g77} or @command{gcc}
  and when the resulting commands compile Fortran source files.
  
! In GCC 3.1, this is changed back to the behaviour @command{gcc} displays
  for @samp{.c} files.
  
  @cindex -fset-g77-defaults option
--- 389,395 ----
  is specified as a command-line option for @command{g77} or @command{gcc}
  and when the resulting commands compile Fortran source files.
  
! In GCC 3.1, this is changed back to the behavior @command{gcc} displays
  for @samp{.c} files.
  
  @cindex -fset-g77-defaults option
*************** Some of these have no effect when compil
*** 1356,1361 ****
--- 1356,1367 ----
  @cindex -Wswitch option
  @cindex options, -Wswitch
  @item -Wswitch
+ @cindex -Wswitch-default option
+ @cindex options, -Wswitch-default
+ @item -Wswitch-default
+ @cindex -Wswitch-enum option
+ @cindex options, -Wswitch-enum
+ @item -Wswitch-enum
  @cindex -Wtraditional option
  @cindex options, -Wtraditional
  @item -Wtraditional
*************** Note that if you are not optimizing, no 
*** 1536,1543 ****
  @cindex conformance, IEEE 754
  Might allow some programs designed to not be too dependent
  on IEEE behavior for floating-point to run faster, or die trying.
! Sets @option{-funsafe-math-optimizations}, and
! @option{-fno-trapping-math}.
  
  @cindex -funsafe-math-optimizations option
  @cindex options, -funsafe-math-optimizations
--- 1542,1549 ----
  @cindex conformance, IEEE 754
  Might allow some programs designed to not be too dependent
  on IEEE behavior for floating-point to run faster, or die trying.
! Sets @option{-funsafe-math-optimizations}, @option{-ffinite-math-only},
! and @option{-fno-trapping-math}.
  
  @cindex -funsafe-math-optimizations option
  @cindex options, -funsafe-math-optimizations
*************** Sets @option{-funsafe-math-optimizations
*** 1545,1550 ****
--- 1551,1568 ----
  Allow optimizations that may be give incorrect results
  for certain IEEE inputs.
  
+ @cindex -ffinite-math-only option
+ @cindex options, -ffinite-math-only
+ @item -ffinite-math-only
+ Allow optimizations for floating-point arithmetic that assume
+ that arguments and results are not NaNs or +-Infs.
+ 
+ This option should never be turned on by any @option{-O} option since
+ it can result in incorrect output for programs which depend on
+ an exact implementation of IEEE or ISO rules/specifications.
+ 
+ The default is @option{-fno-finite-math-only}.
+ 
  @cindex -fno-trapping-math option
  @cindex options, -fno-trapping-math
  @item -fno-trapping-math
diff -Nrc3pad gcc-3.2.3/gcc/f/lang-specs.h gcc-3.3/gcc/f/lang-specs.h
*** gcc-3.2.3/gcc/f/lang-specs.h	2002-10-28 21:53:38.000000000 +0000
--- gcc-3.3/gcc/f/lang-specs.h	2003-01-26 22:07:32.000000000 +0000
***************
*** 1,5 ****
  /* lang-specs.h file for Fortran
!    Copyright (C) 1995, 1996, 1997, 1999, 2000, 2002
     Free Software Foundation, Inc.
     Contributed by James Craig Burley.
  
--- 1,5 ----
  /* lang-specs.h file for Fortran
!    Copyright (C) 1995, 1996, 1997, 1999, 2000, 2002, 2003
     Free Software Foundation, Inc.
     Contributed by James Craig Burley.
  
*************** the Free Software Foundation, 59 Temple 
*** 29,40 ****
    {".fpp", "@f77-cpp-input", 0},
    {".FPP", "@f77-cpp-input", 0},
    {"@f77-cpp-input",
!    "tradcpp0 -lang-fortran %(cpp_options) %{!M:%{!MM:%{!E:%{!pipe:%g.f} |\n\
      f771 %{!pipe:%g.f} %(cc1_options) %{I*} %{!fsyntax-only:%(invoke_as)}}}}", 0},
    {".r", "@ratfor", 0},
    {"@ratfor",
     "%{C:%{!E:%eGNU C does not support -C without using -E}}\
!     ratfor %{C} %{v} %{E:%W{o*}} %{!E: %{!pipe:-o %g.f} %i |\n\
      f771 %{!pipe:%g.f} %(cc1_options) %{I*} %{!fsyntax-only:%(invoke_as)}}", 0},
    {".f",   "@f77", 0},
    {".for", "@f77", 0},
--- 29,43 ----
    {".fpp", "@f77-cpp-input", 0},
    {".FPP", "@f77-cpp-input", 0},
    {"@f77-cpp-input",
!    "cc1 -E -traditional-cpp -D_LANGUAGE_FORTRAN %(cpp_options) \
!         %{E|M|MM:%(cpp_debug_options)}\
!         %{!M:%{!MM:%{!E:%{!pipe:%g.f} |\n\
      f771 %{!pipe:%g.f} %(cc1_options) %{I*} %{!fsyntax-only:%(invoke_as)}}}}", 0},
    {".r", "@ratfor", 0},
    {"@ratfor",
     "%{C:%{!E:%eGNU C does not support -C without using -E}}\
!     %{CC:%{!E:%eGNU C does not support -CC without using -E}}\
!     ratfor %{C} %{CC} %{v} %{E:%W{o*}} %{!E: %{!pipe:-o %g.f} %i |\n\
      f771 %{!pipe:%g.f} %(cc1_options) %{I*} %{!fsyntax-only:%(invoke_as)}}", 0},
    {".f",   "@f77", 0},
    {".for", "@f77", 0},
diff -Nrc3pad gcc-3.2.3/gcc/f/lex.c gcc-3.3/gcc/f/lex.c
*** gcc-3.2.3/gcc/f/lex.c	2002-02-04 16:07:58.000000000 +0000
--- gcc-3.3/gcc/f/lex.c	2002-08-22 02:20:42.000000000 +0000
*************** static ffelexType ffelex_first_char_[256
*** 93,99 ****
  
  /* The wf argument of the most recent active ffelex_file_(fixed,free)
     function.  */
! static ffewhereFile ffelex_current_wf_;
  
  /* TRUE if an INCLUDE statement can be processed (ffelex_set_include
     can be called).  */
--- 93,99 ----
  
  /* The wf argument of the most recent active ffelex_file_(fixed,free)
     function.  */
! static GTY (()) ffewhereFile ffelex_current_wf_;
  
  /* TRUE if an INCLUDE statement can be processed (ffelex_set_include
     can be called).  */
*************** static bool ffelex_set_include_;
*** 106,112 ****
  /* Information on the pending INCLUDE file.  */
  static FILE *ffelex_include_file_;
  static bool ffelex_include_free_form_;
! static ffewhereFile ffelex_include_wherefile_;
  
  /* Current master line count.  */
  static ffewhereLineNumber ffelex_linecount_current_;
--- 106,112 ----
  /* Information on the pending INCLUDE file.  */
  static FILE *ffelex_include_file_;
  static bool ffelex_include_free_form_;
! static GTY(()) ffewhereFile ffelex_include_wherefile_;
  
  /* Current master line count.  */
  static ffewhereLineNumber ffelex_linecount_current_;
*************** ffelex_backslash_ (int c, ffewhereColumn
*** 246,253 ****
       hollerith constants.  */
  
  #define wide_flag 0
- #define warn_traditional 0
- #define flag_traditional 0
  
    switch (state)
      {
--- 246,251 ----
*************** ffelex_backslash_ (int c, ffewhereColumn
*** 268,285 ****
        switch (c)
  	{
  	case 'x':
- 	  if (warn_traditional)
- 	    {
- 	      /* xgettext:no-c-format */
- 	      ffebad_start_msg_lex ("The meaning of `\\x' (at %0) varies with -traditional",
- 				    FFEBAD_severityWARNING);
- 	      ffelex_bad_here_ (0, line, column);
- 	      ffebad_finish ();
- 	    }
- 
- 	  if (flag_traditional)
- 	    return c;
- 
  	  code = 0;
  	  count = 0;
  	  nonnull = 0;
--- 266,271 ----
*************** ffelex_backslash_ (int c, ffewhereColumn
*** 319,342 ****
  	  return TARGET_BS;
  
  	case 'a':
- 	  if (warn_traditional)
- 	    {
- 	      /* xgettext:no-c-format */
- 	      ffebad_start_msg_lex ("The meaning of `\\a' (at %0) varies with -traditional",
- 				    FFEBAD_severityWARNING);
- 	      ffelex_bad_here_ (0, line, column);
- 	      ffebad_finish ();
- 	    }
- 
- 	  if (flag_traditional)
- 	    return c;
  	  return TARGET_BELL;
  
  	case 'v':
- #if 0 /* Vertical tab is present in common usage compilers.  */
- 	  if (flag_traditional)
- 	    return c;
- #endif
  	  return TARGET_VT;
  
  	case 'e':
--- 305,313 ----
*************** ffelex_cfebackslash_ (int *use_d, int *d
*** 589,600 ****
    switch (c)
      {
      case 'x':
-       if (warn_traditional)
- 	warning ("the meaning of `\\x' varies with -traditional");
- 
-       if (flag_traditional)
- 	return c;
- 
        code = 0;
        count = 0;
        nonnull = 0;
--- 560,565 ----
*************** ffelex_cfebackslash_ (int *use_d, int *d
*** 672,689 ****
        return TARGET_BS;
  
      case 'a':
-       if (warn_traditional)
- 	warning ("the meaning of `\\a' varies with -traditional");
- 
-       if (flag_traditional)
- 	return c;
        return TARGET_BELL;
  
      case 'v':
- #if 0 /* Vertical tab is present in common usage compilers.  */
-       if (flag_traditional)
- 	return c;
- #endif
        return TARGET_VT;
  
      case 'e':
--- 637,645 ----
*************** ffelex_token_use (ffelexToken t)
*** 4678,4680 ****
--- 4634,4638 ----
    t->uses++;
    return t;
  }
+ 
+ #include "gt-f-lex.h"
diff -Nrc3pad gcc-3.2.3/gcc/f/Make-lang.in gcc-3.3/gcc/f/Make-lang.in
*** gcc-3.2.3/gcc/f/Make-lang.in	2003-01-28 21:52:58.000000000 +0000
--- gcc-3.3/gcc/f/Make-lang.in	2003-01-26 11:31:24.000000000 +0000
***************
*** 1,5 ****
  # Top level makefile fragment for GNU Fortran.           -*-makefile-*-
! #   Copyright (C) 1995, 1996, 1997, 1998, 2000, 2001, 2002 Free Software Foundation, Inc.
  
  #This file is part of GNU Fortran.
  
--- 1,5 ----
  # Top level makefile fragment for GNU Fortran.           -*-makefile-*-
! #   Copyright (C) 1995, 1996, 1997, 1998, 2000, 2001, 2002, 2003 Free Software Foundation, Inc.
  
  #This file is part of GNU Fortran.
  
*************** F77 f77: f771$(exeext)
*** 65,85 ****
    f77.extraclean f77.maintainer-clean f77.rebuilt \
    f77.stage1 f77.stage2 f77.stage3 f77.stage4
  
! g77spec.o: $(srcdir)/f/g77spec.c $(srcdir)/f/version.h $(SYSTEM_H) $(GCC_H) \
  	$(CONFIG_H)
  	(SHLIB_LINK='$(SHLIB_LINK)' \
  	SHLIB_MULTILIB='$(SHLIB_MULTILIB)'; \
  	$(CC) -c $(ALL_CFLAGS) $(ALL_CPPFLAGS) $(DRIVER_DEFINES) \
  		$(INCLUDES) $(srcdir)/f/g77spec.c)
  
- g77version.o: $(srcdir)/f/version.c
- 	$(CC) -c $(ALL_CFLAGS) $(ALL_CPPFLAGS) $(INCLUDES) -o g77version.o \
- 	    $(srcdir)/f/version.c
- 
  # Create the compiler driver for g77.
! g77$(exeext): gcc.o g77spec.o g77version.o version.o prefix.o intl.o \
    $(LIBDEPS) $(EXTRA_GCC_OBJS)
! 	$(CC) $(ALL_CFLAGS) $(LDFLAGS) -o $@ gcc.o g77spec.o g77version.o \
  	   version.o prefix.o intl.o $(EXTRA_GCC_OBJS) $(LIBS)
  
  # Create a version of the g77 driver which calls the cross-compiler.
--- 65,81 ----
    f77.extraclean f77.maintainer-clean f77.rebuilt \
    f77.stage1 f77.stage2 f77.stage3 f77.stage4
  
! g77spec.o: $(srcdir)/f/g77spec.c $(SYSTEM_H) $(GCC_H) \
  	$(CONFIG_H)
  	(SHLIB_LINK='$(SHLIB_LINK)' \
  	SHLIB_MULTILIB='$(SHLIB_MULTILIB)'; \
  	$(CC) -c $(ALL_CFLAGS) $(ALL_CPPFLAGS) $(DRIVER_DEFINES) \
  		$(INCLUDES) $(srcdir)/f/g77spec.c)
  
  # Create the compiler driver for g77.
! g77$(exeext): gcc.o g77spec.o version.o prefix.o intl.o \
    $(LIBDEPS) $(EXTRA_GCC_OBJS)
! 	$(CC) $(ALL_CFLAGS) $(LDFLAGS) -o $@ gcc.o g77spec.o \
  	   version.o prefix.o intl.o $(EXTRA_GCC_OBJS) $(LIBS)
  
  # Create a version of the g77 driver which calls the cross-compiler.
*************** F77_OBJS = f/bad.o f/bit.o f/bld.o f/com
*** 93,99 ****
   f/global.o f/implic.o f/info.o f/intrin.o f/lab.o f/lex.o f/malloc.o \
   f/name.o f/parse.o f/src.o f/st.o f/sta.o f/stb.o f/stc.o \
   f/std.o f/ste.o f/storag.o f/stp.o f/str.o f/sts.o f/stt.o f/stu.o \
!  f/stv.o f/stw.o f/symbol.o f/target.o f/top.o f/type.o f/version.o f/where.o
  
  # Use loose warnings for this front end.
  f-warn =
--- 89,95 ----
   f/global.o f/implic.o f/info.o f/intrin.o f/lab.o f/lex.o f/malloc.o \
   f/name.o f/parse.o f/src.o f/st.o f/sta.o f/stb.o f/stc.o \
   f/std.o f/ste.o f/storag.o f/stp.o f/str.o f/sts.o f/stt.o f/stu.o \
!  f/stv.o f/stw.o f/symbol.o f/target.o f/top.o f/type.o f/where.o
  
  # Use loose warnings for this front end.
  f-warn =
*************** f/fini.o:
*** 137,142 ****
--- 133,140 ----
  	$(HOST_CC) $(HOST_CFLAGS) $(HOST_CPPFLAGS) $(INCLUDES) \
  	      -c $(srcdir)/f/fini.c $(OUTPUT_OPTION)
  
+ gt-f-lex.h gt-f-where.h gt-f-com.h gt-f-ste.h gtype-f.h : s-gtype; @true
+ 
  #
  # Build hooks:
  
*************** $(srcdir)/f/g77.info: $(srcdir)/f/g77.te
*** 155,161 ****
  		$(srcdir)/f/news.texi  $(srcdir)/f/intdoc.texi \
  		$(srcdir)/f/root.texi $(srcdir)/doc/include/fdl.texi \
  		$(srcdir)/doc/include/gpl.texi \
! 		$(srcdir)/doc/include/funding.texi
  	if [ x$(BUILD_INFO) = xinfo ]; then \
  	  rm -f $(srcdir)/f/g77.info-*; \
  	  cd $(srcdir)/f && $(MAKEINFO) -I../doc/include -o g77.info g77.texi; \
--- 153,160 ----
  		$(srcdir)/f/news.texi  $(srcdir)/f/intdoc.texi \
  		$(srcdir)/f/root.texi $(srcdir)/doc/include/fdl.texi \
  		$(srcdir)/doc/include/gpl.texi \
! 		$(srcdir)/doc/include/funding.texi \
! 		$(srcdir)/doc/include/gcc-common.texi
  	if [ x$(BUILD_INFO) = xinfo ]; then \
  	  rm -f $(srcdir)/f/g77.info-*; \
  	  cd $(srcdir)/f && $(MAKEINFO) -I../doc/include -o g77.info g77.texi; \
*************** f/g77.dvi: $(srcdir)/f/g77.texi $(srcdir
*** 166,173 ****
  		$(srcdir)/f/news.texi  $(srcdir)/f/intdoc.texi \
  		$(srcdir)/f/root.texi $(srcdir)/doc/include/fdl.texi \
  		$(srcdir)/doc/include/gpl.texi \
! 		$(srcdir)/doc/include/funding.texi
! 	s=`cd $(srcdir); pwd`; export s; \
  	cd f && $(TEXI2DVI) -I $$s/doc/include $$s/f/g77.texi
  
  $(srcdir)/f/g77.1: $(srcdir)/f/invoke.texi
--- 165,173 ----
  		$(srcdir)/f/news.texi  $(srcdir)/f/intdoc.texi \
  		$(srcdir)/f/root.texi $(srcdir)/doc/include/fdl.texi \
  		$(srcdir)/doc/include/gpl.texi \
! 		$(srcdir)/doc/include/funding.texi \
! 		$(srcdir)/doc/include/gcc-common.texi
! 	s=`cd $(srcdir); ${PWD}`; export s; \
  	cd f && $(TEXI2DVI) -I $$s/doc/include $$s/f/g77.texi
  
  $(srcdir)/f/g77.1: $(srcdir)/f/invoke.texi
*************** f/ansify$(build_exeext): f/ansify.c hcon
*** 226,236 ****
  
  $(srcdir)/f/BUGS: f/bugs0.texi f/bugs.texi f/root.texi
  	cd $(srcdir)/f; $(MAKEINFO) -D BUGSONLY --no-header --no-split \
! 	  --no-validate -o BUGS bugs0.texi
  
  $(srcdir)/f/NEWS: f/news0.texi f/news.texi f/root.texi
  	cd $(srcdir)/f; $(MAKEINFO) -D NEWSONLY --no-header --no-split \
! 	  --no-validate -o NEWS news0.texi
  
  f77.rebuilt: f/g77.info $(srcdir)/f/BUGS \
    $(srcdir)/f/NEWS 
--- 226,236 ----
  
  $(srcdir)/f/BUGS: f/bugs0.texi f/bugs.texi f/root.texi
  	cd $(srcdir)/f; $(MAKEINFO) -D BUGSONLY --no-header --no-split \
! 	  --no-validate -I../doc/include -o BUGS bugs0.texi
  
  $(srcdir)/f/NEWS: f/news0.texi f/news.texi f/root.texi
  	cd $(srcdir)/f; $(MAKEINFO) -D NEWSONLY --no-header --no-split \
! 	  --no-validate -I../doc/include -o NEWS news0.texi
  
  f77.rebuilt: f/g77.info $(srcdir)/f/BUGS \
    $(srcdir)/f/NEWS 
*************** f77.uninstall: installdirs
*** 313,324 ****
  
  f77.mostlyclean:
  	-rm -f f/*$(objext)
  	-rm -f f/fini$(build_exeext) f/stamp-str f/str-*.h f/str-*.j
  	-rm -f f/intdoc$(build_exeext) f/ansify$(build_exeext) f/intdoc.h0
  	-rm -f g77.aux g77.cps g77.ky g77.toc g77.vr g77.fn g77.kys \
  	       g77.pg g77.tp g77.vrs g77.cp g77.fns g77.log g77.pgs g77.tps 
  f77.clean:
! 	-rm -f g77spec.o g77version.o
  f77.distclean:
  	-rm -f f/Makefile
  f77.extraclean:
--- 313,325 ----
  
  f77.mostlyclean:
  	-rm -f f/*$(objext)
+ 	-rm -f f/*$(coverageexts)
  	-rm -f f/fini$(build_exeext) f/stamp-str f/str-*.h f/str-*.j
  	-rm -f f/intdoc$(build_exeext) f/ansify$(build_exeext) f/intdoc.h0
  	-rm -f g77.aux g77.cps g77.ky g77.toc g77.vr g77.fn g77.kys \
  	       g77.pg g77.tp g77.vrs g77.cp g77.fns g77.log g77.pgs g77.tps 
  f77.clean:
! 	-rm -f g77spec.o
  f77.distclean:
  	-rm -f f/Makefile
  f77.extraclean:
*************** f77.maintainer-clean:
*** 329,335 ****
  # The main makefile has already created stage?/f.
  
  G77STAGESTUFF = f/*$(objext) f/fini$(build_exeext) f/stamp-str \
!   f/str-*.h f/str-*.j g77spec.o g77version.o
  
  f77.stage1: stage1-start
  	-mv -f $(G77STAGESTUFF) stage1/f
--- 330,336 ----
  # The main makefile has already created stage?/f.
  
  G77STAGESTUFF = f/*$(objext) f/fini$(build_exeext) f/stamp-str \
!   f/str-*.h f/str-*.j g77spec.o
  
  f77.stage1: stage1-start
  	-mv -f $(G77STAGESTUFF) stage1/f
*************** f/bad.o: f/bad.c f/proj.h $(CONFIG_H) $(
*** 350,370 ****
   glimits.h f/top.h f/malloc.h flags.h f/com.h f/com-rt.def $(TREE_H) f/bld.h \
   f/bld-op.def f/bit.h f/info.h f/info-b.def f/info-k.def f/info-w.def \
   f/target.h f/lex.h f/type.h f/intrin.h f/intrin.def f/lab.h f/symbol.h \
!  f/symbol.def f/equiv.h f/storag.h f/global.h f/name.h toplev.h intl.h
  f/bit.o: f/bit.c f/proj.h $(CONFIG_H) $(SYSTEM_H) glimits.h f/bit.h \
   f/malloc.h
  f/bld.o: f/bld.c f/proj.h $(CONFIG_H) $(SYSTEM_H) f/bld.h f/bld-op.def f/bit.h \
   f/malloc.h f/com.h f/com-rt.def $(TREE_H) f/info.h f/info-b.def f/info-k.def \
   f/info-w.def f/target.h f/bad.h f/bad.def f/where.h glimits.h f/top.h f/lex.h \
   f/type.h f/lab.h f/storag.h f/symbol.h f/symbol.def f/equiv.h f/global.h \
!  f/name.h f/intrin.h f/intrin.def
  f/com.o: f/com.c f/proj.h $(CONFIG_H) $(SYSTEM_H) flags.h $(RTL_H) $(TREE_H) \
   output.h convert.h f/com.h f/com-rt.def f/bld.h f/bld-op.def f/bit.h \
   f/malloc.h f/info.h f/info-b.def f/info-k.def f/info-w.def f/target.h f/bad.h \
   f/bad.def f/where.h glimits.h f/top.h f/lex.h f/type.h f/intrin.h \
   f/intrin.def f/lab.h f/symbol.h f/symbol.def f/equiv.h f/storag.h f/global.h \
   f/name.h f/expr.h f/implic.h f/src.h f/st.h $(GGC_H) toplev.h diagnostic.h \
!  langhooks.h langhooks-def.h intl.h
  f/data.o: f/data.c f/proj.h $(CONFIG_H) $(SYSTEM_H) f/data.h f/bld.h f/bld-op.def \
   f/bit.h f/malloc.h f/com.h f/com-rt.def $(TREE_H) f/info.h f/info-b.def \
   f/info-k.def f/info-w.def f/target.h f/bad.h f/bad.def f/where.h glimits.h \
--- 351,372 ----
   glimits.h f/top.h f/malloc.h flags.h f/com.h f/com-rt.def $(TREE_H) f/bld.h \
   f/bld-op.def f/bit.h f/info.h f/info-b.def f/info-k.def f/info-w.def \
   f/target.h f/lex.h f/type.h f/intrin.h f/intrin.def f/lab.h f/symbol.h \
!  f/symbol.def f/equiv.h f/storag.h f/global.h f/name.h toplev.h intl.h \
!  diagnostic.h
  f/bit.o: f/bit.c f/proj.h $(CONFIG_H) $(SYSTEM_H) glimits.h f/bit.h \
   f/malloc.h
  f/bld.o: f/bld.c f/proj.h $(CONFIG_H) $(SYSTEM_H) f/bld.h f/bld-op.def f/bit.h \
   f/malloc.h f/com.h f/com-rt.def $(TREE_H) f/info.h f/info-b.def f/info-k.def \
   f/info-w.def f/target.h f/bad.h f/bad.def f/where.h glimits.h f/top.h f/lex.h \
   f/type.h f/lab.h f/storag.h f/symbol.h f/symbol.def f/equiv.h f/global.h \
!  f/name.h f/intrin.h f/intrin.def real.h
  f/com.o: f/com.c f/proj.h $(CONFIG_H) $(SYSTEM_H) flags.h $(RTL_H) $(TREE_H) \
   output.h convert.h f/com.h f/com-rt.def f/bld.h f/bld-op.def f/bit.h \
   f/malloc.h f/info.h f/info-b.def f/info-k.def f/info-w.def f/target.h f/bad.h \
   f/bad.def f/where.h glimits.h f/top.h f/lex.h f/type.h f/intrin.h \
   f/intrin.def f/lab.h f/symbol.h f/symbol.def f/equiv.h f/storag.h f/global.h \
   f/name.h f/expr.h f/implic.h f/src.h f/st.h $(GGC_H) toplev.h diagnostic.h \
!  $(LANGHOOKS_DEF) langhooks.h intl.h real.h debug.h gt-f-com.h gtype-f.h
  f/data.o: f/data.c f/proj.h $(CONFIG_H) $(SYSTEM_H) f/data.h f/bld.h f/bld-op.def \
   f/bit.h f/malloc.h f/com.h f/com-rt.def $(TREE_H) f/info.h f/info-b.def \
   f/info-k.def f/info-w.def f/target.h f/bad.h f/bad.def f/where.h glimits.h \
*************** f/expr.o: f/expr.c f/proj.h $(CONFIG_H) 
*** 380,386 ****
   f/info-k.def f/info-w.def f/target.h f/bad.h f/bad.def f/where.h glimits.h \
   f/top.h f/lex.h f/type.h f/lab.h f/storag.h f/symbol.h f/symbol.def f/equiv.h \
   f/global.h f/name.h f/intrin.h f/intrin.def f/implic.h f/src.h f/st.h \
!  f/stamp-str
  f/fini.o: f/fini.c f/proj.h hconfig.h $(SYSTEM_H) f/malloc.h
  f/global.o: f/global.c f/proj.h $(CONFIG_H) $(SYSTEM_H) f/global.h f/info.h \
   f/info-b.def f/info-k.def f/info-w.def f/target.h $(TREE_H) f/bad.h f/bad.def \
--- 382,388 ----
   f/info-k.def f/info-w.def f/target.h f/bad.h f/bad.def f/where.h glimits.h \
   f/top.h f/lex.h f/type.h f/lab.h f/storag.h f/symbol.h f/symbol.def f/equiv.h \
   f/global.h f/name.h f/intrin.h f/intrin.def f/implic.h f/src.h f/st.h \
!  f/stamp-str real.h
  f/fini.o: f/fini.c f/proj.h hconfig.h $(SYSTEM_H) f/malloc.h
  f/global.o: f/global.c f/proj.h $(CONFIG_H) $(SYSTEM_H) f/global.h f/info.h \
   f/info-b.def f/info-k.def f/info-w.def f/target.h $(TREE_H) f/bad.h f/bad.def \
*************** f/lex.o: f/lex.c f/proj.h $(CONFIG_H) $(
*** 410,416 ****
   f/bld-op.def f/bit.h f/info.h f/info-b.def f/info-k.def f/info-w.def \
   f/target.h f/lex.h f/type.h f/intrin.h f/intrin.def f/lab.h f/symbol.h \
   f/symbol.def f/equiv.h f/storag.h f/global.h f/name.h f/src.h flags.h \
!  debug.h input.h toplev.h output.h $(GGC_H)
  f/malloc.o: f/malloc.c f/proj.h $(CONFIG_H) $(SYSTEM_H) f/malloc.h
  f/name.o: f/name.c f/proj.h $(CONFIG_H) $(SYSTEM_H) f/bad.h f/bad.def f/where.h \
   glimits.h f/top.h f/malloc.h f/name.h f/global.h f/info.h f/info-b.def \
--- 412,418 ----
   f/bld-op.def f/bit.h f/info.h f/info-b.def f/info-k.def f/info-w.def \
   f/target.h f/lex.h f/type.h f/intrin.h f/intrin.def f/lab.h f/symbol.h \
   f/symbol.def f/equiv.h f/storag.h f/global.h f/name.h f/src.h flags.h \
!  debug.h input.h toplev.h output.h $(GGC_H) gt-f-lex.h
  f/malloc.o: f/malloc.c f/proj.h $(CONFIG_H) $(SYSTEM_H) f/malloc.h
  f/name.o: f/name.c f/proj.h $(CONFIG_H) $(SYSTEM_H) f/bad.h f/bad.def f/where.h \
   glimits.h f/top.h f/malloc.h f/name.h f/global.h f/info.h f/info-b.def \
*************** f/parse.o: f/parse.c f/proj.h $(CONFIG_H
*** 421,427 ****
   f/where.h glimits.h f/com.h f/com-rt.def $(TREE_H) f/bld.h f/bld-op.def \
   f/bit.h f/info.h f/info-b.def f/info-k.def f/info-w.def f/target.h f/bad.h \
   f/bad.def f/lex.h f/type.h f/intrin.h f/intrin.def f/lab.h f/symbol.h \
!  f/symbol.def f/equiv.h f/storag.h f/global.h f/name.h f/version.h flags.h
  f/src.o: f/src.c f/proj.h $(CONFIG_H) $(SYSTEM_H) f/src.h f/bad.h f/bad.def \
   f/where.h glimits.h f/top.h f/malloc.h
  f/st.o: f/st.c f/proj.h $(CONFIG_H) $(SYSTEM_H) f/st.h f/bad.h f/bad.def \
--- 423,429 ----
   f/where.h glimits.h f/com.h f/com-rt.def $(TREE_H) f/bld.h f/bld-op.def \
   f/bit.h f/info.h f/info-b.def f/info-k.def f/info-w.def f/target.h f/bad.h \
   f/bad.def f/lex.h f/type.h f/intrin.h f/intrin.def f/lab.h f/symbol.h \
!  f/symbol.def f/equiv.h f/storag.h f/global.h f/name.h version.h flags.h
  f/src.o: f/src.c f/proj.h $(CONFIG_H) $(SYSTEM_H) f/src.h f/bad.h f/bad.def \
   f/where.h glimits.h f/top.h f/malloc.h
  f/st.o: f/st.c f/proj.h $(CONFIG_H) $(SYSTEM_H) f/st.h f/bad.h f/bad.def \
*************** f/ste.o: f/ste.c f/proj.h $(CONFIG_H) $(
*** 460,466 ****
   f/info.h f/info-b.def f/info-k.def f/info-w.def f/target.h f/bad.h f/bad.def \
   f/where.h glimits.h f/top.h f/lex.h f/type.h f/lab.h f/storag.h f/symbol.h \
   f/symbol.def f/equiv.h f/global.h f/name.h f/intrin.h f/intrin.def f/stp.h \
!  f/stt.h f/stamp-str f/sts.h f/stv.h f/stw.h f/expr.h f/sta.h $(GGC_H)
  f/storag.o: f/storag.c f/proj.h $(CONFIG_H) $(SYSTEM_H) f/storag.h f/bld.h  \
   f/bld-op.def f/bit.h f/malloc.h f/com.h f/com-rt.def $(TREE_H) \
   f/info.h f/info-b.def f/info-k.def f/info-w.def f/target.h f/bad.h \
--- 462,469 ----
   f/info.h f/info-b.def f/info-k.def f/info-w.def f/target.h f/bad.h f/bad.def \
   f/where.h glimits.h f/top.h f/lex.h f/type.h f/lab.h f/storag.h f/symbol.h \
   f/symbol.def f/equiv.h f/global.h f/name.h f/intrin.h f/intrin.def f/stp.h \
!  f/stt.h f/stamp-str f/sts.h f/stv.h f/stw.h f/expr.h f/sta.h $(GGC_H) \
!  gt-f-ste.h
  f/storag.o: f/storag.c f/proj.h $(CONFIG_H) $(SYSTEM_H) f/storag.h f/bld.h  \
   f/bld-op.def f/bit.h f/malloc.h f/com.h f/com-rt.def $(TREE_H) \
   f/info.h f/info-b.def f/info-k.def f/info-w.def f/target.h f/bad.h \
*************** f/symbol.o: f/symbol.c f/proj.h $(CONFIG
*** 512,518 ****
   f/lex.h f/type.h f/lab.h f/storag.h f/intrin.h f/intrin.def f/equiv.h \
   f/global.h f/name.h f/src.h f/st.h
  f/target.o: f/target.c f/proj.h $(CONFIG_H) $(SYSTEM_H) glimits.h f/target.h \
!  $(TREE_H) f/bad.h f/bad.def f/where.h f/top.h f/malloc.h f/info.h \
   f/info-b.def f/info-k.def f/info-w.def f/type.h f/lex.h diagnostic.h
  f/top.o: f/top.c f/proj.h $(CONFIG_H) $(SYSTEM_H) f/top.h f/malloc.h f/where.h \
   glimits.h f/bad.h f/bad.def f/bit.h f/bld.h f/bld-op.def f/com.h \
--- 515,521 ----
   f/lex.h f/type.h f/lab.h f/storag.h f/intrin.h f/intrin.def f/equiv.h \
   f/global.h f/name.h f/src.h f/st.h
  f/target.o: f/target.c f/proj.h $(CONFIG_H) $(SYSTEM_H) glimits.h f/target.h \
!  $(TREE_H) f/bad.h f/bad.def f/where.h f/top.h f/malloc.h f/info.h real.h \
   f/info-b.def f/info-k.def f/info-w.def f/type.h f/lex.h diagnostic.h
  f/top.o: f/top.c f/proj.h $(CONFIG_H) $(SYSTEM_H) f/top.h f/malloc.h f/where.h \
   glimits.h f/bad.h f/bad.def f/bit.h f/bld.h f/bld-op.def f/com.h \
*************** f/top.o: f/top.c f/proj.h $(CONFIG_H) $(
*** 522,527 ****
   f/intrin.def f/data.h f/expr.h f/implic.h f/src.h f/st.h flags.h \
   toplev.h
  f/type.o: f/type.c f/proj.h $(CONFIG_H) $(SYSTEM_H) f/type.h f/malloc.h
- f/version.o: f/version.c f/version.h
  f/where.o: f/where.c f/proj.h $(CONFIG_H) $(SYSTEM_H) f/where.h glimits.h f/top.h \
!  f/malloc.h f/lex.h $(GGC_H)
--- 525,529 ----
   f/intrin.def f/data.h f/expr.h f/implic.h f/src.h f/st.h flags.h \
   toplev.h
  f/type.o: f/type.c f/proj.h $(CONFIG_H) $(SYSTEM_H) f/type.h f/malloc.h
  f/where.o: f/where.c f/proj.h $(CONFIG_H) $(SYSTEM_H) f/where.h glimits.h f/top.h \
!  f/malloc.h f/lex.h $(GGC_H) gt-f-where.h
diff -Nrc3pad gcc-3.2.3/gcc/f/NEWS gcc-3.3/gcc/f/NEWS
*** gcc-3.2.3/gcc/f/NEWS	2003-04-22 09:53:56.000000000 +0000
--- gcc-3.3/gcc/f/NEWS	2003-05-14 02:47:28.000000000 +0000
*************** _Note:_ This file is automatically gener
*** 2,12 ****
  `news0.texi' and `news.texi'.  `NEWS' is _not_ a source file, although
  it is normally included within source distributions.
  
!    This file lists news about the GCC-3.2.3 version (and some other
  versions) of the GNU Fortran compiler.  Copyright (C)
! 1995,1996,1997,1998,1999,2000,2001,2002 Free Software Foundation, Inc.
! You may copy, distribute, and modify it freely as long as you preserve
! this copyright notice and permission notice.
  
  News About GNU Fortran
  **********************
--- 2,12 ----
  `news0.texi' and `news.texi'.  `NEWS' is _not_ a source file, although
  it is normally included within source distributions.
  
!    This file lists news about the GCC-3.3 version (and some other
  versions) of the GNU Fortran compiler.  Copyright (C)
! 1995,1996,1997,1998,1999,2000,2001,2002,2003 Free Software Foundation,
! Inc.  You may copy, distribute, and modify it freely as long as you
! preserve this copyright notice and permission notice.
  
  News About GNU Fortran
  **********************
*************** somewhat more difficult.
*** 47,64 ****
  
     An online, "live" version of this document (derived directly from
  the mainline, development version of `g77' within `gcc') is available at
! `http://www.gnu.org/software/gcc/onlinedocs/g77/News.html'.
  
!    The following information was last updated on 2002-10-28:
  
  In `GCC' 3.2 versus `GCC' 3.1:
  ==============================
  
     * Problem Reports fixed (in chronological order of submission):
      `8308'
            gcc-3.x does not compile files with suffix .r (RATFOR) [Fixed
            in 3.2.1]
  
  In `GCC' 3.1 (formerly known as g77-0.5.27) versus `GCC' 3.0:
  =============================================================
  
--- 47,132 ----
  
     An online, "live" version of this document (derived directly from
  the mainline, development version of `g77' within `gcc') is available at
! `http://gcc.gnu.org/onlinedocs/g77/News.html'.
  
!    The following information was last updated on 2003-04-11:
! 
! In `GCC' 3.3 versus `GCC' 3.2:
! ==============================
! 
!    * Problem Reports fixed (in chronological order of submission):
!     `1832'
!           -list directed i/o overflow hangs, -fbounds-check doesn't
!           detect
! 
!     `3924'
!           g77 generates code which is rejected by GAS if COFF debugging
!           info is requested
! 
!     `6286'
!           Broken links on web pages
! 
!     `6367'
!           (libf2c) multiple repeat counts confuse namelist read into
!           array
! 
!     `6491'
!           Logical operations error on logicals when using -fugly-logint
! 
!     `6742'
!           Generation of C++ Prototype for FORTRAN and extern "C"
! 
!     `7113'
!           Failure of g77.f-torture/execute/f90-intrinsic-bit.f -Os on
!           irix6.5
! 
!     `7236'
!           (libf2c) OPEN(...,RECL=nnn,...) without ACCESS='DIRECT'
!           should assume a direct access file
! 
!     `7278'
!           g77 "bug"; the executable misbehave (use of options -O2
!           -fno-automatic gave wrong results)
! 
!     `7384'
!           (libf2c) DATE_AND_TIME milliseconds field inactive on Windows
! 
!     `7388'
!           Incorrect output with 0-based array of characters
! 
!     `8587'
!           Double complex zero ** double precision number -> NaN instead
!           of zero
! 
!     `9038'
!           -ffixed-line-length-none -x f77-cpp-input gives: Warning:
!           unknown register name line-length-none
! 
!     `9263'
!           ICE caused by invalid PARAMETER in implied DO loop
! 
!     `10197'
!           Direct access files not unformatted by default
! 
!    * Richard Henderson (<rth@redhat.com>) analyzed and improved the
!      handling of (no-)aliasing information for dummy arguments and
!      improved the optimization of induction variables in unrolled loops.
  
  In `GCC' 3.2 versus `GCC' 3.1:
  ==============================
  
     * Problem Reports fixed (in chronological order of submission):
+     `7681'
+           ICE in compensate_edge, at reg-stack.c:2591
+ 
      `8308'
            gcc-3.x does not compile files with suffix .r (RATFOR) [Fixed
            in 3.2.1]
  
+     `9258'
+           [3.2/3.3/3.4 regression] ICE in compensate_edge, at
+           reg-stack.c:2589
+ 
  In `GCC' 3.1 (formerly known as g77-0.5.27) versus `GCC' 3.0:
  =============================================================
  
*************** In `GCC' 3.1 (formerly known as g77-0.5.
*** 100,105 ****
--- 168,183 ----
      `5837'
            bug in loop unrolling
  
+     `6106'
+           sparc-sun-solaris2.7 gcc-3.1 extra g77 testsuite failures
+           w/-m64
+ 
+     `6138'
+           Incorrect acces of integer*1 variables on PA
+ 
+     `6304'
+           Failure of LAPACK test dtest on irix6.5 with -mabi=64 -O2
+ 
     * `g77' now has its man page generated from the texinfo
       documentation, to guarantee that it remains up to date.
  
*************** In `GCC' 3.1 (formerly known as g77-0.5.
*** 118,125 ****
       role after offsets have been converted to byte addresses.
       Therefore this check has been removed, and the limit is now 2
       Gbyte of memory (around 530 000 000 REALs).  Note: On GNU/Linux
!      systems one has to compile programs that occupy more than 1 Gbyte
!      statically, i.e. `g77 -static ...'.
  
     * Based on work done by Juergen Pfeifer (<juergen.pfeifer@gmx.net>)
       libf2c is now a shared library.  One can still link in all objects
--- 196,203 ----
       role after offsets have been converted to byte addresses.
       Therefore this check has been removed, and the limit is now 2
       Gbyte of memory (around 530 000 000 REALs).  Note: On GNU/Linux
!      systems one has to compile and link programs that occupy more than
!      1 Gbyte statically, i.e. `g77 -static ...'.
  
     * Based on work done by Juergen Pfeifer (<juergen.pfeifer@gmx.net>)
       libf2c is now a shared library.  One can still link in all objects
diff -Nrc3pad gcc-3.2.3/gcc/f/news.texi gcc-3.3/gcc/f/news.texi
*** gcc-3.2.3/gcc/f/news.texi	2002-10-28 21:53:38.000000000 +0000
--- gcc-3.3/gcc/f/news.texi	2003-04-11 19:29:11.000000000 +0000
***************
*** 1,4 ****
! @c Copyright (C) 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002
  @c  Free Software Foundation, Inc.
  @c This is part of the G77 manual.
  @c For copying conditions, see the file g77.texi.
--- 1,4 ----
! @c Copyright (C) 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003
  @c  Free Software Foundation, Inc.
  @c This is part of the G77 manual.
  @c For copying conditions, see the file g77.texi.
***************
*** 8,20 ****
  
  @c Keep this the same as the dates above, since it's used
  @c in the standalone derivations of this file (e.g. NEWS).
! @set copyrights-news 1995,1996,1997,1998,1999,2000,2001,2002
! 
! @set last-update-news 2002-10-28
  
! @include root.texi
  
  @ifset DOC-NEWS
  @c The immediately following lines apply to the NEWS file
  @c which is derived from this file.
  @emph{Note:} This file is automatically generated from the files
--- 8,19 ----
  
  @c Keep this the same as the dates above, since it's used
  @c in the standalone derivations of this file (e.g. NEWS).
! @set copyrights-news 1995,1996,1997,1998,1999,2000,2001,2002,2003
  
! @set last-update-news 2003-04-11
  
  @ifset DOC-NEWS
+ @include root.texi
  @c The immediately following lines apply to the NEWS file
  @c which is derived from this file.
  @emph{Note:} This file is automatically generated from the files
*************** An online, ``live'' version of this docu
*** 148,165 ****
  (derived directly from the mainline, development version
  of @command{g77} within @command{gcc})
  is available at
! @uref{http://www.gnu.org/software/gcc/onlinedocs/g77/News.html}.
  @end ifclear
  
  The following information was last updated on @value{last-update-news}:
  
  @heading In @code{GCC} 3.2 versus @code{GCC} 3.1:
  @itemize @bullet
  @item
  Problem Reports fixed (in chronological order of submission):
  @table @code
  @item 8308
  gcc-3.x does not compile files with suffix .r (RATFOR) [Fixed in 3.2.1]
  @end table
  @end itemize
  
--- 147,213 ----
  (derived directly from the mainline, development version
  of @command{g77} within @command{gcc})
  is available at
! @uref{http://gcc.gnu.org/onlinedocs/g77/News.html}.
  @end ifclear
  
  The following information was last updated on @value{last-update-news}:
  
+ @heading In @code{GCC} 3.3 versus @code{GCC} 3.2:
+ @itemize @bullet
+ @item
+ Problem Reports fixed (in chronological order of submission):
+ @table @code
+ @item 1832
+ -list directed i/o overflow hangs, -fbounds-check doesn't detect
+ @item 3924
+ g77 generates code which is rejected by GAS if COFF debugging info is
+ requested
+ @item 6286
+ Broken links on web pages
+ @item 6367
+ (libf2c) multiple repeat counts confuse namelist read into array
+ @item 6491
+ Logical operations error on logicals when using -fugly-logint
+ @item 6742
+ Generation of C++ Prototype for FORTRAN and extern "C"
+ @item 7113
+ Failure of g77.f-torture/execute/f90-intrinsic-bit.f -Os on irix6.5
+ @item 7236
+ (libf2c) OPEN(...,RECL=nnn,...) without ACCESS='DIRECT' should assume a direct
+ access file
+ @item 7278
+ g77 "bug"; the executable misbehave (use of options -O2 -fno-automatic
+ gave wrong results)
+ @item 7384
+ (libf2c) DATE_AND_TIME milliseconds field inactive on Windows
+ @item 7388
+ Incorrect output with 0-based array of characters
+ @item 8587
+ Double complex zero ** double precision number -> NaN instead of zero
+ @item 9038
+ -ffixed-line-length-none -x f77-cpp-input gives: Warning: unknown register name line-length-none
+ @item 9263
+ ICE caused by invalid PARAMETER in implied DO loop
+ @item 10197
+ Direct access files not unformatted by default
+ @end table
+ @item
+ Richard Henderson (@email{rth@@redhat.com}) analyzed and improved the handling
+ of (no-)aliasing information for dummy arguments and improved the optimization
+ of induction variables in unrolled loops.
+ @end itemize
+ 
  @heading In @code{GCC} 3.2 versus @code{GCC} 3.1:
  @itemize @bullet
  @item
  Problem Reports fixed (in chronological order of submission):
  @table @code
+ @item 7681
+ ICE in compensate_edge, at reg-stack.c:2591
  @item 8308
  gcc-3.x does not compile files with suffix .r (RATFOR) [Fixed in 3.2.1]
+ @item 9258
+ [3.2/3.3/3.4 regression] ICE in compensate_edge, at reg-stack.c:2589
  @end table
  @end itemize
  
*************** ICE on compiling source with 540 000 000
*** 192,197 ****
--- 240,251 ----
  ICE on BESJN(integer*8,real)
  @item 5837
  bug in loop unrolling
+ @item 6106
+ sparc-sun-solaris2.7 gcc-3.1 extra g77 testsuite failures w/-m64
+ @item 6138
+ Incorrect acces of integer*1 variables on PA
+ @item 6304
+ Failure of LAPACK test dtest on irix6.5 with -mabi=64 -O2
  @end table
  
  @item
*************** because 140 000 000 REALs is larger than
*** 217,224 ****
  expressed in 32 bits.  However, bit-sizes never play a role after offsets
  have been converted to byte addresses.  Therefore this check has been removed,
  and the limit is now 2 Gbyte of memory (around 530 000 000 REALs).
! Note: On GNU/Linux systems one has to compile programs that occupy more
! than 1 Gbyte statically, i.e.@: @code{g77 -static ...}.
  
  @item
  Based on work done by Juergen Pfeifer (@email{juergen.pfeifer@@gmx.net})
--- 271,278 ----
  expressed in 32 bits.  However, bit-sizes never play a role after offsets
  have been converted to byte addresses.  Therefore this check has been removed,
  and the limit is now 2 Gbyte of memory (around 530 000 000 REALs).
! Note: On GNU/Linux systems one has to compile and link programs that occupy
! more than 1 Gbyte statically, i.e.@: @code{g77 -static ...}.
  
  @item
  Based on work done by Juergen Pfeifer (@email{juergen.pfeifer@@gmx.net})
*************** fix up some of the build procedures.
*** 2311,2317 ****
  
  @item
  Change code generation for list-directed I/O so it allows
! for new versions of @code{libf2c} that might return non-zero
  status codes for some operations previously assumed to always
  return zero.
  
--- 2365,2371 ----
  
  @item
  Change code generation for list-directed I/O so it allows
! for new versions of @code{libf2c} that might return nonzero
  status codes for some operations previously assumed to always
  return zero.
  
diff -Nrc3pad gcc-3.2.3/gcc/f/parse.c gcc-3.3/gcc/f/parse.c
*** gcc-3.2.3/gcc/f/parse.c	2001-10-17 22:34:52.000000000 +0000
--- gcc-3.3/gcc/f/parse.c	2002-09-24 03:44:33.000000000 +0000
*************** the Free Software Foundation, 59 Temple 
*** 26,42 ****
  #include "version.h"
  #include "flags.h"
  
- #define NAME_OF_STDIN "<stdin>"
- 
  extern FILE *finput;
  
! int
! yyparse ()
  {
    ffewhereFile wf;
  
    if (ffe_is_version ())
!     fprintf (stderr, "GNU Fortran Front End version %s\n", ffe_version_string);
  
    if (!ffe_is_pedantic ())
      ffe_set_is_pedantic (pedantic);
--- 26,41 ----
  #include "version.h"
  #include "flags.h"
  
  extern FILE *finput;
  
! void
! ffe_parse_file (set_yydebug)
!      int set_yydebug ATTRIBUTE_UNUSED;
  {
    ffewhereFile wf;
  
    if (ffe_is_version ())
!     fprintf (stderr, "GNU Fortran Front End version %s\n", version_string);
  
    if (!ffe_is_pedantic ())
      ffe_set_is_pedantic (pedantic);
*************** yyparse ()
*** 46,51 ****
    ffe_file (wf, finput);
  
    ffecom_finish_compile ();
- 
-   return 0;
  }
--- 45,48 ----
diff -Nrc3pad gcc-3.2.3/gcc/f/root.texi gcc-3.3/gcc/f/root.texi
*** gcc-3.2.3/gcc/f/root.texi	2003-02-05 05:09:14.000000000 +0000
--- gcc-3.3/gcc/f/root.texi	2002-12-23 19:38:43.000000000 +0000
***************
*** 1,9 ****
! @c DEVELOPMENT is set to indicate an in-development version,
! @c as compared to a release version.  When making a release
! @c (e.g. a release branch in the CVS repository for gcc),
! @c clear this and set the version information correctly.
! @clear DEVELOPMENT
! @set version-gcc 3.2.3
  
  @set email-general gcc@@gcc.gnu.org
  @set email-help gcc-help@@gcc.gnu.org
--- 1,4 ----
! @include gcc-common.texi
  
  @set email-general gcc@@gcc.gnu.org
  @set email-help gcc-help@@gcc.gnu.org
***************
*** 12,18 ****
  @set path-g77 gcc/gcc/f
  @set path-libf2c gcc/libf2c
  
! @set which-g77 GCC-@value{version-gcc}
  @set which-gcc GCC
  
  @set email-burley craig@@jcb-sc.com
--- 7,13 ----
  @set path-g77 gcc/gcc/f
  @set path-libf2c gcc/libf2c
  
! @set which-g77 GCC-@value{version-GCC}
  @set which-gcc GCC
  
  @set email-burley craig@@jcb-sc.com
diff -Nrc3pad gcc-3.2.3/gcc/f/stc.c gcc-3.3/gcc/f/stc.c
*** gcc-3.2.3/gcc/f/stc.c	2001-09-13 14:37:23.000000000 +0000
--- gcc-3.3/gcc/f/stc.c	2003-03-22 15:24:51.000000000 +0000
***************
*** 1,5 ****
  /* stc.c -- Implementation File (module.c template V1.0)
!    Copyright (C) 1995, 1996, 1997 Free Software Foundation, Inc.
     Contributed by James Craig Burley.
  
  This file is part of GNU Fortran.
--- 1,5 ----
  /* stc.c -- Implementation File (module.c template V1.0)
!    Copyright (C) 1995, 1996, 1997, 2003 Free Software Foundation, Inc.
     Contributed by James Craig Burley.
  
  This file is part of GNU Fortran.
*************** ffestc_R810 (ffesttCaseList cases, ffele
*** 9195,9212 ****
  	      ffebad_finish ();
  	      continue;
  	    }
- 
  	  if (((caseobj->expr1 != NULL)
  	       && ((ffeinfo_basictype (ffebld_info (caseobj->expr1))
  		    != s->type)
! 		   || (ffeinfo_kindtype (ffebld_info (caseobj->expr1))
! 		       != s->kindtype)))
  	      || ((caseobj->range)
  		  && (caseobj->expr2 != NULL)
  		  && ((ffeinfo_basictype (ffebld_info (caseobj->expr2))
  		       != s->type)
! 		      || (ffeinfo_kindtype (ffebld_info (caseobj->expr2))
! 			  != s->kindtype))))
  	    {
  	      ffebad_start (FFEBAD_CASE_TYPE_DISAGREE);
  	      ffebad_here (0, ffelex_token_where_line (caseobj->t),
--- 9195,9213 ----
  	      ffebad_finish ();
  	      continue;
  	    }
  	  if (((caseobj->expr1 != NULL)
  	       && ((ffeinfo_basictype (ffebld_info (caseobj->expr1))
  		    != s->type)
! 		   || ((ffeinfo_kindtype (ffebld_info (caseobj->expr1))
! 		       != s->kindtype) 
! 		       && (ffeinfo_kindtype (ffebld_info (caseobj->expr1)) != FFEINFO_kindtypeINTEGER1 ))
  	      || ((caseobj->range)
  		  && (caseobj->expr2 != NULL)
  		  && ((ffeinfo_basictype (ffebld_info (caseobj->expr2))
  		       != s->type)
! 		      || ((ffeinfo_kindtype (ffebld_info (caseobj->expr2))
! 			  != s->kindtype)
! 		      && (ffeinfo_kindtype (ffebld_info (caseobj->expr2)) != FFEINFO_kindtypeINTEGER1)))))))
  	    {
  	      ffebad_start (FFEBAD_CASE_TYPE_DISAGREE);
  	      ffebad_here (0, ffelex_token_where_line (caseobj->t),
*************** ffestc_R810 (ffesttCaseList cases, ffele
*** 9217,9222 ****
--- 9218,9225 ----
  	      continue;
  	    }
  
+ 
+ 
  	  if ((s->type == FFEINFO_basictypeLOGICAL) && (caseobj->range))
  	    {
  	      ffebad_start (FFEBAD_CASE_LOGICAL_RANGE);
diff -Nrc3pad gcc-3.2.3/gcc/f/std.c gcc-3.3/gcc/f/std.c
*** gcc-3.2.3/gcc/f/std.c	2001-10-18 03:57:51.000000000 +0000
--- gcc-3.3/gcc/f/std.c	2002-08-22 02:20:42.000000000 +0000
***************
*** 1,5 ****
  /* std.c -- Implementation File (module.c template V1.0)
!    Copyright (C) 1995, 1996, 2000 Free Software Foundation, Inc.
     Contributed by James Craig Burley.
  
  This file is part of GNU Fortran.
--- 1,5 ----
  /* std.c -- Implementation File (module.c template V1.0)
!    Copyright (C) 1995, 1996, 2000, 2002 Free Software Foundation, Inc.
     Contributed by James Craig Burley.
  
  This file is part of GNU Fortran.
*************** ffestd_S3P4 (ffebld filename)
*** 4774,4782 ****
        fi = ffecom_open_include (ffewhere_file_name (wf),
  				ffelex_token_where_line (ffesta_tokens[0]),
  				ffelex_token_where_column (ffesta_tokens[0]));
!       if (fi == NULL)
! 	ffewhere_file_kill (wf);
!       else
  	ffelex_set_include (wf, (ffelex_token_type (ffesta_tokens[0])
  				 == FFELEX_typeNAME), fi);
      }
--- 4774,4780 ----
        fi = ffecom_open_include (ffewhere_file_name (wf),
  				ffelex_token_where_line (ffesta_tokens[0]),
  				ffelex_token_where_column (ffesta_tokens[0]));
!       if (fi != NULL)
  	ffelex_set_include (wf, (ffelex_token_type (ffesta_tokens[0])
  				 == FFELEX_typeNAME), fi);
      }
diff -Nrc3pad gcc-3.2.3/gcc/f/ste.c gcc-3.3/gcc/f/ste.c
*** gcc-3.2.3/gcc/f/ste.c	2002-02-04 16:07:59.000000000 +0000
--- gcc-3.3/gcc/f/ste.c	2003-03-22 15:24:52.000000000 +0000
***************
*** 1,5 ****
  /* ste.c -- Implementation File (module.c template V1.0)
!    Copyright (C) 1995, 1996, 2000, 2002 Free Software Foundation, Inc.
     Contributed by James Craig Burley.
  
  This file is part of GNU Fortran.
--- 1,5 ----
  /* ste.c -- Implementation File (module.c template V1.0)
!    Copyright (C) 1995, 1996, 2000, 2002, 2003 Free Software Foundation, Inc.
     Contributed by James Craig Burley.
  
  This file is part of GNU Fortran.
*************** ffeste_io_douio_ (ffebld expr)
*** 1162,1174 ****
     declaration of variables (temporaries) to the expanding of expressions,
     statements, etc.  */
  
  static tree
  ffeste_io_ialist_ (bool have_err,
  		   ffestvUnit unit,
  		   ffebld unit_expr,
  		   int unit_dflt)
  {
-   static tree f2c_alist_struct = NULL_TREE;
    tree t;
    tree ttype;
    tree field;
--- 1162,1174 ----
     declaration of variables (temporaries) to the expanding of expressions,
     statements, etc.  */
  
+ static GTY(()) tree f2c_alist_struct;
  static tree
  ffeste_io_ialist_ (bool have_err,
  		   ffestvUnit unit,
  		   ffebld unit_expr,
  		   int unit_dflt)
  {
    tree t;
    tree ttype;
    tree field;
*************** ffeste_io_ialist_ (bool have_err,
*** 1193,1200 ****
        TYPE_FIELDS (ref) = errfield;
        layout_type (ref);
  
-       ggc_add_tree_root (&f2c_alist_struct, 1);
- 
        f2c_alist_struct = ref;
      }
  
--- 1193,1198 ----
*************** ffeste_io_ialist_ (bool have_err,
*** 1283,1288 ****
--- 1281,1287 ----
     declaration of variables (temporaries) to the expanding of expressions,
     statements, etc.  */
  
+ static GTY(()) tree f2c_cilist_struct;
  static tree
  ffeste_io_cilist_ (bool have_err,
  		   ffestvUnit unit,
*************** ffeste_io_cilist_ (bool have_err,
*** 1294,1300 ****
  		   bool rec,
  		   ffebld rec_expr)
  {
-   static tree f2c_cilist_struct = NULL_TREE;
    tree t;
    tree ttype;
    tree field;
--- 1293,1298 ----
*************** ffeste_io_cilist_ (bool have_err,
*** 1325,1332 ****
        TYPE_FIELDS (ref) = errfield;
        layout_type (ref);
  
-       ggc_add_tree_root (&f2c_cilist_struct, 1);
- 
        f2c_cilist_struct = ref;
      }
  
--- 1323,1328 ----
*************** ffeste_io_cilist_ (bool have_err,
*** 1508,1519 ****
     declaration of variables (temporaries) to the expanding of expressions,
     statements, etc.  */
  
  static tree
  ffeste_io_cllist_ (bool have_err,
  		   ffebld unit_expr,
  		   ffestpFile *stat_spec)
  {
-   static tree f2c_close_struct = NULL_TREE;
    tree t;
    tree ttype;
    tree field;
--- 1504,1515 ----
     declaration of variables (temporaries) to the expanding of expressions,
     statements, etc.  */
  
+ static GTY(()) tree f2c_close_struct;
  static tree
  ffeste_io_cllist_ (bool have_err,
  		   ffebld unit_expr,
  		   ffestpFile *stat_spec)
  {
    tree t;
    tree ttype;
    tree field;
*************** ffeste_io_cllist_ (bool have_err,
*** 1541,1548 ****
        TYPE_FIELDS (ref) = errfield;
        layout_type (ref);
  
-       ggc_add_tree_root (&f2c_close_struct, 1);
- 
        f2c_close_struct = ref;
      }
  
--- 1537,1542 ----
*************** ffeste_io_cllist_ (bool have_err,
*** 1622,1627 ****
--- 1616,1622 ----
     declaration of variables (temporaries) to the expanding of expressions,
     statements, etc.  */
  
+ static GTY(()) tree f2c_icilist_struct;
  static tree
  ffeste_io_icilist_ (bool have_err,
  		    ffebld unit_expr,
*************** ffeste_io_icilist_ (bool have_err,
*** 1629,1635 ****
  		    ffestvFormat format,
  		    ffestpFile *format_spec)
  {
-   static tree f2c_icilist_struct = NULL_TREE;
    tree t;
    tree ttype;
    tree field;
--- 1624,1629 ----
*************** ffeste_io_icilist_ (bool have_err,
*** 1663,1670 ****
        TYPE_FIELDS (ref) = errfield;
        layout_type (ref);
  
-       ggc_add_tree_root (&f2c_icilist_struct, 1);
- 
        f2c_icilist_struct = ref;
      }
  
--- 1657,1662 ----
*************** ffeste_io_icilist_ (bool have_err,
*** 1851,1856 ****
--- 1843,1849 ----
     declaration of variables (temporaries) to the expanding of expressions,
     statements, etc.  */
  
+ static GTY(()) tree f2c_inquire_struct;
  static tree
  ffeste_io_inlist_ (bool have_err,
  		   ffestpFile *unit_spec,
*************** ffeste_io_inlist_ (bool have_err,
*** 1870,1876 ****
  		   ffestpFile *nextrec_spec,
  		   ffestpFile *blank_spec)
  {
-   static tree f2c_inquire_struct = NULL_TREE;
    tree t;
    tree ttype;
    tree field;
--- 1863,1868 ----
*************** ffeste_io_inlist_ (bool have_err,
*** 1959,1966 ****
        TYPE_FIELDS (ref) = errfield;
        layout_type (ref);
  
-       ggc_add_tree_root (&f2c_inquire_struct, 1);
- 
        f2c_inquire_struct = ref;
      }
  
--- 1951,1956 ----
*************** ffeste_io_inlist_ (bool have_err,
*** 2109,2114 ****
--- 2099,2105 ----
     declaration of variables (temporaries) to the expanding of expressions,
     statements, etc.  */
  
+ static GTY(()) tree f2c_open_struct;
  static tree
  ffeste_io_olist_ (bool have_err,
  		  ffebld unit_expr,
*************** ffeste_io_olist_ (bool have_err,
*** 2119,2125 ****
  		  ffestpFile *recl_spec,
  		  ffestpFile *blank_spec)
  {
-   static tree f2c_open_struct = NULL_TREE;
    tree t;
    tree ttype;
    tree field;
--- 2110,2115 ----
*************** ffeste_io_olist_ (bool have_err,
*** 2163,2170 ****
        TYPE_FIELDS (ref) = errfield;
        layout_type (ref);
  
-       ggc_add_tree_root (&f2c_open_struct, 1);
- 
        f2c_open_struct = ref;
      }
  
--- 2153,2158 ----
*************** ffeste_R810 (ffestw block, unsigned long
*** 2723,2743 ****
      do
        {
  	texprlow = (c->low == NULL) ? NULL_TREE
! 	  : ffecom_constantunion (&ffebld_constant_union (c->low), s->type,
! 				  s->kindtype,
! 				  ffecom_tree_type[s->type][s->kindtype]);
  	if (c->low != c->high)
  	  {
  	    texprhigh = (c->high == NULL) ? NULL_TREE
! 	      : ffecom_constantunion (&ffebld_constant_union (c->high),
! 				      s->type, s->kindtype,
! 				      ffecom_tree_type[s->type][s->kindtype]);
  	    pushok = pushcase_range (texprlow, texprhigh, convert,
  				     tlabel, &duplicate);
  	  }
  	else
  	  pushok = pushcase (texprlow, convert, tlabel, &duplicate);
! 	assert (pushok == 0);
  	c = c->next_stmt;
  	/* Unlink prev.  */
  	c->previous_stmt->previous_stmt->next_stmt = c;
--- 2711,2737 ----
      do
        {
  	texprlow = (c->low == NULL) ? NULL_TREE
! 	  : ffecom_constantunion_with_type (&ffebld_constant_union (c->low),
! 				  ffecom_tree_type[s->type][s->kindtype], c->low->consttype);
  	if (c->low != c->high)
  	  {
  	    texprhigh = (c->high == NULL) ? NULL_TREE
! 	      : ffecom_constantunion_with_type (&ffebld_constant_union (c->high),
! 				      ffecom_tree_type[s->type][s->kindtype], c->high->consttype);
  	    pushok = pushcase_range (texprlow, texprhigh, convert,
  				     tlabel, &duplicate);
  	  }
  	else
  	  pushok = pushcase (texprlow, convert, tlabel, &duplicate);
! 	assert((pushok !=2) || (pushok !=0));
! 	if (pushok==2)
! 	  {
! 	    ffebad_start_msg ("SELECT (at %0) has duplicate cases -- check integer overflow of CASE(s)",
! 	      FFEBAD_severityFATAL);
! 	    ffebad_here (0, ffestw_line (block), ffestw_col (block));
! 	    ffebad_finish ();
! 	    ffestw_set_select_texpr (block, error_mark_node);
! 	  }
  	c = c->next_stmt;
  	/* Unlink prev.  */
  	c->previous_stmt->previous_stmt->next_stmt = c;
*************** ffeste_terminate_2 (void)
*** 4618,4620 ****
--- 4612,4616 ----
    assert (! ffeste_top_block_);
  }
  #endif
+ 
+ #include "gt-f-ste.h"
diff -Nrc3pad gcc-3.2.3/gcc/f/target.c gcc-3.3/gcc/f/target.c
*** gcc-3.2.3/gcc/f/target.c	2002-09-14 20:27:12.000000000 +0000
--- gcc-3.3/gcc/f/target.c	2002-09-16 16:36:38.000000000 +0000
*************** the Free Software Foundation, 59 Temple 
*** 69,81 ****
  /* Include files. */
  
  #include "proj.h"
- #include "glimits.h"
  #include "target.h"
  #include "diagnostic.h"
  #include "bad.h"
  #include "info.h"
  #include "lex.h"
  #include "malloc.h"
  
  /* Externals defined here. */
  
--- 69,81 ----
  /* Include files. */
  
  #include "proj.h"
  #include "target.h"
  #include "diagnostic.h"
  #include "bad.h"
  #include "info.h"
  #include "lex.h"
  #include "malloc.h"
+ #include "real.h"
  
  /* Externals defined here. */
  
*************** ffetarget_print_hex (FILE *f, ffetargetT
*** 2191,2197 ****
  {
    char *p;
    char digits[sizeof (value) * CHAR_BIT / 4 + 1];
!   static char hexdigits[16] = "0123456789ABCDEF";
  
    if (f == NULL)
      f = dmpout;
--- 2191,2197 ----
  {
    char *p;
    char digits[sizeof (value) * CHAR_BIT / 4 + 1];
!   static const char hexdigits[16] = "0123456789ABCDEF";
  
    if (f == NULL)
      f = dmpout;
*************** ffetarget_real1 (ffetargetReal1 *value, 
*** 2277,2285 ****
  
    *p = '\0';
  
!   ffetarget_make_real1 (value,
! 			FFETARGET_ATOF_ (ptr,
! 					 SFmode));
  
    if (sz > ARRAY_SIZE (ffetarget_string_))
      malloc_kill_ks (malloc_pool_image (), ptr, sz);
--- 2277,2287 ----
  
    *p = '\0';
  
!   {
!     REAL_VALUE_TYPE rv;
!     rv = FFETARGET_ATOF_ (ptr, SFmode);
!     ffetarget_make_real1 (value, rv);
!   }
  
    if (sz > ARRAY_SIZE (ffetarget_string_))
      malloc_kill_ks (malloc_pool_image (), ptr, sz);
*************** ffetarget_real2 (ffetargetReal2 *value, 
*** 2363,2371 ****
  
    *p = '\0';
  
!   ffetarget_make_real2 (value,
! 			FFETARGET_ATOF_ (ptr,
! 					 DFmode));
  
    if (sz > ARRAY_SIZE (ffetarget_string_))
      malloc_kill_ks (malloc_pool_image (), ptr, sz);
--- 2365,2375 ----
  
    *p = '\0';
  
!   {
!     REAL_VALUE_TYPE rv;
!     rv = FFETARGET_ATOF_ (ptr, DFmode);
!     ffetarget_make_real2 (value, rv);
!   }
  
    if (sz > ARRAY_SIZE (ffetarget_string_))
      malloc_kill_ks (malloc_pool_image (), ptr, sz);
diff -Nrc3pad gcc-3.2.3/gcc/f/target.h gcc-3.3/gcc/f/target.h
*** gcc-3.2.3/gcc/f/target.h	2002-08-30 07:29:48.000000000 +0000
--- gcc-3.3/gcc/f/target.h	2003-03-27 03:45:24.000000000 +0000
*************** the Free Software Foundation, 59 Temple 
*** 38,53 ****
  #endif
  #endif
  
- /* For now, g77 requires the ability to determine the exact bit pattern
-    of a float on the target machine.  (Hopefully this will be changed
-    soon).  Make sure we can do this.  */
- 
- #if !defined (REAL_ARITHMETIC) \
-   && ((TARGET_FLOAT_FORMAT != HOST_FLOAT_FORMAT) \
-       || (FLOAT_WORDS_BIG_ENDIAN != HOST_FLOAT_WORDS_BIG_ENDIAN))
- #error "g77 requires ability to access exact FP representation of target machine"
- #endif
- 
  /* Simple definitions and enumerations. */
  
  #define FFETARGET_charactersizeNONE (-1)
--- 38,43 ----
*************** typedef ? ffetargetLogical8;
*** 341,457 ****
  ?
  #endif
  #if FFETARGET_okREAL1
- #ifdef REAL_ARITHMETIC
- #ifdef FFETARGET_32bit_longs
- typedef long int ffetargetReal1;
- #define ffetargetReal1_f "l"
- #define ffetarget_cvt_r1_to_rv_ REAL_VALUE_UNTO_TARGET_SINGLE
- #define ffetarget_cvt_rv_to_r1_ REAL_VALUE_TO_TARGET_SINGLE
- #else
  typedef int ffetargetReal1;
  #define ffetargetReal1_f ""
! #define ffetarget_cvt_r1_to_rv_(in) \
!   ({ REAL_VALUE_TYPE _rv; \
!      _rv = REAL_VALUE_UNTO_TARGET_SINGLE ((long) (in)); \
       _rv; })
  #define ffetarget_cvt_rv_to_r1_(in, out) \
    ({ long _tmp; \
       REAL_VALUE_TO_TARGET_SINGLE ((in), _tmp); \
       (out) = (ffetargetReal1) _tmp; })
  #endif
- #else	/* REAL_ARITHMETIC */
- typedef float ffetargetReal1;
- #define ffetargetReal1_f ""
- #endif	/* REAL_ARITHMETIC */
- #endif
  #if FFETARGET_okREAL2
! #ifdef REAL_ARITHMETIC
! #ifdef FFETARGET_32bit_longs
! typedef struct
!   {
!     long int v[2];
!   }
! ffetargetReal2;
! #define ffetargetReal2_f "l"
! #define ffetarget_cvt_r2_to_rv_ REAL_VALUE_UNTO_TARGET_DOUBLE
! #define ffetarget_cvt_rv_to_r2_ REAL_VALUE_TO_TARGET_DOUBLE
! #else
! typedef struct
!   {
!     int v[2];
!   }
! ffetargetReal2;
  #define ffetargetReal2_f ""
! #define ffetarget_cvt_r2_to_rv_(in) \
!   ({ REAL_VALUE_TYPE _rv; \
!      long _tmp[2]; \
!      _tmp[0] = (in)[0]; \
!      _tmp[1] = (in)[1]; \
!      _rv = REAL_VALUE_UNTO_TARGET_DOUBLE (_tmp); \
       _rv; })
! #define ffetarget_cvt_rv_to_r2_(in, out) \
!   ({ long _tmp[2]; \
!      REAL_VALUE_TO_TARGET_DOUBLE ((in), _tmp); \
!      (out)[0] = (int) (_tmp[0]); \
!      (out)[1] = (int) (_tmp[1]); })
! #endif
! #else
! typedef double ffetargetReal2;
! #define ffetargetReal2_f ""
! #endif
  #endif
  #if FFETARGET_okREAL3
- #ifdef REAL_ARITHMETIC
  typedef long ffetargetReal3[?];
- #else
- typedef ? ffetargetReal3;
- #define ffetargetReal3_f
- #endif
  ?
  #endif
  #if FFETARGET_okREAL4
- #ifdef REAL_ARITHMETIC
  typedef long ffetargetReal4[?];
- #else
- typedef ? ffetargetReal4;
- #define ffetargetReal4_f
- #endif
  ?
  #endif
  #if FFETARGET_okREAL5
- #ifdef REAL_ARITHMETIC
  typedef long ffetargetReal5[?];
- #else
- typedef ? ffetargetReal5;
- #define ffetargetReal5_f
- #endif
  ?
  #endif
  #if FFETARGET_okREAL6
- #ifdef REAL_ARITHMETIC
  typedef long ffetargetReal6[?];
- #else
- typedef ? ffetargetReal6;
- #define ffetargetReal6_f
- #endif
  ?
  #endif
  #if FFETARGET_okREAL7
- #ifdef REAL_ARITHMETIC
  typedef long ffetargetReal7[?];
- #else
- typedef ? ffetargetReal7;
- #define ffetargetReal7_f
- #endif
  ?
  #endif
  #if FFETARGET_okREAL8
- #ifdef REAL_ARITHMETIC
  typedef long ffetargetReal8[?];
- #else
- typedef ? ffetargetReal8;
- #define ffetargetReal8_f
- #endif
  ?
  #endif
  #if FFETARGET_okCOMPLEX1
--- 331,383 ----
  ?
  #endif
  #if FFETARGET_okREAL1
  typedef int ffetargetReal1;
  #define ffetargetReal1_f ""
! #define ffetarget_cvt_r1_to_rv_(in)					\
!   ({ REAL_VALUE_TYPE _rv;						\
!      long _in = (in);							\
!      real_from_target (&_rv, &_in, mode_for_size (32, MODE_FLOAT, 0));	\
       _rv; })
  #define ffetarget_cvt_rv_to_r1_(in, out) \
    ({ long _tmp; \
       REAL_VALUE_TO_TARGET_SINGLE ((in), _tmp); \
       (out) = (ffetargetReal1) _tmp; })
  #endif
  #if FFETARGET_okREAL2
! typedef struct { int v[2]; } ffetargetReal2;
  #define ffetargetReal2_f ""
! #define ffetarget_cvt_r2_to_rv_(in)					\
!   ({ REAL_VALUE_TYPE _rv; long _tmp[2];					\
!      _tmp[0] = (in)[0]; _tmp[1] = (in)[1];				\
!      real_from_target (&_rv, _tmp, mode_for_size (64, MODE_FLOAT, 0));	\
       _rv; })
! #define ffetarget_cvt_rv_to_r2_(in, out)				\
!   ({ long _tmp[2];							\
!      REAL_VALUE_TO_TARGET_DOUBLE ((in), _tmp);				\
!      (out)[0] = (int)_tmp[0]; (out)[1] = (int)_tmp[1]; })
  #endif
  #if FFETARGET_okREAL3
  typedef long ffetargetReal3[?];
  ?
  #endif
  #if FFETARGET_okREAL4
  typedef long ffetargetReal4[?];
  ?
  #endif
  #if FFETARGET_okREAL5
  typedef long ffetargetReal5[?];
  ?
  #endif
  #if FFETARGET_okREAL6
  typedef long ffetargetReal6[?];
  ?
  #endif
  #if FFETARGET_okREAL7
  typedef long ffetargetReal7[?];
  ?
  #endif
  #if FFETARGET_okREAL8
  typedef long ffetargetReal8[?];
  ?
  #endif
  #if FFETARGET_okCOMPLEX1
*************** void *ffetarget_memcpy_ (void *dst, void
*** 872,878 ****
    REAL_VALUE_FROM_INT (resr, (long) lf, (long) ((lf < 0) ? -1 : 0),	\
  		       ((kt == 1) ? SFmode : DFmode))
  
- #ifdef REAL_ARITHMETIC
  #define ffetarget_add_complex1(res,l,r) \
    ({ REAL_VALUE_TYPE lr, li, rr, ri, resr, resi; \
       lr = ffetarget_cvt_r1_to_rv_ ((l).real); \
--- 798,803 ----
*************** void *ffetarget_memcpy_ (void *dst, void
*** 895,913 ****
       ffetarget_cvt_rv_to_r2_ (resr, &((res)->real.v[0])); \
       ffetarget_cvt_rv_to_r2_ (resi, &((res)->imaginary.v[0])); \
       FFEBAD; })
- #else
- #define ffetarget_add_complex1(res,l,r) \
-   ((res)->real = (l).real + (r).real, \
-    (res)->imaginary = (l).imaginary + (r).imaginary, FFEBAD)
- #define ffetarget_add_complex2(res,l,r) \
-   ((res)->real = (l).real + (r).real, \
-    (res)->imaginary = (l).imaginary + (r).imaginary, FFEBAD)
- #endif
  #define ffetarget_add_integer1(res,l,r) (*(res) = (l) + (r), FFEBAD)
  #define ffetarget_add_integer2(res,l,r) (*(res) = (l) + (r), FFEBAD)
  #define ffetarget_add_integer3(res,l,r) (*(res) = (l) + (r), FFEBAD)
  #define ffetarget_add_integer4(res,l,r) (*(res) = (l) + (r), FFEBAD)
- #ifdef REAL_ARITHMETIC
  #define ffetarget_add_real1(res,l,r) \
    ({ REAL_VALUE_TYPE lr, rr, resr; \
       lr = ffetarget_cvt_r1_to_rv_ ((l)); \
--- 820,829 ----
*************** void *ffetarget_memcpy_ (void *dst, void
*** 922,931 ****
       REAL_ARITHMETIC (resr, PLUS_EXPR, lr, rr); \
       ffetarget_cvt_rv_to_r2_ (resr, &((res)->v[0])); \
       FFEBAD; })
- #else
- #define ffetarget_add_real1(res,l,r) (*(res) = (l) + (r), FFEBAD)
- #define ffetarget_add_real2(res,l,r) (*(res) = (l) + (r), FFEBAD)
- #endif
  #define ffetarget_aggregate_ptr_memcpy(dbt,dkt,sbt,skt) \
    ((ffetargetCopyfunc) ffetarget_memcpy_)
  #define ffetarget_and_integer1(res,l,r) (*(res) = (l) & (r), FFEBAD)
--- 838,843 ----
*************** void *ffetarget_memcpy_ (void *dst, void
*** 969,975 ****
    ffetarget_convert_any_hollerith_ ((char *) (res), sizeof(*(res)), l)
  #define ffetarget_convert_complex1_typeless(res,l) \
    ffetarget_convert_any_typeless_ ((char *) (res), sizeof(*(res)), l)
- #ifdef REAL_ARITHMETIC
  #define ffetarget_convert_complex1_complex2(res,l) \
    ({ REAL_VALUE_TYPE lr, li; \
       lr = ffetarget_cvt_r2_to_rv_ (&((l).real.v[0])); \
--- 881,886 ----
*************** void *ffetarget_memcpy_ (void *dst, void
*** 977,987 ****
       ffetarget_cvt_rv_to_r1_ (lr, (res)->real); \
       ffetarget_cvt_rv_to_r1_ (li, (res)->imaginary), \
       FFEBAD; })
- #else
- #define ffetarget_convert_complex1_complex2(res,l) \
-   ((res)->real = (l).real, (res)->imaginary = (l).imaginary, FFEBAD)
- #endif
- #ifdef REAL_ARITHMETIC
  #define ffetarget_convert_complex1_integer(res,l) \
    ({ REAL_VALUE_TYPE resi, resr; \
       ffetargetInteger1 lf = (l); \
--- 888,893 ----
*************** void *ffetarget_memcpy_ (void *dst, void
*** 990,1008 ****
       ffetarget_cvt_rv_to_r1_ (resr, (res)->real); \
       ffetarget_cvt_rv_to_r1_ (resi, (res)->imaginary); \
       FFEBAD; })
- #else
- #define ffetarget_convert_complex1_integer(res,l) \
-   ((res)->real = (l), (res)->imaginary = 0, FFEBAD)
- #endif
  #define ffetarget_convert_complex1_integer1 ffetarget_convert_complex1_integer
  #define ffetarget_convert_complex1_integer2 ffetarget_convert_complex1_integer
  #define ffetarget_convert_complex1_integer3 ffetarget_convert_complex1_integer
- #ifdef REAL_ARITHMETIC
  #define ffetarget_convert_complex1_integer4(res,l) FFEBAD_NOCANDO
- #else
- #define ffetarget_convert_complex1_integer4 ffetarget_convert_complex1_integer
- #endif
- #ifdef REAL_ARITHMETIC
  #define ffetarget_convert_complex1_real1(res,l) \
    ((res)->real = (l), \
     ffetarget_cvt_rv_to_r1_ (dconst0, (res)->imaginary), \
--- 896,905 ----
*************** void *ffetarget_memcpy_ (void *dst, void
*** 1013,1031 ****
       ffetarget_cvt_rv_to_r1_ (lr, (res)->real); \
       ffetarget_cvt_rv_to_r1_ (dconst0, (res)->imaginary), \
       FFEBAD; })
- #else
- #define ffetarget_convert_complex1_real1(res,l) \
-   ((res)->real = (l), (res)->imaginary = 0, FFEBAD)
- #define ffetarget_convert_complex1_real2(res,l) \
-   ((res)->real = (l), (res)->imaginary = 0, FFEBAD)
- #endif
  #define ffetarget_convert_complex2_character1(res,l) \
    ffetarget_convert_any_character1_ ((char *) (res), sizeof(*(res)), l)
  #define ffetarget_convert_complex2_hollerith(res,l) \
    ffetarget_convert_any_hollerith_ ((char *) (res), sizeof(*(res)), l)
  #define ffetarget_convert_complex2_typeless(res,l) \
    ffetarget_convert_any_typeless_ ((char *) (res), sizeof(*(res)), l)
- #ifdef REAL_ARITHMETIC
  #define ffetarget_convert_complex2_complex1(res,l) \
    ({ REAL_VALUE_TYPE lr, li; \
       lr = ffetarget_cvt_r1_to_rv_ ((l).real); \
--- 910,921 ----
*************** void *ffetarget_memcpy_ (void *dst, void
*** 1033,1043 ****
       ffetarget_cvt_rv_to_r2_ (lr, &((res)->real.v[0])); \
       ffetarget_cvt_rv_to_r2_ (li, &((res)->imaginary.v[0])), \
       FFEBAD; })
- #else
- #define ffetarget_convert_complex2_complex1(res,l) \
-   ((res)->real = (l).real, (res)->imaginary = (l).imaginary, FFEBAD)
- #endif
- #ifdef REAL_ARITHMETIC
  #define ffetarget_convert_complex2_integer(res,l) \
    ({ REAL_VALUE_TYPE resi, resr; \
       ffetargetInteger1 lf = (l); \
--- 923,928 ----
*************** void *ffetarget_memcpy_ (void *dst, void
*** 1046,1064 ****
       ffetarget_cvt_rv_to_r2_ (resr, &((res)->real.v[0])); \
       ffetarget_cvt_rv_to_r2_ (resi, &((res)->imaginary.v[0])); \
       FFEBAD; })
- #else
- #define ffetarget_convert_complex2_integer(res,l) \
-   ((res)->real = (l), (res)->imaginary = 0, FFEBAD)
- #endif
  #define ffetarget_convert_complex2_integer1 ffetarget_convert_complex2_integer
  #define ffetarget_convert_complex2_integer2 ffetarget_convert_complex2_integer
  #define ffetarget_convert_complex2_integer3 ffetarget_convert_complex2_integer
- #ifdef REAL_ARITHMETIC
  #define ffetarget_convert_complex2_integer4(res,l) FFEBAD_NOCANDO
- #else
- #define ffetarget_convert_complex2_integer4 ffetarget_convert_complex2_integer
- #endif
- #ifdef REAL_ARITHMETIC
  #define ffetarget_convert_complex2_real1(res,l) \
    ({ REAL_VALUE_TYPE lr; \
       lr = ffetarget_cvt_r1_to_rv_ (l); \
--- 931,940 ----
*************** void *ffetarget_memcpy_ (void *dst, void
*** 1069,1080 ****
    ((res)->real = (l), \
     ffetarget_cvt_rv_to_r2_ (dconst0, &((res)->imaginary.v[0])), \
     FFEBAD)
- #else
- #define ffetarget_convert_complex2_real1(res,l) \
-   ((res)->real = (l), (res)->imaginary = 0, FFEBAD)
- #define ffetarget_convert_complex2_real2(res,l) \
-   ((res)->real = (l), (res)->imaginary = 0, FFEBAD)
- #endif
  #define ffetarget_convert_integer2_character1(res,l) \
          ffetarget_convert_integer1_character1(res,l)
  #define ffetarget_convert_integer2_complex1(res,l) \
--- 945,950 ----
*************** void *ffetarget_memcpy_ (void *dst, void
*** 1127,1141 ****
          ffetarget_convert_integer1_typeless(res,l)
  #define ffetarget_convert_integer4_character1(res,l) \
          ffetarget_convert_integer1_character1(res,l)
- #ifdef REAL_ARITHMETIC
  #define ffetarget_convert_integer4_complex1(res,l) FFEBAD_NOCANDO
  #define ffetarget_convert_integer4_complex2(res,l) FFEBAD_NOCANDO
- #else
- #define ffetarget_convert_integer4_complex1(res,l) \
-         ffetarget_convert_integer1_complex1(res,l)
- #define ffetarget_convert_integer4_complex2(res,l) \
-         ffetarget_convert_integer1_complex2(res,l)
- #endif
  #define ffetarget_convert_integer4_hollerith(res,l) \
          ffetarget_convert_integer1_hollerith(res,l)
  #define ffetarget_convert_integer4_integer1(res,l) (*(res) = (l), FFEBAD)
--- 997,1004 ----
*************** void *ffetarget_memcpy_ (void *dst, void
*** 1149,1163 ****
          ffetarget_convert_integer1_logical1(res,l)
  #define ffetarget_convert_integer4_logical4(res,l) \
          ffetarget_convert_integer1_logical1(res,l)
- #ifdef REAL_ARITHMETIC
  #define ffetarget_convert_integer4_real1(res,l) FFEBAD_NOCANDO
  #define ffetarget_convert_integer4_real2(res,l) FFEBAD_NOCANDO
- #else
- #define ffetarget_convert_integer4_real1(res,l) \
-         ffetarget_convert_integer1_real1(res,l)
- #define ffetarget_convert_integer4_real2(res,l) \
-         ffetarget_convert_integer1_real2(res,l)
- #endif
  #define ffetarget_convert_integer4_typeless(res,l) \
          ffetarget_convert_integer1_typeless(res,l)
  #define ffetarget_convert_logical1_character1(res,l) \
--- 1012,1019 ----
*************** void *ffetarget_memcpy_ (void *dst, void
*** 1225,1231 ****
  #define ffetarget_convert_integer1_logical2(res,l) (*(res) = (l), FFEBAD)
  #define ffetarget_convert_integer1_logical3(res,l) (*(res) = (l), FFEBAD)
  #define ffetarget_convert_integer1_logical4(res,l) (*(res) = (l), FFEBAD)
- #ifdef REAL_ARITHMETIC
  #define ffetarget_convert_integer1_real1(res,l) \
    ({ REAL_VALUE_TYPE lr; \
       lr = ffetarget_cvt_r1_to_rv_ (l); \
--- 1081,1086 ----
*************** void *ffetarget_memcpy_ (void *dst, void
*** 1250,1261 ****
       REAL_VALUE_TO_INT (&ffetarget_long_val_, &ffetarget_long_junk_, lr); \
       *(res) = ffetarget_long_val_; \
       FFEBAD; })
- #else
- #define ffetarget_convert_integer1_real1(res,l) (*(res) = (l), FFEBAD)
- #define ffetarget_convert_integer1_real2(res,l) (*(res) = (l), FFEBAD)
- #define ffetarget_convert_integer1_complex1(res,l) (*(res) = (l).real, FFEBAD)
- #define ffetarget_convert_integer1_complex2(res,l) (*(res) = (l).real, FFEBAD)
- #endif
  #define ffetarget_convert_real1_character1(res,l) \
    ffetarget_convert_any_character1_ ((char *) (res), sizeof(*(res)), l)
  #define ffetarget_convert_real1_hollerith(res,l) \
--- 1105,1110 ----
*************** void *ffetarget_memcpy_ (void *dst, void
*** 1264,1299 ****
          ffetarget_convert_real1_integer1(res,l)
  #define ffetarget_convert_real1_integer3(res,l) \
          ffetarget_convert_real1_integer1(res,l)
- #ifdef REAL_ARITHMETIC
  #define ffetarget_convert_real1_integer4(res,l) FFEBAD_NOCANDO
- #else
- #define ffetarget_convert_real1_integer4(res,l) \
-         ffetarget_convert_real1_integer1(res,l)
- #endif
  #define ffetarget_convert_real1_typeless(res,l) \
    ffetarget_convert_any_typeless_ ((char *) (res), sizeof(*(res)), l)
  #define ffetarget_convert_real1_complex1(res,l) (*(res) = (l).real, FFEBAD)
  #define ffetarget_convert_real1_complex2(res,l) \
    ffetarget_convert_real1_real2 ((res), (l).real)
- #ifdef REAL_ARITHMETIC
  #define ffetarget_convert_real1_integer1(res,l) \
    ({ REAL_VALUE_TYPE resr; \
       ffetargetInteger1 lf = (l); \
       FFETARGET_REAL_VALUE_FROM_INT_ (resr, lf, 1); \
       ffetarget_cvt_rv_to_r1_ (resr, *(res)); \
       FFEBAD; })
- #else
- #define ffetarget_convert_real1_integer1(res,l) (*(res) = (l), FFEBAD)
- #endif
- #ifdef REAL_ARITHMETIC
  #define ffetarget_convert_real1_real2(res,l) \
    ({ REAL_VALUE_TYPE lr; \
       lr = ffetarget_cvt_r2_to_rv_ (&((l).v[0])); \
       ffetarget_cvt_rv_to_r1_ (lr, *(res)); \
       FFEBAD; })
- #else
- #define ffetarget_convert_real1_real2(res,l) (*(res) = (l), FFEBAD)
- #endif
  #define ffetarget_convert_real2_character1(res,l) \
    ffetarget_convert_any_character1_ ((char *) (res), sizeof(*(res)), l)
  #define ffetarget_convert_real2_hollerith(res,l) \
--- 1113,1135 ----
*************** void *ffetarget_memcpy_ (void *dst, void
*** 1302,1319 ****
          ffetarget_convert_real2_integer1(res,l)
  #define ffetarget_convert_real2_integer3(res,l) \
          ffetarget_convert_real2_integer1(res,l)
- #ifdef REAL_ARITHMETIC
  #define ffetarget_convert_real2_integer4(res,l) FFEBAD_NOCANDO
- #else
- #define ffetarget_convert_real2_integer4(res,l) \
-         ffetarget_convert_real2_integer1(res,l)
- #endif
  #define ffetarget_convert_real2_typeless(res,l) \
    ffetarget_convert_any_typeless_ ((char *) (res), sizeof(*(res)), l)
  #define ffetarget_convert_real2_complex1(res,l) \
    ffetarget_convert_real2_real1 ((res), (l).real)
  #define ffetarget_convert_real2_complex2(res,l) (*(res) = (l).real, FFEBAD)
- #ifdef REAL_ARITHMETIC
  #define ffetarget_convert_real2_integer(res,l) \
    ({ REAL_VALUE_TYPE resr; \
       ffetargetInteger1 lf = (l); \
--- 1138,1149 ----
*************** void *ffetarget_memcpy_ (void *dst, void
*** 1321,1348 ****
       ffetarget_cvt_rv_to_r2_ (resr, &((res)->v[0])); \
       FFEBAD; })
  #define ffetarget_convert_real2_integer1 ffetarget_convert_real2_integer
- #else
- #define ffetarget_convert_real2_integer1(res,l) (*(res) = (l), FFEBAD)
- #endif
- #ifdef REAL_ARITHMETIC
  #define ffetarget_convert_real2_real1(res,l) \
    ({ REAL_VALUE_TYPE lr; \
       lr = ffetarget_cvt_r1_to_rv_ ((l)); \
       ffetarget_cvt_rv_to_r2_ (lr, &((res)->v[0])); \
       FFEBAD; })
- #else
- #define ffetarget_convert_real2_real1(res,l) (*(res) = (l), FFEBAD)
- #endif
  #define ffetarget_divide_integer1(res,l,r) \
    (((r) == 0) ? (*(res) = 0, FFEBAD_DIV_BY_ZERO)  \
!    : (*(res) = (l) / (r), FFEBAD))
  #define ffetarget_divide_integer2(res,l,r) \
          ffetarget_divide_integer1(res,l,r)
  #define ffetarget_divide_integer3(res,l,r) \
          ffetarget_divide_integer1(res,l,r)
  #define ffetarget_divide_integer4(res,l,r) \
          ffetarget_divide_integer1(res,l,r)
- #ifdef REAL_ARITHMETIC
  #define ffetarget_divide_real1(res,l,r) \
    ({ REAL_VALUE_TYPE lr, rr, resr; \
       lr = ffetarget_cvt_r1_to_rv_ ((l)); \
--- 1151,1171 ----
       ffetarget_cvt_rv_to_r2_ (resr, &((res)->v[0])); \
       FFEBAD; })
  #define ffetarget_convert_real2_integer1 ffetarget_convert_real2_integer
  #define ffetarget_convert_real2_real1(res,l) \
    ({ REAL_VALUE_TYPE lr; \
       lr = ffetarget_cvt_r1_to_rv_ ((l)); \
       ffetarget_cvt_rv_to_r2_ (lr, &((res)->v[0])); \
       FFEBAD; })
  #define ffetarget_divide_integer1(res,l,r) \
    (((r) == 0) ? (*(res) = 0, FFEBAD_DIV_BY_ZERO)  \
!    : (((r) == -1) ? (*(res) = -(l), FFEBAD)       \
!       : (*(res) = (l) / (r), FFEBAD)))
  #define ffetarget_divide_integer2(res,l,r) \
          ffetarget_divide_integer1(res,l,r)
  #define ffetarget_divide_integer3(res,l,r) \
          ffetarget_divide_integer1(res,l,r)
  #define ffetarget_divide_integer4(res,l,r) \
          ffetarget_divide_integer1(res,l,r)
  #define ffetarget_divide_real1(res,l,r) \
    ({ REAL_VALUE_TYPE lr, rr, resr; \
       lr = ffetarget_cvt_r1_to_rv_ ((l)); \
*************** void *ffetarget_memcpy_ (void *dst, void
*** 1369,1383 ****
  	      FFEBAD; \
  	    }); \
  	 })
- #else
- #define ffetarget_divide_real1(res,l,r) \
-   (((r) == 0) ? (*(res) = 0, FFEBAD_DIV_BY_ZERO)  \
-    : (*(res) = (l) / (r), FFEBAD))
- #define ffetarget_divide_real2(res,l,r) \
-   (((r) == 0) ? (*(res) = 0, FFEBAD_DIV_BY_ZERO)  \
-    : (*(res) = (l) / (r), FFEBAD))
- #endif
- #ifdef REAL_ARITHMETIC
  #define ffetarget_eq_complex1(res,l,r) \
    ({ REAL_VALUE_TYPE lr, li, rr, ri; \
       lr = ffetarget_cvt_r1_to_rv_ ((l).real); \
--- 1192,1197 ----
*************** void *ffetarget_memcpy_ (void *dst, void
*** 1396,1409 ****
       *(res) = (REAL_VALUES_EQUAL (lr, rr) && REAL_VALUES_EQUAL (li, ri)) \
         ? TRUE : FALSE; \
       FFEBAD; })
- #else
- #define ffetarget_eq_complex1(res,l,r) \
-   (*(res) = (((l).real == (r).real) && ((l).imaginary == (r).imaginary))  \
-    ? TRUE : FALSE, FFEBAD)
- #define ffetarget_eq_complex2(res,l,r) \
-   (*(res) = (((l).real == (r).real) && ((l).imaginary == (r).imaginary))  \
-    ? TRUE : FALSE, FFEBAD)
- #endif
  #define ffetarget_eq_integer1(res,l,r) \
    (*(res) = ((l) == (r)) ? TRUE : FALSE, FFEBAD)
  #define ffetarget_eq_integer2(res,l,r) \
--- 1210,1215 ----
*************** void *ffetarget_memcpy_ (void *dst, void
*** 1412,1418 ****
    (*(res) = ((l) == (r)) ? TRUE : FALSE, FFEBAD)
  #define ffetarget_eq_integer4(res,l,r) \
    (*(res) = ((l) == (r)) ? TRUE : FALSE, FFEBAD)
- #ifdef REAL_ARITHMETIC
  #define ffetarget_eq_real1(res,l,r) \
    ({ REAL_VALUE_TYPE lr, rr; \
       lr = ffetarget_cvt_r1_to_rv_ ((l)); \
--- 1218,1223 ----
*************** void *ffetarget_memcpy_ (void *dst, void
*** 1425,1436 ****
       rr = ffetarget_cvt_r2_to_rv_ (&((r).v[0])); \
       *(res) = REAL_VALUES_EQUAL (lr, rr) ? TRUE : FALSE; \
       FFEBAD; })
- #else
- #define ffetarget_eq_real1(res,l,r) \
-   (*(res) = ((l) == (r)) ? TRUE : FALSE, FFEBAD)
- #define ffetarget_eq_real2(res,l,r) \
-   (*(res) = ((l) == (r)) ? TRUE : FALSE, FFEBAD)
- #endif
  #define ffetarget_eqv_integer1(res,l,r) (*(res) = (l) ^ ~(r), FFEBAD)
  #define ffetarget_eqv_integer2(res,l,r) (*(res) = (l) ^ ~(r), FFEBAD)
  #define ffetarget_eqv_integer3(res,l,r) (*(res) = (l) ^ ~(r), FFEBAD)
--- 1230,1235 ----
*************** void *ffetarget_memcpy_ (void *dst, void
*** 1447,1453 ****
    (*(res) = ((l) >= (r)) ? TRUE : FALSE, FFEBAD)
  #define ffetarget_ge_integer4(res,l,r) \
    (*(res) = ((l) >= (r)) ? TRUE : FALSE, FFEBAD)
- #ifdef REAL_ARITHMETIC
  #define ffetarget_ge_real1(res,l,r) \
    ({ REAL_VALUE_TYPE lr, rr; \
       lr = ffetarget_cvt_r1_to_rv_ ((l)); \
--- 1246,1251 ----
*************** void *ffetarget_memcpy_ (void *dst, void
*** 1460,1471 ****
       rr = ffetarget_cvt_r2_to_rv_ (&((r).v[0])); \
       *(res) = REAL_VALUES_LESS (lr, rr) ? FALSE : TRUE; \
       FFEBAD; })
- #else
- #define ffetarget_ge_real1(res,l,r) \
-   (*(res) = ((l) >= (r)) ? TRUE : FALSE, FFEBAD)
- #define ffetarget_ge_real2(res,l,r) \
-   (*(res) = ((l) >= (r)) ? TRUE : FALSE, FFEBAD)
- #endif
  #define ffetarget_gt_integer1(res,l,r) \
    (*(res) = ((l) > (r)) ? TRUE : FALSE, FFEBAD)
  #define ffetarget_gt_integer2(res,l,r) \
--- 1258,1263 ----
*************** void *ffetarget_memcpy_ (void *dst, void
*** 1474,1480 ****
    (*(res) = ((l) > (r)) ? TRUE : FALSE, FFEBAD)
  #define ffetarget_gt_integer4(res,l,r) \
    (*(res) = ((l) > (r)) ? TRUE : FALSE, FFEBAD)
- #ifdef REAL_ARITHMETIC
  #define ffetarget_gt_real1(res,l,r) \
    ({ REAL_VALUE_TYPE lr, rr; \
       lr = ffetarget_cvt_r1_to_rv_ ((l)); \
--- 1266,1271 ----
*************** void *ffetarget_memcpy_ (void *dst, void
*** 1489,1500 ****
       *(res) = (REAL_VALUES_LESS (lr, rr) || REAL_VALUES_EQUAL (lr, rr)) \
         ? FALSE : TRUE; \
       FFEBAD; })
- #else
- #define ffetarget_gt_real1(res,l,r) \
-   (*(res) = ((l) > (r)) ? TRUE : FALSE, FFEBAD)
- #define ffetarget_gt_real2(res,l,r) \
-   (*(res) = ((l) > (r)) ? TRUE : FALSE, FFEBAD)
- #endif
  #define ffetarget_hexxmil(v,t) ffetarget_typeless_hex (v, t)
  #define ffetarget_hexxvxt(v,t) ffetarget_typeless_hex (v, t)
  #define ffetarget_hexzmil(v,t) ffetarget_typeless_hex (v, t)
--- 1280,1285 ----
*************** void *ffetarget_memcpy_ (void *dst, void
*** 1511,1517 ****
  #define ffetarget_integerdefault_is_magical(i) \
    (((unsigned int) i) == FFETARGET_integerBIG_MAGICAL)
  #endif
- #ifdef REAL_ARITHMETIC
  #define ffetarget_iszero_real1(l) \
    ({ REAL_VALUE_TYPE lr; \
       lr = ffetarget_cvt_r1_to_rv_ ((l)); \
--- 1296,1301 ----
*************** void *ffetarget_memcpy_ (void *dst, void
*** 1522,1531 ****
       lr = ffetarget_cvt_r2_to_rv_ (&((l).v[0])); \
       REAL_VALUES_EQUAL (lr, dconst0); \
     })
- #else
- #define ffetarget_iszero_real1(l) ((l) == 0.)
- #define ffetarget_iszero_real2(l) ((l) == 0.)
- #endif
  #define ffetarget_iszero_typeless(l) ((l) == 0)
  #define ffetarget_logical1(v,truth) (*(v) = truth ? 1 : 0)
  #define ffetarget_le_integer1(res,l,r) \
--- 1306,1311 ----
*************** void *ffetarget_memcpy_ (void *dst, void
*** 1536,1542 ****
    (*(res) = ((l) <= (r)) ? TRUE : FALSE, FFEBAD)
  #define ffetarget_le_integer4(res,l,r) \
    (*(res) = ((l) <= (r)) ? TRUE : FALSE, FFEBAD)
- #ifdef REAL_ARITHMETIC
  #define ffetarget_le_real1(res,l,r) \
    ({ REAL_VALUE_TYPE lr, rr; \
       lr = ffetarget_cvt_r1_to_rv_ ((l)); \
--- 1316,1321 ----
*************** void *ffetarget_memcpy_ (void *dst, void
*** 1551,1562 ****
       *(res) = (REAL_VALUES_LESS (lr, rr) || REAL_VALUES_EQUAL (lr, rr)) \
         ? TRUE : FALSE; \
       FFEBAD; })
- #else
- #define ffetarget_le_real1(res,l,r) \
-   (*(res) = ((l) <= (r)) ? TRUE : FALSE, FFEBAD)
- #define ffetarget_le_real2(res,l,r) \
-   (*(res) = ((l) <= (r)) ? TRUE : FALSE, FFEBAD)
- #endif
  #define ffetarget_lt_integer1(res,l,r) \
    (*(res) = ((l) < (r)) ? TRUE : FALSE, FFEBAD)
  #define ffetarget_lt_integer2(res,l,r) \
--- 1330,1335 ----
*************** void *ffetarget_memcpy_ (void *dst, void
*** 1565,1571 ****
    (*(res) = ((l) < (r)) ? TRUE : FALSE, FFEBAD)
  #define ffetarget_lt_integer4(res,l,r) \
    (*(res) = ((l) < (r)) ? TRUE : FALSE, FFEBAD)
- #ifdef REAL_ARITHMETIC
  #define ffetarget_lt_real1(res,l,r) \
    ({ REAL_VALUE_TYPE lr, rr; \
       lr = ffetarget_cvt_r1_to_rv_ ((l)); \
--- 1338,1343 ----
*************** void *ffetarget_memcpy_ (void *dst, void
*** 1578,1605 ****
       rr = ffetarget_cvt_r2_to_rv_ (&((r).v[0])); \
       *(res) = REAL_VALUES_LESS (lr, rr) ? TRUE : FALSE; \
       FFEBAD; })
- #else
- #define ffetarget_lt_real1(res,l,r) \
-   (*(res) = ((l) < (r)) ? TRUE : FALSE, FFEBAD)
- #define ffetarget_lt_real2(res,l,r) \
-   (*(res) = ((l) < (r)) ? TRUE : FALSE, FFEBAD)
- #endif
  #define ffetarget_length_character1(c) ((c).length)
  #define ffetarget_length_characterdefault ffetarget_length_character1
- #ifdef REAL_ARITHMETIC
  #define ffetarget_make_real1(res,lr) \
    ffetarget_cvt_rv_to_r1_ ((lr), *(res))
  #define ffetarget_make_real2(res,lr) \
    ffetarget_cvt_rv_to_r2_ ((lr), &((res)->v[0]))
- #else
- #define ffetarget_make_real1(res,lr) (*(res) = (lr))
- #define ffetarget_make_real2(res,lr) (*(res) = (lr))
- #endif
  #define ffetarget_multiply_integer1(res,l,r) (*(res) = (l) * (r), FFEBAD)
  #define ffetarget_multiply_integer2(res,l,r) (*(res) = (l) * (r), FFEBAD)
  #define ffetarget_multiply_integer3(res,l,r) (*(res) = (l) * (r), FFEBAD)
  #define ffetarget_multiply_integer4(res,l,r) (*(res) = (l) * (r), FFEBAD)
- #ifdef REAL_ARITHMETIC
  #define ffetarget_multiply_real1(res,l,r) \
    ({ REAL_VALUE_TYPE lr, rr, resr; \
       lr = ffetarget_cvt_r1_to_rv_ ((l)); \
--- 1350,1365 ----
*************** void *ffetarget_memcpy_ (void *dst, void
*** 1614,1624 ****
       REAL_ARITHMETIC (resr, MULT_EXPR, lr, rr); \
       ffetarget_cvt_rv_to_r2_ (resr, &((res)->v[0])); \
       FFEBAD; })
- #else
- #define ffetarget_multiply_real1(res,l,r) (*(res) = (l) * (r), FFEBAD)
- #define ffetarget_multiply_real2(res,l,r) (*(res) = (l) * (r), FFEBAD)
- #endif
- #ifdef REAL_ARITHMETIC
  #define ffetarget_ne_complex1(res,l,r) \
    ({ REAL_VALUE_TYPE lr, li, rr, ri; \
       lr = ffetarget_cvt_r1_to_rv_ ((l).real); \
--- 1374,1379 ----
*************** void *ffetarget_memcpy_ (void *dst, void
*** 1637,1650 ****
       *(res) = (REAL_VALUES_EQUAL (lr, rr) && REAL_VALUES_EQUAL (li, ri)) \
         ? FALSE : TRUE; \
       FFEBAD; })
- #else
- #define ffetarget_ne_complex1(res,l,r) \
-   (*(res) = (((l).real != (r).real) || ((l).imaginary != (r).imaginary))  \
-    ? TRUE : FALSE, FFEBAD)
- #define ffetarget_ne_complex2(res,l,r) \
-   (*(res) = (((l).real != (r).real) || ((l).imaginary != (r).imaginary))  \
-    ? TRUE : FALSE, FFEBAD)
- #endif
  #define ffetarget_ne_integer1(res,l,r) \
    (*(res) = ((l) != (r)) ? TRUE : FALSE, FFEBAD)
  #define ffetarget_ne_integer2(res,l,r) \
--- 1392,1397 ----
*************** void *ffetarget_memcpy_ (void *dst, void
*** 1653,1659 ****
    (*(res) = ((l) != (r)) ? TRUE : FALSE, FFEBAD)
  #define ffetarget_ne_integer4(res,l,r) \
    (*(res) = ((l) != (r)) ? TRUE : FALSE, FFEBAD)
- #ifdef REAL_ARITHMETIC
  #define ffetarget_ne_real1(res,l,r) \
    ({ REAL_VALUE_TYPE lr, rr; \
       lr = ffetarget_cvt_r1_to_rv_ ((l)); \
--- 1400,1405 ----
*************** void *ffetarget_memcpy_ (void *dst, void
*** 1666,1677 ****
       rr = ffetarget_cvt_r2_to_rv_ (&((r).v[0])); \
       *(res) = REAL_VALUES_EQUAL (lr, rr) ? FALSE : TRUE; \
       FFEBAD; })
- #else
- #define ffetarget_ne_real1(res,l,r) \
-   (*(res) = ((l) != (r)) ? TRUE : FALSE, FFEBAD)
- #define ffetarget_ne_real2(res,l,r) \
-   (*(res) = ((l) != (r)) ? TRUE : FALSE, FFEBAD)
- #endif
  #define ffetarget_neqv_integer1(res,l,r) (*(res) = (l) ^ (r), FFEBAD)
  #define ffetarget_neqv_integer2(res,l,r) (*(res) = (l) ^ (r), FFEBAD)
  #define ffetarget_neqv_integer3(res,l,r) (*(res) = (l) ^ (r), FFEBAD)
--- 1412,1417 ----
*************** void *ffetarget_memcpy_ (void *dst, void
*** 1727,1777 ****
    fprintf ((f), "%" ffetargetLogical4_f "d", (v))
  #define ffetarget_print_octalmil(f,v) ffetarget_print_octal(f,v)
  #define ffetarget_print_octalvxt(f,v) ffetarget_print_octal(f,v)
- #ifdef REAL_ARITHMETIC
  #define ffetarget_print_real1(f,l) \
    ({ REAL_VALUE_TYPE lr; \
       lr = ffetarget_cvt_r1_to_rv_ ((l)); \
!      REAL_VALUE_TO_DECIMAL (lr, bad_fmt_val??, ffetarget_string_); \
       fputs (ffetarget_string_, (f)); \
     })
  #define ffetarget_print_real2(f,l) \
    ({ REAL_VALUE_TYPE lr; \
       lr = ffetarget_cvt_r2_to_rv_ (&((l).v[0])); \
!      REAL_VALUE_TO_DECIMAL (lr, bad_fmt_val??, ffetarget_string_); \
       fputs (ffetarget_string_, (f)); \
     })
- #else
- #define ffetarget_print_real1(f,v) \
-   fprintf ((f), "%" ffetargetReal1_f "g", (v))
- #define ffetarget_print_real2(f,v) \
-   fprintf ((f), "%" ffetargetReal2_f "g", (v))
- #endif
- #ifdef REAL_ARITHMETIC
  #define ffetarget_real1_one(res) ffetarget_cvt_rv_to_r1_ (dconst1, *(res))
  #define ffetarget_real2_one(res) ffetarget_cvt_rv_to_r2_ (dconst1, &((res)->v[0]))
- #else
- #define ffetarget_real1_one(res) (*(res) = (float) 1.)
- #define ffetarget_real2_one(res) (*(res) = 1.)
- #endif
- #ifdef REAL_ARITHMETIC
  #define ffetarget_real1_two(res) ffetarget_cvt_rv_to_r1_ (dconst2, *(res))
  #define ffetarget_real2_two(res) ffetarget_cvt_rv_to_r2_ (dconst2, &((res)->v[0]))
- #else
- #define ffetarget_real1_two(res) (*(res) = (float) 2.)
- #define ffetarget_real2_two(res) (*(res) = 2.)
- #endif
- #ifdef REAL_ARITHMETIC
  #define ffetarget_real1_zero(res) ffetarget_cvt_rv_to_r1_ (dconst0, *(res))
  #define ffetarget_real2_zero(res) ffetarget_cvt_rv_to_r2_ (dconst0, &((res)->v[0]))
- #else
- #define ffetarget_real1_zero(res) (*(res) = (float) 0.)
- #define ffetarget_real2_zero(res) (*(res) = 0.)
- #endif
  #define ffetarget_size_typeless_binary(t) ((ffetarget_num_digits_(t) + 7) / 8)
  #define ffetarget_size_typeless_octal(t) \
    ((ffetarget_num_digits_(t) * 3 + 7) / 8)
  #define ffetarget_size_typeless_hex(t) ((ffetarget_num_digits_(t) + 1) / 2)
- #ifdef REAL_ARITHMETIC
  #define ffetarget_subtract_complex1(res,l,r) \
    ({ REAL_VALUE_TYPE lr, li, rr, ri, resr, resi; \
       lr = ffetarget_cvt_r1_to_rv_ ((l).real); \
--- 1467,1496 ----
    fprintf ((f), "%" ffetargetLogical4_f "d", (v))
  #define ffetarget_print_octalmil(f,v) ffetarget_print_octal(f,v)
  #define ffetarget_print_octalvxt(f,v) ffetarget_print_octal(f,v)
  #define ffetarget_print_real1(f,l) \
    ({ REAL_VALUE_TYPE lr; \
       lr = ffetarget_cvt_r1_to_rv_ ((l)); \
!      real_to_decimal (ffetarget_string_, &lr \
! 			 sizeof(ffetarget_string_), 0, 1); \
       fputs (ffetarget_string_, (f)); \
     })
  #define ffetarget_print_real2(f,l) \
    ({ REAL_VALUE_TYPE lr; \
       lr = ffetarget_cvt_r2_to_rv_ (&((l).v[0])); \
!      real_to_decimal (ffetarget_string_, &lr, \
! 			 sizeof(ffetarget_string_), 0, 1); \
       fputs (ffetarget_string_, (f)); \
     })
  #define ffetarget_real1_one(res) ffetarget_cvt_rv_to_r1_ (dconst1, *(res))
  #define ffetarget_real2_one(res) ffetarget_cvt_rv_to_r2_ (dconst1, &((res)->v[0]))
  #define ffetarget_real1_two(res) ffetarget_cvt_rv_to_r1_ (dconst2, *(res))
  #define ffetarget_real2_two(res) ffetarget_cvt_rv_to_r2_ (dconst2, &((res)->v[0]))
  #define ffetarget_real1_zero(res) ffetarget_cvt_rv_to_r1_ (dconst0, *(res))
  #define ffetarget_real2_zero(res) ffetarget_cvt_rv_to_r2_ (dconst0, &((res)->v[0]))
  #define ffetarget_size_typeless_binary(t) ((ffetarget_num_digits_(t) + 7) / 8)
  #define ffetarget_size_typeless_octal(t) \
    ((ffetarget_num_digits_(t) * 3 + 7) / 8)
  #define ffetarget_size_typeless_hex(t) ((ffetarget_num_digits_(t) + 1) / 2)
  #define ffetarget_subtract_complex1(res,l,r) \
    ({ REAL_VALUE_TYPE lr, li, rr, ri, resr, resi; \
       lr = ffetarget_cvt_r1_to_rv_ ((l).real); \
*************** void *ffetarget_memcpy_ (void *dst, void
*** 1794,1812 ****
       ffetarget_cvt_rv_to_r2_ (resr, &((res)->real.v[0])); \
       ffetarget_cvt_rv_to_r2_ (resi, &((res)->imaginary.v[0])); \
       FFEBAD; })
- #else
- #define ffetarget_subtract_complex1(res,l,r) \
-   ((res)->real = (l).real - (r).real, \
-    (res)->imaginary = (l).imaginary - (r).imaginary, FFEBAD)
- #define ffetarget_subtract_complex2(res,l,r) \
-   ((res)->real = (l).real - (r).real, \
-    (res)->imaginary = (l).imaginary - (r).imaginary, FFEBAD)
- #endif
  #define ffetarget_subtract_integer1(res,l,r) (*(res) = (l) - (r), FFEBAD)
  #define ffetarget_subtract_integer2(res,l,r) (*(res) = (l) - (r), FFEBAD)
  #define ffetarget_subtract_integer3(res,l,r) (*(res) = (l) - (r), FFEBAD)
  #define ffetarget_subtract_integer4(res,l,r) (*(res) = (l) - (r), FFEBAD)
- #ifdef REAL_ARITHMETIC
  #define ffetarget_subtract_real1(res,l,r) \
    ({ REAL_VALUE_TYPE lr, rr, resr; \
       lr = ffetarget_cvt_r1_to_rv_ ((l)); \
--- 1513,1522 ----
*************** void *ffetarget_memcpy_ (void *dst, void
*** 1821,1830 ****
       REAL_ARITHMETIC (resr, MINUS_EXPR, lr, rr); \
       ffetarget_cvt_rv_to_r2_ (resr, &((res)->v[0])); \
       FFEBAD; })
- #else
- #define ffetarget_subtract_real1(res,l,r) (*(res) = (l) - (r), FFEBAD)
- #define ffetarget_subtract_real2(res,l,r) (*(res) = (l) - (r), FFEBAD)
- #endif
  #define ffetarget_terminate_0()
  #define ffetarget_terminate_1()
  #define ffetarget_terminate_2()
--- 1531,1536 ----
*************** void *ffetarget_memcpy_ (void *dst, void
*** 1832,1838 ****
  #define ffetarget_terminate_4()
  #define ffetarget_text_character1(c) ((c).text)
  #define ffetarget_text_characterdefault ffetarget_text_character1
- #ifdef REAL_ARITHMETIC
  #define ffetarget_uminus_complex1(res,l) \
    ({ REAL_VALUE_TYPE lr, li, resr, resi; \
       lr = ffetarget_cvt_r1_to_rv_ ((l).real); \
--- 1538,1543 ----
*************** void *ffetarget_memcpy_ (void *dst, void
*** 1851,1867 ****
       ffetarget_cvt_rv_to_r2_ (resr, &((res)->real.v[0])); \
       ffetarget_cvt_rv_to_r2_ (resi, &((res)->imaginary.v[0])); \
       FFEBAD; })
- #else
- #define ffetarget_uminus_complex1(res,l) \
-   ((res)->real = -(l).real, (res)->imaginary = -(l).imaginary, FFEBAD)
- #define ffetarget_uminus_complex2(res,l) \
-   ((res)->real = -(l).real, (res)->imaginary = -(l).imaginary, FFEBAD)
- #endif
  #define ffetarget_uminus_integer1(res,l) (*(res) = -(l), FFEBAD)
  #define ffetarget_uminus_integer2(res,l) (*(res) = -(l), FFEBAD)
  #define ffetarget_uminus_integer3(res,l) (*(res) = -(l), FFEBAD)
  #define ffetarget_uminus_integer4(res,l) (*(res) = -(l), FFEBAD)
- #ifdef REAL_ARITHMETIC
  #define ffetarget_uminus_real1(res,l) \
    ({ REAL_VALUE_TYPE lr, resr; \
       lr = ffetarget_cvt_r1_to_rv_ ((l)); \
--- 1556,1565 ----
*************** void *ffetarget_memcpy_ (void *dst, void
*** 1874,1890 ****
       resr = REAL_VALUE_NEGATE (lr); \
       ffetarget_cvt_rv_to_r2_ (resr, &((res)->v[0])); \
       FFEBAD; })
- #else
- #define ffetarget_uminus_real1(res,l) (*(res) = -(l), FFEBAD)
- #define ffetarget_uminus_real2(res,l) (*(res) = -(l), FFEBAD)
- #endif
- #ifdef REAL_ARITHMETIC
  #define ffetarget_value_real1(lr) ffetarget_cvt_r1_to_rv_ ((lr))
  #define ffetarget_value_real2(lr) ffetarget_cvt_r2_to_rv_ (&((lr).v[0]))
- #else
- #define ffetarget_value_real1
- #define ffetarget_value_real2
- #endif
  #define ffetarget_xor_integer1(res,l,r) (*(res) = (l) ^ (r), FFEBAD)
  #define ffetarget_xor_integer2(res,l,r) (*(res) = (l) ^ (r), FFEBAD)
  #define ffetarget_xor_integer3(res,l,r) (*(res) = (l) ^ (r), FFEBAD)
--- 1572,1579 ----
diff -Nrc3pad gcc-3.2.3/gcc/f/top.c gcc-3.3/gcc/f/top.c
*** gcc-3.2.3/gcc/f/top.c	2001-11-09 17:50:06.000000000 +0000
--- gcc-3.3/gcc/f/top.c	2002-02-27 18:47:56.000000000 +0000
*************** the Free Software Foundation, 59 Temple 
*** 58,64 ****
  
  /* Externals defined here. */
  
- int flag_traditional;		/* Shouldn't need this (C front end only)! */
  bool ffe_is_do_internal_checks_ = FALSE;
  bool ffe_is_90_ = FFETARGET_defaultIS_90;
  bool ffe_is_automatic_ = FFETARGET_defaultIS_AUTOMATIC;
--- 58,63 ----
diff -Nrc3pad gcc-3.2.3/gcc/f/version.c gcc-3.3/gcc/f/version.c
*** gcc-3.2.3/gcc/f/version.c	2003-04-22 06:16:09.000000000 +0000
--- gcc-3.3/gcc/f/version.c	1970-01-01 00:00:00.000000000 +0000
***************
*** 1,4 ****
- #include "ansidecl.h"
- #include "f/version.h"
- 
- const char *const ffe_version_string = "3.2.3 20030422 (release)";
--- 0 ----
diff -Nrc3pad gcc-3.2.3/gcc/f/version.h gcc-3.3/gcc/f/version.h
*** gcc-3.2.3/gcc/f/version.h	2001-09-12 16:52:42.000000000 +0000
--- gcc-3.3/gcc/f/version.h	1970-01-01 00:00:00.000000000 +0000
***************
*** 1,6 ****
- #ifndef GCC_F_VERSION_H
- #define GCC_F_VERSION_H
- 
- extern const char *const ffe_version_string;
- 
- #endif /* ! GCC_F_VERSION_H */
--- 0 ----
diff -Nrc3pad gcc-3.2.3/gcc/f/where.c gcc-3.3/gcc/f/where.c
*** gcc-3.2.3/gcc/f/where.c	2000-06-21 20:11:14.000000000 +0000
--- gcc-3.3/gcc/f/where.c	2002-08-22 02:20:42.000000000 +0000
***************
*** 1,5 ****
  /* where.c -- Implementation File (module.c template V1.0)
!    Copyright (C) 1995 Free Software Foundation, Inc.
     Contributed by James Craig Burley.
  
  This file is part of GNU Fortran.
--- 1,5 ----
  /* where.c -- Implementation File (module.c template V1.0)
!    Copyright (C) 1995, 2002 Free Software Foundation, Inc.
     Contributed by James Craig Burley.
  
  This file is part of GNU Fortran.
*************** typedef struct _ffewhere_ll_ *ffewhereLL
*** 53,59 ****
  
  /* Internal structure definitions. */
  
! struct _ffewhere_ll_
    {
      ffewhereLL_ next;
      ffewhereLL_ previous;
--- 53,59 ----
  
  /* Internal structure definitions. */
  
! struct _ffewhere_ll_ GTY (())
    {
      ffewhereLL_ next;
      ffewhereLL_ previous;
*************** struct _ffewhere_ll_
*** 62,68 ****
      ffewhereLineNumber offset;	/* User-desired offset (usually 1). */
    };
  
! struct _ffewhere_root_ll_
    {
      ffewhereLL_ first;
      ffewhereLL_ last;
--- 62,68 ----
      ffewhereLineNumber offset;	/* User-desired offset (usually 1). */
    };
  
! struct _ffewhere_root_ll_ GTY (())
    {
      ffewhereLL_ first;
      ffewhereLL_ last;
*************** struct _ffewhere_root_line_
*** 77,83 ****
  
  /* Static objects accessed by functions in this module. */
  
! static struct _ffewhere_root_ll_ ffewhere_root_ll_;
  static struct _ffewhere_root_line_ ffewhere_root_line_;
  
  /* Static functions (internal). */
--- 77,83 ----
  
  /* Static objects accessed by functions in this module. */
  
! static GTY (()) struct _ffewhere_root_ll_ *ffewhere_root_ll_;
  static struct _ffewhere_root_line_ ffewhere_root_line_;
  
  /* Static functions (internal). */
*************** ffewhere_ll_lookup_ (ffewhereLineNumber 
*** 95,104 ****
    ffewhereLL_ ll;
  
    if (ln == 0)
!     return ffewhere_root_ll_.first;
  
!   for (ll = ffewhere_root_ll_.last;
!        ll != (ffewhereLL_) &ffewhere_root_ll_.first;
         ll = ll->previous)
      {
        if (ll->line_no <= ln)
--- 95,104 ----
    ffewhereLL_ ll;
  
    if (ln == 0)
!     return ffewhere_root_ll_->first;
  
!   for (ll = ffewhere_root_ll_->last;
!        ll != (ffewhereLL_) &ffewhere_root_ll_->first;
         ll = ll->previous)
      {
        if (ll->line_no <= ln)
*************** ffewhere_ll_lookup_ (ffewhereLineNumber 
*** 109,205 ****
    return NULL;
  }
  
- /* A somewhat evil way to prevent the garbage collector
-    from collecting 'file' structures.  */
- #define NUM_FFEWHERE_HEAD_FILES 31
- static struct ffewhere_ggc_tracker 
- {
-   struct ffewhere_ggc_tracker *next;
-   ffewhereFile files[NUM_FFEWHERE_HEAD_FILES];
- } *ffewhere_head = NULL;
- 
- static void 
- mark_ffewhere_head (void *arg)
- {
-   struct ffewhere_ggc_tracker *head;
-   int i;
-   
-   for (head = * (struct ffewhere_ggc_tracker **) arg;
-        head != NULL;
-        head = head->next)
-   {
-     ggc_mark (head);
-     for (i = 0; i < NUM_FFEWHERE_HEAD_FILES; i++)
-       ggc_mark (head->files[i]);
-   }
- }
- 
- 
- /* Kill file object.
- 
-    Note that this object must not have been passed in a call
-    to any other ffewhere function except ffewhere_file_name and
-    ffewhere_file_namelen.  */
- 
- void
- ffewhere_file_kill (ffewhereFile wf)
- {
-   struct ffewhere_ggc_tracker *head;
-   int i;
-   
-   for (head = ffewhere_head; head != NULL; head = head->next)
-     for (i = 0; i < NUM_FFEWHERE_HEAD_FILES; i++)
-       if (head->files[i] == wf)
- 	{
- 	  head->files[i] = NULL;
- 	  return;
- 	}
-   /* Called on a file that has already been deallocated... */
-   abort();
- }
- 
  /* Create file object.  */
  
  ffewhereFile
  ffewhere_file_new (const char *name, size_t length)
  {
    ffewhereFile wf;
!   int filepos;
!  
!   wf = ggc_alloc (offsetof (struct _ffewhere_file_, text)
! 		  + length + 1);
    wf->length = length;
    memcpy (&wf->text[0], name, length);
    wf->text[length] = '\0';
  
-   if (ffewhere_head == NULL)
-     {
-       ggc_add_root (&ffewhere_head, 1, sizeof ffewhere_head,
- 		    mark_ffewhere_head);
-       filepos = NUM_FFEWHERE_HEAD_FILES;
-     }
-   else
-     {
-       for (filepos = 0; filepos < NUM_FFEWHERE_HEAD_FILES; filepos++)
- 	if (ffewhere_head->files[filepos] == NULL)
- 	  {
- 	    ffewhere_head->files[filepos] = wf;
- 	    break;
- 	  }
-     }
-   if (filepos == NUM_FFEWHERE_HEAD_FILES)
-     {
-       /* Need to allocate a new block.  */
-       struct ffewhere_ggc_tracker *old_head = ffewhere_head;
-       int i;
-       
-       ffewhere_head = ggc_alloc (sizeof (*ffewhere_head));
-       ffewhere_head->next = old_head;
-       ffewhere_head->files[0] = wf;
-       for (i = 1; i < NUM_FFEWHERE_HEAD_FILES; i++)
- 	ffewhere_head->files[i] = NULL;
-     }
- 
    return wf;
  }
  
--- 109,125 ----
    return NULL;
  }
  
  /* Create file object.  */
  
  ffewhereFile
  ffewhere_file_new (const char *name, size_t length)
  {
    ffewhereFile wf;
!   wf = ggc_alloc (offsetof (struct _ffewhere_file_, text) + length + 1);
    wf->length = length;
    memcpy (&wf->text[0], name, length);
    wf->text[length] = '\0';
  
    return wf;
  }
  
*************** void
*** 211,220 ****
  ffewhere_file_set (ffewhereFile wf, bool have_num, ffewhereLineNumber ln)
  {
    ffewhereLL_ ll;
! 
!   ll = malloc_new_kp (ffe_pool_file (), "ffewhereLL_", sizeof (*ll));
!   ll->next = (ffewhereLL_) &ffewhere_root_ll_.first;
!   ll->previous = ffewhere_root_ll_.last;
    ll->next->previous = ll;
    ll->previous->next = ll;
    if (wf == NULL)
--- 131,139 ----
  ffewhere_file_set (ffewhereFile wf, bool have_num, ffewhereLineNumber ln)
  {
    ffewhereLL_ ll;
!   ll = ggc_alloc (sizeof (*ll));
!   ll->next = (ffewhereLL_) &ffewhere_root_ll_->first;
!   ll->previous = ffewhere_root_ll_->last;
    ll->next->previous = ll;
    ll->previous->next = ll;
    if (wf == NULL)
*************** ffewhere_init_1 ()
*** 248,255 ****
    = (ffewhereLine) &ffewhere_root_line_.first;
    ffewhere_root_line_.none = 0;
  
!   ffewhere_root_ll_.first = ffewhere_root_ll_.last
!     = (ffewhereLL_) &ffewhere_root_ll_.first;
  }
  
  /* Return the textual content of the line.  */
--- 167,178 ----
    = (ffewhereLine) &ffewhere_root_line_.first;
    ffewhere_root_line_.none = 0;
  
!   /* The sentinel is (must be) GGC-allocated.  It is accessed as a
!      struct _ffewhere_ll_/ffewhereLL_ though its type contains just the
!      first two fields (layout-wise).  */
!   ffewhere_root_ll_ = ggc_alloc_cleared (sizeof (struct _ffewhere_ll_));
!   ffewhere_root_ll_->first = ffewhere_root_ll_->last
!     = (ffewhereLL_) &ffewhere_root_ll_->first;
  }
  
  /* Return the textual content of the line.  */
*************** ffewhere_track (ffewhereLine *wl, ffewhe
*** 500,521 ****
    else
      {
        wt[i * 2 - 2] = lo;
!       if (cn > FFEWHERE_indexUNKNOWN)
! 	{
! 	  wt[i * 2 - 1] = FFEWHERE_indexUNKNOWN;
! 	  ffewhere_line_kill (*wl);
! 	  ffewhere_column_kill (*wc);
! 	  *wl = ffewhere_line_unknown ();
! 	  *wc = ffewhere_column_unknown ();
! 	}
!       else
! 	{
! 	  wt[i * 2 - 1] = cn - 1;
! 	  ffewhere_line_kill (*wl);
! 	  ffewhere_column_kill (*wc);
! 	  *wl = ffewhere_line_use (ffewhere_line_new (ln));
! 	  *wc = ffewhere_column_use (ffewhere_column_new (cn));
! 	}
      }
  }
  
--- 423,433 ----
    else
      {
        wt[i * 2 - 2] = lo;
!       wt[i * 2 - 1] = cn - 1;
!       ffewhere_line_kill (*wl);
!       ffewhere_column_kill (*wc);
!       *wl = ffewhere_line_use (ffewhere_line_new (ln));
!       *wc = ffewhere_column_use (ffewhere_column_new (cn));
      }
  }
  
*************** ffewhere_track_kill (ffewhereLine wrl, f
*** 604,606 ****
--- 516,520 ----
  	}
      }
  }
+ 
+ #include "gt-f-where.h"
diff -Nrc3pad gcc-3.2.3/gcc/f/where.h gcc-3.3/gcc/f/where.h
*** gcc-3.2.3/gcc/f/where.h	2001-05-26 01:31:46.000000000 +0000
--- gcc-3.3/gcc/f/where.h	2002-08-22 02:20:42.000000000 +0000
***************
*** 1,5 ****
  /* where.h -- Public #include File (module.h template V1.0)
!    Copyright (C) 1995 Free Software Foundation, Inc.
     Contributed by James Craig Burley.
  
  This file is part of GNU Fortran.
--- 1,5 ----
  /* where.h -- Public #include File (module.h template V1.0)
!    Copyright (C) 1995, 2002 Free Software Foundation, Inc.
     Contributed by James Craig Burley.
  
  This file is part of GNU Fortran.
*************** typedef unsigned int ffewhereUses_;
*** 61,72 ****
  
  /* Include files needed by this one. */
  
- #include "glimits.h"
  #include "top.h"
  
  /* Structure definitions. */
  
! struct _ffewhere_file_
    {
      size_t length;
      char text[1];
--- 61,71 ----
  
  /* Include files needed by this one. */
  
  #include "top.h"
  
  /* Structure definitions. */
  
! struct _ffewhere_file_ GTY (())
    {
      size_t length;
      char text[1];
*************** extern struct _ffewhere_line_ ffewhere_u
*** 88,94 ****
  
  /* Declare functions with prototypes. */
  
- void ffewhere_file_kill (ffewhereFile wf);
  ffewhereFile ffewhere_file_new (const char *name, size_t length);
  void ffewhere_file_set (ffewhereFile wf, bool have_num, ffewhereLineNumber ln);
  void ffewhere_init_1 (void);
--- 87,92 ----
diff -Nrc3pad gcc-3.2.3/libf2c/aclocal.m4 gcc-3.3/libf2c/aclocal.m4
*** gcc-3.2.3/libf2c/aclocal.m4	2003-01-28 01:44:05.000000000 +0000
--- gcc-3.3/libf2c/aclocal.m4	2003-01-28 01:45:12.000000000 +0000
***************
*** 1,4 ****
! dnl Copyright (C) 1994, 1995-8, 1999, 2001 Free Software Foundation, Inc.
  dnl This file is free software; the Free Software Foundation
  dnl gives unlimited permission to copy and/or distribute it,
  dnl with or without modifications, as long as this notice is preserved.
--- 1,4 ----
! dnl Copyright (C) 1994, 1995-8, 1999, 2001, 2002 Free Software Foundation, Inc.
  dnl This file is free software; the Free Software Foundation
  dnl gives unlimited permission to copy and/or distribute it,
  dnl with or without modifications, as long as this notice is preserved.
*************** AC_DEFUN(GLIBCPP_CONFIGURE, [
*** 54,60 ****
  # These need to be absolute paths, yet at the same time need to
  # canonicalize only relative paths, because then amd will not unmount
  # drives. Thus the use of PWDCMD: set it to 'pawd' or 'amq -w' if using amd.
! glibcpp_builddir=`pwd`
  case $srcdir in
  [\\/$]* | ?:[\\/]*) glibcpp_srcdir=${srcdir} ;;
  *) glibcpp_srcdir=`cd "$srcdir" && ${PWDCMD-pwd} || echo "$srcdir"` ;;
--- 54,60 ----
  # These need to be absolute paths, yet at the same time need to
  # canonicalize only relative paths, because then amd will not unmount
  # drives. Thus the use of PWDCMD: set it to 'pawd' or 'amq -w' if using amd.
! glibcpp_builddir=`${PWDCMD-pwd}`
  case $srcdir in
  [\\/$]* | ?:[\\/]*) glibcpp_srcdir=${srcdir} ;;
  *) glibcpp_srcdir=`cd "$srcdir" && ${PWDCMD-pwd} || echo "$srcdir"` ;;
diff -Nrc3pad gcc-3.2.3/libf2c/ChangeLog gcc-3.3/libf2c/ChangeLog
*** gcc-3.2.3/libf2c/ChangeLog	2003-04-22 06:15:25.000000000 +0000
--- gcc-3.3/libf2c/ChangeLog	2003-05-14 00:10:45.000000000 +0000
***************
*** 1,16 ****
! 2003-04-22  Release Manager
  
! 	* GCC 3.2.3 Released.
  
! 2003-02-05  Release Manager
  
! 	* GCC 3.2.2 Released.
  
! 2003-01-28  Christian Cornelssen  <ccorn@cs.tu-berlin.de>
  
! 	* Makefile.in (FLAGS_TO_PASS): Also pass DESTDIR.
! 	(install, uninstall): Prepend $(DESTDIR) to destination
! 	paths in all (un)installation commands.
  
  2003-01-27  Alexandre Oliva  <aoliva@redhat.com>
  
--- 1,39 ----
! 2003-05-13  Release Manager
  
! 	* GCC 3.3 Released.
  
! 2003-05-13  Release Manager
  
! 	* GCC 3.3 Released.
  
! 2003-05-13  Release Manager
  
! 	* GCC 3.3 Released.
! 
! 2003-04-23  Loren J. Rittle  <ljrittle@acm.org>
! 
! 	* libI77/configure.in (_XOPEN_SOURCE): Bump to 600.
! 	* libI77/configure: Regenerate. 
! 	* libU77/configure.in (_XOPEN_SOURCE): Bump to 600.
! 	* libU77/configure: Regenerate. 
! 
! 2003-04-11  Bud Davis <bdavis9659@comcast.net>
! 
! 	PR Fortran/1832
! 	* libf2c/libI77/iio.c (z_putc): Check for overflowing length
! 	of output string.
! 
! 2003-03-24  Bud Davis  <bdavis9659@comcast.net>
! 
! 	PR fortran/10197
! 	* libI77/open.c (f_open): A DIRECT ACCESS file is
! 	UNFORMATTED by default.
! 
! 2003-02-20  Alexandre Oliva  <aoliva@redhat.com>
! 
! 	* configure.in: Propagate ORIGINAL_LD_FOR_MULTILIBS to
! 	config.status.
! 	* configure: Rebuilt.
  
  2003-01-27  Alexandre Oliva  <aoliva@redhat.com>
  
***************
*** 20,48 ****
  	version_specific_libs is enabled.
  	* configure: Rebuilt.
  
! 2002-11-19  Release Manager
  
! 	* GCC 3.2.1 Released.
  
! 2002-11-19  Release Manager
  
! 	* GCC 3.2.1 Released.
  
! 2002-11-18  Release Manager
  
! 	* GCC 3.2.1 Released.
  
! Mon Oct  7 00:32:38 2002  Kaveh R. Ghazi  <ghazi@caip.rutgers.edu>
  
  	* Makefile.in (all): Fix multilib parallel build.
  
! 2002-08-14  Release Manager
  
! 	* GCC 3.2 Released.
  
! 2002-07-25  Release Manager
  
! 	* GCC 3.1.1 Released.
  
  2002-06-25  DJ Delorie  <dj@redhat.com>
  
--- 43,101 ----
  	version_specific_libs is enabled.
  	* configure: Rebuilt.
  
! 2003-01-26  Christian Cornelssen  <ccorn@cs.tu-berlin.de>
  
! 	* Makefile.in (FLAGS_TO_PASS): Also pass DESTDIR.
! 	(install, uninstall): Prepend $(DESTDIR) to destination
! 	paths in all (un)installation commands.
  
! 2002-11-19  Toon Moene  <toon@moene.indiv.nluug.nl>
  
! 	PR fortran/8587
! 	* libF77/pow_zz.c: Handle (0.0, 0.0) ** power.
  
! 2002-10-18  Krister Walfridsson  <cato@df.lth.se>
  
! 	* libU77/configure.in (_XOPEN_SOURCE, _XOPEN_SOURCE_EXTENDED,
! 	__EXTENSIONS__, _FILE_OFFSET_BITS): Check that _XOPEN_SOURCE 500L
! 	may be defined before defining these.
! 	* libU77/configure: Regenerate.
! 	* libI77/configure.in (_XOPEN_SOURCE, _XOPEN_SOURCE_EXTENDED,
! 	__EXTENSIONS__, _FILE_OFFSET_BITS): Check that _XOPEN_SOURCE 500L
! 	may be defined before defining these.
! 	* libI77/configure: Regenerate.
  
! 2002-09-23  Zack Weinberg  <zack@codesourcery.com>
! 
! 	* libF77/Version.c: Rename junk to __LIBF77_VERSION__.  Add
! 	external decls for __LIBI77_VERSION__ and __LIBU77_VERSION__.
! 	Delete __G77_LIBF77_VERSION__
! 	(g77__fvers__): Print all three __LIB*77_VERSION__ strings,
! 	and __VERSION__ if we have it; nothing else.
! 
! 	* libI77/Version.c: Provide only __LIBI77_VERSION__ (formerly junk).
! 	* libU77/Version.c: Provide only __LIBU77_VERSION__ (formerly junk).
! 
! Sun Sep 22 23:43:37 2002  Kaveh R. Ghazi  <ghazi@caip.rutgers.edu>
  
  	* Makefile.in (all): Fix multilib parallel build.
  
! 2002-09-14  Tim Prince  <tprince@computer.org>
  
! 	PR libf2c/7384
! 	* libU77/datetime_.c: Use GetLocalTime on MS-Windows.
  
! 2002-08-31  Toon Moene  <toon@moene.indiv.nluug.nl>
  
! 	PR fortran/6367
! 	* libI77/rsne.c (x_rsne): Use local variable no2 to count further
! 	list elements to read.
! 
! 2002-07-10  Toon Moene  <toon@moene.indiv.nluug.nl>
! 
! 	* libI77/open.c (f_open): Do not indicate unformatted file
! 	if record length is given without a FORMATTED/UNFORMATTED
! 	specification.
  
  2002-06-25  DJ Delorie  <dj@redhat.com>
  
*************** Mon Oct  7 00:32:38 2002  Kaveh R. Ghazi
*** 51,63 ****
  	* configure.in: Call it before AC_CANONICAL_SYSTEM.
  	* configure: Regenerate.
  
! 2002-05-14  Release Manager
  
! 	* GCC 3.1 Released.
  
! 2002-05-14  Release Manager
  
! 	* GCC 3.1 Released.
  
  2002-05-08  Alexandre Oliva  <aoliva@redhat.com>
  
--- 104,273 ----
  	* configure.in: Call it before AC_CANONICAL_SYSTEM.
  	* configure: Regenerate.
  
! Wed Jun  5 15:05:41 2002  Kaveh R. Ghazi  <ghazi@caip.rutgers.edu>
  
! 	* f2cext.c (alarm_): Mark parameter(s) with attribute `unused'.
! 	* libF77/h_len.c (h_len): Likewise.
! 	* libF77/i_len.c (i_len): Likewise.
! 	* libI77/rsli.c (i_ungetc): Likewise.
! 	* libU77/date_.c (G77_date_y2kbuggy_0): Likewise.
! 	* libU77/fputc_.c (G77_fputc_0): Likewise.
! 	* libU77/vxtidate_.c (G77_vxtidate_y2kbuggy_0): Likewise.
! 	* libU77/vxttime_.c (G77_vxttime_0): Likewise.
  
! Mon Jun  3 22:24:48 2002  Kaveh R. Ghazi  <ghazi@caip.rutgers.edu>
  
! 	* libF77/main.c (f_setarg, f_setsig): Prototype.
! 	* libI77/lread.c (quad_read): Delete.
! 	* libI77/uio.c: Include config.h.
! 	* libI77/wref.c (wrt_E): Cast isdigit arg to unsigned char.
! 	* libU77/dtime_.c (clk_tck): Move to the scope where it is used.
! 	* libU77/etime_.c (clk_tck): Likewise.
! 
! Mon Jun  3 22:23:03 2002  Kaveh R. Ghazi  <ghazi@caip.rutgers.edu>
! 
! 	* libF77/lbitbits.c (lbit_cshift): disambiguate expressions
! 	with parentheses.
! 	* libF77/qbitbits.c (qbit_cshift): Likewise.
! 	* libI77/inquire.c (f_inqu): Likewise.
! 	* libI77/rdfmt.c (rd_Z): Likewise.
! 	* libI77/rsne.c (x_rsne): Likewise.
! 
! Mon Jun  3 22:21:23 2002  Kaveh R. Ghazi  <ghazi@caip.rutgers.edu>
! 
! 	* Makefile.in (s-libe77): Add WARN_CFLAGS.
! 
! Sun Jun  2 10:32:35 2002  Kaveh R. Ghazi  <ghazi@caip.rutgers.edu>
! 
! 	* libI77/dfe.c (s_rdfe, s_wdfe): Wrap parentheses around
! 	assignment used as truth value.
! 	* libI77/due.c (s_rdue, s_wdue): Likewise.
! 	* libI77/endfile.c (f_end): Likewise.
! 	* libI77/iio.c (s_rsfi, s_wsfi): Likewise.
! 	* libI77/lread.c (ERR, l_C, nmL_getc, s_rsle): Likewise.
! 	* libI77/lwrite.c (l_g, l_put): Likewise.
! 	* libI77/open.c (f_open): Likewise.
! 	* libI77/rdfmt.c (rd_Z): Likewise.
! 	* libI77/rsfe.c (s_rsfe): Likewise.
! 	* libI77/rsne.c (hash, mk_hashtab, nl_init, getname, getdimen,
! 	x_rsne, s_rsne): Likewise.
! 	* libI77/sue.c (s_rsue, s_wsue): Likewise.
! 	* libI77/wref.c (wrt_E, wrt_F): Likewise.
! 	* libI77/wsfe.c (s_wsfe): Likewise.
! 	* libI77/wsle.c (s_wsle): Likewise.
! 	* libI77/wsne.c (s_wsne): Likewise.
! 
! Sun Jun  2 08:59:50 2002  Kaveh R. Ghazi  <ghazi@caip.rutgers.edu>
! 
! 	* libF77/main.c (main): Avoid implicit int.
! 	* libI77/dfe.c (y_rsk, y_getc, c_dfe): Likewise.
! 	* libI77/due.c (c_due): Likewise.
! 	* libI77/err.c (f__canseek, f__nowreading, f__nowwriting):
! 	Likewise.
! 	* libI77/fmt.c (op_gen, ne_d, e_d, pars_f, type_f, en_fio):
! 	Likewise.
! 	* libI77/iio.c (z_getc, z_rnew, c_si, z_wnew): Likewise.
! 	* libI77/lread.c (t_getc, c_le, l_read): Likewise.
! 	* libI77/lwrite.c (l_write): Likewise.
! 	* libI77/open.c (fk_open): Likewise.
! 	* libI77/rdfmt.c (rd_ed, rd_ned): Likewise.
! 	* libI77/rsfe.c (xrd_SL, x_getc, x_endp, x_rev): Likewise.
! 	* libI77/rsne.c (t_getc, x_rsne): Likewise.
! 	* libI77/sfe.c (c_sfe): Likewise.
! 	* libI77/sue.c (c_sue): Likewise.
! 	* libI77/uio.c (do_us): Likewise.
! 	* libI77/wref.c (wrt_E, wrt_F): Likewise.
! 	* libI77/wrtfmt.c (wrt_L, w_ed, w_ned): Likewise.
! 
! Sun Jun  2 08:58:05 2002  Kaveh R. Ghazi  <ghazi@caip.rutgers.edu>
! 
! 	* libI77/rdfmt.c (rd_I): Delete unused variable(s).
! 	* libU77/access_.c (G77_access_0): Likewise.
! 	* libU77/chdir_.c (G77_chdir_0): Likewise.
! 	* libU77/chmod_.c (G77_chmod_0): Likewise.
! 	* libU77/ctime_.c (G77_ctime_0): Likewise.
! 	* libU77/link_.c (G77_link_0): Likewise.
! 	* libU77/lstat_.c (G77_lstat_0): Likewise.
! 	* libU77/rename_.c (G77_rename_0): Likewise.
! 	* libU77/stat_.c (G77_stat_0): Likewise.
! 	* libU77/symlnk_.c (G77_symlnk_0): Likewise.
! 	* libU77/unlink_.c (G77_unlink_0): Likewise.
! 
! Sun Jun  2 08:55:20 2002  Kaveh R. Ghazi  <ghazi@caip.rutgers.edu>
! 
! 	* libI77/inquire.c (f_inqu): Avoid ambiguous else clauses.
! 	* libI77/lread.c (l_C, l_L): Likewise.
! 	* libI77/open.c (f_open): Likewise.
! 	* libI77/rsne.c (x_rsne): Likewise.
! 	* libI77/wref.c (wrt_F): Likewise.
! 
! Sun Jun  2 08:53:15 2002  Kaveh R. Ghazi  <ghazi@caip.rutgers.edu>
! 
! 	* libF77/getenv_.c (G77_getenv_0): Avoid signed/unsigned warning.
! 	* libF77/system_.c (G77_system_0): Likewise.
! 	* libI77/open.c (f_open): Likewise.
! 	* libI77/rdfmt.c (rd_Z): Likewise.
! 	* libI77/uio.c (do_us, do_ud): Likewise.
! 
! Sat Jun  1 08:33:14 2002  Kaveh R. Ghazi  <ghazi@caip.rutgers.edu>
! 
! 	* libF77/*: Fix formatting.
! 	* libI77/*: Likewise.
! 	* libU77/*: Likewise.
! 
! Fri May 31 21:56:30 2002  Kaveh R. Ghazi  <ghazi@caip.rutgers.edu>
! 
! 	* g2c.hin, libF77/d_cnjg.c, libF77/main.c, libF77/r_cnjg.c,
! 	libF77/s_cat.c, libF77/s_paus.c, libF77/s_rnge.c, libF77/setarg.c,
! 	libF77/setsig.c, libF77/signal1.h0, libI77/dfe.c, libI77/due.c,
! 	libI77/err.c, libI77/fio.h, libI77/fmt.c, libI77/iio.c,
! 	libI77/ilnw.c, libI77/lread.c, libI77/lwrite.c, libI77/rsfe.c,
! 	libI77/rsli.c, libI77/rsne.c, libI77/sfe.c, libI77/sue.c,
! 	libI77/util.c, libI77/wrtfmt.c, libI77/wsfe.c, libI77/wsle.c,
! 	libI77/xwsne.c, libU77/date_.c: Kill VOID, Void and Int.
! 
! Fri May 31 21:54:37 2002  Kaveh R. Ghazi  <ghazi@caip.rutgers.edu>
! 
! 	* libF77/F77_aloc.c, libF77/exit_.c, libF77/main.c,
! 	libF77/s_paus.c, libF77/s_stop.c, libF77/setarg.c,
! 	libF77/setsig.c, libF77/sig_die.c, libF77/signal1.h0,
! 	libI77/close.c, libI77/dolio.c, libI77/fio.h, libI77/fmt.h,
! 	libI77/lio.h: Delete checks on __cplusplus.
! 
! Fri May 31 21:50:01 2002  Kaveh R. Ghazi  <ghazi@caip.rutgers.edu>
! 
! 	* libF77/*: Delete KR_headers cruft.
! 	* libI77/*: Likewise.
! 	* libU77/*: Likewise.
! 
! Thu May 30 23:04:52 2002  Kaveh R. Ghazi  <ghazi@caip.rutgers.edu>
! 
! 	* Makefile.in (WARN_CFLAGS): New.
! 	(FLAGS_TO_PASS): Add WARN_CFLAGS.
! 	* libF77/Makefile.in (ALL_CFLAGS): Likewise.
! 	* libI77/Makefile.in (ALL_CFLAGS): Likewise.
! 	* libU77/Makefile.in (ALL_CFLAGS): Likewise.
! 
! 2002-05-30  H.J. Lu  (hjl@gnu.org)
! 
! 	* libI77/open.c (_XOPEN_SOURCE): Removed.
! 
! Mon May 20 13:03:54 2002  Kaveh R. Ghazi  <ghazi@caip.rutgers.edu>
! 
! 	* libF77/Makefile.in (SHELL): Set to @SHELL@.
! 	* libI77/Makefile.in (SHELL): Likewise.
! 	* libU77/Makefile.in (SHELL): Likewise.
! 
! 2002-05-20  Toon Moene  <toon@moene.indiv.nluug.nl>
! 
! 	* Makefile.in: Use @SHELL@, not /bin/sh for SHELL
! 	definition.
! 
! 2002-05-16  Rainer Orth  <ro@TechFak.Uni-Bielefeld.DE>
! 
! 	* Makefile.in: Allow for PWDCMD to override hardcoded pwd.
! 	* aclocal.m4: Likewise.
! 	* configure: Regenerate.
  
  2002-05-08  Alexandre Oliva  <aoliva@redhat.com>
  
*************** Mon Oct  7 00:32:38 2002  Kaveh R. Ghazi
*** 67,80 ****
  
  2002-05-02  Alexandre Oliva  <aoliva@redhat.com>
  
!         * Makefile.in: Fix for multilibbed natives.
  
  2002-04-15  Loren J. Rittle  <ljrittle@acm.org>
  
  	* aclocal.m4 (gcc_version_trigger): Use robust path construction.
  	* configure: Rebuilt.
  
! 2002-04-01  Phil Edwards  <pme@gcc.gnu.org>
  
  	* libF77/Version.c:  Fix misplaced leading blanks on first line.
  	* libI77/Version.c:  Likewise.
--- 277,294 ----
  
  2002-05-02  Alexandre Oliva  <aoliva@redhat.com>
  
! 	* Makefile.in: Fix for multilibbed natives.
  
  2002-04-15  Loren J. Rittle  <ljrittle@acm.org>
  
  	* aclocal.m4 (gcc_version_trigger): Use robust path construction.
  	* configure: Rebuilt.
  
! 2002-04-11  Toon Moene  <toon@moene.indiv.nluug.nl>
! 
! 	* libI77/lio.h: Treat INTEGER*1 as signed char.
! 
! 2002-03-06  Phil Edwards  <pme@gcc.gnu.org>
  
  	* libF77/Version.c:  Fix misplaced leading blanks on first line.
  	* libI77/Version.c:  Likewise.
*************** Mon Oct  7 00:32:38 2002  Kaveh R. Ghazi
*** 217,223 ****
  	of shared libf2c to 0:0:0.
  
  2001-09-29  Juergen Pfeifer  <juergen.pfeifer@gmx.net>
!             Toon Moene  <toon@moene.indiv.nluug.nl>
  
  	Make libf2c a shared library.
  
--- 431,437 ----
  	of shared libf2c to 0:0:0.
  
  2001-09-29  Juergen Pfeifer  <juergen.pfeifer@gmx.net>
! 	    Toon Moene  <toon@moene.indiv.nluug.nl>
  
  	Make libf2c a shared library.
  
*************** Wed Jul 18 11:14:33 2001  Kaveh R. Ghazi
*** 291,297 ****
  	* libI77/Makefile.in: Add necessary dependencies on config.h.
  
  2001-07-06  Toon Moene  <toon@moene.indiv.nluug.nl>
!             Pedro Vazquez  <vazquez@penelope.iqm.unicamp.br>
  
  	* libI77/configure.in: Check for fseeko, ftello.
  	* libI77/configure: Rebuilt.
--- 505,511 ----
  	* libI77/Makefile.in: Add necessary dependencies on config.h.
  
  2001-07-06  Toon Moene  <toon@moene.indiv.nluug.nl>
! 	    Pedro Vazquez  <vazquez@penelope.iqm.unicamp.br>
  
  	* libI77/configure.in: Check for fseeko, ftello.
  	* libI77/configure: Rebuilt.
*************** Wed Jul 18 11:14:33 2001  Kaveh R. Ghazi
*** 318,324 ****
  	* libI77/fio.h: Include <sys/types.h> for off_t.
  
  2001-07-01  Toon Moene  <toon@moene.indiv.nluug.nl>
!             Pedro Vazquez  <vazquez@penelope.iqm.unicamp.br>
  
  	* libI77/fio.h: Use off_t when appropriate.
  	* libI77/backspace.c (f_back): Ditto.
--- 532,538 ----
  	* libI77/fio.h: Include <sys/types.h> for off_t.
  
  2001-07-01  Toon Moene  <toon@moene.indiv.nluug.nl>
! 	    Pedro Vazquez  <vazquez@penelope.iqm.unicamp.br>
  
  	* libI77/fio.h: Use off_t when appropriate.
  	* libI77/backspace.c (f_back): Ditto.
*************** Wed Jul 18 11:14:33 2001  Kaveh R. Ghazi
*** 476,482 ****
  	file atomically.
  
  2000-07-03  Donn Terry  (donnte@microsoft.com)
!         * libU77/aclocal.m4: check for 2 argument gettimeofday without
  	struct timezone
  
  2000-07-02  Toon Moene  <toon@moene.indiv.nluug.nl>
--- 690,696 ----
  	file atomically.
  
  2000-07-03  Donn Terry  (donnte@microsoft.com)
! 	* libU77/aclocal.m4: check for 2 argument gettimeofday without
  	struct timezone
  
  2000-07-02  Toon Moene  <toon@moene.indiv.nluug.nl>
diff -Nrc3pad gcc-3.2.3/libf2c/configure gcc-3.3/libf2c/configure
*** gcc-3.2.3/libf2c/configure	2003-01-28 01:44:05.000000000 +0000
--- gcc-3.3/libf2c/configure	2003-02-20 09:12:17.000000000 +0000
*************** test "$ac_cv_mingw32" = yes && MINGW32=y
*** 768,774 ****
  # These need to be absolute paths, yet at the same time need to
  # canonicalize only relative paths, because then amd will not unmount
  # drives. Thus the use of PWDCMD: set it to 'pawd' or 'amq -w' if using amd.
! glibcpp_builddir=`pwd`
  case $srcdir in
  \\/$* | ?:\\/*) glibcpp_srcdir=${srcdir} ;;
  *) glibcpp_srcdir=`cd "$srcdir" && ${PWDCMD-pwd} || echo "$srcdir"` ;;
--- 768,774 ----
  # These need to be absolute paths, yet at the same time need to
  # canonicalize only relative paths, because then amd will not unmount
  # drives. Thus the use of PWDCMD: set it to 'pawd' or 'amq -w' if using amd.
! glibcpp_builddir=`${PWDCMD-pwd}`
  case $srcdir in
  \\/$* | ?:\\/*) glibcpp_srcdir=${srcdir} ;;
  *) glibcpp_srcdir=`cd "$srcdir" && ${PWDCMD-pwd} || echo "$srcdir"` ;;
*************** gnu*)
*** 1596,1604 ****
    ;;
  
  hpux10.20*|hpux11*)
!   lt_cv_deplibs_check_method='file_magic (s[0-9][0-9][0-9]|PA-RISC[0-9].[0-9]) shared library'
!   lt_cv_file_magic_cmd=/usr/bin/file
!   lt_cv_file_magic_test_file=/usr/lib/libc.sl
    ;;
  
  irix5* | irix6*)
--- 1596,1613 ----
    ;;
  
  hpux10.20*|hpux11*)
!   case $host_cpu in
!   hppa*)
!     lt_cv_deplibs_check_method='file_magic (s[0-9][0-9][0-9]|PA-RISC[0-9].[0-9]) shared library'
!     lt_cv_file_magic_cmd=/usr/bin/file
!     lt_cv_file_magic_test_file=/usr/lib/libc.sl
!     ;;
!   ia64*)
!     lt_cv_deplibs_check_method='file_magic (s[0-9][0-9][0-9]|ELF-[0-9][0-9]) shared object file - IA64'
!     lt_cv_file_magic_cmd=/usr/bin/file
!     lt_cv_file_magic_test_file=/usr/lib/hpux32/libc.so
!     ;;
!   esac
    ;;
  
  irix5* | irix6*)
*************** file_magic_cmd=$lt_cv_file_magic_cmd
*** 1688,1700 ****
  deplibs_check_method=$lt_cv_deplibs_check_method
  
  echo $ac_n "checking for object suffix""... $ac_c" 1>&6
! echo "configure:1692: checking for object suffix" >&5
  if eval "test \"`echo '$''{'ac_cv_objext'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    rm -f conftest*
  echo 'int i = 1;' > conftest.$ac_ext
! if { (eval echo configure:1698: \"$ac_compile\") 1>&5; (eval $ac_compile) 2>&5; }; then
    for ac_file in conftest.*; do
      case $ac_file in
      *.c) ;;
--- 1697,1709 ----
  deplibs_check_method=$lt_cv_deplibs_check_method
  
  echo $ac_n "checking for object suffix""... $ac_c" 1>&6
! echo "configure:1701: checking for object suffix" >&5
  if eval "test \"`echo '$''{'ac_cv_objext'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    rm -f conftest*
  echo 'int i = 1;' > conftest.$ac_ext
! if { (eval echo configure:1707: \"$ac_compile\") 1>&5; (eval $ac_compile) 2>&5; }; then
    for ac_file in conftest.*; do
      case $ac_file in
      *.c) ;;
*************** case $deplibs_check_method in
*** 1718,1724 ****
  file_magic*)
    if test "$file_magic_cmd" = '$MAGIC_CMD'; then
      echo $ac_n "checking for ${ac_tool_prefix}file""... $ac_c" 1>&6
! echo "configure:1722: checking for ${ac_tool_prefix}file" >&5
  if eval "test \"`echo '$''{'lt_cv_path_MAGIC_CMD'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
--- 1727,1733 ----
  file_magic*)
    if test "$file_magic_cmd" = '$MAGIC_CMD'; then
      echo $ac_n "checking for ${ac_tool_prefix}file""... $ac_c" 1>&6
! echo "configure:1731: checking for ${ac_tool_prefix}file" >&5
  if eval "test \"`echo '$''{'lt_cv_path_MAGIC_CMD'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
*************** fi
*** 1780,1786 ****
  if test -z "$lt_cv_path_MAGIC_CMD"; then
    if test -n "$ac_tool_prefix"; then
      echo $ac_n "checking for file""... $ac_c" 1>&6
! echo "configure:1784: checking for file" >&5
  if eval "test \"`echo '$''{'lt_cv_path_MAGIC_CMD'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
--- 1789,1795 ----
  if test -z "$lt_cv_path_MAGIC_CMD"; then
    if test -n "$ac_tool_prefix"; then
      echo $ac_n "checking for file""... $ac_c" 1>&6
! echo "configure:1793: checking for file" >&5
  if eval "test \"`echo '$''{'lt_cv_path_MAGIC_CMD'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
*************** esac
*** 1851,1857 ****
  # Extract the first word of "${ac_tool_prefix}ranlib", so it can be a program name with args.
  set dummy ${ac_tool_prefix}ranlib; ac_word=$2
  echo $ac_n "checking for $ac_word""... $ac_c" 1>&6
! echo "configure:1855: checking for $ac_word" >&5
  if eval "test \"`echo '$''{'ac_cv_prog_RANLIB'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
--- 1860,1866 ----
  # Extract the first word of "${ac_tool_prefix}ranlib", so it can be a program name with args.
  set dummy ${ac_tool_prefix}ranlib; ac_word=$2
  echo $ac_n "checking for $ac_word""... $ac_c" 1>&6
! echo "configure:1864: checking for $ac_word" >&5
  if eval "test \"`echo '$''{'ac_cv_prog_RANLIB'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
*************** if test -n "$ac_tool_prefix"; then
*** 1883,1889 ****
    # Extract the first word of "ranlib", so it can be a program name with args.
  set dummy ranlib; ac_word=$2
  echo $ac_n "checking for $ac_word""... $ac_c" 1>&6
! echo "configure:1887: checking for $ac_word" >&5
  if eval "test \"`echo '$''{'ac_cv_prog_RANLIB'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
--- 1892,1898 ----
    # Extract the first word of "ranlib", so it can be a program name with args.
  set dummy ranlib; ac_word=$2
  echo $ac_n "checking for $ac_word""... $ac_c" 1>&6
! echo "configure:1896: checking for $ac_word" >&5
  if eval "test \"`echo '$''{'ac_cv_prog_RANLIB'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
*************** fi
*** 1918,1924 ****
  # Extract the first word of "${ac_tool_prefix}strip", so it can be a program name with args.
  set dummy ${ac_tool_prefix}strip; ac_word=$2
  echo $ac_n "checking for $ac_word""... $ac_c" 1>&6
! echo "configure:1922: checking for $ac_word" >&5
  if eval "test \"`echo '$''{'ac_cv_prog_STRIP'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
--- 1927,1933 ----
  # Extract the first word of "${ac_tool_prefix}strip", so it can be a program name with args.
  set dummy ${ac_tool_prefix}strip; ac_word=$2
  echo $ac_n "checking for $ac_word""... $ac_c" 1>&6
! echo "configure:1931: checking for $ac_word" >&5
  if eval "test \"`echo '$''{'ac_cv_prog_STRIP'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
*************** if test -n "$ac_tool_prefix"; then
*** 1950,1956 ****
    # Extract the first word of "strip", so it can be a program name with args.
  set dummy strip; ac_word=$2
  echo $ac_n "checking for $ac_word""... $ac_c" 1>&6
! echo "configure:1954: checking for $ac_word" >&5
  if eval "test \"`echo '$''{'ac_cv_prog_STRIP'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
--- 1959,1965 ----
    # Extract the first word of "strip", so it can be a program name with args.
  set dummy strip; ac_word=$2
  echo $ac_n "checking for $ac_word""... $ac_c" 1>&6
! echo "configure:1963: checking for $ac_word" >&5
  if eval "test \"`echo '$''{'ac_cv_prog_STRIP'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
*************** test x"$pic_mode" = xno && libtool_flags
*** 2017,2024 ****
  case $host in
  *-*-irix6*)
    # Find out which ABI we are using.
!   echo '#line 2021 "configure"' > conftest.$ac_ext
!   if { (eval echo configure:2022: \"$ac_compile\") 1>&5; (eval $ac_compile) 2>&5; }; then
      case `/usr/bin/file conftest.$ac_objext` in
      *32-bit*)
        LD="${LD-ld} -32"
--- 2026,2046 ----
  case $host in
  *-*-irix6*)
    # Find out which ABI we are using.
!   echo '#line 2030 "configure"' > conftest.$ac_ext
!   if { (eval echo configure:2031: \"$ac_compile\") 1>&5; (eval $ac_compile) 2>&5; }; then
!    if test "$lt_cv_prog_gnu_ld" = yes; then
!     case `/usr/bin/file conftest.$ac_objext` in
!     *32-bit*)
!       LD="${LD-ld} -melf32bsmip"
!       ;;
!     *N32*)
!       LD="${LD-ld} -melf32bmipn32"
!       ;;
!     *64-bit*)
!       LD="${LD-ld} -melf64bmip"
!       ;;
!     esac
!    else
      case `/usr/bin/file conftest.$ac_objext` in
      *32-bit*)
        LD="${LD-ld} -32"
*************** case $host in
*** 2030,2035 ****
--- 2052,2116 ----
        LD="${LD-ld} -64"
        ;;
      esac
+    fi
+   fi
+   rm -rf conftest*
+   ;;
+ 
+ ia64-*-hpux*)
+   # Find out which ABI we are using.
+   echo 'int i;' > conftest.$ac_ext
+   if { (eval echo configure:2064: \"$ac_compile\") 1>&5; (eval $ac_compile) 2>&5; }; then
+     case "`/usr/bin/file conftest.o`" in
+     *ELF-32*)
+       HPUX_IA64_MODE="32"
+       ;;
+     *ELF-64*)
+       HPUX_IA64_MODE="64"
+       ;;
+     esac
+   fi
+   rm -rf conftest*
+   ;;
+ 
+ x86_64-*linux*|ppc*-*linux*|powerpc*-*linux*|s390*-*linux*|sparc*-*linux*)
+   # Find out which ABI we are using.
+   echo 'int i;' > conftest.$ac_ext
+   if { (eval echo configure:2080: \"$ac_compile\") 1>&5; (eval $ac_compile) 2>&5; }; then
+     case "`/usr/bin/file conftest.o`" in
+     *32-bit*)
+       case $host in
+         x86_64-*linux*)
+           LD="${LD-ld} -m elf_i386"
+           ;;
+         ppc64-*linux*)
+           LD="${LD-ld} -m elf32ppclinux"
+           ;;
+         s390x-*linux*)
+           LD="${LD-ld} -m elf_s390"
+           ;;
+         sparc64-*linux*)
+           LD="${LD-ld} -m elf32_sparc"
+           ;;
+       esac
+       ;;
+     *64-bit*)
+       case $host in
+         x86_64-*linux*)
+           LD="${LD-ld} -m elf_x86_64"
+           ;;
+         ppc*-*linux*|powerpc*-*linux*)
+           LD="${LD-ld} -m elf64ppc"
+           ;;
+         s390*-*linux*)
+           LD="${LD-ld} -m elf64_s390"
+           ;;
+         sparc*-*linux*)
+           LD="${LD-ld} -m elf64_sparc"
+           ;;
+       esac
+       ;;
+     esac
    fi
    rm -rf conftest*
    ;;
*************** case $host in
*** 2039,2045 ****
    SAVE_CFLAGS="$CFLAGS"
    CFLAGS="$CFLAGS -belf"
    echo $ac_n "checking whether the C compiler needs -belf""... $ac_c" 1>&6
! echo "configure:2043: checking whether the C compiler needs -belf" >&5
  if eval "test \"`echo '$''{'lt_cv_cc_needs_belf'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
--- 2120,2126 ----
    SAVE_CFLAGS="$CFLAGS"
    CFLAGS="$CFLAGS -belf"
    echo $ac_n "checking whether the C compiler needs -belf""... $ac_c" 1>&6
! echo "configure:2124: checking whether the C compiler needs -belf" >&5
  if eval "test \"`echo '$''{'lt_cv_cc_needs_belf'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
*************** ac_link='${CC-cc} -o conftest${ac_exeext
*** 2052,2065 ****
  cross_compiling=$ac_cv_prog_cc_cross
  
       cat > conftest.$ac_ext <<EOF
! #line 2056 "configure"
  #include "confdefs.h"
  
  int main() {
  
  ; return 0; }
  EOF
! if { (eval echo configure:2063: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest${ac_exeext}; then
    rm -rf conftest*
    lt_cv_cc_needs_belf=yes
  else
--- 2133,2146 ----
  cross_compiling=$ac_cv_prog_cc_cross
  
       cat > conftest.$ac_ext <<EOF
! #line 2137 "configure"
  #include "confdefs.h"
  
  int main() {
  
  ; return 0; }
  EOF
! if { (eval echo configure:2144: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest${ac_exeext}; then
    rm -rf conftest*
    lt_cv_cc_needs_belf=yes
  else
*************** else
*** 2183,2189 ****
    # Extract the first word of "ranlib", so it can be a program name with args.
  set dummy ranlib; ac_word=$2
  echo $ac_n "checking for $ac_word""... $ac_c" 1>&6
! echo "configure:2187: checking for $ac_word" >&5
  if eval "test \"`echo '$''{'ac_cv_prog_RANLIB'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
--- 2264,2270 ----
    # Extract the first word of "ranlib", so it can be a program name with args.
  set dummy ranlib; ac_word=$2
  echo $ac_n "checking for $ac_word""... $ac_c" 1>&6
! echo "configure:2268: checking for $ac_word" >&5
  if eval "test \"`echo '$''{'ac_cv_prog_RANLIB'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
*************** fi
*** 2223,2229 ****
  # SVR4 /usr/ucb/install, which tries to use the nonexistent group "staff"
  # ./install, which can be erroneously created by make from ./install.sh.
  echo $ac_n "checking for a BSD compatible install""... $ac_c" 1>&6
! echo "configure:2227: checking for a BSD compatible install" >&5
  if test -z "$INSTALL"; then
  if eval "test \"`echo '$''{'ac_cv_path_install'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
--- 2304,2310 ----
  # SVR4 /usr/ucb/install, which tries to use the nonexistent group "staff"
  # ./install, which can be erroneously created by make from ./install.sh.
  echo $ac_n "checking for a BSD compatible install""... $ac_c" 1>&6
! echo "configure:2308: checking for a BSD compatible install" >&5
  if test -z "$INSTALL"; then
  if eval "test \"`echo '$''{'ac_cv_path_install'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
*************** test -z "$INSTALL_SCRIPT" && INSTALL_SCR
*** 2276,2282 ****
  test -z "$INSTALL_DATA" && INSTALL_DATA='${INSTALL} -m 644'
  
  echo $ac_n "checking whether ${MAKE-make} sets \${MAKE}""... $ac_c" 1>&6
! echo "configure:2280: checking whether ${MAKE-make} sets \${MAKE}" >&5
  set dummy ${MAKE-make}; ac_make=`echo "$2" | sed 'y%./+-%__p_%'`
  if eval "test \"`echo '$''{'ac_cv_prog_make_${ac_make}_set'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
--- 2357,2363 ----
  test -z "$INSTALL_DATA" && INSTALL_DATA='${INSTALL} -m 644'
  
  echo $ac_n "checking whether ${MAKE-make} sets \${MAKE}""... $ac_c" 1>&6
! echo "configure:2361: checking whether ${MAKE-make} sets \${MAKE}" >&5
  set dummy ${MAKE-make}; ac_make=`echo "$2" | sed 'y%./+-%__p_%'`
  if eval "test \"`echo '$''{'ac_cv_prog_make_${ac_make}_set'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
*************** fi
*** 2305,2311 ****
  
  # Sanity check for the cross-compilation case:
  echo $ac_n "checking how to run the C preprocessor""... $ac_c" 1>&6
! echo "configure:2309: checking how to run the C preprocessor" >&5
  # On Suns, sometimes $CPP names a directory.
  if test -n "$CPP" && test -d "$CPP"; then
    CPP=
--- 2386,2392 ----
  
  # Sanity check for the cross-compilation case:
  echo $ac_n "checking how to run the C preprocessor""... $ac_c" 1>&6
! echo "configure:2390: checking how to run the C preprocessor" >&5
  # On Suns, sometimes $CPP names a directory.
  if test -n "$CPP" && test -d "$CPP"; then
    CPP=
*************** else
*** 2320,2332 ****
    # On the NeXT, cc -E runs the code through the compiler's parser,
    # not just through cpp.
    cat > conftest.$ac_ext <<EOF
! #line 2324 "configure"
  #include "confdefs.h"
  #include <assert.h>
  Syntax Error
  EOF
  ac_try="$ac_cpp conftest.$ac_ext >/dev/null 2>conftest.out"
! { (eval echo configure:2330: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; }
  ac_err=`grep -v '^ *+' conftest.out | grep -v "^conftest.${ac_ext}\$"`
  if test -z "$ac_err"; then
    :
--- 2401,2413 ----
    # On the NeXT, cc -E runs the code through the compiler's parser,
    # not just through cpp.
    cat > conftest.$ac_ext <<EOF
! #line 2405 "configure"
  #include "confdefs.h"
  #include <assert.h>
  Syntax Error
  EOF
  ac_try="$ac_cpp conftest.$ac_ext >/dev/null 2>conftest.out"
! { (eval echo configure:2411: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; }
  ac_err=`grep -v '^ *+' conftest.out | grep -v "^conftest.${ac_ext}\$"`
  if test -z "$ac_err"; then
    :
*************** else
*** 2337,2349 ****
    rm -rf conftest*
    CPP="${CC-cc} -E -traditional-cpp"
    cat > conftest.$ac_ext <<EOF
! #line 2341 "configure"
  #include "confdefs.h"
  #include <assert.h>
  Syntax Error
  EOF
  ac_try="$ac_cpp conftest.$ac_ext >/dev/null 2>conftest.out"
! { (eval echo configure:2347: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; }
  ac_err=`grep -v '^ *+' conftest.out | grep -v "^conftest.${ac_ext}\$"`
  if test -z "$ac_err"; then
    :
--- 2418,2430 ----
    rm -rf conftest*
    CPP="${CC-cc} -E -traditional-cpp"
    cat > conftest.$ac_ext <<EOF
! #line 2422 "configure"
  #include "confdefs.h"
  #include <assert.h>
  Syntax Error
  EOF
  ac_try="$ac_cpp conftest.$ac_ext >/dev/null 2>conftest.out"
! { (eval echo configure:2428: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; }
  ac_err=`grep -v '^ *+' conftest.out | grep -v "^conftest.${ac_ext}\$"`
  if test -z "$ac_err"; then
    :
*************** else
*** 2354,2366 ****
    rm -rf conftest*
    CPP="${CC-cc} -nologo -E"
    cat > conftest.$ac_ext <<EOF
! #line 2358 "configure"
  #include "confdefs.h"
  #include <assert.h>
  Syntax Error
  EOF
  ac_try="$ac_cpp conftest.$ac_ext >/dev/null 2>conftest.out"
! { (eval echo configure:2364: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; }
  ac_err=`grep -v '^ *+' conftest.out | grep -v "^conftest.${ac_ext}\$"`
  if test -z "$ac_err"; then
    :
--- 2435,2447 ----
    rm -rf conftest*
    CPP="${CC-cc} -nologo -E"
    cat > conftest.$ac_ext <<EOF
! #line 2439 "configure"
  #include "confdefs.h"
  #include <assert.h>
  Syntax Error
  EOF
  ac_try="$ac_cpp conftest.$ac_ext >/dev/null 2>conftest.out"
! { (eval echo configure:2445: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; }
  ac_err=`grep -v '^ *+' conftest.out | grep -v "^conftest.${ac_ext}\$"`
  if test -z "$ac_err"; then
    :
*************** echo "$ac_t""$CPP" 1>&6
*** 2386,2402 ****
  
  ac_safe=`echo "stdio.h" | sed 'y%./+-%__p_%'`
  echo $ac_n "checking for stdio.h""... $ac_c" 1>&6
! echo "configure:2390: checking for stdio.h" >&5
  if eval "test \"`echo '$''{'ac_cv_header_$ac_safe'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 2395 "configure"
  #include "confdefs.h"
  #include <stdio.h>
  EOF
  ac_try="$ac_cpp conftest.$ac_ext >/dev/null 2>conftest.out"
! { (eval echo configure:2400: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; }
  ac_err=`grep -v '^ *+' conftest.out | grep -v "^conftest.${ac_ext}\$"`
  if test -z "$ac_err"; then
    rm -rf conftest*
--- 2467,2483 ----
  
  ac_safe=`echo "stdio.h" | sed 'y%./+-%__p_%'`
  echo $ac_n "checking for stdio.h""... $ac_c" 1>&6
! echo "configure:2471: checking for stdio.h" >&5
  if eval "test \"`echo '$''{'ac_cv_header_$ac_safe'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 2476 "configure"
  #include "confdefs.h"
  #include <stdio.h>
  EOF
  ac_try="$ac_cpp conftest.$ac_ext >/dev/null 2>conftest.out"
! { (eval echo configure:2481: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; }
  ac_err=`grep -v '^ *+' conftest.out | grep -v "^conftest.${ac_ext}\$"`
  if test -z "$ac_err"; then
    rm -rf conftest*
*************** fi
*** 2424,2435 ****
  
  
  echo $ac_n "checking for built-in g77 integer types""... $ac_c" 1>&6
! echo "configure:2428: checking for built-in g77 integer types" >&5
  if eval "test \"`echo '$''{'libf2c_cv_has_g77_builtin_types'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 2433 "configure"
  #include "confdefs.h"
  
  int main() {
--- 2505,2516 ----
  
  
  echo $ac_n "checking for built-in g77 integer types""... $ac_c" 1>&6
! echo "configure:2509: checking for built-in g77 integer types" >&5
  if eval "test \"`echo '$''{'libf2c_cv_has_g77_builtin_types'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 2514 "configure"
  #include "confdefs.h"
  
  int main() {
*************** __g77_longint g77l;
*** 2439,2445 ****
  __g77_ulongint g77ul;
  ; return 0; }
  EOF
! if { (eval echo configure:2443: \"$ac_compile\") 1>&5; (eval $ac_compile) 2>&5; }; then
    rm -rf conftest*
    libf2c_cv_has_g77_builtin_types=yes
  else
--- 2520,2526 ----
  __g77_ulongint g77ul;
  ; return 0; }
  EOF
! if { (eval echo configure:2524: \"$ac_compile\") 1>&5; (eval $ac_compile) 2>&5; }; then
    rm -rf conftest*
    libf2c_cv_has_g77_builtin_types=yes
  else
*************** with_multisubdir=${with_multisubdir}
*** 2782,2787 ****
--- 2863,2869 ----
  ac_configure_args="--enable-multilib ${ac_configure_args}"
  toplevel_srcdir=${toplevel_srcdir}
  CONFIG_SHELL=${CONFIG_SHELL-/bin/sh}
+ ORIGINAL_LD_FOR_MULTILIBS="${ORIGINAL_LD_FOR_MULTILIBS}"
  
  EOF
  cat >> $CONFIG_STATUS <<\EOF
diff -Nrc3pad gcc-3.2.3/libf2c/configure.in gcc-3.3/libf2c/configure.in
*** gcc-3.2.3/libf2c/configure.in	2002-06-26 04:15:29.000000000 +0000
--- gcc-3.3/libf2c/configure.in	2003-02-20 09:12:17.000000000 +0000
***************
*** 1,5 ****
  # Process this file with autoconf to produce a configure script.
! #   Copyright (C) 1995, 1997, 1998, 1999, 2002 Free Software Foundation, Inc.
  #   Contributed by Dave Love (d.love@dl.ac.uk).
  #
  #This file is part of GNU Fortran.
--- 1,6 ----
  # Process this file with autoconf to produce a configure script.
! #   Copyright (C) 1995, 1997, 1998, 1999, 2002, 2003
! #    Free Software Foundation, Inc.
  #   Contributed by Dave Love (d.love@dl.ac.uk).
  #
  #This file is part of GNU Fortran.
*************** with_multisubdir=${with_multisubdir}
*** 137,142 ****
--- 138,144 ----
  ac_configure_args="--enable-multilib ${ac_configure_args}"
  toplevel_srcdir=${toplevel_srcdir}
  CONFIG_SHELL=${CONFIG_SHELL-/bin/sh}
+ ORIGINAL_LD_FOR_MULTILIBS="${ORIGINAL_LD_FOR_MULTILIBS}"
  )
  
  
diff -Nrc3pad gcc-3.2.3/libf2c/f2cext.c gcc-3.3/libf2c/f2cext.c
*** gcc-3.2.3/libf2c/f2cext.c	1999-03-05 23:40:08.000000000 +0000
--- gcc-3.3/libf2c/f2cext.c	2002-06-05 19:07:09.000000000 +0000
*************** integer access_ (const char *name, const
*** 140,146 ****
  #endif
  
  #ifdef Lalarm
! integer alarm_ (integer *seconds, sig_proc proc, integer *status) {
      extern integer G77_alarm_0 (integer *seconds, sig_proc proc);
      return G77_alarm_0 (seconds, proc);
  }
--- 140,147 ----
  #endif
  
  #ifdef Lalarm
! integer alarm_ (integer *seconds, sig_proc proc,
! 		integer *status __attribute__ ((__unused__))) {
      extern integer G77_alarm_0 (integer *seconds, sig_proc proc);
      return G77_alarm_0 (seconds, proc);
  }
diff -Nrc3pad gcc-3.2.3/libf2c/g2c.hin gcc-3.3/libf2c/g2c.hin
*** gcc-3.2.3/libf2c/g2c.hin	2000-05-18 17:44:27.000000000 +0000
--- gcc-3.3/libf2c/g2c.hin	2002-06-01 01:58:09.000000000 +0000
*************** typedef struct
*** 132,139 ****
  	ftnlen	inblanklen;
  } inlist;
  
- #define VOID void
- 
  union Multitype {	/* for multiple entry points */
  	integer1 g;
  	shortint h;
--- 132,137 ----
*************** typedef shortint (*J_fp)(...);
*** 183,193 ****
  typedef integer (*I_fp)(...);
  typedef real (*R_fp)(...);
  typedef doublereal (*D_fp)(...), (*E_fp)(...);
! typedef /* Complex */ VOID (*C_fp)(...);
! typedef /* Double Complex */ VOID (*Z_fp)(...);
  typedef logical (*L_fp)(...);
  typedef shortlogical (*K_fp)(...);
! typedef /* Character */ VOID (*H_fp)(...);
  typedef /* Subroutine */ int (*S_fp)(...);
  #else
  typedef int /* Unknown procedure type */ (*U_fp)();
--- 181,191 ----
  typedef integer (*I_fp)(...);
  typedef real (*R_fp)(...);
  typedef doublereal (*D_fp)(...), (*E_fp)(...);
! typedef /* Complex */ void (*C_fp)(...);
! typedef /* Double Complex */ void (*Z_fp)(...);
  typedef logical (*L_fp)(...);
  typedef shortlogical (*K_fp)(...);
! typedef /* Character */ void (*H_fp)(...);
  typedef /* Subroutine */ int (*S_fp)(...);
  #else
  typedef int /* Unknown procedure type */ (*U_fp)();
*************** typedef shortint (*J_fp)();
*** 195,211 ****
  typedef integer (*I_fp)();
  typedef real (*R_fp)();
  typedef doublereal (*D_fp)(), (*E_fp)();
! typedef /* Complex */ VOID (*C_fp)();
! typedef /* Double Complex */ VOID (*Z_fp)();
  typedef logical (*L_fp)();
  typedef shortlogical (*K_fp)();
! typedef /* Character */ VOID (*H_fp)();
  typedef /* Subroutine */ int (*S_fp)();
  #endif
  /* E_fp is for real functions when -R is not specified */
! typedef VOID C_f;	/* complex function */
! typedef VOID H_f;	/* character function */
! typedef VOID Z_f;	/* double complex function */
  typedef doublereal E_f;	/* real function with -R not specified */
  
  /* undef any lower-case symbols that your C compiler predefines, e.g.: */
--- 193,209 ----
  typedef integer (*I_fp)();
  typedef real (*R_fp)();
  typedef doublereal (*D_fp)(), (*E_fp)();
! typedef /* Complex */ void (*C_fp)();
! typedef /* Double Complex */ void (*Z_fp)();
  typedef logical (*L_fp)();
  typedef shortlogical (*K_fp)();
! typedef /* Character */ void (*H_fp)();
  typedef /* Subroutine */ int (*S_fp)();
  #endif
  /* E_fp is for real functions when -R is not specified */
! typedef void C_f;	/* complex function */
! typedef void H_f;	/* character function */
! typedef void Z_f;	/* double complex function */
  typedef doublereal E_f;	/* real function with -R not specified */
  
  /* undef any lower-case symbols that your C compiler predefines, e.g.: */
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/abort_.c gcc-3.3/libf2c/libF77/abort_.c
*** gcc-3.2.3/libf2c/libF77/abort_.c	1999-05-10 14:40:52.000000000 +0000
--- gcc-3.3/libf2c/libF77/abort_.c	2002-06-01 12:38:27.000000000 +0000
***************
*** 1,16 ****
  #include <stdio.h>
  #include "f2c.h"
  
! #ifdef KR_headers
! extern VOID sig_die();
! 
! int G77_abort_0 ()
! #else
! extern void sig_die(char*,int);
  
! int G77_abort_0 (void)
! #endif
  {
! sig_die("Fortran abort routine called", 1);
! return 0;	/* not reached */
  }
--- 1,11 ----
  #include <stdio.h>
  #include "f2c.h"
  
! extern void sig_die (char *, int);
  
! int
! G77_abort_0 (void)
  {
!   sig_die ("Fortran abort routine called", 1);
!   return 0;			/* not reached */
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/c_abs.c gcc-3.3/libf2c/libF77/c_abs.c
*** gcc-3.2.3/libf2c/libF77/c_abs.c	1999-09-04 15:09:16.000000000 +0000
--- gcc-3.3/libf2c/libF77/c_abs.c	2002-06-01 12:38:27.000000000 +0000
***************
*** 1,14 ****
  #include "f2c.h"
  
! #ifdef KR_headers
! extern double f__cabs();
! 
! double c_abs(z) complex *z;
! #else
! extern double f__cabs(double, double);
  
! double c_abs(complex *z)
! #endif
  {
! return( f__cabs( z->r, z->i ) );
  }
--- 1,9 ----
  #include "f2c.h"
  
! extern double f__cabs (double, double);
  
! double
! c_abs (complex * z)
  {
!   return (f__cabs (z->r, z->i));
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/cabs.c gcc-3.3/libf2c/libF77/cabs.c
*** gcc-3.2.3/libf2c/libF77/cabs.c	1999-09-04 15:09:16.000000000 +0000
--- gcc-3.3/libf2c/libF77/cabs.c	2002-06-01 12:38:27.000000000 +0000
***************
*** 1,27 ****
- #ifdef KR_headers
- extern double sqrt();
- double f__cabs(real, imag) double real, imag;
- #else
  #undef abs
  #include <math.h>
! double f__cabs(double real, double imag)
! #endif
  {
! double temp;
  
! if(real < 0)
! 	real = -real;
! if(imag < 0)
! 	imag = -imag;
! if(imag > real){
! 	temp = real;
! 	real = imag;
! 	imag = temp;
! }
! if((real+imag) == real)
! 	return(real);
  
! temp = imag/real;
! temp = real*sqrt(1.0 + temp*temp);  /*overflow!!*/
! return(temp);
  }
--- 1,24 ----
  #undef abs
  #include <math.h>
! double
! f__cabs (double real, double imag)
  {
!   double temp;
  
!   if (real < 0)
!     real = -real;
!   if (imag < 0)
!     imag = -imag;
!   if (imag > real)
!     {
!       temp = real;
!       real = imag;
!       imag = temp;
!     }
!   if ((real + imag) == real)
!     return (real);
  
!   temp = imag / real;
!   temp = real * sqrt (1.0 + temp * temp);	/*overflow!! */
!   return (temp);
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/c_cos.c gcc-3.3/libf2c/libF77/c_cos.c
*** gcc-3.2.3/libf2c/libF77/c_cos.c	1999-05-03 08:35:07.000000000 +0000
--- gcc-3.3/libf2c/libF77/c_cos.c	2002-06-01 12:38:27.000000000 +0000
***************
*** 1,17 ****
  #include "f2c.h"
  
- #ifdef KR_headers
- extern double sin(), cos(), sinh(), cosh();
- 
- VOID c_cos(r, z) complex *r, *z;
- #else
  #undef abs
  #include "math.h"
  
! void c_cos(complex *r, complex *z)
! #endif
  {
! 	double zi = z->i, zr = z->r;
! 	r->r =   cos(zr) * cosh(zi);
! 	r->i = - sin(zr) * sinh(zi);
! 	}
--- 1,12 ----
  #include "f2c.h"
  
  #undef abs
  #include "math.h"
  
! void
! c_cos (complex * r, complex * z)
  {
!   double zi = z->i, zr = z->r;
!   r->r = cos (zr) * cosh (zi);
!   r->i = -sin (zr) * sinh (zi);
! }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/c_div.c gcc-3.3/libf2c/libF77/c_div.c
*** gcc-3.2.3/libf2c/libF77/c_div.c	2000-03-12 19:20:47.000000000 +0000
--- gcc-3.3/libf2c/libF77/c_div.c	2002-06-01 12:38:27.000000000 +0000
***************
*** 1,47 ****
  #include "f2c.h"
  
! #ifdef KR_headers
! extern VOID sig_die();
! VOID c_div(c, a, b)
! complex *a, *b, *c;
! #else
! extern void sig_die(char*,int);
! void c_div(complex *c, complex *a, complex *b)
! #endif
  {
! 	double ratio, den;
! 	double abr, abi, cr;
  
! 	if( (abr = b->r) < 0.)
! 		abr = - abr;
! 	if( (abi = b->i) < 0.)
! 		abi = - abi;
! 	if( abr <= abi )
! 		{
! 		if(abi == 0) {
  #ifdef IEEE_COMPLEX_DIVIDE
! 			float af, bf;
! 			af = bf = abr;
! 			if (a->i != 0 || a->r != 0)
! 				af = 1.;
! 			c->i = c->r = af / bf;
! 			return;
  #else
! 			sig_die("complex division by zero", 1);
  #endif
- 			}
- 		ratio = (double)b->r / b->i ;
- 		den = b->i * (1 + ratio*ratio);
- 		cr = (a->r*ratio + a->i) / den;
- 		c->i = (a->i*ratio - a->r) / den;
- 		}
- 
- 	else
- 		{
- 		ratio = (double)b->i / b->r ;
- 		den = b->r * (1 + ratio*ratio);
- 		cr = (a->r + a->i*ratio) / den;
- 		c->i = (a->i - a->r*ratio) / den;
- 		}
- 	c->r = cr;
  	}
--- 1,43 ----
  #include "f2c.h"
  
! extern void sig_die (char *, int);
! void
! c_div (complex * c, complex * a, complex * b)
  {
!   double ratio, den;
!   double abr, abi, cr;
  
!   if ((abr = b->r) < 0.)
!     abr = -abr;
!   if ((abi = b->i) < 0.)
!     abi = -abi;
!   if (abr <= abi)
!     {
!       if (abi == 0)
! 	{
  #ifdef IEEE_COMPLEX_DIVIDE
! 	  float af, bf;
! 	  af = bf = abr;
! 	  if (a->i != 0 || a->r != 0)
! 	    af = 1.;
! 	  c->i = c->r = af / bf;
! 	  return;
  #else
! 	  sig_die ("complex division by zero", 1);
  #endif
  	}
+       ratio = (double) b->r / b->i;
+       den = b->i * (1 + ratio * ratio);
+       cr = (a->r * ratio + a->i) / den;
+       c->i = (a->i * ratio - a->r) / den;
+     }
+ 
+   else
+     {
+       ratio = (double) b->i / b->r;
+       den = b->r * (1 + ratio * ratio);
+       cr = (a->r + a->i * ratio) / den;
+       c->i = (a->i - a->r * ratio) / den;
+     }
+   c->r = cr;
+ }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/c_exp.c gcc-3.3/libf2c/libF77/c_exp.c
*** gcc-3.2.3/libf2c/libF77/c_exp.c	1999-05-03 08:35:08.000000000 +0000
--- gcc-3.3/libf2c/libF77/c_exp.c	2002-06-01 12:38:27.000000000 +0000
***************
*** 1,19 ****
  #include "f2c.h"
  
- #ifdef KR_headers
- extern double exp(), cos(), sin();
- 
-  VOID c_exp(r, z) complex *r, *z;
- #else
  #undef abs
  #include "math.h"
  
! void c_exp(complex *r, complex *z)
! #endif
  {
! 	double expx, zi = z->i;
  
! 	expx = exp(z->r);
! 	r->r = expx * cos(zi);
! 	r->i = expx * sin(zi);
! 	}
--- 1,14 ----
  #include "f2c.h"
  
  #undef abs
  #include "math.h"
  
! void
! c_exp (complex * r, complex * z)
  {
!   double expx, zi = z->i;
  
!   expx = exp (z->r);
!   r->r = expx * cos (zi);
!   r->i = expx * sin (zi);
! }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/c_log.c gcc-3.3/libf2c/libF77/c_log.c
*** gcc-3.2.3/libf2c/libF77/c_log.c	1999-05-10 14:40:53.000000000 +0000
--- gcc-3.3/libf2c/libF77/c_log.c	2002-06-01 12:38:27.000000000 +0000
***************
*** 1,17 ****
  #include "f2c.h"
  
- #ifdef KR_headers
- extern double log(), f__cabs(), atan2();
- VOID c_log(r, z) complex *r, *z;
- #else
  #undef abs
  #include "math.h"
! extern double f__cabs(double, double);
  
! void c_log(complex *r, complex *z)
! #endif
  {
! 	double zi, zr;
! 	r->i = atan2(zi = z->i, zr = z->r);
! 	r->r = log( f__cabs(zr, zi) );
! 	}
--- 1,13 ----
  #include "f2c.h"
  
  #undef abs
  #include "math.h"
! extern double f__cabs (double, double);
  
! void
! c_log (complex * r, complex * z)
  {
!   double zi, zr;
!   r->i = atan2 (zi = z->i, zr = z->r);
!   r->r = log (f__cabs (zr, zi));
! }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/configure gcc-3.3/libf2c/libF77/configure
*** gcc-3.2.3/libf2c/libF77/configure	2001-12-04 09:53:17.000000000 +0000
--- gcc-3.3/libf2c/libF77/configure	2002-06-01 01:53:50.000000000 +0000
*************** program_suffix=NONE
*** 28,34 ****
  program_transform_name=s,x,x,
  silent=
  site=
- sitefile=
  srcdir=
  target=NONE
  verbose=
--- 28,33 ----
*************** Configuration:
*** 143,149 ****
    --help                  print this message
    --no-create             do not create output files
    --quiet, --silent       do not print \`checking...' messages
-   --site-file=FILE        use FILE as the site file
    --version               print the version of autoconf that created configure
  Directory and file names:
    --prefix=PREFIX         install architecture-independent files in PREFIX
--- 142,147 ----
*************** EOF
*** 314,324 ****
    -site=* | --site=* | --sit=*)
      site="$ac_optarg" ;;
  
-   -site-file | --site-file | --site-fil | --site-fi | --site-f)
-     ac_prev=sitefile ;;
-   -site-file=* | --site-file=* | --site-fil=* | --site-fi=* | --site-f=*)
-     sitefile="$ac_optarg" ;;
- 
    -srcdir | --srcdir | --srcdi | --srcd | --src | --sr)
      ac_prev=srcdir ;;
    -srcdir=* | --srcdir=* | --srcdi=* | --srcd=* | --src=* | --sr=*)
--- 312,317 ----
*************** fi
*** 484,499 ****
  srcdir=`echo "${srcdir}" | sed 's%\([^/]\)/*$%\1%'`
  
  # Prefer explicitly selected file to automatically selected ones.
! if test -z "$sitefile"; then
!   if test -z "$CONFIG_SITE"; then
!     if test "x$prefix" != xNONE; then
!       CONFIG_SITE="$prefix/share/config.site $prefix/etc/config.site"
!     else
!       CONFIG_SITE="$ac_default_prefix/share/config.site $ac_default_prefix/etc/config.site"
!     fi
    fi
- else
-   CONFIG_SITE="$sitefile"
  fi
  for ac_site_file in $CONFIG_SITE; do
    if test -r "$ac_site_file"; then
--- 477,488 ----
  srcdir=`echo "${srcdir}" | sed 's%\([^/]\)/*$%\1%'`
  
  # Prefer explicitly selected file to automatically selected ones.
! if test -z "$CONFIG_SITE"; then
!   if test "x$prefix" != xNONE; then
!     CONFIG_SITE="$prefix/share/config.site $prefix/etc/config.site"
!   else
!     CONFIG_SITE="$ac_default_prefix/share/config.site $ac_default_prefix/etc/config.site"
    fi
  fi
  for ac_site_file in $CONFIG_SITE; do
    if test -r "$ac_site_file"; then
*************** fi
*** 541,547 ****
  # Extract the first word of "gcc", so it can be a program name with args.
  set dummy gcc; ac_word=$2
  echo $ac_n "checking for $ac_word""... $ac_c" 1>&6
! echo "configure:545: checking for $ac_word" >&5
  if eval "test \"`echo '$''{'ac_cv_prog_CC'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
--- 530,536 ----
  # Extract the first word of "gcc", so it can be a program name with args.
  set dummy gcc; ac_word=$2
  echo $ac_n "checking for $ac_word""... $ac_c" 1>&6
! echo "configure:534: checking for $ac_word" >&5
  if eval "test \"`echo '$''{'ac_cv_prog_CC'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
*************** if test -z "$CC"; then
*** 571,577 ****
    # Extract the first word of "cc", so it can be a program name with args.
  set dummy cc; ac_word=$2
  echo $ac_n "checking for $ac_word""... $ac_c" 1>&6
! echo "configure:575: checking for $ac_word" >&5
  if eval "test \"`echo '$''{'ac_cv_prog_CC'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
--- 560,566 ----
    # Extract the first word of "cc", so it can be a program name with args.
  set dummy cc; ac_word=$2
  echo $ac_n "checking for $ac_word""... $ac_c" 1>&6
! echo "configure:564: checking for $ac_word" >&5
  if eval "test \"`echo '$''{'ac_cv_prog_CC'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
*************** fi
*** 622,628 ****
        # Extract the first word of "cl", so it can be a program name with args.
  set dummy cl; ac_word=$2
  echo $ac_n "checking for $ac_word""... $ac_c" 1>&6
! echo "configure:626: checking for $ac_word" >&5
  if eval "test \"`echo '$''{'ac_cv_prog_CC'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
--- 611,617 ----
        # Extract the first word of "cl", so it can be a program name with args.
  set dummy cl; ac_word=$2
  echo $ac_n "checking for $ac_word""... $ac_c" 1>&6
! echo "configure:615: checking for $ac_word" >&5
  if eval "test \"`echo '$''{'ac_cv_prog_CC'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
*************** fi
*** 655,661 ****
  
  
  echo $ac_n "checking whether we are using GNU C""... $ac_c" 1>&6
! echo "configure:659: checking whether we are using GNU C" >&5
  if eval "test \"`echo '$''{'ac_cv_prog_gcc'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
--- 644,650 ----
  
  
  echo $ac_n "checking whether we are using GNU C""... $ac_c" 1>&6
! echo "configure:648: checking whether we are using GNU C" >&5
  if eval "test \"`echo '$''{'ac_cv_prog_gcc'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
*************** else
*** 664,670 ****
    yes;
  #endif
  EOF
! if { ac_try='${CC-cc} -E conftest.c'; { (eval echo configure:668: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; }; } | egrep yes >/dev/null 2>&1; then
    ac_cv_prog_gcc=yes
  else
    ac_cv_prog_gcc=no
--- 653,659 ----
    yes;
  #endif
  EOF
! if { ac_try='${CC-cc} -E conftest.c'; { (eval echo configure:657: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; }; } | egrep yes >/dev/null 2>&1; then
    ac_cv_prog_gcc=yes
  else
    ac_cv_prog_gcc=no
*************** ac_test_CFLAGS="${CFLAGS+set}"
*** 683,689 ****
  ac_save_CFLAGS="$CFLAGS"
  CFLAGS=
  echo $ac_n "checking whether ${CC-cc} accepts -g""... $ac_c" 1>&6
! echo "configure:687: checking whether ${CC-cc} accepts -g" >&5
  if eval "test \"`echo '$''{'ac_cv_prog_cc_g'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
--- 672,678 ----
  ac_save_CFLAGS="$CFLAGS"
  CFLAGS=
  echo $ac_n "checking whether ${CC-cc} accepts -g""... $ac_c" 1>&6
! echo "configure:676: checking whether ${CC-cc} accepts -g" >&5
  if eval "test \"`echo '$''{'ac_cv_prog_cc_g'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
*************** else
*** 726,732 ****
    # Extract the first word of "ranlib", so it can be a program name with args.
  set dummy ranlib; ac_word=$2
  echo $ac_n "checking for $ac_word""... $ac_c" 1>&6
! echo "configure:730: checking for $ac_word" >&5
  if eval "test \"`echo '$''{'ac_cv_prog_RANLIB'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
--- 715,721 ----
    # Extract the first word of "ranlib", so it can be a program name with args.
  set dummy ranlib; ac_word=$2
  echo $ac_n "checking for $ac_word""... $ac_c" 1>&6
! echo "configure:719: checking for $ac_word" >&5
  if eval "test \"`echo '$''{'ac_cv_prog_RANLIB'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
*************** fi
*** 755,761 ****
  
  fi
  echo $ac_n "checking whether ${MAKE-make} sets \${MAKE}""... $ac_c" 1>&6
! echo "configure:759: checking whether ${MAKE-make} sets \${MAKE}" >&5
  set dummy ${MAKE-make}; ac_make=`echo "$2" | sed 'y%./+-%__p_%'`
  if eval "test \"`echo '$''{'ac_cv_prog_make_${ac_make}_set'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
--- 744,750 ----
  
  fi
  echo $ac_n "checking whether ${MAKE-make} sets \${MAKE}""... $ac_c" 1>&6
! echo "configure:748: checking whether ${MAKE-make} sets \${MAKE}" >&5
  set dummy ${MAKE-make}; ac_make=`echo "$2" | sed 'y%./+-%__p_%'`
  if eval "test \"`echo '$''{'ac_cv_prog_make_${ac_make}_set'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
*************** fi
*** 785,791 ****
  
  # Sanity check for the cross-compilation case:
  echo $ac_n "checking how to run the C preprocessor""... $ac_c" 1>&6
! echo "configure:789: checking how to run the C preprocessor" >&5
  # On Suns, sometimes $CPP names a directory.
  if test -n "$CPP" && test -d "$CPP"; then
    CPP=
--- 774,780 ----
  
  # Sanity check for the cross-compilation case:
  echo $ac_n "checking how to run the C preprocessor""... $ac_c" 1>&6
! echo "configure:778: checking how to run the C preprocessor" >&5
  # On Suns, sometimes $CPP names a directory.
  if test -n "$CPP" && test -d "$CPP"; then
    CPP=
*************** else
*** 800,812 ****
    # On the NeXT, cc -E runs the code through the compiler's parser,
    # not just through cpp.
    cat > conftest.$ac_ext <<EOF
! #line 804 "configure"
  #include "confdefs.h"
  #include <assert.h>
  Syntax Error
  EOF
  ac_try="$ac_cpp conftest.$ac_ext >/dev/null 2>conftest.out"
! { (eval echo configure:810: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; }
  ac_err=`grep -v '^ *+' conftest.out | grep -v "^conftest.${ac_ext}\$"`
  if test -z "$ac_err"; then
    :
--- 789,801 ----
    # On the NeXT, cc -E runs the code through the compiler's parser,
    # not just through cpp.
    cat > conftest.$ac_ext <<EOF
! #line 793 "configure"
  #include "confdefs.h"
  #include <assert.h>
  Syntax Error
  EOF
  ac_try="$ac_cpp conftest.$ac_ext >/dev/null 2>conftest.out"
! { (eval echo configure:799: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; }
  ac_err=`grep -v '^ *+' conftest.out | grep -v "^conftest.${ac_ext}\$"`
  if test -z "$ac_err"; then
    :
*************** else
*** 817,829 ****
    rm -rf conftest*
    CPP="${CC-cc} -E -traditional-cpp"
    cat > conftest.$ac_ext <<EOF
! #line 821 "configure"
  #include "confdefs.h"
  #include <assert.h>
  Syntax Error
  EOF
  ac_try="$ac_cpp conftest.$ac_ext >/dev/null 2>conftest.out"
! { (eval echo configure:827: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; }
  ac_err=`grep -v '^ *+' conftest.out | grep -v "^conftest.${ac_ext}\$"`
  if test -z "$ac_err"; then
    :
--- 806,818 ----
    rm -rf conftest*
    CPP="${CC-cc} -E -traditional-cpp"
    cat > conftest.$ac_ext <<EOF
! #line 810 "configure"
  #include "confdefs.h"
  #include <assert.h>
  Syntax Error
  EOF
  ac_try="$ac_cpp conftest.$ac_ext >/dev/null 2>conftest.out"
! { (eval echo configure:816: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; }
  ac_err=`grep -v '^ *+' conftest.out | grep -v "^conftest.${ac_ext}\$"`
  if test -z "$ac_err"; then
    :
*************** else
*** 834,846 ****
    rm -rf conftest*
    CPP="${CC-cc} -nologo -E"
    cat > conftest.$ac_ext <<EOF
! #line 838 "configure"
  #include "confdefs.h"
  #include <assert.h>
  Syntax Error
  EOF
  ac_try="$ac_cpp conftest.$ac_ext >/dev/null 2>conftest.out"
! { (eval echo configure:844: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; }
  ac_err=`grep -v '^ *+' conftest.out | grep -v "^conftest.${ac_ext}\$"`
  if test -z "$ac_err"; then
    :
--- 823,835 ----
    rm -rf conftest*
    CPP="${CC-cc} -nologo -E"
    cat > conftest.$ac_ext <<EOF
! #line 827 "configure"
  #include "confdefs.h"
  #include <assert.h>
  Syntax Error
  EOF
  ac_try="$ac_cpp conftest.$ac_ext >/dev/null 2>conftest.out"
! { (eval echo configure:833: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; }
  ac_err=`grep -v '^ *+' conftest.out | grep -v "^conftest.${ac_ext}\$"`
  if test -z "$ac_err"; then
    :
*************** echo "$ac_t""$CPP" 1>&6
*** 866,882 ****
  
  ac_safe=`echo "stdio.h" | sed 'y%./+-%__p_%'`
  echo $ac_n "checking for stdio.h""... $ac_c" 1>&6
! echo "configure:870: checking for stdio.h" >&5
  if eval "test \"`echo '$''{'ac_cv_header_$ac_safe'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 875 "configure"
  #include "confdefs.h"
  #include <stdio.h>
  EOF
  ac_try="$ac_cpp conftest.$ac_ext >/dev/null 2>conftest.out"
! { (eval echo configure:880: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; }
  ac_err=`grep -v '^ *+' conftest.out | grep -v "^conftest.${ac_ext}\$"`
  if test -z "$ac_err"; then
    rm -rf conftest*
--- 855,871 ----
  
  ac_safe=`echo "stdio.h" | sed 'y%./+-%__p_%'`
  echo $ac_n "checking for stdio.h""... $ac_c" 1>&6
! echo "configure:859: checking for stdio.h" >&5
  if eval "test \"`echo '$''{'ac_cv_header_$ac_safe'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 864 "configure"
  #include "confdefs.h"
  #include <stdio.h>
  EOF
  ac_try="$ac_cpp conftest.$ac_ext >/dev/null 2>conftest.out"
! { (eval echo configure:869: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; }
  ac_err=`grep -v '^ *+' conftest.out | grep -v "^conftest.${ac_ext}\$"`
  if test -z "$ac_err"; then
    rm -rf conftest*
*************** fi
*** 904,915 ****
  
  
  echo $ac_n "checking for ANSI C header files""... $ac_c" 1>&6
! echo "configure:908: checking for ANSI C header files" >&5
  if eval "test \"`echo '$''{'ac_cv_header_stdc'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 913 "configure"
  #include "confdefs.h"
  #include <stdlib.h>
  #include <stdarg.h>
--- 893,904 ----
  
  
  echo $ac_n "checking for ANSI C header files""... $ac_c" 1>&6
! echo "configure:897: checking for ANSI C header files" >&5
  if eval "test \"`echo '$''{'ac_cv_header_stdc'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 902 "configure"
  #include "confdefs.h"
  #include <stdlib.h>
  #include <stdarg.h>
*************** else
*** 917,923 ****
  #include <float.h>
  EOF
  ac_try="$ac_cpp conftest.$ac_ext >/dev/null 2>conftest.out"
! { (eval echo configure:921: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; }
  ac_err=`grep -v '^ *+' conftest.out | grep -v "^conftest.${ac_ext}\$"`
  if test -z "$ac_err"; then
    rm -rf conftest*
--- 906,912 ----
  #include <float.h>
  EOF
  ac_try="$ac_cpp conftest.$ac_ext >/dev/null 2>conftest.out"
! { (eval echo configure:910: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; }
  ac_err=`grep -v '^ *+' conftest.out | grep -v "^conftest.${ac_ext}\$"`
  if test -z "$ac_err"; then
    rm -rf conftest*
*************** rm -f conftest*
*** 934,940 ****
  if test $ac_cv_header_stdc = yes; then
    # SunOS 4.x string.h does not declare mem*, contrary to ANSI.
  cat > conftest.$ac_ext <<EOF
! #line 938 "configure"
  #include "confdefs.h"
  #include <string.h>
  EOF
--- 923,929 ----
  if test $ac_cv_header_stdc = yes; then
    # SunOS 4.x string.h does not declare mem*, contrary to ANSI.
  cat > conftest.$ac_ext <<EOF
! #line 927 "configure"
  #include "confdefs.h"
  #include <string.h>
  EOF
*************** fi
*** 952,958 ****
  if test $ac_cv_header_stdc = yes; then
    # ISC 2.0.2 stdlib.h does not declare free, contrary to ANSI.
  cat > conftest.$ac_ext <<EOF
! #line 956 "configure"
  #include "confdefs.h"
  #include <stdlib.h>
  EOF
--- 941,947 ----
  if test $ac_cv_header_stdc = yes; then
    # ISC 2.0.2 stdlib.h does not declare free, contrary to ANSI.
  cat > conftest.$ac_ext <<EOF
! #line 945 "configure"
  #include "confdefs.h"
  #include <stdlib.h>
  EOF
*************** if test "$cross_compiling" = yes; then
*** 973,979 ****
    :
  else
    cat > conftest.$ac_ext <<EOF
! #line 977 "configure"
  #include "confdefs.h"
  #include <ctype.h>
  #define ISLOWER(c) ('a' <= (c) && (c) <= 'z')
--- 962,968 ----
    :
  else
    cat > conftest.$ac_ext <<EOF
! #line 966 "configure"
  #include "confdefs.h"
  #include <ctype.h>
  #define ISLOWER(c) ('a' <= (c) && (c) <= 'z')
*************** if (XOR (islower (i), ISLOWER (i)) || to
*** 984,990 ****
  exit (0); }
  
  EOF
! if { (eval echo configure:988: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest${ac_exeext} && (./conftest; exit) 2>/dev/null
  then
    :
  else
--- 973,979 ----
  exit (0); }
  
  EOF
! if { (eval echo configure:977: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest${ac_exeext} && (./conftest; exit) 2>/dev/null
  then
    :
  else
*************** EOF
*** 1007,1020 ****
  
  fi
  
- 
  echo $ac_n "checking for posix""... $ac_c" 1>&6
! echo "configure:1013: checking for posix" >&5
  if eval "test \"`echo '$''{'g77_cv_header_posix'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 1018 "configure"
  #include "confdefs.h"
  #include <sys/types.h>
  #include <unistd.h>
--- 996,1008 ----
  
  fi
  
  echo $ac_n "checking for posix""... $ac_c" 1>&6
! echo "configure:1001: checking for posix" >&5
  if eval "test \"`echo '$''{'g77_cv_header_posix'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 1006 "configure"
  #include "confdefs.h"
  #include <sys/types.h>
  #include <unistd.h>
*************** echo "$ac_t""$g77_cv_header_posix" 1>&6
*** 1040,1051 ****
  # We can rely on the GNU library being posix-ish.  I guess checking the 
  # header isn't actually like checking the functions, though...
  echo $ac_n "checking for GNU library""... $ac_c" 1>&6
! echo "configure:1044: checking for GNU library" >&5
  if eval "test \"`echo '$''{'g77_cv_lib_gnu'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 1049 "configure"
  #include "confdefs.h"
  #include <stdio.h>
  #ifdef __GNU_LIBRARY__
--- 1028,1039 ----
  # We can rely on the GNU library being posix-ish.  I guess checking the 
  # header isn't actually like checking the functions, though...
  echo $ac_n "checking for GNU library""... $ac_c" 1>&6
! echo "configure:1032: checking for GNU library" >&5
  if eval "test \"`echo '$''{'g77_cv_lib_gnu'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 1037 "configure"
  #include "confdefs.h"
  #include <stdio.h>
  #ifdef __GNU_LIBRARY__
*************** fi
*** 1068,1079 ****
  echo "$ac_t""$g77_cv_lib_gnu" 1>&6
  
  echo $ac_n "checking return type of signal handlers""... $ac_c" 1>&6
! echo "configure:1072: checking return type of signal handlers" >&5
  if eval "test \"`echo '$''{'ac_cv_type_signal'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 1077 "configure"
  #include "confdefs.h"
  #include <sys/types.h>
  #include <signal.h>
--- 1056,1067 ----
  echo "$ac_t""$g77_cv_lib_gnu" 1>&6
  
  echo $ac_n "checking return type of signal handlers""... $ac_c" 1>&6
! echo "configure:1060: checking return type of signal handlers" >&5
  if eval "test \"`echo '$''{'ac_cv_type_signal'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 1065 "configure"
  #include "confdefs.h"
  #include <sys/types.h>
  #include <signal.h>
*************** int main() {
*** 1090,1096 ****
  int i;
  ; return 0; }
  EOF
! if { (eval echo configure:1094: \"$ac_compile\") 1>&5; (eval $ac_compile) 2>&5; }; then
    rm -rf conftest*
    ac_cv_type_signal=void
  else
--- 1078,1084 ----
  int i;
  ; return 0; }
  EOF
! if { (eval echo configure:1082: \"$ac_compile\") 1>&5; (eval $ac_compile) 2>&5; }; then
    rm -rf conftest*
    ac_cv_type_signal=void
  else
*************** EOF
*** 1111,1122 ****
  # we'll get atexit by default
  if test $ac_cv_header_stdc != yes; then
  echo $ac_n "checking for atexit""... $ac_c" 1>&6
! echo "configure:1115: checking for atexit" >&5
  if eval "test \"`echo '$''{'ac_cv_func_atexit'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 1120 "configure"
  #include "confdefs.h"
  /* System header to define __stub macros and hopefully few prototypes,
      which can conflict with char atexit(); below.  */
--- 1099,1110 ----
  # we'll get atexit by default
  if test $ac_cv_header_stdc != yes; then
  echo $ac_n "checking for atexit""... $ac_c" 1>&6
! echo "configure:1103: checking for atexit" >&5
  if eval "test \"`echo '$''{'ac_cv_func_atexit'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 1108 "configure"
  #include "confdefs.h"
  /* System header to define __stub macros and hopefully few prototypes,
      which can conflict with char atexit(); below.  */
*************** atexit();
*** 1139,1145 ****
  
  ; return 0; }
  EOF
! if { (eval echo configure:1143: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest${ac_exeext}; then
    rm -rf conftest*
    eval "ac_cv_func_atexit=yes"
  else
--- 1127,1133 ----
  
  ; return 0; }
  EOF
! if { (eval echo configure:1131: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest${ac_exeext}; then
    rm -rf conftest*
    eval "ac_cv_func_atexit=yes"
  else
*************** else
*** 1164,1175 ****
  EOF
  
    echo $ac_n "checking for onexit""... $ac_c" 1>&6
! echo "configure:1168: checking for onexit" >&5
  if eval "test \"`echo '$''{'ac_cv_func_onexit'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 1173 "configure"
  #include "confdefs.h"
  /* System header to define __stub macros and hopefully few prototypes,
      which can conflict with char onexit(); below.  */
--- 1152,1163 ----
  EOF
  
    echo $ac_n "checking for onexit""... $ac_c" 1>&6
! echo "configure:1156: checking for onexit" >&5
  if eval "test \"`echo '$''{'ac_cv_func_onexit'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 1161 "configure"
  #include "confdefs.h"
  /* System header to define __stub macros and hopefully few prototypes,
      which can conflict with char onexit(); below.  */
*************** onexit();
*** 1192,1198 ****
  
  ; return 0; }
  EOF
! if { (eval echo configure:1196: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest${ac_exeext}; then
    rm -rf conftest*
    eval "ac_cv_func_onexit=yes"
  else
--- 1180,1186 ----
  
  ; return 0; }
  EOF
! if { (eval echo configure:1184: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest${ac_exeext}; then
    rm -rf conftest*
    eval "ac_cv_func_onexit=yes"
  else
*************** if eval "test \"`echo '$ac_cv_func_'onex
*** 1210,1221 ****
  else
    echo "$ac_t""no" 1>&6
  echo $ac_n "checking for on_exit""... $ac_c" 1>&6
! echo "configure:1214: checking for on_exit" >&5
  if eval "test \"`echo '$''{'ac_cv_func_on_exit'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 1219 "configure"
  #include "confdefs.h"
  /* System header to define __stub macros and hopefully few prototypes,
      which can conflict with char on_exit(); below.  */
--- 1198,1209 ----
  else
    echo "$ac_t""no" 1>&6
  echo $ac_n "checking for on_exit""... $ac_c" 1>&6
! echo "configure:1202: checking for on_exit" >&5
  if eval "test \"`echo '$''{'ac_cv_func_on_exit'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 1207 "configure"
  #include "confdefs.h"
  /* System header to define __stub macros and hopefully few prototypes,
      which can conflict with char on_exit(); below.  */
*************** on_exit();
*** 1238,1244 ****
  
  ; return 0; }
  EOF
! if { (eval echo configure:1242: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest${ac_exeext}; then
    rm -rf conftest*
    eval "ac_cv_func_on_exit=yes"
  else
--- 1226,1232 ----
  
  ; return 0; }
  EOF
! if { (eval echo configure:1230: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest${ac_exeext}; then
    rm -rf conftest*
    eval "ac_cv_func_on_exit=yes"
  else
*************** else true
*** 1268,1274 ****
  fi
  
  echo $ac_n "checking for drem in -lm""... $ac_c" 1>&6
! echo "configure:1272: checking for drem in -lm" >&5
  ac_lib_var=`echo m'_'drem | sed 'y%./+-%__p_%'`
  if eval "test \"`echo '$''{'ac_cv_lib_$ac_lib_var'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
--- 1256,1262 ----
  fi
  
  echo $ac_n "checking for drem in -lm""... $ac_c" 1>&6
! echo "configure:1260: checking for drem in -lm" >&5
  ac_lib_var=`echo m'_'drem | sed 'y%./+-%__p_%'`
  if eval "test \"`echo '$''{'ac_cv_lib_$ac_lib_var'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
*************** else
*** 1276,1282 ****
    ac_save_LIBS="$LIBS"
  LIBS="-lm  $LIBS"
  cat > conftest.$ac_ext <<EOF
! #line 1280 "configure"
  #include "confdefs.h"
  /* Override any gcc2 internal prototype to avoid an error.  */
  /* We use char because int might match the return type of a gcc2
--- 1264,1270 ----
    ac_save_LIBS="$LIBS"
  LIBS="-lm  $LIBS"
  cat > conftest.$ac_ext <<EOF
! #line 1268 "configure"
  #include "confdefs.h"
  /* Override any gcc2 internal prototype to avoid an error.  */
  /* We use char because int might match the return type of a gcc2
*************** int main() {
*** 1287,1293 ****
  drem()
  ; return 0; }
  EOF
! if { (eval echo configure:1291: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest${ac_exeext}; then
    rm -rf conftest*
    eval "ac_cv_lib_$ac_lib_var=yes"
  else
--- 1275,1281 ----
  drem()
  ; return 0; }
  EOF
! if { (eval echo configure:1279: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest${ac_exeext}; then
    rm -rf conftest*
    eval "ac_cv_lib_$ac_lib_var=yes"
  else
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/configure.in gcc-3.3/libf2c/libF77/configure.in
*** gcc-3.2.3/libf2c/libF77/configure.in	2001-12-04 09:53:17.000000000 +0000
--- gcc-3.3/libf2c/libF77/configure.in	2002-06-01 01:53:50.000000000 +0000
*************** the G77 runtime system.  If necessary, i
*** 56,72 ****
  then the target library, then build with \`LANGUAGES=f77'.])])
  
  AC_HEADER_STDC
- dnl We could do this if we didn't know we were using gcc
- dnl AC_MSG_CHECKING(for prototype-savvy compiler)
- dnl AC_CACHE_VAL(g77_cv_sys_proto,                
- dnl   [AC_TRY_LINK(,                             
- dnl dnl looks screwy because TRY_LINK expects a function body
- dnl    [return 0;} int foo (int * bar) {],       
- dnl    g77_cv_sys_proto=yes,                      
- dnl    [g77_cv_sys_proto=no                       
- dnl     AC_DEFINE(KR_headers)])])                
- dnl AC_MSG_RESULT($g77_cv_sys_proto)              
- 
  AC_MSG_CHECKING(for posix)
  AC_CACHE_VAL(g77_cv_header_posix,
    AC_EGREP_CPP(yes,
--- 56,61 ----
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/c_sin.c gcc-3.3/libf2c/libF77/c_sin.c
*** gcc-3.2.3/libf2c/libF77/c_sin.c	1999-05-03 08:35:09.000000000 +0000
--- gcc-3.3/libf2c/libF77/c_sin.c	2002-06-01 12:38:27.000000000 +0000
***************
*** 1,17 ****
  #include "f2c.h"
  
- #ifdef KR_headers
- extern double sin(), cos(), sinh(), cosh();
- 
- VOID c_sin(r, z) complex *r, *z;
- #else
  #undef abs
  #include "math.h"
  
! void c_sin(complex *r, complex *z)
! #endif
  {
! 	double zi = z->i, zr = z->r;
! 	r->r = sin(zr) * cosh(zi);
! 	r->i = cos(zr) * sinh(zi);
! 	}
--- 1,12 ----
  #include "f2c.h"
  
  #undef abs
  #include "math.h"
  
! void
! c_sin (complex * r, complex * z)
  {
!   double zi = z->i, zr = z->r;
!   r->r = sin (zr) * cosh (zi);
!   r->i = cos (zr) * sinh (zi);
! }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/c_sqrt.c gcc-3.3/libf2c/libF77/c_sqrt.c
*** gcc-3.2.3/libf2c/libF77/c_sqrt.c	1999-05-03 08:33:12.000000000 +0000
--- gcc-3.3/libf2c/libF77/c_sqrt.c	2002-06-01 12:38:27.000000000 +0000
***************
*** 1,35 ****
  #include "f2c.h"
  
- #ifdef KR_headers
- extern double sqrt(), f__cabs();
- 
- VOID c_sqrt(r, z) complex *r, *z;
- #else
  #undef abs
  #include "math.h"
! extern double f__cabs(double, double);
  
! void c_sqrt(complex *r, complex *z)
! #endif
  {
! 	double mag, t;
! 	double zi = z->i, zr = z->r;
  
! 	if( (mag = f__cabs(zr, zi)) == 0.)
! 		r->r = r->i = 0.;
! 	else if(zr > 0)
! 		{
! 		r->r = t = sqrt(0.5 * (mag + zr) );
! 		t = zi / t;
! 		r->i = 0.5 * t;
! 		}
! 	else
! 		{
! 		t = sqrt(0.5 * (mag - zr) );
! 		if(zi < 0)
! 			t = -t;
! 		r->i = t;
! 		t = zi / t;
! 		r->r = 0.5 * t;
! 		}
! 	}
--- 1,30 ----
  #include "f2c.h"
  
  #undef abs
  #include "math.h"
! extern double f__cabs (double, double);
  
! void
! c_sqrt (complex * r, complex * z)
  {
!   double mag, t;
!   double zi = z->i, zr = z->r;
  
!   if ((mag = f__cabs (zr, zi)) == 0.)
!     r->r = r->i = 0.;
!   else if (zr > 0)
!     {
!       r->r = t = sqrt (0.5 * (mag + zr));
!       t = zi / t;
!       r->i = 0.5 * t;
!     }
!   else
!     {
!       t = sqrt (0.5 * (mag - zr));
!       if (zi < 0)
! 	t = -t;
!       r->i = t;
!       t = zi / t;
!       r->r = 0.5 * t;
!     }
! }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/d_abs.c gcc-3.3/libf2c/libF77/d_abs.c
*** gcc-3.2.3/libf2c/libF77/d_abs.c	1999-09-04 15:09:16.000000000 +0000
--- gcc-3.3/libf2c/libF77/d_abs.c	2002-06-01 12:38:27.000000000 +0000
***************
*** 1,12 ****
  #include "f2c.h"
  
! #ifdef KR_headers
! double d_abs(x) doublereal *x;
! #else
! double d_abs(doublereal *x)
! #endif
  {
! if(*x >= 0)
! 	return(*x);
! return(- *x);
  }
--- 1,9 ----
  #include "f2c.h"
  
! double
! d_abs (doublereal * x)
  {
!   if (*x >= 0)
!     return (*x);
!   return (-*x);
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/d_acos.c gcc-3.3/libf2c/libF77/d_acos.c
*** gcc-3.2.3/libf2c/libF77/d_acos.c	1999-09-04 15:09:16.000000000 +0000
--- gcc-3.3/libf2c/libF77/d_acos.c	2002-06-01 12:38:27.000000000 +0000
***************
*** 1,13 ****
  #include "f2c.h"
  
- #ifdef KR_headers
- double acos();
- double d_acos(x) doublereal *x;
- #else
  #undef abs
  #include <math.h>
! double d_acos(doublereal *x)
! #endif
  {
! return( acos(*x) );
  }
--- 1,9 ----
  #include "f2c.h"
  
  #undef abs
  #include <math.h>
! double
! d_acos (doublereal * x)
  {
!   return (acos (*x));
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/d_asin.c gcc-3.3/libf2c/libF77/d_asin.c
*** gcc-3.2.3/libf2c/libF77/d_asin.c	1999-09-04 15:09:16.000000000 +0000
--- gcc-3.3/libf2c/libF77/d_asin.c	2002-06-01 12:38:27.000000000 +0000
***************
*** 1,13 ****
  #include "f2c.h"
  
- #ifdef KR_headers
- double asin();
- double d_asin(x) doublereal *x;
- #else
  #undef abs
  #include <math.h>
! double d_asin(doublereal *x)
! #endif
  {
! return( asin(*x) );
  }
--- 1,9 ----
  #include "f2c.h"
  
  #undef abs
  #include <math.h>
! double
! d_asin (doublereal * x)
  {
!   return (asin (*x));
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/d_atan.c gcc-3.3/libf2c/libF77/d_atan.c
*** gcc-3.2.3/libf2c/libF77/d_atan.c	1999-09-04 15:09:16.000000000 +0000
--- gcc-3.3/libf2c/libF77/d_atan.c	2002-06-01 12:38:27.000000000 +0000
***************
*** 1,13 ****
  #include "f2c.h"
  
- #ifdef KR_headers
- double atan();
- double d_atan(x) doublereal *x;
- #else
  #undef abs
  #include <math.h>
! double d_atan(doublereal *x)
! #endif
  {
! return( atan(*x) );
  }
--- 1,9 ----
  #include "f2c.h"
  
  #undef abs
  #include <math.h>
! double
! d_atan (doublereal * x)
  {
!   return (atan (*x));
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/d_atn2.c gcc-3.3/libf2c/libF77/d_atn2.c
*** gcc-3.2.3/libf2c/libF77/d_atn2.c	1999-09-04 15:09:16.000000000 +0000
--- gcc-3.3/libf2c/libF77/d_atn2.c	2002-06-01 12:38:27.000000000 +0000
***************
*** 1,13 ****
  #include "f2c.h"
  
- #ifdef KR_headers
- double atan2();
- double d_atn2(x,y) doublereal *x, *y;
- #else
  #undef abs
  #include <math.h>
! double d_atn2(doublereal *x, doublereal *y)
! #endif
  {
! return( atan2(*x,*y) );
  }
--- 1,9 ----
  #include "f2c.h"
  
  #undef abs
  #include <math.h>
! double
! d_atn2 (doublereal * x, doublereal * y)
  {
!   return (atan2 (*x, *y));
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/d_cnjg.c gcc-3.3/libf2c/libF77/d_cnjg.c
*** gcc-3.2.3/libf2c/libF77/d_cnjg.c	1999-05-03 08:35:10.000000000 +0000
--- gcc-3.3/libf2c/libF77/d_cnjg.c	2002-06-01 12:38:27.000000000 +0000
***************
*** 1,13 ****
  #include "f2c.h"
  
!  VOID
! #ifdef KR_headers
! d_cnjg(r, z) doublecomplex *r, *z;
! #else
! d_cnjg(doublecomplex *r, doublecomplex *z)
! #endif
  {
! 	doublereal zi = z->i;
! 	r->r = z->r;
! 	r->i = -zi;
! 	}
--- 1,9 ----
  #include "f2c.h"
  
! void
! d_cnjg (doublecomplex * r, doublecomplex * z)
  {
!   doublereal zi = z->i;
!   r->r = z->r;
!   r->i = -zi;
! }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/d_cos.c gcc-3.3/libf2c/libF77/d_cos.c
*** gcc-3.2.3/libf2c/libF77/d_cos.c	1999-09-04 15:09:16.000000000 +0000
--- gcc-3.3/libf2c/libF77/d_cos.c	2002-06-01 12:38:27.000000000 +0000
***************
*** 1,13 ****
  #include "f2c.h"
  
- #ifdef KR_headers
- double cos();
- double d_cos(x) doublereal *x;
- #else
  #undef abs
  #include <math.h>
! double d_cos(doublereal *x)
! #endif
  {
! return( cos(*x) );
  }
--- 1,9 ----
  #include "f2c.h"
  
  #undef abs
  #include <math.h>
! double
! d_cos (doublereal * x)
  {
!   return (cos (*x));
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/d_cosh.c gcc-3.3/libf2c/libF77/d_cosh.c
*** gcc-3.2.3/libf2c/libF77/d_cosh.c	1999-09-04 15:09:16.000000000 +0000
--- gcc-3.3/libf2c/libF77/d_cosh.c	2002-06-01 12:38:27.000000000 +0000
***************
*** 1,13 ****
  #include "f2c.h"
  
- #ifdef KR_headers
- double cosh();
- double d_cosh(x) doublereal *x;
- #else
  #undef abs
  #include <math.h>
! double d_cosh(doublereal *x)
! #endif
  {
! return( cosh(*x) );
  }
--- 1,9 ----
  #include "f2c.h"
  
  #undef abs
  #include <math.h>
! double
! d_cosh (doublereal * x)
  {
!   return (cosh (*x));
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/d_dim.c gcc-3.3/libf2c/libF77/d_dim.c
*** gcc-3.2.3/libf2c/libF77/d_dim.c	1999-09-04 15:09:16.000000000 +0000
--- gcc-3.3/libf2c/libF77/d_dim.c	2002-06-01 12:38:27.000000000 +0000
***************
*** 1,10 ****
  #include "f2c.h"
  
! #ifdef KR_headers
! double d_dim(a,b) doublereal *a, *b;
! #else
! double d_dim(doublereal *a, doublereal *b)
! #endif
  {
! return( *a > *b ? *a - *b : 0);
  }
--- 1,7 ----
  #include "f2c.h"
  
! double
! d_dim (doublereal * a, doublereal * b)
  {
!   return (*a > *b ? *a - *b : 0);
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/derf_.c gcc-3.3/libf2c/libF77/derf_.c
*** gcc-3.2.3/libf2c/libF77/derf_.c	1999-09-04 15:09:16.000000000 +0000
--- gcc-3.3/libf2c/libF77/derf_.c	2002-06-01 12:38:27.000000000 +0000
***************
*** 1,12 ****
  #include "f2c.h"
  
! #ifdef KR_headers
! double erf();
! double G77_derf_0 (x) doublereal *x;
! #else
! extern double erf(double);
! double G77_derf_0 (doublereal *x)
! #endif
  {
! return( erf(*x) );
  }
--- 1,8 ----
  #include "f2c.h"
  
! extern double erf (double);
! double
! G77_derf_0 (doublereal * x)
  {
!   return (erf (*x));
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/derfc_.c gcc-3.3/libf2c/libF77/derfc_.c
*** gcc-3.2.3/libf2c/libF77/derfc_.c	1999-09-04 15:09:16.000000000 +0000
--- gcc-3.3/libf2c/libF77/derfc_.c	2002-06-01 12:38:27.000000000 +0000
***************
*** 1,14 ****
  #include "f2c.h"
  
! #ifdef KR_headers
! extern double erfc();
! 
! double G77_derfc_0 (x) doublereal *x;
! #else
! extern double erfc(double);
  
! double G77_derfc_0 (doublereal *x)
! #endif
  {
! return( erfc(*x) );
  }
--- 1,9 ----
  #include "f2c.h"
  
! extern double erfc (double);
  
! double
! G77_derfc_0 (doublereal * x)
  {
!   return (erfc (*x));
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/d_exp.c gcc-3.3/libf2c/libF77/d_exp.c
*** gcc-3.2.3/libf2c/libF77/d_exp.c	1999-09-04 15:09:16.000000000 +0000
--- gcc-3.3/libf2c/libF77/d_exp.c	2002-06-01 12:38:27.000000000 +0000
***************
*** 1,13 ****
  #include "f2c.h"
  
- #ifdef KR_headers
- double exp();
- double d_exp(x) doublereal *x;
- #else
  #undef abs
  #include <math.h>
! double d_exp(doublereal *x)
! #endif
  {
! return( exp(*x) );
  }
--- 1,9 ----
  #include "f2c.h"
  
  #undef abs
  #include <math.h>
! double
! d_exp (doublereal * x)
  {
!   return (exp (*x));
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/d_imag.c gcc-3.3/libf2c/libF77/d_imag.c
*** gcc-3.2.3/libf2c/libF77/d_imag.c	1999-09-04 15:09:16.000000000 +0000
--- gcc-3.3/libf2c/libF77/d_imag.c	2002-06-01 12:38:27.000000000 +0000
***************
*** 1,10 ****
  #include "f2c.h"
  
! #ifdef KR_headers
! double d_imag(z) doublecomplex *z;
! #else
! double d_imag(doublecomplex *z)
! #endif
  {
! return(z->i);
  }
--- 1,7 ----
  #include "f2c.h"
  
! double
! d_imag (doublecomplex * z)
  {
!   return (z->i);
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/d_int.c gcc-3.3/libf2c/libF77/d_int.c
*** gcc-3.2.3/libf2c/libF77/d_int.c	1999-09-04 15:09:16.000000000 +0000
--- gcc-3.3/libf2c/libF77/d_int.c	2002-06-01 12:38:27.000000000 +0000
***************
*** 1,13 ****
  #include "f2c.h"
  
- #ifdef KR_headers
- double floor();
- double d_int(x) doublereal *x;
- #else
  #undef abs
  #include <math.h>
! double d_int(doublereal *x)
! #endif
  {
! return( (*x>0) ? floor(*x) : -floor(- *x) );
  }
--- 1,9 ----
  #include "f2c.h"
  
  #undef abs
  #include <math.h>
! double
! d_int (doublereal * x)
  {
!   return ((*x > 0) ? floor (*x) : -floor (-*x));
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/d_lg10.c gcc-3.3/libf2c/libF77/d_lg10.c
*** gcc-3.2.3/libf2c/libF77/d_lg10.c	1999-09-04 15:09:16.000000000 +0000
--- gcc-3.3/libf2c/libF77/d_lg10.c	2002-06-01 12:38:27.000000000 +0000
***************
*** 2,15 ****
  
  #define log10e 0.43429448190325182765
  
- #ifdef KR_headers
- double log();
- double d_lg10(x) doublereal *x;
- #else
  #undef abs
  #include <math.h>
! double d_lg10(doublereal *x)
! #endif
  {
! return( log10e * log(*x) );
  }
--- 2,11 ----
  
  #define log10e 0.43429448190325182765
  
  #undef abs
  #include <math.h>
! double
! d_lg10 (doublereal * x)
  {
!   return (log10e * log (*x));
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/d_log.c gcc-3.3/libf2c/libF77/d_log.c
*** gcc-3.2.3/libf2c/libF77/d_log.c	1999-09-04 15:09:16.000000000 +0000
--- gcc-3.3/libf2c/libF77/d_log.c	2002-06-01 12:38:27.000000000 +0000
***************
*** 1,13 ****
  #include "f2c.h"
  
- #ifdef KR_headers
- double log();
- double d_log(x) doublereal *x;
- #else
  #undef abs
  #include <math.h>
! double d_log(doublereal *x)
! #endif
  {
! return( log(*x) );
  }
--- 1,9 ----
  #include "f2c.h"
  
  #undef abs
  #include <math.h>
! double
! d_log (doublereal * x)
  {
!   return (log (*x));
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/d_mod.c gcc-3.3/libf2c/libF77/d_mod.c
*** gcc-3.2.3/libf2c/libF77/d_mod.c	1999-09-04 15:09:16.000000000 +0000
--- gcc-3.3/libf2c/libF77/d_mod.c	2002-06-01 12:38:27.000000000 +0000
***************
*** 1,40 ****
  #include "f2c.h"
  
- #ifdef KR_headers
  #ifdef IEEE_drem
! double drem();
! #else
! double floor();
! #endif
! double d_mod(x,y) doublereal *x, *y;
! #else
! #ifdef IEEE_drem
! double drem(double, double);
  #else
  #undef abs
  #include <math.h>
  #endif
! double d_mod(doublereal *x, doublereal *y)
! #endif
  {
  #ifdef IEEE_drem
! 	double xa, ya, z;
! 	if ((ya = *y) < 0.)
! 		ya = -ya;
! 	z = drem(xa = *x, ya);
! 	if (xa > 0) {
! 		if (z < 0)
! 			z += ya;
! 		}
! 	else if (z > 0)
! 		z -= ya;
! 	return z;
  #else
! 	double quotient;
! 	if( (quotient = *x / *y) >= 0)
! 		quotient = floor(quotient);
! 	else
! 		quotient = -floor(-quotient);
! 	return(*x - (*y) * quotient );
  #endif
  }
--- 1,33 ----
  #include "f2c.h"
  
  #ifdef IEEE_drem
! double drem (double, double);
  #else
  #undef abs
  #include <math.h>
  #endif
! double
! d_mod (doublereal * x, doublereal * y)
  {
  #ifdef IEEE_drem
!   double xa, ya, z;
!   if ((ya = *y) < 0.)
!     ya = -ya;
!   z = drem (xa = *x, ya);
!   if (xa > 0)
!     {
!       if (z < 0)
! 	z += ya;
!     }
!   else if (z > 0)
!     z -= ya;
!   return z;
  #else
!   double quotient;
!   if ((quotient = *x / *y) >= 0)
!     quotient = floor (quotient);
!   else
!     quotient = -floor (-quotient);
!   return (*x - (*y) * quotient);
  #endif
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/d_nint.c gcc-3.3/libf2c/libF77/d_nint.c
*** gcc-3.2.3/libf2c/libF77/d_nint.c	1999-09-04 15:09:16.000000000 +0000
--- gcc-3.3/libf2c/libF77/d_nint.c	2002-06-01 12:38:27.000000000 +0000
***************
*** 1,14 ****
  #include "f2c.h"
  
- #ifdef KR_headers
- double floor();
- double d_nint(x) doublereal *x;
- #else
  #undef abs
  #include <math.h>
! double d_nint(doublereal *x)
! #endif
  {
! return( (*x)>=0 ?
! 	floor(*x + .5) : -floor(.5 - *x) );
  }
--- 1,9 ----
  #include "f2c.h"
  
  #undef abs
  #include <math.h>
! double
! d_nint (doublereal * x)
  {
!   return ((*x) >= 0 ? floor (*x + .5) : -floor (.5 - *x));
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/d_prod.c gcc-3.3/libf2c/libF77/d_prod.c
*** gcc-3.2.3/libf2c/libF77/d_prod.c	1999-09-04 15:09:16.000000000 +0000
--- gcc-3.3/libf2c/libF77/d_prod.c	2002-06-01 12:38:27.000000000 +0000
***************
*** 1,10 ****
  #include "f2c.h"
  
! #ifdef KR_headers
! double d_prod(x,y) real *x, *y;
! #else
! double d_prod(real *x, real *y)
! #endif
  {
! return( (*x) * (*y) );
  }
--- 1,7 ----
  #include "f2c.h"
  
! double
! d_prod (real * x, real * y)
  {
!   return ((*x) * (*y));
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/d_sign.c gcc-3.3/libf2c/libF77/d_sign.c
*** gcc-3.2.3/libf2c/libF77/d_sign.c	1999-09-04 15:09:16.000000000 +0000
--- gcc-3.3/libf2c/libF77/d_sign.c	2002-06-01 12:38:27.000000000 +0000
***************
*** 1,12 ****
  #include "f2c.h"
  
! #ifdef KR_headers
! double d_sign(a,b) doublereal *a, *b;
! #else
! double d_sign(doublereal *a, doublereal *b)
! #endif
  {
! double x;
! x = (*a >= 0 ? *a : - *a);
! return( *b >= 0 ? x : -x);
  }
--- 1,9 ----
  #include "f2c.h"
  
! double
! d_sign (doublereal * a, doublereal * b)
  {
!   double x;
!   x = (*a >= 0 ? *a : -*a);
!   return (*b >= 0 ? x : -x);
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/d_sin.c gcc-3.3/libf2c/libF77/d_sin.c
*** gcc-3.2.3/libf2c/libF77/d_sin.c	1999-09-04 15:09:16.000000000 +0000
--- gcc-3.3/libf2c/libF77/d_sin.c	2002-06-01 12:38:27.000000000 +0000
***************
*** 1,13 ****
  #include "f2c.h"
  
- #ifdef KR_headers
- double sin();
- double d_sin(x) doublereal *x;
- #else
  #undef abs
  #include <math.h>
! double d_sin(doublereal *x)
! #endif
  {
! return( sin(*x) );
  }
--- 1,9 ----
  #include "f2c.h"
  
  #undef abs
  #include <math.h>
! double
! d_sin (doublereal * x)
  {
!   return (sin (*x));
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/d_sinh.c gcc-3.3/libf2c/libF77/d_sinh.c
*** gcc-3.2.3/libf2c/libF77/d_sinh.c	1999-09-04 15:09:16.000000000 +0000
--- gcc-3.3/libf2c/libF77/d_sinh.c	2002-06-01 12:38:27.000000000 +0000
***************
*** 1,13 ****
  #include "f2c.h"
  
- #ifdef KR_headers
- double sinh();
- double d_sinh(x) doublereal *x;
- #else
  #undef abs
  #include <math.h>
! double d_sinh(doublereal *x)
! #endif
  {
! return( sinh(*x) );
  }
--- 1,9 ----
  #include "f2c.h"
  
  #undef abs
  #include <math.h>
! double
! d_sinh (doublereal * x)
  {
!   return (sinh (*x));
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/d_sqrt.c gcc-3.3/libf2c/libF77/d_sqrt.c
*** gcc-3.2.3/libf2c/libF77/d_sqrt.c	1999-09-04 15:09:16.000000000 +0000
--- gcc-3.3/libf2c/libF77/d_sqrt.c	2002-06-01 12:38:27.000000000 +0000
***************
*** 1,13 ****
  #include "f2c.h"
  
- #ifdef KR_headers
- double sqrt();
- double d_sqrt(x) doublereal *x;
- #else
  #undef abs
  #include <math.h>
! double d_sqrt(doublereal *x)
! #endif
  {
! return( sqrt(*x) );
  }
--- 1,9 ----
  #include "f2c.h"
  
  #undef abs
  #include <math.h>
! double
! d_sqrt (doublereal * x)
  {
!   return (sqrt (*x));
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/d_tan.c gcc-3.3/libf2c/libF77/d_tan.c
*** gcc-3.2.3/libf2c/libF77/d_tan.c	1999-09-04 15:09:16.000000000 +0000
--- gcc-3.3/libf2c/libF77/d_tan.c	2002-06-01 12:38:27.000000000 +0000
***************
*** 1,13 ****
  #include "f2c.h"
  
- #ifdef KR_headers
- double tan();
- double d_tan(x) doublereal *x;
- #else
  #undef abs
  #include <math.h>
! double d_tan(doublereal *x)
! #endif
  {
! return( tan(*x) );
  }
--- 1,9 ----
  #include "f2c.h"
  
  #undef abs
  #include <math.h>
! double
! d_tan (doublereal * x)
  {
!   return (tan (*x));
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/d_tanh.c gcc-3.3/libf2c/libF77/d_tanh.c
*** gcc-3.2.3/libf2c/libF77/d_tanh.c	1999-09-04 15:09:16.000000000 +0000
--- gcc-3.3/libf2c/libF77/d_tanh.c	2002-06-01 12:38:27.000000000 +0000
***************
*** 1,13 ****
  #include "f2c.h"
  
- #ifdef KR_headers
- double tanh();
- double d_tanh(x) doublereal *x;
- #else
  #undef abs
  #include <math.h>
! double d_tanh(doublereal *x)
! #endif
  {
! return( tanh(*x) );
  }
--- 1,9 ----
  #include "f2c.h"
  
  #undef abs
  #include <math.h>
! double
! d_tanh (doublereal * x)
  {
!   return (tanh (*x));
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/dtime_.c gcc-3.3/libf2c/libF77/dtime_.c
*** gcc-3.2.3/libf2c/libF77/dtime_.c	2000-12-09 15:34:53.000000000 +0000
--- gcc-3.3/libf2c/libF77/dtime_.c	2002-06-01 12:38:27.000000000 +0000
***************
*** 23,53 ****
  #endif
  #endif
  
!  double
! #ifdef KR_headers
! dtime_(tarray) float *tarray;
! #else
! dtime_(float *tarray)
! #endif
  {
  #ifdef USE_CLOCK
  #ifndef CLOCKS_PER_SECOND
  #define CLOCKS_PER_SECOND Hz
  #endif
! 	static double t0;
! 	double t = clock();
! 	tarray[1] = 0;
! 	tarray[0] = (t - t0) / CLOCKS_PER_SECOND;
! 	t0 = t;
! 	return tarray[0];
  #else
! 	struct tms t;
! 	static struct tms t0;
  
! 	times(&t);
! 	tarray[0] = (double)(t.tms_utime - t0.tms_utime) / Hz;
! 	tarray[1] = (double)(t.tms_stime - t0.tms_stime) / Hz;
! 	t0 = t;
! 	return tarray[0] + tarray[1];
  #endif
! 	}
--- 23,49 ----
  #endif
  #endif
  
! double
! dtime_ (float *tarray)
  {
  #ifdef USE_CLOCK
  #ifndef CLOCKS_PER_SECOND
  #define CLOCKS_PER_SECOND Hz
  #endif
!   static double t0;
!   double t = clock ();
!   tarray[1] = 0;
!   tarray[0] = (t - t0) / CLOCKS_PER_SECOND;
!   t0 = t;
!   return tarray[0];
  #else
!   struct tms t;
!   static struct tms t0;
  
!   times (&t);
!   tarray[0] = (double) (t.tms_utime - t0.tms_utime) / Hz;
!   tarray[1] = (double) (t.tms_stime - t0.tms_stime) / Hz;
!   t0 = t;
!   return tarray[0] + tarray[1];
  #endif
! }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/ef1asc_.c gcc-3.3/libf2c/libF77/ef1asc_.c
*** gcc-3.2.3/libf2c/libF77/ef1asc_.c	1999-05-10 14:40:54.000000000 +0000
--- gcc-3.3/libf2c/libF77/ef1asc_.c	2002-06-01 12:38:27.000000000 +0000
***************
*** 6,19 ****
  #define M	( (long) (sizeof(long) - 1) )
  #define EVEN(x)	( ( (x)+ M) & (~M) )
  
! #ifdef KR_headers
! extern VOID s_copy();
! G77_ef1asc_0 (a, la, b, lb) ftnint *a, *b; ftnlen *la, *lb;
! #else
! extern void s_copy(char*,char*,ftnlen,ftnlen);
! int G77_ef1asc_0 (ftnint *a, ftnlen *la, ftnint *b, ftnlen *lb)
! #endif
  {
! s_copy( (char *)a, (char *)b, EVEN(*la), *lb );
! return 0;	/* ignored return value */
  }
--- 6,15 ----
  #define M	( (long) (sizeof(long) - 1) )
  #define EVEN(x)	( ( (x)+ M) & (~M) )
  
! extern void s_copy (char *, char *, ftnlen, ftnlen);
! int
! G77_ef1asc_0 (ftnint * a, ftnlen * la, ftnint * b, ftnlen * lb)
  {
!   s_copy ((char *) a, (char *) b, EVEN (*la), *lb);
!   return 0;			/* ignored return value */
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/ef1cmc_.c gcc-3.3/libf2c/libF77/ef1cmc_.c
*** gcc-3.2.3/libf2c/libF77/ef1cmc_.c	1999-09-04 15:09:16.000000000 +0000
--- gcc-3.3/libf2c/libF77/ef1cmc_.c	2002-06-01 12:38:27.000000000 +0000
***************
*** 2,14 ****
  
  #include "f2c.h"
  
! #ifdef KR_headers
! extern integer s_cmp();
! integer G77_ef1cmc_0 (a, la, b, lb) ftnint *a, *b; ftnlen *la, *lb;
! #else
! extern integer s_cmp(char*,char*,ftnlen,ftnlen);
! integer G77_ef1cmc_0 (ftnint *a, ftnlen *la, ftnint *b, ftnlen *lb)
! #endif
  {
! return( s_cmp( (char *)a, (char *)b, *la, *lb) );
  }
--- 2,10 ----
  
  #include "f2c.h"
  
! extern integer s_cmp (char *, char *, ftnlen, ftnlen);
! integer
! G77_ef1cmc_0 (ftnint * a, ftnlen * la, ftnint * b, ftnlen * lb)
  {
!   return (s_cmp ((char *) a, (char *) b, *la, *lb));
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/erf_.c gcc-3.3/libf2c/libF77/erf_.c
*** gcc-3.2.3/libf2c/libF77/erf_.c	1999-09-04 15:09:16.000000000 +0000
--- gcc-3.3/libf2c/libF77/erf_.c	2002-06-01 12:38:27.000000000 +0000
***************
*** 1,12 ****
  #include "f2c.h"
  
! #ifdef KR_headers
! double erf();
! double G77_erf_0 (x) real *x;
! #else
! extern double erf(double);
! double G77_erf_0 (real *x)
! #endif
  {
! return( erf(*x) );
  }
--- 1,8 ----
  #include "f2c.h"
  
! extern double erf (double);
! double
! G77_erf_0 (real * x)
  {
!   return (erf (*x));
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/erfc_.c gcc-3.3/libf2c/libF77/erfc_.c
*** gcc-3.2.3/libf2c/libF77/erfc_.c	1999-09-04 15:09:16.000000000 +0000
--- gcc-3.3/libf2c/libF77/erfc_.c	2002-06-01 12:38:27.000000000 +0000
***************
*** 1,12 ****
  #include "f2c.h"
  
! #ifdef KR_headers
! double erfc();
! double G77_erfc_0 (x) real *x;
! #else
! extern double erfc(double);
! double G77_erfc_0 (real *x)
! #endif
  {
! return( erfc(*x) );
  }
--- 1,8 ----
  #include "f2c.h"
  
! extern double erfc (double);
! double
! G77_erfc_0 (real * x)
  {
!   return (erfc (*x));
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/etime_.c gcc-3.3/libf2c/libF77/etime_.c
*** gcc-3.2.3/libf2c/libF77/etime_.c	2000-12-09 15:34:53.000000000 +0000
--- gcc-3.3/libf2c/libF77/etime_.c	2002-06-01 12:38:27.000000000 +0000
***************
*** 23,47 ****
  #endif
  #endif
  
!  double
! #ifdef KR_headers
! etime_(tarray) float *tarray;
! #else
! etime_(float *tarray)
! #endif
  {
  #ifdef USE_CLOCK
  #ifndef CLOCKS_PER_SECOND
  #define CLOCKS_PER_SECOND Hz
  #endif
! 	double t = clock();
! 	tarray[1] = 0;
! 	return tarray[0] = t / CLOCKS_PER_SECOND;
  #else
! 	struct tms t;
  
! 	times(&t);
! 	return	  (tarray[0] = (double)t.tms_utime/Hz)
! 		+ (tarray[1] = (double)t.tms_stime/Hz);
  #endif
! 	}
--- 23,43 ----
  #endif
  #endif
  
! double
! etime_ (float *tarray)
  {
  #ifdef USE_CLOCK
  #ifndef CLOCKS_PER_SECOND
  #define CLOCKS_PER_SECOND Hz
  #endif
!   double t = clock ();
!   tarray[1] = 0;
!   return tarray[0] = t / CLOCKS_PER_SECOND;
  #else
!   struct tms t;
  
!   times (&t);
!   return (tarray[0] = (double) t.tms_utime / Hz)
!     + (tarray[1] = (double) t.tms_stime / Hz);
  #endif
! }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/exit_.c gcc-3.3/libf2c/libF77/exit_.c
*** gcc-3.2.3/libf2c/libF77/exit_.c	1999-09-04 15:09:16.000000000 +0000
--- gcc-3.3/libf2c/libF77/exit_.c	2002-06-01 12:38:27.000000000 +0000
***************
*** 12,37 ****
  #undef abs
  #undef min
  #undef max
- #ifndef KR_headers
  #include <stdlib.h>
! #ifdef __cplusplus
! extern "C" {
! #endif
! extern void f_exit(void);
! #endif
  
!  void
! #ifdef KR_headers
! G77_exit_0 (rc) integer *rc;
! #else
! G77_exit_0 (integer *rc)
! #endif
  {
  #ifdef NO_ONEXIT
! 	f_exit();
  #endif
! 	exit(*rc);
! 	}
! #ifdef __cplusplus
  }
- #endif
--- 12,25 ----
  #undef abs
  #undef min
  #undef max
  #include <stdlib.h>
! extern void f_exit (void);
  
! void
! G77_exit_0 (integer * rc)
  {
  #ifdef NO_ONEXIT
!   f_exit ();
  #endif
!   exit (*rc);
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/f2ch.add gcc-3.3/libf2c/libF77/f2ch.add
*** gcc-3.2.3/libf2c/libF77/f2ch.add	1999-09-04 15:09:16.000000000 +0000
--- gcc-3.3/libf2c/libF77/f2ch.add	2002-06-01 12:38:27.000000000 +0000
***************
*** 2,162 ****
     for compiling libF77 and libI77. */
  
  #ifdef __cplusplus
! extern "C" {
! extern int abort_(void);
! extern double c_abs(complex *);
! extern void c_cos(complex *, complex *);
! extern void c_div(complex *, complex *, complex *);
! extern void c_exp(complex *, complex *);
! extern void c_log(complex *, complex *);
! extern void c_sin(complex *, complex *);
! extern void c_sqrt(complex *, complex *);
! extern double d_abs(double *);
! extern double d_acos(double *);
! extern double d_asin(double *);
! extern double d_atan(double *);
! extern double d_atn2(double *, double *);
! extern void d_cnjg(doublecomplex *, doublecomplex *);
! extern double d_cos(double *);
! extern double d_cosh(double *);
! extern double d_dim(double *, double *);
! extern double d_exp(double *);
! extern double d_imag(doublecomplex *);
! extern double d_int(double *);
! extern double d_lg10(double *);
! extern double d_log(double *);
! extern double d_mod(double *, double *);
! extern double d_nint(double *);
! extern double d_prod(float *, float *);
! extern double d_sign(double *, double *);
! extern double d_sin(double *);
! extern double d_sinh(double *);
! extern double d_sqrt(double *);
! extern double d_tan(double *);
! extern double d_tanh(double *);
! extern double derf_(double *);
! extern double derfc_(double *);
! extern integer do_fio(ftnint *, char *, ftnlen);
! extern integer do_lio(ftnint *, ftnint *, char *, ftnlen);
! extern integer do_uio(ftnint *, char *, ftnlen);
! extern integer e_rdfe(void);
! extern integer e_rdue(void);
! extern integer e_rsfe(void);
! extern integer e_rsfi(void);
! extern integer e_rsle(void);
! extern integer e_rsli(void);
! extern integer e_rsue(void);
! extern integer e_wdfe(void);
! extern integer e_wdue(void);
! extern integer e_wsfe(void);
! extern integer e_wsfi(void);
! extern integer e_wsle(void);
! extern integer e_wsli(void);
! extern integer e_wsue(void);
! extern int ef1asc_(ftnint *, ftnlen *, ftnint *, ftnlen *);
! extern integer ef1cmc_(ftnint *, ftnlen *, ftnint *, ftnlen *);
! extern double erf(double);
! extern double erf_(float *);
! extern double erfc(double);
! extern double erfc_(float *);
! extern integer f_back(alist *);
! extern integer f_clos(cllist *);
! extern integer f_end(alist *);
! extern void f_exit(void);
! extern integer f_inqu(inlist *);
! extern integer f_open(olist *);
! extern integer f_rew(alist *);
! extern int flush_(void);
! extern void getarg_(integer *, char *, ftnlen);
! extern void getenv_(char *, char *, ftnlen, ftnlen);
! extern short h_abs(short *);
! extern short h_dim(short *, short *);
! extern short h_dnnt(double *);
! extern short h_indx(char *, char *, ftnlen, ftnlen);
! extern short h_len(char *, ftnlen);
! extern short h_mod(short *, short *);
! extern short h_nint(float *);
! extern short h_sign(short *, short *);
! extern short hl_ge(char *, char *, ftnlen, ftnlen);
! extern short hl_gt(char *, char *, ftnlen, ftnlen);
! extern short hl_le(char *, char *, ftnlen, ftnlen);
! extern short hl_lt(char *, char *, ftnlen, ftnlen);
! extern integer i_abs(integer *);
! extern integer i_dim(integer *, integer *);
! extern integer i_dnnt(double *);
! extern integer i_indx(char *, char *, ftnlen, ftnlen);
! extern integer i_len(char *, ftnlen);
! extern integer i_mod(integer *, integer *);
! extern integer i_nint(float *);
! extern integer i_sign(integer *, integer *);
! extern integer iargc_(void);
! extern ftnlen l_ge(char *, char *, ftnlen, ftnlen);
! extern ftnlen l_gt(char *, char *, ftnlen, ftnlen);
! extern ftnlen l_le(char *, char *, ftnlen, ftnlen);
! extern ftnlen l_lt(char *, char *, ftnlen, ftnlen);
! extern void pow_ci(complex *, complex *, integer *);
! extern double pow_dd(double *, double *);
! extern double pow_di(double *, integer *);
! extern short pow_hh(short *, shortint *);
! extern integer pow_ii(integer *, integer *);
! extern double pow_ri(float *, integer *);
! extern void pow_zi(doublecomplex *, doublecomplex *, integer *);
! extern void pow_zz(doublecomplex *, doublecomplex *, doublecomplex *);
! extern double r_abs(float *);
! extern double r_acos(float *);
! extern double r_asin(float *);
! extern double r_atan(float *);
! extern double r_atn2(float *, float *);
! extern void r_cnjg(complex *, complex *);
! extern double r_cos(float *);
! extern double r_cosh(float *);
! extern double r_dim(float *, float *);
! extern double r_exp(float *);
! extern double r_imag(complex *);
! extern double r_int(float *);
! extern double r_lg10(float *);
! extern double r_log(float *);
! extern double r_mod(float *, float *);
! extern double r_nint(float *);
! extern double r_sign(float *, float *);
! extern double r_sin(float *);
! extern double r_sinh(float *);
! extern double r_sqrt(float *);
! extern double r_tan(float *);
! extern double r_tanh(float *);
! extern void s_cat(char *, char **, integer *, integer *, ftnlen);
! extern integer s_cmp(char *, char *, ftnlen, ftnlen);
! extern void s_copy(char *, char *, ftnlen, ftnlen);
! extern int s_paus(char *, ftnlen);
! extern integer s_rdfe(cilist *);
! extern integer s_rdue(cilist *);
! extern integer s_rnge(char *, integer, char *, integer);
! extern integer s_rsfe(cilist *);
! extern integer s_rsfi(icilist *);
! extern integer s_rsle(cilist *);
! extern integer s_rsli(icilist *);
! extern integer s_rsne(cilist *);
! extern integer s_rsni(icilist *);
! extern integer s_rsue(cilist *);
! extern int s_stop(char *, ftnlen);
! extern integer s_wdfe(cilist *);
! extern integer s_wdue(cilist *);
! extern integer s_wsfe(cilist *);
! extern integer s_wsfi(icilist *);
! extern integer s_wsle(cilist *);
! extern integer s_wsli(icilist *);
! extern integer s_wsne(cilist *);
! extern integer s_wsni(icilist *);
! extern integer s_wsue(cilist *);
! extern void sig_die(char *, int);
! extern integer signal_(integer *, void (*)(int));
! extern integer system_(char *, ftnlen);
! extern double z_abs(doublecomplex *);
! extern void z_cos(doublecomplex *, doublecomplex *);
! extern void z_div(doublecomplex *, doublecomplex *, doublecomplex *);
! extern void z_exp(doublecomplex *, doublecomplex *);
! extern void z_log(doublecomplex *, doublecomplex *);
! extern void z_sin(doublecomplex *, doublecomplex *);
! extern void z_sqrt(doublecomplex *, doublecomplex *);
! 	}
  #endif
--- 2,163 ----
     for compiling libF77 and libI77. */
  
  #ifdef __cplusplus
! extern "C"
! {
!   extern int abort_ (void);
!   extern double c_abs (complex *);
!   extern void c_cos (complex *, complex *);
!   extern void c_div (complex *, complex *, complex *);
!   extern void c_exp (complex *, complex *);
!   extern void c_log (complex *, complex *);
!   extern void c_sin (complex *, complex *);
!   extern void c_sqrt (complex *, complex *);
!   extern double d_abs (double *);
!   extern double d_acos (double *);
!   extern double d_asin (double *);
!   extern double d_atan (double *);
!   extern double d_atn2 (double *, double *);
!   extern void d_cnjg (doublecomplex *, doublecomplex *);
!   extern double d_cos (double *);
!   extern double d_cosh (double *);
!   extern double d_dim (double *, double *);
!   extern double d_exp (double *);
!   extern double d_imag (doublecomplex *);
!   extern double d_int (double *);
!   extern double d_lg10 (double *);
!   extern double d_log (double *);
!   extern double d_mod (double *, double *);
!   extern double d_nint (double *);
!   extern double d_prod (float *, float *);
!   extern double d_sign (double *, double *);
!   extern double d_sin (double *);
!   extern double d_sinh (double *);
!   extern double d_sqrt (double *);
!   extern double d_tan (double *);
!   extern double d_tanh (double *);
!   extern double derf_ (double *);
!   extern double derfc_ (double *);
!   extern integer do_fio (ftnint *, char *, ftnlen);
!   extern integer do_lio (ftnint *, ftnint *, char *, ftnlen);
!   extern integer do_uio (ftnint *, char *, ftnlen);
!   extern integer e_rdfe (void);
!   extern integer e_rdue (void);
!   extern integer e_rsfe (void);
!   extern integer e_rsfi (void);
!   extern integer e_rsle (void);
!   extern integer e_rsli (void);
!   extern integer e_rsue (void);
!   extern integer e_wdfe (void);
!   extern integer e_wdue (void);
!   extern integer e_wsfe (void);
!   extern integer e_wsfi (void);
!   extern integer e_wsle (void);
!   extern integer e_wsli (void);
!   extern integer e_wsue (void);
!   extern int ef1asc_ (ftnint *, ftnlen *, ftnint *, ftnlen *);
!   extern integer ef1cmc_ (ftnint *, ftnlen *, ftnint *, ftnlen *);
!   extern double erf (double);
!   extern double erf_ (float *);
!   extern double erfc (double);
!   extern double erfc_ (float *);
!   extern integer f_back (alist *);
!   extern integer f_clos (cllist *);
!   extern integer f_end (alist *);
!   extern void f_exit (void);
!   extern integer f_inqu (inlist *);
!   extern integer f_open (olist *);
!   extern integer f_rew (alist *);
!   extern int flush_ (void);
!   extern void getarg_ (integer *, char *, ftnlen);
!   extern void getenv_ (char *, char *, ftnlen, ftnlen);
!   extern short h_abs (short *);
!   extern short h_dim (short *, short *);
!   extern short h_dnnt (double *);
!   extern short h_indx (char *, char *, ftnlen, ftnlen);
!   extern short h_len (char *, ftnlen);
!   extern short h_mod (short *, short *);
!   extern short h_nint (float *);
!   extern short h_sign (short *, short *);
!   extern short hl_ge (char *, char *, ftnlen, ftnlen);
!   extern short hl_gt (char *, char *, ftnlen, ftnlen);
!   extern short hl_le (char *, char *, ftnlen, ftnlen);
!   extern short hl_lt (char *, char *, ftnlen, ftnlen);
!   extern integer i_abs (integer *);
!   extern integer i_dim (integer *, integer *);
!   extern integer i_dnnt (double *);
!   extern integer i_indx (char *, char *, ftnlen, ftnlen);
!   extern integer i_len (char *, ftnlen);
!   extern integer i_mod (integer *, integer *);
!   extern integer i_nint (float *);
!   extern integer i_sign (integer *, integer *);
!   extern integer iargc_ (void);
!   extern ftnlen l_ge (char *, char *, ftnlen, ftnlen);
!   extern ftnlen l_gt (char *, char *, ftnlen, ftnlen);
!   extern ftnlen l_le (char *, char *, ftnlen, ftnlen);
!   extern ftnlen l_lt (char *, char *, ftnlen, ftnlen);
!   extern void pow_ci (complex *, complex *, integer *);
!   extern double pow_dd (double *, double *);
!   extern double pow_di (double *, integer *);
!   extern short pow_hh (short *, shortint *);
!   extern integer pow_ii (integer *, integer *);
!   extern double pow_ri (float *, integer *);
!   extern void pow_zi (doublecomplex *, doublecomplex *, integer *);
!   extern void pow_zz (doublecomplex *, doublecomplex *, doublecomplex *);
!   extern double r_abs (float *);
!   extern double r_acos (float *);
!   extern double r_asin (float *);
!   extern double r_atan (float *);
!   extern double r_atn2 (float *, float *);
!   extern void r_cnjg (complex *, complex *);
!   extern double r_cos (float *);
!   extern double r_cosh (float *);
!   extern double r_dim (float *, float *);
!   extern double r_exp (float *);
!   extern double r_imag (complex *);
!   extern double r_int (float *);
!   extern double r_lg10 (float *);
!   extern double r_log (float *);
!   extern double r_mod (float *, float *);
!   extern double r_nint (float *);
!   extern double r_sign (float *, float *);
!   extern double r_sin (float *);
!   extern double r_sinh (float *);
!   extern double r_sqrt (float *);
!   extern double r_tan (float *);
!   extern double r_tanh (float *);
!   extern void s_cat (char *, char **, integer *, integer *, ftnlen);
!   extern integer s_cmp (char *, char *, ftnlen, ftnlen);
!   extern void s_copy (char *, char *, ftnlen, ftnlen);
!   extern int s_paus (char *, ftnlen);
!   extern integer s_rdfe (cilist *);
!   extern integer s_rdue (cilist *);
!   extern integer s_rnge (char *, integer, char *, integer);
!   extern integer s_rsfe (cilist *);
!   extern integer s_rsfi (icilist *);
!   extern integer s_rsle (cilist *);
!   extern integer s_rsli (icilist *);
!   extern integer s_rsne (cilist *);
!   extern integer s_rsni (icilist *);
!   extern integer s_rsue (cilist *);
!   extern int s_stop (char *, ftnlen);
!   extern integer s_wdfe (cilist *);
!   extern integer s_wdue (cilist *);
!   extern integer s_wsfe (cilist *);
!   extern integer s_wsfi (icilist *);
!   extern integer s_wsle (cilist *);
!   extern integer s_wsli (icilist *);
!   extern integer s_wsne (cilist *);
!   extern integer s_wsni (icilist *);
!   extern integer s_wsue (cilist *);
!   extern void sig_die (char *, int);
!   extern integer signal_ (integer *, void (*)(int));
!   extern integer system_ (char *, ftnlen);
!   extern double z_abs (doublecomplex *);
!   extern void z_cos (doublecomplex *, doublecomplex *);
!   extern void z_div (doublecomplex *, doublecomplex *, doublecomplex *);
!   extern void z_exp (doublecomplex *, doublecomplex *);
!   extern void z_log (doublecomplex *, doublecomplex *);
!   extern void z_sin (doublecomplex *, doublecomplex *);
!   extern void z_sqrt (doublecomplex *, doublecomplex *);
! }
  #endif
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/F77_aloc.c gcc-3.3/libf2c/libF77/F77_aloc.c
*** gcc-3.2.3/libf2c/libF77/F77_aloc.c	1999-03-17 08:21:10.000000000 +0000
--- gcc-3.3/libf2c/libF77/F77_aloc.c	2002-06-01 12:38:27.000000000 +0000
***************
*** 6,38 ****
  
  static integer memfailure = 3;
  
- #ifdef KR_headers
- extern char *malloc();
- extern void G77_exit_0 ();
- 
-  char *
- F77_aloc(Len, whence) integer Len; char *whence;
- #else
  #include <stdlib.h>
! #ifdef __cplusplus
! extern "C" {
! #endif
! extern void G77_exit_0 (integer*);
! #ifdef __cplusplus
! 	}
! #endif
  
!  char *
! F77_aloc(integer Len, char *whence)
! #endif
  {
! 	char *rv;
! 	unsigned int uLen = (unsigned int) Len;	/* for K&R C */
  
! 	if (!(rv = (char*)malloc(uLen))) {
! 		fprintf(stderr, "malloc(%u) failure in %s\n",
! 			uLen, whence);
! 		G77_exit_0 (&memfailure);
! 		}
! 	return rv;
! 	}
--- 6,24 ----
  
  static integer memfailure = 3;
  
  #include <stdlib.h>
! extern void G77_exit_0 (integer *);
  
! char *
! F77_aloc (integer Len, char *whence)
  {
!   char *rv;
!   unsigned int uLen = (unsigned int) Len;	/* for K&R C */
  
!   if (!(rv = (char *) malloc (uLen)))
!     {
!       fprintf (stderr, "malloc(%u) failure in %s\n", uLen, whence);
!       G77_exit_0 (&memfailure);
!     }
!   return rv;
! }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/getarg_.c gcc-3.3/libf2c/libF77/getarg_.c
*** gcc-3.2.3/libf2c/libF77/getarg_.c	1998-05-22 10:31:09.000000000 +0000
--- gcc-3.3/libf2c/libF77/getarg_.c	2002-06-01 12:38:27.000000000 +0000
***************
*** 6,28 ****
   * variable argument c
  */
  
! #ifdef KR_headers
! VOID G77_getarg_0 (n, s, ls) ftnint *n; register char *s; ftnlen ls;
! #else
! void G77_getarg_0 (ftnint *n, register char *s, ftnlen ls)
! #endif
  {
! extern int f__xargc;
! extern char **f__xargv;
! register char *t;
! register int i;
  
! if(*n>=0 && *n<f__xargc)
! 	t = f__xargv[*n];
! else
! 	t = "";
! for(i = 0; i<ls && *t!='\0' ; ++i)
! 	*s++ = *t++;
! for( ; i<ls ; ++i)
! 	*s++ = ' ';
  }
--- 6,25 ----
   * variable argument c
  */
  
! void
! G77_getarg_0 (ftnint * n, register char *s, ftnlen ls)
  {
!   extern int f__xargc;
!   extern char **f__xargv;
!   register char *t;
!   register int i;
  
!   if (*n >= 0 && *n < f__xargc)
!     t = f__xargv[*n];
!   else
!     t = "";
!   for (i = 0; i < ls && *t != '\0'; ++i)
!     *s++ = *t++;
!   for (; i < ls; ++i)
!     *s++ = ' ';
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/getenv_.c gcc-3.3/libf2c/libF77/getenv_.c
*** gcc-3.2.3/libf2c/libF77/getenv_.c	1999-05-03 08:35:13.000000000 +0000
--- gcc-3.3/libf2c/libF77/getenv_.c	2002-06-02 12:54:28.000000000 +0000
***************
*** 1,12 ****
  #include "f2c.h"
  #undef abs
- #ifdef KR_headers
- extern char *F77_aloc(), *getenv();
- #else
  #include <stdlib.h>
  #include <string.h>
! extern char *F77_aloc(ftnlen, char*);
! #endif
  
  /*
   * getenv - f77 subroutine to return environment variables
--- 1,8 ----
  #include "f2c.h"
  #undef abs
  #include <stdlib.h>
  #include <string.h>
! extern char *F77_aloc (ftnlen, char *);
  
  /*
   * getenv - f77 subroutine to return environment variables
*************** extern char *F77_aloc(ftnlen, char*);
*** 20,56 ****
   *		if ENV_NAME is not defined
   */
  
! #ifdef KR_headers
!  VOID
! G77_getenv_0 (fname, value, flen, vlen) char *value, *fname; ftnlen vlen, flen;
! #else
!  void
  G77_getenv_0 (char *fname, char *value, ftnlen flen, ftnlen vlen)
- #endif
  {
! 	char buf[256], *ep, *fp;
! 	integer i;
  
! 	if (flen <= 0)
! 		goto add_blanks;
! 	for(i = 0; i < sizeof(buf); i++) {
! 		if (i == flen || (buf[i] = fname[i]) == ' ') {
! 			buf[i] = 0;
! 			ep = getenv(buf);
! 			goto have_ep;
! 			}
! 		}
! 	while(i < flen && fname[i] != ' ')
! 		i++;
! 	strncpy(fp = F77_aloc(i+1, "getenv_"), fname, (int)i);
! 	fp[i] = 0;
! 	ep = getenv(fp);
! 	free(fp);
!  have_ep:
! 	if (ep)
! 		while(*ep && vlen-- > 0)
! 			*value++ = *ep++;
!  add_blanks:
! 	while(vlen-- > 0)
! 		*value++ = ' ';
  	}
--- 16,49 ----
   *		if ENV_NAME is not defined
   */
  
! void
  G77_getenv_0 (char *fname, char *value, ftnlen flen, ftnlen vlen)
  {
!   char buf[256], *ep, *fp;
!   integer i;
  
!   if (flen <= 0)
!     goto add_blanks;
!   for (i = 0; i < (integer) sizeof (buf); i++)
!     {
!       if (i == flen || (buf[i] = fname[i]) == ' ')
! 	{
! 	  buf[i] = 0;
! 	  ep = getenv (buf);
! 	  goto have_ep;
  	}
+     }
+   while (i < flen && fname[i] != ' ')
+     i++;
+   strncpy (fp = F77_aloc (i + 1, "getenv_"), fname, (int) i);
+   fp[i] = 0;
+   ep = getenv (fp);
+   free (fp);
+ have_ep:
+   if (ep)
+     while (*ep && vlen-- > 0)
+       *value++ = *ep++;
+ add_blanks:
+   while (vlen-- > 0)
+     *value++ = ' ';
+ }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/h_abs.c gcc-3.3/libf2c/libF77/h_abs.c
*** gcc-3.2.3/libf2c/libF77/h_abs.c	1999-09-04 15:09:16.000000000 +0000
--- gcc-3.3/libf2c/libF77/h_abs.c	2002-06-01 12:38:27.000000000 +0000
***************
*** 1,12 ****
  #include "f2c.h"
  
! #ifdef KR_headers
! shortint h_abs(x) shortint *x;
! #else
! shortint h_abs(shortint *x)
! #endif
  {
! if(*x >= 0)
! 	return(*x);
! return(- *x);
  }
--- 1,9 ----
  #include "f2c.h"
  
! shortint
! h_abs (shortint * x)
  {
!   if (*x >= 0)
!     return (*x);
!   return (-*x);
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/h_dim.c gcc-3.3/libf2c/libF77/h_dim.c
*** gcc-3.2.3/libf2c/libF77/h_dim.c	1999-09-04 15:09:16.000000000 +0000
--- gcc-3.3/libf2c/libF77/h_dim.c	2002-06-01 12:38:27.000000000 +0000
***************
*** 1,10 ****
  #include "f2c.h"
  
! #ifdef KR_headers
! shortint h_dim(a,b) shortint *a, *b;
! #else
! shortint h_dim(shortint *a, shortint *b)
! #endif
  {
! return( *a > *b ? *a - *b : 0);
  }
--- 1,7 ----
  #include "f2c.h"
  
! shortint
! h_dim (shortint * a, shortint * b)
  {
!   return (*a > *b ? *a - *b : 0);
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/h_dnnt.c gcc-3.3/libf2c/libF77/h_dnnt.c
*** gcc-3.2.3/libf2c/libF77/h_dnnt.c	1998-05-19 10:50:54.000000000 +0000
--- gcc-3.3/libf2c/libF77/h_dnnt.c	2002-06-01 12:38:27.000000000 +0000
***************
*** 1,13 ****
  #include "f2c.h"
  
- #ifdef KR_headers
- double floor();
- shortint h_dnnt(x) doublereal *x;
- #else
  #undef abs
  #include <math.h>
! shortint h_dnnt(doublereal *x)
! #endif
  {
! return (shortint)(*x >= 0. ? floor(*x + .5) : -floor(.5 - *x));
  }
--- 1,9 ----
  #include "f2c.h"
  
  #undef abs
  #include <math.h>
! shortint
! h_dnnt (doublereal * x)
  {
!   return (shortint) (*x >= 0. ? floor (*x + .5) : -floor (.5 - *x));
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/h_indx.c gcc-3.3/libf2c/libF77/h_indx.c
*** gcc-3.2.3/libf2c/libF77/h_indx.c	1999-09-04 15:09:16.000000000 +0000
--- gcc-3.3/libf2c/libF77/h_indx.c	2002-06-01 12:38:27.000000000 +0000
***************
*** 1,26 ****
  #include "f2c.h"
  
! #ifdef KR_headers
! shortint h_indx(a, b, la, lb) char *a, *b; ftnlen la, lb;
! #else
! shortint h_indx(char *a, char *b, ftnlen la, ftnlen lb)
! #endif
  {
! ftnlen i, n;
! char *s, *t, *bend;
  
! n = la - lb + 1;
! bend = b + lb;
  
! for(i = 0 ; i < n ; ++i)
! 	{
! 	s = a + i;
! 	t = b;
! 	while(t < bend)
! 		if(*s++ != *t++)
! 			goto no;
! 	return((shortint)i+1);
! 	no: ;
! 	}
! return(0);
  }
--- 1,23 ----
  #include "f2c.h"
  
! shortint
! h_indx (char *a, char *b, ftnlen la, ftnlen lb)
  {
!   ftnlen i, n;
!   char *s, *t, *bend;
  
!   n = la - lb + 1;
!   bend = b + lb;
  
!   for (i = 0; i < n; ++i)
!     {
!       s = a + i;
!       t = b;
!       while (t < bend)
! 	if (*s++ != *t++)
! 	  goto no;
!       return ((shortint) i + 1);
!     no:;
!     }
!   return (0);
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/h_len.c gcc-3.3/libf2c/libF77/h_len.c
*** gcc-3.2.3/libf2c/libF77/h_len.c	1999-09-04 15:09:16.000000000 +0000
--- gcc-3.3/libf2c/libF77/h_len.c	2002-06-05 19:07:09.000000000 +0000
***************
*** 1,10 ****
  #include "f2c.h"
  
! #ifdef KR_headers
! shortint h_len(s, n) char *s; ftnlen n;
! #else
! shortint h_len(char *s, ftnlen n)
! #endif
  {
! return(n);
  }
--- 1,7 ----
  #include "f2c.h"
  
! shortint
! h_len (char *s __attribute__ ((__unused__)), ftnlen n)
  {
!   return (n);
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/hl_ge.c gcc-3.3/libf2c/libF77/hl_ge.c
*** gcc-3.2.3/libf2c/libF77/hl_ge.c	1999-09-04 15:09:16.000000000 +0000
--- gcc-3.3/libf2c/libF77/hl_ge.c	2002-06-01 12:38:27.000000000 +0000
***************
*** 1,12 ****
  #include "f2c.h"
  
! #ifdef KR_headers
! extern integer s_cmp();
! shortlogical hl_ge(a,b,la,lb) char *a, *b; ftnlen la, lb;
! #else
! extern integer s_cmp(char *, char *, ftnlen, ftnlen);
! shortlogical hl_ge(char *a, char *b, ftnlen la, ftnlen lb)
! #endif
  {
! return(s_cmp(a,b,la,lb) >= 0);
  }
--- 1,8 ----
  #include "f2c.h"
  
! extern integer s_cmp (char *, char *, ftnlen, ftnlen);
! shortlogical
! hl_ge (char *a, char *b, ftnlen la, ftnlen lb)
  {
!   return (s_cmp (a, b, la, lb) >= 0);
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/hl_gt.c gcc-3.3/libf2c/libF77/hl_gt.c
*** gcc-3.2.3/libf2c/libF77/hl_gt.c	1999-09-04 15:09:16.000000000 +0000
--- gcc-3.3/libf2c/libF77/hl_gt.c	2002-06-01 12:38:27.000000000 +0000
***************
*** 1,12 ****
  #include "f2c.h"
  
! #ifdef KR_headers
! extern integer s_cmp();
! shortlogical hl_gt(a,b,la,lb) char *a, *b; ftnlen la, lb;
! #else
! extern integer s_cmp(char *, char *, ftnlen, ftnlen);
! shortlogical hl_gt(char *a, char *b, ftnlen la, ftnlen lb)
! #endif
  {
! return(s_cmp(a,b,la,lb) > 0);
  }
--- 1,8 ----
  #include "f2c.h"
  
! extern integer s_cmp (char *, char *, ftnlen, ftnlen);
! shortlogical
! hl_gt (char *a, char *b, ftnlen la, ftnlen lb)
  {
!   return (s_cmp (a, b, la, lb) > 0);
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/hl_le.c gcc-3.3/libf2c/libF77/hl_le.c
*** gcc-3.2.3/libf2c/libF77/hl_le.c	1999-09-04 15:09:16.000000000 +0000
--- gcc-3.3/libf2c/libF77/hl_le.c	2002-06-01 12:38:27.000000000 +0000
***************
*** 1,12 ****
  #include "f2c.h"
  
! #ifdef KR_headers
! extern integer s_cmp();
! shortlogical hl_le(a,b,la,lb) char *a, *b; ftnlen la, lb;
! #else
! extern integer s_cmp(char *, char *, ftnlen, ftnlen);
! shortlogical hl_le(char *a, char *b, ftnlen la, ftnlen lb)
! #endif
  {
! return(s_cmp(a,b,la,lb) <= 0);
  }
--- 1,8 ----
  #include "f2c.h"
  
! extern integer s_cmp (char *, char *, ftnlen, ftnlen);
! shortlogical
! hl_le (char *a, char *b, ftnlen la, ftnlen lb)
  {
!   return (s_cmp (a, b, la, lb) <= 0);
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/hl_lt.c gcc-3.3/libf2c/libF77/hl_lt.c
*** gcc-3.2.3/libf2c/libF77/hl_lt.c	1999-09-04 15:09:16.000000000 +0000
--- gcc-3.3/libf2c/libF77/hl_lt.c	2002-06-01 12:38:27.000000000 +0000
***************
*** 1,12 ****
  #include "f2c.h"
  
! #ifdef KR_headers
! extern integer s_cmp();
! shortlogical hl_lt(a,b,la,lb) char *a, *b; ftnlen la, lb;
! #else
! extern integer s_cmp(char *, char *, ftnlen, ftnlen);
! shortlogical hl_lt(char *a, char *b, ftnlen la, ftnlen lb)
! #endif
  {
! return(s_cmp(a,b,la,lb) < 0);
  }
--- 1,8 ----
  #include "f2c.h"
  
! extern integer s_cmp (char *, char *, ftnlen, ftnlen);
! shortlogical
! hl_lt (char *a, char *b, ftnlen la, ftnlen lb)
  {
!   return (s_cmp (a, b, la, lb) < 0);
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/h_mod.c gcc-3.3/libf2c/libF77/h_mod.c
*** gcc-3.2.3/libf2c/libF77/h_mod.c	1999-09-04 15:09:16.000000000 +0000
--- gcc-3.3/libf2c/libF77/h_mod.c	2002-06-01 12:38:27.000000000 +0000
***************
*** 1,10 ****
  #include "f2c.h"
  
! #ifdef KR_headers
! shortint h_mod(a,b) short *a, *b;
! #else
! shortint h_mod(short *a, short *b)
! #endif
  {
! return( *a % *b);
  }
--- 1,7 ----
  #include "f2c.h"
  
! shortint
! h_mod (short *a, short *b)
  {
!   return (*a % *b);
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/h_nint.c gcc-3.3/libf2c/libF77/h_nint.c
*** gcc-3.2.3/libf2c/libF77/h_nint.c	1998-05-19 10:50:55.000000000 +0000
--- gcc-3.3/libf2c/libF77/h_nint.c	2002-06-01 12:38:27.000000000 +0000
***************
*** 1,13 ****
  #include "f2c.h"
  
- #ifdef KR_headers
- double floor();
- shortint h_nint(x) real *x;
- #else
  #undef abs
  #include <math.h>
! shortint h_nint(real *x)
! #endif
  {
! return (shortint)(*x >= 0 ? floor(*x + .5) : -floor(.5 - *x));
  }
--- 1,9 ----
  #include "f2c.h"
  
  #undef abs
  #include <math.h>
! shortint
! h_nint (real * x)
  {
!   return (shortint) (*x >= 0 ? floor (*x + .5) : -floor (.5 - *x));
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/h_sign.c gcc-3.3/libf2c/libF77/h_sign.c
*** gcc-3.2.3/libf2c/libF77/h_sign.c	1999-09-04 15:09:16.000000000 +0000
--- gcc-3.3/libf2c/libF77/h_sign.c	2002-06-01 12:38:27.000000000 +0000
***************
*** 1,12 ****
  #include "f2c.h"
  
! #ifdef KR_headers
! shortint h_sign(a,b) shortint *a, *b;
! #else
! shortint h_sign(shortint *a, shortint *b)
! #endif
  {
! shortint x;
! x = (*a >= 0 ? *a : - *a);
! return( *b >= 0 ? x : -x);
  }
--- 1,9 ----
  #include "f2c.h"
  
! shortint
! h_sign (shortint * a, shortint * b)
  {
!   shortint x;
!   x = (*a >= 0 ? *a : -*a);
!   return (*b >= 0 ? x : -x);
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/i_abs.c gcc-3.3/libf2c/libF77/i_abs.c
*** gcc-3.2.3/libf2c/libF77/i_abs.c	1999-09-04 15:09:16.000000000 +0000
--- gcc-3.3/libf2c/libF77/i_abs.c	2002-06-01 12:38:27.000000000 +0000
***************
*** 1,12 ****
  #include "f2c.h"
  
! #ifdef KR_headers
! integer i_abs(x) integer *x;
! #else
! integer i_abs(integer *x)
! #endif
  {
! if(*x >= 0)
! 	return(*x);
! return(- *x);
  }
--- 1,9 ----
  #include "f2c.h"
  
! integer
! i_abs (integer * x)
  {
!   if (*x >= 0)
!     return (*x);
!   return (-*x);
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/iargc_.c gcc-3.3/libf2c/libF77/iargc_.c
*** gcc-3.2.3/libf2c/libF77/iargc_.c	1998-05-22 10:31:10.000000000 +0000
--- gcc-3.3/libf2c/libF77/iargc_.c	2002-06-01 12:38:28.000000000 +0000
***************
*** 1,11 ****
  #include "f2c.h"
  
! #ifdef KR_headers
! ftnint G77_iargc_0 ()
! #else
! ftnint G77_iargc_0 (void)
! #endif
  {
! extern int f__xargc;
! return ( f__xargc - 1 );
  }
--- 1,8 ----
  #include "f2c.h"
  
! ftnint
! G77_iargc_0 (void)
  {
!   extern int f__xargc;
!   return (f__xargc - 1);
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/i_dim.c gcc-3.3/libf2c/libF77/i_dim.c
*** gcc-3.2.3/libf2c/libF77/i_dim.c	1999-09-04 15:09:16.000000000 +0000
--- gcc-3.3/libf2c/libF77/i_dim.c	2002-06-01 12:38:27.000000000 +0000
***************
*** 1,10 ****
  #include "f2c.h"
  
! #ifdef KR_headers
! integer i_dim(a,b) integer *a, *b;
! #else
! integer i_dim(integer *a, integer *b)
! #endif
  {
! return( *a > *b ? *a - *b : 0);
  }
--- 1,7 ----
  #include "f2c.h"
  
! integer
! i_dim (integer * a, integer * b)
  {
!   return (*a > *b ? *a - *b : 0);
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/i_dnnt.c gcc-3.3/libf2c/libF77/i_dnnt.c
*** gcc-3.2.3/libf2c/libF77/i_dnnt.c	1998-05-19 10:50:56.000000000 +0000
--- gcc-3.3/libf2c/libF77/i_dnnt.c	2002-06-01 12:38:28.000000000 +0000
***************
*** 1,13 ****
  #include "f2c.h"
  
- #ifdef KR_headers
- double floor();
- integer i_dnnt(x) doublereal *x;
- #else
  #undef abs
  #include <math.h>
! integer i_dnnt(doublereal *x)
! #endif
  {
! return (integer)(*x >= 0. ? floor(*x + .5) : -floor(.5 - *x));
  }
--- 1,9 ----
  #include "f2c.h"
  
  #undef abs
  #include <math.h>
! integer
! i_dnnt (doublereal * x)
  {
!   return (integer) (*x >= 0. ? floor (*x + .5) : -floor (.5 - *x));
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/i_indx.c gcc-3.3/libf2c/libF77/i_indx.c
*** gcc-3.2.3/libf2c/libF77/i_indx.c	1999-09-04 15:09:16.000000000 +0000
--- gcc-3.3/libf2c/libF77/i_indx.c	2002-06-01 12:38:28.000000000 +0000
***************
*** 1,26 ****
  #include "f2c.h"
  
! #ifdef KR_headers
! integer i_indx(a, b, la, lb) char *a, *b; ftnlen la, lb;
! #else
! integer i_indx(char *a, char *b, ftnlen la, ftnlen lb)
! #endif
  {
! ftnlen i, n;
! char *s, *t, *bend;
  
! n = la - lb + 1;
! bend = b + lb;
  
! for(i = 0 ; i < n ; ++i)
! 	{
! 	s = a + i;
! 	t = b;
! 	while(t < bend)
! 		if(*s++ != *t++)
! 			goto no;
! 	return(i+1);
! 	no: ;
! 	}
! return(0);
  }
--- 1,23 ----
  #include "f2c.h"
  
! integer
! i_indx (char *a, char *b, ftnlen la, ftnlen lb)
  {
!   ftnlen i, n;
!   char *s, *t, *bend;
  
!   n = la - lb + 1;
!   bend = b + lb;
  
!   for (i = 0; i < n; ++i)
!     {
!       s = a + i;
!       t = b;
!       while (t < bend)
! 	if (*s++ != *t++)
! 	  goto no;
!       return (i + 1);
!     no:;
!     }
!   return (0);
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/i_len.c gcc-3.3/libf2c/libF77/i_len.c
*** gcc-3.2.3/libf2c/libF77/i_len.c	1999-09-04 15:09:16.000000000 +0000
--- gcc-3.3/libf2c/libF77/i_len.c	2002-06-05 19:07:10.000000000 +0000
***************
*** 1,10 ****
  #include "f2c.h"
  
! #ifdef KR_headers
! integer i_len(s, n) char *s; ftnlen n;
! #else
! integer i_len(char *s, ftnlen n)
! #endif
  {
! return(n);
  }
--- 1,7 ----
  #include "f2c.h"
  
! integer
! i_len (char *s __attribute__ ((__unused__)), ftnlen n)
  {
!   return (n);
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/i_mod.c gcc-3.3/libf2c/libF77/i_mod.c
*** gcc-3.2.3/libf2c/libF77/i_mod.c	1999-09-04 15:09:16.000000000 +0000
--- gcc-3.3/libf2c/libF77/i_mod.c	2002-06-01 12:38:28.000000000 +0000
***************
*** 1,10 ****
  #include "f2c.h"
  
! #ifdef KR_headers
! integer i_mod(a,b) integer *a, *b;
! #else
! integer i_mod(integer *a, integer *b)
! #endif
  {
! return( *a % *b);
  }
--- 1,7 ----
  #include "f2c.h"
  
! integer
! i_mod (integer * a, integer * b)
  {
!   return (*a % *b);
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/i_nint.c gcc-3.3/libf2c/libF77/i_nint.c
*** gcc-3.2.3/libf2c/libF77/i_nint.c	1998-05-19 10:50:57.000000000 +0000
--- gcc-3.3/libf2c/libF77/i_nint.c	2002-06-01 12:38:28.000000000 +0000
***************
*** 1,13 ****
  #include "f2c.h"
  
- #ifdef KR_headers
- double floor();
- integer i_nint(x) real *x;
- #else
  #undef abs
  #include <math.h>
! integer i_nint(real *x)
! #endif
  {
! return (integer)(*x >= 0 ? floor(*x + .5) : -floor(.5 - *x));
  }
--- 1,9 ----
  #include "f2c.h"
  
  #undef abs
  #include <math.h>
! integer
! i_nint (real * x)
  {
!   return (integer) (*x >= 0 ? floor (*x + .5) : -floor (.5 - *x));
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/i_sign.c gcc-3.3/libf2c/libF77/i_sign.c
*** gcc-3.2.3/libf2c/libF77/i_sign.c	1999-09-04 15:09:16.000000000 +0000
--- gcc-3.3/libf2c/libF77/i_sign.c	2002-06-01 12:38:28.000000000 +0000
***************
*** 1,12 ****
  #include "f2c.h"
  
! #ifdef KR_headers
! integer i_sign(a,b) integer *a, *b;
! #else
! integer i_sign(integer *a, integer *b)
! #endif
  {
! integer x;
! x = (*a >= 0 ? *a : - *a);
! return( *b >= 0 ? x : -x);
  }
--- 1,9 ----
  #include "f2c.h"
  
! integer
! i_sign (integer * a, integer * b)
  {
!   integer x;
!   x = (*a >= 0 ? *a : -*a);
!   return (*b >= 0 ? x : -x);
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/lbitbits.c gcc-3.3/libf2c/libF77/lbitbits.c
*** gcc-3.2.3/libf2c/libF77/lbitbits.c	1999-09-04 15:09:16.000000000 +0000
--- gcc-3.3/libf2c/libF77/lbitbits.c	2002-06-04 02:24:24.000000000 +0000
***************
*** 4,62 ****
  #define LONGBITS 32
  #endif
  
!  integer
! #ifdef KR_headers
! lbit_bits(a, b, len) integer a, b, len;
! #else
! lbit_bits(integer a, integer b, integer len)
! #endif
  {
! 	/* Assume 2's complement arithmetic */
  
! 	unsigned long x, y;
  
! 	x = (unsigned long) a;
! 	y = (unsigned long)-1L;
! 	x >>= b;
! 	y <<= len;
! 	return (integer)(x & ~y);
! 	}
  
!  integer
! #ifdef KR_headers
! lbit_cshift(a, b, len) integer a, b, len;
! #else
! lbit_cshift(integer a, integer b, integer len)
! #endif
  {
! 	unsigned long x, y, z;
  
! 	x = (unsigned long)a;
! 	if (len <= 0) {
! 		if (len == 0)
! 			return 0;
! 		goto full_len;
! 		}
! 	if (len >= LONGBITS) {
!  full_len:
! 		if (b >= 0) {
! 			b %= LONGBITS;
! 			return (integer)(x << b | x >> LONGBITS -b );
! 			}
! 		b = -b;
! 		b %= LONGBITS;
! 		return (integer)(x << LONGBITS - b | x >> b);
! 		}
! 	y = z = (unsigned long)-1;
! 	y <<= len;
! 	z &= ~y;
! 	y &= x;
! 	x &= z;
! 	if (b >= 0) {
! 		b %= len;
! 		return (integer)(y | z & (x << b | x >> len - b));
! 		}
! 	b = -b;
! 	b %= len;
! 	return (integer)(y | z & (x >> b | x << len - b));
  	}
--- 4,58 ----
  #define LONGBITS 32
  #endif
  
! integer
! lbit_bits (integer a, integer b, integer len)
  {
!   /* Assume 2's complement arithmetic */
  
!   unsigned long x, y;
  
!   x = (unsigned long) a;
!   y = (unsigned long) -1L;
!   x >>= b;
!   y <<= len;
!   return (integer) (x & ~y);
! }
  
! integer
! lbit_cshift (integer a, integer b, integer len)
  {
!   unsigned long x, y, z;
  
!   x = (unsigned long) a;
!   if (len <= 0)
!     {
!       if (len == 0)
! 	return 0;
!       goto full_len;
!     }
!   if (len >= LONGBITS)
!     {
!     full_len:
!       if (b >= 0)
! 	{
! 	  b %= LONGBITS;
! 	  return (integer) (x << b | x >> (LONGBITS - b));
  	}
+       b = -b;
+       b %= LONGBITS;
+       return (integer) (x << (LONGBITS - b) | x >> b);
+     }
+   y = z = (unsigned long) -1;
+   y <<= len;
+   z &= ~y;
+   y &= x;
+   x &= z;
+   if (b >= 0)
+     {
+       b %= len;
+       return (integer) (y | (z & (x << b | x >> (len - b))));
+     }
+   b = -b;
+   b %= len;
+   return (integer) (y | (z & (x >> b | x << (len - b))));
+ }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/lbitshft.c gcc-3.3/libf2c/libF77/lbitshft.c
*** gcc-3.2.3/libf2c/libF77/lbitshft.c	1999-09-04 15:09:16.000000000 +0000
--- gcc-3.3/libf2c/libF77/lbitshft.c	2002-06-01 12:38:28.000000000 +0000
***************
*** 1,11 ****
  #include "f2c.h"
  
!  integer
! #ifdef KR_headers
! lbit_shift(a, b) integer a; integer b;
! #else
! lbit_shift(integer a, integer b)
! #endif
  {
! 	return b >= 0 ? a << b : (integer)((uinteger)a >> -b);
! 	}
--- 1,7 ----
  #include "f2c.h"
  
! integer
! lbit_shift (integer a, integer b)
  {
!   return b >= 0 ? a << b : (integer) ((uinteger) a >> -b);
! }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/l_ge.c gcc-3.3/libf2c/libF77/l_ge.c
*** gcc-3.2.3/libf2c/libF77/l_ge.c	1999-09-04 15:09:16.000000000 +0000
--- gcc-3.3/libf2c/libF77/l_ge.c	2002-06-01 12:38:28.000000000 +0000
***************
*** 1,12 ****
  #include "f2c.h"
  
! #ifdef KR_headers
! extern integer s_cmp();
! logical l_ge(a,b,la,lb) char *a, *b; ftnlen la, lb;
! #else
! extern integer s_cmp(char *, char *, ftnlen, ftnlen);
! logical l_ge(char *a, char *b, ftnlen la, ftnlen lb)
! #endif
  {
! return(s_cmp(a,b,la,lb) >= 0);
  }
--- 1,8 ----
  #include "f2c.h"
  
! extern integer s_cmp (char *, char *, ftnlen, ftnlen);
! logical
! l_ge (char *a, char *b, ftnlen la, ftnlen lb)
  {
!   return (s_cmp (a, b, la, lb) >= 0);
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/l_gt.c gcc-3.3/libf2c/libF77/l_gt.c
*** gcc-3.2.3/libf2c/libF77/l_gt.c	1999-09-04 15:09:16.000000000 +0000
--- gcc-3.3/libf2c/libF77/l_gt.c	2002-06-01 12:38:28.000000000 +0000
***************
*** 1,12 ****
  #include "f2c.h"
  
! #ifdef KR_headers
! extern integer s_cmp();
! logical l_gt(a,b,la,lb) char *a, *b; ftnlen la, lb;
! #else
! extern integer s_cmp(char *, char *, ftnlen, ftnlen);
! logical l_gt(char *a, char *b, ftnlen la, ftnlen lb)
! #endif
  {
! return(s_cmp(a,b,la,lb) > 0);
  }
--- 1,8 ----
  #include "f2c.h"
  
! extern integer s_cmp (char *, char *, ftnlen, ftnlen);
! logical
! l_gt (char *a, char *b, ftnlen la, ftnlen lb)
  {
!   return (s_cmp (a, b, la, lb) > 0);
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/l_le.c gcc-3.3/libf2c/libF77/l_le.c
*** gcc-3.2.3/libf2c/libF77/l_le.c	1999-09-04 15:09:16.000000000 +0000
--- gcc-3.3/libf2c/libF77/l_le.c	2002-06-01 12:38:28.000000000 +0000
***************
*** 1,12 ****
  #include "f2c.h"
  
! #ifdef KR_headers
! extern integer s_cmp();
! logical l_le(a,b,la,lb) char *a, *b; ftnlen la, lb;
! #else
! extern integer s_cmp(char *, char *, ftnlen, ftnlen);
! logical l_le(char *a, char *b, ftnlen la, ftnlen lb)
! #endif
  {
! return(s_cmp(a,b,la,lb) <= 0);
  }
--- 1,8 ----
  #include "f2c.h"
  
! extern integer s_cmp (char *, char *, ftnlen, ftnlen);
! logical
! l_le (char *a, char *b, ftnlen la, ftnlen lb)
  {
!   return (s_cmp (a, b, la, lb) <= 0);
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/l_lt.c gcc-3.3/libf2c/libF77/l_lt.c
*** gcc-3.2.3/libf2c/libF77/l_lt.c	1999-09-04 15:09:16.000000000 +0000
--- gcc-3.3/libf2c/libF77/l_lt.c	2002-06-01 12:38:28.000000000 +0000
***************
*** 1,12 ****
  #include "f2c.h"
  
! #ifdef KR_headers
! extern integer s_cmp();
! logical l_lt(a,b,la,lb) char *a, *b; ftnlen la, lb;
! #else
! extern integer s_cmp(char *, char *, ftnlen, ftnlen);
! logical l_lt(char *a, char *b, ftnlen la, ftnlen lb)
! #endif
  {
! return(s_cmp(a,b,la,lb) < 0);
  }
--- 1,8 ----
  #include "f2c.h"
  
! extern integer s_cmp (char *, char *, ftnlen, ftnlen);
! logical
! l_lt (char *a, char *b, ftnlen la, ftnlen lb)
  {
!   return (s_cmp (a, b, la, lb) < 0);
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/main.c gcc-3.3/libf2c/libF77/main.c
*** gcc-3.2.3/libf2c/libF77/main.c	1998-05-22 10:31:11.000000000 +0000
--- gcc-3.3/libf2c/libF77/main.c	2002-06-04 02:25:47.000000000 +0000
***************
*** 3,68 ****
  #include <stdio.h>
  #include "signal1.h"
  
- #ifndef KR_headers
- #undef VOID
  #include <stdlib.h>
- #endif
  
! #ifndef VOID
! #define VOID void
! #endif
! 
! #ifdef __cplusplus
! extern "C" {
! #endif
! 
! #ifdef NO__STDC
! #define ONEXIT onexit
! extern VOID f_exit();
! #else
! #ifndef KR_headers
! extern void f_exit(void);
  #ifndef NO_ONEXIT
  #define ONEXIT atexit
! extern int atexit(void (*)(void));
! #endif
! #else
! #ifndef NO_ONEXIT
! #define ONEXIT onexit
! extern VOID f_exit();
! #endif
! #endif
! #endif
! 
! #ifdef KR_headers
! extern VOID f_init();
! extern int MAIN__();
! #else
! extern void f_init(void);
! extern int MAIN__(void);
  #endif
  
! #ifdef __cplusplus
! 	}
! #endif
  
! #ifdef KR_headers
! main(argc, argv) int argc; char **argv;
! #else
! main(int argc, char **argv)
! #endif
  {
! f_setarg(argc, argv);
! f_setsig();
! f_init();
  #ifndef NO_ONEXIT
! ONEXIT(f_exit);
  #endif
! MAIN__();
  #ifdef NO_ONEXIT
! f_exit();
  #endif
! exit(0);	/* exit(0) rather than return(0) to bypass Cray bug */
! return 0;	/* For compilers that complain of missing return values; */
! 		/* others will complain that this is unreachable code. */
  }
--- 3,35 ----
  #include <stdio.h>
  #include "signal1.h"
  
  #include <stdlib.h>
  
! extern void f_exit (void);
  #ifndef NO_ONEXIT
  #define ONEXIT atexit
! extern int atexit (void (*)(void));
  #endif
  
! extern void f_init (void);
! extern int MAIN__ (void);
! extern void f_setarg (int, char **);
! extern void f_setsig (void);
  
! int
! main (int argc, char **argv)
  {
!   f_setarg (argc, argv);
!   f_setsig ();
!   f_init ();
  #ifndef NO_ONEXIT
!   ONEXIT (f_exit);
  #endif
!   MAIN__ ();
  #ifdef NO_ONEXIT
!   f_exit ();
  #endif
!   exit (0);			/* exit(0) rather than return(0) to bypass Cray bug */
!   return 0;			/* For compilers that complain of missing return values; */
!   /* others will complain that this is unreachable code. */
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/Makefile.in gcc-3.3/libf2c/libF77/Makefile.in
*** gcc-3.2.3/libf2c/libF77/Makefile.in	2001-12-04 09:53:17.000000000 +0000
--- gcc-3.3/libf2c/libF77/Makefile.in	2002-05-31 03:07:19.000000000 +0000
*************** ARFLAGS = rc
*** 41,51 ****
  RANLIB = @RANLIB@
  @SET_MAKE@
  
! SHELL = /bin/sh
  
  #### End of system configuration section. ####
  
! ALL_CFLAGS = -I. -I$(srcdir) -I$(G2C_H_DIR) -I$(F2C_H_DIR) $(CPPFLAGS) $(DEFS) $(CFLAGS)
  
  .SUFFIXES:
  .SUFFIXES: .c .lo
--- 41,51 ----
  RANLIB = @RANLIB@
  @SET_MAKE@
  
! SHELL = @SHELL@
  
  #### End of system configuration section. ####
  
! ALL_CFLAGS = -I. -I$(srcdir) -I$(G2C_H_DIR) -I$(F2C_H_DIR) $(CPPFLAGS) $(DEFS) $(WARN_CFLAGS) $(CFLAGS)
  
  .SUFFIXES:
  .SUFFIXES: .c .lo
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/pow_ci.c gcc-3.3/libf2c/libF77/pow_ci.c
*** gcc-3.2.3/libf2c/libF77/pow_ci.c	1999-09-04 15:09:17.000000000 +0000
--- gcc-3.3/libf2c/libF77/pow_ci.c	2002-06-01 12:38:28.000000000 +0000
***************
*** 1,20 ****
  #include "f2c.h"
  
! #ifdef KR_headers
! VOID pow_ci(p, a, b) 	/* p = a**b  */
!  complex *p, *a; integer *b;
! #else
! extern void pow_zi(doublecomplex*, doublecomplex*, integer*);
! void pow_ci(complex *p, complex *a, integer *b) 	/* p = a**b  */
! #endif
  {
! doublecomplex p1, a1;
  
! a1.r = a->r;
! a1.i = a->i;
  
! pow_zi(&p1, &a1, b);
  
! p->r = p1.r;
! p->i = p1.i;
  }
--- 1,16 ----
  #include "f2c.h"
  
! extern void pow_zi (doublecomplex *, doublecomplex *, integer *);
! void
! pow_ci (complex * p, complex * a, integer * b)	/* p = a**b  */
  {
!   doublecomplex p1, a1;
  
!   a1.r = a->r;
!   a1.i = a->i;
  
!   pow_zi (&p1, &a1, b);
  
!   p->r = p1.r;
!   p->i = p1.i;
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/pow_dd.c gcc-3.3/libf2c/libF77/pow_dd.c
*** gcc-3.2.3/libf2c/libF77/pow_dd.c	1999-09-04 15:09:17.000000000 +0000
--- gcc-3.3/libf2c/libF77/pow_dd.c	2002-06-01 12:38:28.000000000 +0000
***************
*** 1,13 ****
  #include "f2c.h"
  
- #ifdef KR_headers
- double pow();
- double pow_dd(ap, bp) doublereal *ap, *bp;
- #else
  #undef abs
  #include <math.h>
! double pow_dd(doublereal *ap, doublereal *bp)
! #endif
  {
! return(pow(*ap, *bp) );
  }
--- 1,9 ----
  #include "f2c.h"
  
  #undef abs
  #include <math.h>
! double
! pow_dd (doublereal * ap, doublereal * bp)
  {
!   return (pow (*ap, *bp));
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/pow_di.c gcc-3.3/libf2c/libF77/pow_di.c
*** gcc-3.2.3/libf2c/libF77/pow_di.c	1999-09-04 15:09:17.000000000 +0000
--- gcc-3.3/libf2c/libF77/pow_di.c	2002-06-01 12:38:28.000000000 +0000
***************
*** 1,35 ****
  #include "f2c.h"
  
! #ifdef KR_headers
! double pow_di(ap, bp) doublereal *ap; integer *bp;
! #else
! double pow_di(doublereal *ap, integer *bp)
! #endif
  {
! double pow, x;
! integer n;
! unsigned long u;
  
! pow = 1;
! x = *ap;
! n = *bp;
  
! if(n != 0)
  	{
! 	if(n < 0)
! 		{
! 		n = -n;
! 		x = 1/x;
! 		}
! 	for(u = n; ; )
! 		{
! 		if(u & 01)
! 			pow *= x;
! 		if(u >>= 1)
! 			x *= x;
! 		else
! 			break;
! 		}
  	}
! return(pow);
  }
--- 1,32 ----
  #include "f2c.h"
  
! double
! pow_di (doublereal * ap, integer * bp)
  {
!   double pow, x;
!   integer n;
!   unsigned long u;
  
!   pow = 1;
!   x = *ap;
!   n = *bp;
  
!   if (n != 0)
!     {
!       if (n < 0)
  	{
! 	  n = -n;
! 	  x = 1 / x;
  	}
!       for (u = n;;)
! 	{
! 	  if (u & 01)
! 	    pow *= x;
! 	  if (u >>= 1)
! 	    x *= x;
! 	  else
! 	    break;
! 	}
!     }
!   return (pow);
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/pow_hh.c gcc-3.3/libf2c/libF77/pow_hh.c
*** gcc-3.2.3/libf2c/libF77/pow_hh.c	1999-09-04 15:09:17.000000000 +0000
--- gcc-3.3/libf2c/libF77/pow_hh.c	2002-06-01 12:38:28.000000000 +0000
***************
*** 1,33 ****
  #include "f2c.h"
  
! #ifdef KR_headers
! shortint pow_hh(ap, bp) shortint *ap, *bp;
! #else
! shortint pow_hh(shortint *ap, shortint *bp)
! #endif
  {
! 	shortint pow, x, n;
! 	unsigned u;
  
! 	x = *ap;
! 	n = *bp;
  
! 	if (n <= 0) {
! 		if (n == 0 || x == 1)
! 			return 1;
! 		if (x != -1)
! 			return x == 0 ? 1/x : 0;
! 		n = -n;
! 		}
! 	u = n;
! 	for(pow = 1; ; )
! 		{
! 		if(u & 01)
! 			pow *= x;
! 		if(u >>= 1)
! 			x *= x;
! 		else
! 			break;
! 		}
! 	return(pow);
! 	}
--- 1,31 ----
  #include "f2c.h"
  
! shortint
! pow_hh (shortint * ap, shortint * bp)
  {
!   shortint pow, x, n;
!   unsigned u;
  
!   x = *ap;
!   n = *bp;
  
!   if (n <= 0)
!     {
!       if (n == 0 || x == 1)
! 	return 1;
!       if (x != -1)
! 	return x == 0 ? 1 / x : 0;
!       n = -n;
!     }
!   u = n;
!   for (pow = 1;;)
!     {
!       if (u & 01)
! 	pow *= x;
!       if (u >>= 1)
! 	x *= x;
!       else
! 	break;
!     }
!   return (pow);
! }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/pow_ii.c gcc-3.3/libf2c/libF77/pow_ii.c
*** gcc-3.2.3/libf2c/libF77/pow_ii.c	1999-09-04 15:09:17.000000000 +0000
--- gcc-3.3/libf2c/libF77/pow_ii.c	2002-06-01 12:38:28.000000000 +0000
***************
*** 1,33 ****
  #include "f2c.h"
  
! #ifdef KR_headers
! integer pow_ii(ap, bp) integer *ap, *bp;
! #else
! integer pow_ii(integer *ap, integer *bp)
! #endif
  {
! 	integer pow, x, n;
! 	unsigned long u;
  
! 	x = *ap;
! 	n = *bp;
  
! 	if (n <= 0) {
! 		if (n == 0 || x == 1)
! 			return 1;
! 		if (x != -1)
! 			return x == 0 ? 1/x : 0;
! 		n = -n;
! 		}
! 	u = n;
! 	for(pow = 1; ; )
! 		{
! 		if(u & 01)
! 			pow *= x;
! 		if(u >>= 1)
! 			x *= x;
! 		else
! 			break;
! 		}
! 	return(pow);
! 	}
--- 1,31 ----
  #include "f2c.h"
  
! integer
! pow_ii (integer * ap, integer * bp)
  {
!   integer pow, x, n;
!   unsigned long u;
  
!   x = *ap;
!   n = *bp;
  
!   if (n <= 0)
!     {
!       if (n == 0 || x == 1)
! 	return 1;
!       if (x != -1)
! 	return x == 0 ? 1 / x : 0;
!       n = -n;
!     }
!   u = n;
!   for (pow = 1;;)
!     {
!       if (u & 01)
! 	pow *= x;
!       if (u >>= 1)
! 	x *= x;
!       else
! 	break;
!     }
!   return (pow);
! }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/pow_qq.c gcc-3.3/libf2c/libF77/pow_qq.c
*** gcc-3.2.3/libf2c/libF77/pow_qq.c	1999-09-04 15:09:17.000000000 +0000
--- gcc-3.3/libf2c/libF77/pow_qq.c	2002-06-01 12:38:28.000000000 +0000
***************
*** 1,33 ****
  #include "f2c.h"
  
! #ifdef KR_headers
! longint pow_qq(ap, bp) longint *ap, *bp;
! #else
! longint pow_qq(longint *ap, longint *bp)
! #endif
  {
! 	longint pow, x, n;
! 	unsigned long long u;	/* system-dependent */
  
! 	x = *ap;
! 	n = *bp;
  
! 	if (n <= 0) {
! 		if (n == 0 || x == 1)
! 			return 1;
! 		if (x != -1)
! 			return x == 0 ? 1/x : 0;
! 		n = -n;
! 		}
! 	u = n;
! 	for(pow = 1; ; )
! 		{
! 		if(u & 01)
! 			pow *= x;
! 		if(u >>= 1)
! 			x *= x;
! 		else
! 			break;
! 		}
! 	return(pow);
! 	}
--- 1,31 ----
  #include "f2c.h"
  
! longint
! pow_qq (longint * ap, longint * bp)
  {
!   longint pow, x, n;
!   unsigned long long u;		/* system-dependent */
  
!   x = *ap;
!   n = *bp;
  
!   if (n <= 0)
!     {
!       if (n == 0 || x == 1)
! 	return 1;
!       if (x != -1)
! 	return x == 0 ? 1 / x : 0;
!       n = -n;
!     }
!   u = n;
!   for (pow = 1;;)
!     {
!       if (u & 01)
! 	pow *= x;
!       if (u >>= 1)
! 	x *= x;
!       else
! 	break;
!     }
!   return (pow);
! }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/pow_ri.c gcc-3.3/libf2c/libF77/pow_ri.c
*** gcc-3.2.3/libf2c/libF77/pow_ri.c	1999-09-04 15:09:17.000000000 +0000
--- gcc-3.3/libf2c/libF77/pow_ri.c	2002-06-01 12:38:28.000000000 +0000
***************
*** 1,35 ****
  #include "f2c.h"
  
! #ifdef KR_headers
! double pow_ri(ap, bp) real *ap; integer *bp;
! #else
! double pow_ri(real *ap, integer *bp)
! #endif
  {
! double pow, x;
! integer n;
! unsigned long u;
  
! pow = 1;
! x = *ap;
! n = *bp;
  
! if(n != 0)
  	{
! 	if(n < 0)
! 		{
! 		n = -n;
! 		x = 1/x;
! 		}
! 	for(u = n; ; )
! 		{
! 		if(u & 01)
! 			pow *= x;
! 		if(u >>= 1)
! 			x *= x;
! 		else
! 			break;
! 		}
  	}
! return(pow);
  }
--- 1,32 ----
  #include "f2c.h"
  
! double
! pow_ri (real * ap, integer * bp)
  {
!   double pow, x;
!   integer n;
!   unsigned long u;
  
!   pow = 1;
!   x = *ap;
!   n = *bp;
  
!   if (n != 0)
!     {
!       if (n < 0)
  	{
! 	  n = -n;
! 	  x = 1 / x;
  	}
!       for (u = n;;)
! 	{
! 	  if (u & 01)
! 	    pow *= x;
! 	  if (u >>= 1)
! 	    x *= x;
! 	  else
! 	    break;
! 	}
!     }
!   return (pow);
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/pow_zi.c gcc-3.3/libf2c/libF77/pow_zi.c
*** gcc-3.2.3/libf2c/libF77/pow_zi.c	1999-05-03 08:33:14.000000000 +0000
--- gcc-3.3/libf2c/libF77/pow_zi.c	2002-06-01 12:38:28.000000000 +0000
***************
*** 1,54 ****
  #include "f2c.h"
  
! #ifdef KR_headers
! VOID pow_zi(p, a, b) 	/* p = a**b  */
!  doublecomplex *p, *a; integer *b;
! #else
! extern void z_div(doublecomplex*, doublecomplex*, doublecomplex*);
! void pow_zi(doublecomplex *p, doublecomplex *a, integer *b) 	/* p = a**b  */
! #endif
  {
! 	integer n;
! 	unsigned long u;
! 	double t;
! 	doublecomplex q, x;
! 	static doublecomplex one = {1.0, 0.0};
  
! 	n = *b;
! 	q.r = 1;
! 	q.i = 0;
  
! 	if(n == 0)
! 		goto done;
! 	if(n < 0)
! 		{
! 		n = -n;
! 		z_div(&x, &one, a);
! 		}
! 	else
! 		{
! 		x.r = a->r;
! 		x.i = a->i;
! 		}
  
! 	for(u = n; ; )
! 		{
! 		if(u & 01)
! 			{
! 			t = q.r * x.r - q.i * x.i;
! 			q.i = q.r * x.i + q.i * x.r;
! 			q.r = t;
! 			}
! 		if(u >>= 1)
! 			{
! 			t = x.r * x.r - x.i * x.i;
! 			x.i = 2 * x.r * x.i;
! 			x.r = t;
! 			}
! 		else
! 			break;
! 		}
!  done:
! 	p->i = q.i;
! 	p->r = q.r;
  	}
--- 1,50 ----
  #include "f2c.h"
  
! extern void z_div (doublecomplex *, doublecomplex *, doublecomplex *);
! void
! pow_zi (doublecomplex * p, doublecomplex * a, integer * b)	/* p = a**b  */
  {
!   integer n;
!   unsigned long u;
!   double t;
!   doublecomplex q, x;
!   static doublecomplex one = { 1.0, 0.0 };
  
!   n = *b;
!   q.r = 1;
!   q.i = 0;
  
!   if (n == 0)
!     goto done;
!   if (n < 0)
!     {
!       n = -n;
!       z_div (&x, &one, a);
!     }
!   else
!     {
!       x.r = a->r;
!       x.i = a->i;
!     }
  
!   for (u = n;;)
!     {
!       if (u & 01)
! 	{
! 	  t = q.r * x.r - q.i * x.i;
! 	  q.i = q.r * x.i + q.i * x.r;
! 	  q.r = t;
! 	}
!       if (u >>= 1)
! 	{
! 	  t = x.r * x.r - x.i * x.i;
! 	  x.i = 2 * x.r * x.i;
! 	  x.r = t;
  	}
+       else
+ 	break;
+     }
+ done:
+   p->i = q.i;
+   p->r = q.r;
+ }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/pow_zz.c gcc-3.3/libf2c/libF77/pow_zz.c
*** gcc-3.2.3/libf2c/libF77/pow_zz.c	1999-09-04 15:09:17.000000000 +0000
--- gcc-3.3/libf2c/libF77/pow_zz.c	2002-11-19 23:17:36.000000000 +0000
***************
*** 1,23 ****
  #include "f2c.h"
  
- #ifdef KR_headers
- double log(), exp(), cos(), sin(), atan2(), f__cabs();
- VOID pow_zz(r,a,b) doublecomplex *r, *a, *b;
- #else
  #undef abs
  #include <math.h>
! extern double f__cabs(double,double);
! void pow_zz(doublecomplex *r, doublecomplex *a, doublecomplex *b)
! #endif
  {
! double logr, logi, x, y;
  
! logr = log( f__cabs(a->r, a->i) );
! logi = atan2(a->i, a->r);
  
! x = exp( logr * b->r - logi * b->i );
! y = logr * b->i + logi * b->r;
  
! r->r = x * cos(y);
! r->i = x * sin(y);
  }
--- 1,25 ----
  #include "f2c.h"
  
  #undef abs
  #include <math.h>
! extern double f__cabs (double, double);
! void
! pow_zz (doublecomplex * r, doublecomplex * a, doublecomplex * b)
  {
!   double logr, logi, x, y;
  
!   if (a->r == 0.0 && a->i == 0.0)
!     {
! 	/* Algorithm below doesn't cope.  */
!         r->r = r->i = 0.0;
!         return;
!     }
!   logr = log (f__cabs (a->r, a->i));
!   logi = atan2 (a->i, a->r);
  
!   x = exp (logr * b->r - logi * b->i);
!   y = logr * b->i + logi * b->r;
  
!   r->r = x * cos (y);
!   r->i = x * sin (y);
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/qbitbits.c gcc-3.3/libf2c/libF77/qbitbits.c
*** gcc-3.2.3/libf2c/libF77/qbitbits.c	1999-09-04 15:09:17.000000000 +0000
--- gcc-3.3/libf2c/libF77/qbitbits.c	2002-06-04 02:24:24.000000000 +0000
***************
*** 8,66 ****
  #define LONG8BITS (2*LONGBITS)
  #endif
  
!  integer
! #ifdef KR_headers
! qbit_bits(a, b, len) longint a; integer b, len;
! #else
! qbit_bits(longint a, integer b, integer len)
! #endif
  {
! 	/* Assume 2's complement arithmetic */
  
! 	ulongint x, y;
  
! 	x = (ulongint) a;
! 	y = (ulongint)-1L;
! 	x >>= b;
! 	y <<= len;
! 	return (longint)(x & y);
! 	}
  
!  longint
! #ifdef KR_headers
! qbit_cshift(a, b, len) longint a; integer b, len;
! #else
! qbit_cshift(longint a, integer b, integer len)
! #endif
  {
! 	ulongint x, y, z;
  
! 	x = (ulongint)a;
! 	if (len <= 0) {
! 		if (len == 0)
! 			return 0;
! 		goto full_len;
! 		}
! 	if (len >= LONG8BITS) {
!  full_len:
! 		if (b >= 0) {
! 			b %= LONG8BITS;
! 			return (longint)(x << b | x >> LONG8BITS - b );
! 			}
! 		b = -b;
! 		b %= LONG8BITS;
! 		return (longint)(x << LONG8BITS - b | x >> b);
! 		}
! 	y = z = (unsigned long)-1;
! 	y <<= len;
! 	z &= ~y;
! 	y &= x;
! 	x &= z;
! 	if (b >= 0) {
! 		b %= len;
! 		return (longint)(y | z & (x << b | x >> len - b));
! 		}
! 	b = -b;
! 	b %= len;
! 	return (longint)(y | z & (x >> b | x << len - b));
  	}
--- 8,62 ----
  #define LONG8BITS (2*LONGBITS)
  #endif
  
! integer
! qbit_bits (longint a, integer b, integer len)
  {
!   /* Assume 2's complement arithmetic */
  
!   ulongint x, y;
  
!   x = (ulongint) a;
!   y = (ulongint) - 1L;
!   x >>= b;
!   y <<= len;
!   return (longint) (x & y);
! }
  
! longint
! qbit_cshift (longint a, integer b, integer len)
  {
!   ulongint x, y, z;
  
!   x = (ulongint) a;
!   if (len <= 0)
!     {
!       if (len == 0)
! 	return 0;
!       goto full_len;
!     }
!   if (len >= LONG8BITS)
!     {
!     full_len:
!       if (b >= 0)
! 	{
! 	  b %= LONG8BITS;
! 	  return (longint) (x << b | x >> (LONG8BITS - b));
  	}
+       b = -b;
+       b %= LONG8BITS;
+       return (longint) (x << (LONG8BITS - b) | x >> b);
+     }
+   y = z = (unsigned long) -1;
+   y <<= len;
+   z &= ~y;
+   y &= x;
+   x &= z;
+   if (b >= 0)
+     {
+       b %= len;
+       return (longint) (y | (z & (x << b | x >> (len - b))));
+     }
+   b = -b;
+   b %= len;
+   return (longint) (y | (z & (x >> b | x << (len - b))));
+ }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/qbitshft.c gcc-3.3/libf2c/libF77/qbitshft.c
*** gcc-3.2.3/libf2c/libF77/qbitshft.c	1999-09-04 15:09:17.000000000 +0000
--- gcc-3.3/libf2c/libF77/qbitshft.c	2002-06-01 12:38:28.000000000 +0000
***************
*** 1,11 ****
  #include "f2c.h"
  
!  longint
! #ifdef KR_headers
! qbit_shift(a, b) longint a; integer b;
! #else
! qbit_shift(longint a, integer b)
! #endif
  {
! 	return b >= 0 ? a << b : (longint)((ulongint)a >> -b);
! 	}
--- 1,7 ----
  #include "f2c.h"
  
! longint
! qbit_shift (longint a, integer b)
  {
!   return b >= 0 ? a << b : (longint) ((ulongint) a >> -b);
! }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/r_abs.c gcc-3.3/libf2c/libF77/r_abs.c
*** gcc-3.2.3/libf2c/libF77/r_abs.c	1999-09-04 15:09:17.000000000 +0000
--- gcc-3.3/libf2c/libF77/r_abs.c	2002-06-01 12:38:28.000000000 +0000
***************
*** 1,12 ****
  #include "f2c.h"
  
! #ifdef KR_headers
! double r_abs(x) real *x;
! #else
! double r_abs(real *x)
! #endif
  {
! if(*x >= 0)
! 	return(*x);
! return(- *x);
  }
--- 1,9 ----
  #include "f2c.h"
  
! double
! r_abs (real * x)
  {
!   if (*x >= 0)
!     return (*x);
!   return (-*x);
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/r_acos.c gcc-3.3/libf2c/libF77/r_acos.c
*** gcc-3.2.3/libf2c/libF77/r_acos.c	1999-09-04 15:09:17.000000000 +0000
--- gcc-3.3/libf2c/libF77/r_acos.c	2002-06-01 12:38:28.000000000 +0000
***************
*** 1,13 ****
  #include "f2c.h"
  
- #ifdef KR_headers
- double acos();
- double r_acos(x) real *x;
- #else
  #undef abs
  #include <math.h>
! double r_acos(real *x)
! #endif
  {
! return( acos(*x) );
  }
--- 1,9 ----
  #include "f2c.h"
  
  #undef abs
  #include <math.h>
! double
! r_acos (real * x)
  {
!   return (acos (*x));
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/r_asin.c gcc-3.3/libf2c/libF77/r_asin.c
*** gcc-3.2.3/libf2c/libF77/r_asin.c	1999-09-04 15:09:17.000000000 +0000
--- gcc-3.3/libf2c/libF77/r_asin.c	2002-06-01 12:38:28.000000000 +0000
***************
*** 1,13 ****
  #include "f2c.h"
  
- #ifdef KR_headers
- double asin();
- double r_asin(x) real *x;
- #else
  #undef abs
  #include <math.h>
! double r_asin(real *x)
! #endif
  {
! return( asin(*x) );
  }
--- 1,9 ----
  #include "f2c.h"
  
  #undef abs
  #include <math.h>
! double
! r_asin (real * x)
  {
!   return (asin (*x));
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/r_atan.c gcc-3.3/libf2c/libF77/r_atan.c
*** gcc-3.2.3/libf2c/libF77/r_atan.c	1999-09-04 15:09:17.000000000 +0000
--- gcc-3.3/libf2c/libF77/r_atan.c	2002-06-01 12:38:28.000000000 +0000
***************
*** 1,13 ****
  #include "f2c.h"
  
- #ifdef KR_headers
- double atan();
- double r_atan(x) real *x;
- #else
  #undef abs
  #include <math.h>
! double r_atan(real *x)
! #endif
  {
! return( atan(*x) );
  }
--- 1,9 ----
  #include "f2c.h"
  
  #undef abs
  #include <math.h>
! double
! r_atan (real * x)
  {
!   return (atan (*x));
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/r_atn2.c gcc-3.3/libf2c/libF77/r_atn2.c
*** gcc-3.2.3/libf2c/libF77/r_atn2.c	1999-09-04 15:09:17.000000000 +0000
--- gcc-3.3/libf2c/libF77/r_atn2.c	2002-06-01 12:38:28.000000000 +0000
***************
*** 1,13 ****
  #include "f2c.h"
  
- #ifdef KR_headers
- double atan2();
- double r_atn2(x,y) real *x, *y;
- #else
  #undef abs
  #include <math.h>
! double r_atn2(real *x, real *y)
! #endif
  {
! return( atan2(*x,*y) );
  }
--- 1,9 ----
  #include "f2c.h"
  
  #undef abs
  #include <math.h>
! double
! r_atn2 (real * x, real * y)
  {
!   return (atan2 (*x, *y));
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/r_cnjg.c gcc-3.3/libf2c/libF77/r_cnjg.c
*** gcc-3.2.3/libf2c/libF77/r_cnjg.c	1999-05-03 08:35:14.000000000 +0000
--- gcc-3.3/libf2c/libF77/r_cnjg.c	2002-06-01 12:38:28.000000000 +0000
***************
*** 1,12 ****
  #include "f2c.h"
  
! #ifdef KR_headers
! VOID r_cnjg(r, z) complex *r, *z;
! #else
! VOID r_cnjg(complex *r, complex *z)
! #endif
  {
! 	real zi = z->i;
! 	r->r = z->r;
! 	r->i = -zi;
! 	}
--- 1,9 ----
  #include "f2c.h"
  
! void
! r_cnjg (complex * r, complex * z)
  {
!   real zi = z->i;
!   r->r = z->r;
!   r->i = -zi;
! }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/r_cos.c gcc-3.3/libf2c/libF77/r_cos.c
*** gcc-3.2.3/libf2c/libF77/r_cos.c	1999-09-04 15:09:17.000000000 +0000
--- gcc-3.3/libf2c/libF77/r_cos.c	2002-06-01 12:38:28.000000000 +0000
***************
*** 1,13 ****
  #include "f2c.h"
  
- #ifdef KR_headers
- double cos();
- double r_cos(x) real *x;
- #else
  #undef abs
  #include <math.h>
! double r_cos(real *x)
! #endif
  {
! return( cos(*x) );
  }
--- 1,9 ----
  #include "f2c.h"
  
  #undef abs
  #include <math.h>
! double
! r_cos (real * x)
  {
!   return (cos (*x));
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/r_cosh.c gcc-3.3/libf2c/libF77/r_cosh.c
*** gcc-3.2.3/libf2c/libF77/r_cosh.c	1999-09-04 15:09:17.000000000 +0000
--- gcc-3.3/libf2c/libF77/r_cosh.c	2002-06-01 12:38:28.000000000 +0000
***************
*** 1,13 ****
  #include "f2c.h"
  
- #ifdef KR_headers
- double cosh();
- double r_cosh(x) real *x;
- #else
  #undef abs
  #include <math.h>
! double r_cosh(real *x)
! #endif
  {
! return( cosh(*x) );
  }
--- 1,9 ----
  #include "f2c.h"
  
  #undef abs
  #include <math.h>
! double
! r_cosh (real * x)
  {
!   return (cosh (*x));
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/r_dim.c gcc-3.3/libf2c/libF77/r_dim.c
*** gcc-3.2.3/libf2c/libF77/r_dim.c	1999-09-04 15:09:17.000000000 +0000
--- gcc-3.3/libf2c/libF77/r_dim.c	2002-06-01 12:38:28.000000000 +0000
***************
*** 1,10 ****
  #include "f2c.h"
  
! #ifdef KR_headers
! double r_dim(a,b) real *a, *b;
! #else
! double r_dim(real *a, real *b)
! #endif
  {
! return( *a > *b ? *a - *b : 0);
  }
--- 1,7 ----
  #include "f2c.h"
  
! double
! r_dim (real * a, real * b)
  {
!   return (*a > *b ? *a - *b : 0);
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/r_exp.c gcc-3.3/libf2c/libF77/r_exp.c
*** gcc-3.2.3/libf2c/libF77/r_exp.c	1999-09-04 15:09:17.000000000 +0000
--- gcc-3.3/libf2c/libF77/r_exp.c	2002-06-01 12:38:28.000000000 +0000
***************
*** 1,13 ****
  #include "f2c.h"
  
- #ifdef KR_headers
- double exp();
- double r_exp(x) real *x;
- #else
  #undef abs
  #include <math.h>
! double r_exp(real *x)
! #endif
  {
! return( exp(*x) );
  }
--- 1,9 ----
  #include "f2c.h"
  
  #undef abs
  #include <math.h>
! double
! r_exp (real * x)
  {
!   return (exp (*x));
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/r_imag.c gcc-3.3/libf2c/libF77/r_imag.c
*** gcc-3.2.3/libf2c/libF77/r_imag.c	1999-09-04 15:09:17.000000000 +0000
--- gcc-3.3/libf2c/libF77/r_imag.c	2002-06-01 12:38:28.000000000 +0000
***************
*** 1,10 ****
  #include "f2c.h"
  
! #ifdef KR_headers
! double r_imag(z) complex *z;
! #else
! double r_imag(complex *z)
! #endif
  {
! return(z->i);
  }
--- 1,7 ----
  #include "f2c.h"
  
! double
! r_imag (complex * z)
  {
!   return (z->i);
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/r_int.c gcc-3.3/libf2c/libF77/r_int.c
*** gcc-3.2.3/libf2c/libF77/r_int.c	1999-09-04 15:09:17.000000000 +0000
--- gcc-3.3/libf2c/libF77/r_int.c	2002-06-01 12:38:28.000000000 +0000
***************
*** 1,13 ****
  #include "f2c.h"
  
- #ifdef KR_headers
- double floor();
- double r_int(x) real *x;
- #else
  #undef abs
  #include <math.h>
! double r_int(real *x)
! #endif
  {
! return( (*x>0) ? floor(*x) : -floor(- *x) );
  }
--- 1,9 ----
  #include "f2c.h"
  
  #undef abs
  #include <math.h>
! double
! r_int (real * x)
  {
!   return ((*x > 0) ? floor (*x) : -floor (-*x));
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/r_lg10.c gcc-3.3/libf2c/libF77/r_lg10.c
*** gcc-3.2.3/libf2c/libF77/r_lg10.c	1999-09-04 15:09:17.000000000 +0000
--- gcc-3.3/libf2c/libF77/r_lg10.c	2002-06-01 12:38:28.000000000 +0000
***************
*** 2,15 ****
  
  #define log10e 0.43429448190325182765
  
- #ifdef KR_headers
- double log();
- double r_lg10(x) real *x;
- #else
  #undef abs
  #include <math.h>
! double r_lg10(real *x)
! #endif
  {
! return( log10e * log(*x) );
  }
--- 2,11 ----
  
  #define log10e 0.43429448190325182765
  
  #undef abs
  #include <math.h>
! double
! r_lg10 (real * x)
  {
!   return (log10e * log (*x));
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/r_log.c gcc-3.3/libf2c/libF77/r_log.c
*** gcc-3.2.3/libf2c/libF77/r_log.c	1999-09-04 15:09:17.000000000 +0000
--- gcc-3.3/libf2c/libF77/r_log.c	2002-06-01 12:38:28.000000000 +0000
***************
*** 1,13 ****
  #include "f2c.h"
  
- #ifdef KR_headers
- double log();
- double r_log(x) real *x;
- #else
  #undef abs
  #include <math.h>
! double r_log(real *x)
! #endif
  {
! return( log(*x) );
  }
--- 1,9 ----
  #include "f2c.h"
  
  #undef abs
  #include <math.h>
! double
! r_log (real * x)
  {
!   return (log (*x));
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/r_mod.c gcc-3.3/libf2c/libF77/r_mod.c
*** gcc-3.2.3/libf2c/libF77/r_mod.c	1999-09-04 15:09:17.000000000 +0000
--- gcc-3.3/libf2c/libF77/r_mod.c	2002-06-01 12:38:28.000000000 +0000
***************
*** 1,40 ****
  #include "f2c.h"
  
- #ifdef KR_headers
  #ifdef IEEE_drem
! double drem();
! #else
! double floor();
! #endif
! double r_mod(x,y) real *x, *y;
! #else
! #ifdef IEEE_drem
! double drem(double, double);
  #else
  #undef abs
  #include <math.h>
  #endif
! double r_mod(real *x, real *y)
! #endif
  {
  #ifdef IEEE_drem
! 	double xa, ya, z;
! 	if ((ya = *y) < 0.)
! 		ya = -ya;
! 	z = drem(xa = *x, ya);
! 	if (xa > 0) {
! 		if (z < 0)
! 			z += ya;
! 		}
! 	else if (z > 0)
! 		z -= ya;
! 	return z;
  #else
! 	double quotient;
! 	if( (quotient = (double)*x / *y) >= 0)
! 		quotient = floor(quotient);
! 	else
! 		quotient = -floor(-quotient);
! 	return(*x - (*y) * quotient );
  #endif
  }
--- 1,33 ----
  #include "f2c.h"
  
  #ifdef IEEE_drem
! double drem (double, double);
  #else
  #undef abs
  #include <math.h>
  #endif
! double
! r_mod (real * x, real * y)
  {
  #ifdef IEEE_drem
!   double xa, ya, z;
!   if ((ya = *y) < 0.)
!     ya = -ya;
!   z = drem (xa = *x, ya);
!   if (xa > 0)
!     {
!       if (z < 0)
! 	z += ya;
!     }
!   else if (z > 0)
!     z -= ya;
!   return z;
  #else
!   double quotient;
!   if ((quotient = (double) *x / *y) >= 0)
!     quotient = floor (quotient);
!   else
!     quotient = -floor (-quotient);
!   return (*x - (*y) * quotient);
  #endif
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/r_nint.c gcc-3.3/libf2c/libF77/r_nint.c
*** gcc-3.2.3/libf2c/libF77/r_nint.c	1999-09-04 15:09:17.000000000 +0000
--- gcc-3.3/libf2c/libF77/r_nint.c	2002-06-01 12:38:28.000000000 +0000
***************
*** 1,14 ****
  #include "f2c.h"
  
- #ifdef KR_headers
- double floor();
- double r_nint(x) real *x;
- #else
  #undef abs
  #include <math.h>
! double r_nint(real *x)
! #endif
  {
! return( (*x)>=0 ?
! 	floor(*x + .5) : -floor(.5 - *x) );
  }
--- 1,9 ----
  #include "f2c.h"
  
  #undef abs
  #include <math.h>
! double
! r_nint (real * x)
  {
!   return ((*x) >= 0 ? floor (*x + .5) : -floor (.5 - *x));
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/r_sign.c gcc-3.3/libf2c/libF77/r_sign.c
*** gcc-3.2.3/libf2c/libF77/r_sign.c	1999-09-04 15:09:17.000000000 +0000
--- gcc-3.3/libf2c/libF77/r_sign.c	2002-06-01 12:38:28.000000000 +0000
***************
*** 1,12 ****
  #include "f2c.h"
  
! #ifdef KR_headers
! double r_sign(a,b) real *a, *b;
! #else
! double r_sign(real *a, real *b)
! #endif
  {
! double x;
! x = (*a >= 0 ? *a : - *a);
! return( *b >= 0 ? x : -x);
  }
--- 1,9 ----
  #include "f2c.h"
  
! double
! r_sign (real * a, real * b)
  {
!   double x;
!   x = (*a >= 0 ? *a : -*a);
!   return (*b >= 0 ? x : -x);
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/r_sin.c gcc-3.3/libf2c/libF77/r_sin.c
*** gcc-3.2.3/libf2c/libF77/r_sin.c	1999-09-04 15:09:17.000000000 +0000
--- gcc-3.3/libf2c/libF77/r_sin.c	2002-06-01 12:38:28.000000000 +0000
***************
*** 1,13 ****
  #include "f2c.h"
  
- #ifdef KR_headers
- double sin();
- double r_sin(x) real *x;
- #else
  #undef abs
  #include <math.h>
! double r_sin(real *x)
! #endif
  {
! return( sin(*x) );
  }
--- 1,9 ----
  #include "f2c.h"
  
  #undef abs
  #include <math.h>
! double
! r_sin (real * x)
  {
!   return (sin (*x));
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/r_sinh.c gcc-3.3/libf2c/libF77/r_sinh.c
*** gcc-3.2.3/libf2c/libF77/r_sinh.c	1999-09-04 15:09:17.000000000 +0000
--- gcc-3.3/libf2c/libF77/r_sinh.c	2002-06-01 12:38:28.000000000 +0000
***************
*** 1,13 ****
  #include "f2c.h"
  
- #ifdef KR_headers
- double sinh();
- double r_sinh(x) real *x;
- #else
  #undef abs
  #include <math.h>
! double r_sinh(real *x)
! #endif
  {
! return( sinh(*x) );
  }
--- 1,9 ----
  #include "f2c.h"
  
  #undef abs
  #include <math.h>
! double
! r_sinh (real * x)
  {
!   return (sinh (*x));
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/r_sqrt.c gcc-3.3/libf2c/libF77/r_sqrt.c
*** gcc-3.2.3/libf2c/libF77/r_sqrt.c	1999-09-04 15:09:17.000000000 +0000
--- gcc-3.3/libf2c/libF77/r_sqrt.c	2002-06-01 12:38:28.000000000 +0000
***************
*** 1,13 ****
  #include "f2c.h"
  
- #ifdef KR_headers
- double sqrt();
- double r_sqrt(x) real *x;
- #else
  #undef abs
  #include <math.h>
! double r_sqrt(real *x)
! #endif
  {
! return( sqrt(*x) );
  }
--- 1,9 ----
  #include "f2c.h"
  
  #undef abs
  #include <math.h>
! double
! r_sqrt (real * x)
  {
!   return (sqrt (*x));
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/r_tan.c gcc-3.3/libf2c/libF77/r_tan.c
*** gcc-3.2.3/libf2c/libF77/r_tan.c	1999-09-04 15:09:17.000000000 +0000
--- gcc-3.3/libf2c/libF77/r_tan.c	2002-06-01 12:38:28.000000000 +0000
***************
*** 1,13 ****
  #include "f2c.h"
  
- #ifdef KR_headers
- double tan();
- double r_tan(x) real *x;
- #else
  #undef abs
  #include <math.h>
! double r_tan(real *x)
! #endif
  {
! return( tan(*x) );
  }
--- 1,9 ----
  #include "f2c.h"
  
  #undef abs
  #include <math.h>
! double
! r_tan (real * x)
  {
!   return (tan (*x));
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/r_tanh.c gcc-3.3/libf2c/libF77/r_tanh.c
*** gcc-3.2.3/libf2c/libF77/r_tanh.c	1999-09-04 15:09:17.000000000 +0000
--- gcc-3.3/libf2c/libF77/r_tanh.c	2002-06-01 12:38:28.000000000 +0000
***************
*** 1,13 ****
  #include "f2c.h"
  
- #ifdef KR_headers
- double tanh();
- double r_tanh(x) real *x;
- #else
  #undef abs
  #include <math.h>
! double r_tanh(real *x)
! #endif
  {
! return( tanh(*x) );
  }
--- 1,9 ----
  #include "f2c.h"
  
  #undef abs
  #include <math.h>
! double
! r_tanh (real * x)
  {
!   return (tanh (*x));
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/s_cat.c gcc-3.3/libf2c/libF77/s_cat.c
*** gcc-3.2.3/libf2c/libF77/s_cat.c	2000-12-09 15:34:53.000000000 +0000
--- gcc-3.3/libf2c/libF77/s_cat.c	2002-06-01 12:38:28.000000000 +0000
***************
*** 7,75 ****
  #ifndef NO_OVERWRITE
  #include <stdio.h>
  #undef abs
- #ifdef KR_headers
-  extern char *F77_aloc();
-  extern void free();
-  extern void G77_exit_0 ();
- #else
  #undef min
  #undef max
  #include <stdlib.h>
!  extern char *F77_aloc(ftnlen, char*);
! #endif
  #include <string.h>
  #endif /* NO_OVERWRITE */
  
!  VOID
! #ifdef KR_headers
! s_cat(lp, rpp, rnp, np, ll) char *lp, *rpp[]; ftnint rnp[], *np; ftnlen ll;
! #else
! s_cat(char *lp, char *rpp[], ftnint rnp[], ftnint *np, ftnlen ll)
! #endif
  {
! 	ftnlen i, nc;
! 	char *rp;
! 	ftnlen n = *np;
  #ifndef NO_OVERWRITE
! 	ftnlen L, m;
! 	char *lp0, *lp1;
  
! 	lp0 = 0;
! 	lp1 = lp;
! 	L = ll;
! 	i = 0;
! 	while(i < n) {
! 		rp = rpp[i];
! 		m = rnp[i++];
! 		if (rp >= lp1 || rp + m <= lp) {
! 			if ((L -= m) <= 0) {
! 				n = i;
! 				break;
! 				}
! 			lp1 += m;
! 			continue;
! 			}
! 		lp0 = lp;
! 		lp = lp1 = F77_aloc(L = ll, "s_cat");
! 		break;
! 		}
! 	lp1 = lp;
  #endif /* NO_OVERWRITE */
! 	for(i = 0 ; i < n ; ++i) {
! 		nc = ll;
! 		if(rnp[i] < nc)
! 			nc = rnp[i];
! 		ll -= nc;
! 		rp = rpp[i];
! 		while(--nc >= 0)
! 			*lp++ = *rp++;
! 		}
! 	while(--ll >= 0)
! 		*lp++ = ' ';
  #ifndef NO_OVERWRITE
! 	if (lp0) {
! 		memcpy(lp0, lp1, L);
! 		free(lp1);
! 		}
  #endif
! 	}
--- 7,70 ----
  #ifndef NO_OVERWRITE
  #include <stdio.h>
  #undef abs
  #undef min
  #undef max
  #include <stdlib.h>
! extern char *F77_aloc (ftnlen, char *);
  #include <string.h>
  #endif /* NO_OVERWRITE */
  
! void
! s_cat (char *lp, char *rpp[], ftnint rnp[], ftnint * np, ftnlen ll)
  {
!   ftnlen i, nc;
!   char *rp;
!   ftnlen n = *np;
  #ifndef NO_OVERWRITE
!   ftnlen L, m;
!   char *lp0, *lp1;
  
!   lp0 = 0;
!   lp1 = lp;
!   L = ll;
!   i = 0;
!   while (i < n)
!     {
!       rp = rpp[i];
!       m = rnp[i++];
!       if (rp >= lp1 || rp + m <= lp)
! 	{
! 	  if ((L -= m) <= 0)
! 	    {
! 	      n = i;
! 	      break;
! 	    }
! 	  lp1 += m;
! 	  continue;
! 	}
!       lp0 = lp;
!       lp = lp1 = F77_aloc (L = ll, "s_cat");
!       break;
!     }
!   lp1 = lp;
  #endif /* NO_OVERWRITE */
!   for (i = 0; i < n; ++i)
!     {
!       nc = ll;
!       if (rnp[i] < nc)
! 	nc = rnp[i];
!       ll -= nc;
!       rp = rpp[i];
!       while (--nc >= 0)
! 	*lp++ = *rp++;
!     }
!   while (--ll >= 0)
!     *lp++ = ' ';
  #ifndef NO_OVERWRITE
!   if (lp0)
!     {
!       memcpy (lp0, lp1, L);
!       free (lp1);
!     }
  #endif
! }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/s_cmp.c gcc-3.3/libf2c/libF77/s_cmp.c
*** gcc-3.2.3/libf2c/libF77/s_cmp.c	1999-09-04 15:09:17.000000000 +0000
--- gcc-3.3/libf2c/libF77/s_cmp.c	2002-06-01 12:38:28.000000000 +0000
***************
*** 2,44 ****
  
  /* compare two strings */
  
! #ifdef KR_headers
! integer s_cmp(a0, b0, la, lb) char *a0, *b0; ftnlen la, lb;
! #else
! integer s_cmp(char *a0, char *b0, ftnlen la, ftnlen lb)
! #endif
  {
! register unsigned char *a, *aend, *b, *bend;
! a = (unsigned char *)a0;
! b = (unsigned char *)b0;
! aend = a + la;
! bend = b + lb;
  
! if(la <= lb)
! 	{
! 	while(a < aend)
! 		if(*a != *b)
! 			return( *a - *b );
! 		else
! 			{ ++a; ++b; }
  
! 	while(b < bend)
! 		if(*b != ' ')
! 			return( ' ' - *b );
! 		else	++b;
! 	}
  
! else
! 	{
! 	while(b < bend)
! 		if(*a == *b)
! 			{ ++a; ++b; }
! 		else
! 			return( *a - *b );
! 	while(a < aend)
! 		if(*a != ' ')
! 			return(*a - ' ');
! 		else	++a;
! 	}
! return(0);
  }
--- 2,49 ----
  
  /* compare two strings */
  
! integer
! s_cmp (char *a0, char *b0, ftnlen la, ftnlen lb)
  {
!   register unsigned char *a, *aend, *b, *bend;
!   a = (unsigned char *) a0;
!   b = (unsigned char *) b0;
!   aend = a + la;
!   bend = b + lb;
  
!   if (la <= lb)
!     {
!       while (a < aend)
! 	if (*a != *b)
! 	  return (*a - *b);
! 	else
! 	  {
! 	    ++a;
! 	    ++b;
! 	  }
  
!       while (b < bend)
! 	if (*b != ' ')
! 	  return (' ' - *b);
! 	else
! 	  ++b;
!     }
  
!   else
!     {
!       while (b < bend)
! 	if (*a == *b)
! 	  {
! 	    ++a;
! 	    ++b;
! 	  }
! 	else
! 	  return (*a - *b);
!       while (a < aend)
! 	if (*a != ' ')
! 	  return (*a - ' ');
! 	else
! 	  ++a;
!     }
!   return (0);
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/s_copy.c gcc-3.3/libf2c/libF77/s_copy.c
*** gcc-3.2.3/libf2c/libF77/s_copy.c	1999-09-04 15:09:17.000000000 +0000
--- gcc-3.3/libf2c/libF77/s_copy.c	2002-06-01 12:38:28.000000000 +0000
***************
*** 8,51 ****
  
  /* assign strings:  a = b */
  
! #ifdef KR_headers
! VOID s_copy(a, b, la, lb) register char *a, *b; ftnlen la, lb;
! #else
! void s_copy(register char *a, register char *b, ftnlen la, ftnlen lb)
! #endif
  {
! 	register char *aend, *bend;
  
! 	aend = a + la;
  
! 	if(la <= lb)
  #ifndef NO_OVERWRITE
! 		if (a <= b || a >= b + la)
  #endif
! 			while(a < aend)
! 				*a++ = *b++;
  #ifndef NO_OVERWRITE
! 		else
! 			for(b += la; a < aend; )
! 				*--aend = *--b;
  #endif
  
! 	else {
! 		bend = b + lb;
  #ifndef NO_OVERWRITE
! 		if (a <= b || a >= bend)
  #endif
! 			while(b < bend)
! 				*a++ = *b++;
  #ifndef NO_OVERWRITE
! 		else {
! 			a += lb;
! 			while(b < bend)
! 				*--a = *--bend;
! 			a += lb;
! 			}
! #endif
! 		while(a < aend)
! 			*a++ = ' ';
! 		}
  	}
--- 8,50 ----
  
  /* assign strings:  a = b */
  
! void
! s_copy (register char *a, register char *b, ftnlen la, ftnlen lb)
  {
!   register char *aend, *bend;
  
!   aend = a + la;
  
!   if (la <= lb)
  #ifndef NO_OVERWRITE
!     if (a <= b || a >= b + la)
  #endif
!       while (a < aend)
! 	*a++ = *b++;
  #ifndef NO_OVERWRITE
!     else
!       for (b += la; a < aend;)
! 	*--aend = *--b;
  #endif
  
!   else
!     {
!       bend = b + lb;
  #ifndef NO_OVERWRITE
!       if (a <= b || a >= bend)
  #endif
! 	while (b < bend)
! 	  *a++ = *b++;
  #ifndef NO_OVERWRITE
!       else
! 	{
! 	  a += lb;
! 	  while (b < bend)
! 	    *--a = *--bend;
! 	  a += lb;
  	}
+ #endif
+       while (a < aend)
+ 	*a++ = ' ';
+     }
+ }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/setarg.c gcc-3.3/libf2c/libF77/setarg.c
*** gcc-3.2.3/libf2c/libF77/setarg.c	1999-09-04 15:09:17.000000000 +0000
--- gcc-3.3/libf2c/libF77/setarg.c	2002-06-01 12:38:28.000000000 +0000
***************
*** 1,29 ****
  /* Set up the global argc/argv info for use by getarg_, iargc_, and
     g77's inlined intrinsic equivalents.  */
  
- #ifndef KR_headers
- #undef VOID
  #include <stdlib.h>
- #endif
- 
- #ifndef VOID
- #define VOID void
- #endif
  
  int f__xargc;
  char **f__xargv;
  
! #ifdef __cplusplus
! 	}
! #endif
! 
!  void
! #ifdef KR_headers
! f_setarg(argc, argv) int argc; char **argv;
! #else
! f_setarg(int argc, char **argv)
! #endif
  {
! f__xargc = argc;
! f__xargv = argv;
  }
--- 1,14 ----
  /* Set up the global argc/argv info for use by getarg_, iargc_, and
     g77's inlined intrinsic equivalents.  */
  
  #include <stdlib.h>
  
  int f__xargc;
  char **f__xargv;
  
! void
! f_setarg (int argc, char **argv)
  {
!   f__xargc = argc;
!   f__xargv = argv;
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/setsig.c gcc-3.3/libf2c/libF77/setsig.c
*** gcc-3.2.3/libf2c/libF77/setsig.c	1999-09-04 15:09:17.000000000 +0000
--- gcc-3.3/libf2c/libF77/setsig.c	2002-06-01 12:38:28.000000000 +0000
***************
*** 9,101 ****
  #endif
  #endif
  
- #ifndef KR_headers
- #undef VOID
  #include <stdlib.h>
- #endif
- 
- #ifndef VOID
- #define VOID void
- #endif
- 
- #ifdef __cplusplus
- extern "C" {
- #endif
  
! #ifdef KR_headers
! extern VOID sig_die();
! #define Int /* int */
! #else
! extern void sig_die(char*, int);
! #define Int int
! #endif
  
! static VOID sigfdie(Sigarg)
  {
! Use_Sigarg;
! sig_die("Floating Exception", 1);
  }
  
  
! static VOID sigidie(Sigarg)
  {
! Use_Sigarg;
! sig_die("IOT Trap", 1);
  }
  
  #ifdef SIGQUIT
! static VOID sigqdie(Sigarg)
  {
! Use_Sigarg;
! sig_die("Quit signal", 1);
  }
  #endif
  
  
! static VOID sigindie(Sigarg)
  {
! Use_Sigarg;
! sig_die("Interrupt", 0);
  }
  
! static VOID sigtdie(Sigarg)
  {
! Use_Sigarg;
! sig_die("Killed", 0);
  }
  
  #ifdef SIGTRAP
! static VOID sigtrdie(Sigarg)
  {
! Use_Sigarg;
! sig_die("Trace trap", 1);
  }
  #endif
  
  
! #ifdef __cplusplus
! 	}
! #endif
! 
!  void
! f_setsig()
  {
! signal1(SIGFPE, sigfdie);	/* ignore underflow, enable overflow */
  #ifdef SIGIOT
! signal1(SIGIOT, sigidie);
  #endif
  #ifdef SIGTRAP
! signal1(SIGTRAP, sigtrdie);
  #endif
  #ifdef SIGQUIT
! if(signal1(SIGQUIT,sigqdie) == SIG_IGN)
! 	signal1(SIGQUIT, SIG_IGN);
  #endif
! if(signal1(SIGINT, sigindie) == SIG_IGN)
! 	signal1(SIGINT, SIG_IGN);
! signal1(SIGTERM,sigtdie);
  
  #ifdef pdp11
! 	ldfps(01200); /* detect overflow as an exception */
  #endif
  }
--- 9,86 ----
  #endif
  #endif
  
  #include <stdlib.h>
  
! extern void sig_die (char *, int);
  
! static void
! sigfdie (Sigarg)
  {
!   Use_Sigarg;
!   sig_die ("Floating Exception", 1);
  }
  
  
! static void
! sigidie (Sigarg)
  {
!   Use_Sigarg;
!   sig_die ("IOT Trap", 1);
  }
  
  #ifdef SIGQUIT
! static void
! sigqdie (Sigarg)
  {
!   Use_Sigarg;
!   sig_die ("Quit signal", 1);
  }
  #endif
  
  
! static void
! sigindie (Sigarg)
  {
!   Use_Sigarg;
!   sig_die ("Interrupt", 0);
  }
  
! static void
! sigtdie (Sigarg)
  {
!   Use_Sigarg;
!   sig_die ("Killed", 0);
  }
  
  #ifdef SIGTRAP
! static void
! sigtrdie (Sigarg)
  {
!   Use_Sigarg;
!   sig_die ("Trace trap", 1);
  }
  #endif
  
  
! void
! f_setsig ()
  {
!   signal1 (SIGFPE, sigfdie);	/* ignore underflow, enable overflow */
  #ifdef SIGIOT
!   signal1 (SIGIOT, sigidie);
  #endif
  #ifdef SIGTRAP
!   signal1 (SIGTRAP, sigtrdie);
  #endif
  #ifdef SIGQUIT
!   if (signal1 (SIGQUIT, sigqdie) == SIG_IGN)
!     signal1 (SIGQUIT, SIG_IGN);
  #endif
!   if (signal1 (SIGINT, sigindie) == SIG_IGN)
!     signal1 (SIGINT, SIG_IGN);
!   signal1 (SIGTERM, sigtdie);
  
  #ifdef pdp11
!   ldfps (01200);		/* detect overflow as an exception */
  #endif
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/sig_die.c gcc-3.3/libf2c/libF77/sig_die.c
*** gcc-3.2.3/libf2c/libF77/sig_die.c	1999-09-04 15:09:17.000000000 +0000
--- gcc-3.3/libf2c/libF77/sig_die.c	2002-06-01 12:38:28.000000000 +0000
***************
*** 7,45 ****
  #endif
  #endif
  
- #ifdef KR_headers
- void sig_die(s, kill) register char *s; int kill;
- #else
  #include <stdlib.h>
! #ifdef __cplusplus
! extern "C" {
! #endif
!  extern void f_exit(void);
  
! void sig_die(register char *s, int kill)
! #endif
  {
! 	/* print error message, then clear buffers */
! 	fprintf(stderr, "%s\n", s);
  
! 	if(kill)
! 		{
! 		fflush(stderr);
! 		f_exit();
! 		fflush(stderr);
! 		/* now get a core */
  #ifdef SIGIOT
! 		signal(SIGIOT, SIG_DFL);
  #endif
! 		abort();
! 		}
! 	else {
  #ifdef NO_ONEXIT
! 		f_exit();
  #endif
! 		exit(1);
! 		}
! 	}
! #ifdef __cplusplus
  }
- #endif
--- 7,37 ----
  #endif
  #endif
  
  #include <stdlib.h>
! extern void f_exit (void);
  
! void
! sig_die (register char *s, int kill)
  {
!   /* print error message, then clear buffers */
!   fprintf (stderr, "%s\n", s);
  
!   if (kill)
!     {
!       fflush (stderr);
!       f_exit ();
!       fflush (stderr);
!       /* now get a core */
  #ifdef SIGIOT
!       signal (SIGIOT, SIG_DFL);
  #endif
!       abort ();
!     }
!   else
!     {
  #ifdef NO_ONEXIT
!       f_exit ();
  #endif
!       exit (1);
!     }
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/signal1.h0 gcc-3.3/libf2c/libF77/signal1.h0
*** gcc-3.2.3/libf2c/libF77/signal1.h0	1999-03-17 08:21:15.000000000 +0000
--- gcc-3.3/libf2c/libF77/signal1.h0	2002-06-01 12:38:28.000000000 +0000
***************
*** 11,35 ****
  #define Sigret_t void
  #endif
  #ifndef Sigarg_t
- #ifdef KR_headers
- #define Sigarg_t
- #else
  #define Sigarg_t int
! #endif
! #endif /*Sigarg_t*/
  
! #ifdef USE_SIG_PF	/* compile with -DUSE_SIG_PF under IRIX */
  #define sig_pf SIG_PF
  #else
! typedef Sigret_t (*sig_pf)(Sigarg_t);
  #endif
  
  #define signal1(a,b) signal(a,(sig_pf)b)
  
! #ifdef __cplusplus
! #define Sigarg ...
! #define Use_Sigarg
! #else
! #define Sigarg Int n
  #define Use_Sigarg n = n	/* shut up compiler warning */
- #endif
--- 11,26 ----
  #define Sigret_t void
  #endif
  #ifndef Sigarg_t
  #define Sigarg_t int
! #endif /*Sigarg_t */
  
! #ifdef USE_SIG_PF		/* compile with -DUSE_SIG_PF under IRIX */
  #define sig_pf SIG_PF
  #else
! typedef Sigret_t (*sig_pf) (Sigarg_t);
  #endif
  
  #define signal1(a,b) signal(a,(sig_pf)b)
  
! #define Sigarg int n
  #define Use_Sigarg n = n	/* shut up compiler warning */
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/signal_.c gcc-3.3/libf2c/libF77/signal_.c
*** gcc-3.2.3/libf2c/libF77/signal_.c	1998-05-19 11:01:47.000000000 +0000
--- gcc-3.3/libf2c/libF77/signal_.c	2002-06-01 12:38:28.000000000 +0000
***************
*** 1,16 ****
  #include "f2c.h"
  #include "signal1.h"
  
- #ifdef KR_headers
- void *
- G77_signal_0 (sigp, proc) integer *sigp; sig_pf proc;
- #else
  void *
! G77_signal_0 (integer *sigp, sig_pf proc)
! #endif
  {
! 	int sig;
! 	sig = (int)*sigp;
  
! 	return (void *) signal(sig, proc);
! 	}
--- 1,11 ----
  #include "f2c.h"
  #include "signal1.h"
  
  void *
! G77_signal_0 (integer * sigp, sig_pf proc)
  {
!   int sig;
!   sig = (int) *sigp;
  
!   return (void *) signal (sig, proc);
! }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/s_paus.c gcc-3.3/libf2c/libF77/s_paus.c
*** gcc-3.2.3/libf2c/libF77/s_paus.c	1998-05-19 10:50:59.000000000 +0000
--- gcc-3.3/libf2c/libF77/s_paus.c	2002-06-01 12:38:28.000000000 +0000
***************
*** 3,88 ****
  #define PAUSESIG 15
  
  #include "signal1.h"
- #ifdef KR_headers
- #define Void /* void */
- #define Int /* int */
- #else
- #define Void void
- #define Int int
  #undef abs
  #undef min
  #undef max
  #include <stdlib.h>
! #ifdef __cplusplus
! extern "C" {
! #endif
! extern int getpid(void), isatty(int), pause(void);
! #endif
  
! extern VOID f_exit(Void);
  
!  static VOID
! waitpause(Sigarg)
! {	Use_Sigarg;
! 	return;
! 	}
  
!  static VOID
! #ifdef KR_headers
! s_1paus(fin) FILE *fin;
! #else
! s_1paus(FILE *fin)
! #endif
  {
! 	fprintf(stderr,
! 	"To resume execution, type go.  Other input will terminate the job.\n");
! 	fflush(stderr);
! 	if( getc(fin)!='g' || getc(fin)!='o' || getc(fin)!='\n' ) {
! 		fprintf(stderr, "STOP\n");
  #ifdef NO_ONEXIT
! 		f_exit();
  #endif
! 		exit(0);
! 		}
! 	}
  
!  int
! #ifdef KR_headers
! s_paus(s, n) char *s; ftnlen n;
! #else
! s_paus(char *s, ftnlen n)
! #endif
  {
! 	fprintf(stderr, "PAUSE ");
! 	if(n > 0)
! 		fprintf(stderr, " %.*s", (int)n, s);
! 	fprintf(stderr, " statement executed\n");
! 	if( isatty(fileno(stdin)) )
! 		s_1paus(stdin);
! 	else {
  #if (defined (MSDOS) && !defined (GO32)) || defined (_WIN32)
! 		FILE *fin;
! 		fin = fopen("con", "r");
! 		if (!fin) {
! 			fprintf(stderr, "s_paus: can't open con!\n");
! 			fflush(stderr);
! 			exit(1);
! 			}
! 		s_1paus(fin);
! 		fclose(fin);
! #else
! 		fprintf(stderr,
! 		"To resume execution, execute a   kill -%d %d   command\n",
! 			PAUSESIG, getpid() );
! 		signal1(PAUSESIG, waitpause);
! 		fflush(stderr);
! 		pause();
! #endif
! 		}
! 	fprintf(stderr, "Execution resumes after PAUSE.\n");
! 	fflush(stderr);
! 	return 0; /* NOT REACHED */
! #ifdef __cplusplus
  	}
  #endif
  }
--- 3,71 ----
  #define PAUSESIG 15
  
  #include "signal1.h"
  #undef abs
  #undef min
  #undef max
  #include <stdlib.h>
! extern int getpid (void), isatty (int), pause (void);
  
! extern void f_exit (void);
  
! static void
! waitpause (Sigarg)
! {
!   Use_Sigarg;
!   return;
! }
  
! static void
! s_1paus (FILE * fin)
  {
!   fprintf (stderr,
! 	   "To resume execution, type go.  Other input will terminate the job.\n");
!   fflush (stderr);
!   if (getc (fin) != 'g' || getc (fin) != 'o' || getc (fin) != '\n')
!     {
!       fprintf (stderr, "STOP\n");
  #ifdef NO_ONEXIT
!       f_exit ();
  #endif
!       exit (0);
!     }
! }
  
! int
! s_paus (char *s, ftnlen n)
  {
!   fprintf (stderr, "PAUSE ");
!   if (n > 0)
!     fprintf (stderr, " %.*s", (int) n, s);
!   fprintf (stderr, " statement executed\n");
!   if (isatty (fileno (stdin)))
!     s_1paus (stdin);
!   else
!     {
  #if (defined (MSDOS) && !defined (GO32)) || defined (_WIN32)
!       FILE *fin;
!       fin = fopen ("con", "r");
!       if (!fin)
! 	{
! 	  fprintf (stderr, "s_paus: can't open con!\n");
! 	  fflush (stderr);
! 	  exit (1);
  	}
+       s_1paus (fin);
+       fclose (fin);
+ #else
+       fprintf (stderr,
+ 	       "To resume execution, execute a   kill -%d %d   command\n",
+ 	       PAUSESIG, getpid ());
+       signal1 (PAUSESIG, waitpause);
+       fflush (stderr);
+       pause ();
  #endif
+     }
+   fprintf (stderr, "Execution resumes after PAUSE.\n");
+   fflush (stderr);
+   return 0;			/* NOT REACHED */
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/s_rnge.c gcc-3.3/libf2c/libF77/s_rnge.c
*** gcc-3.2.3/libf2c/libF77/s_rnge.c	2000-03-12 19:20:47.000000000 +0000
--- gcc-3.3/libf2c/libF77/s_rnge.c	2002-06-01 12:38:28.000000000 +0000
***************
*** 3,26 ****
  
  /* called when a subscript is out of range */
  
! #ifdef KR_headers
! extern VOID sig_die();
! integer s_rnge(varn, offset, procn, line) char *varn, *procn; ftnint offset, line;
! #else
! extern VOID sig_die(char*,int);
! integer s_rnge(char *varn, ftnint offset, char *procn, ftnint line)
! #endif
  {
! register int i;
  
! fprintf(stderr, "Subscript out of range on file line %ld, procedure ",
! 	(long)line);
! while((i = *procn) && i != '_' && i != ' ')
! 	putc(*procn++, stderr);
! fprintf(stderr, ".\nAttempt to access the %ld-th element of variable ",
! 	(long)offset+1);
! while((i = *varn) && i != ' ')
! 	putc(*varn++, stderr);
! sig_die(".", 1);
! return 0;	/* not reached */
  }
--- 3,22 ----
  
  /* called when a subscript is out of range */
  
! extern void sig_die (char *, int);
! integer
! s_rnge (char *varn, ftnint offset, char *procn, ftnint line)
  {
!   register int i;
  
!   fprintf (stderr, "Subscript out of range on file line %ld, procedure ",
! 	   (long) line);
!   while ((i = *procn) && i != '_' && i != ' ')
!     putc (*procn++, stderr);
!   fprintf (stderr, ".\nAttempt to access the %ld-th element of variable ",
! 	   (long) offset + 1);
!   while ((i = *varn) && i != ' ')
!     putc (*varn++, stderr);
!   sig_die (".", 1);
!   return 0;			/* not reached */
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/s_stop.c gcc-3.3/libf2c/libF77/s_stop.c
*** gcc-3.2.3/libf2c/libF77/s_stop.c	1999-05-10 14:40:56.000000000 +0000
--- gcc-3.3/libf2c/libF77/s_stop.c	2002-06-01 12:38:28.000000000 +0000
***************
*** 1,42 ****
  #include <stdio.h>
  #include "f2c.h"
  
- #ifdef KR_headers
- extern void f_exit();
- VOID s_stop(s, n) char *s; ftnlen n;
- #else
  #undef abs
  #undef min
  #undef max
  #include <stdlib.h>
! #ifdef __cplusplus
! extern "C" {
! #endif
! void f_exit(void);
  
! int s_stop(char *s, ftnlen n)
! #endif
  {
! int i;
  
! if(n > 0)
! 	{
! 	fprintf(stderr, "STOP ");
! 	for(i = 0; i<n ; ++i)
! 		putc(*s++, stderr);
! 	fprintf(stderr, " statement executed\n");
! 	}
  #ifdef NO_ONEXIT
! f_exit();
  #endif
! exit(0);
  
  /* We cannot avoid (useless) compiler diagnostics here:		*/
  /* some compilers complain if there is no return statement,	*/
  /* and others complain that this one cannot be reached.		*/
  
! return 0; /* NOT REACHED */
! }
! #ifdef __cplusplus
  }
- #endif
--- 1,32 ----
  #include <stdio.h>
  #include "f2c.h"
  
  #undef abs
  #undef min
  #undef max
  #include <stdlib.h>
! void f_exit (void);
  
! int
! s_stop (char *s, ftnlen n)
  {
!   int i;
  
!   if (n > 0)
!     {
!       fprintf (stderr, "STOP ");
!       for (i = 0; i < n; ++i)
! 	putc (*s++, stderr);
!       fprintf (stderr, " statement executed\n");
!     }
  #ifdef NO_ONEXIT
!   f_exit ();
  #endif
!   exit (0);
  
  /* We cannot avoid (useless) compiler diagnostics here:		*/
  /* some compilers complain if there is no return statement,	*/
  /* and others complain that this one cannot be reached.		*/
  
!   return 0;			/* NOT REACHED */
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/system_.c gcc-3.3/libf2c/libF77/system_.c
*** gcc-3.2.3/libf2c/libF77/system_.c	1999-09-04 15:09:17.000000000 +0000
--- gcc-3.3/libf2c/libF77/system_.c	2002-06-02 12:54:28.000000000 +0000
***************
*** 2,36 ****
  
  #include "f2c.h"
  
- #ifdef KR_headers
- extern char *F77_aloc();
- 
-  integer
- G77_system_0 (s, n) register char *s; ftnlen n;
- #else
  #undef abs
  #undef min
  #undef max
  #include <stdlib.h>
! extern char *F77_aloc(ftnlen, char*);
  
!  integer
  G77_system_0 (register char *s, ftnlen n)
- #endif
  {
! 	char buff0[256], *buff;
! 	register char *bp, *blast;
! 	integer rv;
  
! 	buff = bp = n < sizeof(buff0)
! 			? buff0 : F77_aloc(n+1, "system_");
! 	blast = bp + n;
  
! 	while(bp < blast && *s)
! 		*bp++ = *s++;
! 	*bp = 0;
! 	rv = system(buff);
! 	if (buff != buff0)
! 		free(buff);
! 	return rv;
! 	}
--- 2,28 ----
  
  #include "f2c.h"
  
  #undef abs
  #undef min
  #undef max
  #include <stdlib.h>
! extern char *F77_aloc (ftnlen, char *);
  
! integer
  G77_system_0 (register char *s, ftnlen n)
  {
!   char buff0[256], *buff;
!   register char *bp, *blast;
!   integer rv;
  
!   buff = bp = n < (ftnlen) sizeof (buff0) ? buff0 : F77_aloc (n + 1, "system_");
!   blast = bp + n;
  
!   while (bp < blast && *s)
!     *bp++ = *s++;
!   *bp = 0;
!   rv = system (buff);
!   if (buff != buff0)
!     free (buff);
!   return rv;
! }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/Version.c gcc-3.3/libf2c/libF77/Version.c
*** gcc-3.2.3/libf2c/libF77/Version.c	2003-04-22 00:16:27.000000000 +0000
--- gcc-3.3/libf2c/libF77/Version.c	2002-09-24 03:44:34.000000000 +0000
***************
*** 1,9 ****
! static char junk[] = "\n@(#)LIBF77 VERSION 20000929\n";
! 
! /*
! */
! 
! char __G77_LIBF77_VERSION__[] = "3.2.2 20030422 (release)";
  
  /*
  2.00	11 June 1980.  File version.c added to library.
--- 1,6 ----
! const char __LIBF77_VERSION__[] = "@(#) LIBF77 VERSION 20000929\n";
! extern const char __LIBI77_VERSION__[];
! extern const char __LIBU77_VERSION__[];
  
  /*
  2.00	11 June 1980.  File version.c added to library.
*************** char __G77_LIBF77_VERSION__[] = "3.2.2 2
*** 87,92 ****
  void
  g77__fvers__ ()
  {
!   fprintf (stderr, "__G77_LIBF77_VERSION__: %s", __G77_LIBF77_VERSION__);
!   fputs (junk, stderr);
  }
--- 84,94 ----
  void
  g77__fvers__ ()
  {
!   fputs ("GNU Fortran library.\n", stderr);
! #if defined __GNUC__ && defined __VERSION__
!   fprintf (stderr, "Compiled by GCC %s\n", __VERSION__);
! #endif
!   fputs (__LIBF77_VERSION__, stderr);
!   fputs (__LIBI77_VERSION__, stderr);
!   fputs (__LIBU77_VERSION__, stderr);
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/z_abs.c gcc-3.3/libf2c/libF77/z_abs.c
*** gcc-3.2.3/libf2c/libF77/z_abs.c	1999-09-04 15:09:17.000000000 +0000
--- gcc-3.3/libf2c/libF77/z_abs.c	2002-06-01 12:38:28.000000000 +0000
***************
*** 1,12 ****
  #include "f2c.h"
  
! #ifdef KR_headers
! double f__cabs();
! double z_abs(z) doublecomplex *z;
! #else
! double f__cabs(double, double);
! double z_abs(doublecomplex *z)
! #endif
  {
! return( f__cabs( z->r, z->i ) );
  }
--- 1,8 ----
  #include "f2c.h"
  
! double f__cabs (double, double);
! double
! z_abs (doublecomplex * z)
  {
!   return (f__cabs (z->r, z->i));
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/z_cos.c gcc-3.3/libf2c/libF77/z_cos.c
*** gcc-3.2.3/libf2c/libF77/z_cos.c	1999-05-03 08:35:15.000000000 +0000
--- gcc-3.3/libf2c/libF77/z_cos.c	2002-06-01 12:38:28.000000000 +0000
***************
*** 1,15 ****
  #include "f2c.h"
  
- #ifdef KR_headers
- double sin(), cos(), sinh(), cosh();
- VOID z_cos(r, z) doublecomplex *r, *z;
- #else
  #undef abs
  #include "math.h"
! void z_cos(doublecomplex *r, doublecomplex *z)
! #endif
  {
! 	double zi = z->i, zr = z->r;
! 	r->r =   cos(zr) * cosh(zi);
! 	r->i = - sin(zr) * sinh(zi);
! 	}
--- 1,11 ----
  #include "f2c.h"
  
  #undef abs
  #include "math.h"
! void
! z_cos (doublecomplex * r, doublecomplex * z)
  {
!   double zi = z->i, zr = z->r;
!   r->r = cos (zr) * cosh (zi);
!   r->i = -sin (zr) * sinh (zi);
! }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/z_div.c gcc-3.3/libf2c/libF77/z_div.c
*** gcc-3.2.3/libf2c/libF77/z_div.c	2000-03-12 19:20:47.000000000 +0000
--- gcc-3.3/libf2c/libF77/z_div.c	2002-06-01 12:38:28.000000000 +0000
***************
*** 1,44 ****
  #include "f2c.h"
  
! #ifdef KR_headers
! extern VOID sig_die();
! VOID z_div(c, a, b) doublecomplex *a, *b, *c;
! #else
! extern void sig_die(char*, int);
! void z_div(doublecomplex *c, doublecomplex *a, doublecomplex *b)
! #endif
  {
! 	double ratio, den;
! 	double abr, abi, cr;
  
! 	if( (abr = b->r) < 0.)
! 		abr = - abr;
! 	if( (abi = b->i) < 0.)
! 		abi = - abi;
! 	if( abr <= abi )
! 		{
! 		if(abi == 0) {
  #ifdef IEEE_COMPLEX_DIVIDE
! 			if (a->i != 0 || a->r != 0)
! 				abi = 1.;
! 			c->i = c->r = abi / abr;
! 			return;
  #else
! 			sig_die("complex division by zero", 1);
  #endif
- 			}
- 		ratio = b->r / b->i ;
- 		den = b->i * (1 + ratio*ratio);
- 		cr = (a->r*ratio + a->i) / den;
- 		c->i = (a->i*ratio - a->r) / den;
- 		}
- 
- 	else
- 		{
- 		ratio = b->i / b->r ;
- 		den = b->r * (1 + ratio*ratio);
- 		cr = (a->r + a->i*ratio) / den;
- 		c->i = (a->i - a->r*ratio) / den;
- 		}
- 	c->r = cr;
  	}
--- 1,41 ----
  #include "f2c.h"
  
! extern void sig_die (char *, int);
! void
! z_div (doublecomplex * c, doublecomplex * a, doublecomplex * b)
  {
!   double ratio, den;
!   double abr, abi, cr;
  
!   if ((abr = b->r) < 0.)
!     abr = -abr;
!   if ((abi = b->i) < 0.)
!     abi = -abi;
!   if (abr <= abi)
!     {
!       if (abi == 0)
! 	{
  #ifdef IEEE_COMPLEX_DIVIDE
! 	  if (a->i != 0 || a->r != 0)
! 	    abi = 1.;
! 	  c->i = c->r = abi / abr;
! 	  return;
  #else
! 	  sig_die ("complex division by zero", 1);
  #endif
  	}
+       ratio = b->r / b->i;
+       den = b->i * (1 + ratio * ratio);
+       cr = (a->r * ratio + a->i) / den;
+       c->i = (a->i * ratio - a->r) / den;
+     }
+ 
+   else
+     {
+       ratio = b->i / b->r;
+       den = b->r * (1 + ratio * ratio);
+       cr = (a->r + a->i * ratio) / den;
+       c->i = (a->i - a->r * ratio) / den;
+     }
+   c->r = cr;
+ }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/z_exp.c gcc-3.3/libf2c/libF77/z_exp.c
*** gcc-3.2.3/libf2c/libF77/z_exp.c	1999-05-03 08:35:16.000000000 +0000
--- gcc-3.3/libf2c/libF77/z_exp.c	2002-06-01 12:38:28.000000000 +0000
***************
*** 1,17 ****
  #include "f2c.h"
  
- #ifdef KR_headers
- double exp(), cos(), sin();
- VOID z_exp(r, z) doublecomplex *r, *z;
- #else
  #undef abs
  #include "math.h"
! void z_exp(doublecomplex *r, doublecomplex *z)
! #endif
  {
! 	double expx, zi = z->i;
  
! 	expx = exp(z->r);
! 	r->r = expx * cos(zi);
! 	r->i = expx * sin(zi);
! 	}
--- 1,13 ----
  #include "f2c.h"
  
  #undef abs
  #include "math.h"
! void
! z_exp (doublecomplex * r, doublecomplex * z)
  {
!   double expx, zi = z->i;
  
!   expx = exp (z->r);
!   r->r = expx * cos (zi);
!   r->i = expx * sin (zi);
! }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/z_log.c gcc-3.3/libf2c/libF77/z_log.c
*** gcc-3.2.3/libf2c/libF77/z_log.c	2000-12-09 15:34:53.000000000 +0000
--- gcc-3.3/libf2c/libF77/z_log.c	2002-06-01 12:38:28.000000000 +0000
***************
*** 1,63 ****
  #include "f2c.h"
  
- #ifdef KR_headers
- double log(), f__cabs(), atan2();
- VOID z_log(r, z) doublecomplex *r, *z;
- #else
  #undef abs
  #include "math.h"
! extern double f__cabs(double, double);
! void z_log(doublecomplex *r, doublecomplex *z)
! #endif
  {
! 	double s, s0, t, t2, u, v;
! 	double zi = z->i, zr = z->r;
  
! 	r->i = atan2(zi, zr);
  #ifdef Pre20000310
! 	r->r = log( f__cabs( zr, zi ) );
  #else
! 	if (zi < 0)
! 		zi = -zi;
! 	if (zr < 0)
! 		zr = -zr;
! 	if (zr < zi) {
! 		t = zi;
! 		zi = zr;
! 		zr = t;
! 		}
! 	t = zi/zr;
! 	s = zr * sqrt(1 + t*t);
! 	/* now s = f__cabs(zi,zr), and zr = |zr| >= |zi| = zi */
! 	if ((t = s - 1) < 0)
! 		t = -t;
! 	if (t > .01)
! 		r->r = log(s);
! 	else {
  
  #ifdef Comment
  
! 	log(1+x) = x - x^2/2 + x^3/3 - x^4/4 + - ...
! 
! 		 = x(1 - x/2 + x^2/3 -+...)
! 
! 	[sqrt(y^2 + z^2) - 1] * [sqrt(y^2 + z^2) + 1] = y^2 + z^2 - 1, so
! 
! 	sqrt(y^2 + z^2) - 1 = (y^2 + z^2 - 1) / [sqrt(y^2 + z^2) + 1]
! 
! #endif /*Comment*/
! 
! 		t = ((zr*zr - 1.) + zi*zi) / (s + 1);
! 		t2 = t*t;
! 		s = 1. - 0.5*t;
! 		u = v = 1;
! 		do {
! 			s0 = s;
! 			u *= t2;
! 			v += 2;
! 			s += u/v - t*u/(v+1);
! 			} while(s > s0);
! 		r->r = s*t;
! 		}
! #endif
  	}
--- 1,59 ----
  #include "f2c.h"
  
  #undef abs
  #include "math.h"
! extern double f__cabs (double, double);
! void
! z_log (doublecomplex * r, doublecomplex * z)
  {
!   double s, s0, t, t2, u, v;
!   double zi = z->i, zr = z->r;
  
!   r->i = atan2 (zi, zr);
  #ifdef Pre20000310
!   r->r = log (f__cabs (zr, zi));
  #else
!   if (zi < 0)
!     zi = -zi;
!   if (zr < 0)
!     zr = -zr;
!   if (zr < zi)
!     {
!       t = zi;
!       zi = zr;
!       zr = t;
!     }
!   t = zi / zr;
!   s = zr * sqrt (1 + t * t);
!   /* now s = f__cabs(zi,zr), and zr = |zr| >= |zi| = zi */
!   if ((t = s - 1) < 0)
!     t = -t;
!   if (t > .01)
!     r->r = log (s);
!   else
!     {
  
  #ifdef Comment
  
!       log (1 + x) = x - x ^ 2 / 2 + x ^ 3 / 3 - x ^ 4 / 4 + -...
! 	= x (1 - x / 2 + x ^ 2 / 3 - +...)
! 	[sqrt (y ^ 2 + z ^ 2) - 1] *[sqrt (y ^ 2 + z ^ 2) + 1] =
! 	y ^ 2 + z ^ 2 - 1, so sqrt (y ^ 2 + z ^ 2) - 1 =
! 	(y ^ 2 + z ^ 2 - 1) /[sqrt (y ^ 2 + z ^ 2) + 1]
! #endif /*Comment */
! 	t = ((zr * zr - 1.) + zi * zi) / (s + 1);
!       t2 = t * t;
!       s = 1. - 0.5 * t;
!       u = v = 1;
!       do
! 	{
! 	  s0 = s;
! 	  u *= t2;
! 	  v += 2;
! 	  s += u / v - t * u / (v + 1);
  	}
+       while (s > s0);
+       r->r = s * t;
+     }
+ #endif
+ }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/z_sin.c gcc-3.3/libf2c/libF77/z_sin.c
*** gcc-3.2.3/libf2c/libF77/z_sin.c	1999-05-03 08:35:18.000000000 +0000
--- gcc-3.3/libf2c/libF77/z_sin.c	2002-06-01 12:38:28.000000000 +0000
***************
*** 1,15 ****
  #include "f2c.h"
  
- #ifdef KR_headers
- double sin(), cos(), sinh(), cosh();
- VOID z_sin(r, z) doublecomplex *r, *z;
- #else
  #undef abs
  #include "math.h"
! void z_sin(doublecomplex *r, doublecomplex *z)
! #endif
  {
! 	double zi = z->i, zr = z->r;
! 	r->r = sin(zr) * cosh(zi);
! 	r->i = cos(zr) * sinh(zi);
! 	}
--- 1,11 ----
  #include "f2c.h"
  
  #undef abs
  #include "math.h"
! void
! z_sin (doublecomplex * r, doublecomplex * z)
  {
!   double zi = z->i, zr = z->r;
!   r->r = sin (zr) * cosh (zi);
!   r->i = cos (zr) * sinh (zi);
! }
diff -Nrc3pad gcc-3.2.3/libf2c/libF77/z_sqrt.c gcc-3.3/libf2c/libF77/z_sqrt.c
*** gcc-3.2.3/libf2c/libF77/z_sqrt.c	1999-05-03 08:33:21.000000000 +0000
--- gcc-3.3/libf2c/libF77/z_sqrt.c	2002-06-01 12:38:28.000000000 +0000
***************
*** 1,29 ****
  #include "f2c.h"
  
- #ifdef KR_headers
- double sqrt(), f__cabs();
- VOID z_sqrt(r, z) doublecomplex *r, *z;
- #else
  #undef abs
  #include "math.h"
! extern double f__cabs(double, double);
! void z_sqrt(doublecomplex *r, doublecomplex *z)
! #endif
  {
! 	double mag, zi = z->i, zr = z->r;
  
! 	if( (mag = f__cabs(zr, zi)) == 0.)
! 		r->r = r->i = 0.;
! 	else if(zr > 0)
! 		{
! 		r->r = sqrt(0.5 * (mag + zr) );
! 		r->i = zi / r->r / 2;
! 		}
! 	else
! 		{
! 		r->i = sqrt(0.5 * (mag - zr) );
! 		if(zi < 0)
! 			r->i = - r->i;
! 		r->r = zi / r->i / 2;
! 		}
! 	}
--- 1,25 ----
  #include "f2c.h"
  
  #undef abs
  #include "math.h"
! extern double f__cabs (double, double);
! void
! z_sqrt (doublecomplex * r, doublecomplex * z)
  {
!   double mag, zi = z->i, zr = z->r;
  
!   if ((mag = f__cabs (zr, zi)) == 0.)
!     r->r = r->i = 0.;
!   else if (zr > 0)
!     {
!       r->r = sqrt (0.5 * (mag + zr));
!       r->i = zi / r->r / 2;
!     }
!   else
!     {
!       r->i = sqrt (0.5 * (mag - zr));
!       if (zi < 0)
! 	r->i = -r->i;
!       r->r = zi / r->i / 2;
!     }
! }
diff -Nrc3pad gcc-3.2.3/libf2c/libI77/backspace.c gcc-3.3/libf2c/libI77/backspace.c
*** gcc-3.2.3/libf2c/libI77/backspace.c	2001-07-06 12:09:39.000000000 +0000
--- gcc-3.3/libf2c/libI77/backspace.c	2002-06-01 12:38:29.000000000 +0000
***************
*** 2,74 ****
  #include <sys/types.h>
  #include "f2c.h"
  #include "fio.h"
! #ifdef KR_headers
! integer f_back(a) alist *a;
! #else
! integer f_back(alist *a)
! #endif
! {	unit *b;
! 	off_t v, w, x, y, z;
! 	uiolen n;
! 	FILE *f;
  
! 	f__curunit = b = &f__units[a->aunit];	/* curunit for error messages */
! 	if (f__init & 2)
! 		f__fatal (131, "I/O recursion");
! 	if(a->aunit >= MXUNIT || a->aunit < 0)
! 		err(a->aerr,101,"backspace");
! 	if(b->useek==0) err(a->aerr,106,"backspace");
! 	if(b->ufd == NULL) {
! 		fk_open(1, 1, a->aunit);
! 		return(0);
! 		}
! 	if(b->uend==1)
! 	{	b->uend=0;
! 		return(0);
! 	}
! 	if(b->uwrt) {
! 		t_runc(a);
! 		if (f__nowreading(b))
! 			err(a->aerr,errno,"backspace");
! 		}
! 	f = b->ufd;	/* may have changed in t_runc() */
! 	if(b->url>0)
! 	{
! 		x=FTELL(f);
! 		y = x % b->url;
! 		if(y == 0) x--;
! 		x /= b->url;
! 		x *= b->url;
! 		FSEEK(f,x,SEEK_SET);
! 		return(0);
! 	}
  
! 	if(b->ufmt==0)
! 	{	FSEEK(f,-(off_t)sizeof(uiolen),SEEK_CUR);
! 		fread((char *)&n,sizeof(uiolen),1,f);
! 		FSEEK(f,-(off_t)n-2*sizeof(uiolen),SEEK_CUR);
! 		return(0);
  	}
! 	w = x = FTELL(f);
! 	z = 0;
!  loop:
! 	while(x) {
! 		x -= x < 64 ? x : 64;
! 		FSEEK(f,x,SEEK_SET);
! 		for(y = x; y < w; y++) {
! 			if (getc(f) != '\n')
! 				continue;
! 			v = FTELL(f);
! 			if (v == w) {
! 				if (z)
! 					goto break2;
! 				goto loop;
! 				}
! 			z = v;
! 			}
! 		err(a->aerr,(EOF),"backspace");
! 		}
!  break2:
! 	FSEEK(f, z, SEEK_SET);
! 	return 0;
  }
--- 2,81 ----
  #include <sys/types.h>
  #include "f2c.h"
  #include "fio.h"
! integer
! f_back (alist * a)
! {
!   unit *b;
!   off_t v, w, x, y, z;
!   uiolen n;
!   FILE *f;
  
!   f__curunit = b = &f__units[a->aunit];	/* curunit for error messages */
!   if (f__init & 2)
!     f__fatal (131, "I/O recursion");
!   if (a->aunit >= MXUNIT || a->aunit < 0)
!     err (a->aerr, 101, "backspace");
!   if (b->useek == 0)
!     err (a->aerr, 106, "backspace");
!   if (b->ufd == NULL)
!     {
!       fk_open (1, 1, a->aunit);
!       return (0);
!     }
!   if (b->uend == 1)
!     {
!       b->uend = 0;
!       return (0);
!     }
!   if (b->uwrt)
!     {
!       t_runc (a);
!       if (f__nowreading (b))
! 	err (a->aerr, errno, "backspace");
!     }
!   f = b->ufd;			/* may have changed in t_runc() */
!   if (b->url > 0)
!     {
!       x = FTELL (f);
!       y = x % b->url;
!       if (y == 0)
! 	x--;
!       x /= b->url;
!       x *= b->url;
!       FSEEK (f, x, SEEK_SET);
!       return (0);
!     }
  
!   if (b->ufmt == 0)
!     {
!       FSEEK (f, -(off_t) sizeof (uiolen), SEEK_CUR);
!       fread ((char *) &n, sizeof (uiolen), 1, f);
!       FSEEK (f, -(off_t) n - 2 * sizeof (uiolen), SEEK_CUR);
!       return (0);
!     }
!   w = x = FTELL (f);
!   z = 0;
! loop:
!   while (x)
!     {
!       x -= x < 64 ? x : 64;
!       FSEEK (f, x, SEEK_SET);
!       for (y = x; y < w; y++)
! 	{
! 	  if (getc (f) != '\n')
! 	    continue;
! 	  v = FTELL (f);
! 	  if (v == w)
! 	    {
! 	      if (z)
! 		goto break2;
! 	      goto loop;
! 	    }
! 	  z = v;
  	}
!       err (a->aerr, (EOF), "backspace");
!     }
! break2:
!   FSEEK (f, z, SEEK_SET);
!   return 0;
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libI77/close.c gcc-3.3/libf2c/libI77/close.c
*** gcc-3.2.3/libf2c/libI77/close.c	2001-05-16 18:59:29.000000000 +0000
--- gcc-3.3/libf2c/libI77/close.c	2002-06-01 12:38:29.000000000 +0000
***************
*** 1,9 ****
  #include "config.h"
  #include "f2c.h"
  #include "fio.h"
! #ifdef KR_headers
! integer f_clos(a) cllist *a;
! #else
  #undef abs
  #undef min
  #undef max
--- 1,7 ----
  #include "config.h"
  #include "f2c.h"
  #include "fio.h"
! 
  #undef abs
  #undef min
  #undef max
*************** integer f_clos(a) cllist *a;
*** 16,106 ****
  #if defined (MSDOS) && !defined (GO32)
  #include "io.h"
  #else
! #ifdef __cplusplus
! extern "C" int unlink(const char*);
! #else
! extern int unlink(const char*);
! #endif
  #endif
  #endif
  
! integer f_clos(cllist *a)
! #endif
! {	unit *b;
  
! 	if (f__init & 2)
! 		f__fatal (131, "I/O recursion");
! 	if(a->cunit >= MXUNIT) return(0);
! 	b= &f__units[a->cunit];
! 	if(b->ufd==NULL)
! 		goto done;
! 	if (b->uscrtch == 1)
! 		goto Delete;
! 	if (!a->csta)
! 		goto Keep;
! 	switch(*a->csta) {
! 		default:
! 	 	Keep:
! 		case 'k':
! 		case 'K':
! 			if(b->uwrt == 1)
! 				t_runc((alist *)a);
! 			if(b->ufnm) {
! 				fclose(b->ufd);
! 				free(b->ufnm);
! 				}
! 			break;
! 		case 'd':
! 		case 'D':
! 		Delete:
! 			fclose(b->ufd);
! 			if(b->ufnm) {
! 				unlink(b->ufnm); /*SYSDEP*/
! 				free(b->ufnm);
! 				}
! 		}
! 	b->ufd=NULL;
!  done:
! 	b->uend=0;
! 	b->ufnm=NULL;
! 	return(0);
  	}
!  void
! #ifdef KR_headers
! f_exit()
! #else
! f_exit(void)
! #endif
! {	int i;
! 	static cllist xx;
! 	if (! (f__init & 1))
! 		return;		/* Not initialized, so no open units. */
! 	/* I/O no longer in progress.  If, during an I/O operation (such
! 	   as waiting for the user to enter a line), there is an
! 	   interrupt (such as ^C to stop the program on a UNIX system),
! 	   f_exit() is called, but there is no longer any I/O in
! 	   progress.  Without turning off this flag, f_clos() would
! 	   think that there is an I/O recursion in this circumstance. */
! 	f__init &= ~2;
! 	if (!xx.cerr) {
! 		xx.cerr=1;
! 		xx.csta=NULL;
! 		for(i=0;i<MXUNIT;i++)
! 		{
! 			xx.cunit=i;
! 			(void) f_clos(&xx);
! 		}
  	}
  }
!  int
! #ifdef KR_headers
! G77_flush_0 ()
! #else
  G77_flush_0 (void)
! #endif
! {	int i;
! 	for(i=0;i<MXUNIT;i++)
! 		if(f__units[i].ufd != NULL && f__units[i].uwrt)
! 			fflush(f__units[i].ufd);
! return 0;
  }
--- 14,101 ----
  #if defined (MSDOS) && !defined (GO32)
  #include "io.h"
  #else
! extern int unlink (const char *);
  #endif
  #endif
  
! integer
! f_clos (cllist * a)
! {
!   unit *b;
  
!   if (f__init & 2)
!     f__fatal (131, "I/O recursion");
!   if (a->cunit >= MXUNIT)
!     return (0);
!   b = &f__units[a->cunit];
!   if (b->ufd == NULL)
!     goto done;
!   if (b->uscrtch == 1)
!     goto Delete;
!   if (!a->csta)
!     goto Keep;
!   switch (*a->csta)
!     {
!     default:
!     Keep:
!     case 'k':
!     case 'K':
!       if (b->uwrt == 1)
! 	t_runc ((alist *) a);
!       if (b->ufnm)
! 	{
! 	  fclose (b->ufd);
! 	  free (b->ufnm);
  	}
!       break;
!     case 'd':
!     case 'D':
!     Delete:
!       fclose (b->ufd);
!       if (b->ufnm)
! 	{
! 	  unlink (b->ufnm);
! 	  /*SYSDEP*/ free (b->ufnm);
  	}
+     }
+   b->ufd = NULL;
+ done:
+   b->uend = 0;
+   b->ufnm = NULL;
+   return (0);
  }
! 
! void
! f_exit (void)
! {
!   int i;
!   static cllist xx;
!   if (!(f__init & 1))
!     return;			/* Not initialized, so no open units. */
!   /* I/O no longer in progress.  If, during an I/O operation (such
!      as waiting for the user to enter a line), there is an
!      interrupt (such as ^C to stop the program on a UNIX system),
!      f_exit() is called, but there is no longer any I/O in
!      progress.  Without turning off this flag, f_clos() would
!      think that there is an I/O recursion in this circumstance. */
!   f__init &= ~2;
!   if (!xx.cerr)
!     {
!       xx.cerr = 1;
!       xx.csta = NULL;
!       for (i = 0; i < MXUNIT; i++)
! 	{
! 	  xx.cunit = i;
! 	  (void) f_clos (&xx);
! 	}
!     }
! }
! int
  G77_flush_0 (void)
! {
!   int i;
!   for (i = 0; i < MXUNIT; i++)
!     if (f__units[i].ufd != NULL && f__units[i].uwrt)
!       fflush (f__units[i].ufd);
!   return 0;
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libI77/configure gcc-3.3/libf2c/libI77/configure
*** gcc-3.2.3/libf2c/libI77/configure	2002-01-15 17:27:05.000000000 +0000
--- gcc-3.3/libf2c/libI77/configure	2003-04-24 01:58:04.000000000 +0000
*************** program_suffix=NONE
*** 28,33 ****
--- 28,34 ----
  program_transform_name=s,x,x,
  silent=
  site=
+ sitefile=
  srcdir=
  target=NONE
  verbose=
*************** Configuration:
*** 142,147 ****
--- 143,149 ----
    --help                  print this message
    --no-create             do not create output files
    --quiet, --silent       do not print \`checking...' messages
+   --site-file=FILE        use FILE as the site file
    --version               print the version of autoconf that created configure
  Directory and file names:
    --prefix=PREFIX         install architecture-independent files in PREFIX
*************** EOF
*** 312,317 ****
--- 314,324 ----
    -site=* | --site=* | --sit=*)
      site="$ac_optarg" ;;
  
+   -site-file | --site-file | --site-fil | --site-fi | --site-f)
+     ac_prev=sitefile ;;
+   -site-file=* | --site-file=* | --site-fil=* | --site-fi=* | --site-f=*)
+     sitefile="$ac_optarg" ;;
+ 
    -srcdir | --srcdir | --srcdi | --srcd | --src | --sr)
      ac_prev=srcdir ;;
    -srcdir=* | --srcdir=* | --srcdi=* | --srcd=* | --src=* | --sr=*)
*************** fi
*** 477,488 ****
  srcdir=`echo "${srcdir}" | sed 's%\([^/]\)/*$%\1%'`
  
  # Prefer explicitly selected file to automatically selected ones.
! if test -z "$CONFIG_SITE"; then
!   if test "x$prefix" != xNONE; then
!     CONFIG_SITE="$prefix/share/config.site $prefix/etc/config.site"
!   else
!     CONFIG_SITE="$ac_default_prefix/share/config.site $ac_default_prefix/etc/config.site"
    fi
  fi
  for ac_site_file in $CONFIG_SITE; do
    if test -r "$ac_site_file"; then
--- 484,499 ----
  srcdir=`echo "${srcdir}" | sed 's%\([^/]\)/*$%\1%'`
  
  # Prefer explicitly selected file to automatically selected ones.
! if test -z "$sitefile"; then
!   if test -z "$CONFIG_SITE"; then
!     if test "x$prefix" != xNONE; then
!       CONFIG_SITE="$prefix/share/config.site $prefix/etc/config.site"
!     else
!       CONFIG_SITE="$ac_default_prefix/share/config.site $ac_default_prefix/etc/config.site"
!     fi
    fi
+ else
+   CONFIG_SITE="$sitefile"
  fi
  for ac_site_file in $CONFIG_SITE; do
    if test -r "$ac_site_file"; then
*************** fi
*** 523,554 ****
  
  
  
- # These defines are necessary to get 64-bit file size support.
- 
- cat >> confdefs.h <<\EOF
- #define _XOPEN_SOURCE 500L
- EOF
- 
- # The following is needed by irix6.2 so that struct timeval is declared.
- cat >> confdefs.h <<\EOF
- #define _XOPEN_SOURCE_EXTENDED 1
- EOF
- 
- # The following is needed by Solaris2.5.1 so that struct timeval is declared.
- cat >> confdefs.h <<\EOF
- #define __EXTENSIONS__ 1
- EOF
- 
- cat >> confdefs.h <<\EOF
- #define _FILE_OFFSET_BITS 64
- EOF
- 
- cat >> confdefs.h <<\EOF
- #define _LARGEFILE_SOURCE 1
- EOF
- 
- 
- 
  
  
  # For g77 we'll set CC to point at the built gcc, but this will get it into
--- 534,539 ----
*************** EOF
*** 556,562 ****
  # Extract the first word of "gcc", so it can be a program name with args.
  set dummy gcc; ac_word=$2
  echo $ac_n "checking for $ac_word""... $ac_c" 1>&6
! echo "configure:560: checking for $ac_word" >&5
  if eval "test \"`echo '$''{'ac_cv_prog_CC'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
--- 541,547 ----
  # Extract the first word of "gcc", so it can be a program name with args.
  set dummy gcc; ac_word=$2
  echo $ac_n "checking for $ac_word""... $ac_c" 1>&6
! echo "configure:545: checking for $ac_word" >&5
  if eval "test \"`echo '$''{'ac_cv_prog_CC'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
*************** if test -z "$CC"; then
*** 586,592 ****
    # Extract the first word of "cc", so it can be a program name with args.
  set dummy cc; ac_word=$2
  echo $ac_n "checking for $ac_word""... $ac_c" 1>&6
! echo "configure:590: checking for $ac_word" >&5
  if eval "test \"`echo '$''{'ac_cv_prog_CC'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
--- 571,577 ----
    # Extract the first word of "cc", so it can be a program name with args.
  set dummy cc; ac_word=$2
  echo $ac_n "checking for $ac_word""... $ac_c" 1>&6
! echo "configure:575: checking for $ac_word" >&5
  if eval "test \"`echo '$''{'ac_cv_prog_CC'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
*************** fi
*** 637,643 ****
        # Extract the first word of "cl", so it can be a program name with args.
  set dummy cl; ac_word=$2
  echo $ac_n "checking for $ac_word""... $ac_c" 1>&6
! echo "configure:641: checking for $ac_word" >&5
  if eval "test \"`echo '$''{'ac_cv_prog_CC'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
--- 622,628 ----
        # Extract the first word of "cl", so it can be a program name with args.
  set dummy cl; ac_word=$2
  echo $ac_n "checking for $ac_word""... $ac_c" 1>&6
! echo "configure:626: checking for $ac_word" >&5
  if eval "test \"`echo '$''{'ac_cv_prog_CC'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
*************** fi
*** 670,676 ****
  
  
  echo $ac_n "checking whether we are using GNU C""... $ac_c" 1>&6
! echo "configure:674: checking whether we are using GNU C" >&5
  if eval "test \"`echo '$''{'ac_cv_prog_gcc'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
--- 655,661 ----
  
  
  echo $ac_n "checking whether we are using GNU C""... $ac_c" 1>&6
! echo "configure:659: checking whether we are using GNU C" >&5
  if eval "test \"`echo '$''{'ac_cv_prog_gcc'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
*************** else
*** 679,685 ****
    yes;
  #endif
  EOF
! if { ac_try='${CC-cc} -E conftest.c'; { (eval echo configure:683: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; }; } | egrep yes >/dev/null 2>&1; then
    ac_cv_prog_gcc=yes
  else
    ac_cv_prog_gcc=no
--- 664,670 ----
    yes;
  #endif
  EOF
! if { ac_try='${CC-cc} -E conftest.c'; { (eval echo configure:668: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; }; } | egrep yes >/dev/null 2>&1; then
    ac_cv_prog_gcc=yes
  else
    ac_cv_prog_gcc=no
*************** ac_test_CFLAGS="${CFLAGS+set}"
*** 698,704 ****
  ac_save_CFLAGS="$CFLAGS"
  CFLAGS=
  echo $ac_n "checking whether ${CC-cc} accepts -g""... $ac_c" 1>&6
! echo "configure:702: checking whether ${CC-cc} accepts -g" >&5
  if eval "test \"`echo '$''{'ac_cv_prog_cc_g'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
--- 683,689 ----
  ac_save_CFLAGS="$CFLAGS"
  CFLAGS=
  echo $ac_n "checking whether ${CC-cc} accepts -g""... $ac_c" 1>&6
! echo "configure:687: checking whether ${CC-cc} accepts -g" >&5
  if eval "test \"`echo '$''{'ac_cv_prog_cc_g'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
*************** else
*** 730,742 ****
  fi
  
  
  LIBTOOL='$(SHELL) ../libtool'
  
  
  test "$AR" || AR=ar
  
  echo $ac_n "checking whether ${MAKE-make} sets \${MAKE}""... $ac_c" 1>&6
! echo "configure:740: checking whether ${MAKE-make} sets \${MAKE}" >&5
  set dummy ${MAKE-make}; ac_make=`echo "$2" | sed 'y%./+-%__p_%'`
  if eval "test \"`echo '$''{'ac_cv_prog_make_${ac_make}_set'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
--- 715,778 ----
  fi
  
  
+ # These defines are necessary to get 64-bit file size support.
+ # NetBSD 1.4 header files does not support XOPEN_SOURCE == 600, but it
+ # handles 64-bit file sizes without needing these defines.
+ echo $ac_n "checking whether _XOPEN_SOURCE may be defined""... $ac_c" 1>&6
+ echo "configure:723: checking whether _XOPEN_SOURCE may be defined" >&5
+ cat > conftest.$ac_ext <<EOF
+ #line 725 "configure"
+ #include "confdefs.h"
+ #define _XOPEN_SOURCE 600L
+ #include <unistd.h>
+ int main() {
+ 
+ ; return 0; }
+ EOF
+ if { (eval echo configure:733: \"$ac_compile\") 1>&5; (eval $ac_compile) 2>&5; }; then
+   rm -rf conftest*
+   may_use_xopen_source=yes
+ else
+   echo "configure: failed program was:" >&5
+   cat conftest.$ac_ext >&5
+   rm -rf conftest*
+   may_use_xopen_source=no
+ fi
+ rm -f conftest*
+ echo "$ac_t""$may_use_xopen_source" 1>&6
+ if test $may_use_xopen_source = yes; then
+   cat >> confdefs.h <<\EOF
+ #define _XOPEN_SOURCE 600L
+ EOF
+ 
+   # The following is needed by irix6.2 so that struct timeval is declared.
+   cat >> confdefs.h <<\EOF
+ #define _XOPEN_SOURCE_EXTENDED 1
+ EOF
+ 
+   # The following is needed by Solaris2.5.1 so that struct timeval is declared.
+   cat >> confdefs.h <<\EOF
+ #define __EXTENSIONS__ 1
+ EOF
+ 
+   cat >> confdefs.h <<\EOF
+ #define _FILE_OFFSET_BITS 64
+ EOF
+ 
+   cat >> confdefs.h <<\EOF
+ #define _LARGEFILE_SOURCE 1
+ EOF
+ 
+ fi
+ 
+ 
  LIBTOOL='$(SHELL) ../libtool'
  
  
  test "$AR" || AR=ar
  
  echo $ac_n "checking whether ${MAKE-make} sets \${MAKE}""... $ac_c" 1>&6
! echo "configure:776: checking whether ${MAKE-make} sets \${MAKE}" >&5
  set dummy ${MAKE-make}; ac_make=`echo "$2" | sed 'y%./+-%__p_%'`
  if eval "test \"`echo '$''{'ac_cv_prog_make_${ac_make}_set'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
*************** fi
*** 766,772 ****
  
  # Sanity check for the cross-compilation case:
  echo $ac_n "checking how to run the C preprocessor""... $ac_c" 1>&6
! echo "configure:770: checking how to run the C preprocessor" >&5
  # On Suns, sometimes $CPP names a directory.
  if test -n "$CPP" && test -d "$CPP"; then
    CPP=
--- 802,808 ----
  
  # Sanity check for the cross-compilation case:
  echo $ac_n "checking how to run the C preprocessor""... $ac_c" 1>&6
! echo "configure:806: checking how to run the C preprocessor" >&5
  # On Suns, sometimes $CPP names a directory.
  if test -n "$CPP" && test -d "$CPP"; then
    CPP=
*************** else
*** 781,793 ****
    # On the NeXT, cc -E runs the code through the compiler's parser,
    # not just through cpp.
    cat > conftest.$ac_ext <<EOF
! #line 785 "configure"
  #include "confdefs.h"
  #include <assert.h>
  Syntax Error
  EOF
  ac_try="$ac_cpp conftest.$ac_ext >/dev/null 2>conftest.out"
! { (eval echo configure:791: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; }
  ac_err=`grep -v '^ *+' conftest.out | grep -v "^conftest.${ac_ext}\$"`
  if test -z "$ac_err"; then
    :
--- 817,829 ----
    # On the NeXT, cc -E runs the code through the compiler's parser,
    # not just through cpp.
    cat > conftest.$ac_ext <<EOF
! #line 821 "configure"
  #include "confdefs.h"
  #include <assert.h>
  Syntax Error
  EOF
  ac_try="$ac_cpp conftest.$ac_ext >/dev/null 2>conftest.out"
! { (eval echo configure:827: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; }
  ac_err=`grep -v '^ *+' conftest.out | grep -v "^conftest.${ac_ext}\$"`
  if test -z "$ac_err"; then
    :
*************** else
*** 798,810 ****
    rm -rf conftest*
    CPP="${CC-cc} -E -traditional-cpp"
    cat > conftest.$ac_ext <<EOF
! #line 802 "configure"
  #include "confdefs.h"
  #include <assert.h>
  Syntax Error
  EOF
  ac_try="$ac_cpp conftest.$ac_ext >/dev/null 2>conftest.out"
! { (eval echo configure:808: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; }
  ac_err=`grep -v '^ *+' conftest.out | grep -v "^conftest.${ac_ext}\$"`
  if test -z "$ac_err"; then
    :
--- 834,846 ----
    rm -rf conftest*
    CPP="${CC-cc} -E -traditional-cpp"
    cat > conftest.$ac_ext <<EOF
! #line 838 "configure"
  #include "confdefs.h"
  #include <assert.h>
  Syntax Error
  EOF
  ac_try="$ac_cpp conftest.$ac_ext >/dev/null 2>conftest.out"
! { (eval echo configure:844: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; }
  ac_err=`grep -v '^ *+' conftest.out | grep -v "^conftest.${ac_ext}\$"`
  if test -z "$ac_err"; then
    :
*************** else
*** 815,827 ****
    rm -rf conftest*
    CPP="${CC-cc} -nologo -E"
    cat > conftest.$ac_ext <<EOF
! #line 819 "configure"
  #include "confdefs.h"
  #include <assert.h>
  Syntax Error
  EOF
  ac_try="$ac_cpp conftest.$ac_ext >/dev/null 2>conftest.out"
! { (eval echo configure:825: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; }
  ac_err=`grep -v '^ *+' conftest.out | grep -v "^conftest.${ac_ext}\$"`
  if test -z "$ac_err"; then
    :
--- 851,863 ----
    rm -rf conftest*
    CPP="${CC-cc} -nologo -E"
    cat > conftest.$ac_ext <<EOF
! #line 855 "configure"
  #include "confdefs.h"
  #include <assert.h>
  Syntax Error
  EOF
  ac_try="$ac_cpp conftest.$ac_ext >/dev/null 2>conftest.out"
! { (eval echo configure:861: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; }
  ac_err=`grep -v '^ *+' conftest.out | grep -v "^conftest.${ac_ext}\$"`
  if test -z "$ac_err"; then
    :
*************** echo "$ac_t""$CPP" 1>&6
*** 847,863 ****
  
  ac_safe=`echo "stdio.h" | sed 'y%./+-%__p_%'`
  echo $ac_n "checking for stdio.h""... $ac_c" 1>&6
! echo "configure:851: checking for stdio.h" >&5
  if eval "test \"`echo '$''{'ac_cv_header_$ac_safe'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 856 "configure"
  #include "confdefs.h"
  #include <stdio.h>
  EOF
  ac_try="$ac_cpp conftest.$ac_ext >/dev/null 2>conftest.out"
! { (eval echo configure:861: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; }
  ac_err=`grep -v '^ *+' conftest.out | grep -v "^conftest.${ac_ext}\$"`
  if test -z "$ac_err"; then
    rm -rf conftest*
--- 883,899 ----
  
  ac_safe=`echo "stdio.h" | sed 'y%./+-%__p_%'`
  echo $ac_n "checking for stdio.h""... $ac_c" 1>&6
! echo "configure:887: checking for stdio.h" >&5
  if eval "test \"`echo '$''{'ac_cv_header_$ac_safe'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 892 "configure"
  #include "confdefs.h"
  #include <stdio.h>
  EOF
  ac_try="$ac_cpp conftest.$ac_ext >/dev/null 2>conftest.out"
! { (eval echo configure:897: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; }
  ac_err=`grep -v '^ *+' conftest.out | grep -v "^conftest.${ac_ext}\$"`
  if test -z "$ac_err"; then
    rm -rf conftest*
*************** fi
*** 885,896 ****
  
  
  echo $ac_n "checking for ANSI C header files""... $ac_c" 1>&6
! echo "configure:889: checking for ANSI C header files" >&5
  if eval "test \"`echo '$''{'ac_cv_header_stdc'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 894 "configure"
  #include "confdefs.h"
  #include <stdlib.h>
  #include <stdarg.h>
--- 921,932 ----
  
  
  echo $ac_n "checking for ANSI C header files""... $ac_c" 1>&6
! echo "configure:925: checking for ANSI C header files" >&5
  if eval "test \"`echo '$''{'ac_cv_header_stdc'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 930 "configure"
  #include "confdefs.h"
  #include <stdlib.h>
  #include <stdarg.h>
*************** else
*** 898,904 ****
  #include <float.h>
  EOF
  ac_try="$ac_cpp conftest.$ac_ext >/dev/null 2>conftest.out"
! { (eval echo configure:902: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; }
  ac_err=`grep -v '^ *+' conftest.out | grep -v "^conftest.${ac_ext}\$"`
  if test -z "$ac_err"; then
    rm -rf conftest*
--- 934,940 ----
  #include <float.h>
  EOF
  ac_try="$ac_cpp conftest.$ac_ext >/dev/null 2>conftest.out"
! { (eval echo configure:938: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; }
  ac_err=`grep -v '^ *+' conftest.out | grep -v "^conftest.${ac_ext}\$"`
  if test -z "$ac_err"; then
    rm -rf conftest*
*************** rm -f conftest*
*** 915,921 ****
  if test $ac_cv_header_stdc = yes; then
    # SunOS 4.x string.h does not declare mem*, contrary to ANSI.
  cat > conftest.$ac_ext <<EOF
! #line 919 "configure"
  #include "confdefs.h"
  #include <string.h>
  EOF
--- 951,957 ----
  if test $ac_cv_header_stdc = yes; then
    # SunOS 4.x string.h does not declare mem*, contrary to ANSI.
  cat > conftest.$ac_ext <<EOF
! #line 955 "configure"
  #include "confdefs.h"
  #include <string.h>
  EOF
*************** fi
*** 933,939 ****
  if test $ac_cv_header_stdc = yes; then
    # ISC 2.0.2 stdlib.h does not declare free, contrary to ANSI.
  cat > conftest.$ac_ext <<EOF
! #line 937 "configure"
  #include "confdefs.h"
  #include <stdlib.h>
  EOF
--- 969,975 ----
  if test $ac_cv_header_stdc = yes; then
    # ISC 2.0.2 stdlib.h does not declare free, contrary to ANSI.
  cat > conftest.$ac_ext <<EOF
! #line 973 "configure"
  #include "confdefs.h"
  #include <stdlib.h>
  EOF
*************** if test "$cross_compiling" = yes; then
*** 954,960 ****
    :
  else
    cat > conftest.$ac_ext <<EOF
! #line 958 "configure"
  #include "confdefs.h"
  #include <ctype.h>
  #define ISLOWER(c) ('a' <= (c) && (c) <= 'z')
--- 990,996 ----
    :
  else
    cat > conftest.$ac_ext <<EOF
! #line 994 "configure"
  #include "confdefs.h"
  #include <ctype.h>
  #define ISLOWER(c) ('a' <= (c) && (c) <= 'z')
*************** if (XOR (islower (i), ISLOWER (i)) || to
*** 965,971 ****
  exit (0); }
  
  EOF
! if { (eval echo configure:969: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest${ac_exeext} && (./conftest; exit) 2>/dev/null
  then
    :
  else
--- 1001,1007 ----
  exit (0); }
  
  EOF
! if { (eval echo configure:1005: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest${ac_exeext} && (./conftest; exit) 2>/dev/null
  then
    :
  else
*************** EOF
*** 988,1001 ****
  
  fi
  
- 
  echo $ac_n "checking for posix""... $ac_c" 1>&6
! echo "configure:994: checking for posix" >&5
  if eval "test \"`echo '$''{'g77_cv_header_posix'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 999 "configure"
  #include "confdefs.h"
  #include <sys/types.h>
  #include <unistd.h>
--- 1024,1036 ----
  
  fi
  
  echo $ac_n "checking for posix""... $ac_c" 1>&6
! echo "configure:1029: checking for posix" >&5
  if eval "test \"`echo '$''{'g77_cv_header_posix'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 1034 "configure"
  #include "confdefs.h"
  #include <sys/types.h>
  #include <unistd.h>
*************** echo "$ac_t""$g77_cv_header_posix" 1>&6
*** 1021,1032 ****
  # We can rely on the GNU library being posix-ish.  I guess checking the 
  # header isn't actually like checking the functions, though...
  echo $ac_n "checking for GNU library""... $ac_c" 1>&6
! echo "configure:1025: checking for GNU library" >&5
  if eval "test \"`echo '$''{'g77_cv_lib_gnu'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 1030 "configure"
  #include "confdefs.h"
  #include <stdio.h>
  #ifdef __GNU_LIBRARY__
--- 1056,1067 ----
  # We can rely on the GNU library being posix-ish.  I guess checking the 
  # header isn't actually like checking the functions, though...
  echo $ac_n "checking for GNU library""... $ac_c" 1>&6
! echo "configure:1060: checking for GNU library" >&5
  if eval "test \"`echo '$''{'g77_cv_lib_gnu'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 1065 "configure"
  #include "confdefs.h"
  #include <stdio.h>
  #ifdef __GNU_LIBRARY__
*************** echo "$ac_t""$g77_cv_lib_gnu" 1>&6
*** 1050,1061 ****
  
  # Apparently cygwin needs to be special-cased.
  echo $ac_n "checking for cyg\`win'32""... $ac_c" 1>&6
! echo "configure:1054: checking for cyg\`win'32" >&5
  if eval "test \"`echo '$''{'g77_cv_sys_cygwin32'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 1059 "configure"
  #include "confdefs.h"
  #ifdef __CYGWIN32__
    yes
--- 1085,1096 ----
  
  # Apparently cygwin needs to be special-cased.
  echo $ac_n "checking for cyg\`win'32""... $ac_c" 1>&6
! echo "configure:1089: checking for cyg\`win'32" >&5
  if eval "test \"`echo '$''{'g77_cv_sys_cygwin32'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 1094 "configure"
  #include "confdefs.h"
  #ifdef __CYGWIN32__
    yes
*************** echo "$ac_t""$g77_cv_sys_cygwin32" 1>&6
*** 1078,1089 ****
  
  # ditto for mingw32.
  echo $ac_n "checking for mingw32""... $ac_c" 1>&6
! echo "configure:1082: checking for mingw32" >&5
  if eval "test \"`echo '$''{'g77_cv_sys_mingw32'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 1087 "configure"
  #include "confdefs.h"
  #ifdef __MINGW32__
    yes
--- 1113,1124 ----
  
  # ditto for mingw32.
  echo $ac_n "checking for mingw32""... $ac_c" 1>&6
! echo "configure:1117: checking for mingw32" >&5
  if eval "test \"`echo '$''{'g77_cv_sys_mingw32'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 1122 "configure"
  #include "confdefs.h"
  #ifdef __MINGW32__
    yes
*************** echo "$ac_t""$g77_cv_sys_mingw32" 1>&6
*** 1106,1117 ****
  
  
  echo $ac_n "checking for working const""... $ac_c" 1>&6
! echo "configure:1110: checking for working const" >&5
  if eval "test \"`echo '$''{'ac_cv_c_const'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 1115 "configure"
  #include "confdefs.h"
  
  int main() {
--- 1141,1152 ----
  
  
  echo $ac_n "checking for working const""... $ac_c" 1>&6
! echo "configure:1145: checking for working const" >&5
  if eval "test \"`echo '$''{'ac_cv_c_const'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 1150 "configure"
  #include "confdefs.h"
  
  int main() {
*************** ccp = (char const *const *) p;
*** 1160,1166 ****
  
  ; return 0; }
  EOF
! if { (eval echo configure:1164: \"$ac_compile\") 1>&5; (eval $ac_compile) 2>&5; }; then
    rm -rf conftest*
    ac_cv_c_const=yes
  else
--- 1195,1201 ----
  
  ; return 0; }
  EOF
! if { (eval echo configure:1199: \"$ac_compile\") 1>&5; (eval $ac_compile) 2>&5; }; then
    rm -rf conftest*
    ac_cv_c_const=yes
  else
*************** EOF
*** 1181,1192 ****
  fi
  
  echo $ac_n "checking for size_t""... $ac_c" 1>&6
! echo "configure:1185: checking for size_t" >&5
  if eval "test \"`echo '$''{'ac_cv_type_size_t'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 1190 "configure"
  #include "confdefs.h"
  #include <sys/types.h>
  #if STDC_HEADERS
--- 1216,1227 ----
  fi
  
  echo $ac_n "checking for size_t""... $ac_c" 1>&6
! echo "configure:1220: checking for size_t" >&5
  if eval "test \"`echo '$''{'ac_cv_type_size_t'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 1225 "configure"
  #include "confdefs.h"
  #include <sys/types.h>
  #if STDC_HEADERS
*************** fi
*** 1219,1230 ****
  # Apparently positive result on cygwin loses re. NON_UNIX_STDIO
  # (as of cygwin b18). Likewise on mingw.
  echo $ac_n "checking for fstat""... $ac_c" 1>&6
! echo "configure:1223: checking for fstat" >&5
  if eval "test \"`echo '$''{'ac_cv_func_fstat'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 1228 "configure"
  #include "confdefs.h"
  /* System header to define __stub macros and hopefully few prototypes,
      which can conflict with char fstat(); below.  */
--- 1254,1265 ----
  # Apparently positive result on cygwin loses re. NON_UNIX_STDIO
  # (as of cygwin b18). Likewise on mingw.
  echo $ac_n "checking for fstat""... $ac_c" 1>&6
! echo "configure:1258: checking for fstat" >&5
  if eval "test \"`echo '$''{'ac_cv_func_fstat'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 1263 "configure"
  #include "confdefs.h"
  /* System header to define __stub macros and hopefully few prototypes,
      which can conflict with char fstat(); below.  */
*************** fstat();
*** 1247,1253 ****
  
  ; return 0; }
  EOF
! if { (eval echo configure:1251: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest${ac_exeext}; then
    rm -rf conftest*
    eval "ac_cv_func_fstat=yes"
  else
--- 1282,1288 ----
  
  ; return 0; }
  EOF
! if { (eval echo configure:1286: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest${ac_exeext}; then
    rm -rf conftest*
    eval "ac_cv_func_fstat=yes"
  else
*************** else
*** 1267,1273 ****
  fi
  
  echo $ac_n "checking need for NON_UNIX_STDIO""... $ac_c" 1>&6
! echo "configure:1271: checking need for NON_UNIX_STDIO" >&5
  if test $g77_cv_sys_cygwin32 = yes \
    || test $g77_cv_sys_mingw32 = yes \
    || test $ac_cv_func_fstat = no; then
--- 1302,1308 ----
  fi
  
  echo $ac_n "checking need for NON_UNIX_STDIO""... $ac_c" 1>&6
! echo "configure:1306: checking need for NON_UNIX_STDIO" >&5
  if test $g77_cv_sys_cygwin32 = yes \
    || test $g77_cv_sys_mingw32 = yes \
    || test $ac_cv_func_fstat = no; then
*************** fi
*** 1283,1294 ****
  for ac_func in fseeko
  do
  echo $ac_n "checking for $ac_func""... $ac_c" 1>&6
! echo "configure:1287: checking for $ac_func" >&5
  if eval "test \"`echo '$''{'ac_cv_func_$ac_func'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 1292 "configure"
  #include "confdefs.h"
  /* System header to define __stub macros and hopefully few prototypes,
      which can conflict with char $ac_func(); below.  */
--- 1318,1329 ----
  for ac_func in fseeko
  do
  echo $ac_n "checking for $ac_func""... $ac_c" 1>&6
! echo "configure:1322: checking for $ac_func" >&5
  if eval "test \"`echo '$''{'ac_cv_func_$ac_func'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 1327 "configure"
  #include "confdefs.h"
  /* System header to define __stub macros and hopefully few prototypes,
      which can conflict with char $ac_func(); below.  */
*************** $ac_func();
*** 1311,1317 ****
  
  ; return 0; }
  EOF
! if { (eval echo configure:1315: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest${ac_exeext}; then
    rm -rf conftest*
    eval "ac_cv_func_$ac_func=yes"
  else
--- 1346,1352 ----
  
  ; return 0; }
  EOF
! if { (eval echo configure:1350: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest${ac_exeext}; then
    rm -rf conftest*
    eval "ac_cv_func_$ac_func=yes"
  else
*************** done
*** 1338,1349 ****
  for ac_func in ftello
  do
  echo $ac_n "checking for $ac_func""... $ac_c" 1>&6
! echo "configure:1342: checking for $ac_func" >&5
  if eval "test \"`echo '$''{'ac_cv_func_$ac_func'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 1347 "configure"
  #include "confdefs.h"
  /* System header to define __stub macros and hopefully few prototypes,
      which can conflict with char $ac_func(); below.  */
--- 1373,1384 ----
  for ac_func in ftello
  do
  echo $ac_n "checking for $ac_func""... $ac_c" 1>&6
! echo "configure:1377: checking for $ac_func" >&5
  if eval "test \"`echo '$''{'ac_cv_func_$ac_func'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 1382 "configure"
  #include "confdefs.h"
  /* System header to define __stub macros and hopefully few prototypes,
      which can conflict with char $ac_func(); below.  */
*************** $ac_func();
*** 1366,1372 ****
  
  ; return 0; }
  EOF
! if { (eval echo configure:1370: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest${ac_exeext}; then
    rm -rf conftest*
    eval "ac_cv_func_$ac_func=yes"
  else
--- 1401,1407 ----
  
  ; return 0; }
  EOF
! if { (eval echo configure:1405: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest${ac_exeext}; then
    rm -rf conftest*
    eval "ac_cv_func_$ac_func=yes"
  else
*************** done
*** 1393,1404 ****
  for ac_func in ftruncate
  do
  echo $ac_n "checking for $ac_func""... $ac_c" 1>&6
! echo "configure:1397: checking for $ac_func" >&5
  if eval "test \"`echo '$''{'ac_cv_func_$ac_func'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 1402 "configure"
  #include "confdefs.h"
  /* System header to define __stub macros and hopefully few prototypes,
      which can conflict with char $ac_func(); below.  */
--- 1428,1439 ----
  for ac_func in ftruncate
  do
  echo $ac_n "checking for $ac_func""... $ac_c" 1>&6
! echo "configure:1432: checking for $ac_func" >&5
  if eval "test \"`echo '$''{'ac_cv_func_$ac_func'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 1437 "configure"
  #include "confdefs.h"
  /* System header to define __stub macros and hopefully few prototypes,
      which can conflict with char $ac_func(); below.  */
*************** $ac_func();
*** 1421,1427 ****
  
  ; return 0; }
  EOF
! if { (eval echo configure:1425: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest${ac_exeext}; then
    rm -rf conftest*
    eval "ac_cv_func_$ac_func=yes"
  else
--- 1456,1462 ----
  
  ; return 0; }
  EOF
! if { (eval echo configure:1460: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest${ac_exeext}; then
    rm -rf conftest*
    eval "ac_cv_func_$ac_func=yes"
  else
*************** done
*** 1448,1459 ****
  for ac_func in mkstemp
  do
  echo $ac_n "checking for $ac_func""... $ac_c" 1>&6
! echo "configure:1452: checking for $ac_func" >&5
  if eval "test \"`echo '$''{'ac_cv_func_$ac_func'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 1457 "configure"
  #include "confdefs.h"
  /* System header to define __stub macros and hopefully few prototypes,
      which can conflict with char $ac_func(); below.  */
--- 1483,1494 ----
  for ac_func in mkstemp
  do
  echo $ac_n "checking for $ac_func""... $ac_c" 1>&6
! echo "configure:1487: checking for $ac_func" >&5
  if eval "test \"`echo '$''{'ac_cv_func_$ac_func'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 1492 "configure"
  #include "confdefs.h"
  /* System header to define __stub macros and hopefully few prototypes,
      which can conflict with char $ac_func(); below.  */
*************** $ac_func();
*** 1476,1482 ****
  
  ; return 0; }
  EOF
! if { (eval echo configure:1480: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest${ac_exeext}; then
    rm -rf conftest*
    eval "ac_cv_func_$ac_func=yes"
  else
--- 1511,1517 ----
  
  ; return 0; }
  EOF
! if { (eval echo configure:1515: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest${ac_exeext}; then
    rm -rf conftest*
    eval "ac_cv_func_$ac_func=yes"
  else
*************** done
*** 1503,1514 ****
  for ac_func in tempnam
  do
  echo $ac_n "checking for $ac_func""... $ac_c" 1>&6
! echo "configure:1507: checking for $ac_func" >&5
  if eval "test \"`echo '$''{'ac_cv_func_$ac_func'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 1512 "configure"
  #include "confdefs.h"
  /* System header to define __stub macros and hopefully few prototypes,
      which can conflict with char $ac_func(); below.  */
--- 1538,1549 ----
  for ac_func in tempnam
  do
  echo $ac_n "checking for $ac_func""... $ac_c" 1>&6
! echo "configure:1542: checking for $ac_func" >&5
  if eval "test \"`echo '$''{'ac_cv_func_$ac_func'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 1547 "configure"
  #include "confdefs.h"
  /* System header to define __stub macros and hopefully few prototypes,
      which can conflict with char $ac_func(); below.  */
*************** $ac_func();
*** 1531,1537 ****
  
  ; return 0; }
  EOF
! if { (eval echo configure:1535: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest${ac_exeext}; then
    rm -rf conftest*
    eval "ac_cv_func_$ac_func=yes"
  else
--- 1566,1572 ----
  
  ; return 0; }
  EOF
! if { (eval echo configure:1570: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest${ac_exeext}; then
    rm -rf conftest*
    eval "ac_cv_func_$ac_func=yes"
  else
*************** done
*** 1558,1569 ****
  for ac_func in tmpnam
  do
  echo $ac_n "checking for $ac_func""... $ac_c" 1>&6
! echo "configure:1562: checking for $ac_func" >&5
  if eval "test \"`echo '$''{'ac_cv_func_$ac_func'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 1567 "configure"
  #include "confdefs.h"
  /* System header to define __stub macros and hopefully few prototypes,
      which can conflict with char $ac_func(); below.  */
--- 1593,1604 ----
  for ac_func in tmpnam
  do
  echo $ac_n "checking for $ac_func""... $ac_c" 1>&6
! echo "configure:1597: checking for $ac_func" >&5
  if eval "test \"`echo '$''{'ac_cv_func_$ac_func'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 1602 "configure"
  #include "confdefs.h"
  /* System header to define __stub macros and hopefully few prototypes,
      which can conflict with char $ac_func(); below.  */
*************** $ac_func();
*** 1586,1592 ****
  
  ; return 0; }
  EOF
! if { (eval echo configure:1590: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest${ac_exeext}; then
    rm -rf conftest*
    eval "ac_cv_func_$ac_func=yes"
  else
--- 1621,1627 ----
  
  ; return 0; }
  EOF
! if { (eval echo configure:1625: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest${ac_exeext}; then
    rm -rf conftest*
    eval "ac_cv_func_$ac_func=yes"
  else
*************** done
*** 1616,1634 ****
  # However, on my sunos4/gcc setup unistd.h leads us wrongly to believe
  # we're posix-conformant, so always do the test.
  echo $ac_n "checking for ansi/posix sprintf result""... $ac_c" 1>&6
! echo "configure:1620: checking for ansi/posix sprintf result" >&5
  if test "$cross_compiling" = yes; then
    g77_cv_sys_sprintf_ansi=no
  else
    cat > conftest.$ac_ext <<EOF
! #line 1625 "configure"
  #include "confdefs.h"
    #include <stdio.h>
      /* does sprintf return the number of chars transferred? */
      main () {char foo[2]; (sprintf(foo, "1") == 1) ? exit(0) : exit(1);}
  
  EOF
! if { (eval echo configure:1632: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest${ac_exeext} && (./conftest; exit) 2>/dev/null
  then
    g77_cv_sys_sprintf_ansi=yes
  else
--- 1651,1669 ----
  # However, on my sunos4/gcc setup unistd.h leads us wrongly to believe
  # we're posix-conformant, so always do the test.
  echo $ac_n "checking for ansi/posix sprintf result""... $ac_c" 1>&6
! echo "configure:1655: checking for ansi/posix sprintf result" >&5
  if test "$cross_compiling" = yes; then
    g77_cv_sys_sprintf_ansi=no
  else
    cat > conftest.$ac_ext <<EOF
! #line 1660 "configure"
  #include "confdefs.h"
    #include <stdio.h>
      /* does sprintf return the number of chars transferred? */
      main () {char foo[2]; (sprintf(foo, "1") == 1) ? exit(0) : exit(1);}
  
  EOF
! if { (eval echo configure:1667: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest${ac_exeext} && (./conftest; exit) 2>/dev/null
  then
    g77_cv_sys_sprintf_ansi=yes
  else
*************** fi
*** 1659,1667 ****
  
  # define NON_ANSI_RW_MODES on unix (can't hurt)
  echo $ac_n "checking NON_ANSI_RW_MODES""... $ac_c" 1>&6
! echo "configure:1663: checking NON_ANSI_RW_MODES" >&5
  cat > conftest.$ac_ext <<EOF
! #line 1665 "configure"
  #include "confdefs.h"
  #ifdef unix
    yes
--- 1694,1702 ----
  
  # define NON_ANSI_RW_MODES on unix (can't hurt)
  echo $ac_n "checking NON_ANSI_RW_MODES""... $ac_c" 1>&6
! echo "configure:1698: checking NON_ANSI_RW_MODES" >&5
  cat > conftest.$ac_ext <<EOF
! #line 1700 "configure"
  #include "confdefs.h"
  #ifdef unix
    yes
*************** EOF
*** 1706,1717 ****
  
  
  echo $ac_n "checking for off_t""... $ac_c" 1>&6
! echo "configure:1710: checking for off_t" >&5
  if eval "test \"`echo '$''{'ac_cv_type_off_t'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 1715 "configure"
  #include "confdefs.h"
  #include <sys/types.h>
  #if STDC_HEADERS
--- 1741,1752 ----
  
  
  echo $ac_n "checking for off_t""... $ac_c" 1>&6
! echo "configure:1745: checking for off_t" >&5
  if eval "test \"`echo '$''{'ac_cv_type_off_t'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 1750 "configure"
  #include "confdefs.h"
  #include <sys/types.h>
  #if STDC_HEADERS
diff -Nrc3pad gcc-3.2.3/libf2c/libI77/configure.in gcc-3.3/libf2c/libI77/configure.in
*** gcc-3.2.3/libf2c/libI77/configure.in	2002-01-15 17:27:05.000000000 +0000
--- gcc-3.3/libf2c/libI77/configure.in	2003-04-24 01:58:04.000000000 +0000
*************** AC_PREREQ(2.12.1)
*** 23,40 ****
  AC_INIT(ftell_.c)
  AC_CONFIG_HEADER(config.h)
  
- # These defines are necessary to get 64-bit file size support.
- 
- AC_DEFINE(_XOPEN_SOURCE, 500L, [Get Single Unix Specification semantics])
- # The following is needed by irix6.2 so that struct timeval is declared.
- AC_DEFINE(_XOPEN_SOURCE_EXTENDED, 1, [Get Single Unix Specification semantics])
- # The following is needed by Solaris2.5.1 so that struct timeval is declared.
- AC_DEFINE(__EXTENSIONS__, 1, [Solaris extensions])
- AC_DEFINE(_FILE_OFFSET_BITS, 64, [Get 64-bit file size support])
- AC_DEFINE(_LARGEFILE_SOURCE, 1, [Define for HP-UX ftello and fseeko extension.])
- 
- dnl Checks for programs.
- 
  dnl FIXME AC_PROG_CC wants CC to be able to link things, but it may
  dnl not be able to.
  define([AC_PROG_CC_WORKS],[])
--- 23,28 ----
*************** define([AC_PROG_CC_WORKS],[])
*** 43,48 ****
--- 31,57 ----
  # the makefiles
  AC_PROG_CC
  
+ # These defines are necessary to get 64-bit file size support.
+ # NetBSD 1.4 header files does not support XOPEN_SOURCE == 600, but it
+ # handles 64-bit file sizes without needing these defines.
+ AC_MSG_CHECKING(whether _XOPEN_SOURCE may be defined)
+ AC_TRY_COMPILE([#define _XOPEN_SOURCE 600L
+ #include <unistd.h>],,
+ may_use_xopen_source=yes,
+ may_use_xopen_source=no)
+ AC_MSG_RESULT($may_use_xopen_source)
+ if test $may_use_xopen_source = yes; then
+   AC_DEFINE(_XOPEN_SOURCE, 600L, [Get Single Unix Specification semantics])
+   # The following is needed by irix6.2 so that struct timeval is declared.
+   AC_DEFINE(_XOPEN_SOURCE_EXTENDED, 1, [Get Single Unix Specification semantics])
+   # The following is needed by Solaris2.5.1 so that struct timeval is declared.
+   AC_DEFINE(__EXTENSIONS__, 1, [Solaris extensions])
+   AC_DEFINE(_FILE_OFFSET_BITS, 64, [Get 64-bit file size support])
+   AC_DEFINE(_LARGEFILE_SOURCE, 1, [Define for HP-UX ftello and fseeko extension.])
+ fi
+ 
+ dnl Checks for programs.
+ 
  LIBTOOL='$(SHELL) ../libtool'
  AC_SUBST(LIBTOOL)
  
*************** the G77 runtime system.  If necessary, i
*** 62,78 ****
  then the target library, then build with \`LANGUAGES=f77'.])])
  
  AC_HEADER_STDC
- dnl We could do this if we didn't know we were using gcc
- dnl AC_MSG_CHECKING(for prototype-savvy compiler)
- dnl AC_CACHE_VAL(g77_cv_sys_proto,                
- dnl   [AC_TRY_LINK(,                             
- dnl dnl looks screwy because TRY_LINK expects a function body
- dnl    [return 0;} int foo (int * bar) {],       
- dnl    g77_cv_sys_proto=yes,                      
- dnl    [g77_cv_sys_proto=no                       
- dnl     AC_DEFINE(KR_headers)])])                
- dnl AC_MSG_RESULT($g77_cv_sys_proto)              
- 
  AC_MSG_CHECKING(for posix)
  AC_CACHE_VAL(g77_cv_header_posix,
    AC_EGREP_CPP(yes,
--- 71,76 ----
diff -Nrc3pad gcc-3.2.3/libf2c/libI77/dfe.c gcc-3.3/libf2c/libI77/dfe.c
*** gcc-3.2.3/libf2c/libI77/dfe.c	2001-07-10 20:39:40.000000000 +0000
--- gcc-3.3/libf2c/libI77/dfe.c	2002-06-02 14:34:31.000000000 +0000
***************
*** 3,147 ****
  #include "fio.h"
  #include "fmt.h"
  
! y_rsk(Void)
  {
! 	if(f__curunit->uend || f__curunit->url <= f__recpos
! 		|| f__curunit->url == 1) return 0;
! 	do {
! 		getc(f__cf);
! 	} while(++f__recpos < f__curunit->url);
! 	return 0;
  }
! y_getc(Void)
  {
! 	int ch;
! 	if(f__curunit->uend) return(-1);
! 	if((ch=getc(f__cf))!=EOF)
! 	{
! 		f__recpos++;
! 		if(f__curunit->url>=f__recpos ||
! 			f__curunit->url==1)
! 			return(ch);
! 		else	return(' ');
! 	}
! 	if(feof(f__cf))
! 	{
! 		f__curunit->uend=1;
! 		errno=0;
! 		return(-1);
! 	}
! 	err(f__elist->cierr,errno,"readingd");
  }
  
!  static int
! y_rev(Void)
  {
! 	if (f__recpos < f__hiwater)
! 		f__recpos = f__hiwater;
! 	if (f__curunit->url > 1)
! 		while(f__recpos < f__curunit->url)
! 			(*f__putn)(' ');
! 	if (f__recpos)
! 		f__putbuf(0);
! 	f__recpos = 0;
! 	return(0);
  }
  
!  static int
! y_err(Void)
  {
! 	err(f__elist->cierr, 110, "dfe");
  }
  
!  static int
! y_newrec(Void)
  {
! 	y_rev();
! 	f__hiwater = f__cursor = 0;
! 	return(1);
  }
  
! #ifdef KR_headers
! c_dfe(a) cilist *a;
! #else
! c_dfe(cilist *a)
! #endif
  {
! 	f__sequential=0;
! 	f__formatted=f__external=1;
! 	f__elist=a;
! 	f__cursor=f__scale=f__recpos=0;
! 	f__curunit = &f__units[a->ciunit];
! 	if(a->ciunit>MXUNIT || a->ciunit<0)
! 		err(a->cierr,101,"startchk");
! 	if(f__curunit->ufd==NULL && fk_open(DIR,FMT,a->ciunit))
! 		err(a->cierr,104,"dfe");
! 	f__cf=f__curunit->ufd;
! 	if(!f__curunit->ufmt) err(a->cierr,102,"dfe");
! 	if(!f__curunit->useek) err(a->cierr,104,"dfe");
! 	f__fmtbuf=a->cifmt;
! 	if(a->cirec <= 0)
! 		err(a->cierr,130,"dfe");
! 	FSEEK(f__cf,(off_t)f__curunit->url * (a->cirec-1),SEEK_SET);
! 	f__curunit->uend = 0;
! 	return(0);
  }
! #ifdef KR_headers
! integer s_rdfe(a) cilist *a;
! #else
! integer s_rdfe(cilist *a)
! #endif
  {
! 	int n;
! 	if(f__init != 1) f_init();
! 	f__init = 3;
! 	f__reading=1;
! 	if(n=c_dfe(a))return(n);
! 	if(f__curunit->uwrt && f__nowreading(f__curunit))
! 		err(a->cierr,errno,"read start");
! 	f__getn = y_getc;
! 	f__doed = rd_ed;
! 	f__doned = rd_ned;
! 	f__dorevert = f__donewrec = y_err;
! 	f__doend = y_rsk;
! 	if(pars_f(f__fmtbuf)<0)
! 		err(a->cierr,100,"read start");
! 	fmt_bg();
! 	return(0);
  }
! #ifdef KR_headers
! integer s_wdfe(a) cilist *a;
! #else
! integer s_wdfe(cilist *a)
! #endif
  {
! 	int n;
! 	if(f__init != 1) f_init();
! 	f__init = 3;
! 	f__reading=0;
! 	if(n=c_dfe(a)) return(n);
! 	if(f__curunit->uwrt != 1 && f__nowwriting(f__curunit))
! 		err(a->cierr,errno,"startwrt");
! 	f__putn = x_putc;
! 	f__doed = w_ed;
! 	f__doned= w_ned;
! 	f__dorevert = y_err;
! 	f__donewrec = y_newrec;
! 	f__doend = y_rev;
! 	if(pars_f(f__fmtbuf)<0)
! 		err(a->cierr,100,"startwrt");
! 	fmt_bg();
! 	return(0);
  }
! integer e_rdfe(Void)
  {
! 	f__init = 1;
! 	en_fio();
! 	return(0);
  }
  
! integer e_wdfe(Void)
  {
! 	f__init = 1;
! 	return en_fio();
  }
--- 3,156 ----
  #include "fio.h"
  #include "fmt.h"
  
! int
! y_rsk (void)
  {
!   if (f__curunit->uend || f__curunit->url <= f__recpos
!       || f__curunit->url == 1)
!     return 0;
!   do
!     {
!       getc (f__cf);
!     }
!   while (++f__recpos < f__curunit->url);
!   return 0;
  }
! 
! int
! y_getc (void)
  {
!   int ch;
!   if (f__curunit->uend)
!     return (-1);
!   if ((ch = getc (f__cf)) != EOF)
!     {
!       f__recpos++;
!       if (f__curunit->url >= f__recpos || f__curunit->url == 1)
! 	return (ch);
!       else
! 	return (' ');
!     }
!   if (feof (f__cf))
!     {
!       f__curunit->uend = 1;
!       errno = 0;
!       return (-1);
!     }
!   err (f__elist->cierr, errno, "readingd");
  }
  
! static int
! y_rev (void)
  {
!   if (f__recpos < f__hiwater)
!     f__recpos = f__hiwater;
!   if (f__curunit->url > 1)
!     while (f__recpos < f__curunit->url)
!       (*f__putn) (' ');
!   if (f__recpos)
!     f__putbuf (0);
!   f__recpos = 0;
!   return (0);
  }
  
! static int
! y_err (void)
  {
!   err (f__elist->cierr, 110, "dfe");
  }
  
! static int
! y_newrec (void)
  {
!   y_rev ();
!   f__hiwater = f__cursor = 0;
!   return (1);
  }
  
! int
! c_dfe (cilist * a)
  {
!   f__sequential = 0;
!   f__formatted = f__external = 1;
!   f__elist = a;
!   f__cursor = f__scale = f__recpos = 0;
!   f__curunit = &f__units[a->ciunit];
!   if (a->ciunit > MXUNIT || a->ciunit < 0)
!     err (a->cierr, 101, "startchk");
!   if (f__curunit->ufd == NULL && fk_open (DIR, FMT, a->ciunit))
!     err (a->cierr, 104, "dfe");
!   f__cf = f__curunit->ufd;
!   if (!f__curunit->ufmt)
!     err (a->cierr, 102, "dfe");
!   if (!f__curunit->useek)
!     err (a->cierr, 104, "dfe");
!   f__fmtbuf = a->cifmt;
!   if (a->cirec <= 0)
!     err (a->cierr, 130, "dfe");
!   FSEEK (f__cf, (off_t) f__curunit->url * (a->cirec - 1), SEEK_SET);
!   f__curunit->uend = 0;
!   return (0);
  }
! 
! integer
! s_rdfe (cilist * a)
  {
!   int n;
!   if (f__init != 1)
!     f_init ();
!   f__init = 3;
!   f__reading = 1;
!   if ((n = c_dfe (a)))
!     return (n);
!   if (f__curunit->uwrt && f__nowreading (f__curunit))
!     err (a->cierr, errno, "read start");
!   f__getn = y_getc;
!   f__doed = rd_ed;
!   f__doned = rd_ned;
!   f__dorevert = f__donewrec = y_err;
!   f__doend = y_rsk;
!   if (pars_f (f__fmtbuf) < 0)
!     err (a->cierr, 100, "read start");
!   fmt_bg ();
!   return (0);
  }
! 
! integer
! s_wdfe (cilist * a)
  {
!   int n;
!   if (f__init != 1)
!     f_init ();
!   f__init = 3;
!   f__reading = 0;
!   if ((n = c_dfe (a)))
!     return (n);
!   if (f__curunit->uwrt != 1 && f__nowwriting (f__curunit))
!     err (a->cierr, errno, "startwrt");
!   f__putn = x_putc;
!   f__doed = w_ed;
!   f__doned = w_ned;
!   f__dorevert = y_err;
!   f__donewrec = y_newrec;
!   f__doend = y_rev;
!   if (pars_f (f__fmtbuf) < 0)
!     err (a->cierr, 100, "startwrt");
!   fmt_bg ();
!   return (0);
  }
! 
! integer
! e_rdfe (void)
  {
!   f__init = 1;
!   en_fio ();
!   return (0);
  }
  
! integer
! e_wdfe (void)
  {
!   f__init = 1;
!   return en_fio ();
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libI77/dolio.c gcc-3.3/libf2c/libI77/dolio.c
*** gcc-3.2.3/libf2c/libI77/dolio.c	2001-05-16 18:59:29.000000000 +0000
--- gcc-3.3/libf2c/libI77/dolio.c	2002-06-01 12:38:29.000000000 +0000
***************
*** 1,21 ****
  #include "config.h"
  #include "f2c.h"
  
! #ifdef __cplusplus
! extern "C" {
! #endif
! #ifdef KR_headers
! extern int (*f__lioproc)();
! 
! integer do_lio(type,number,ptr,len) ftnint *number,*type; char *ptr; ftnlen len;
! #else
! extern int (*f__lioproc)(ftnint*, char*, ftnlen, ftnint);
  
! integer do_lio(ftnint *type, ftnint *number, char *ptr, ftnlen len)
! #endif
  {
! 	return((*f__lioproc)(number,ptr,len,*type));
  }
- #ifdef __cplusplus
- 	}
- #endif
--- 1,10 ----
  #include "config.h"
  #include "f2c.h"
  
! extern int (*f__lioproc) (ftnint *, char *, ftnlen, ftnint);
  
! integer
! do_lio (ftnint * type, ftnint * number, char *ptr, ftnlen len)
  {
!   return ((*f__lioproc) (number, ptr, len, *type));
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libI77/due.c gcc-3.3/libf2c/libI77/due.c
*** gcc-3.2.3/libf2c/libI77/due.c	2001-07-10 20:39:40.000000000 +0000
--- gcc-3.3/libf2c/libI77/due.c	2002-06-02 14:34:31.000000000 +0000
***************
*** 2,76 ****
  #include "f2c.h"
  #include "fio.h"
  
! #ifdef KR_headers
! c_due(a) cilist *a;
! #else
! c_due(cilist *a)
! #endif
  {
! 	if(f__init != 1) f_init();
! 	f__init = 3;
! 	if(a->ciunit>=MXUNIT || a->ciunit<0)
! 		err(a->cierr,101,"startio");
! 	f__sequential=f__formatted=f__recpos=0;
! 	f__external=1;
! 	f__curunit = &f__units[a->ciunit];
! 	if(a->ciunit>=MXUNIT || a->ciunit<0)
! 		err(a->cierr,101,"startio");
! 	f__elist=a;
! 	if(f__curunit->ufd==NULL && fk_open(DIR,UNF,a->ciunit) ) err(a->cierr,104,"due");
! 	f__cf=f__curunit->ufd;
! 	if(f__curunit->ufmt) err(a->cierr,102,"cdue");
! 	if(!f__curunit->useek) err(a->cierr,104,"cdue");
! 	if(f__curunit->ufd==NULL) err(a->cierr,114,"cdue");
! 	if(a->cirec <= 0)
! 		err(a->cierr,130,"due");
! 	FSEEK(f__cf,(off_t)(a->cirec-1)*f__curunit->url,SEEK_SET);
! 	f__curunit->uend = 0;
! 	return(0);
  }
! #ifdef KR_headers
! integer s_rdue(a) cilist *a;
! #else
! integer s_rdue(cilist *a)
! #endif
  {
! 	int n;
! 	f__reading=1;
! 	if(n=c_due(a)) return(n);
! 	if(f__curunit->uwrt && f__nowreading(f__curunit))
! 		err(a->cierr,errno,"read start");
! 	return(0);
  }
! #ifdef KR_headers
! integer s_wdue(a) cilist *a;
! #else
! integer s_wdue(cilist *a)
! #endif
  {
! 	int n;
! 	f__reading=0;
! 	if(n=c_due(a)) return(n);
! 	if(f__curunit->uwrt != 1 && f__nowwriting(f__curunit))
! 		err(a->cierr,errno,"write start");
! 	return(0);
  }
! integer e_rdue(Void)
  {
! 	f__init = 1;
! 	if(f__curunit->url==1 || f__recpos==f__curunit->url)
! 		return(0);
! 	FSEEK(f__cf,(off_t)(f__curunit->url-f__recpos),SEEK_CUR);
! 	if(FTELL(f__cf)%f__curunit->url)
! 		err(f__elist->cierr,200,"syserr");
! 	return(0);
  }
! integer e_wdue(Void)
  {
! 	f__init = 1;
  #ifdef ALWAYS_FLUSH
! 	if (fflush(f__cf))
! 		err(f__elist->cierr,errno,"write end");
  #endif
! 	return(e_rdue());
  }
--- 2,80 ----
  #include "f2c.h"
  #include "fio.h"
  
! int
! c_due (cilist * a)
  {
!   if (f__init != 1)
!     f_init ();
!   f__init = 3;
!   if (a->ciunit >= MXUNIT || a->ciunit < 0)
!     err (a->cierr, 101, "startio");
!   f__sequential = f__formatted = f__recpos = 0;
!   f__external = 1;
!   f__curunit = &f__units[a->ciunit];
!   if (a->ciunit >= MXUNIT || a->ciunit < 0)
!     err (a->cierr, 101, "startio");
!   f__elist = a;
!   if (f__curunit->ufd == NULL && fk_open (DIR, UNF, a->ciunit))
!     err (a->cierr, 104, "due");
!   f__cf = f__curunit->ufd;
!   if (f__curunit->ufmt)
!     err (a->cierr, 102, "cdue");
!   if (!f__curunit->useek)
!     err (a->cierr, 104, "cdue");
!   if (f__curunit->ufd == NULL)
!     err (a->cierr, 114, "cdue");
!   if (a->cirec <= 0)
!     err (a->cierr, 130, "due");
!   FSEEK (f__cf, (off_t) (a->cirec - 1) * f__curunit->url, SEEK_SET);
!   f__curunit->uend = 0;
!   return (0);
  }
! 
! integer
! s_rdue (cilist * a)
  {
!   int n;
!   f__reading = 1;
!   if ((n = c_due (a)))
!     return (n);
!   if (f__curunit->uwrt && f__nowreading (f__curunit))
!     err (a->cierr, errno, "read start");
!   return (0);
  }
! 
! integer
! s_wdue (cilist * a)
  {
!   int n;
!   f__reading = 0;
!   if ((n = c_due (a)))
!     return (n);
!   if (f__curunit->uwrt != 1 && f__nowwriting (f__curunit))
!     err (a->cierr, errno, "write start");
!   return (0);
  }
! 
! integer
! e_rdue (void)
  {
!   f__init = 1;
!   if (f__curunit->url == 1 || f__recpos == f__curunit->url)
!     return (0);
!   FSEEK (f__cf, (off_t) (f__curunit->url - f__recpos), SEEK_CUR);
!   if (FTELL (f__cf) % f__curunit->url)
!     err (f__elist->cierr, 200, "syserr");
!   return (0);
  }
! 
! integer
! e_wdue (void)
  {
!   f__init = 1;
  #ifdef ALWAYS_FLUSH
!   if (fflush (f__cf))
!     err (f__elist->cierr, errno, "write end");
  #endif
!   return (e_rdue ());
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libI77/endfile.c gcc-3.3/libf2c/libI77/endfile.c
*** gcc-3.2.3/libf2c/libI77/endfile.c	2001-12-02 14:00:56.000000000 +0000
--- gcc-3.3/libf2c/libI77/endfile.c	2002-06-02 14:34:31.000000000 +0000
***************
*** 5,140 ****
  #include <sys/types.h>
  #include <unistd.h>
  
- #ifdef KR_headers
- extern char *strcpy();
- extern FILE *tmpfile();
- #else
  #undef abs
  #undef min
  #undef max
  #include <stdlib.h>
  #include <string.h>
- #endif
  
  extern char *f__r_mode[], *f__w_mode[];
  
! #ifdef KR_headers
! integer f_end(a) alist *a;
! #else
! integer f_end(alist *a)
! #endif
  {
! 	unit *b;
! 	FILE *tf;
  
! 	if (f__init & 2)
! 		f__fatal (131, "I/O recursion");
! 	if(a->aunit>=MXUNIT || a->aunit<0) err(a->aerr,101,"endfile");
! 	b = &f__units[a->aunit];
! 	if(b->ufd==NULL) {
! 		char nbuf[10];
! 		sprintf(nbuf,"fort.%ld",(long)a->aunit);
! 		if (tf = fopen(nbuf, f__w_mode[0]))
! 			fclose(tf);
! 		return(0);
! 		}
! 	b->uend=1;
! 	return(b->useek ? t_runc(a) : 0);
  }
  
  #ifndef HAVE_FTRUNCATE
!  static int
! #ifdef KR_headers
! copy(from, len, to) FILE *from, *to; register long len;
! #else
! copy(FILE *from, register long len, FILE *to)
! #endif
  {
! 	int len1;
! 	char buf[BUFSIZ];
  
! 	while(fread(buf, len1 = len > BUFSIZ ? BUFSIZ : (int)len, 1, from)) {
! 		if (!fwrite(buf, len1, 1, to))
! 			return 1;
! 		if ((len -= len1) <= 0)
! 			break;
! 		}
! 	return 0;
! 	}
  #endif /* !defined(HAVE_FTRUNCATE) */
  
!  int
! #ifdef KR_headers
! t_runc(a) alist *a;
! #else
! t_runc(alist *a)
! #endif
  {
! 	off_t loc, len;
! 	unit *b;
! 	int rc;
! 	FILE *bf;
  #ifndef HAVE_FTRUNCATE
! 	FILE *tf;
  #endif /* !defined(HAVE_FTRUNCATE) */
  
! 	b = &f__units[a->aunit];
! 	if(b->url)
! 		return(0);	/*don't truncate direct files*/
! 	loc=FTELL(bf = b->ufd);
! 	FSEEK(bf,0,SEEK_END);
! 	len=FTELL(bf);
! 	if (loc >= len || b->useek == 0 || b->ufnm == NULL)
! 		return(0);
  #ifndef HAVE_FTRUNCATE
! 	rc = 0;
! 	fclose(b->ufd);
! 	if (!loc) {
! 		if (!(bf = fopen(b->ufnm, f__w_mode[b->ufmt])))
! 			rc = 1;
! 		if (b->uwrt)
! 			b->uwrt = 1;
! 		goto done;
! 		}
! 	if (!(bf = fopen(b->ufnm, f__r_mode[0]))
! 	 || !(tf = tmpfile())) {
  #ifdef NON_UNIX_STDIO
!  bad:
  #endif
! 		rc = 1;
! 		goto done;
! 		}
! 	if (copy(bf, loc, tf)) {
!  bad1:
! 		rc = 1;
! 		goto done1;
! 		}
! 	if (!(bf = freopen(b->ufnm, f__w_mode[0], bf)))
! 		goto bad1;
! 	FSEEK(tf, 0, SEEK_SET);
! 	if (copy(tf, loc, bf))
! 		goto bad1;
! 	b->uwrt = 1;
! 	b->urw = 2;
  #ifdef NON_UNIX_STDIO
! 	if (b->ufmt) {
! 		fclose(bf);
! 		if (!(bf = fopen(b->ufnm, f__w_mode[3])))
! 			goto bad;
! 		FSEEK(bf,0,SEEK_END);
! 		b->urw = 3;
! 		}
  #endif
  done1:
! 	fclose(tf);
  done:
! 	f__cf = b->ufd = bf;
! #else  /* !defined(HAVE_FTRUNCATE) */
! 	fflush(b->ufd);
! 	rc = ftruncate(fileno(b->ufd), loc);
!         FSEEK(bf,loc,SEEK_SET);
  #endif /* !defined(HAVE_FTRUNCATE) */
! 	if (rc)
! 		err(a->aerr,111,"endfile");
! 	return 0;
! 	}
--- 5,130 ----
  #include <sys/types.h>
  #include <unistd.h>
  
  #undef abs
  #undef min
  #undef max
  #include <stdlib.h>
  #include <string.h>
  
  extern char *f__r_mode[], *f__w_mode[];
  
! integer
! f_end (alist * a)
  {
!   unit *b;
!   FILE *tf;
  
!   if (f__init & 2)
!     f__fatal (131, "I/O recursion");
!   if (a->aunit >= MXUNIT || a->aunit < 0)
!     err (a->aerr, 101, "endfile");
!   b = &f__units[a->aunit];
!   if (b->ufd == NULL)
!     {
!       char nbuf[10];
!       sprintf (nbuf, "fort.%ld", (long) a->aunit);
!       if ((tf = fopen (nbuf, f__w_mode[0])))
! 	fclose (tf);
!       return (0);
!     }
!   b->uend = 1;
!   return (b->useek ? t_runc (a) : 0);
  }
  
  #ifndef HAVE_FTRUNCATE
! static int
! copy (FILE * from, register long len, FILE * to)
  {
!   int len1;
!   char buf[BUFSIZ];
  
!   while (fread (buf, len1 = len > BUFSIZ ? BUFSIZ : (int) len, 1, from))
!     {
!       if (!fwrite (buf, len1, 1, to))
! 	return 1;
!       if ((len -= len1) <= 0)
! 	break;
!     }
!   return 0;
! }
  #endif /* !defined(HAVE_FTRUNCATE) */
  
! int
! t_runc (alist * a)
  {
!   off_t loc, len;
!   unit *b;
!   int rc;
!   FILE *bf;
  #ifndef HAVE_FTRUNCATE
!   FILE *tf;
  #endif /* !defined(HAVE_FTRUNCATE) */
  
!   b = &f__units[a->aunit];
!   if (b->url)
!     return (0);			/*don't truncate direct files */
!   loc = FTELL (bf = b->ufd);
!   FSEEK (bf, 0, SEEK_END);
!   len = FTELL (bf);
!   if (loc >= len || b->useek == 0 || b->ufnm == NULL)
!     return (0);
  #ifndef HAVE_FTRUNCATE
!   rc = 0;
!   fclose (b->ufd);
!   if (!loc)
!     {
!       if (!(bf = fopen (b->ufnm, f__w_mode[b->ufmt])))
! 	rc = 1;
!       if (b->uwrt)
! 	b->uwrt = 1;
!       goto done;
!     }
!   if (!(bf = fopen (b->ufnm, f__r_mode[0])) || !(tf = tmpfile ()))
!     {
  #ifdef NON_UNIX_STDIO
!     bad:
  #endif
!       rc = 1;
!       goto done;
!     }
!   if (copy (bf, loc, tf))
!     {
!     bad1:
!       rc = 1;
!       goto done1;
!     }
!   if (!(bf = freopen (b->ufnm, f__w_mode[0], bf)))
!     goto bad1;
!   FSEEK (tf, 0, SEEK_SET);
!   if (copy (tf, loc, bf))
!     goto bad1;
!   b->uwrt = 1;
!   b->urw = 2;
  #ifdef NON_UNIX_STDIO
!   if (b->ufmt)
!     {
!       fclose (bf);
!       if (!(bf = fopen (b->ufnm, f__w_mode[3])))
! 	goto bad;
!       FSEEK (bf, 0, SEEK_END);
!       b->urw = 3;
!     }
  #endif
  done1:
!   fclose (tf);
  done:
!   f__cf = b->ufd = bf;
! #else /* !defined(HAVE_FTRUNCATE) */
!   fflush (b->ufd);
!   rc = ftruncate (fileno (b->ufd), loc);
!   FSEEK (bf, loc, SEEK_SET);
  #endif /* !defined(HAVE_FTRUNCATE) */
!   if (rc)
!     err (a->aerr, 111, "endfile");
!   return 0;
! }
diff -Nrc3pad gcc-3.2.3/libf2c/libI77/err.c gcc-3.3/libf2c/libI77/err.c
*** gcc-3.2.3/libf2c/libI77/err.c	2001-07-07 18:51:58.000000000 +0000
--- gcc-3.3/libf2c/libI77/err.c	2002-06-02 13:01:11.000000000 +0000
***************
*** 6,290 ****
  #include <sys/stat.h>
  #endif
  #include "f2c.h"
- #ifdef KR_headers
- extern char *malloc();
- #else
  #undef abs
  #undef min
  #undef max
  #include <stdlib.h>
- #endif
  #include "fio.h"
! #include "fmt.h"	/* for struct syl */
  
  /*global definitions*/
! unit f__units[MXUNIT];	/*unit table*/
! int f__init;	/*bit 0: set after initializations;
! 		  bit 1: set during I/O involving returns to
! 		    caller of library (or calls to user code)*/
! cilist *f__elist;	/*active external io list*/
! icilist *f__svic;	/*active internal io list*/
! flag f__reading;	/*1 if reading, 0 if writing*/
! flag f__cplus,f__cblank;
  char *f__fmtbuf;
  int f__fmtlen;
! flag f__external;	/*1 if external io, 0 if internal */
! #ifdef KR_headers
! int (*f__doed)(),(*f__doned)();
! int (*f__doend)(),(*f__donewrec)(),(*f__dorevert)();
! int (*f__getn)();	/* for formatted input */
! void (*f__putn)();	/* for formatted output */
! #else
! int (*f__getn)(void);	/* for formatted input */
! void (*f__putn)(int);	/* for formatted output */
! int (*f__doed)(struct syl*, char*, ftnlen),(*f__doned)(struct syl*);
! int (*f__dorevert)(void),(*f__donewrec)(void),(*f__doend)(void);
! #endif
! flag f__sequential;	/*1 if sequential io, 0 if direct*/
! flag f__formatted;	/*1 if formatted io, 0 if unformatted*/
! FILE *f__cf;	/*current file*/
! unit *f__curunit;	/*current unit*/
! int f__recpos;	/*place in current record*/
  int f__cursor, f__hiwater, f__scale;
  char *f__icptr;
  
  /*error messages*/
! char *F_err[] =
! {
! 	"error in format",				/* 100 */
! 	"illegal unit number",				/* 101 */
! 	"formatted io not allowed",			/* 102 */
! 	"unformatted io not allowed",			/* 103 */
! 	"direct io not allowed",			/* 104 */
! 	"sequential io not allowed",			/* 105 */
! 	"can't backspace file",				/* 106 */
! 	"null file name",				/* 107 */
! 	"can't stat file",				/* 108 */
! 	"unit not connected",				/* 109 */
! 	"off end of record",				/* 110 */
! 	"truncation failed in endfile",			/* 111 */
! 	"incomprehensible list input",			/* 112 */
! 	"out of free space",				/* 113 */
! 	"unit not connected",				/* 114 */
! 	"read unexpected character",			/* 115 */
! 	"bad logical input field",			/* 116 */
! 	"bad variable type",				/* 117 */
! 	"bad namelist name",				/* 118 */
! 	"variable not in namelist",			/* 119 */
! 	"no end record",				/* 120 */
! 	"variable count incorrect",			/* 121 */
! 	"subscript for scalar variable",		/* 122 */
! 	"invalid array section",			/* 123 */
! 	"substring out of bounds",			/* 124 */
! 	"subscript out of bounds",			/* 125 */
! 	"can't read file",				/* 126 */
! 	"can't write file",				/* 127 */
! 	"'new' file exists",				/* 128 */
! 	"can't append to file",				/* 129 */
! 	"non-positive record number",			/* 130 */
! 	"I/O started while already doing I/O",		/* 131 */
! 	"Temporary file name (TMPDIR?) too long"        /* 132 */
  };
  #define MAXERR (sizeof(F_err)/sizeof(char *)+100)
  
! #ifdef KR_headers
! f__canseek(f) FILE *f; /*SYSDEP*/
! #else
! f__canseek(FILE *f) /*SYSDEP*/
! #endif
  {
  #ifdef NON_UNIX_STDIO
! 	return !isatty(fileno(f));
  #else
! 	struct stat x;
  
! 	if (fstat(fileno(f),&x) < 0)
! 		return(0);
  #ifdef S_IFMT
! 	switch(x.st_mode & S_IFMT) {
! 	case S_IFDIR:
! 	case S_IFREG:
! 		if(x.st_nlink > 0)	/* !pipe */
! 			return(1);
! 		else
! 			return(0);
! 	case S_IFCHR:
! 		if(isatty(fileno(f)))
! 			return(0);
! 		return(1);
  #ifdef S_IFBLK
! 	case S_IFBLK:
! 		return(1);
  #endif
! 	}
  #else
  #ifdef S_ISDIR
! 	/* POSIX version */
! 	if (S_ISREG(x.st_mode) || S_ISDIR(x.st_mode)) {
! 		if(x.st_nlink > 0)	/* !pipe */
! 			return(1);
! 		else
! 			return(0);
! 		}
! 	if (S_ISCHR(x.st_mode)) {
! 		if(isatty(fileno(f)))
! 			return(0);
! 		return(1);
! 		}
! 	if (S_ISBLK(x.st_mode))
! 		return(1);
  #else
! 	Help! How does fstat work on this system?
  #endif
  #endif
! 	return(0);	/* who knows what it is? */
  #endif
  }
  
!  void
! #ifdef KR_headers
! f__fatal(n,s) char *s;
! #else
! f__fatal(int n, char *s)
! #endif
  {
! 	static int dead = 0;
  
! 	if(n<100 && n>=0) perror(s); /*SYSDEP*/
! 	else if(n >= (int)MAXERR || n < -1)
! 	{	fprintf(stderr,"%s: illegal error number %d\n",s,n);
! 	}
! 	else if(n == -1) fprintf(stderr,"%s: end of file\n",s);
! 	else
! 		fprintf(stderr,"%s: %s\n",s,F_err[n-100]);
! 	if (dead) {
! 		fprintf (stderr, "(libf2c f__fatal already called, aborting.)");
! 		abort();
! 	}
! 	dead = 1;
! 	if (f__init & 1) {
! 		if (f__curunit) {
! 			fprintf(stderr,"apparent state: unit %d ",
! 				(int)(f__curunit-f__units));
! 			fprintf(stderr, f__curunit->ufnm ? "named %s\n" : "(unnamed)\n",
! 				f__curunit->ufnm);
! 			}
! 		else
! 			fprintf(stderr,"apparent state: internal I/O\n");
! 		if (f__fmtbuf)
! 			fprintf(stderr,"last format: %.*s\n",f__fmtlen,f__fmtbuf);
! 		fprintf(stderr,"lately %s %s %s %s",f__reading?"reading":"writing",
! 			f__sequential?"sequential":"direct",f__formatted?"formatted":"unformatted",
! 			f__external?"external":"internal");
  	}
! 	f__init &= ~2;	/* No longer doing I/O (no more user code to be called). */
! 	sig_die(" IO", 1);
  }
  /*initialization routine*/
!  VOID
! f_init(Void)
! {	unit *p;
  
! 	if (f__init & 2)
! 		f__fatal (131, "I/O recursion");
! 	f__init = 1;
! 	p= &f__units[0];
! 	p->ufd=stderr;
! 	p->useek=f__canseek(stderr);
! 	p->ufmt=1;
! 	p->uwrt=1;
! 	p = &f__units[5];
! 	p->ufd=stdin;
! 	p->useek=f__canseek(stdin);
! 	p->ufmt=1;
! 	p->uwrt=0;
! 	p= &f__units[6];
! 	p->ufd=stdout;
! 	p->useek=f__canseek(stdout);
! 	p->ufmt=1;
! 	p->uwrt=1;
  }
! #ifdef KR_headers
! f__nowreading(x) unit *x;
! #else
! f__nowreading(unit *x)
! #endif
  {
! 	off_t loc;
! 	int ufmt, urw;
! 	extern char *f__r_mode[], *f__w_mode[];
  
! 	if (x->urw & 1)
! 		goto done;
! 	if (!x->ufnm)
! 		goto cantread;
! 	ufmt = x->url ? 0 : x->ufmt;
! 	loc = FTELL(x->ufd);
! 	urw = 3;
! 	if (!freopen(x->ufnm, f__w_mode[ufmt|2], x->ufd)) {
! 		urw = 1;
! 		if(!freopen(x->ufnm, f__r_mode[ufmt], x->ufd)) {
!  cantread:
! 			errno = 126;
! 			return 1;
! 			}
! 		}
! 	FSEEK(x->ufd,loc,SEEK_SET);
! 	x->urw = urw;
!  done:
! 	x->uwrt = 0;
! 	return 0;
  }
! #ifdef KR_headers
! f__nowwriting(x) unit *x;
! #else
! f__nowwriting(unit *x)
! #endif
  {
! 	off_t loc;
! 	int ufmt;
! 	extern char *f__w_mode[];
  
! 	if (x->urw & 2)
! 		goto done;
! 	if (!x->ufnm)
! 		goto cantwrite;
! 	ufmt = x->url ? 0 : x->ufmt;
! 	if (x->uwrt == 3) { /* just did write, rewind */
! 		if (!(f__cf = x->ufd =
! 				freopen(x->ufnm,f__w_mode[ufmt],x->ufd)))
! 			goto cantwrite;
! 		x->urw = 2;
! 		}
! 	else {
! 		loc=FTELL(x->ufd);
! 		if (!(f__cf = x->ufd =
! 			freopen(x->ufnm, f__w_mode[ufmt |= 2], x->ufd)))
! 			{
! 			x->ufd = NULL;
!  cantwrite:
! 			errno = 127;
! 			return(1);
! 			}
! 		x->urw = 3;
! 		FSEEK(x->ufd,loc,SEEK_SET);
! 		}
!  done:
! 	x->uwrt = 1;
! 	return 0;
  }
  
!  int
! #ifdef KR_headers
! err__fl(f, m, s) int f, m; char *s;
! #else
! err__fl(int f, int m, char *s)
! #endif
  {
! 	if (!f)
! 		f__fatal(m, s);
! 	if (f__doend)
! 		(*f__doend)();
! 	f__init &= ~2;
! 	return errno = m;
! 	}
--- 6,279 ----
  #include <sys/stat.h>
  #endif
  #include "f2c.h"
  #undef abs
  #undef min
  #undef max
  #include <stdlib.h>
  #include "fio.h"
! #include "fmt.h"		/* for struct syl */
  
  /*global definitions*/
! unit f__units[MXUNIT];		/*unit table */
! int f__init;			/*bit 0: set after initializations;
! 				   bit 1: set during I/O involving returns to
! 				   caller of library (or calls to user code) */
! cilist *f__elist;		/*active external io list */
! icilist *f__svic;		/*active internal io list */
! flag f__reading;		/*1 if reading, 0 if writing */
! flag f__cplus, f__cblank;
  char *f__fmtbuf;
  int f__fmtlen;
! flag f__external;		/*1 if external io, 0 if internal */
! int (*f__getn) (void);		/* for formatted input */
! void (*f__putn) (int);		/* for formatted output */
! int (*f__doed) (struct syl *, char *, ftnlen), (*f__doned) (struct syl *);
! int (*f__dorevert) (void), (*f__donewrec) (void), (*f__doend) (void);
! flag f__sequential;		/*1 if sequential io, 0 if direct */
! flag f__formatted;		/*1 if formatted io, 0 if unformatted */
! FILE *f__cf;			/*current file */
! unit *f__curunit;		/*current unit */
! int f__recpos;			/*place in current record */
  int f__cursor, f__hiwater, f__scale;
  char *f__icptr;
  
  /*error messages*/
! char *F_err[] = {
!   "error in format",		/* 100 */
!   "illegal unit number",	/* 101 */
!   "formatted io not allowed",	/* 102 */
!   "unformatted io not allowed",	/* 103 */
!   "direct io not allowed",	/* 104 */
!   "sequential io not allowed",	/* 105 */
!   "can't backspace file",	/* 106 */
!   "null file name",		/* 107 */
!   "can't stat file",		/* 108 */
!   "unit not connected",		/* 109 */
!   "off end of record",		/* 110 */
!   "truncation failed in endfile",	/* 111 */
!   "incomprehensible list input",	/* 112 */
!   "out of free space",		/* 113 */
!   "unit not connected",		/* 114 */
!   "read unexpected character",	/* 115 */
!   "bad logical input field",	/* 116 */
!   "bad variable type",		/* 117 */
!   "bad namelist name",		/* 118 */
!   "variable not in namelist",	/* 119 */
!   "no end record",		/* 120 */
!   "variable count incorrect",	/* 121 */
!   "subscript for scalar variable",	/* 122 */
!   "invalid array section",	/* 123 */
!   "substring out of bounds",	/* 124 */
!   "subscript out of bounds",	/* 125 */
!   "can't read file",		/* 126 */
!   "can't write file",		/* 127 */
!   "'new' file exists",		/* 128 */
!   "can't append to file",	/* 129 */
!   "non-positive record number",	/* 130 */
!   "I/O started while already doing I/O",	/* 131 */
!   "Temporary file name (TMPDIR?) too long"	/* 132 */
  };
  #define MAXERR (sizeof(F_err)/sizeof(char *)+100)
  
! int
! f__canseek (FILE * f) /*SYSDEP*/
  {
  #ifdef NON_UNIX_STDIO
!   return !isatty (fileno (f));
  #else
!   struct stat x;
  
!   if (fstat (fileno (f), &x) < 0)
!     return (0);
  #ifdef S_IFMT
!   switch (x.st_mode & S_IFMT)
!     {
!     case S_IFDIR:
!     case S_IFREG:
!       if (x.st_nlink > 0)	/* !pipe */
! 	return (1);
!       else
! 	return (0);
!     case S_IFCHR:
!       if (isatty (fileno (f)))
! 	return (0);
!       return (1);
  #ifdef S_IFBLK
!     case S_IFBLK:
!       return (1);
  #endif
!     }
  #else
  #ifdef S_ISDIR
!   /* POSIX version */
!   if (S_ISREG (x.st_mode) || S_ISDIR (x.st_mode))
!     {
!       if (x.st_nlink > 0)	/* !pipe */
! 	return (1);
!       else
! 	return (0);
!     }
!   if (S_ISCHR (x.st_mode))
!     {
!       if (isatty (fileno (f)))
! 	return (0);
!       return (1);
!     }
!   if (S_ISBLK (x.st_mode))
!     return (1);
  #else
!   Help ! How does fstat work on this system ?
  #endif
  #endif
!     return (0);			/* who knows what it is? */
  #endif
  }
  
! void
! f__fatal (int n, char *s)
  {
!   static int dead = 0;
  
!   if (n < 100 && n >= 0)
!     perror (s);
!   /*SYSDEP*/
!   else if (n >= (int) MAXERR || n < -1)
!     {
!       fprintf (stderr, "%s: illegal error number %d\n", s, n);
!     }
!   else if (n == -1)
!     fprintf (stderr, "%s: end of file\n", s);
!   else
!     fprintf (stderr, "%s: %s\n", s, F_err[n - 100]);
!   if (dead)
!     {
!       fprintf (stderr, "(libf2c f__fatal already called, aborting.)");
!       abort ();
!     }
!   dead = 1;
!   if (f__init & 1)
!     {
!       if (f__curunit)
! 	{
! 	  fprintf (stderr, "apparent state: unit %d ",
! 		   (int) (f__curunit - f__units));
! 	  fprintf (stderr, f__curunit->ufnm ? "named %s\n" : "(unnamed)\n",
! 		   f__curunit->ufnm);
  	}
!       else
! 	fprintf (stderr, "apparent state: internal I/O\n");
!       if (f__fmtbuf)
! 	fprintf (stderr, "last format: %.*s\n", f__fmtlen, f__fmtbuf);
!       fprintf (stderr, "lately %s %s %s %s",
! 	       f__reading ? "reading" : "writing",
! 	       f__sequential ? "sequential" : "direct",
! 	       f__formatted ? "formatted" : "unformatted",
! 	       f__external ? "external" : "internal");
!     }
!   f__init &= ~2;		/* No longer doing I/O (no more user code to be called). */
!   sig_die (" IO", 1);
  }
+ 
  /*initialization routine*/
! void
! f_init (void)
! {
!   unit *p;
  
!   if (f__init & 2)
!     f__fatal (131, "I/O recursion");
!   f__init = 1;
!   p = &f__units[0];
!   p->ufd = stderr;
!   p->useek = f__canseek (stderr);
!   p->ufmt = 1;
!   p->uwrt = 1;
!   p = &f__units[5];
!   p->ufd = stdin;
!   p->useek = f__canseek (stdin);
!   p->ufmt = 1;
!   p->uwrt = 0;
!   p = &f__units[6];
!   p->ufd = stdout;
!   p->useek = f__canseek (stdout);
!   p->ufmt = 1;
!   p->uwrt = 1;
  }
! 
! int
! f__nowreading (unit * x)
  {
!   off_t loc;
!   int ufmt, urw;
!   extern char *f__r_mode[], *f__w_mode[];
  
!   if (x->urw & 1)
!     goto done;
!   if (!x->ufnm)
!     goto cantread;
!   ufmt = x->url ? 0 : x->ufmt;
!   loc = FTELL (x->ufd);
!   urw = 3;
!   if (!freopen (x->ufnm, f__w_mode[ufmt | 2], x->ufd))
!     {
!       urw = 1;
!       if (!freopen (x->ufnm, f__r_mode[ufmt], x->ufd))
! 	{
! 	cantread:
! 	  errno = 126;
! 	  return 1;
! 	}
!     }
!   FSEEK (x->ufd, loc, SEEK_SET);
!   x->urw = urw;
! done:
!   x->uwrt = 0;
!   return 0;
  }
! 
! int
! f__nowwriting (unit * x)
  {
!   off_t loc;
!   int ufmt;
!   extern char *f__w_mode[];
  
!   if (x->urw & 2)
!     goto done;
!   if (!x->ufnm)
!     goto cantwrite;
!   ufmt = x->url ? 0 : x->ufmt;
!   if (x->uwrt == 3)
!     {				/* just did write, rewind */
!       if (!(f__cf = x->ufd = freopen (x->ufnm, f__w_mode[ufmt], x->ufd)))
! 	goto cantwrite;
!       x->urw = 2;
!     }
!   else
!     {
!       loc = FTELL (x->ufd);
!       if (!(f__cf = x->ufd = freopen (x->ufnm, f__w_mode[ufmt |= 2], x->ufd)))
! 	{
! 	  x->ufd = NULL;
! 	cantwrite:
! 	  errno = 127;
! 	  return (1);
! 	}
!       x->urw = 3;
!       FSEEK (x->ufd, loc, SEEK_SET);
!     }
! done:
!   x->uwrt = 1;
!   return 0;
  }
  
! int
! err__fl (int f, int m, char *s)
  {
!   if (!f)
!     f__fatal (m, s);
!   if (f__doend)
!     (*f__doend) ();
!   f__init &= ~2;
!   return errno = m;
! }
diff -Nrc3pad gcc-3.2.3/libf2c/libI77/f2ch.add gcc-3.3/libf2c/libI77/f2ch.add
*** gcc-3.2.3/libf2c/libI77/f2ch.add	1999-09-04 15:09:17.000000000 +0000
--- gcc-3.3/libf2c/libI77/f2ch.add	2002-06-01 12:38:29.000000000 +0000
***************
*** 2,162 ****
     for compiling libF77 and libI77. */
  
  #ifdef __cplusplus
! extern "C" {
! extern int abort_(void);
! extern double c_abs(complex *);
! extern void c_cos(complex *, complex *);
! extern void c_div(complex *, complex *, complex *);
! extern void c_exp(complex *, complex *);
! extern void c_log(complex *, complex *);
! extern void c_sin(complex *, complex *);
! extern void c_sqrt(complex *, complex *);
! extern double d_abs(double *);
! extern double d_acos(double *);
! extern double d_asin(double *);
! extern double d_atan(double *);
! extern double d_atn2(double *, double *);
! extern void d_cnjg(doublecomplex *, doublecomplex *);
! extern double d_cos(double *);
! extern double d_cosh(double *);
! extern double d_dim(double *, double *);
! extern double d_exp(double *);
! extern double d_imag(doublecomplex *);
! extern double d_int(double *);
! extern double d_lg10(double *);
! extern double d_log(double *);
! extern double d_mod(double *, double *);
! extern double d_nint(double *);
! extern double d_prod(float *, float *);
! extern double d_sign(double *, double *);
! extern double d_sin(double *);
! extern double d_sinh(double *);
! extern double d_sqrt(double *);
! extern double d_tan(double *);
! extern double d_tanh(double *);
! extern double derf_(double *);
! extern double derfc_(double *);
! extern integer do_fio(ftnint *, char *, ftnlen);
! extern integer do_lio(ftnint *, ftnint *, char *, ftnlen);
! extern integer do_uio(ftnint *, char *, ftnlen);
! extern integer e_rdfe(void);
! extern integer e_rdue(void);
! extern integer e_rsfe(void);
! extern integer e_rsfi(void);
! extern integer e_rsle(void);
! extern integer e_rsli(void);
! extern integer e_rsue(void);
! extern integer e_wdfe(void);
! extern integer e_wdue(void);
! extern integer e_wsfe(void);
! extern integer e_wsfi(void);
! extern integer e_wsle(void);
! extern integer e_wsli(void);
! extern integer e_wsue(void);
! extern int ef1asc_(ftnint *, ftnlen *, ftnint *, ftnlen *);
! extern integer ef1cmc_(ftnint *, ftnlen *, ftnint *, ftnlen *);
! extern double erf(double);
! extern double erf_(float *);
! extern double erfc(double);
! extern double erfc_(float *);
! extern integer f_back(alist *);
! extern integer f_clos(cllist *);
! extern integer f_end(alist *);
! extern void f_exit(void);
! extern integer f_inqu(inlist *);
! extern integer f_open(olist *);
! extern integer f_rew(alist *);
! extern int flush_(void);
! extern void getarg_(integer *, char *, ftnlen);
! extern void getenv_(char *, char *, ftnlen, ftnlen);
! extern short h_abs(short *);
! extern short h_dim(short *, short *);
! extern short h_dnnt(double *);
! extern short h_indx(char *, char *, ftnlen, ftnlen);
! extern short h_len(char *, ftnlen);
! extern short h_mod(short *, short *);
! extern short h_nint(float *);
! extern short h_sign(short *, short *);
! extern short hl_ge(char *, char *, ftnlen, ftnlen);
! extern short hl_gt(char *, char *, ftnlen, ftnlen);
! extern short hl_le(char *, char *, ftnlen, ftnlen);
! extern short hl_lt(char *, char *, ftnlen, ftnlen);
! extern integer i_abs(integer *);
! extern integer i_dim(integer *, integer *);
! extern integer i_dnnt(double *);
! extern integer i_indx(char *, char *, ftnlen, ftnlen);
! extern integer i_len(char *, ftnlen);
! extern integer i_mod(integer *, integer *);
! extern integer i_nint(float *);
! extern integer i_sign(integer *, integer *);
! extern integer iargc_(void);
! extern ftnlen l_ge(char *, char *, ftnlen, ftnlen);
! extern ftnlen l_gt(char *, char *, ftnlen, ftnlen);
! extern ftnlen l_le(char *, char *, ftnlen, ftnlen);
! extern ftnlen l_lt(char *, char *, ftnlen, ftnlen);
! extern void pow_ci(complex *, complex *, integer *);
! extern double pow_dd(double *, double *);
! extern double pow_di(double *, integer *);
! extern short pow_hh(short *, shortint *);
! extern integer pow_ii(integer *, integer *);
! extern double pow_ri(float *, integer *);
! extern void pow_zi(doublecomplex *, doublecomplex *, integer *);
! extern void pow_zz(doublecomplex *, doublecomplex *, doublecomplex *);
! extern double r_abs(float *);
! extern double r_acos(float *);
! extern double r_asin(float *);
! extern double r_atan(float *);
! extern double r_atn2(float *, float *);
! extern void r_cnjg(complex *, complex *);
! extern double r_cos(float *);
! extern double r_cosh(float *);
! extern double r_dim(float *, float *);
! extern double r_exp(float *);
! extern double r_imag(complex *);
! extern double r_int(float *);
! extern double r_lg10(float *);
! extern double r_log(float *);
! extern double r_mod(float *, float *);
! extern double r_nint(float *);
! extern double r_sign(float *, float *);
! extern double r_sin(float *);
! extern double r_sinh(float *);
! extern double r_sqrt(float *);
! extern double r_tan(float *);
! extern double r_tanh(float *);
! extern void s_cat(char *, char **, integer *, integer *, ftnlen);
! extern integer s_cmp(char *, char *, ftnlen, ftnlen);
! extern void s_copy(char *, char *, ftnlen, ftnlen);
! extern int s_paus(char *, ftnlen);
! extern integer s_rdfe(cilist *);
! extern integer s_rdue(cilist *);
! extern integer s_rnge(char *, integer, char *, integer);
! extern integer s_rsfe(cilist *);
! extern integer s_rsfi(icilist *);
! extern integer s_rsle(cilist *);
! extern integer s_rsli(icilist *);
! extern integer s_rsne(cilist *);
! extern integer s_rsni(icilist *);
! extern integer s_rsue(cilist *);
! extern int s_stop(char *, ftnlen);
! extern integer s_wdfe(cilist *);
! extern integer s_wdue(cilist *);
! extern integer s_wsfe(cilist *);
! extern integer s_wsfi(icilist *);
! extern integer s_wsle(cilist *);
! extern integer s_wsli(icilist *);
! extern integer s_wsne(cilist *);
! extern integer s_wsni(icilist *);
! extern integer s_wsue(cilist *);
! extern void sig_die(char *, int);
! extern integer signal_(integer *, void (*)(int));
! extern integer system_(char *, ftnlen);
! extern double z_abs(doublecomplex *);
! extern void z_cos(doublecomplex *, doublecomplex *);
! extern void z_div(doublecomplex *, doublecomplex *, doublecomplex *);
! extern void z_exp(doublecomplex *, doublecomplex *);
! extern void z_log(doublecomplex *, doublecomplex *);
! extern void z_sin(doublecomplex *, doublecomplex *);
! extern void z_sqrt(doublecomplex *, doublecomplex *);
! 	}
  #endif
--- 2,163 ----
     for compiling libF77 and libI77. */
  
  #ifdef __cplusplus
! extern "C"
! {
!   extern int abort_ (void);
!   extern double c_abs (complex *);
!   extern void c_cos (complex *, complex *);
!   extern void c_div (complex *, complex *, complex *);
!   extern void c_exp (complex *, complex *);
!   extern void c_log (complex *, complex *);
!   extern void c_sin (complex *, complex *);
!   extern void c_sqrt (complex *, complex *);
!   extern double d_abs (double *);
!   extern double d_acos (double *);
!   extern double d_asin (double *);
!   extern double d_atan (double *);
!   extern double d_atn2 (double *, double *);
!   extern void d_cnjg (doublecomplex *, doublecomplex *);
!   extern double d_cos (double *);
!   extern double d_cosh (double *);
!   extern double d_dim (double *, double *);
!   extern double d_exp (double *);
!   extern double d_imag (doublecomplex *);
!   extern double d_int (double *);
!   extern double d_lg10 (double *);
!   extern double d_log (double *);
!   extern double d_mod (double *, double *);
!   extern double d_nint (double *);
!   extern double d_prod (float *, float *);
!   extern double d_sign (double *, double *);
!   extern double d_sin (double *);
!   extern double d_sinh (double *);
!   extern double d_sqrt (double *);
!   extern double d_tan (double *);
!   extern double d_tanh (double *);
!   extern double derf_ (double *);
!   extern double derfc_ (double *);
!   extern integer do_fio (ftnint *, char *, ftnlen);
!   extern integer do_lio (ftnint *, ftnint *, char *, ftnlen);
!   extern integer do_uio (ftnint *, char *, ftnlen);
!   extern integer e_rdfe (void);
!   extern integer e_rdue (void);
!   extern integer e_rsfe (void);
!   extern integer e_rsfi (void);
!   extern integer e_rsle (void);
!   extern integer e_rsli (void);
!   extern integer e_rsue (void);
!   extern integer e_wdfe (void);
!   extern integer e_wdue (void);
!   extern integer e_wsfe (void);
!   extern integer e_wsfi (void);
!   extern integer e_wsle (void);
!   extern integer e_wsli (void);
!   extern integer e_wsue (void);
!   extern int ef1asc_ (ftnint *, ftnlen *, ftnint *, ftnlen *);
!   extern integer ef1cmc_ (ftnint *, ftnlen *, ftnint *, ftnlen *);
!   extern double erf (double);
!   extern double erf_ (float *);
!   extern double erfc (double);
!   extern double erfc_ (float *);
!   extern integer f_back (alist *);
!   extern integer f_clos (cllist *);
!   extern integer f_end (alist *);
!   extern void f_exit (void);
!   extern integer f_inqu (inlist *);
!   extern integer f_open (olist *);
!   extern integer f_rew (alist *);
!   extern int flush_ (void);
!   extern void getarg_ (integer *, char *, ftnlen);
!   extern void getenv_ (char *, char *, ftnlen, ftnlen);
!   extern short h_abs (short *);
!   extern short h_dim (short *, short *);
!   extern short h_dnnt (double *);
!   extern short h_indx (char *, char *, ftnlen, ftnlen);
!   extern short h_len (char *, ftnlen);
!   extern short h_mod (short *, short *);
!   extern short h_nint (float *);
!   extern short h_sign (short *, short *);
!   extern short hl_ge (char *, char *, ftnlen, ftnlen);
!   extern short hl_gt (char *, char *, ftnlen, ftnlen);
!   extern short hl_le (char *, char *, ftnlen, ftnlen);
!   extern short hl_lt (char *, char *, ftnlen, ftnlen);
!   extern integer i_abs (integer *);
!   extern integer i_dim (integer *, integer *);
!   extern integer i_dnnt (double *);
!   extern integer i_indx (char *, char *, ftnlen, ftnlen);
!   extern integer i_len (char *, ftnlen);
!   extern integer i_mod (integer *, integer *);
!   extern integer i_nint (float *);
!   extern integer i_sign (integer *, integer *);
!   extern integer iargc_ (void);
!   extern ftnlen l_ge (char *, char *, ftnlen, ftnlen);
!   extern ftnlen l_gt (char *, char *, ftnlen, ftnlen);
!   extern ftnlen l_le (char *, char *, ftnlen, ftnlen);
!   extern ftnlen l_lt (char *, char *, ftnlen, ftnlen);
!   extern void pow_ci (complex *, complex *, integer *);
!   extern double pow_dd (double *, double *);
!   extern double pow_di (double *, integer *);
!   extern short pow_hh (short *, shortint *);
!   extern integer pow_ii (integer *, integer *);
!   extern double pow_ri (float *, integer *);
!   extern void pow_zi (doublecomplex *, doublecomplex *, integer *);
!   extern void pow_zz (doublecomplex *, doublecomplex *, doublecomplex *);
!   extern double r_abs (float *);
!   extern double r_acos (float *);
!   extern double r_asin (float *);
!   extern double r_atan (float *);
!   extern double r_atn2 (float *, float *);
!   extern void r_cnjg (complex *, complex *);
!   extern double r_cos (float *);
!   extern double r_cosh (float *);
!   extern double r_dim (float *, float *);
!   extern double r_exp (float *);
!   extern double r_imag (complex *);
!   extern double r_int (float *);
!   extern double r_lg10 (float *);
!   extern double r_log (float *);
!   extern double r_mod (float *, float *);
!   extern double r_nint (float *);
!   extern double r_sign (float *, float *);
!   extern double r_sin (float *);
!   extern double r_sinh (float *);
!   extern double r_sqrt (float *);
!   extern double r_tan (float *);
!   extern double r_tanh (float *);
!   extern void s_cat (char *, char **, integer *, integer *, ftnlen);
!   extern integer s_cmp (char *, char *, ftnlen, ftnlen);
!   extern void s_copy (char *, char *, ftnlen, ftnlen);
!   extern int s_paus (char *, ftnlen);
!   extern integer s_rdfe (cilist *);
!   extern integer s_rdue (cilist *);
!   extern integer s_rnge (char *, integer, char *, integer);
!   extern integer s_rsfe (cilist *);
!   extern integer s_rsfi (icilist *);
!   extern integer s_rsle (cilist *);
!   extern integer s_rsli (icilist *);
!   extern integer s_rsne (cilist *);
!   extern integer s_rsni (icilist *);
!   extern integer s_rsue (cilist *);
!   extern int s_stop (char *, ftnlen);
!   extern integer s_wdfe (cilist *);
!   extern integer s_wdue (cilist *);
!   extern integer s_wsfe (cilist *);
!   extern integer s_wsfi (icilist *);
!   extern integer s_wsle (cilist *);
!   extern integer s_wsli (icilist *);
!   extern integer s_wsne (cilist *);
!   extern integer s_wsni (icilist *);
!   extern integer s_wsue (cilist *);
!   extern void sig_die (char *, int);
!   extern integer signal_ (integer *, void (*)(int));
!   extern integer system_ (char *, ftnlen);
!   extern double z_abs (doublecomplex *);
!   extern void z_cos (doublecomplex *, doublecomplex *);
!   extern void z_div (doublecomplex *, doublecomplex *, doublecomplex *);
!   extern void z_exp (doublecomplex *, doublecomplex *);
!   extern void z_log (doublecomplex *, doublecomplex *);
!   extern void z_sin (doublecomplex *, doublecomplex *);
!   extern void z_sqrt (doublecomplex *, doublecomplex *);
! }
  #endif
diff -Nrc3pad gcc-3.2.3/libf2c/libI77/fio.h gcc-3.3/libf2c/libI77/fio.h
*** gcc-3.2.3/libf2c/libI77/fio.h	2002-01-15 17:27:05.000000000 +0000
--- gcc-3.3/libf2c/libI77/fio.h	2002-06-01 12:38:29.000000000 +0000
*************** typedef long uiolen;
*** 39,103 ****
  
  /*units*/
  typedef struct
! {	FILE *ufd;	/*0=unconnected*/
! 	char *ufnm;
  #if !(defined (MSDOS) && !defined (GO32))
! 	long uinode;
! 	int udev;
  #endif
! 	int url;	/*0=sequential*/
! 	flag useek;	/*true=can backspace, use dir, ...*/
! 	flag ufmt;
! 	flag urw;	/* (1 for can read) | (2 for can write) */
! 	flag ublnk;
! 	flag uend;
! 	flag uwrt;	/*last io was write*/
! 	flag uscrtch;
! } unit;
  
  extern int f__init;
! extern cilist *f__elist;	/*active external io list*/
! extern flag f__reading,f__external,f__sequential,f__formatted;
! #undef Void
! #ifdef KR_headers
! #define Void /*void*/
! extern int (*f__getn)();	/* for formatted input */
! extern void (*f__putn)();	/* for formatted output */
! extern void x_putc();
! extern long f__inode();
! extern VOID sig_die();
! extern int (*f__donewrec)(), t_putc(), x_wSL();
! extern int c_sfe(), err__fl(), xrd_SL(), f__putbuf();
! #else
! #define Void void
! #ifdef __cplusplus
! extern "C" {
! #endif
! extern int (*f__getn)(void);	/* for formatted input */
! extern void (*f__putn)(int);	/* for formatted output */
! extern void x_putc(int);
! extern long f__inode(char*,int*);
! extern void sig_die(char*,int);
! extern void f__fatal(int,char*);
! extern int t_runc(alist*);
! extern int f__nowreading(unit*), f__nowwriting(unit*);
! extern int fk_open(int,int,ftnint);
! extern int en_fio(void);
! extern void f_init(void);
! extern int (*f__donewrec)(void), t_putc(int), x_wSL(void);
! extern void b_char(char*,char*,ftnlen), g_char(char*,ftnlen,char*);
! extern int c_sfe(cilist*), z_rnew(void);
! extern int isatty(int);
! extern int err__fl(int,int,char*);
! extern int xrd_SL(void);
! extern int f__putbuf(int);
! #ifdef __cplusplus
! 	}
! #endif
! #endif
! extern int (*f__doend)(Void);
! extern FILE *f__cf;	/*current file*/
! extern unit *f__curunit;	/*current unit*/
  extern unit f__units[];
  #define err(f,m,s) do {if(f) {f__init &= ~2; errno= m;} else f__fatal(m,s); return(m);} while(0)
  #define errfl(f,m,s) do {return err__fl((int)f,m,s);} while(0)
--- 39,86 ----
  
  /*units*/
  typedef struct
! {
!   FILE *ufd;			/*0=unconnected */
!   char *ufnm;
  #if !(defined (MSDOS) && !defined (GO32))
!   long uinode;
!   int udev;
  #endif
!   int url;			/*0=sequential */
!   flag useek;			/*true=can backspace, use dir, ... */
!   flag ufmt;
!   flag urw;			/* (1 for can read) | (2 for can write) */
!   flag ublnk;
!   flag uend;
!   flag uwrt;			/*last io was write */
!   flag uscrtch;
! }
! unit;
  
  extern int f__init;
! extern cilist *f__elist;	/*active external io list */
! extern flag f__reading, f__external, f__sequential, f__formatted;
! extern int (*f__getn) (void);	/* for formatted input */
! extern void (*f__putn) (int);	/* for formatted output */
! extern void x_putc (int);
! extern long f__inode (char *, int *);
! extern void sig_die (char *, int);
! extern void f__fatal (int, char *);
! extern int t_runc (alist *);
! extern int f__nowreading (unit *), f__nowwriting (unit *);
! extern int fk_open (int, int, ftnint);
! extern int en_fio (void);
! extern void f_init (void);
! extern int (*f__donewrec) (void), t_putc (int), x_wSL (void);
! extern void b_char (char *, char *, ftnlen), g_char (char *, ftnlen, char *);
! extern int c_sfe (cilist *), z_rnew (void);
! extern int isatty (int);
! extern int err__fl (int, int, char *);
! extern int xrd_SL (void);
! extern int f__putbuf (int);
! extern int (*f__doend) (void);
! extern FILE *f__cf;		/*current file */
! extern unit *f__curunit;	/*current unit */
  extern unit f__units[];
  #define err(f,m,s) do {if(f) {f__init &= ~2; errno= m;} else f__fatal(m,s); return(m);} while(0)
  #define errfl(f,m,s) do {return err__fl((int)f,m,s);} while(0)
*************** extern unit f__units[];
*** 105,113 ****
  /*Table sizes*/
  #define MXUNIT 100
  
! extern int f__recpos;	/*position in current record*/
! extern int f__cursor;	/* offset to move to */
! extern int f__hiwater;	/* so TL doesn't confuse us */
  
  #define WRITE	1
  #define READ	2
--- 88,96 ----
  /*Table sizes*/
  #define MXUNIT 100
  
! extern int f__recpos;		/*position in current record */
! extern int f__cursor;		/* offset to move to */
! extern int f__hiwater;		/* so TL doesn't confuse us */
  
  #define WRITE	1
  #define READ	2
diff -Nrc3pad gcc-3.2.3/libf2c/libI77/fmt.c gcc-3.3/libf2c/libI77/fmt.c
*** gcc-3.2.3/libf2c/libI77/fmt.c	2001-05-16 18:59:29.000000000 +0000
--- gcc-3.3/libf2c/libI77/fmt.c	2002-06-02 13:01:11.000000000 +0000
***************
*** 17,544 ****
  #endif
  #define GLITCH '\2'
  	/* special quote character for stu */
! extern int f__cursor,f__scale;
! extern flag f__cblank,f__cplus;	/*blanks in I and compulsory plus*/
  static struct syl f__syl[SYLMX];
! int f__parenlvl,f__pc,f__revloc;
  
!  static
! #ifdef KR_headers
! char *ap_end(s) char *s;
! #else
! char *ap_end(char *s)
! #endif
! {	char quote;
! 	quote= *s++;
! 	for(;*s;s++)
! 	{	if(*s!=quote) continue;
! 		if(*++s!=quote) return(s);
! 	}
! 	if(f__elist->cierr) {
! 		errno = 100;
! 		return(NULL);
! 	}
! 	f__fatal(100, "bad string");
! 	/*NOTREACHED*/ return 0;
  }
!  static
! #ifdef KR_headers
! op_gen(a,b,c,d)
! #else
! op_gen(int a, int b, int c, int d)
! #endif
! {	struct syl *p= &f__syl[f__pc];
! 	if(f__pc>=SYLMX)
! 	{	fprintf(stderr,"format too complicated:\n");
! 		sig_die(f__fmtbuf, 1);
! 	}
! 	p->op=a;
! 	p->p1=b;
! 	p->p2.i[0]=c;
! 	p->p2.i[1]=d;
! 	return(f__pc++);
  }
! #ifdef KR_headers
! static char *f_list();
! static char *gt_num(s,n,n1) char *s; int *n, n1;
! #else
! static char *f_list(char*);
! static char *gt_num(char *s, int *n, int n1)
! #endif
! {	int m=0,f__cnt=0;
! 	char c;
! 	for(c= *s;;c = *s)
! 	{	if(c==' ')
! 		{	s++;
! 			continue;
! 		}
! 		if(c>'9' || c<'0') break;
! 		m=10*m+c-'0';
! 		f__cnt++;
! 		s++;
  	}
! 	if(f__cnt==0) {
! 		if (!n1)
! 			s = 0;
! 		*n=n1;
! 		}
! 	else *n=m;
! 	return(s);
  }
  
!  static
! #ifdef KR_headers
! char *f_s(s,curloc) char *s;
! #else
! char *f_s(char *s, int curloc)
! #endif
  {
! 	skip(s);
! 	if(*s++!='(')
  	{
! 		return(NULL);
  	}
! 	if(f__parenlvl++ ==1) f__revloc=curloc;
! 	if(op_gen(RET1,curloc,0,0)<0 ||
! 		(s=f_list(s))==NULL)
  	{
! 		return(NULL);
  	}
! 	return(s);
! }
! 
!  static
! #ifdef KR_headers
! ne_d(s,p) char *s,**p;
! #else
! ne_d(char *s, char **p)
! #endif
! {	int n,x,sign=0;
! 	struct syl *sp;
! 	switch(*s)
  	{
  	default:
! 		return(0);
! 	case ':': (void) op_gen(COLON,0,0,0); break;
! 	case '$':
! 		(void) op_gen(NONL, 0, 0, 0); break;
! 	case 'B':
! 	case 'b':
! 		if(*++s=='z' || *s == 'Z') (void) op_gen(BZ,0,0,0);
! 		else (void) op_gen(BN,0,0,0);
! 		break;
! 	case 'S':
! 	case 's':
! 		if(*(s+1)=='s' || *(s+1) == 'S')
! 		{	x=SS;
! 			s++;
! 		}
! 		else if(*(s+1)=='p' || *(s+1) == 'P')
! 		{	x=SP;
! 			s++;
! 		}
! 		else x=S;
! 		(void) op_gen(x,0,0,0);
! 		break;
! 	case '/': (void) op_gen(SLASH,0,0,0); break;
! 	case '-': sign=1;
! 	case '+':	s++;	/*OUTRAGEOUS CODING TRICK*/
! 	case '0': case '1': case '2': case '3': case '4':
! 	case '5': case '6': case '7': case '8': case '9':
! 		if (!(s=gt_num(s,&n,0))) {
!  bad:			*p = 0;
! 			return 1;
! 			}
! 		switch(*s)
! 		{
! 		default:
! 			return(0);
! 		case 'P':
! 		case 'p': if(sign) n= -n; (void) op_gen(P,n,0,0); break;
! 		case 'X':
! 		case 'x': (void) op_gen(X,n,0,0); break;
! 		case 'H':
! 		case 'h':
! 			sp = &f__syl[op_gen(H,n,0,0)];
! 			sp->p2.s = s + 1;
! 			s+=n;
! 			break;
! 		}
! 		break;
! 	case GLITCH:
! 	case '"':
! 	case '\'':
! 		sp = &f__syl[op_gen(APOS,0,0,0)];
! 		sp->p2.s = s;
! 		if((*p = ap_end(s)) == NULL)
! 			return(0);
! 		return(1);
! 	case 'T':
! 	case 't':
! 		if(*(s+1)=='l' || *(s+1) == 'L')
! 		{	x=TL;
! 			s++;
! 		}
! 		else if(*(s+1)=='r'|| *(s+1) == 'R')
! 		{	x=TR;
! 			s++;
! 		}
! 		else x=T;
! 		if (!(s=gt_num(s+1,&n,0)))
! 			goto bad;
! 		s--;
! 		(void) op_gen(x,n,0,0);
! 		break;
! 	case 'X':
! 	case 'x': (void) op_gen(X,1,0,0); break;
  	case 'P':
! 	case 'p': (void) op_gen(P,1,0,0); break;
  	}
! 	s++;
! 	*p=s;
! 	return(1);
  }
  
!  static
! #ifdef KR_headers
! e_d(s,p) char *s,**p;
! #else
! e_d(char *s, char **p)
! #endif
! {	int i,im,n,w,d,e,found=0,x=0;
! 	char *sv=s;
! 	s=gt_num(s,&n,1);
! 	(void) op_gen(STACK,n,0,0);
! 	switch(*s++)
  	{
! 	default: break;
! 	case 'E':
! 	case 'e':	x=1;
! 	case 'G':
! 	case 'g':
! 		found=1;
! 		if (!(s=gt_num(s,&w,0))) {
!  bad:
! 			*p = 0;
! 			return 1;
! 			}
! 		if(w==0) break;
! 		if(*s=='.') {
! 			if (!(s=gt_num(s+1,&d,0)))
! 				goto bad;
! 			}
! 		else d=0;
! 		if(*s!='E' && *s != 'e')
! 			(void) op_gen(x==1?E:G,w,d,0);	/* default is Ew.dE2 */
! 		else {
! 			if (!(s=gt_num(s+1,&e,0)))
! 				goto bad;
! 			(void) op_gen(x==1?EE:GE,w,d,e);
! 			}
! 		break;
! 	case 'O':
! 	case 'o':
! 		i = O;
! 		im = OM;
! 		goto finish_I;
! 	case 'Z':
! 	case 'z':
! 		i = Z;
! 		im = ZM;
! 		goto finish_I;
! 	case 'L':
! 	case 'l':
! 		found=1;
! 		if (!(s=gt_num(s,&w,0)))
! 			goto bad;
! 		if(w==0) break;
! 		(void) op_gen(L,w,0,0);
! 		break;
! 	case 'A':
! 	case 'a':
! 		found=1;
! 		skip(s);
! 		if(*s>='0' && *s<='9')
! 		{	s=gt_num(s,&w,1);
! 			if(w==0) break;
! 			(void) op_gen(AW,w,0,0);
! 			break;
! 		}
! 		(void) op_gen(A,0,0,0);
! 		break;
! 	case 'F':
! 	case 'f':
! 		if (!(s=gt_num(s,&w,0)))
! 			goto bad;
! 		found=1;
! 		if(w==0) break;
! 		if(*s=='.') {
! 			if (!(s=gt_num(s+1,&d,0)))
! 				goto bad;
! 			}
! 		else d=0;
! 		(void) op_gen(F,w,d,0);
! 		break;
! 	case 'D':
! 	case 'd':
! 		found=1;
! 		if (!(s=gt_num(s,&w,0)))
! 			goto bad;
! 		if(w==0) break;
! 		if(*s=='.') {
! 			if (!(s=gt_num(s+1,&d,0)))
! 				goto bad;
! 			}
! 		else d=0;
! 		(void) op_gen(D,w,d,0);
! 		break;
! 	case 'I':
! 	case 'i':
! 		i = I;
! 		im = IM;
!  finish_I:
! 		if (!(s=gt_num(s,&w,0)))
! 			goto bad;
! 		found=1;
! 		if(w==0) break;
! 		if(*s!='.')
! 		{	(void) op_gen(i,w,0,0);
! 			break;
! 		}
! 		if (!(s=gt_num(s+1,&d,0)))
! 			goto bad;
! 		(void) op_gen(im,w,d,0);
! 		break;
  	}
! 	if(found==0)
! 	{	f__pc--; /*unSTACK*/
! 		*p=sv;
! 		return(0);
  	}
! 	*p=s;
! 	return(1);
  }
!  static
! #ifdef KR_headers
! char *i_tem(s) char *s;
! #else
! char *i_tem(char *s)
! #endif
! {	char *t;
! 	int n,curloc;
! 	if(*s==')') return(s);
! 	if(ne_d(s,&t)) return(t);
! 	if(e_d(s,&t)) return(t);
! 	s=gt_num(s,&n,1);
! 	if((curloc=op_gen(STACK,n,0,0))<0) return(NULL);
! 	return(f_s(s,curloc));
  }
  
!  static
! #ifdef KR_headers
! char *f_list(s) char *s;
! #else
! char *f_list(char *s)
! #endif
  {
! 	for(;*s!=0;)
! 	{	skip(s);
! 		if((s=i_tem(s))==NULL) return(NULL);
! 		skip(s);
! 		if(*s==',') s++;
! 		else if(*s==')')
! 		{	if(--f__parenlvl==0)
! 			{
! 				(void) op_gen(REVERT,f__revloc,0,0);
! 				return(++s);
! 			}
! 			(void) op_gen(GOTO,0,0,0);
! 			return(++s);
! 		}
  	}
! 	return(NULL);
  }
  
! #ifdef KR_headers
! pars_f(s) char *s;
! #else
! pars_f(char *s)
! #endif
  {
! 	char *e;
  
! 	f__parenlvl=f__revloc=f__pc=0;
! 	if((e=f_s(s,0)) == NULL)
! 	{
! 		/* Try and delimit the format string.  Parens within
! 		   hollerith and quoted strings have to match for this
! 		   to work, but it's probably adequate for most needs.
! 		   Note that this is needed because a valid CHARACTER
! 		   variable passed for FMT= can contain '(I)garbage',
! 		   where `garbage' is billions and billions of junk
! 		   characters, and it's up to the run-time library to
! 		   know where the format string ends by counting parens.
! 		   Meanwhile, still treat NUL byte as "hard stop", since
! 		   f2c still appends that at end of FORMAT-statement
! 		   strings.  */
  
! 		int level=0;
  
! 		for (f__fmtlen=0;
! 			((*s!=')') || (--level > 0))
! 				&& (*s!='\0')
! 				&& (f__fmtlen<80);
! 			++s, ++f__fmtlen)
! 		{
! 			if (*s=='(')
! 				++level;
! 		}
! 		if (*s==')')
! 			++f__fmtlen;
! 		return(-1);
  	}
! 	f__fmtlen = e - s;
! 	return(0);
  }
  #define STKSZ 10
! int f__cnt[STKSZ],f__ret[STKSZ],f__cp,f__rp;
  flag f__workdone, f__nonl;
  
!  static
! #ifdef KR_headers
! type_f(n)
! #else
! type_f(int n)
! #endif
  {
! 	switch(n)
! 	{
! 	default:
! 		return(n);
! 	case RET1:
! 		return(RET1);
! 	case REVERT: return(REVERT);
! 	case GOTO: return(GOTO);
! 	case STACK: return(STACK);
! 	case X:
! 	case SLASH:
! 	case APOS: case H:
! 	case T: case TL: case TR:
! 		return(NED);
! 	case F:
! 	case I:
! 	case IM:
! 	case A: case AW:
! 	case O: case OM:
! 	case L:
! 	case E: case EE: case D:
! 	case G: case GE:
! 	case Z: case ZM:
! 		return(ED);
! 	}
  }
! #ifdef KR_headers
! integer do_fio(number,ptr,len) ftnint *number; ftnlen len; char *ptr;
! #else
! integer do_fio(ftnint *number, char *ptr, ftnlen len)
! #endif
! {	struct syl *p;
! 	int n,i;
! 	for(i=0;i<*number;i++,ptr+=len)
! 	{
! loop:	switch(type_f((p= &f__syl[f__pc])->op))
  	{
  	default:
! 		fprintf(stderr,"unknown code in do_fio: %d\n%.*s\n",
! 			p->op,f__fmtlen,f__fmtbuf);
! 		err(f__elist->cierr,100,"do_fio");
  	case NED:
! 		if((*f__doned)(p))
! 		{	f__pc++;
! 			goto loop;
! 		}
! 		f__pc++;
! 		continue;
  	case ED:
! 		if(f__cnt[f__cp]<=0)
! 		{	f__cp--;
! 			f__pc++;
! 			goto loop;
! 		}
! 		if(ptr==NULL)
! 			return((*f__doend)());
! 		f__cnt[f__cp]--;
! 		f__workdone=1;
! 		if((n=(*f__doed)(p,ptr,len))>0)
! 			errfl(f__elist->cierr,errno,"fmt");
! 		if(n<0)
! 			err(f__elist->ciend,(EOF),"fmt");
! 		continue;
  	case STACK:
! 		f__cnt[++f__cp]=p->p1;
! 		f__pc++;
! 		goto loop;
  	case RET1:
! 		f__ret[++f__rp]=p->p1;
! 		f__pc++;
! 		goto loop;
  	case GOTO:
! 		if(--f__cnt[f__cp]<=0)
! 		{	f__cp--;
! 			f__rp--;
! 			f__pc++;
! 			goto loop;
! 		}
! 		f__pc=1+f__ret[f__rp--];
! 		goto loop;
  	case REVERT:
! 		f__rp=f__cp=0;
! 		f__pc = p->p1;
! 		if(ptr==NULL)
! 			return((*f__doend)());
! 		if(!f__workdone) return(0);
! 		if((n=(*f__dorevert)()) != 0) return(n);
! 		goto loop;
  	case COLON:
! 		if(ptr==NULL)
! 			return((*f__doend)());
! 		f__pc++;
! 		goto loop;
  	case NONL:
! 		f__nonl = 1;
! 		f__pc++;
! 		goto loop;
  	case S:
  	case SS:
! 		f__cplus=0;
! 		f__pc++;
! 		goto loop;
  	case SP:
! 		f__cplus = 1;
! 		f__pc++;
! 		goto loop;
! 	case P:	f__scale=p->p1;
! 		f__pc++;
! 		goto loop;
  	case BN:
! 		f__cblank=0;
! 		f__pc++;
! 		goto loop;
  	case BZ:
! 		f__cblank=1;
! 		f__pc++;
! 		goto loop;
! 	}
  	}
! 	return(0);
  }
! en_fio(Void)
! {	ftnint one=1;
! 	return(do_fio(&one,(char *)NULL,(ftnint)0));
  }
!  VOID
! fmt_bg(Void)
  {
! 	f__workdone=f__cp=f__rp=f__pc=f__cursor=0;
! 	f__cnt[0]=f__ret[0]=0;
  }
--- 17,602 ----
  #endif
  #define GLITCH '\2'
  	/* special quote character for stu */
! extern int f__cursor, f__scale;
! extern flag f__cblank, f__cplus;	/*blanks in I and compulsory plus */
  static struct syl f__syl[SYLMX];
! int f__parenlvl, f__pc, f__revloc;
  
! static char *
! ap_end (char *s)
! {
!   char quote;
!   quote = *s++;
!   for (; *s; s++)
!     {
!       if (*s != quote)
! 	continue;
!       if (*++s != quote)
! 	return (s);
!     }
!   if (f__elist->cierr)
!     {
!       errno = 100;
!       return (NULL);
!     }
!   f__fatal (100, "bad string");
!    /*NOTREACHED*/ return 0;
  }
! 
! static int
! op_gen (int a, int b, int c, int d)
! {
!   struct syl *p = &f__syl[f__pc];
!   if (f__pc >= SYLMX)
!     {
!       fprintf (stderr, "format too complicated:\n");
!       sig_die (f__fmtbuf, 1);
!     }
!   p->op = a;
!   p->p1 = b;
!   p->p2.i[0] = c;
!   p->p2.i[1] = d;
!   return (f__pc++);
  }
! static char *f_list (char *);
! static char *
! gt_num (char *s, int *n, int n1)
! {
!   int m = 0, f__cnt = 0;
!   char c;
!   for (c = *s;; c = *s)
!     {
!       if (c == ' ')
! 	{
! 	  s++;
! 	  continue;
  	}
!       if (c > '9' || c < '0')
! 	break;
!       m = 10 * m + c - '0';
!       f__cnt++;
!       s++;
!     }
!   if (f__cnt == 0)
!     {
!       if (!n1)
! 	s = 0;
!       *n = n1;
!     }
!   else
!     *n = m;
!   return (s);
  }
  
! static char *
! f_s (char *s, int curloc)
  {
!   skip (s);
!   if (*s++ != '(')
!     {
!       return (NULL);
!     }
!   if (f__parenlvl++ == 1)
!     f__revloc = curloc;
!   if (op_gen (RET1, curloc, 0, 0) < 0 || (s = f_list (s)) == NULL)
!     {
!       return (NULL);
!     }
!   return (s);
! }
! 
! static int
! ne_d (char *s, char **p)
! {
!   int n, x, sign = 0;
!   struct syl *sp;
!   switch (*s)
!     {
!     default:
!       return (0);
!     case ':':
!       (void) op_gen (COLON, 0, 0, 0);
!       break;
!     case '$':
!       (void) op_gen (NONL, 0, 0, 0);
!       break;
!     case 'B':
!     case 'b':
!       if (*++s == 'z' || *s == 'Z')
! 	(void) op_gen (BZ, 0, 0, 0);
!       else
! 	(void) op_gen (BN, 0, 0, 0);
!       break;
!     case 'S':
!     case 's':
!       if (*(s + 1) == 's' || *(s + 1) == 'S')
  	{
! 	  x = SS;
! 	  s++;
  	}
!       else if (*(s + 1) == 'p' || *(s + 1) == 'P')
  	{
! 	  x = SP;
! 	  s++;
  	}
!       else
! 	x = S;
!       (void) op_gen (x, 0, 0, 0);
!       break;
!     case '/':
!       (void) op_gen (SLASH, 0, 0, 0);
!       break;
!     case '-':
!       sign = 1;
!     case '+':
!       s++;			/*OUTRAGEOUS CODING TRICK */
!     case '0':
!     case '1':
!     case '2':
!     case '3':
!     case '4':
!     case '5':
!     case '6':
!     case '7':
!     case '8':
!     case '9':
!       if (!(s = gt_num (s, &n, 0)))
! 	{
! 	bad:*p = 0;
! 	  return 1;
! 	}
!       switch (*s)
  	{
  	default:
! 	  return (0);
  	case 'P':
! 	case 'p':
! 	  if (sign)
! 	    n = -n;
! 	  (void) op_gen (P, n, 0, 0);
! 	  break;
! 	case 'X':
! 	case 'x':
! 	  (void) op_gen (X, n, 0, 0);
! 	  break;
! 	case 'H':
! 	case 'h':
! 	  sp = &f__syl[op_gen (H, n, 0, 0)];
! 	  sp->p2.s = s + 1;
! 	  s += n;
! 	  break;
  	}
!       break;
!     case GLITCH:
!     case '"':
!     case '\'':
!       sp = &f__syl[op_gen (APOS, 0, 0, 0)];
!       sp->p2.s = s;
!       if ((*p = ap_end (s)) == NULL)
! 	return (0);
!       return (1);
!     case 'T':
!     case 't':
!       if (*(s + 1) == 'l' || *(s + 1) == 'L')
! 	{
! 	  x = TL;
! 	  s++;
! 	}
!       else if (*(s + 1) == 'r' || *(s + 1) == 'R')
! 	{
! 	  x = TR;
! 	  s++;
! 	}
!       else
! 	x = T;
!       if (!(s = gt_num (s + 1, &n, 0)))
! 	goto bad;
!       s--;
!       (void) op_gen (x, n, 0, 0);
!       break;
!     case 'X':
!     case 'x':
!       (void) op_gen (X, 1, 0, 0);
!       break;
!     case 'P':
!     case 'p':
!       (void) op_gen (P, 1, 0, 0);
!       break;
!     }
!   s++;
!   *p = s;
!   return (1);
  }
  
! static int
! e_d (char *s, char **p)
! {
!   int i, im, n, w, d, e, found = 0, x = 0;
!   char *sv = s;
!   s = gt_num (s, &n, 1);
!   (void) op_gen (STACK, n, 0, 0);
!   switch (*s++)
!     {
!     default:
!       break;
!     case 'E':
!     case 'e':
!       x = 1;
!     case 'G':
!     case 'g':
!       found = 1;
!       if (!(s = gt_num (s, &w, 0)))
  	{
! 	bad:
! 	  *p = 0;
! 	  return 1;
  	}
!       if (w == 0)
! 	break;
!       if (*s == '.')
! 	{
! 	  if (!(s = gt_num (s + 1, &d, 0)))
! 	    goto bad;
  	}
!       else
! 	d = 0;
!       if (*s != 'E' && *s != 'e')
! 	(void) op_gen (x == 1 ? E : G, w, d, 0);	/* default is Ew.dE2 */
!       else
! 	{
! 	  if (!(s = gt_num (s + 1, &e, 0)))
! 	    goto bad;
! 	  (void) op_gen (x == 1 ? EE : GE, w, d, e);
! 	}
!       break;
!     case 'O':
!     case 'o':
!       i = O;
!       im = OM;
!       goto finish_I;
!     case 'Z':
!     case 'z':
!       i = Z;
!       im = ZM;
!       goto finish_I;
!     case 'L':
!     case 'l':
!       found = 1;
!       if (!(s = gt_num (s, &w, 0)))
! 	goto bad;
!       if (w == 0)
! 	break;
!       (void) op_gen (L, w, 0, 0);
!       break;
!     case 'A':
!     case 'a':
!       found = 1;
!       skip (s);
!       if (*s >= '0' && *s <= '9')
! 	{
! 	  s = gt_num (s, &w, 1);
! 	  if (w == 0)
! 	    break;
! 	  (void) op_gen (AW, w, 0, 0);
! 	  break;
! 	}
!       (void) op_gen (A, 0, 0, 0);
!       break;
!     case 'F':
!     case 'f':
!       if (!(s = gt_num (s, &w, 0)))
! 	goto bad;
!       found = 1;
!       if (w == 0)
! 	break;
!       if (*s == '.')
! 	{
! 	  if (!(s = gt_num (s + 1, &d, 0)))
! 	    goto bad;
! 	}
!       else
! 	d = 0;
!       (void) op_gen (F, w, d, 0);
!       break;
!     case 'D':
!     case 'd':
!       found = 1;
!       if (!(s = gt_num (s, &w, 0)))
! 	goto bad;
!       if (w == 0)
! 	break;
!       if (*s == '.')
! 	{
! 	  if (!(s = gt_num (s + 1, &d, 0)))
! 	    goto bad;
! 	}
!       else
! 	d = 0;
!       (void) op_gen (D, w, d, 0);
!       break;
!     case 'I':
!     case 'i':
!       i = I;
!       im = IM;
!     finish_I:
!       if (!(s = gt_num (s, &w, 0)))
! 	goto bad;
!       found = 1;
!       if (w == 0)
! 	break;
!       if (*s != '.')
! 	{
! 	  (void) op_gen (i, w, 0, 0);
! 	  break;
! 	}
!       if (!(s = gt_num (s + 1, &d, 0)))
! 	goto bad;
!       (void) op_gen (im, w, d, 0);
!       break;
!     }
!   if (found == 0)
!     {
!       f__pc--;			/*unSTACK */
!       *p = sv;
!       return (0);
!     }
!   *p = s;
!   return (1);
  }
! static char *
! i_tem (char *s)
! {
!   char *t;
!   int n, curloc;
!   if (*s == ')')
!     return (s);
!   if (ne_d (s, &t))
!     return (t);
!   if (e_d (s, &t))
!     return (t);
!   s = gt_num (s, &n, 1);
!   if ((curloc = op_gen (STACK, n, 0, 0)) < 0)
!     return (NULL);
!   return (f_s (s, curloc));
  }
  
! static char *
! f_list (char *s)
  {
!   for (; *s != 0;)
!     {
!       skip (s);
!       if ((s = i_tem (s)) == NULL)
! 	return (NULL);
!       skip (s);
!       if (*s == ',')
! 	s++;
!       else if (*s == ')')
! 	{
! 	  if (--f__parenlvl == 0)
! 	    {
! 	      (void) op_gen (REVERT, f__revloc, 0, 0);
! 	      return (++s);
! 	    }
! 	  (void) op_gen (GOTO, 0, 0, 0);
! 	  return (++s);
  	}
!     }
!   return (NULL);
  }
  
! int
! pars_f (char *s)
  {
!   char *e;
  
!   f__parenlvl = f__revloc = f__pc = 0;
!   if ((e = f_s (s, 0)) == NULL)
!     {
!       /* Try and delimit the format string.  Parens within
!          hollerith and quoted strings have to match for this
!          to work, but it's probably adequate for most needs.
!          Note that this is needed because a valid CHARACTER
!          variable passed for FMT= can contain '(I)garbage',
!          where `garbage' is billions and billions of junk
!          characters, and it's up to the run-time library to
!          know where the format string ends by counting parens.
!          Meanwhile, still treat NUL byte as "hard stop", since
!          f2c still appends that at end of FORMAT-statement
!          strings.  */
  
!       int level = 0;
  
!       for (f__fmtlen = 0;
! 	   ((*s != ')') || (--level > 0))
! 	   && (*s != '\0') && (f__fmtlen < 80); ++s, ++f__fmtlen)
! 	{
! 	  if (*s == '(')
! 	    ++level;
  	}
!       if (*s == ')')
! 	++f__fmtlen;
!       return (-1);
!     }
!   f__fmtlen = e - s;
!   return (0);
  }
+ 
  #define STKSZ 10
! int f__cnt[STKSZ], f__ret[STKSZ], f__cp, f__rp;
  flag f__workdone, f__nonl;
  
! static int
! type_f (int n)
  {
!   switch (n)
!     {
!     default:
!       return (n);
!     case RET1:
!       return (RET1);
!     case REVERT:
!       return (REVERT);
!     case GOTO:
!       return (GOTO);
!     case STACK:
!       return (STACK);
!     case X:
!     case SLASH:
!     case APOS:
!     case H:
!     case T:
!     case TL:
!     case TR:
!       return (NED);
!     case F:
!     case I:
!     case IM:
!     case A:
!     case AW:
!     case O:
!     case OM:
!     case L:
!     case E:
!     case EE:
!     case D:
!     case G:
!     case GE:
!     case Z:
!     case ZM:
!       return (ED);
!     }
  }
! integer
! do_fio (ftnint * number, char *ptr, ftnlen len)
! {
!   struct syl *p;
!   int n, i;
!   for (i = 0; i < *number; i++, ptr += len)
!     {
!     loop:switch (type_f ((p = &f__syl[f__pc])->op))
  	{
  	default:
! 	  fprintf (stderr, "unknown code in do_fio: %d\n%.*s\n",
! 		   p->op, f__fmtlen, f__fmtbuf);
! 	  err (f__elist->cierr, 100, "do_fio");
  	case NED:
! 	  if ((*f__doned) (p))
! 	    {
! 	      f__pc++;
! 	      goto loop;
! 	    }
! 	  f__pc++;
! 	  continue;
  	case ED:
! 	  if (f__cnt[f__cp] <= 0)
! 	    {
! 	      f__cp--;
! 	      f__pc++;
! 	      goto loop;
! 	    }
! 	  if (ptr == NULL)
! 	    return ((*f__doend) ());
! 	  f__cnt[f__cp]--;
! 	  f__workdone = 1;
! 	  if ((n = (*f__doed) (p, ptr, len)) > 0)
! 	    errfl (f__elist->cierr, errno, "fmt");
! 	  if (n < 0)
! 	    err (f__elist->ciend, (EOF), "fmt");
! 	  continue;
  	case STACK:
! 	  f__cnt[++f__cp] = p->p1;
! 	  f__pc++;
! 	  goto loop;
  	case RET1:
! 	  f__ret[++f__rp] = p->p1;
! 	  f__pc++;
! 	  goto loop;
  	case GOTO:
! 	  if (--f__cnt[f__cp] <= 0)
! 	    {
! 	      f__cp--;
! 	      f__rp--;
! 	      f__pc++;
! 	      goto loop;
! 	    }
! 	  f__pc = 1 + f__ret[f__rp--];
! 	  goto loop;
  	case REVERT:
! 	  f__rp = f__cp = 0;
! 	  f__pc = p->p1;
! 	  if (ptr == NULL)
! 	    return ((*f__doend) ());
! 	  if (!f__workdone)
! 	    return (0);
! 	  if ((n = (*f__dorevert) ()) != 0)
! 	    return (n);
! 	  goto loop;
  	case COLON:
! 	  if (ptr == NULL)
! 	    return ((*f__doend) ());
! 	  f__pc++;
! 	  goto loop;
  	case NONL:
! 	  f__nonl = 1;
! 	  f__pc++;
! 	  goto loop;
  	case S:
  	case SS:
! 	  f__cplus = 0;
! 	  f__pc++;
! 	  goto loop;
  	case SP:
! 	  f__cplus = 1;
! 	  f__pc++;
! 	  goto loop;
! 	case P:
! 	  f__scale = p->p1;
! 	  f__pc++;
! 	  goto loop;
  	case BN:
! 	  f__cblank = 0;
! 	  f__pc++;
! 	  goto loop;
  	case BZ:
! 	  f__cblank = 1;
! 	  f__pc++;
! 	  goto loop;
  	}
!     }
!   return (0);
  }
! 
! int
! en_fio (void)
! {
!   ftnint one = 1;
!   return (do_fio (&one, (char *) NULL, (ftnint) 0));
  }
! 
! void
! fmt_bg (void)
  {
!   f__workdone = f__cp = f__rp = f__pc = f__cursor = 0;
!   f__cnt[0] = f__ret[0] = 0;
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libI77/fmt.h gcc-3.3/libf2c/libI77/fmt.h
*** gcc-3.2.3/libf2c/libI77/fmt.h	1999-09-04 15:09:17.000000000 +0000
--- gcc-3.3/libf2c/libI77/fmt.h	2002-06-01 12:38:30.000000000 +0000
***************
*** 1,8 ****
  struct syl
! {	int op;
! 	int p1;
! 	union { int i[2]; char *s;} p2;
! 	};
  #define RET1 1
  #define REVERT 2
  #define GOTO 3
--- 1,14 ----
  struct syl
! {
!   int op;
!   int p1;
!   union
!   {
!     int i[2];
!     char *s;
!   }
!   p2;
! };
  #define RET1 1
  #define REVERT 2
  #define GOTO 3
*************** struct syl
*** 39,83 ****
  #define OM 34
  #define Z 35
  #define ZM 36
! extern int f__pc,f__parenlvl,f__revloc;
  typedef union
! {	real pf;
! 	doublereal pd;
! } ufloat;
  typedef union
! {	short is;
! #ifndef KR_headers
! 	signed
! #endif
! 		char ic;
! 	integer il;
  #ifdef Allow_TYQUAD
! 	longint ili;
! #endif
! } Uint;
! #ifdef KR_headers
! extern int (*f__doed)(),(*f__doned)();
! extern int (*f__dorevert)();
! extern int rd_ed(),rd_ned();
! extern int w_ed(),w_ned();
! #else
! #ifdef __cplusplus
! extern "C" {
! #endif
! extern int (*f__doed)(struct syl*, char*, ftnlen),(*f__doned)(struct syl*);
! extern int (*f__dorevert)(void);
! extern void fmt_bg(void);
! extern int pars_f(char*);
! extern int rd_ed(struct syl*, char*, ftnlen),rd_ned(struct syl*);
! extern int w_ed(struct syl*, char*, ftnlen),w_ned(struct syl*);
! extern int wrt_E(ufloat*, int, int, int, ftnlen);
! extern int wrt_F(ufloat*, int, int, ftnlen);
! extern int wrt_L(Uint*, int, ftnlen);
! #ifdef __cplusplus
! 	}
! #endif
  #endif
! extern flag f__cblank,f__cplus,f__workdone, f__nonl;
  extern char *f__fmtbuf;
  extern int f__fmtlen;
  extern int f__scale;
--- 45,78 ----
  #define OM 34
  #define Z 35
  #define ZM 36
! extern int f__pc, f__parenlvl, f__revloc;
  typedef union
! {
!   real pf;
!   doublereal pd;
! }
! ufloat;
  typedef union
! {
!   short is;
!   signed char ic;
!   integer il;
  #ifdef Allow_TYQUAD
!   longint ili;
  #endif
! }
! Uint;
! extern int (*f__doed) (struct syl *, char *, ftnlen),
!   (*f__doned) (struct syl *);
! extern int (*f__dorevert) (void);
! extern void fmt_bg (void);
! extern int pars_f (char *);
! extern int rd_ed (struct syl *, char *, ftnlen), rd_ned (struct syl *);
! extern int w_ed (struct syl *, char *, ftnlen), w_ned (struct syl *);
! extern int wrt_E (ufloat *, int, int, int, ftnlen);
! extern int wrt_F (ufloat *, int, int, ftnlen);
! extern int wrt_L (Uint *, int, ftnlen);
! extern flag f__cblank, f__cplus, f__workdone, f__nonl;
  extern char *f__fmtbuf;
  extern int f__fmtlen;
  extern int f__scale;
*************** extern int f__cursor;
*** 94,101 ****
  #define TYQUAD 14
  #endif
  
! #ifdef KR_headers
! extern char *f__icvt();
! #else
! extern char *f__icvt(longint, int*, int*, int);
! #endif
--- 89,92 ----
  #define TYQUAD 14
  #endif
  
! extern char *f__icvt (longint, int *, int *, int);
diff -Nrc3pad gcc-3.2.3/libf2c/libI77/fmtlib.c gcc-3.3/libf2c/libI77/fmtlib.c
*** gcc-3.2.3/libf2c/libI77/fmtlib.c	2001-05-16 18:59:29.000000000 +0000
--- gcc-3.3/libf2c/libI77/fmtlib.c	2002-06-01 12:38:30.000000000 +0000
***************
*** 10,46 ****
  #define ulongint unsigned long
  #endif
  
! #ifdef KR_headers
! char *f__icvt(value,ndigit,sign, base) longint value; int *ndigit,*sign;
!  register int base;
! #else
! char *f__icvt(longint value, int *ndigit, int *sign, int base)
! #endif
  {
! 	static char buf[MAXINTLENGTH+1];
! 	register int i;
! 	ulongint uvalue;
  
! 	if(value > 0) {
! 		uvalue = value;
! 		*sign = 0;
! 		}
! 	else if (value < 0) {
! 		uvalue = -value;
! 		*sign = 1;
! 		}
! 	else {
! 		*sign = 0;
! 		*ndigit = 1;
! 		buf[MAXINTLENGTH-1] = '0';
! 		return &buf[MAXINTLENGTH-1];
! 		}
! 	i = MAXINTLENGTH;
! 	do {
! 		buf[--i] = (uvalue%base) + '0';
! 		uvalue /= base;
! 		}
! 		while(uvalue > 0);
! 	*ndigit = MAXINTLENGTH - i;
! 	return &buf[i];
! 	}
--- 10,46 ----
  #define ulongint unsigned long
  #endif
  
! char *
! f__icvt (longint value, int *ndigit, int *sign, int base)
  {
!   static char buf[MAXINTLENGTH + 1];
!   register int i;
!   ulongint uvalue;
  
!   if (value > 0)
!     {
!       uvalue = value;
!       *sign = 0;
!     }
!   else if (value < 0)
!     {
!       uvalue = -value;
!       *sign = 1;
!     }
!   else
!     {
!       *sign = 0;
!       *ndigit = 1;
!       buf[MAXINTLENGTH - 1] = '0';
!       return &buf[MAXINTLENGTH - 1];
!     }
!   i = MAXINTLENGTH;
!   do
!     {
!       buf[--i] = (uvalue % base) + '0';
!       uvalue /= base;
!     }
!   while (uvalue > 0);
!   *ndigit = MAXINTLENGTH - i;
!   return &buf[i];
! }
diff -Nrc3pad gcc-3.2.3/libf2c/libI77/fp.h gcc-3.3/libf2c/libI77/fp.h
*** gcc-3.2.3/libf2c/libI77/fp.h	1999-09-04 15:09:18.000000000 +0000
--- gcc-3.3/libf2c/libI77/fp.h	2002-06-01 12:38:30.000000000 +0000
***************
*** 4,10 ****
  /* FMAX = max number of nonzero digits passed to atof() */
  /* EXPMAX = 10^EXPMAXDIGS - 1 = largest allowed exponent absolute value */
  
! #ifdef V10 /* Research Tenth-Edition Unix */
  #include "local.h"
  #endif
  
--- 4,10 ----
  /* FMAX = max number of nonzero digits passed to atof() */
  /* EXPMAX = 10^EXPMAXDIGS - 1 = largest allowed exponent absolute value */
  
! #ifdef V10			/* Research Tenth-Edition Unix */
  #include "local.h"
  #endif
  
diff -Nrc3pad gcc-3.2.3/libf2c/libI77/ftell_.c gcc-3.3/libf2c/libI77/ftell_.c
*** gcc-3.2.3/libf2c/libI77/ftell_.c	2001-07-10 20:39:40.000000000 +0000
--- gcc-3.3/libf2c/libI77/ftell_.c	2002-06-01 12:38:30.000000000 +0000
***************
*** 2,47 ****
  #include "f2c.h"
  #include "fio.h"
  
!  static FILE *
! #ifdef KR_headers
! unit_chk(Unit, who) integer Unit; char *who;
! #else
! unit_chk(integer Unit, char *who)
! #endif
  {
! 	if (Unit >= MXUNIT || Unit < 0)
! 		f__fatal(101, who);
! 	return f__units[Unit].ufd;
! 	}
  
!  integer
! #ifdef KR_headers
! G77_ftell_0 (Unit) integer *Unit;
! #else
! G77_ftell_0 (integer *Unit)
! #endif
  {
! 	FILE *f;
! 	return (f = unit_chk(*Unit, "ftell")) ? (integer) FTELL(f) : -1L;
! 	}
  
!  integer
! #ifdef KR_headers
! G77_fseek_0 (Unit, offset, xwhence) integer *Unit, *offset, *xwhence;
! #else
! G77_fseek_0 (integer *Unit, integer *offset, integer *xwhence)
! #endif
  {
! 	FILE *f;
! 	int w = (int)*xwhence;
  #ifdef SEEK_SET
! 	static int wohin[3] = { SEEK_SET, SEEK_CUR, SEEK_END };
  #endif
! 	if (w < 0 || w > 2)
! 		w = 0;
  #ifdef SEEK_SET
! 	w = wohin[w];
  #endif
! 	return	!(f = unit_chk(*Unit, "fseek"))
! 		|| FSEEK(f, (off_t) *offset, w) ? 1 : 0;
! 	}
--- 2,35 ----
  #include "f2c.h"
  #include "fio.h"
  
! static FILE *
! unit_chk (integer Unit, char *who)
  {
!   if (Unit >= MXUNIT || Unit < 0)
!     f__fatal (101, who);
!   return f__units[Unit].ufd;
! }
  
! integer
! G77_ftell_0 (integer * Unit)
  {
!   FILE *f;
!   return (f = unit_chk (*Unit, "ftell")) ? (integer) FTELL (f) : -1L;
! }
  
! integer
! G77_fseek_0 (integer * Unit, integer * offset, integer * xwhence)
  {
!   FILE *f;
!   int w = (int) *xwhence;
  #ifdef SEEK_SET
!   static int wohin[3] = { SEEK_SET, SEEK_CUR, SEEK_END };
  #endif
!   if (w < 0 || w > 2)
!     w = 0;
  #ifdef SEEK_SET
!   w = wohin[w];
  #endif
!   return !(f = unit_chk (*Unit, "fseek"))
!     || FSEEK (f, (off_t) * offset, w) ? 1 : 0;
! }
diff -Nrc3pad gcc-3.2.3/libf2c/libI77/iio.c gcc-3.3/libf2c/libI77/iio.c
*** gcc-3.2.3/libf2c/libI77/iio.c	1998-06-23 14:37:10.000000000 +0000
--- gcc-3.3/libf2c/libI77/iio.c	2003-04-11 19:29:11.000000000 +0000
*************** char *f__icend;
*** 6,154 ****
  extern icilist *f__svic;
  int f__icnum;
  extern int f__hiwater;
! z_getc(Void)
  {
! 	if(f__recpos++ < f__svic->icirlen) {
! 		if(f__icptr >= f__icend) err(f__svic->iciend,(EOF),"endfile");
! 		return(*(unsigned char *)f__icptr++);
! 		}
! 	return '\n';
  }
  
!  void
! #ifdef KR_headers
! z_putc(c)
! #else
! z_putc(int c)
! #endif
  {
! 	if (f__icptr < f__icend && f__recpos++ < f__svic->icirlen)
! 		*f__icptr++ = c;
  }
! z_rnew(Void)
  {
! 	f__icptr = f__svic->iciunit + (++f__icnum)*f__svic->icirlen;
! 	f__recpos = 0;
! 	f__cursor = 0;
! 	f__hiwater = 0;
! 	return 1;
  }
  
!  static int
! z_endp(Void)
  {
! 	(*f__donewrec)();
! 	return 0;
! 	}
  
! #ifdef KR_headers
! c_si(a) icilist *a;
! #else
! c_si(icilist *a)
! #endif
  {
! 	if (f__init & 2)
! 		f__fatal (131, "I/O recursion");
! 	f__init |= 2;
! 	f__elist = (cilist *)a;
! 	f__fmtbuf=a->icifmt;
! 	f__curunit = 0;
! 	f__sequential=f__formatted=1;
! 	f__external=0;
! 	if(pars_f(f__fmtbuf)<0)
! 		err(a->icierr,100,"startint");
! 	fmt_bg();
! 	f__cblank=f__cplus=f__scale=0;
! 	f__svic=a;
! 	f__icnum=f__recpos=0;
! 	f__cursor = 0;
! 	f__hiwater = 0;
! 	f__icptr = a->iciunit;
! 	f__icend = f__icptr + a->icirlen*a->icirnum;
! 	f__cf = 0;
! 	return(0);
  }
  
!  int
! iw_rev(Void)
  {
! 	if(f__workdone)
! 		z_endp();
! 	f__hiwater = f__recpos = f__cursor = 0;
! 	return(f__workdone=0);
! 	}
  
! #ifdef KR_headers
! integer s_rsfi(a) icilist *a;
! #else
! integer s_rsfi(icilist *a)
! #endif
! {	int n;
! 	if(n=c_si(a)) return(n);
! 	f__reading=1;
! 	f__doed=rd_ed;
! 	f__doned=rd_ned;
! 	f__getn=z_getc;
! 	f__dorevert = z_endp;
! 	f__donewrec = z_rnew;
! 	f__doend = z_endp;
! 	return(0);
  }
  
! z_wnew(Void)
  {
! 	if (f__recpos < f__hiwater) {
! 		f__icptr += f__hiwater - f__recpos;
! 		f__recpos = f__hiwater;
! 		}
! 	while(f__recpos++ < f__svic->icirlen)
! 		*f__icptr++ = ' ';
! 	f__recpos = 0;
! 	f__cursor = 0;
! 	f__hiwater = 0;
! 	f__icnum++;
! 	return 1;
  }
! #ifdef KR_headers
! integer s_wsfi(a) icilist *a;
! #else
! integer s_wsfi(icilist *a)
! #endif
! {	int n;
! 	if(n=c_si(a)) return(n);
! 	f__reading=0;
! 	f__doed=w_ed;
! 	f__doned=w_ned;
! 	f__putn=z_putc;
! 	f__dorevert = iw_rev;
! 	f__donewrec = z_wnew;
! 	f__doend = z_endp;
! 	return(0);
  }
! integer e_rsfi(Void)
! {	int n;
! 	f__init &= ~2;
! 	n = en_fio();
! 	f__fmtbuf = NULL;
! 	return(n);
  }
! integer e_wsfi(Void)
  {
! 	int n;
! 	f__init &= ~2;
! 	n = en_fio();
! 	f__fmtbuf = NULL;
! 	if(f__svic->icirnum != 1
! 	 && (f__icnum >  f__svic->icirnum
! 	 || (f__icnum == f__svic->icirnum && (f__recpos | f__hiwater))))
! 		err(f__svic->icierr,110,"inwrite");
! 	if (f__recpos < f__hiwater)
! 		f__recpos = f__hiwater;
! 	if (f__recpos >= f__svic->icirlen)
! 		err(f__svic->icierr,110,"recend");
! 	if (!f__recpos && f__icnum)
! 		return n;
! 	while(f__recpos++ < f__svic->icirlen)
! 		*f__icptr++ = ' ';
! 	return n;
  }
--- 6,157 ----
  extern icilist *f__svic;
  int f__icnum;
  extern int f__hiwater;
! int
! z_getc (void)
  {
!   if (f__recpos++ < f__svic->icirlen)
!     {
!       if (f__icptr >= f__icend)
! 	err (f__svic->iciend, (EOF), "endfile");
!       return (*(unsigned char *) f__icptr++);
!     }
!   return '\n';
  }
  
! void
! z_putc (int c)
  {
!   if (f__recpos++ < f__svic->icirlen && f__icptr < f__icend)
!     *f__icptr++ = c;
  }
! int
! z_rnew (void)
  {
!   f__icptr = f__svic->iciunit + (++f__icnum) * f__svic->icirlen;
!   f__recpos = 0;
!   f__cursor = 0;
!   f__hiwater = 0;
!   return 1;
  }
  
! static int
! z_endp (void)
  {
!   (*f__donewrec) ();
!   return 0;
! }
  
! int
! c_si (icilist * a)
  {
!   if (f__init & 2)
!     f__fatal (131, "I/O recursion");
!   f__init |= 2;
!   f__elist = (cilist *) a;
!   f__fmtbuf = a->icifmt;
!   f__curunit = 0;
!   f__sequential = f__formatted = 1;
!   f__external = 0;
!   if (pars_f (f__fmtbuf) < 0)
!     err (a->icierr, 100, "startint");
!   fmt_bg ();
!   f__cblank = f__cplus = f__scale = 0;
!   f__svic = a;
!   f__icnum = f__recpos = 0;
!   f__cursor = 0;
!   f__hiwater = 0;
!   f__icptr = a->iciunit;
!   f__icend = f__icptr + a->icirlen * a->icirnum;
!   f__cf = 0;
!   return (0);
  }
  
! int
! iw_rev (void)
  {
!   if (f__workdone)
!     z_endp ();
!   f__hiwater = f__recpos = f__cursor = 0;
!   return (f__workdone = 0);
! }
  
! integer
! s_rsfi (icilist * a)
! {
!   int n;
!   if ((n = c_si (a)))
!     return (n);
!   f__reading = 1;
!   f__doed = rd_ed;
!   f__doned = rd_ned;
!   f__getn = z_getc;
!   f__dorevert = z_endp;
!   f__donewrec = z_rnew;
!   f__doend = z_endp;
!   return (0);
  }
  
! int
! z_wnew (void)
  {
!   if (f__recpos < f__hiwater)
!     {
!       f__icptr += f__hiwater - f__recpos;
!       f__recpos = f__hiwater;
!     }
!   while (f__recpos++ < f__svic->icirlen)
!     *f__icptr++ = ' ';
!   f__recpos = 0;
!   f__cursor = 0;
!   f__hiwater = 0;
!   f__icnum++;
!   return 1;
  }
! 
! integer
! s_wsfi (icilist * a)
! {
!   int n;
!   if ((n = c_si (a)))
!     return (n);
!   f__reading = 0;
!   f__doed = w_ed;
!   f__doned = w_ned;
!   f__putn = z_putc;
!   f__dorevert = iw_rev;
!   f__donewrec = z_wnew;
!   f__doend = z_endp;
!   return (0);
  }
! 
! integer
! e_rsfi (void)
! {
!   int n;
!   f__init &= ~2;
!   n = en_fio ();
!   f__fmtbuf = NULL;
!   return (n);
  }
! 
! integer
! e_wsfi (void)
  {
!   int n;
!   f__init &= ~2;
!   n = en_fio ();
!   f__fmtbuf = NULL;
!   if (f__svic->icirnum != 1
!       && (f__icnum > f__svic->icirnum
! 	  || (f__icnum == f__svic->icirnum && (f__recpos | f__hiwater))))
!     err (f__svic->icierr, 110, "inwrite");
!   if (f__recpos < f__hiwater)
!     f__recpos = f__hiwater;
!   if (f__recpos >= f__svic->icirlen)
!     err (f__svic->icierr, 110, "recend");
!   if (!f__recpos && f__icnum)
!     return n;
!   while (f__recpos++ < f__svic->icirlen)
!     *f__icptr++ = ' ';
!   return n;
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libI77/ilnw.c gcc-3.3/libf2c/libI77/ilnw.c
*** gcc-3.2.3/libf2c/libI77/ilnw.c	2001-05-16 18:59:29.000000000 +0000
--- gcc-3.3/libf2c/libI77/ilnw.c	2002-06-01 12:38:30.000000000 +0000
*************** extern char *f__icptr;
*** 6,83 ****
  extern char *f__icend;
  extern icilist *f__svic;
  extern int f__icnum;
! #ifdef KR_headers
! extern void z_putc();
! #else
! extern void z_putc(int);
! #endif
  
!  static int
! z_wSL(Void)
  {
! 	while(f__recpos < f__svic->icirlen)
! 		z_putc(' ');
! 	return z_rnew();
! 	}
  
!  static void
! #ifdef KR_headers
! c_liw(a) icilist *a;
! #else
! c_liw(icilist *a)
! #endif
  {
! 	f__reading = 0;
! 	f__external = 0;
! 	f__formatted = 1;
! 	f__putn = z_putc;
! 	L_len = a->icirlen;
! 	f__donewrec = z_wSL;
! 	f__svic = a;
! 	f__icnum = f__recpos = 0;
! 	f__cursor = 0;
! 	f__cf = 0;
! 	f__curunit = 0;
! 	f__icptr = a->iciunit;
! 	f__icend = f__icptr + a->icirlen*a->icirnum;
! 	f__elist = (cilist *)a;
! 	}
  
!  integer
! #ifdef KR_headers
! s_wsni(a) icilist *a;
! #else
! s_wsni(icilist *a)
! #endif
  {
! 	cilist ca;
  
! 	if(f__init != 1) f_init();
! 	f__init = 3;
! 	c_liw(a);
! 	ca.cifmt = a->icifmt;
! 	x_wsne(&ca);
! 	z_wSL();
! 	return 0;
! 	}
  
!  integer
! #ifdef KR_headers
! s_wsli(a) icilist *a;
! #else
! s_wsli(icilist *a)
! #endif
  {
! 	if(f__init != 1) f_init();
! 	f__init = 3;
! 	f__lioproc = l_write;
! 	c_liw(a);
! 	return(0);
! 	}
  
! integer e_wsli(Void)
  {
! 	f__init = 1;
! 	z_wSL();
! 	return(0);
! 	}
--- 6,70 ----
  extern char *f__icend;
  extern icilist *f__svic;
  extern int f__icnum;
! extern void z_putc (int);
  
! static int
! z_wSL (void)
  {
!   while (f__recpos < f__svic->icirlen)
!     z_putc (' ');
!   return z_rnew ();
! }
  
! static void
! c_liw (icilist * a)
  {
!   f__reading = 0;
!   f__external = 0;
!   f__formatted = 1;
!   f__putn = z_putc;
!   L_len = a->icirlen;
!   f__donewrec = z_wSL;
!   f__svic = a;
!   f__icnum = f__recpos = 0;
!   f__cursor = 0;
!   f__cf = 0;
!   f__curunit = 0;
!   f__icptr = a->iciunit;
!   f__icend = f__icptr + a->icirlen * a->icirnum;
!   f__elist = (cilist *) a;
! }
  
! integer
! s_wsni (icilist * a)
  {
!   cilist ca;
  
!   if (f__init != 1)
!     f_init ();
!   f__init = 3;
!   c_liw (a);
!   ca.cifmt = a->icifmt;
!   x_wsne (&ca);
!   z_wSL ();
!   return 0;
! }
  
! integer
! s_wsli (icilist * a)
  {
!   if (f__init != 1)
!     f_init ();
!   f__init = 3;
!   f__lioproc = l_write;
!   c_liw (a);
!   return (0);
! }
  
! integer
! e_wsli (void)
  {
!   f__init = 1;
!   z_wSL ();
!   return (0);
! }
diff -Nrc3pad gcc-3.2.3/libf2c/libI77/inquire.c gcc-3.3/libf2c/libI77/inquire.c
*** gcc-3.2.3/libf2c/libI77/inquire.c	2001-07-06 12:09:39.000000000 +0000
--- gcc-3.3/libf2c/libI77/inquire.c	2002-06-04 02:24:25.000000000 +0000
***************
*** 2,109 ****
  #include "f2c.h"
  #include "fio.h"
  #include <string.h>
- #ifdef KR_headers
- integer f_inqu(a) inlist *a;
- #else
  #if defined (MSDOS) && !defined (GO32)
  #undef abs
  #undef min
  #undef max
  #include "io.h"
  #endif
! integer f_inqu(inlist *a)
! #endif
! {	flag byfile;
! 	int i, n;
! 	unit *p;
! 	char buf[256];
! 	long x;
! 	if (f__init & 2)
! 		f__fatal (131, "I/O recursion");
! 	if(a->infile!=NULL)
! 	{	byfile=1;
! 		g_char(a->infile,a->infilen,buf);
  #ifdef NON_UNIX_STDIO
! 		x = access(buf,0) ? -1 : 0;
! 		for(i=0,p=NULL;i<MXUNIT;i++)
! 			if(f__units[i].ufd != NULL
! 			 && f__units[i].ufnm != NULL
! 			 && !strcmp(f__units[i].ufnm,buf)) {
! 				p = &f__units[i];
! 				break;
! 				}
  #else
! 		x=f__inode(buf, &n);
! 		for(i=0,p=NULL;i<MXUNIT;i++)
! 			if(f__units[i].uinode==x
! 			&& f__units[i].ufd!=NULL
! 			&& f__units[i].udev == n) {
! 				p = &f__units[i];
! 				break;
! 				}
  #endif
  	}
! 	else
  	{
! 		byfile=0;
! 		if(a->inunit<MXUNIT && a->inunit>=0)
! 		{
! 			p= &f__units[a->inunit];
! 		}
! 		else
! 		{
! 			p=NULL;
! 		}
  	}
! 	if(a->inex!=NULL)
! 		if(byfile && x != -1 || !byfile && p!=NULL)
! 			*a->inex=1;
! 		else *a->inex=0;
! 	if(a->inopen!=NULL)
! 		if(byfile) *a->inopen=(p!=NULL);
! 		else *a->inopen=(p!=NULL && p->ufd!=NULL);
! 	if(a->innum!=NULL) *a->innum= p-f__units;
! 	if(a->innamed!=NULL)
! 		if(byfile || p!=NULL && p->ufnm!=NULL)
! 			*a->innamed=1;
! 		else	*a->innamed=0;
! 	if(a->inname!=NULL)
! 		if(byfile)
! 			b_char(buf,a->inname,a->innamlen);
! 		else if(p!=NULL && p->ufnm!=NULL)
! 			b_char(p->ufnm,a->inname,a->innamlen);
! 	if(a->inacc!=NULL && p!=NULL && p->ufd!=NULL)
! 		if(p->url)
! 			b_char("DIRECT",a->inacc,a->inacclen);
! 		else	b_char("SEQUENTIAL",a->inacc,a->inacclen);
! 	if(a->inseq!=NULL)
! 		if(p!=NULL && p->url)
! 			b_char("NO",a->inseq,a->inseqlen);
! 		else	b_char("YES",a->inseq,a->inseqlen);
! 	if(a->indir!=NULL)
! 		if(p==NULL || p->url)
! 			b_char("YES",a->indir,a->indirlen);
! 		else	b_char("NO",a->indir,a->indirlen);
! 	if(a->infmt!=NULL)
! 		if(p!=NULL && p->ufmt==0)
! 			b_char("UNFORMATTED",a->infmt,a->infmtlen);
! 		else	b_char("FORMATTED",a->infmt,a->infmtlen);
! 	if(a->inform!=NULL)
! 		if(p!=NULL && p->ufmt==0)
! 		b_char("NO",a->inform,a->informlen);
! 		else b_char("YES",a->inform,a->informlen);
! 	if(a->inunf)
! 		if(p!=NULL && p->ufmt==0)
! 			b_char("YES",a->inunf,a->inunflen);
! 		else if (p!=NULL) b_char("NO",a->inunf,a->inunflen);
! 		else b_char("UNKNOWN",a->inunf,a->inunflen);
! 	if(a->inrecl!=NULL && p!=NULL)
! 		*a->inrecl=p->url;
! 	if(a->innrec!=NULL && p!=NULL && p->url>0)
! 		*a->innrec=FTELL(p->ufd)/p->url+1;
! 	if(a->inblank && p!=NULL && p->ufmt)
! 		if(p->ublnk)
! 			b_char("ZERO",a->inblank,a->inblanklen);
! 		else	b_char("NULL",a->inblank,a->inblanklen);
! 	return(0);
  }
--- 2,143 ----
  #include "f2c.h"
  #include "fio.h"
  #include <string.h>
  #if defined (MSDOS) && !defined (GO32)
  #undef abs
  #undef min
  #undef max
  #include "io.h"
  #endif
! integer
! f_inqu (inlist * a)
! {
!   flag byfile;
!   int i, n;
!   unit *p;
!   char buf[256];
!   long x;
!   if (f__init & 2)
!     f__fatal (131, "I/O recursion");
!   if (a->infile != NULL)
!     {
!       byfile = 1;
!       g_char (a->infile, a->infilen, buf);
  #ifdef NON_UNIX_STDIO
!       x = access (buf, 0) ? -1 : 0;
!       for (i = 0, p = NULL; i < MXUNIT; i++)
! 	if (f__units[i].ufd != NULL
! 	    && f__units[i].ufnm != NULL && !strcmp (f__units[i].ufnm, buf))
! 	  {
! 	    p = &f__units[i];
! 	    break;
! 	  }
  #else
!       x = f__inode (buf, &n);
!       for (i = 0, p = NULL; i < MXUNIT; i++)
! 	if (f__units[i].uinode == x
! 	    && f__units[i].ufd != NULL && f__units[i].udev == n)
! 	  {
! 	    p = &f__units[i];
! 	    break;
! 	  }
  #endif
+     }
+   else
+     {
+       byfile = 0;
+       if (a->inunit < MXUNIT && a->inunit >= 0)
+ 	{
+ 	  p = &f__units[a->inunit];
  	}
!       else
  	{
! 	  p = NULL;
  	}
!     }
!   if (a->inex != NULL)
!     {
!       if ((byfile && x != -1) || (!byfile && p != NULL))
! 	*a->inex = 1;
!       else
! 	*a->inex = 0;
!     }
!   if (a->inopen != NULL)
!     {
!       if (byfile)
! 	*a->inopen = (p != NULL);
!       else
! 	*a->inopen = (p != NULL && p->ufd != NULL);
!     }
!   if (a->innum != NULL)
!     *a->innum = p - f__units;
!   if (a->innamed != NULL)
!     {
!       if (byfile || (p != NULL && p->ufnm != NULL))
! 	*a->innamed = 1;
!       else
! 	*a->innamed = 0;
!     }
!   if (a->inname != NULL)
!     {
!       if (byfile)
! 	b_char (buf, a->inname, a->innamlen);
!       else if (p != NULL && p->ufnm != NULL)
! 	b_char (p->ufnm, a->inname, a->innamlen);
!     }
!   if (a->inacc != NULL && p != NULL && p->ufd != NULL)
!     {
!       if (p->url)
! 	b_char ("DIRECT", a->inacc, a->inacclen);
!       else
! 	b_char ("SEQUENTIAL", a->inacc, a->inacclen);
!     }
!   if (a->inseq != NULL)
!     {
!       if (p != NULL && p->url)
! 	b_char ("NO", a->inseq, a->inseqlen);
!       else
! 	b_char ("YES", a->inseq, a->inseqlen);
!     }
!   if (a->indir != NULL)
!     {
!       if (p == NULL || p->url)
! 	b_char ("YES", a->indir, a->indirlen);
!       else
! 	b_char ("NO", a->indir, a->indirlen);
!     }
!   if (a->infmt != NULL)
!     {
!       if (p != NULL && p->ufmt == 0)
! 	b_char ("UNFORMATTED", a->infmt, a->infmtlen);
!       else
! 	b_char ("FORMATTED", a->infmt, a->infmtlen);
!     }
!   if (a->inform != NULL)
!     {
!       if (p != NULL && p->ufmt == 0)
! 	b_char ("NO", a->inform, a->informlen);
!       else
! 	b_char ("YES", a->inform, a->informlen);
!     }
!   if (a->inunf)
!     {
!       if (p != NULL && p->ufmt == 0)
! 	b_char ("YES", a->inunf, a->inunflen);
!       else if (p != NULL)
! 	b_char ("NO", a->inunf, a->inunflen);
!       else
! 	b_char ("UNKNOWN", a->inunf, a->inunflen);
!     }
!   if (a->inrecl != NULL && p != NULL)
!     *a->inrecl = p->url;
!   if (a->innrec != NULL && p != NULL && p->url > 0)
!     *a->innrec = FTELL (p->ufd) / p->url + 1;
!   if (a->inblank && p != NULL && p->ufmt)
!     {
!       if (p->ublnk)
! 	b_char ("ZERO", a->inblank, a->inblanklen);
!       else
! 	b_char ("NULL", a->inblank, a->inblanklen);
!     }
!   return (0);
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libI77/lio.h gcc-3.3/libf2c/libI77/lio.h
*** gcc-3.2.3/libf2c/libI77/lio.h	1999-09-04 15:09:18.000000000 +0000
--- gcc-3.3/libf2c/libI77/lio.h	2002-06-01 12:38:30.000000000 +0000
***************
*** 43,74 ****
  
  typedef union
  {
! 	char	flchar;
! 	short	flshort;
! 	ftnint	flint;
  #ifdef Allow_TYQUAD
! 	longint fllongint;
  #endif
! 	real	flreal;
! 	doublereal	fldouble;
! } flex;
  extern int f__scale;
! #ifdef KR_headers
! extern int (*f__lioproc)(), (*l_getc)(), (*l_ungetc)();
! extern int l_read(), l_write();
! #else
! #ifdef __cplusplus
! extern "C" {
! #endif
! extern int (*f__lioproc)(ftnint*, char*, ftnlen, ftnint);
! extern int l_write(ftnint*, char*, ftnlen, ftnint);
! extern void x_wsne(cilist*);
! extern int c_le(cilist*), (*l_getc)(void), (*l_ungetc)(int,FILE*);
! extern int l_read(ftnint*,char*,ftnlen,ftnint);
! extern integer e_rsle(void), e_wsle(void), s_wsne(cilist*);
! extern int z_rnew(void);
! #ifdef __cplusplus
! 	}
! #endif
! #endif
  extern ftnint L_len;
--- 43,64 ----
  
  typedef union
  {
!   signed char flchar;
!   short flshort;
!   ftnint flint;
  #ifdef Allow_TYQUAD
!   longint fllongint;
  #endif
!   real flreal;
!   doublereal fldouble;
! }
! flex;
  extern int f__scale;
! extern int (*f__lioproc) (ftnint *, char *, ftnlen, ftnint);
! extern int l_write (ftnint *, char *, ftnlen, ftnint);
! extern void x_wsne (cilist *);
! extern int c_le (cilist *), (*l_getc) (void), (*l_ungetc) (int, FILE *);
! extern int l_read (ftnint *, char *, ftnlen, ftnint);
! extern integer e_rsle (void), e_wsle (void), s_wsne (cilist *);
! extern int z_rnew (void);
  extern ftnint L_len;
diff -Nrc3pad gcc-3.2.3/libf2c/libI77/lread.c gcc-3.3/libf2c/libI77/lread.c
*** gcc-3.2.3/libf2c/libI77/lread.c	2001-05-16 18:59:29.000000000 +0000
--- gcc-3.3/libf2c/libI77/lread.c	2002-06-04 02:25:47.000000000 +0000
*************** extern int f__fmtlen;
*** 13,40 ****
  
  #ifdef Allow_TYQUAD
  static longint f__llx;
- static int quad_read;
  #endif
  
- #ifdef KR_headers
- extern double atof();
- extern char *malloc(), *realloc();
- int (*f__lioproc)(), (*l_getc)(), (*l_ungetc)();
- #else
  #undef abs
  #undef min
  #undef max
  #include <stdlib.h>
- #endif
  
  #include "fmt.h"
  #include "lio.h"
  #include "fp.h"
  
! #ifndef KR_headers
! int (*f__lioproc)(ftnint*, char*, ftnlen, ftnint), (*l_getc)(void),
! 	(*l_ungetc)(int,FILE*);
! #endif
  
  int l_eof;
  
--- 13,31 ----
  
  #ifdef Allow_TYQUAD
  static longint f__llx;
  #endif
  
  #undef abs
  #undef min
  #undef max
  #include <stdlib.h>
  
  #include "fmt.h"
  #include "lio.h"
  #include "fp.h"
  
! int (*f__lioproc) (ftnint *, char *, ftnlen, ftnint), (*l_getc) (void),
!   (*l_ungetc) (int, FILE *);
  
  int l_eof;
  
*************** int l_eof;
*** 50,798 ****
  #define EX 8
  #define SG 16
  #define WH 32
! char f__ltab[128+1] = {	/* offset one for EOF */
! 	0,
! 	0,0,AX,0,0,0,0,0,0,WH|B,SX|WH,0,0,0,0,0,
! 	0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
! 	SX|B|WH,0,AX,0,0,0,0,AX,0,0,0,SG,SX,SG,0,SX,
! 	0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
! 	0,0,0,0,EX,EX,0,0,0,0,0,0,0,0,0,0,
! 	0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
! 	AX,0,0,0,EX,EX,0,0,0,0,0,0,0,0,0,0,
! 	0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
  };
  
  #ifdef ungetc
!  static int
! #ifdef KR_headers
! un_getc(x,f__cf) int x; FILE *f__cf;
! #else
! un_getc(int x, FILE *f__cf)
! #endif
! { return ungetc(x,f__cf); }
  #else
  #define un_getc ungetc
! #ifdef KR_headers
!  extern int ungetc();
! #else
! extern int ungetc(int, FILE*);	/* for systems with a buggy stdio.h */
! #endif
  #endif
  
! t_getc(Void)
! {	int ch;
! 	if(f__curunit->uend) return(EOF);
! 	if((ch=getc(f__cf))!=EOF) return(ch);
! 	if(feof(f__cf))
! 		f__curunit->uend = l_eof = 1;
! 	return(EOF);
  }
! integer e_rsle(Void)
  {
! 	int ch;
! 	f__init = 1;
! 	if(f__curunit->uend) return(0);
! 	while((ch=t_getc())!='\n')
! 		if (ch == EOF) {
! 			if(feof(f__cf))
! 				f__curunit->uend = l_eof = 1;
! 			return EOF;
! 			}
! 	return(0);
  }
  
  flag f__lquit;
! int f__lcount,f__ltype,nml_read;
  char *f__lchar;
! double f__lx,f__ly;
! #define ERR(x) if(n=(x)) {f__init &= ~2; return(n);}
  #define GETC(x) (x=(*l_getc)())
  #define Ungetc(x,y) (*l_ungetc)(x,y)
  
!  static int
! #ifdef KR_headers
! l_R(poststar, reqint) int poststar, reqint;
! #else
! l_R(int poststar, int reqint)
! #endif
  {
! 	char s[FMAX+EXPMAXDIGS+4];
! 	register int ch;
! 	register char *sp, *spe, *sp1;
! 	long e, exp;
! 	int havenum, havestar, se;
  
! 	if (!poststar) {
! 		if (f__lcount > 0)
! 			return(0);
! 		f__lcount = 1;
! 		}
  #ifdef Allow_TYQUAD
! 	f__llx = 0;
  #endif
! 	f__ltype = 0;
! 	exp = 0;
! 	havestar = 0;
  retry:
! 	sp1 = sp = s;
! 	spe = sp + FMAX;
! 	havenum = 0;
  
! 	switch(GETC(ch)) {
! 		case '-': *sp++ = ch; sp1++; spe++;
! 		case '+':
! 			GETC(ch);
! 		}
! 	while(ch == '0') {
! 		++havenum;
! 		GETC(ch);
! 		}
! 	while(isdigit(ch)) {
! 		if (sp < spe) *sp++ = ch;
! 		else ++exp;
! 		GETC(ch);
! 		}
! 	if (ch == '*' && !poststar) {
! 		if (sp == sp1 || exp || *s == '-') {
! 			errfl(f__elist->cierr,112,"bad repetition count");
! 			}
! 		poststar = havestar = 1;
! 		*sp = 0;
! 		f__lcount = atoi(s);
! 		goto retry;
! 		}
! 	if (ch == '.') {
  #ifndef ALLOW_FLOAT_IN_INTEGER_LIST_INPUT
! 		if (reqint)
! 			errfl(f__elist->cierr,115,"invalid integer");
  #endif
! 		GETC(ch);
! 		if (sp == sp1)
! 			while(ch == '0') {
! 				++havenum;
! 				--exp;
! 				GETC(ch);
! 				}
! 		while(isdigit(ch)) {
! 			if (sp < spe)
! 				{ *sp++ = ch; --exp; }
! 			GETC(ch);
! 			}
! 		}
! 	havenum += sp - sp1;
! 	se = 0;
! 	if (issign(ch))
! 		goto signonly;
! 	if (havenum && isexp(ch)) {
  #ifndef ALLOW_FLOAT_IN_INTEGER_LIST_INPUT
! 		if (reqint)
! 			errfl(f__elist->cierr,115,"invalid integer");
  #endif
! 		GETC(ch);
! 		if (issign(ch)) {
! signonly:
! 			if (ch == '-') se = 1;
! 			GETC(ch);
! 			}
! 		if (!isdigit(ch)) {
! bad:
! 			errfl(f__elist->cierr,112,"exponent field");
! 			}
  
! 		e = ch - '0';
! 		while(isdigit(GETC(ch))) {
! 			e = 10*e + ch - '0';
! 			if (e > EXPMAX)
! 				goto bad;
! 			}
! 		if (se)
! 			exp -= e;
! 		else
! 			exp += e;
! 		}
! 	(void) Ungetc(ch, f__cf);
! 	if (sp > sp1) {
! 		++havenum;
! 		while(*--sp == '0')
! 			++exp;
! 		if (exp)
! 			sprintf(sp+1, "e%ld", exp);
! 		else
! 			sp[1] = 0;
! 		f__lx = atof(s);
  #ifdef Allow_TYQUAD
! 		if (reqint&2 && (se = sp - sp1 + exp) > 14 && se < 20) {
! 			/* Assuming 64-bit longint and 32-bit long. */
! 			if (exp < 0)
! 				sp += exp;
! 			if (sp1 <= sp) {
! 				f__llx = *sp1 - '0';
! 				while(++sp1 <= sp)
! 					f__llx = 10*f__llx + (*sp1 - '0');
! 				}
! 			while(--exp >= 0)
! 				f__llx *= 10;
! 			if (*s == '-')
! 				f__llx = -f__llx;
! 			}
! #endif
! 		}
! 	else
! 		f__lx = 0.;
! 	if (havenum)
! 		f__ltype = TYLONG;
! 	else
! 		switch(ch) {
! 			case ',':
! 			case '/':
! 				break;
! 			default:
! 				if (havestar && ( ch == ' '
! 						||ch == '\t'
! 						||ch == '\n'))
! 					break;
! 				if (nml_read > 1) {
! 					f__lquit = 2;
! 					return 0;
! 					}
! 				errfl(f__elist->cierr,112,"invalid number");
! 			}
! 	return 0;
  	}
- 
-  static int
- #ifdef KR_headers
- rd_count(ch) register int ch;
- #else
- rd_count(register int ch)
  #endif
  {
! 	if (ch < '0' || ch > '9')
! 		return 1;
! 	f__lcount = ch - '0';
! 	while(GETC(ch) >= '0' && ch <= '9')
! 		f__lcount = 10*f__lcount + ch - '0';
! 	Ungetc(ch,f__cf);
! 	return f__lcount <= 0;
! 	}
  
!  static int
! l_C(Void)
! {	int ch, nml_save;
! 	double lz;
! 	if(f__lcount>0) return(0);
! 	f__ltype=0;
! 	GETC(ch);
! 	if(ch!='(')
  	{
! 		if (nml_read > 1 && (ch < '0' || ch > '9')) {
! 			Ungetc(ch,f__cf);
! 			f__lquit = 2;
! 			return 0;
! 			}
! 		if (rd_count(ch))
! 			if(!f__cf || !feof(f__cf))
! 				errfl(f__elist->cierr,112,"complex format");
! 			else
! 				err(f__elist->cierr,(EOF),"lread");
! 		if(GETC(ch)!='*')
! 		{
! 			if(!f__cf || !feof(f__cf))
! 				errfl(f__elist->cierr,112,"no star");
! 			else
! 				err(f__elist->cierr,(EOF),"lread");
! 		}
! 		if(GETC(ch)!='(')
! 		{	Ungetc(ch,f__cf);
! 			return(0);
! 		}
  	}
! 	else
! 		f__lcount = 1;
! 	while(iswhit(GETC(ch)));
! 	Ungetc(ch,f__cf);
! 	nml_save = nml_read;
! 	nml_read = 0;
! 	if (ch = l_R(1,0))
! 		return ch;
! 	if (!f__ltype)
! 		errfl(f__elist->cierr,112,"no real part");
! 	lz = f__lx;
! 	while(iswhit(GETC(ch)));
! 	if(ch!=',')
! 	{	(void) Ungetc(ch,f__cf);
! 		errfl(f__elist->cierr,112,"no comma");
  	}
! 	while(iswhit(GETC(ch)));
! 	(void) Ungetc(ch,f__cf);
! 	if (ch = l_R(1,0))
! 		return ch;
! 	if (!f__ltype)
! 		errfl(f__elist->cierr,112,"no imaginary part");
! 	while(iswhit(GETC(ch)));
! 	if(ch!=')') errfl(f__elist->cierr,112,"no )");
! 	f__ly = f__lx;
! 	f__lx = lz;
  #ifdef Allow_TYQUAD
! 	f__llx = 0;
  #endif
! 	nml_read = nml_save;
! 	return(0);
  }
  
!  static char nmLbuf[256], *nmL_next;
!  static int (*nmL_getc_save)(Void);
! #ifdef KR_headers
!  static int (*nmL_ungetc_save)(/* int, FILE* */);
! #else
!  static int (*nmL_ungetc_save)(int, FILE*);
! #endif
  
!  static int
! nmL_getc(Void)
  {
! 	int rv;
! 	if (rv = *nmL_next++)
! 		return rv;
! 	l_getc = nmL_getc_save;
! 	l_ungetc = nmL_ungetc_save;
! 	return (*l_getc)();
! 	}
  
!  static int
! #ifdef KR_headers
! nmL_ungetc(x, f) int x; FILE *f;
! #else
! nmL_ungetc(int x, FILE *f)
! #endif
  {
! 	f = f;	/* banish non-use warning */
! 	return *--nmL_next = x;
! 	}
  
!  static int
! #ifdef KR_headers
! Lfinish(ch, dot, rvp) int ch, dot, *rvp;
! #else
! Lfinish(int ch, int dot, int *rvp)
! #endif
  {
! 	char *s, *se;
! 	static char what[] = "namelist input";
  
! 	s = nmLbuf + 2;
! 	se = nmLbuf + sizeof(nmLbuf) - 1;
! 	*s++ = ch;
! 	while(!issep(GETC(ch)) && ch!=EOF) {
! 		if (s >= se) {
!  nmLbuf_ovfl:
! 			return *rvp = err__fl(f__elist->cierr,131,what);
! 			}
! 		*s++ = ch;
! 		if (ch != '=')
! 			continue;
! 		if (dot)
! 			return *rvp = err__fl(f__elist->cierr,112,what);
!  got_eq:
! 		*s = 0;
! 		nmL_getc_save = l_getc;
! 		l_getc = nmL_getc;
! 		nmL_ungetc_save = l_ungetc;
! 		l_ungetc = nmL_ungetc;
! 		nmLbuf[1] = *(nmL_next = nmLbuf) = ',';
! 		*rvp = f__lcount = 0;
! 		return 1;
! 		}
! 	if (dot)
! 		goto done;
! 	for(;;) {
! 		if (s >= se)
! 			goto nmLbuf_ovfl;
! 		*s++ = ch;
! 		if (!isblnk(ch))
! 			break;
! 		if (GETC(ch) == EOF)
! 			goto done;
! 		}
! 	if (ch == '=')
! 		goto got_eq;
!  done:
! 	Ungetc(ch, f__cf);
! 	return 0;
  	}
  
!  static int
! l_L(Void)
  {
! 	int ch, rv, sawdot;
! 	if(f__lcount>0)
! 		return(0);
! 	f__lcount = 1;
! 	f__ltype=0;
! 	GETC(ch);
! 	if(isdigit(ch))
  	{
! 		rd_count(ch);
! 		if(GETC(ch)!='*')
! 			if(!f__cf || !feof(f__cf))
! 				errfl(f__elist->cierr,112,"no star");
! 			else
! 				err(f__elist->cierr,(EOF),"lread");
! 		GETC(ch);
  	}
! 	sawdot = 0;
! 	if(ch == '.') {
! 		sawdot = 1;
! 		GETC(ch);
! 		}
! 	switch(ch)
  	{
! 	case 't':
! 	case 'T':
! 		if (nml_read && Lfinish(ch, sawdot, &rv))
! 			return rv;
! 		f__lx=1;
! 		break;
! 	case 'f':
! 	case 'F':
! 		if (nml_read && Lfinish(ch, sawdot, &rv))
! 			return rv;
! 		f__lx=0;
! 		break;
! 	default:
! 		if(isblnk(ch) || issep(ch) || ch==EOF)
! 		{	(void) Ungetc(ch,f__cf);
! 			return(0);
! 		}
! 		if (nml_read > 1) {
! 			Ungetc(ch,f__cf);
! 			f__lquit = 2;
! 			return 0;
! 			}
! 		errfl(f__elist->cierr,112,"logical");
  	}
! 	f__ltype=TYLONG;
! 	while(!issep(GETC(ch)) && ch!=EOF);
! 	(void) Ungetc(ch, f__cf);
! 	return(0);
  }
  
  #define BUFSIZE	128
  
!  static int
! l_CHAR(Void)
! {	int ch,size,i;
! 	static char rafail[] = "realloc failure";
! 	char quote,*p;
! 	if(f__lcount>0) return(0);
! 	f__ltype=0;
! 	if(f__lchar!=NULL) free(f__lchar);
! 	size=BUFSIZE;
! 	p=f__lchar = (char *)malloc((unsigned int)size);
! 	if(f__lchar == NULL)
! 		errfl(f__elist->cierr,113,"no space");
  
! 	GETC(ch);
! 	if(isdigit(ch)) {
! 		/* allow Fortran 8x-style unquoted string...	*/
! 		/* either find a repetition count or the string	*/
! 		f__lcount = ch - '0';
! 		*p++ = ch;
! 		for(i = 1;;) {
! 			switch(GETC(ch)) {
! 				case '*':
! 					if (f__lcount == 0) {
! 						f__lcount = 1;
! #ifndef F8X_NML_ELIDE_QUOTES
! 						if (nml_read)
! 							goto no_quote;
! #endif
! 						goto noquote;
! 						}
! 					p = f__lchar;
! 					goto have_lcount;
! 				case ',':
! 				case ' ':
! 				case '\t':
! 				case '\n':
! 				case '/':
! 					Ungetc(ch,f__cf);
! 					/* no break */
! 				case EOF:
! 					f__lcount = 1;
! 					f__ltype = TYCHAR;
! 					return *p = 0;
! 				}
! 			if (!isdigit(ch)) {
! 				f__lcount = 1;
  #ifndef F8X_NML_ELIDE_QUOTES
! 				if (nml_read) {
!  no_quote:
! 					errfl(f__elist->cierr,112,
! 						"undelimited character string");
! 					}
  #endif
! 				goto noquote;
! 				}
! 			*p++ = ch;
! 			f__lcount = 10*f__lcount + ch - '0';
! 			if (++i == size) {
! 				f__lchar = (char *)realloc(f__lchar,
! 					(unsigned int)(size += BUFSIZE));
! 				if(f__lchar == NULL)
! 					errfl(f__elist->cierr,113,rafail);
! 				p = f__lchar + i;
! 				}
! 			}
! 		}
! 	else	(void) Ungetc(ch,f__cf);
!  have_lcount:
! 	if(GETC(ch)=='\'' || ch=='"') quote=ch;
! 	else if(isblnk(ch) || (issep(ch) && ch != '\n') || ch==EOF) {
! 		Ungetc(ch,f__cf);
! 		return 0;
  		}
  #ifndef F8X_NML_ELIDE_QUOTES
! 	else if (nml_read > 1) {
! 		Ungetc(ch,f__cf);
! 		f__lquit = 2;
! 		return 0;
! 		}
! #endif
! 	else {
! 		/* Fortran 8x-style unquoted string */
! 		*p++ = ch;
! 		for(i = 1;;) {
! 			switch(GETC(ch)) {
! 				case ',':
! 				case ' ':
! 				case '\t':
! 				case '\n':
! 				case '/':
! 					Ungetc(ch,f__cf);
! 					/* no break */
! 				case EOF:
! 					f__ltype = TYCHAR;
! 					return *p = 0;
! 				}
!  noquote:
! 			*p++ = ch;
! 			if (++i == size) {
! 				f__lchar = (char *)realloc(f__lchar,
! 					(unsigned int)(size += BUFSIZE));
! 				if(f__lchar == NULL)
! 					errfl(f__elist->cierr,113,rafail);
! 				p = f__lchar + i;
! 				}
! 			}
! 		}
! 	f__ltype=TYCHAR;
! 	for(i=0;;)
! 	{	while(GETC(ch)!=quote && ch!='\n'
! 			&& ch!=EOF && ++i<size) *p++ = ch;
! 		if(i==size)
  		{
! 		newone:
! 			f__lchar= (char *)realloc(f__lchar,
! 					(unsigned int)(size += BUFSIZE));
! 			if(f__lchar == NULL)
! 				errfl(f__elist->cierr,113,rafail);
! 			p=f__lchar+i-1;
! 			*p++ = ch;
! 		}
! 		else if(ch==EOF) return(EOF);
! 		else if(ch=='\n')
! 		{	if(*(p-1) != '\\') continue;
! 			i--;
! 			p--;
! 			if(++i<size) *p++ = ch;
! 			else goto newone;
! 		}
! 		else if(GETC(ch)==quote)
! 		{	if(++i<size) *p++ = ch;
! 			else goto newone;
! 		}
! 		else
! 		{	(void) Ungetc(ch,f__cf);
! 			*p = 0;
! 			return(0);
  		}
  	}
! }
! #ifdef KR_headers
! c_le(a) cilist *a;
! #else
! c_le(cilist *a)
  #endif
  {
! 	if(f__init != 1) f_init();
! 	f__init = 3;
! 	f__fmtbuf="list io";
! 	f__curunit = &f__units[a->ciunit];
! 	f__fmtlen=7;
! 	if(a->ciunit>=MXUNIT || a->ciunit<0)
! 		err(a->cierr,101,"stler");
! 	f__scale=f__recpos=0;
! 	f__elist=a;
! 	if(f__curunit->ufd==NULL && fk_open(SEQ,FMT,a->ciunit))
! 		err(a->cierr,102,"lio");
! 	f__cf=f__curunit->ufd;
! 	if(!f__curunit->ufmt) err(a->cierr,103,"lio");
! 	return(0);
  }
! #ifdef KR_headers
! l_read(number,ptr,len,type) ftnint *number,type; char *ptr; ftnlen len;
! #else
! l_read(ftnint *number, char *ptr, ftnlen len, ftnint type)
! #endif
  {
  #define Ptr ((flex *)ptr)
! 	int i,n,ch;
! 	doublereal *yy;
! 	real *xx;
! 	for(i=0;i<*number;i++)
  	{
! 		if(f__lquit) return(0);
! 		if(l_eof)
! 			err(f__elist->ciend, EOF, "list in");
! 		if(f__lcount == 0) {
! 			f__ltype = 0;
! 			for(;;)  {
! 				GETC(ch);
! 				switch(ch) {
! 				case EOF:
! 					err(f__elist->ciend,(EOF),"list in");
! 				case ' ':
! 				case '\t':
! 				case '\n':
! 					continue;
! 				case '/':
! 					f__lquit = 1;
! 					goto loopend;
! 				case ',':
! 					f__lcount = 1;
! 					goto loopend;
! 				default:
! 					(void) Ungetc(ch, f__cf);
! 					goto rddata;
! 				}
! 			}
! 		}
! 	rddata:
! 		switch((int)type)
  		{
! 		case TYINT1:
! 		case TYSHORT:
! 		case TYLONG:
  #ifndef ALLOW_FLOAT_IN_INTEGER_LIST_INPUT
! 			ERR(l_R(0,1));
! 			break;
  #endif
! 		case TYREAL:
! 		case TYDREAL:
! 			ERR(l_R(0,0));
! 			break;
  #ifdef TYQUAD
! 		case TYQUAD:
! 			n = l_R(0,2);
! 			if (n)
! 				return n;
! 			break;
  #endif
! 		case TYCOMPLEX:
! 		case TYDCOMPLEX:
! 			ERR(l_C());
! 			break;
! 		case TYLOGICAL1:
! 		case TYLOGICAL2:
! 		case TYLOGICAL:
! 			ERR(l_L());
! 			break;
! 		case TYCHAR:
! 			ERR(l_CHAR());
! 			break;
! 		}
! 	while (GETC(ch) == ' ' || ch == '\t');
! 	if (ch != ',' || f__lcount > 1)
! 		Ungetc(ch,f__cf);
! 	loopend:
! 		if(f__lquit) return(0);
! 		if(f__cf && ferror(f__cf)) {
! 			clearerr(f__cf);
! 			errfl(f__elist->cierr,errno,"list in");
! 			}
! 		if(f__ltype==0) goto bump;
! 		switch((int)type)
! 		{
! 		case TYINT1:
! 		case TYLOGICAL1:
! 			Ptr->flchar = (char)f__lx;
! 			break;
! 		case TYLOGICAL2:
! 		case TYSHORT:
! 			Ptr->flshort = (short)f__lx;
! 			break;
! 		case TYLOGICAL:
! 		case TYLONG:
! 			Ptr->flint = (ftnint)f__lx;
! 			break;
  #ifdef Allow_TYQUAD
! 		case TYQUAD:
! 			if (!(Ptr->fllongint = f__llx))
! 				Ptr->fllongint = f__lx;
! 			break;
  #endif
! 		case TYREAL:
! 			Ptr->flreal=f__lx;
! 			break;
! 		case TYDREAL:
! 			Ptr->fldouble=f__lx;
! 			break;
! 		case TYCOMPLEX:
! 			xx=(real *)ptr;
! 			*xx++ = f__lx;
! 			*xx = f__ly;
! 			break;
! 		case TYDCOMPLEX:
! 			yy=(doublereal *)ptr;
! 			*yy++ = f__lx;
! 			*yy = f__ly;
! 			break;
! 		case TYCHAR:
! 			b_char(f__lchar,ptr,len);
! 			break;
! 		}
! 	bump:
! 		if(f__lcount>0) f__lcount--;
! 		ptr += len;
! 		if (nml_read)
! 			nml_read++;
  	}
! 	return(0);
  #undef Ptr
  }
! #ifdef KR_headers
! integer s_rsle(a) cilist *a;
! #else
! integer s_rsle(cilist *a)
! #endif
  {
! 	int n;
  
! 	f__reading=1;
! 	f__external=1;
! 	f__formatted=1;
! 	if(n=c_le(a)) return(n);
! 	f__lioproc = l_read;
! 	f__lquit = 0;
! 	f__lcount = 0;
! 	l_eof = 0;
! 	if(f__curunit->uwrt && f__nowreading(f__curunit))
! 		err(a->cierr,errno,"read start");
! 	if(f__curunit->uend)
! 		err(f__elist->ciend,(EOF),"read start");
! 	l_getc = t_getc;
! 	l_ungetc = un_getc;
! 	f__doend = xrd_SL;
! 	return(0);
  }
--- 41,845 ----
  #define EX 8
  #define SG 16
  #define WH 32
! char f__ltab[128 + 1] = {	/* offset one for EOF */
!   0,
!   0, 0, AX, 0, 0, 0, 0, 0, 0, WH | B, SX | WH, 0, 0, 0, 0, 0,
!   0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
!   SX | B | WH, 0, AX, 0, 0, 0, 0, AX, 0, 0, 0, SG, SX, SG, 0, SX,
!   0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
!   0, 0, 0, 0, EX, EX, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
!   0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
!   AX, 0, 0, 0, EX, EX, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
!   0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  };
  
  #ifdef ungetc
! static int
! un_getc (int x, FILE * f__cf)
! {
!   return ungetc (x, f__cf);
! }
  #else
  #define un_getc ungetc
! extern int ungetc (int, FILE *);	/* for systems with a buggy stdio.h */
  #endif
  
! int
! t_getc (void)
! {
!   int ch;
!   if (f__curunit->uend)
!     return (EOF);
!   if ((ch = getc (f__cf)) != EOF)
!     return (ch);
!   if (feof (f__cf))
!     f__curunit->uend = l_eof = 1;
!   return (EOF);
  }
! 
! integer
! e_rsle (void)
  {
!   int ch;
!   f__init = 1;
!   if (f__curunit->uend)
!     return (0);
!   while ((ch = t_getc ()) != '\n')
!     if (ch == EOF)
!       {
! 	if (feof (f__cf))
! 	  f__curunit->uend = l_eof = 1;
! 	return EOF;
!       }
!   return (0);
  }
  
  flag f__lquit;
! int f__lcount, f__ltype, nml_read;
  char *f__lchar;
! double f__lx, f__ly;
! #define ERR(x) if((n=(x))) {f__init &= ~2; return(n);}
  #define GETC(x) (x=(*l_getc)())
  #define Ungetc(x,y) (*l_ungetc)(x,y)
  
! static int
! l_R (int poststar, int reqint)
  {
!   char s[FMAX + EXPMAXDIGS + 4];
!   register int ch;
!   register char *sp, *spe, *sp1;
!   long e, exp;
!   int havenum, havestar, se;
  
!   if (!poststar)
!     {
!       if (f__lcount > 0)
! 	return (0);
!       f__lcount = 1;
!     }
  #ifdef Allow_TYQUAD
!   f__llx = 0;
  #endif
!   f__ltype = 0;
!   exp = 0;
!   havestar = 0;
  retry:
!   sp1 = sp = s;
!   spe = sp + FMAX;
!   havenum = 0;
  
!   switch (GETC (ch))
!     {
!     case '-':
!       *sp++ = ch;
!       sp1++;
!       spe++;
!     case '+':
!       GETC (ch);
!     }
!   while (ch == '0')
!     {
!       ++havenum;
!       GETC (ch);
!     }
!   while (isdigit (ch))
!     {
!       if (sp < spe)
! 	*sp++ = ch;
!       else
! 	++exp;
!       GETC (ch);
!     }
!   if (ch == '*' && !poststar)
!     {
!       if (sp == sp1 || exp || *s == '-')
! 	{
! 	  errfl (f__elist->cierr, 112, "bad repetition count");
! 	}
!       poststar = havestar = 1;
!       *sp = 0;
!       f__lcount = atoi (s);
!       goto retry;
!     }
!   if (ch == '.')
!     {
  #ifndef ALLOW_FLOAT_IN_INTEGER_LIST_INPUT
!       if (reqint)
! 	errfl (f__elist->cierr, 115, "invalid integer");
  #endif
!       GETC (ch);
!       if (sp == sp1)
! 	while (ch == '0')
! 	  {
! 	    ++havenum;
! 	    --exp;
! 	    GETC (ch);
! 	  }
!       while (isdigit (ch))
! 	{
! 	  if (sp < spe)
! 	    {
! 	      *sp++ = ch;
! 	      --exp;
! 	    }
! 	  GETC (ch);
! 	}
!     }
!   havenum += sp - sp1;
!   se = 0;
!   if (issign (ch))
!     goto signonly;
!   if (havenum && isexp (ch))
!     {
  #ifndef ALLOW_FLOAT_IN_INTEGER_LIST_INPUT
!       if (reqint)
! 	errfl (f__elist->cierr, 115, "invalid integer");
  #endif
!       GETC (ch);
!       if (issign (ch))
! 	{
! 	signonly:
! 	  if (ch == '-')
! 	    se = 1;
! 	  GETC (ch);
! 	}
!       if (!isdigit (ch))
! 	{
! 	bad:
! 	  errfl (f__elist->cierr, 112, "exponent field");
! 	}
  
!       e = ch - '0';
!       while (isdigit (GETC (ch)))
! 	{
! 	  e = 10 * e + ch - '0';
! 	  if (e > EXPMAX)
! 	    goto bad;
! 	}
!       if (se)
! 	exp -= e;
!       else
! 	exp += e;
!     }
!   (void) Ungetc (ch, f__cf);
!   if (sp > sp1)
!     {
!       ++havenum;
!       while (*--sp == '0')
! 	++exp;
!       if (exp)
! 	sprintf (sp + 1, "e%ld", exp);
!       else
! 	sp[1] = 0;
!       f__lx = atof (s);
  #ifdef Allow_TYQUAD
!       if (reqint & 2 && (se = sp - sp1 + exp) > 14 && se < 20)
! 	{
! 	  /* Assuming 64-bit longint and 32-bit long. */
! 	  if (exp < 0)
! 	    sp += exp;
! 	  if (sp1 <= sp)
! 	    {
! 	      f__llx = *sp1 - '0';
! 	      while (++sp1 <= sp)
! 		f__llx = 10 * f__llx + (*sp1 - '0');
! 	    }
! 	  while (--exp >= 0)
! 	    f__llx *= 10;
! 	  if (*s == '-')
! 	    f__llx = -f__llx;
  	}
  #endif
+     }
+   else
+     f__lx = 0.;
+   if (havenum)
+     f__ltype = TYLONG;
+   else
+     switch (ch)
+       {
+       case ',':
+       case '/':
+ 	break;
+       default:
+ 	if (havestar && (ch == ' ' || ch == '\t' || ch == '\n'))
+ 	  break;
+ 	if (nml_read > 1)
+ 	  {
+ 	    f__lquit = 2;
+ 	    return 0;
+ 	  }
+ 	errfl (f__elist->cierr, 112, "invalid number");
+       }
+   return 0;
+ }
+ 
+ static int
+ rd_count (register int ch)
  {
!   if (ch < '0' || ch > '9')
!     return 1;
!   f__lcount = ch - '0';
!   while (GETC (ch) >= '0' && ch <= '9')
!     f__lcount = 10 * f__lcount + ch - '0';
!   Ungetc (ch, f__cf);
!   return f__lcount <= 0;
! }
  
! static int
! l_C (void)
! {
!   int ch, nml_save;
!   double lz;
!   if (f__lcount > 0)
!     return (0);
!   f__ltype = 0;
!   GETC (ch);
!   if (ch != '(')
!     {
!       if (nml_read > 1 && (ch < '0' || ch > '9'))
  	{
! 	  Ungetc (ch, f__cf);
! 	  f__lquit = 2;
! 	  return 0;
  	}
!       if (rd_count (ch))
!         {
! 	  if (!f__cf || !feof (f__cf))
! 	    errfl (f__elist->cierr, 112, "complex format");
! 	  else
! 	    err (f__elist->cierr, (EOF), "lread");
  	}
!       if (GETC (ch) != '*')
! 	{
! 	  if (!f__cf || !feof (f__cf))
! 	    errfl (f__elist->cierr, 112, "no star");
! 	  else
! 	    err (f__elist->cierr, (EOF), "lread");
! 	}
!       if (GETC (ch) != '(')
! 	{
! 	  Ungetc (ch, f__cf);
! 	  return (0);
! 	}
!     }
!   else
!     f__lcount = 1;
!   while (iswhit (GETC (ch)));
!   Ungetc (ch, f__cf);
!   nml_save = nml_read;
!   nml_read = 0;
!   if ((ch = l_R (1, 0)))
!     return ch;
!   if (!f__ltype)
!     errfl (f__elist->cierr, 112, "no real part");
!   lz = f__lx;
!   while (iswhit (GETC (ch)));
!   if (ch != ',')
!     {
!       (void) Ungetc (ch, f__cf);
!       errfl (f__elist->cierr, 112, "no comma");
!     }
!   while (iswhit (GETC (ch)));
!   (void) Ungetc (ch, f__cf);
!   if ((ch = l_R (1, 0)))
!     return ch;
!   if (!f__ltype)
!     errfl (f__elist->cierr, 112, "no imaginary part");
!   while (iswhit (GETC (ch)));
!   if (ch != ')')
!     errfl (f__elist->cierr, 112, "no )");
!   f__ly = f__lx;
!   f__lx = lz;
  #ifdef Allow_TYQUAD
!   f__llx = 0;
  #endif
!   nml_read = nml_save;
!   return (0);
  }
  
! static char nmLbuf[256], *nmL_next;
! static int (*nmL_getc_save) (void);
! static int (*nmL_ungetc_save) (int, FILE *);
  
! static int
! nmL_getc (void)
  {
!   int rv;
!   if ((rv = *nmL_next++))
!     return rv;
!   l_getc = nmL_getc_save;
!   l_ungetc = nmL_ungetc_save;
!   return (*l_getc) ();
! }
  
! static int
! nmL_ungetc (int x, FILE * f)
  {
!   f = f;			/* banish non-use warning */
!   return *--nmL_next = x;
! }
  
! static int
! Lfinish (int ch, int dot, int *rvp)
  {
!   char *s, *se;
!   static char what[] = "namelist input";
  
!   s = nmLbuf + 2;
!   se = nmLbuf + sizeof (nmLbuf) - 1;
!   *s++ = ch;
!   while (!issep (GETC (ch)) && ch != EOF)
!     {
!       if (s >= se)
! 	{
! 	nmLbuf_ovfl:
! 	  return *rvp = err__fl (f__elist->cierr, 131, what);
  	}
+       *s++ = ch;
+       if (ch != '=')
+ 	continue;
+       if (dot)
+ 	return *rvp = err__fl (f__elist->cierr, 112, what);
+     got_eq:
+       *s = 0;
+       nmL_getc_save = l_getc;
+       l_getc = nmL_getc;
+       nmL_ungetc_save = l_ungetc;
+       l_ungetc = nmL_ungetc;
+       nmLbuf[1] = *(nmL_next = nmLbuf) = ',';
+       *rvp = f__lcount = 0;
+       return 1;
+     }
+   if (dot)
+     goto done;
+   for (;;)
+     {
+       if (s >= se)
+ 	goto nmLbuf_ovfl;
+       *s++ = ch;
+       if (!isblnk (ch))
+ 	break;
+       if (GETC (ch) == EOF)
+ 	goto done;
+     }
+   if (ch == '=')
+     goto got_eq;
+ done:
+   Ungetc (ch, f__cf);
+   return 0;
+ }
  
! static int
! l_L (void)
  {
!   int ch, rv, sawdot;
!   if (f__lcount > 0)
!     return (0);
!   f__lcount = 1;
!   f__ltype = 0;
!   GETC (ch);
!   if (isdigit (ch))
!     {
!       rd_count (ch);
!       if (GETC (ch) != '*')
!         {
! 	  if (!f__cf || !feof (f__cf))
! 	    errfl (f__elist->cierr, 112, "no star");
! 	  else
! 	    err (f__elist->cierr, (EOF), "lread");
! 	}
!       GETC (ch);
!     }
!   sawdot = 0;
!   if (ch == '.')
!     {
!       sawdot = 1;
!       GETC (ch);
!     }
!   switch (ch)
!     {
!     case 't':
!     case 'T':
!       if (nml_read && Lfinish (ch, sawdot, &rv))
! 	return rv;
!       f__lx = 1;
!       break;
!     case 'f':
!     case 'F':
!       if (nml_read && Lfinish (ch, sawdot, &rv))
! 	return rv;
!       f__lx = 0;
!       break;
!     default:
!       if (isblnk (ch) || issep (ch) || ch == EOF)
  	{
! 	  (void) Ungetc (ch, f__cf);
! 	  return (0);
  	}
!       if (nml_read > 1)
  	{
! 	  Ungetc (ch, f__cf);
! 	  f__lquit = 2;
! 	  return 0;
  	}
!       errfl (f__elist->cierr, 112, "logical");
!     }
!   f__ltype = TYLONG;
!   while (!issep (GETC (ch)) && ch != EOF);
!   (void) Ungetc (ch, f__cf);
!   return (0);
  }
  
  #define BUFSIZE	128
  
! static int
! l_CHAR (void)
! {
!   int ch, size, i;
!   static char rafail[] = "realloc failure";
!   char quote, *p;
!   if (f__lcount > 0)
!     return (0);
!   f__ltype = 0;
!   if (f__lchar != NULL)
!     free (f__lchar);
!   size = BUFSIZE;
!   p = f__lchar = (char *) malloc ((unsigned int) size);
!   if (f__lchar == NULL)
!     errfl (f__elist->cierr, 113, "no space");
  
!   GETC (ch);
!   if (isdigit (ch))
!     {
!       /* allow Fortran 8x-style unquoted string...    */
!       /* either find a repetition count or the string */
!       f__lcount = ch - '0';
!       *p++ = ch;
!       for (i = 1;;)
! 	{
! 	  switch (GETC (ch))
! 	    {
! 	    case '*':
! 	      if (f__lcount == 0)
! 		{
! 		  f__lcount = 1;
  #ifndef F8X_NML_ELIDE_QUOTES
! 		  if (nml_read)
! 		    goto no_quote;
  #endif
! 		  goto noquote;
  		}
+ 	      p = f__lchar;
+ 	      goto have_lcount;
+ 	    case ',':
+ 	    case ' ':
+ 	    case '\t':
+ 	    case '\n':
+ 	    case '/':
+ 	      Ungetc (ch, f__cf);
+ 	      /* no break */
+ 	    case EOF:
+ 	      f__lcount = 1;
+ 	      f__ltype = TYCHAR;
+ 	      return *p = 0;
+ 	    }
+ 	  if (!isdigit (ch))
+ 	    {
+ 	      f__lcount = 1;
  #ifndef F8X_NML_ELIDE_QUOTES
! 	      if (nml_read)
  		{
! 		no_quote:
! 		  errfl (f__elist->cierr, 112,
! 			 "undelimited character string");
  		}
+ #endif
+ 	      goto noquote;
+ 	    }
+ 	  *p++ = ch;
+ 	  f__lcount = 10 * f__lcount + ch - '0';
+ 	  if (++i == size)
+ 	    {
+ 	      f__lchar = (char *) realloc (f__lchar,
+ 					   (unsigned int) (size += BUFSIZE));
+ 	      if (f__lchar == NULL)
+ 		errfl (f__elist->cierr, 113, rafail);
+ 	      p = f__lchar + i;
+ 	    }
  	}
!     }
!   else
!     (void) Ungetc (ch, f__cf);
! have_lcount:
!   if (GETC (ch) == '\'' || ch == '"')
!     quote = ch;
!   else if (isblnk (ch) || (issep (ch) && ch != '\n') || ch == EOF)
!     {
!       Ungetc (ch, f__cf);
!       return 0;
!     }
! #ifndef F8X_NML_ELIDE_QUOTES
!   else if (nml_read > 1)
!     {
!       Ungetc (ch, f__cf);
!       f__lquit = 2;
!       return 0;
!     }
  #endif
+   else
+     {
+       /* Fortran 8x-style unquoted string */
+       *p++ = ch;
+       for (i = 1;;)
+ 	{
+ 	  switch (GETC (ch))
+ 	    {
+ 	    case ',':
+ 	    case ' ':
+ 	    case '\t':
+ 	    case '\n':
+ 	    case '/':
+ 	      Ungetc (ch, f__cf);
+ 	      /* no break */
+ 	    case EOF:
+ 	      f__ltype = TYCHAR;
+ 	      return *p = 0;
+ 	    }
+ 	noquote:
+ 	  *p++ = ch;
+ 	  if (++i == size)
+ 	    {
+ 	      f__lchar = (char *) realloc (f__lchar,
+ 					   (unsigned int) (size += BUFSIZE));
+ 	      if (f__lchar == NULL)
+ 		errfl (f__elist->cierr, 113, rafail);
+ 	      p = f__lchar + i;
+ 	    }
+ 	}
+     }
+   f__ltype = TYCHAR;
+   for (i = 0;;)
+     {
+       while (GETC (ch) != quote && ch != '\n' && ch != EOF && ++i < size)
+ 	*p++ = ch;
+       if (i == size)
+ 	{
+ 	newone:
+ 	  f__lchar = (char *) realloc (f__lchar,
+ 				       (unsigned int) (size += BUFSIZE));
+ 	  if (f__lchar == NULL)
+ 	    errfl (f__elist->cierr, 113, rafail);
+ 	  p = f__lchar + i - 1;
+ 	  *p++ = ch;
+ 	}
+       else if (ch == EOF)
+ 	return (EOF);
+       else if (ch == '\n')
+ 	{
+ 	  if (*(p - 1) != '\\')
+ 	    continue;
+ 	  i--;
+ 	  p--;
+ 	  if (++i < size)
+ 	    *p++ = ch;
+ 	  else
+ 	    goto newone;
+ 	}
+       else if (GETC (ch) == quote)
+ 	{
+ 	  if (++i < size)
+ 	    *p++ = ch;
+ 	  else
+ 	    goto newone;
+ 	}
+       else
+ 	{
+ 	  (void) Ungetc (ch, f__cf);
+ 	  *p = 0;
+ 	  return (0);
+ 	}
+     }
+ }
+ 
+ int
+ c_le (cilist * a)
  {
!   if (f__init != 1)
!     f_init ();
!   f__init = 3;
!   f__fmtbuf = "list io";
!   f__curunit = &f__units[a->ciunit];
!   f__fmtlen = 7;
!   if (a->ciunit >= MXUNIT || a->ciunit < 0)
!     err (a->cierr, 101, "stler");
!   f__scale = f__recpos = 0;
!   f__elist = a;
!   if (f__curunit->ufd == NULL && fk_open (SEQ, FMT, a->ciunit))
!     err (a->cierr, 102, "lio");
!   f__cf = f__curunit->ufd;
!   if (!f__curunit->ufmt)
!     err (a->cierr, 103, "lio");
!   return (0);
  }
! 
! int
! l_read (ftnint * number, char *ptr, ftnlen len, ftnint type)
  {
  #define Ptr ((flex *)ptr)
!   int i, n, ch;
!   doublereal *yy;
!   real *xx;
!   for (i = 0; i < *number; i++)
!     {
!       if (f__lquit)
! 	return (0);
!       if (l_eof)
! 	err (f__elist->ciend, EOF, "list in");
!       if (f__lcount == 0)
  	{
! 	  f__ltype = 0;
! 	  for (;;)
! 	    {
! 	      GETC (ch);
! 	      switch (ch)
  		{
! 		case EOF:
! 		  err (f__elist->ciend, (EOF), "list in");
! 		case ' ':
! 		case '\t':
! 		case '\n':
! 		  continue;
! 		case '/':
! 		  f__lquit = 1;
! 		  goto loopend;
! 		case ',':
! 		  f__lcount = 1;
! 		  goto loopend;
! 		default:
! 		  (void) Ungetc (ch, f__cf);
! 		  goto rddata;
! 		}
! 	    }
! 	}
!     rddata:
!       switch ((int) type)
! 	{
! 	case TYINT1:
! 	case TYSHORT:
! 	case TYLONG:
  #ifndef ALLOW_FLOAT_IN_INTEGER_LIST_INPUT
! 	  ERR (l_R (0, 1));
! 	  break;
  #endif
! 	case TYREAL:
! 	case TYDREAL:
! 	  ERR (l_R (0, 0));
! 	  break;
  #ifdef TYQUAD
! 	case TYQUAD:
! 	  n = l_R (0, 2);
! 	  if (n)
! 	    return n;
! 	  break;
  #endif
! 	case TYCOMPLEX:
! 	case TYDCOMPLEX:
! 	  ERR (l_C ());
! 	  break;
! 	case TYLOGICAL1:
! 	case TYLOGICAL2:
! 	case TYLOGICAL:
! 	  ERR (l_L ());
! 	  break;
! 	case TYCHAR:
! 	  ERR (l_CHAR ());
! 	  break;
! 	}
!       while (GETC (ch) == ' ' || ch == '\t');
!       if (ch != ',' || f__lcount > 1)
! 	Ungetc (ch, f__cf);
!     loopend:
!       if (f__lquit)
! 	return (0);
!       if (f__cf && ferror (f__cf))
! 	{
! 	  clearerr (f__cf);
! 	  errfl (f__elist->cierr, errno, "list in");
! 	}
!       if (f__ltype == 0)
! 	goto bump;
!       switch ((int) type)
! 	{
! 	case TYINT1:
! 	case TYLOGICAL1:
! 	  Ptr->flchar = (char) f__lx;
! 	  break;
! 	case TYLOGICAL2:
! 	case TYSHORT:
! 	  Ptr->flshort = (short) f__lx;
! 	  break;
! 	case TYLOGICAL:
! 	case TYLONG:
! 	  Ptr->flint = (ftnint) f__lx;
! 	  break;
  #ifdef Allow_TYQUAD
! 	case TYQUAD:
! 	  if (!(Ptr->fllongint = f__llx))
! 	    Ptr->fllongint = f__lx;
! 	  break;
  #endif
! 	case TYREAL:
! 	  Ptr->flreal = f__lx;
! 	  break;
! 	case TYDREAL:
! 	  Ptr->fldouble = f__lx;
! 	  break;
! 	case TYCOMPLEX:
! 	  xx = (real *) ptr;
! 	  *xx++ = f__lx;
! 	  *xx = f__ly;
! 	  break;
! 	case TYDCOMPLEX:
! 	  yy = (doublereal *) ptr;
! 	  *yy++ = f__lx;
! 	  *yy = f__ly;
! 	  break;
! 	case TYCHAR:
! 	  b_char (f__lchar, ptr, len);
! 	  break;
  	}
!     bump:
!       if (f__lcount > 0)
! 	f__lcount--;
!       ptr += len;
!       if (nml_read)
! 	nml_read++;
!     }
!   return (0);
  #undef Ptr
  }
! 
! integer
! s_rsle (cilist * a)
  {
!   int n;
  
!   f__reading = 1;
!   f__external = 1;
!   f__formatted = 1;
!   if ((n = c_le (a)))
!     return (n);
!   f__lioproc = l_read;
!   f__lquit = 0;
!   f__lcount = 0;
!   l_eof = 0;
!   if (f__curunit->uwrt && f__nowreading (f__curunit))
!     err (a->cierr, errno, "read start");
!   if (f__curunit->uend)
!     err (f__elist->ciend, (EOF), "read start");
!   l_getc = t_getc;
!   l_ungetc = un_getc;
!   f__doend = xrd_SL;
!   return (0);
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libI77/lwrite.c gcc-3.3/libf2c/libI77/lwrite.c
*** gcc-3.2.3/libf2c/libI77/lwrite.c	1998-05-19 10:51:11.000000000 +0000
--- gcc-3.3/libf2c/libI77/lwrite.c	2002-06-02 14:34:31.000000000 +0000
***************
*** 6,302 ****
  ftnint L_len;
  int f__Aquote;
  
!  static VOID
! donewrec(Void)
  {
! 	if (f__recpos)
! 		(*f__donewrec)();
! 	}
  
!  static VOID
! #ifdef KR_headers
! lwrt_I(n) longint n;
! #else
! lwrt_I(longint n)
! #endif
  {
! 	char *p;
! 	int ndigit, sign;
  
! 	p = f__icvt(n, &ndigit, &sign, 10);
! 	if(f__recpos + ndigit >= L_len)
! 		donewrec();
! 	PUT(' ');
! 	if (sign)
! 		PUT('-');
! 	while(*p)
! 		PUT(*p++);
  }
!  static VOID
! #ifdef KR_headers
! lwrt_L(n, len) ftnint n; ftnlen len;
! #else
! lwrt_L(ftnint n, ftnlen len)
! #endif
  {
! 	if(f__recpos+LLOGW>=L_len)
! 		donewrec();
! 	wrt_L((Uint *)&n,LLOGW, len);
  }
!  static VOID
! #ifdef KR_headers
! lwrt_A(p,len) char *p; ftnlen len;
! #else
! lwrt_A(char *p, ftnlen len)
! #endif
  {
! 	int a;
! 	char *p1, *pe;
  
! 	a = 0;
! 	pe = p + len;
! 	if (f__Aquote) {
! 		a = 3;
! 		if (len > 1 && p[len-1] == ' ') {
! 			while(--len > 1 && p[len-1] == ' ');
! 			pe = p + len;
! 			}
! 		p1 = p;
! 		while(p1 < pe)
! 			if (*p1++ == '\'')
! 				a++;
! 		}
! 	if(f__recpos+len+a >= L_len)
! 		donewrec();
! 	if (a
  #ifndef OMIT_BLANK_CC
! 		|| !f__recpos
  #endif
! 		)
! 		PUT(' ');
! 	if (a) {
! 		PUT('\'');
! 		while(p < pe) {
! 			if (*p == '\'')
! 				PUT('\'');
! 			PUT(*p++);
! 			}
! 		PUT('\'');
! 		}
! 	else
! 		while(p < pe)
! 			PUT(*p++);
  }
  
!  static int
! #ifdef KR_headers
! l_g(buf, n) char *buf; double n;
! #else
! l_g(char *buf, double n)
! #endif
  {
  #ifdef Old_list_output
! 	doublereal absn;
! 	char *fmt;
  
! 	absn = n;
! 	if (absn < 0)
! 		absn = -absn;
! 	fmt = LLOW <= absn && absn < LHIGH ? LFFMT : LEFMT;
  #ifdef USE_STRLEN
! 	sprintf(buf, fmt, n);
! 	return strlen(buf);
  #else
! 	return sprintf(buf, fmt, n);
  #endif
  
  #else
! 	register char *b, c, c1;
  
! 	b = buf;
! 	*b++ = ' ';
! 	if (n < 0) {
! 		*b++ = '-';
! 		n = -n;
! 		}
! 	else
! 		*b++ = ' ';
! 	if (n == 0) {
! 		*b++ = '0';
! 		*b++ = '.';
! 		*b = 0;
! 		goto f__ret;
! 		}
! 	sprintf(b, LGFMT, n);
! 	switch(*b) {
  #ifndef WANT_LEAD_0
! 		case '0':
! 			while(b[0] = b[1])
! 				b++;
! 			break;
  #endif
! 		case 'i':
! 		case 'I':
! 			/* Infinity */
! 		case 'n':
! 		case 'N':
! 			/* NaN */
! 			while(*++b);
! 			break;
  
! 		default:
! 	/* Fortran 77 insists on having a decimal point... */
! 		    for(;; b++)
! 			switch(*b) {
! 			case 0:
! 				*b++ = '.';
! 				*b = 0;
! 				goto f__ret;
! 			case '.':
! 				while(*++b);
! 				goto f__ret;
! 			case 'E':
! 				for(c1 = '.', c = 'E';  *b = c1;
! 					c1 = c, c = *++b);
! 				goto f__ret;
! 			}
! 		}
!  f__ret:
! 	return b - buf;
  #endif
! 	}
  
!  static VOID
! #ifdef KR_headers
! l_put(s) register char *s;
! #else
! l_put(register char *s)
! #endif
  {
! #ifdef KR_headers
! 	register void (*pn)() = f__putn;
! #else
! 	register void (*pn)(int) = f__putn;
! #endif
! 	register int c;
  
! 	while(c = *s++)
! 		(*pn)(c);
! 	}
  
!  static VOID
! #ifdef KR_headers
! lwrt_F(n) double n;
! #else
! lwrt_F(double n)
! #endif
  {
! 	char buf[LEFBL];
  
! 	if(f__recpos + l_g(buf,n) >= L_len)
! 		donewrec();
! 	l_put(buf);
  }
!  static VOID
! #ifdef KR_headers
! lwrt_C(a,b) double a,b;
! #else
! lwrt_C(double a, double b)
! #endif
  {
! 	char *ba, *bb, bufa[LEFBL], bufb[LEFBL];
! 	int al, bl;
  
! 	al = l_g(bufa, a);
! 	for(ba = bufa; *ba == ' '; ba++)
! 		--al;
! 	bl = l_g(bufb, b) + 1;	/* intentionally high by 1 */
! 	for(bb = bufb; *bb == ' '; bb++)
! 		--bl;
! 	if(f__recpos + al + bl + 3 >= L_len)
! 		donewrec();
  #ifdef OMIT_BLANK_CC
! 	else
  #endif
! 	PUT(' ');
! 	PUT('(');
! 	l_put(ba);
! 	PUT(',');
! 	if (f__recpos + bl >= L_len) {
! 		(*f__donewrec)();
  #ifndef OMIT_BLANK_CC
! 		PUT(' ');
  #endif
! 		}
! 	l_put(bb);
! 	PUT(')');
  }
! #ifdef KR_headers
! l_write(number,ptr,len,type) ftnint *number,type; char *ptr; ftnlen len;
! #else
! l_write(ftnint *number, char *ptr, ftnlen len, ftnint type)
! #endif
  {
  #define Ptr ((flex *)ptr)
! 	int i;
! 	longint x;
! 	double y,z;
! 	real *xx;
! 	doublereal *yy;
! 	for(i=0;i< *number; i++)
  	{
! 		switch((int)type)
! 		{
! 		default: f__fatal(204,"unknown type in lio");
! 		case TYINT1:
! 			x = Ptr->flchar;
! 			goto xint;
! 		case TYSHORT:
! 			x=Ptr->flshort;
! 			goto xint;
  #ifdef Allow_TYQUAD
! 		case TYQUAD:
! 			x = Ptr->fllongint;
! 			goto xint;
  #endif
! 		case TYLONG:
! 			x=Ptr->flint;
! 		xint:	lwrt_I(x);
! 			break;
! 		case TYREAL:
! 			y=Ptr->flreal;
! 			goto xfloat;
! 		case TYDREAL:
! 			y=Ptr->fldouble;
! 		xfloat: lwrt_F(y);
! 			break;
! 		case TYCOMPLEX:
! 			xx= &Ptr->flreal;
! 			y = *xx++;
! 			z = *xx;
! 			goto xcomplex;
! 		case TYDCOMPLEX:
! 			yy = &Ptr->fldouble;
! 			y= *yy++;
! 			z = *yy;
! 		xcomplex:
! 			lwrt_C(y,z);
! 			break;
! 		case TYLOGICAL1:
! 			x = Ptr->flchar;
! 			goto xlog;
! 		case TYLOGICAL2:
! 			x = Ptr->flshort;
! 			goto xlog;
! 		case TYLOGICAL:
! 			x = Ptr->flint;
! 		xlog:	lwrt_L(Ptr->flint, len);
! 			break;
! 		case TYCHAR:
! 			lwrt_A(ptr,len);
! 			break;
! 		}
! 		ptr += len;
  	}
! 	return(0);
  }
--- 6,277 ----
  ftnint L_len;
  int f__Aquote;
  
! static void
! donewrec (void)
  {
!   if (f__recpos)
!     (*f__donewrec) ();
! }
  
! static void
! lwrt_I (longint n)
  {
!   char *p;
!   int ndigit, sign;
  
!   p = f__icvt (n, &ndigit, &sign, 10);
!   if (f__recpos + ndigit >= L_len)
!     donewrec ();
!   PUT (' ');
!   if (sign)
!     PUT ('-');
!   while (*p)
!     PUT (*p++);
  }
! static void
! lwrt_L (ftnint n, ftnlen len)
  {
!   if (f__recpos + LLOGW >= L_len)
!     donewrec ();
!   wrt_L ((Uint *) & n, LLOGW, len);
  }
! static void
! lwrt_A (char *p, ftnlen len)
  {
!   int a;
!   char *p1, *pe;
  
!   a = 0;
!   pe = p + len;
!   if (f__Aquote)
!     {
!       a = 3;
!       if (len > 1 && p[len - 1] == ' ')
! 	{
! 	  while (--len > 1 && p[len - 1] == ' ');
! 	  pe = p + len;
! 	}
!       p1 = p;
!       while (p1 < pe)
! 	if (*p1++ == '\'')
! 	  a++;
!     }
!   if (f__recpos + len + a >= L_len)
!     donewrec ();
!   if (a
  #ifndef OMIT_BLANK_CC
!       || !f__recpos
  #endif
!     )
!     PUT (' ');
!   if (a)
!     {
!       PUT ('\'');
!       while (p < pe)
! 	{
! 	  if (*p == '\'')
! 	    PUT ('\'');
! 	  PUT (*p++);
! 	}
!       PUT ('\'');
!     }
!   else
!     while (p < pe)
!       PUT (*p++);
  }
  
! static int
! l_g (char *buf, double n)
  {
  #ifdef Old_list_output
!   doublereal absn;
!   char *fmt;
  
!   absn = n;
!   if (absn < 0)
!     absn = -absn;
!   fmt = LLOW <= absn && absn < LHIGH ? LFFMT : LEFMT;
  #ifdef USE_STRLEN
!   sprintf (buf, fmt, n);
!   return strlen (buf);
  #else
!   return sprintf (buf, fmt, n);
  #endif
  
  #else
!   register char *b, c, c1;
  
!   b = buf;
!   *b++ = ' ';
!   if (n < 0)
!     {
!       *b++ = '-';
!       n = -n;
!     }
!   else
!     *b++ = ' ';
!   if (n == 0)
!     {
!       *b++ = '0';
!       *b++ = '.';
!       *b = 0;
!       goto f__ret;
!     }
!   sprintf (b, LGFMT, n);
!   switch (*b)
!     {
  #ifndef WANT_LEAD_0
!     case '0':
!       while (b[0] = b[1])
! 	b++;
!       break;
  #endif
!     case 'i':
!     case 'I':
!       /* Infinity */
!     case 'n':
!     case 'N':
!       /* NaN */
!       while (*++b);
!       break;
  
!     default:
!       /* Fortran 77 insists on having a decimal point... */
!       for (;; b++)
! 	switch (*b)
! 	  {
! 	  case 0:
! 	    *b++ = '.';
! 	    *b = 0;
! 	    goto f__ret;
! 	  case '.':
! 	    while (*++b);
! 	    goto f__ret;
! 	  case 'E':
! 	    for (c1 = '.', c = 'E'; (*b = c1); c1 = c, c = *++b);
! 	    goto f__ret;
! 	  }
!     }
! f__ret:
!   return b - buf;
  #endif
! }
  
! static void
! l_put (register char *s)
  {
!   register void (*pn) (int) = f__putn;
!   register int c;
  
!   while ((c = *s++))
!     (*pn) (c);
! }
  
! static void
! lwrt_F (double n)
  {
!   char buf[LEFBL];
  
!   if (f__recpos + l_g (buf, n) >= L_len)
!     donewrec ();
!   l_put (buf);
  }
! static void
! lwrt_C (double a, double b)
  {
!   char *ba, *bb, bufa[LEFBL], bufb[LEFBL];
!   int al, bl;
  
!   al = l_g (bufa, a);
!   for (ba = bufa; *ba == ' '; ba++)
!     --al;
!   bl = l_g (bufb, b) + 1;	/* intentionally high by 1 */
!   for (bb = bufb; *bb == ' '; bb++)
!     --bl;
!   if (f__recpos + al + bl + 3 >= L_len)
!     donewrec ();
  #ifdef OMIT_BLANK_CC
!   else
  #endif
!     PUT (' ');
!   PUT ('(');
!   l_put (ba);
!   PUT (',');
!   if (f__recpos + bl >= L_len)
!     {
!       (*f__donewrec) ();
  #ifndef OMIT_BLANK_CC
!       PUT (' ');
  #endif
!     }
!   l_put (bb);
!   PUT (')');
  }
! 
! int
! l_write (ftnint * number, char *ptr, ftnlen len, ftnint type)
  {
  #define Ptr ((flex *)ptr)
!   int i;
!   longint x;
!   double y, z;
!   real *xx;
!   doublereal *yy;
!   for (i = 0; i < *number; i++)
!     {
!       switch ((int) type)
  	{
! 	default:
! 	  f__fatal (204, "unknown type in lio");
! 	case TYINT1:
! 	  x = Ptr->flchar;
! 	  goto xint;
! 	case TYSHORT:
! 	  x = Ptr->flshort;
! 	  goto xint;
  #ifdef Allow_TYQUAD
! 	case TYQUAD:
! 	  x = Ptr->fllongint;
! 	  goto xint;
  #endif
! 	case TYLONG:
! 	  x = Ptr->flint;
! 	xint:lwrt_I (x);
! 	  break;
! 	case TYREAL:
! 	  y = Ptr->flreal;
! 	  goto xfloat;
! 	case TYDREAL:
! 	  y = Ptr->fldouble;
! 	xfloat:lwrt_F (y);
! 	  break;
! 	case TYCOMPLEX:
! 	  xx = &Ptr->flreal;
! 	  y = *xx++;
! 	  z = *xx;
! 	  goto xcomplex;
! 	case TYDCOMPLEX:
! 	  yy = &Ptr->fldouble;
! 	  y = *yy++;
! 	  z = *yy;
! 	xcomplex:
! 	  lwrt_C (y, z);
! 	  break;
! 	case TYLOGICAL1:
! 	  x = Ptr->flchar;
! 	  goto xlog;
! 	case TYLOGICAL2:
! 	  x = Ptr->flshort;
! 	  goto xlog;
! 	case TYLOGICAL:
! 	  x = Ptr->flint;
! 	xlog:lwrt_L (Ptr->flint, len);
! 	  break;
! 	case TYCHAR:
! 	  lwrt_A (ptr, len);
! 	  break;
  	}
!       ptr += len;
!     }
!   return (0);
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libI77/Makefile.in gcc-3.3/libf2c/libI77/Makefile.in
*** gcc-3.2.3/libf2c/libI77/Makefile.in	2002-01-15 17:27:05.000000000 +0000
--- gcc-3.3/libf2c/libI77/Makefile.in	2002-05-31 03:07:20.000000000 +0000
*************** CFLAGS = @CFLAGS@
*** 38,49 ****
  CPPFLAGS = @CPPFLAGS@
  @SET_MAKE@
  
! SHELL = /bin/sh
  
  #### End of system configuration section. ####
  
  ALL_CFLAGS = -I. -I$(srcdir) -I$(G2C_H_DIR) -I$(F2C_H_DIR) $(CPPFLAGS) \
!              $(DEFS) $(CFLAGS)
  
  .SUFFIXES:
  .SUFFIXES: .c .lo
--- 38,49 ----
  CPPFLAGS = @CPPFLAGS@
  @SET_MAKE@
  
! SHELL = @SHELL@
  
  #### End of system configuration section. ####
  
  ALL_CFLAGS = -I. -I$(srcdir) -I$(G2C_H_DIR) -I$(F2C_H_DIR) $(CPPFLAGS) \
!              $(DEFS) $(WARN_CFLAGS) $(CFLAGS)
  
  .SUFFIXES:
  .SUFFIXES: .c .lo
diff -Nrc3pad gcc-3.2.3/libf2c/libI77/open.c gcc-3.3/libf2c/libI77/open.c
*** gcc-3.2.3/libf2c/libI77/open.c	2002-01-15 17:27:05.000000000 +0000
--- gcc-3.3/libf2c/libI77/open.c	2003-03-24 23:36:09.000000000 +0000
***************
*** 1,6 ****
- /* Define _XOPEN_SOURCE to get tempnam prototype with glibc et al --
-    more general than _INCLUDE_XOPEN_SOURCE used elsewhere `for HP-UX'.  */
- #define _XOPEN_SOURCE 1
  #include "config.h"
  #include "f2c.h"
  #include "fio.h"
--- 1,3 ----
***************
*** 9,315 ****
  #ifdef MSDOS
  #include "io.h"
  #else
! #include "unistd.h"	/* for access */
  #endif
  #endif
  
- #ifdef KR_headers
- extern char *malloc();
- #ifdef NON_ANSI_STDIO
- extern char *mktemp();
- #endif
- extern integer f_clos();
- #else
  #undef abs
  #undef min
  #undef max
  #include <stdlib.h>
! extern int f__canseek(FILE*);
! extern integer f_clos(cllist*);
! #endif
  
  #ifdef NON_ANSI_RW_MODES
! char *f__r_mode[2] = {"r", "r"};
! char *f__w_mode[4] = {"w", "w", "r+w", "r+w"};
  #else
! char *f__r_mode[2] = {"rb", "r"};
! char *f__w_mode[4] = {"wb", "w", "r+b", "r+"};
  #endif
  
!  static char f__buf0[400], *f__buf = f__buf0;
!  int f__buflen = (int)sizeof(f__buf0);
  
!  static void
! #ifdef KR_headers
! f__bufadj(n, c) int n, c;
! #else
! f__bufadj(int n, int c)
! #endif
  {
! 	unsigned int len;
! 	char *nbuf, *s, *t, *te;
  
! 	if (f__buf == f__buf0)
! 		f__buflen = 1024;
! 	while(f__buflen <= n)
! 		f__buflen <<= 1;
! 	len = (unsigned int)f__buflen;
! 	if (len != f__buflen || !(nbuf = (char*)malloc(len)))
! 		f__fatal(113, "malloc failure");
! 	s = nbuf;
! 	t = f__buf;
! 	te = t + c;
! 	while(t < te)
! 		*s++ = *t++;
! 	if (f__buf != f__buf0)
! 		free(f__buf);
! 	f__buf = nbuf;
! 	}
  
!  int
! #ifdef KR_headers
! f__putbuf(c) int c;
! #else
! f__putbuf(int c)
! #endif
  {
! 	char *s, *se;
! 	int n;
  
! 	if (f__hiwater > f__recpos)
! 		f__recpos = f__hiwater;
! 	n = f__recpos + 1;
! 	if (n >= f__buflen)
! 		f__bufadj(n, f__recpos);
! 	s = f__buf;
! 	se = s + f__recpos;
! 	if (c)
! 		*se++ = c;
! 	*se = 0;
! 	for(;;) {
! 		fputs(s, f__cf);
! 		s += strlen(s);
! 		if (s >= se)
! 			break;	/* normally happens the first time */
! 		putc(*s++, f__cf);
! 		}
! 	return 0;
! 	}
  
!  void
! #ifdef KR_headers
! x_putc(c)
! #else
! x_putc(int c)
! #endif
  {
! 	if (f__recpos >= f__buflen)
! 		f__bufadj(f__recpos, f__buflen);
! 	f__buf[f__recpos++] = c;
! 	}
  
  #define opnerr(f,m,s) \
    do {if(f) {f__init &= ~2; errno= m;} else opn_err(m,s,a); return(m);} while(0)
  
!  static void
! #ifdef KR_headers
! opn_err(m, s, a) int m; char *s; olist *a;
! #else
! opn_err(int m, char *s, olist *a)
! #endif
  {
! 	if (a->ofnm) {
! 		/* supply file name to error message */
! 		if (a->ofnmlen >= f__buflen)
! 			f__bufadj((int)a->ofnmlen, 0);
! 		g_char(a->ofnm, a->ofnmlen, f__curunit->ufnm = f__buf);
! 		}
! 	f__fatal(m, s);
! 	}
  
! #ifdef KR_headers
! integer f_open(a) olist *a;
! #else
! integer f_open(olist *a)
! #endif
! {	unit *b;
! 	integer rv;
! 	char buf[256], *s, *env;
! 	cllist x;
! 	int ufmt;
! 	FILE *tf;
! 	int fd, len;
  #ifndef NON_UNIX_STDIO
! 	int n;
  #endif
! 	if(f__init != 1) f_init();
! 	f__external = 1;
! 	if(a->ounit>=MXUNIT || a->ounit<0)
! 		err(a->oerr,101,"open");
! 	f__curunit = b = &f__units[a->ounit];
! 	if(b->ufd) {
! 		if(a->ofnm==0)
! 		{
! 		same:	if (a->oblnk)
! 				b->ublnk = *a->oblnk == 'z' || *a->oblnk == 'Z';
! 			return(0);
! 		}
  #ifdef NON_UNIX_STDIO
! 		if (b->ufnm
! 		 && strlen(b->ufnm) == a->ofnmlen
! 		 && !strncmp(b->ufnm, a->ofnm, (unsigned)a->ofnmlen))
! 			goto same;
  #else
! 		g_char(a->ofnm,a->ofnmlen,buf);
! 		if (f__inode(buf,&n) == b->uinode && n == b->udev)
! 			goto same;
  #endif
! 		x.cunit=a->ounit;
! 		x.csta=0;
! 		x.cerr=a->oerr;
! 		if ((rv = f_clos(&x)) != 0)
! 			return rv;
! 		}
! 	b->url = (int)a->orl;
! 	b->ublnk = a->oblnk && (*a->oblnk == 'z' || *a->oblnk == 'Z');
! 	if(a->ofm==0)
! 	{	if(b->url>0) b->ufmt=0;
! 		else b->ufmt=1;
! 	}
! 	else if(*a->ofm=='f' || *a->ofm == 'F') b->ufmt=1;
! 	else b->ufmt=0;
! 	ufmt = b->ufmt;
  #ifdef url_Adjust
! 	if (b->url && !ufmt)
! 		url_Adjust(b->url);
  #endif
! 	if (a->ofnm) {
! 		g_char(a->ofnm,a->ofnmlen,buf);
! 		if (!buf[0])
! 			opnerr(a->oerr,107,"open");
! 		}
! 	else
! 		sprintf(buf, "fort.%ld", (long)a->ounit);
! 	b->uscrtch = 0;
! 	b->uend=0;
! 	b->uwrt = 0;
! 	b->ufd = 0;
! 	b->urw = 3;
! 	switch(a->osta ? *a->osta : 'u')
! 	{
! 	case 'o':
! 	case 'O':
  #ifdef NON_POSIX_STDIO
! 		if (!(tf = fopen(buf,"r")))
! 			opnerr(a->oerr,errno,"open");
! 		fclose(tf);
  #else
! 		if (access(buf,0))
! 			opnerr(a->oerr,errno,"open");
  #endif
! 		break;
! 	 case 's':
! 	 case 'S':
! 		b->uscrtch=1;
! #ifdef HAVE_MKSTEMP             /* Allow use of TMPDIR preferentially. */
! 		env = getenv("TMPDIR");
! 		if (!env) env = getenv("TEMP");
! 		if (!env) env = "/tmp";
! 		len = strlen(env);
! 		if (len > 256 - sizeof "/tmp.FXXXXXX")
! 		  err (a->oerr, 132, "open");
! 		strcpy(buf, env);
! 		strcat(buf, "/tmp.FXXXXXX");
! 		fd = mkstemp(buf);
! 		if (fd == -1 || close(fd))
! 		  err (a->oerr, 132, "open");
  #else /* ! defined (HAVE_MKSTEMP) */
  #ifdef HAVE_TEMPNAM		/* Allow use of TMPDIR preferentially. */
! 		s = tempnam (0, buf);
! 		if (strlen (s) >= sizeof (buf))
! 		  err (a->oerr, 132, "open");
! 		(void) strcpy (buf, s);
! 		free (s);
  #else /* ! defined (HAVE_TEMPNAM) */
  #ifdef HAVE_TMPNAM
! 		tmpnam(buf);
  #else
! 		(void) strcpy(buf,"tmp.FXXXXXX");
! 		(void) mktemp(buf);
  #endif
  #endif /* ! defined (HAVE_TEMPNAM) */
  #endif /* ! defined (HAVE_MKSTEMP) */
! 		goto replace;
! 	case 'n':
! 	case 'N':
  #ifdef NON_POSIX_STDIO
! 		if ((tf = fopen(buf,"r")) || (tf = fopen(buf,"a"))) {
! 			fclose(tf);
! 			opnerr(a->oerr,128,"open");
! 			}
  #else
! 		if (!access(buf,0))
! 			opnerr(a->oerr,128,"open");
  #endif
! 		/* no break */
! 	case 'r':	/* Fortran 90 replace option */
! 	case 'R':
!  replace:
! 		if (tf = fopen(buf,f__w_mode[0]))
! 			fclose(tf);
! 	}
  
! 	b->ufnm=(char *) malloc((unsigned int)(strlen(buf)+1));
! 	if(b->ufnm==NULL) opnerr(a->oerr,113,"no space");
! 	(void) strcpy(b->ufnm,buf);
! 	if ((s = a->oacc) && b->url)
! 		ufmt = 0;
! 	if(!(tf = fopen(buf, f__w_mode[ufmt|2]))) {
! 		if (tf = fopen(buf, f__r_mode[ufmt]))
! 			b->urw = 1;
! 		else if (tf = fopen(buf, f__w_mode[ufmt])) {
! 			b->uwrt = 1;
! 			b->urw = 2;
! 			}
! 		else
! 			err(a->oerr, errno, "open");
! 		}
! 	b->useek = f__canseek(b->ufd = tf);
  #ifndef NON_UNIX_STDIO
! 	if((b->uinode = f__inode(buf,&b->udev)) == -1)
! 		opnerr(a->oerr,108,"open");
  #endif
! 	if(b->useek)
! 		if (a->orl)
! 			FSEEK(b->ufd, 0, SEEK_SET);
! 		else if ((s = a->oacc) && (*s == 'a' || *s == 'A')
! 			&& FSEEK(b->ufd, 0, SEEK_END))
! 				opnerr(a->oerr,129,"open");
! 	return(0);
  }
- #ifdef KR_headers
- fk_open(seq,fmt,n) ftnint n;
- #else
- fk_open(int seq, int fmt, ftnint n)
- #endif
- {	char nbuf[10];
- 	olist a;
- 	int rtn;
- 	int save_init;
  
! 	(void) sprintf(nbuf,"fort.%ld",(long)n);
! 	a.oerr=1;
! 	a.ounit=n;
! 	a.ofnm=nbuf;
! 	a.ofnmlen=strlen(nbuf);
! 	a.osta=NULL;
! 	a.oacc= seq==SEQ?"s":"d";
! 	a.ofm = fmt==FMT?"f":"u";
! 	a.orl = seq==DIR?1:0;
! 	a.oblnk=NULL;
! 	save_init = f__init;
! 	f__init &= ~2;
! 	rtn = f_open(&a);
! 	f__init = save_init | 1;
! 	return rtn;
  }
--- 6,301 ----
  #ifdef MSDOS
  #include "io.h"
  #else
! #include "unistd.h"		/* for access */
  #endif
  #endif
  
  #undef abs
  #undef min
  #undef max
  #include <stdlib.h>
! extern int f__canseek (FILE *);
! extern integer f_clos (cllist *);
  
  #ifdef NON_ANSI_RW_MODES
! char *f__r_mode[2] = { "r", "r" };
! char *f__w_mode[4] = { "w", "w", "r+w", "r+w" };
  #else
! char *f__r_mode[2] = { "rb", "r" };
! char *f__w_mode[4] = { "wb", "w", "r+b", "r+" };
  #endif
  
! static char f__buf0[400], *f__buf = f__buf0;
! int f__buflen = (int) sizeof (f__buf0);
  
! static void
! f__bufadj (int n, int c)
  {
!   unsigned int len;
!   char *nbuf, *s, *t, *te;
  
!   if (f__buf == f__buf0)
!     f__buflen = 1024;
!   while (f__buflen <= n)
!     f__buflen <<= 1;
!   len = (unsigned int) f__buflen;
!   if (len != f__buflen || !(nbuf = (char *) malloc (len)))
!     f__fatal (113, "malloc failure");
!   s = nbuf;
!   t = f__buf;
!   te = t + c;
!   while (t < te)
!     *s++ = *t++;
!   if (f__buf != f__buf0)
!     free (f__buf);
!   f__buf = nbuf;
! }
  
! int
! f__putbuf (int c)
  {
!   char *s, *se;
!   int n;
  
!   if (f__hiwater > f__recpos)
!     f__recpos = f__hiwater;
!   n = f__recpos + 1;
!   if (n >= f__buflen)
!     f__bufadj (n, f__recpos);
!   s = f__buf;
!   se = s + f__recpos;
!   if (c)
!     *se++ = c;
!   *se = 0;
!   for (;;)
!     {
!       fputs (s, f__cf);
!       s += strlen (s);
!       if (s >= se)
! 	break;			/* normally happens the first time */
!       putc (*s++, f__cf);
!     }
!   return 0;
! }
  
! void
! x_putc (int c)
  {
!   if (f__recpos >= f__buflen)
!     f__bufadj (f__recpos, f__buflen);
!   f__buf[f__recpos++] = c;
! }
  
  #define opnerr(f,m,s) \
    do {if(f) {f__init &= ~2; errno= m;} else opn_err(m,s,a); return(m);} while(0)
  
! static void
! opn_err (int m, char *s, olist * a)
  {
!   if (a->ofnm)
!     {
!       /* supply file name to error message */
!       if (a->ofnmlen >= f__buflen)
! 	f__bufadj ((int) a->ofnmlen, 0);
!       g_char (a->ofnm, a->ofnmlen, f__curunit->ufnm = f__buf);
!     }
!   f__fatal (m, s);
! }
  
! integer
! f_open (olist * a)
! {
!   unit *b;
!   integer rv;
!   char buf[256], *s, *env;
!   cllist x;
!   int ufmt;
!   FILE *tf;
!   int fd, len;
  #ifndef NON_UNIX_STDIO
!   int n;
  #endif
!   if (f__init != 1)
!     f_init ();
!   f__external = 1;
!   if (a->ounit >= MXUNIT || a->ounit < 0)
!     err (a->oerr, 101, "open");
!   f__curunit = b = &f__units[a->ounit];
!   if (b->ufd)
!     {
!       if (a->ofnm == 0)
! 	{
! 	same:if (a->oblnk)
! 	    b->ublnk = *a->oblnk == 'z' || *a->oblnk == 'Z';
! 	  return (0);
! 	}
  #ifdef NON_UNIX_STDIO
!       if (b->ufnm
! 	  && strlen (b->ufnm) == a->ofnmlen
! 	  && !strncmp (b->ufnm, a->ofnm, (unsigned) a->ofnmlen))
! 	goto same;
  #else
!       g_char (a->ofnm, a->ofnmlen, buf);
!       if (f__inode (buf, &n) == b->uinode && n == b->udev)
! 	goto same;
  #endif
!       x.cunit = a->ounit;
!       x.csta = 0;
!       x.cerr = a->oerr;
!       if ((rv = f_clos (&x)) != 0)
! 	return rv;
!     }
!   b->url = (int) a->orl;
!   b->ublnk = a->oblnk && (*a->oblnk == 'z' || *a->oblnk == 'Z');
!   if (a->ofm == 0)
!     if ((a->oacc) && (*a->oacc == 'D' || *a->oacc == 'd'))
!       b->ufmt = 0;
!     else
!       b->ufmt = 1;
!   else if (*a->ofm == 'f' || *a->ofm == 'F')
!     b->ufmt = 1;
!   else
!     b->ufmt = 0;
!   ufmt = b->ufmt;
  #ifdef url_Adjust
!   if (b->url && !ufmt)
!     url_Adjust (b->url);
  #endif
!   if (a->ofnm)
!     {
!       g_char (a->ofnm, a->ofnmlen, buf);
!       if (!buf[0])
! 	opnerr (a->oerr, 107, "open");
!     }
!   else
!     sprintf (buf, "fort.%ld", (long) a->ounit);
!   b->uscrtch = 0;
!   b->uend = 0;
!   b->uwrt = 0;
!   b->ufd = 0;
!   b->urw = 3;
!   switch (a->osta ? *a->osta : 'u')
!     {
!     case 'o':
!     case 'O':
  #ifdef NON_POSIX_STDIO
!       if (!(tf = fopen (buf, "r")))
! 	opnerr (a->oerr, errno, "open");
!       fclose (tf);
  #else
!       if (access (buf, 0))
! 	opnerr (a->oerr, errno, "open");
  #endif
!       break;
!     case 's':
!     case 'S':
!       b->uscrtch = 1;
! #ifdef HAVE_MKSTEMP		/* Allow use of TMPDIR preferentially. */
!       env = getenv ("TMPDIR");
!       if (!env)
! 	env = getenv ("TEMP");
!       if (!env)
! 	env = "/tmp";
!       len = strlen (env);
!       if (len > 256 - (int) sizeof ("/tmp.FXXXXXX"))
! 	err (a->oerr, 132, "open");
!       strcpy (buf, env);
!       strcat (buf, "/tmp.FXXXXXX");
!       fd = mkstemp (buf);
!       if (fd == -1 || close (fd))
! 	err (a->oerr, 132, "open");
  #else /* ! defined (HAVE_MKSTEMP) */
  #ifdef HAVE_TEMPNAM		/* Allow use of TMPDIR preferentially. */
!       s = tempnam (0, buf);
!       if (strlen (s) >= sizeof (buf))
! 	err (a->oerr, 132, "open");
!       (void) strcpy (buf, s);
!       free (s);
  #else /* ! defined (HAVE_TEMPNAM) */
  #ifdef HAVE_TMPNAM
!       tmpnam (buf);
  #else
!       (void) strcpy (buf, "tmp.FXXXXXX");
!       (void) mktemp (buf);
  #endif
  #endif /* ! defined (HAVE_TEMPNAM) */
  #endif /* ! defined (HAVE_MKSTEMP) */
!       goto replace;
!     case 'n':
!     case 'N':
  #ifdef NON_POSIX_STDIO
!       if ((tf = fopen (buf, "r")) || (tf = fopen (buf, "a")))
! 	{
! 	  fclose (tf);
! 	  opnerr (a->oerr, 128, "open");
! 	}
  #else
!       if (!access (buf, 0))
! 	opnerr (a->oerr, 128, "open");
  #endif
!       /* no break */
!     case 'r':			/* Fortran 90 replace option */
!     case 'R':
!     replace:
!       if ((tf = fopen (buf, f__w_mode[0])))
! 	fclose (tf);
!     }
  
!   b->ufnm = (char *) malloc ((unsigned int) (strlen (buf) + 1));
!   if (b->ufnm == NULL)
!     opnerr (a->oerr, 113, "no space");
!   (void) strcpy (b->ufnm, buf);
!   if ((s = a->oacc) && b->url)
!     ufmt = 0;
!   if (!(tf = fopen (buf, f__w_mode[ufmt | 2])))
!     {
!       if ((tf = fopen (buf, f__r_mode[ufmt])))
! 	b->urw = 1;
!       else if ((tf = fopen (buf, f__w_mode[ufmt])))
! 	{
! 	  b->uwrt = 1;
! 	  b->urw = 2;
! 	}
!       else
! 	err (a->oerr, errno, "open");
!     }
!   b->useek = f__canseek (b->ufd = tf);
  #ifndef NON_UNIX_STDIO
!   if ((b->uinode = f__inode (buf, &b->udev)) == -1)
!     opnerr (a->oerr, 108, "open");
  #endif
!   if (b->useek)
!     {
!       if (a->orl)
! 	FSEEK (b->ufd, 0, SEEK_SET);
!       else if ((s = a->oacc) && (*s == 'a' || *s == 'A')
! 	       && FSEEK (b->ufd, 0, SEEK_END))
! 	opnerr (a->oerr, 129, "open");
!     }
!   return (0);
  }
  
! int
! fk_open (int seq, int fmt, ftnint n)
! {
!   char nbuf[10];
!   olist a;
!   int rtn;
!   int save_init;
! 
!   (void) sprintf (nbuf, "fort.%ld", (long) n);
!   a.oerr = 1;
!   a.ounit = n;
!   a.ofnm = nbuf;
!   a.ofnmlen = strlen (nbuf);
!   a.osta = NULL;
!   a.oacc = seq == SEQ ? "s" : "d";
!   a.ofm = fmt == FMT ? "f" : "u";
!   a.orl = seq == DIR ? 1 : 0;
!   a.oblnk = NULL;
!   save_init = f__init;
!   f__init &= ~2;
!   rtn = f_open (&a);
!   f__init = save_init | 1;
!   return rtn;
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libI77/rdfmt.c gcc-3.3/libf2c/libI77/rdfmt.c
*** gcc-3.2.3/libf2c/libI77/rdfmt.c	2001-07-06 12:09:39.000000000 +0000
--- gcc-3.3/libf2c/libI77/rdfmt.c	2002-06-04 02:24:26.000000000 +0000
***************
*** 4,546 ****
  #include "fio.h"
  
  extern int f__cursor;
- #ifdef KR_headers
- extern double atof();
- #else
  #undef abs
  #undef min
  #undef max
  #include <stdlib.h>
- #endif
  
  #include "fmt.h"
  #include "fp.h"
  
!  static int
! #ifdef KR_headers
! rd_Z(n,w,len) Uint *n; ftnlen len;
! #else
! rd_Z(Uint *n, int w, ftnlen len)
! #endif
  {
! 	long x[9];
! 	char *s, *s0, *s1, *se, *t;
! 	int ch, i, w1, w2;
! 	static char hex[256];
! 	static int one = 1;
! 	int bad = 0;
  
! 	if (!hex['0']) {
! 		s = "0123456789";
! 		while(ch = *s++)
! 			hex[ch] = ch - '0' + 1;
! 		s = "ABCDEF";
! 		while(ch = *s++)
! 			hex[ch] = hex[ch + 'a' - 'A'] = ch - 'A' + 11;
! 		}
! 	s = s0 = (char *)x;
! 	s1 = (char *)&x[4];
! 	se = (char *)&x[8];
! 	if (len > 4*sizeof(long))
! 		return errno = 117;
! 	while (w) {
! 		GET(ch);
! 		if (ch==',' || ch=='\n')
! 			break;
! 		w--;
! 		if (ch > ' ') {
! 			if (!hex[ch & 0xff])
! 				bad++;
! 			*s++ = ch;
! 			if (s == se) {
! 				/* discard excess characters */
! 				for(t = s0, s = s1; t < s1;)
! 					*t++ = *s++;
! 				s = s1;
! 				}
! 			}
! 		}
! 	if (bad)
! 		return errno = 115;
! 	w = (int)len;
! 	w1 = s - s0;
! 	w2 = w1+1 >> 1;
! 	t = (char *)n;
! 	if (*(char *)&one) {
! 		/* little endian */
! 		t += w - 1;
! 		i = -1;
! 		}
! 	else
! 		i = 1;
! 	for(; w > w2; t += i, --w)
! 		*t = 0;
! 	if (!w)
! 		return 0;
! 	if (w < w2)
! 		s0 = s - (w << 1);
! 	else if (w1 & 1) {
! 		*t = hex[*s0++ & 0xff] - 1;
! 		if (!--w)
! 			return 0;
! 		t += i;
! 		}
! 	do {
! 		*t = hex[*s0 & 0xff]-1 << 4 | hex[s0[1] & 0xff]-1;
! 		t += i;
! 		s0 += 2;
! 		}
! 		while(--w);
! 	return 0;
  	}
  
!  static int
! #ifdef KR_headers
! rd_I(n,w,len, base) Uint *n; int w; ftnlen len; register int base;
! #else
! rd_I(Uint *n, int w, ftnlen len, register int base)
! #endif
  {
! 	int bad, ch, sign;
! 	longint x = 0;
  
! 	if (w <= 0)
! 		goto have_x;
! 	for(;;) {
! 		GET(ch);
! 		if (ch != ' ')
! 			break;
! 		if (!--w)
! 			goto have_x;
! 		}
! 	sign = 0;
! 	switch(ch) {
! 	  case ',':
! 	  case '\n':
! 		w = 0;
! 		goto have_x;
! 	  case '-':
! 		sign = 1;
! 	  case '+':
! 		break;
! 	  default:
! 		if (ch >= '0' && ch <= '9') {
! 			x = ch - '0';
! 			break;
! 			}
! 		goto have_x;
! 		}
! 	while(--w) {
! 		GET(ch);
! 		if (ch >= '0' && ch <= '9') {
! 			x = x*base + ch - '0';
! 			continue;
! 			}
! 		if (ch != ' ') {
! 			if (ch == '\n' || ch == ',')
! 				w = 0;
! 			break;
! 			}
! 		if (f__cblank)
! 			x *= base;
! 		}
! 	if (sign)
! 		x = -x;
!  have_x:
! 	if(len == sizeof(integer))
! 		n->il=x;
! 	else if(len == sizeof(char))
! 		n->ic = (char)x;
  #ifdef Allow_TYQUAD
! 	else if (len == sizeof(longint))
! 		n->ili = x;
  #endif
! 	else
! 		n->is = (short)x;
! 	if (w) {
! 		while(--w)
! 			GET(ch);
! 		return errno = 115;
! 		}
! 	return 0;
  }
  
!  static int
! #ifdef KR_headers
! rd_L(n,w,len) ftnint *n; ftnlen len;
! #else
! rd_L(ftnint *n, int w, ftnlen len)
! #endif
! {	int ch, dot, lv;
  
! 	if (w <= 0)
! 		goto bad;
! 	for(;;) {
! 		GET(ch);
! 		--w;
! 		if (ch != ' ')
! 			break;
! 		if (!w)
! 			goto bad;
! 		}
! 	dot = 0;
!  retry:
! 	switch(ch) {
! 	  case '.':
! 		if (dot++ || !w)
! 			goto bad;
! 		GET(ch);
! 		--w;
! 		goto retry;
! 	  case 't':
! 	  case 'T':
! 		lv = 1;
! 		break;
! 	  case 'f':
! 	  case 'F':
! 		lv = 0;
! 		break;
! 	  default:
!  bad:
! 		for(; w > 0; --w)
! 			GET(ch);
! 		/* no break */
! 	  case ',':
! 	  case '\n':
! 		return errno = 116;
! 		}
! 	/* The switch statement that was here
! 	   didn't cut it:  It broke down for targets
! 	   where sizeof(char) == sizeof(short). */
! 	if (len == sizeof(char))
! 		*(char *)n = (char)lv;
! 	else if (len == sizeof(short))
! 		*(short *)n = (short)lv;
! 	else
! 		*n = lv;
! 	while(w-- > 0) {
! 		GET(ch);
! 		if (ch == ',' || ch == '\n')
! 			break;
! 		}
! 	return 0;
  }
  
!  static int
! #ifdef KR_headers
! rd_F(p, w, d, len) ufloat *p; ftnlen len;
! #else
! rd_F(ufloat *p, int w, int d, ftnlen len)
! #endif
  {
! 	char s[FMAX+EXPMAXDIGS+4];
! 	register int ch;
! 	register char *sp, *spe, *sp1;
! 	double x;
! 	int scale1, se;
! 	long e, exp;
  
! 	sp1 = sp = s;
! 	spe = sp + FMAX;
! 	exp = -d;
! 	x = 0.;
  
! 	do {
! 		GET(ch);
! 		w--;
! 		} while (ch == ' ' && w);
! 	switch(ch) {
! 		case '-': *sp++ = ch; sp1++; spe++;
! 		case '+':
! 			if (!w) goto zero;
! 			--w;
! 			GET(ch);
! 		}
! 	while(ch == ' ') {
! blankdrop:
! 		if (!w--) goto zero; GET(ch); }
! 	while(ch == '0')
! 		{ if (!w--) goto zero; GET(ch); }
! 	if (ch == ' ' && f__cblank)
! 		goto blankdrop;
! 	scale1 = f__scale;
! 	while(isdigit(ch)) {
! digloop1:
! 		if (sp < spe) *sp++ = ch;
! 		else ++exp;
! digloop1e:
! 		if (!w--) goto done;
! 		GET(ch);
! 		}
! 	if (ch == ' ') {
! 		if (f__cblank)
! 			{ ch = '0'; goto digloop1; }
! 		goto digloop1e;
! 		}
! 	if (ch == '.') {
! 		exp += d;
! 		if (!w--) goto done;
! 		GET(ch);
! 		if (sp == sp1) { /* no digits yet */
! 			while(ch == '0') {
! skip01:
! 				--exp;
! skip0:
! 				if (!w--) goto done;
! 				GET(ch);
! 				}
! 			if (ch == ' ') {
! 				if (f__cblank) goto skip01;
! 				goto skip0;
! 				}
! 			}
! 		while(isdigit(ch)) {
! digloop2:
! 			if (sp < spe)
! 				{ *sp++ = ch; --exp; }
! digloop2e:
! 			if (!w--) goto done;
! 			GET(ch);
! 			}
! 		if (ch == ' ') {
! 			if (f__cblank)
! 				{ ch = '0'; goto digloop2; }
! 			goto digloop2e;
! 			}
! 		}
! 	switch(ch) {
! 	  default:
! 		break;
! 	  case '-': se = 1; goto signonly;
! 	  case '+': se = 0; goto signonly;
! 	  case 'e':
! 	  case 'E':
! 	  case 'd':
! 	  case 'D':
! 		if (!w--)
! 			goto bad;
! 		GET(ch);
! 		while(ch == ' ') {
! 			if (!w--)
! 				goto bad;
! 			GET(ch);
! 			}
! 		se = 0;
! 	  	switch(ch) {
! 		  case '-': se = 1;
! 		  case '+':
! signonly:
! 			if (!w--)
! 				goto bad;
! 			GET(ch);
! 			}
! 		while(ch == ' ') {
! 			if (!w--)
! 				goto bad;
! 			GET(ch);
! 			}
! 		if (!isdigit(ch))
! 			goto bad;
  
! 		e = ch - '0';
! 		for(;;) {
! 			if (!w--)
! 				{ ch = '\n'; break; }
! 			GET(ch);
! 			if (!isdigit(ch)) {
! 				if (ch == ' ') {
! 					if (f__cblank)
! 						ch = '0';
! 					else continue;
! 					}
! 				else
! 					break;
! 				}
! 			e = 10*e + ch - '0';
! 			if (e > EXPMAX && sp > sp1)
! 				goto bad;
! 			}
! 		if (se)
! 			exp -= e;
! 		else
! 			exp += e;
! 		scale1 = 0;
  		}
! 	switch(ch) {
! 	  case '\n':
! 	  case ',':
  		break;
! 	  default:
! bad:
! 		return (errno = 115);
! 		}
  done:
! 	if (sp > sp1) {
! 		while(*--sp == '0')
! 			++exp;
! 		if (exp -= scale1)
! 			sprintf(sp+1, "e%ld", exp);
! 		else
! 			sp[1] = 0;
! 		x = atof(s);
! 		}
  zero:
! 	if (len == sizeof(real))
! 		p->pf = x;
! 	else
! 		p->pd = x;
! 	return(0);
! 	}
  
  
!  static int
! #ifdef KR_headers
! rd_A(p,len) char *p; ftnlen len;
! #else
! rd_A(char *p, ftnlen len)
! #endif
! {	int i,ch;
! 	for(i=0;i<len;i++)
! 	{	GET(ch);
! 		*p++=VAL(ch);
! 	}
! 	return(0);
  }
!  static int
! #ifdef KR_headers
! rd_AW(p,w,len) char *p; ftnlen len;
! #else
! rd_AW(char *p, int w, ftnlen len)
! #endif
! {	int i,ch;
! 	if(w>=len)
! 	{	for(i=0;i<w-len;i++)
! 			GET(ch);
! 		for(i=0;i<len;i++)
! 		{	GET(ch);
! 			*p++=VAL(ch);
! 		}
! 		return(0);
! 	}
! 	for(i=0;i<w;i++)
! 	{	GET(ch);
! 		*p++=VAL(ch);
  	}
! 	for(i=0;i<len-w;i++) *p++=' ';
! 	return(0);
  }
!  static int
! #ifdef KR_headers
! rd_H(n,s) char *s;
! #else
! rd_H(int n, char *s)
! #endif
! {	int i,ch;
! 	for(i=0;i<n;i++)
! 		if((ch=(*f__getn)())<0) return(ch);
! 		else *s++ = ch=='\n'?' ':ch;
! 	return(1);
  }
!  static int
! #ifdef KR_headers
! rd_POS(s) char *s;
! #else
! rd_POS(char *s)
! #endif
! {	char quote;
! 	int ch;
! 	quote= *s++;
! 	for(;*s;s++)
! 		if(*s==quote && *(s+1)!=quote) break;
! 		else if((ch=(*f__getn)())<0) return(ch);
! 		else *s = ch=='\n'?' ':ch;
! 	return(1);
  }
! #ifdef KR_headers
! rd_ed(p,ptr,len) struct syl *p; char *ptr; ftnlen len;
! #else
! rd_ed(struct syl *p, char *ptr, ftnlen len)
! #endif
! {	int ch;
! 	for(;f__cursor>0;f__cursor--) if((ch=(*f__getn)())<0) return(ch);
! 	if(f__cursor<0)
! 	{	if(f__recpos+f__cursor < 0) /*err(elist->cierr,110,"fmt")*/
! 			f__cursor = -f__recpos;	/* is this in the standard? */
! 		if(f__external == 0) {
! 			extern char *f__icptr;
! 			f__icptr += f__cursor;
! 		}
! 		else if(f__curunit && f__curunit->useek)
! 			FSEEK(f__cf,(off_t)f__cursor,SEEK_CUR);
! 		else
! 			err(f__elist->cierr,106,"fmt");
! 		f__recpos += f__cursor;
! 		f__cursor=0;
! 	}
! 	switch(p->op)
  	{
! 	default: fprintf(stderr,"rd_ed, unexpected code: %d\n", p->op);
! 		sig_die(f__fmtbuf, 1);
! 	case IM:
! 	case I: ch = rd_I((Uint *)ptr,p->p1,len, 10);
! 		break;
  
! 		/* O and OM don't work right for character, double, complex, */
! 		/* or doublecomplex, and they differ from Fortran 90 in */
! 		/* showing a minus sign for negative values. */
  
! 	case OM:
! 	case O: ch = rd_I((Uint *)ptr, p->p1, len, 8);
! 		break;
! 	case L: ch = rd_L((ftnint *)ptr,p->p1,len);
! 		break;
! 	case A:	ch = rd_A(ptr,len);
! 		break;
! 	case AW:
! 		ch = rd_AW(ptr,p->p1,len);
! 		break;
! 	case E: case EE:
! 	case D:
! 	case G:
! 	case GE:
! 	case F:	ch = rd_F((ufloat *)ptr,p->p1,p->p2.i[0],len);
! 		break;
  
! 		/* Z and ZM assume 8-bit bytes. */
  
! 	case ZM:
! 	case Z:
! 		ch = rd_Z((Uint *)ptr, p->p1, len);
! 		break;
! 	}
! 	if(ch == 0) return(ch);
! 	else if(ch == EOF) return(EOF);
! 	if (f__cf)
! 		clearerr(f__cf);
! 	return(errno);
  }
! #ifdef KR_headers
! rd_ned(p) struct syl *p;
! #else
! rd_ned(struct syl *p)
! #endif
  {
! 	switch(p->op)
! 	{
! 	default: fprintf(stderr,"rd_ned, unexpected code: %d\n", p->op);
! 		sig_die(f__fmtbuf, 1);
! 	case APOS:
! 		return(rd_POS(p->p2.s));
! 	case H:	return(rd_H(p->p1,p->p2.s));
! 	case SLASH: return((*f__donewrec)());
! 	case TR:
! 	case X:	f__cursor += p->p1;
! 		return(1);
! 	case T: f__cursor=p->p1-f__recpos - 1;
! 		return(1);
! 	case TL: f__cursor -= p->p1;
! 		if(f__cursor < -f__recpos)	/* TL1000, 1X */
! 			f__cursor = -f__recpos;
! 		return(1);
! 	}
  }
--- 4,615 ----
  #include "fio.h"
  
  extern int f__cursor;
  #undef abs
  #undef min
  #undef max
  #include <stdlib.h>
  
  #include "fmt.h"
  #include "fp.h"
  
! static int
! rd_Z (Uint * n, int w, ftnlen len)
  {
!   long x[9];
!   char *s, *s0, *s1, *se, *t;
!   int ch, i, w1, w2;
!   static char hex[256];
!   static int one = 1;
!   int bad = 0;
  
!   if (!hex['0'])
!     {
!       s = "0123456789";
!       while ((ch = *s++))
! 	hex[ch] = ch - '0' + 1;
!       s = "ABCDEF";
!       while ((ch = *s++))
! 	hex[ch] = hex[ch + 'a' - 'A'] = ch - 'A' + 11;
!     }
!   s = s0 = (char *) x;
!   s1 = (char *) &x[4];
!   se = (char *) &x[8];
!   if (len > 4 * (ftnlen) sizeof (long))
!     return errno = 117;
!   while (w)
!     {
!       GET (ch);
!       if (ch == ',' || ch == '\n')
! 	break;
!       w--;
!       if (ch > ' ')
! 	{
! 	  if (!hex[ch & 0xff])
! 	    bad++;
! 	  *s++ = ch;
! 	  if (s == se)
! 	    {
! 	      /* discard excess characters */
! 	      for (t = s0, s = s1; t < s1;)
! 		*t++ = *s++;
! 	      s = s1;
! 	    }
  	}
+     }
+   if (bad)
+     return errno = 115;
+   w = (int) len;
+   w1 = s - s0;
+   w2 = (w1 + 1) >> 1;
+   t = (char *) n;
+   if (*(char *) &one)
+     {
+       /* little endian */
+       t += w - 1;
+       i = -1;
+     }
+   else
+     i = 1;
+   for (; w > w2; t += i, --w)
+     *t = 0;
+   if (!w)
+     return 0;
+   if (w < w2)
+     s0 = s - (w << 1);
+   else if (w1 & 1)
+     {
+       *t = hex[*s0++ & 0xff] - 1;
+       if (!--w)
+ 	return 0;
+       t += i;
+     }
+   do
+     {
+       *t = (hex[*s0 & 0xff] - 1) << 4 | (hex[s0[1] & 0xff] - 1);
+       t += i;
+       s0 += 2;
+     }
+   while (--w);
+   return 0;
+ }
  
! static int
! rd_I (Uint * n, int w, ftnlen len, register int base)
  {
!   int ch, sign;
!   longint x = 0;
  
!   if (w <= 0)
!     goto have_x;
!   for (;;)
!     {
!       GET (ch);
!       if (ch != ' ')
! 	break;
!       if (!--w)
! 	goto have_x;
!     }
!   sign = 0;
!   switch (ch)
!     {
!     case ',':
!     case '\n':
!       w = 0;
!       goto have_x;
!     case '-':
!       sign = 1;
!     case '+':
!       break;
!     default:
!       if (ch >= '0' && ch <= '9')
! 	{
! 	  x = ch - '0';
! 	  break;
! 	}
!       goto have_x;
!     }
!   while (--w)
!     {
!       GET (ch);
!       if (ch >= '0' && ch <= '9')
! 	{
! 	  x = x * base + ch - '0';
! 	  continue;
! 	}
!       if (ch != ' ')
! 	{
! 	  if (ch == '\n' || ch == ',')
! 	    w = 0;
! 	  break;
! 	}
!       if (f__cblank)
! 	x *= base;
!     }
!   if (sign)
!     x = -x;
! have_x:
!   if (len == sizeof (integer))
!     n->il = x;
!   else if (len == sizeof (char))
!     n->ic = (char) x;
  #ifdef Allow_TYQUAD
!   else if (len == sizeof (longint))
!     n->ili = x;
  #endif
!   else
!     n->is = (short) x;
!   if (w)
!     {
!       while (--w)
! 	GET (ch);
!       return errno = 115;
!     }
!   return 0;
  }
  
! static int
! rd_L (ftnint * n, int w, ftnlen len)
! {
!   int ch, dot, lv;
  
!   if (w <= 0)
!     goto bad;
!   for (;;)
!     {
!       GET (ch);
!       --w;
!       if (ch != ' ')
! 	break;
!       if (!w)
! 	goto bad;
!     }
!   dot = 0;
! retry:
!   switch (ch)
!     {
!     case '.':
!       if (dot++ || !w)
! 	goto bad;
!       GET (ch);
!       --w;
!       goto retry;
!     case 't':
!     case 'T':
!       lv = 1;
!       break;
!     case 'f':
!     case 'F':
!       lv = 0;
!       break;
!     default:
!     bad:
!       for (; w > 0; --w)
! 	GET (ch);
!       /* no break */
!     case ',':
!     case '\n':
!       return errno = 116;
!     }
!   /* The switch statement that was here
!      didn't cut it:  It broke down for targets
!      where sizeof(char) == sizeof(short). */
!   if (len == sizeof (char))
!     *(char *) n = (char) lv;
!   else if (len == sizeof (short))
!     *(short *) n = (short) lv;
!   else
!     *n = lv;
!   while (w-- > 0)
!     {
!       GET (ch);
!       if (ch == ',' || ch == '\n')
! 	break;
!     }
!   return 0;
  }
  
! static int
! rd_F (ufloat * p, int w, int d, ftnlen len)
  {
!   char s[FMAX + EXPMAXDIGS + 4];
!   register int ch;
!   register char *sp, *spe, *sp1;
!   double x;
!   int scale1, se;
!   long e, exp;
  
!   sp1 = sp = s;
!   spe = sp + FMAX;
!   exp = -d;
!   x = 0.;
  
!   do
!     {
!       GET (ch);
!       w--;
!     }
!   while (ch == ' ' && w);
!   switch (ch)
!     {
!     case '-':
!       *sp++ = ch;
!       sp1++;
!       spe++;
!     case '+':
!       if (!w)
! 	goto zero;
!       --w;
!       GET (ch);
!     }
!   while (ch == ' ')
!     {
!     blankdrop:
!       if (!w--)
! 	goto zero;
!       GET (ch);
!     }
!   while (ch == '0')
!     {
!       if (!w--)
! 	goto zero;
!       GET (ch);
!     }
!   if (ch == ' ' && f__cblank)
!     goto blankdrop;
!   scale1 = f__scale;
!   while (isdigit (ch))
!     {
!     digloop1:
!       if (sp < spe)
! 	*sp++ = ch;
!       else
! 	++exp;
!     digloop1e:
!       if (!w--)
! 	goto done;
!       GET (ch);
!     }
!   if (ch == ' ')
!     {
!       if (f__cblank)
! 	{
! 	  ch = '0';
! 	  goto digloop1;
! 	}
!       goto digloop1e;
!     }
!   if (ch == '.')
!     {
!       exp += d;
!       if (!w--)
! 	goto done;
!       GET (ch);
!       if (sp == sp1)
! 	{			/* no digits yet */
! 	  while (ch == '0')
! 	    {
! 	    skip01:
! 	      --exp;
! 	    skip0:
! 	      if (!w--)
! 		goto done;
! 	      GET (ch);
! 	    }
! 	  if (ch == ' ')
! 	    {
! 	      if (f__cblank)
! 		goto skip01;
! 	      goto skip0;
! 	    }
! 	}
!       while (isdigit (ch))
! 	{
! 	digloop2:
! 	  if (sp < spe)
! 	    {
! 	      *sp++ = ch;
! 	      --exp;
! 	    }
! 	digloop2e:
! 	  if (!w--)
! 	    goto done;
! 	  GET (ch);
! 	}
!       if (ch == ' ')
! 	{
! 	  if (f__cblank)
! 	    {
! 	      ch = '0';
! 	      goto digloop2;
! 	    }
! 	  goto digloop2e;
! 	}
!     }
!   switch (ch)
!     {
!     default:
!       break;
!     case '-':
!       se = 1;
!       goto signonly;
!     case '+':
!       se = 0;
!       goto signonly;
!     case 'e':
!     case 'E':
!     case 'd':
!     case 'D':
!       if (!w--)
! 	goto bad;
!       GET (ch);
!       while (ch == ' ')
! 	{
! 	  if (!w--)
! 	    goto bad;
! 	  GET (ch);
! 	}
!       se = 0;
!       switch (ch)
! 	{
! 	case '-':
! 	  se = 1;
! 	case '+':
! 	signonly:
! 	  if (!w--)
! 	    goto bad;
! 	  GET (ch);
! 	}
!       while (ch == ' ')
! 	{
! 	  if (!w--)
! 	    goto bad;
! 	  GET (ch);
! 	}
!       if (!isdigit (ch))
! 	goto bad;
  
!       e = ch - '0';
!       for (;;)
! 	{
! 	  if (!w--)
! 	    {
! 	      ch = '\n';
! 	      break;
! 	    }
! 	  GET (ch);
! 	  if (!isdigit (ch))
! 	    {
! 	      if (ch == ' ')
! 		{
! 		  if (f__cblank)
! 		    ch = '0';
! 		  else
! 		    continue;
  		}
! 	      else
  		break;
! 	    }
! 	  e = 10 * e + ch - '0';
! 	  if (e > EXPMAX && sp > sp1)
! 	    goto bad;
! 	}
!       if (se)
! 	exp -= e;
!       else
! 	exp += e;
!       scale1 = 0;
!     }
!   switch (ch)
!     {
!     case '\n':
!     case ',':
!       break;
!     default:
!     bad:
!       return (errno = 115);
!     }
  done:
!   if (sp > sp1)
!     {
!       while (*--sp == '0')
! 	++exp;
!       if (exp -= scale1)
! 	sprintf (sp + 1, "e%ld", exp);
!       else
! 	sp[1] = 0;
!       x = atof (s);
!     }
  zero:
!   if (len == sizeof (real))
!     p->pf = x;
!   else
!     p->pd = x;
!   return (0);
! }
  
  
! static int
! rd_A (char *p, ftnlen len)
! {
!   int i, ch;
!   for (i = 0; i < len; i++)
!     {
!       GET (ch);
!       *p++ = VAL (ch);
!     }
!   return (0);
  }
! static int
! rd_AW (char *p, int w, ftnlen len)
! {
!   int i, ch;
!   if (w >= len)
!     {
!       for (i = 0; i < w - len; i++)
! 	GET (ch);
!       for (i = 0; i < len; i++)
! 	{
! 	  GET (ch);
! 	  *p++ = VAL (ch);
  	}
!       return (0);
!     }
!   for (i = 0; i < w; i++)
!     {
!       GET (ch);
!       *p++ = VAL (ch);
!     }
!   for (i = 0; i < len - w; i++)
!     *p++ = ' ';
!   return (0);
  }
! static int
! rd_H (int n, char *s)
! {
!   int i, ch;
!   for (i = 0; i < n; i++)
!     if ((ch = (*f__getn) ()) < 0)
!       return (ch);
!     else
!       *s++ = ch == '\n' ? ' ' : ch;
!   return (1);
  }
! static int
! rd_POS (char *s)
! {
!   char quote;
!   int ch;
!   quote = *s++;
!   for (; *s; s++)
!     if (*s == quote && *(s + 1) != quote)
!       break;
!     else if ((ch = (*f__getn) ()) < 0)
!       return (ch);
!     else
!       *s = ch == '\n' ? ' ' : ch;
!   return (1);
  }
! 
! int
! rd_ed (struct syl * p, char *ptr, ftnlen len)
! {
!   int ch;
!   for (; f__cursor > 0; f__cursor--)
!     if ((ch = (*f__getn) ()) < 0)
!       return (ch);
!   if (f__cursor < 0)
!     {
!       if (f__recpos + f__cursor < 0)	/*err(elist->cierr,110,"fmt") */
! 	f__cursor = -f__recpos;	/* is this in the standard? */
!       if (f__external == 0)
  	{
! 	  extern char *f__icptr;
! 	  f__icptr += f__cursor;
! 	}
!       else if (f__curunit && f__curunit->useek)
! 	FSEEK (f__cf, (off_t) f__cursor, SEEK_CUR);
!       else
! 	err (f__elist->cierr, 106, "fmt");
!       f__recpos += f__cursor;
!       f__cursor = 0;
!     }
!   switch (p->op)
!     {
!     default:
!       fprintf (stderr, "rd_ed, unexpected code: %d\n", p->op);
!       sig_die (f__fmtbuf, 1);
!     case IM:
!     case I:
!       ch = rd_I ((Uint *) ptr, p->p1, len, 10);
!       break;
  
!       /* O and OM don't work right for character, double, complex, */
!       /* or doublecomplex, and they differ from Fortran 90 in */
!       /* showing a minus sign for negative values. */
  
!     case OM:
!     case O:
!       ch = rd_I ((Uint *) ptr, p->p1, len, 8);
!       break;
!     case L:
!       ch = rd_L ((ftnint *) ptr, p->p1, len);
!       break;
!     case A:
!       ch = rd_A (ptr, len);
!       break;
!     case AW:
!       ch = rd_AW (ptr, p->p1, len);
!       break;
!     case E:
!     case EE:
!     case D:
!     case G:
!     case GE:
!     case F:
!       ch = rd_F ((ufloat *) ptr, p->p1, p->p2.i[0], len);
!       break;
  
!       /* Z and ZM assume 8-bit bytes. */
  
!     case ZM:
!     case Z:
!       ch = rd_Z ((Uint *) ptr, p->p1, len);
!       break;
!     }
!   if (ch == 0)
!     return (ch);
!   else if (ch == EOF)
!     return (EOF);
!   if (f__cf)
!     clearerr (f__cf);
!   return (errno);
  }
! 
! int
! rd_ned (struct syl * p)
  {
!   switch (p->op)
!     {
!     default:
!       fprintf (stderr, "rd_ned, unexpected code: %d\n", p->op);
!       sig_die (f__fmtbuf, 1);
!     case APOS:
!       return (rd_POS (p->p2.s));
!     case H:
!       return (rd_H (p->p1, p->p2.s));
!     case SLASH:
!       return ((*f__donewrec) ());
!     case TR:
!     case X:
!       f__cursor += p->p1;
!       return (1);
!     case T:
!       f__cursor = p->p1 - f__recpos - 1;
!       return (1);
!     case TL:
!       f__cursor -= p->p1;
!       if (f__cursor < -f__recpos)	/* TL1000, 1X */
! 	f__cursor = -f__recpos;
!       return (1);
!     }
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libI77/rewind.c gcc-3.3/libf2c/libI77/rewind.c
*** gcc-3.2.3/libf2c/libI77/rewind.c	2001-07-07 18:51:58.000000000 +0000
--- gcc-3.3/libf2c/libI77/rewind.c	2002-06-01 12:38:30.000000000 +0000
***************
*** 1,27 ****
  #include "config.h"
  #include "f2c.h"
  #include "fio.h"
! #ifdef KR_headers
! integer f_rew(a) alist *a;
! #else
! integer f_rew(alist *a)
! #endif
  {
! 	unit *b;
! 	if (f__init & 2)
! 		f__fatal (131, "I/O recursion");
! 	if(a->aunit>=MXUNIT || a->aunit<0)
! 		err(a->aerr,101,"rewind");
! 	b = &f__units[a->aunit];
! 	if(b->ufd == NULL || b->uwrt == 3)
! 		return(0);
! 	if(!b->useek)
! 		err(a->aerr,106,"rewind");
! 	if(b->uwrt) {
! 		(void) t_runc(a);
! 		b->uwrt = 3;
! 		}
! 	FSEEK(b->ufd, 0, SEEK_SET);
! 	b->uend=0;
! 	return(0);
  }
--- 1,25 ----
  #include "config.h"
  #include "f2c.h"
  #include "fio.h"
! integer
! f_rew (alist * a)
  {
!   unit *b;
!   if (f__init & 2)
!     f__fatal (131, "I/O recursion");
!   if (a->aunit >= MXUNIT || a->aunit < 0)
!     err (a->aerr, 101, "rewind");
!   b = &f__units[a->aunit];
!   if (b->ufd == NULL || b->uwrt == 3)
!     return (0);
!   if (!b->useek)
!     err (a->aerr, 106, "rewind");
!   if (b->uwrt)
!     {
!       (void) t_runc (a);
!       b->uwrt = 3;
!     }
!   FSEEK (b->ufd, 0, SEEK_SET);
!   b->uend = 0;
!   return (0);
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libI77/rsfe.c gcc-3.3/libf2c/libI77/rsfe.c
*** gcc-3.2.3/libf2c/libI77/rsfe.c	2001-05-16 18:59:29.000000000 +0000
--- gcc-3.3/libf2c/libI77/rsfe.c	2002-06-02 14:34:31.000000000 +0000
***************
*** 4,81 ****
  #include "fio.h"
  #include "fmt.h"
  
! xrd_SL(Void)
! {	int ch;
! 	if(!f__curunit->uend)
! 		while((ch=getc(f__cf))!='\n')
! 			if (ch == EOF) {
! 				f__curunit->uend = 1;
! 				break;
! 				}
! 	f__cursor=f__recpos=0;
! 	return(1);
! }
! x_getc(Void)
! {	int ch;
! 	if(f__curunit->uend) return(EOF);
! 	ch = getc(f__cf);
! 	if(ch!=EOF && ch!='\n')
! 	{	f__recpos++;
! 		return(ch);
! 	}
! 	if(ch=='\n')
! 	{	(void) ungetc(ch,f__cf);
! 		return(ch);
! 	}
! 	if(f__curunit->uend || feof(f__cf))
! 	{	errno=0;
! 		f__curunit->uend=1;
! 		return(-1);
  	}
! 	return(-1);
  }
! x_endp(Void)
  {
! 	xrd_SL();
! 	return f__curunit->uend == 1 ? EOF : 0;
  }
! x_rev(Void)
  {
! 	(void) xrd_SL();
! 	return(0);
  }
! #ifdef KR_headers
! integer s_rsfe(a) cilist *a; /* start */
! #else
! integer s_rsfe(cilist *a) /* start */
! #endif
! {	int n;
! 	if(f__init != 1) f_init();
! 	f__init = 3;
! 	f__reading=1;
! 	f__sequential=1;
! 	f__formatted=1;
! 	f__external=1;
! 	if(n=c_sfe(a)) return(n);
! 	f__elist=a;
! 	f__cursor=f__recpos=0;
! 	f__scale=0;
! 	f__fmtbuf=a->cifmt;
! 	f__curunit= &f__units[a->ciunit];
! 	f__cf=f__curunit->ufd;
! 	if(pars_f(f__fmtbuf)<0) err(a->cierr,100,"startio");
! 	f__getn= x_getc;
! 	f__doed= rd_ed;
! 	f__doned= rd_ned;
! 	fmt_bg();
! 	f__doend=x_endp;
! 	f__donewrec=xrd_SL;
! 	f__dorevert=x_rev;
! 	f__cblank=f__curunit->ublnk;
! 	f__cplus=0;
! 	if(f__curunit->uwrt && f__nowreading(f__curunit))
! 		err(a->cierr,errno,"read start");
! 	if(f__curunit->uend)
! 		err(f__elist->ciend,(EOF),"read start");
! 	return(0);
  }
--- 4,97 ----
  #include "fio.h"
  #include "fmt.h"
  
! int
! xrd_SL (void)
! {
!   int ch;
!   if (!f__curunit->uend)
!     while ((ch = getc (f__cf)) != '\n')
!       if (ch == EOF)
! 	{
! 	  f__curunit->uend = 1;
! 	  break;
  	}
!   f__cursor = f__recpos = 0;
!   return (1);
  }
! 
! int
! x_getc (void)
  {
!   int ch;
!   if (f__curunit->uend)
!     return (EOF);
!   ch = getc (f__cf);
!   if (ch != EOF && ch != '\n')
!     {
!       f__recpos++;
!       return (ch);
!     }
!   if (ch == '\n')
!     {
!       (void) ungetc (ch, f__cf);
!       return (ch);
!     }
!   if (f__curunit->uend || feof (f__cf))
!     {
!       errno = 0;
!       f__curunit->uend = 1;
!       return (-1);
!     }
!   return (-1);
  }
! 
! int
! x_endp (void)
  {
!   xrd_SL ();
!   return f__curunit->uend == 1 ? EOF : 0;
  }
! 
! int
! x_rev (void)
! {
!   (void) xrd_SL ();
!   return (0);
! }
! 
! integer
! s_rsfe (cilist * a)		/* start */
! {
!   int n;
!   if (f__init != 1)
!     f_init ();
!   f__init = 3;
!   f__reading = 1;
!   f__sequential = 1;
!   f__formatted = 1;
!   f__external = 1;
!   if ((n = c_sfe (a)))
!     return (n);
!   f__elist = a;
!   f__cursor = f__recpos = 0;
!   f__scale = 0;
!   f__fmtbuf = a->cifmt;
!   f__curunit = &f__units[a->ciunit];
!   f__cf = f__curunit->ufd;
!   if (pars_f (f__fmtbuf) < 0)
!     err (a->cierr, 100, "startio");
!   f__getn = x_getc;
!   f__doed = rd_ed;
!   f__doned = rd_ned;
!   fmt_bg ();
!   f__doend = x_endp;
!   f__donewrec = xrd_SL;
!   f__dorevert = x_rev;
!   f__cblank = f__curunit->ublnk;
!   f__cplus = 0;
!   if (f__curunit->uwrt && f__nowreading (f__curunit))
!     err (a->cierr, errno, "read start");
!   if (f__curunit->uend)
!     err (f__elist->ciend, (EOF), "read start");
!   return (0);
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libI77/rsli.c gcc-3.3/libf2c/libI77/rsli.c
*** gcc-3.2.3/libf2c/libI77/rsli.c	1999-09-04 15:09:18.000000000 +0000
--- gcc-3.3/libf2c/libI77/rsli.c	2002-06-05 19:07:10.000000000 +0000
***************
*** 1,7 ****
  #include "f2c.h"
  #include "fio.h"
  #include "lio.h"
! #include "fmt.h" /* for f__doend */
  
  extern flag f__lquit;
  extern int f__lcount;
--- 1,7 ----
  #include "f2c.h"
  #include "fio.h"
  #include "lio.h"
! #include "fmt.h"		/* for f__doend */
  
  extern flag f__lquit;
  extern int f__lcount;
*************** extern char *f__icend;
*** 10,105 ****
  extern icilist *f__svic;
  extern int f__icnum, f__recpos;
  
! static int i_getc(Void)
  {
! 	if(f__recpos >= f__svic->icirlen) {
! 		if (f__recpos++ == f__svic->icirlen)
! 			return '\n';
! 		z_rnew();
! 		}
! 	f__recpos++;
! 	if(f__icptr >= f__icend)
! 		return EOF;
! 	return(*f__icptr++);
! 	}
  
!  static
! #ifdef KR_headers
! int i_ungetc(ch, f) int ch; FILE *f;
! #else
! int i_ungetc(int ch, FILE *f)
! #endif
  {
! 	if (--f__recpos == f__svic->icirlen)
! 		return '\n';
! 	if (f__recpos < -1)
! 		err(f__svic->icierr,110,"recend");
! 	/* *--icptr == ch, and icptr may point to read-only memory */
! 	return *--f__icptr /* = ch */;
! 	}
  
!  static void
! #ifdef KR_headers
! c_lir(a) icilist *a;
! #else
! c_lir(icilist *a)
! #endif
  {
! 	extern int l_eof;
! 	if(f__init != 1) f_init();
! 	f__init = 3;
! 	f__reading = 1;
! 	f__external = 0;
! 	f__formatted = 1;
! 	f__svic = a;
! 	L_len = a->icirlen;
! 	f__recpos = -1;
! 	f__icnum = f__recpos = 0;
! 	f__cursor = 0;
! 	l_getc = i_getc;
! 	l_ungetc = i_ungetc;
! 	l_eof = 0;
! 	f__icptr = a->iciunit;
! 	f__icend = f__icptr + a->icirlen*a->icirnum;
! 	f__cf = 0;
! 	f__curunit = 0;
! 	f__elist = (cilist *)a;
! 	}
  
  
! #ifdef KR_headers
! integer s_rsli(a) icilist *a;
! #else
! integer s_rsli(icilist *a)
! #endif
  {
! 	f__lioproc = l_read;
! 	f__lquit = 0;
! 	f__lcount = 0;
! 	c_lir(a);
! 	f__doend = 0;
! 	return(0);
! 	}
  
! integer e_rsli(Void)
! { f__init = 1; return 0; }
  
! #ifdef KR_headers
! integer s_rsni(a) icilist *a;
! #else
! extern int x_rsne(cilist*);
  
! integer s_rsni(icilist *a)
! #endif
  {
! 	extern int nml_read;
! 	integer rv;
! 	cilist ca;
! 	ca.ciend = a->iciend;
! 	ca.cierr = a->icierr;
! 	ca.cifmt = a->icifmt;
! 	c_lir(a);
! 	rv = x_rsne(&ca);
! 	nml_read = 0;
! 	return rv;
! 	}
--- 10,99 ----
  extern icilist *f__svic;
  extern int f__icnum, f__recpos;
  
! static int
! i_getc (void)
  {
!   if (f__recpos >= f__svic->icirlen)
!     {
!       if (f__recpos++ == f__svic->icirlen)
! 	return '\n';
!       z_rnew ();
!     }
!   f__recpos++;
!   if (f__icptr >= f__icend)
!     return EOF;
!   return (*f__icptr++);
! }
  
! static int
! i_ungetc (int ch __attribute__ ((__unused__)),
! 	  FILE * f __attribute__ ((__unused__)))
  {
!   if (--f__recpos == f__svic->icirlen)
!     return '\n';
!   if (f__recpos < -1)
!     err (f__svic->icierr, 110, "recend");
!   /* *--icptr == ch, and icptr may point to read-only memory */
!   return *--f__icptr /* = ch */ ;
! }
  
! static void
! c_lir (icilist * a)
  {
!   extern int l_eof;
!   if (f__init != 1)
!     f_init ();
!   f__init = 3;
!   f__reading = 1;
!   f__external = 0;
!   f__formatted = 1;
!   f__svic = a;
!   L_len = a->icirlen;
!   f__recpos = -1;
!   f__icnum = f__recpos = 0;
!   f__cursor = 0;
!   l_getc = i_getc;
!   l_ungetc = i_ungetc;
!   l_eof = 0;
!   f__icptr = a->iciunit;
!   f__icend = f__icptr + a->icirlen * a->icirnum;
!   f__cf = 0;
!   f__curunit = 0;
!   f__elist = (cilist *) a;
! }
  
  
! integer
! s_rsli (icilist * a)
  {
!   f__lioproc = l_read;
!   f__lquit = 0;
!   f__lcount = 0;
!   c_lir (a);
!   f__doend = 0;
!   return (0);
! }
  
! integer
! e_rsli (void)
! {
!   f__init = 1;
!   return 0;
! }
  
! extern int x_rsne (cilist *);
  
! integer
! s_rsni (icilist * a)
  {
!   extern int nml_read;
!   integer rv;
!   cilist ca;
!   ca.ciend = a->iciend;
!   ca.cierr = a->icierr;
!   ca.cifmt = a->icifmt;
!   c_lir (a);
!   rv = x_rsne (&ca);
!   nml_read = 0;
!   return rv;
! }
diff -Nrc3pad gcc-3.2.3/libf2c/libI77/rsne.c gcc-3.3/libf2c/libI77/rsne.c
*** gcc-3.2.3/libf2c/libI77/rsne.c	2001-05-16 18:59:29.000000000 +0000
--- gcc-3.3/libf2c/libI77/rsne.c	2002-08-31 14:38:57.000000000 +0000
***************
*** 3,57 ****
  #include "fio.h"
  #include "lio.h"
  
! #define MAX_NL_CACHE 3	/* maximum number of namelist hash tables to cache */
! #define MAXDIM 20	/* maximum number of subscripts */
! 
!  struct dimen {
! 	ftnlen extent;
! 	ftnlen curval;
! 	ftnlen delta;
! 	ftnlen stride;
! 	};
!  typedef struct dimen dimen;
! 
!  struct hashentry {
! 	struct hashentry *next;
! 	char *name;
! 	Vardesc *vd;
! 	};
!  typedef struct hashentry hashentry;
  
!  struct hashtab {
! 	struct hashtab *next;
! 	Namelist *nl;
! 	int htsize;
! 	hashentry *tab[1];
! 	};
!  typedef struct hashtab hashtab;
  
!  static hashtab *nl_cache;
!  static int n_nlcache;
!  static hashentry **zot;
!  static int colonseen;
!  extern ftnlen f__typesize[];
  
!  extern flag f__lquit;
!  extern int f__lcount, nml_read;
!  extern t_getc(Void);
  
! #ifdef KR_headers
!  extern char *malloc(), *memset();
  
! #ifdef ungetc
!  static int
! un_getc(x,f__cf) int x; FILE *f__cf;
! { return ungetc(x,f__cf); }
! #else
! #define un_getc ungetc
!  extern int ungetc();
! #endif
  
- #else
  #undef abs
  #undef min
  #undef max
--- 3,47 ----
  #include "fio.h"
  #include "lio.h"
  
! #define MAX_NL_CACHE 3		/* maximum number of namelist hash tables to cache */
! #define MAXDIM 20		/* maximum number of subscripts */
  
! struct dimen
! {
!   ftnlen extent;
!   ftnlen curval;
!   ftnlen delta;
!   ftnlen stride;
! };
! typedef struct dimen dimen;
  
! struct hashentry
! {
!   struct hashentry *next;
!   char *name;
!   Vardesc *vd;
! };
! typedef struct hashentry hashentry;
  
! struct hashtab
! {
!   struct hashtab *next;
!   Namelist *nl;
!   int htsize;
!   hashentry *tab[1];
! };
! typedef struct hashtab hashtab;
  
! static hashtab *nl_cache;
! static int n_nlcache;
! static hashentry **zot;
! static int colonseen;
! extern ftnlen f__typesize[];
  
! extern flag f__lquit;
! extern int f__lcount, nml_read;
! extern int t_getc (void);
  
  #undef abs
  #undef min
  #undef max
*************** un_getc(x,f__cf) int x; FILE *f__cf;
*** 59,608 ****
  #include <string.h>
  
  #ifdef ungetc
!  static int
! un_getc(int x, FILE *f__cf)
! { return ungetc(x,f__cf); }
  #else
  #define un_getc ungetc
! extern int ungetc(int, FILE*);	/* for systems with a buggy stdio.h */
! #endif
  #endif
  
!  static Vardesc *
! #ifdef KR_headers
! hash(ht, s) hashtab *ht; register char *s;
! #else
! hash(hashtab *ht, register char *s)
! #endif
  {
! 	register int c, x;
! 	register hashentry *h;
! 	char *s0 = s;
  
! 	for(x = 0; c = *s++; x = x & 0x4000 ? ((x << 1) & 0x7fff) + 1 : x << 1)
! 		x += c;
! 	for(h = *(zot = ht->tab + x % ht->htsize); h; h = h->next)
! 		if (!strcmp(s0, h->name))
! 			return h->vd;
! 	return 0;
! 	}
  
!  hashtab *
! #ifdef KR_headers
! mk_hashtab(nl) Namelist *nl;
! #else
! mk_hashtab(Namelist *nl)
! #endif
  {
! 	int nht, nv;
! 	hashtab *ht;
! 	Vardesc *v, **vd, **vde;
! 	hashentry *he;
  
! 	hashtab **x, **x0, *y;
! 	for(x = &nl_cache; y = *x; x0 = x, x = &y->next)
! 		if (nl == y->nl)
! 			return y;
! 	if (n_nlcache >= MAX_NL_CACHE) {
! 		/* discard least recently used namelist hash table */
! 		y = *x0;
! 		free((char *)y->next);
! 		y->next = 0;
! 		}
! 	else
! 		n_nlcache++;
! 	nv = nl->nvars;
! 	if (nv >= 0x4000)
! 		nht = 0x7fff;
! 	else {
! 		for(nht = 1; nht < nv; nht <<= 1);
! 		nht += nht - 1;
! 		}
! 	ht = (hashtab *)malloc(sizeof(hashtab) + (nht-1)*sizeof(hashentry *)
! 				+ nv*sizeof(hashentry));
! 	if (!ht)
! 		return 0;
! 	he = (hashentry *)&ht->tab[nht];
! 	ht->nl = nl;
! 	ht->htsize = nht;
! 	ht->next = nl_cache;
! 	nl_cache = ht;
! 	memset((char *)ht->tab, 0, nht*sizeof(hashentry *));
! 	vd = nl->vars;
! 	vde = vd + nv;
! 	while(vd < vde) {
! 		v = *vd++;
! 		if (!hash(ht, v->name)) {
! 			he->next = *zot;
! 			*zot = he;
! 			he->name = v->name;
! 			he->vd = v;
! 			he++;
! 			}
! 		}
! 	return ht;
  	}
  
  static char Alpha[256], Alphanum[256];
  
!  static VOID
! nl_init(Void) {
! 	register char *s;
! 	register int c;
  
! 	for(s = "ABCDEFGHIJKLMNOPQRSTUVWXYZ"; c = *s++; )
! 		Alpha[c]
! 		= Alphanum[c]
! 		= Alpha[c + 'a' - 'A']
! 		= Alphanum[c + 'a' - 'A']
! 		= c;
! 	for(s = "0123456789_"; c = *s++; )
! 		Alphanum[c] = c;
! 	}
  
  #define GETC(x) (x=(*l_getc)())
  #define Ungetc(x,y) (*l_ungetc)(x,y)
  
!  static int
! #ifdef KR_headers
! getname(s, slen) register char *s; int slen;
! #else
! getname(register char *s, int slen)
! #endif
  {
! 	register char *se = s + slen - 1;
! 	register int ch;
  
! 	GETC(ch);
! 	if (!(*s++ = Alpha[ch & 0xff])) {
! 		if (ch != EOF)
! 			ch = 115;
! 		errfl(f__elist->cierr, ch, "namelist read");
! 		}
! 	while(*s = Alphanum[GETC(ch) & 0xff])
! 		if (s < se)
! 			s++;
! 	if (ch == EOF)
! 		err(f__elist->cierr, EOF, "namelist read");
! 	if (ch > ' ')
! 		Ungetc(ch,f__cf);
! 	return *s = 0;
! 	}
  
!  static int
! #ifdef KR_headers
! getnum(chp, val) int *chp; ftnlen *val;
! #else
! getnum(int *chp, ftnlen *val)
! #endif
  {
! 	register int ch, sign;
! 	register ftnlen x;
  
! 	while(GETC(ch) <= ' ' && ch >= 0);
! 	if (ch == '-') {
! 		sign = 1;
! 		GETC(ch);
! 		}
! 	else {
! 		sign = 0;
! 		if (ch == '+')
! 			GETC(ch);
! 		}
! 	x = ch - '0';
! 	if (x < 0 || x > 9)
! 		return 115;
! 	while(GETC(ch) >= '0' && ch <= '9')
! 		x = 10*x + ch - '0';
! 	while(ch <= ' ' && ch >= 0)
! 		GETC(ch);
! 	if (ch == EOF)
! 		return EOF;
! 	*val = sign ? -x : x;
! 	*chp = ch;
! 	return 0;
! 	}
  
!  static int
! #ifdef KR_headers
! getdimen(chp, d, delta, extent, x1)
!  int *chp; dimen *d; ftnlen delta, extent, *x1;
! #else
! getdimen(int *chp, dimen *d, ftnlen delta, ftnlen extent, ftnlen *x1)
! #endif
  {
! 	register int k;
! 	ftnlen x2, x3;
  
! 	if (k = getnum(chp, x1))
! 		return k;
! 	x3 = 1;
! 	if (*chp == ':') {
! 		if (k = getnum(chp, &x2))
! 			return k;
! 		x2 -= *x1;
! 		if (*chp == ':') {
! 			if (k = getnum(chp, &x3))
! 				return k;
! 			if (!x3)
! 				return 123;
! 			x2 /= x3;
! 			colonseen = 1;
! 			}
! 		if (x2 < 0 || x2 >= extent)
! 			return 123;
! 		d->extent = x2 + 1;
! 		}
! 	else
! 		d->extent = 1;
! 	d->curval = 0;
! 	d->delta = delta;
! 	d->stride = x3;
! 	return 0;
  	}
  
  #ifndef No_Namelist_Questions
!  static Void
! #ifdef KR_headers
! print_ne(a) cilist *a;
! #else
! print_ne(cilist *a)
! #endif
  {
! 	flag intext = f__external;
! 	int rpsave = f__recpos;
! 	FILE *cfsave = f__cf;
! 	unit *usave = f__curunit;
! 	cilist t;
! 	t = *a;
! 	t.ciunit = 6;
! 	s_wsne(&t);
! 	fflush(f__cf);
! 	f__external = intext;
! 	f__reading = 1;
! 	f__recpos = rpsave;
! 	f__cf = cfsave;
! 	f__curunit = usave;
! 	f__elist = a;
! 	}
  #endif
  
!  static char where0[] = "namelist read start ";
  
! #ifdef KR_headers
! x_rsne(a) cilist *a;
! #else
! x_rsne(cilist *a)
! #endif
  {
! 	int ch, got1, k, n, nd, quote, readall;
! 	Namelist *nl;
! 	static char where[] = "namelist read";
! 	char buf[64];
! 	hashtab *ht;
! 	Vardesc *v;
! 	dimen *dn, *dn0, *dn1;
! 	ftnlen *dims, *dims1;
! 	ftnlen b, b0, b1, ex, no, nomax, size, span;
! 	ftnint no1, type;
! 	char *vaddr;
! 	long iva, ivae;
! 	dimen dimens[MAXDIM], substr;
  
! 	if (!Alpha['a'])
! 		nl_init();
! 	f__reading=1;
! 	f__formatted=1;
! 	got1 = 0;
!  top:
! 	for(;;) switch(GETC(ch)) {
! 		case EOF:
!  eof:
! 			err(a->ciend,(EOF),where0);
! 		case '&':
! 		case '$':
! 			goto have_amp;
  #ifndef No_Namelist_Questions
! 		case '?':
! 			print_ne(a);
! 			continue;
  #endif
! 		default:
! 			if (ch <= ' ' && ch >= 0)
! 				continue;
  #ifndef No_Namelist_Comments
! 			while(GETC(ch) != '\n')
! 				if (ch == EOF)
! 					goto eof;
  #else
! 			errfl(a->cierr, 115, where0);
  #endif
! 		}
!  have_amp:
! 	if (ch = getname(buf,sizeof(buf)))
! 		return ch;
! 	nl = (Namelist *)a->cifmt;
! 	if (strcmp(buf, nl->name))
  #ifdef No_Bad_Namelist_Skip
! 		errfl(a->cierr, 118, where0);
  #else
  	{
! 		fprintf(stderr,
! 			"Skipping namelist \"%s\": seeking namelist \"%s\".\n",
! 			buf, nl->name);
! 		fflush(stderr);
! 		for(;;) switch(GETC(ch)) {
! 			case EOF:
! 				err(a->ciend, EOF, where0);
! 			case '/':
! 			case '&':
! 			case '$':
! 				if (f__external)
! 					e_rsle();
! 				else
! 					z_rnew();
! 				goto top;
! 			case '"':
! 			case '\'':
! 				quote = ch;
!  more_quoted:
! 				while(GETC(ch) != quote)
! 					if (ch == EOF)
! 						err(a->ciend, EOF, where0);
! 				if (GETC(ch) == quote)
! 					goto more_quoted;
! 				Ungetc(ch,f__cf);
! 			default:
! 				continue;
! 			}
  		}
! #endif
! 	ht = mk_hashtab(nl);
! 	if (!ht)
! 		errfl(f__elist->cierr, 113, where0);
! 	for(;;) {
! 		for(;;) switch(GETC(ch)) {
! 			case EOF:
! 				if (got1)
! 					return 0;
! 				err(a->ciend, EOF, where0);
! 			case '/':
! 			case '$':
! 			case '&':
! 				return 0;
! 			default:
! 				if (ch <= ' ' && ch >= 0 || ch == ',')
! 					continue;
! 				Ungetc(ch,f__cf);
! 				if (ch = getname(buf,sizeof(buf)))
! 					return ch;
! 				goto havename;
! 			}
!  havename:
! 		v = hash(ht,buf);
! 		if (!v)
! 			errfl(a->cierr, 119, where);
! 		while(GETC(ch) <= ' ' && ch >= 0);
! 		vaddr = v->addr;
! 		type = v->type;
! 		if (type < 0) {
! 			size = -type;
! 			type = TYCHAR;
! 			}
! 		else
! 			size = f__typesize[type];
! 		ivae = size;
! 		iva = readall = 0;
! 		if (ch == '(' /*)*/ ) {
! 			dn = dimens;
! 			if (!(dims = v->dims)) {
! 				if (type != TYCHAR)
! 					errfl(a->cierr, 122, where);
! 				if (k = getdimen(&ch, dn, (ftnlen)size,
! 						(ftnlen)size, &b))
! 					errfl(a->cierr, k, where);
! 				if (ch != ')')
! 					errfl(a->cierr, 115, where);
! 				b1 = dn->extent;
! 				if (--b < 0 || b + b1 > size)
! 					return 124;
! 				iva += b;
! 				size = b1;
! 				while(GETC(ch) <= ' ' && ch >= 0);
! 				goto scalar;
! 				}
! 			nd = (int)dims[0];
! 			nomax = span = dims[1];
! 			ivae = iva + size*nomax;
! 			colonseen = 0;
! 			if (k = getdimen(&ch, dn, size, nomax, &b))
! 				errfl(a->cierr, k, where);
! 			no = dn->extent;
! 			b0 = dims[2];
! 			dims1 = dims += 3;
! 			ex = 1;
! 			for(n = 1; n++ < nd; dims++) {
! 				if (ch != ',')
! 					errfl(a->cierr, 115, where);
! 				dn1 = dn + 1;
! 				span /= *dims;
! 				if (k = getdimen(&ch, dn1, dn->delta**dims,
! 						span, &b1))
! 					errfl(a->cierr, k, where);
! 				ex *= *dims;
! 				b += b1*ex;
! 				no *= dn1->extent;
! 				dn = dn1;
! 				}
! 			if (ch != ')')
! 				errfl(a->cierr, 115, where);
! 			readall = 1 - colonseen;
! 			b -= b0;
! 			if (b < 0 || b >= nomax)
! 				errfl(a->cierr, 125, where);
! 			iva += size * b;
! 			dims = dims1;
! 			while(GETC(ch) <= ' ' && ch >= 0);
! 			no1 = 1;
! 			dn0 = dimens;
! 			if (type == TYCHAR && ch == '(' /*)*/) {
! 				if (k = getdimen(&ch, &substr, size, size, &b))
! 					errfl(a->cierr, k, where);
! 				if (ch != ')')
! 					errfl(a->cierr, 115, where);
! 				b1 = substr.extent;
! 				if (--b < 0 || b + b1 > size)
! 					return 124;
! 				iva += b;
! 				b0 = size;
! 				size = b1;
! 				while(GETC(ch) <= ' ' && ch >= 0);
! 				if (b1 < b0)
! 					goto delta_adj;
! 				}
! 			if (readall)
! 				goto delta_adj;
! 			for(; dn0 < dn; dn0++) {
! 				if (dn0->extent != *dims++ || dn0->stride != 1)
! 					break;
! 				no1 *= dn0->extent;
! 				}
! 			if (dn0 == dimens && dimens[0].stride == 1) {
! 				no1 = dimens[0].extent;
! 				dn0++;
! 				}
!  delta_adj:
! 			ex = 0;
! 			for(dn1 = dn0; dn1 <= dn; dn1++)
! 				ex += (dn1->extent-1)
! 					* (dn1->delta *= dn1->stride);
! 			for(dn1 = dn; dn1 > dn0; dn1--) {
! 				ex -= (dn1->extent - 1) * dn1->delta;
! 				dn1->delta -= ex;
! 				}
! 			}
! 		else if (dims = v->dims) {
! 			no = no1 = dims[1];
! 			ivae = iva + no*size;
! 			}
! 		else
!  scalar:
! 			no = no1 = 1;
! 		if (ch != '=')
! 			errfl(a->cierr, 115, where);
! 		got1 = nml_read = 1;
! 		f__lcount = 0;
! 	 readloop:
! 		for(;;) {
! 			if (iva >= ivae || iva < 0) {
! 				f__lquit = 1;
! 				goto mustend;
! 				}
! 			else if (iva + no1*size > ivae)
! 				no1 = (ivae - iva)/size;
! 			f__lquit = 0;
! 			if (k = l_read(&no1, vaddr + iva, size, type))
! 				return k;
! 			if (f__lquit == 1)
! 				return 0;
! 			if (readall) {
! 				iva += dn0->delta;
! 				if (f__lcount > 0) {
! 					no1 = (ivae - iva)/size;
! 					if (no1 > f__lcount)
! 						no1 = f__lcount;
! 					if (k = l_read(&no1, vaddr + iva,
! 							size, type))
! 						return k;
! 					iva += no1 * dn0->delta;
! 					}
! 				}
!  mustend:
! 			GETC(ch);
! 			if (readall)
! 				if (iva >= ivae)
! 					readall = 0;
! 				else for(;;) {
! 					switch(ch) {
! 						case ' ':
! 						case '\t':
! 						case '\n':
! 							GETC(ch);
! 							continue;
! 						}
! 					break;
! 					}
! 			if (ch == '/' || ch == '$' || ch == '&') {
! 				f__lquit = 1;
! 				return 0;
! 				}
! 			else if (f__lquit) {
! 				while(ch <= ' ' && ch >= 0)
! 					GETC(ch);
! 				Ungetc(ch,f__cf);
! 				if (!Alpha[ch & 0xff] && ch >= 0)
! 					errfl(a->cierr, 125, where);
! 				break;
! 				}
! 			Ungetc(ch,f__cf);
! 			if (readall && !Alpha[ch & 0xff])
! 				goto readloop;
! 			if ((no -= no1) <= 0)
! 				break;
! 			for(dn1 = dn0; dn1 <= dn; dn1++) {
! 				if (++dn1->curval < dn1->extent) {
! 					iva += dn1->delta;
! 					goto readloop;
! 					}
! 				dn1->curval = 0;
! 				}
! 			break;
! 			}
  		}
  	}
  
!  integer
! #ifdef KR_headers
! s_rsne(a) cilist *a;
! #else
! s_rsne(cilist *a)
! #endif
  {
! 	extern int l_eof;
! 	int n;
  
! 	f__external=1;
! 	l_eof = 0;
! 	if(n = c_le(a))
! 		return n;
! 	if(f__curunit->uwrt && f__nowreading(f__curunit))
! 		err(a->cierr,errno,where0);
! 	l_getc = t_getc;
! 	l_ungetc = un_getc;
! 	f__doend = xrd_SL;
! 	n = x_rsne(a);
! 	nml_read = 0;
! 	if (n)
! 		return n;
! 	return e_rsle();
! 	}
--- 49,599 ----
  #include <string.h>
  
  #ifdef ungetc
! static int
! un_getc (int x, FILE * f__cf)
! {
!   return ungetc (x, f__cf);
! }
  #else
  #define un_getc ungetc
! extern int ungetc (int, FILE *);	/* for systems with a buggy stdio.h */
  #endif
  
! static Vardesc *
! hash (hashtab * ht, register char *s)
  {
!   register int c, x;
!   register hashentry *h;
!   char *s0 = s;
  
!   for (x = 0; (c = *s++); x = x & 0x4000 ? ((x << 1) & 0x7fff) + 1 : x << 1)
!     x += c;
!   for (h = *(zot = ht->tab + x % ht->htsize); h; h = h->next)
!     if (!strcmp (s0, h->name))
!       return h->vd;
!   return 0;
! }
  
! hashtab *
! mk_hashtab (Namelist * nl)
  {
!   int nht, nv;
!   hashtab *ht;
!   Vardesc *v, **vd, **vde;
!   hashentry *he;
  
!   hashtab **x, **x0, *y;
!   for (x = &nl_cache; (y = *x); x0 = x, x = &y->next)
!     if (nl == y->nl)
!       return y;
!   if (n_nlcache >= MAX_NL_CACHE)
!     {
!       /* discard least recently used namelist hash table */
!       y = *x0;
!       free ((char *) y->next);
!       y->next = 0;
!     }
!   else
!     n_nlcache++;
!   nv = nl->nvars;
!   if (nv >= 0x4000)
!     nht = 0x7fff;
!   else
!     {
!       for (nht = 1; nht < nv; nht <<= 1);
!       nht += nht - 1;
!     }
!   ht = (hashtab *) malloc (sizeof (hashtab) + (nht - 1) * sizeof (hashentry *)
! 			   + nv * sizeof (hashentry));
!   if (!ht)
!     return 0;
!   he = (hashentry *) & ht->tab[nht];
!   ht->nl = nl;
!   ht->htsize = nht;
!   ht->next = nl_cache;
!   nl_cache = ht;
!   memset ((char *) ht->tab, 0, nht * sizeof (hashentry *));
!   vd = nl->vars;
!   vde = vd + nv;
!   while (vd < vde)
!     {
!       v = *vd++;
!       if (!hash (ht, v->name))
! 	{
! 	  he->next = *zot;
! 	  *zot = he;
! 	  he->name = v->name;
! 	  he->vd = v;
! 	  he++;
  	}
+     }
+   return ht;
+ }
  
  static char Alpha[256], Alphanum[256];
  
! static void
! nl_init (void)
! {
!   register char *s;
!   register int c;
  
!   for (s = "ABCDEFGHIJKLMNOPQRSTUVWXYZ"; (c = *s++);)
!     Alpha[c]
!       = Alphanum[c] = Alpha[c + 'a' - 'A'] = Alphanum[c + 'a' - 'A'] = c;
!   for (s = "0123456789_"; (c = *s++);)
!     Alphanum[c] = c;
! }
  
  #define GETC(x) (x=(*l_getc)())
  #define Ungetc(x,y) (*l_ungetc)(x,y)
  
! static int
! getname (register char *s, int slen)
  {
!   register char *se = s + slen - 1;
!   register int ch;
  
!   GETC (ch);
!   if (!(*s++ = Alpha[ch & 0xff]))
!     {
!       if (ch != EOF)
! 	ch = 115;
!       errfl (f__elist->cierr, ch, "namelist read");
!     }
!   while ((*s = Alphanum[GETC (ch) & 0xff]))
!     if (s < se)
!       s++;
!   if (ch == EOF)
!     err (f__elist->cierr, EOF, "namelist read");
!   if (ch > ' ')
!     Ungetc (ch, f__cf);
!   return *s = 0;
! }
  
! static int
! getnum (int *chp, ftnlen * val)
  {
!   register int ch, sign;
!   register ftnlen x;
  
!   while (GETC (ch) <= ' ' && ch >= 0);
!   if (ch == '-')
!     {
!       sign = 1;
!       GETC (ch);
!     }
!   else
!     {
!       sign = 0;
!       if (ch == '+')
! 	GETC (ch);
!     }
!   x = ch - '0';
!   if (x < 0 || x > 9)
!     return 115;
!   while (GETC (ch) >= '0' && ch <= '9')
!     x = 10 * x + ch - '0';
!   while (ch <= ' ' && ch >= 0)
!     GETC (ch);
!   if (ch == EOF)
!     return EOF;
!   *val = sign ? -x : x;
!   *chp = ch;
!   return 0;
! }
  
! static int
! getdimen (int *chp, dimen * d, ftnlen delta, ftnlen extent, ftnlen * x1)
  {
!   register int k;
!   ftnlen x2, x3;
  
!   if ((k = getnum (chp, x1)))
!     return k;
!   x3 = 1;
!   if (*chp == ':')
!     {
!       if ((k = getnum (chp, &x2)))
! 	return k;
!       x2 -= *x1;
!       if (*chp == ':')
! 	{
! 	  if ((k = getnum (chp, &x3)))
! 	    return k;
! 	  if (!x3)
! 	    return 123;
! 	  x2 /= x3;
! 	  colonseen = 1;
  	}
+       if (x2 < 0 || x2 >= extent)
+ 	return 123;
+       d->extent = x2 + 1;
+     }
+   else
+     d->extent = 1;
+   d->curval = 0;
+   d->delta = delta;
+   d->stride = x3;
+   return 0;
+ }
  
  #ifndef No_Namelist_Questions
! static void
! print_ne (cilist * a)
  {
!   flag intext = f__external;
!   int rpsave = f__recpos;
!   FILE *cfsave = f__cf;
!   unit *usave = f__curunit;
!   cilist t;
!   t = *a;
!   t.ciunit = 6;
!   s_wsne (&t);
!   fflush (f__cf);
!   f__external = intext;
!   f__reading = 1;
!   f__recpos = rpsave;
!   f__cf = cfsave;
!   f__curunit = usave;
!   f__elist = a;
! }
  #endif
  
! static char where0[] = "namelist read start ";
  
! int
! x_rsne (cilist * a)
  {
!   int ch, got1, k, n, nd, quote, readall;
!   Namelist *nl;
!   static char where[] = "namelist read";
!   char buf[64];
!   hashtab *ht;
!   Vardesc *v;
!   dimen *dn, *dn0, *dn1;
!   ftnlen *dims, *dims1;
!   ftnlen b, b0, b1, ex, no, nomax, size, span;
!   ftnint no1, type;
!   char *vaddr;
!   long iva, ivae;
!   dimen dimens[MAXDIM], substr;
  
!   if (!Alpha['a'])
!     nl_init ();
!   f__reading = 1;
!   f__formatted = 1;
!   got1 = 0;
! top:
!   for (;;)
!     switch (GETC (ch))
!       {
!       case EOF:
!       eof:
! 	err (a->ciend, (EOF), where0);
!       case '&':
!       case '$':
! 	goto have_amp;
  #ifndef No_Namelist_Questions
!       case '?':
! 	print_ne (a);
! 	continue;
  #endif
!       default:
! 	if (ch <= ' ' && ch >= 0)
! 	  continue;
  #ifndef No_Namelist_Comments
! 	while (GETC (ch) != '\n')
! 	  if (ch == EOF)
! 	    goto eof;
  #else
! 	errfl (a->cierr, 115, where0);
  #endif
!       }
! have_amp:
!   if ((ch = getname (buf, sizeof (buf))))
!     return ch;
!   nl = (Namelist *) a->cifmt;
!   if (strcmp (buf, nl->name))
  #ifdef No_Bad_Namelist_Skip
!     errfl (a->cierr, 118, where0);
  #else
+     {
+       fprintf (stderr,
+ 	       "Skipping namelist \"%s\": seeking namelist \"%s\".\n",
+ 	       buf, nl->name);
+       fflush (stderr);
+       for (;;)
+ 	switch (GETC (ch))
+ 	  {
+ 	  case EOF:
+ 	    err (a->ciend, EOF, where0);
+ 	  case '/':
+ 	  case '&':
+ 	  case '$':
+ 	    if (f__external)
+ 	      e_rsle ();
+ 	    else
+ 	      z_rnew ();
+ 	    goto top;
+ 	  case '"':
+ 	  case '\'':
+ 	    quote = ch;
+ 	  more_quoted:
+ 	    while (GETC (ch) != quote)
+ 	      if (ch == EOF)
+ 		err (a->ciend, EOF, where0);
+ 	    if (GETC (ch) == quote)
+ 	      goto more_quoted;
+ 	    Ungetc (ch, f__cf);
+ 	  default:
+ 	    continue;
+ 	  }
+     }
+ #endif
+   ht = mk_hashtab (nl);
+   if (!ht)
+     errfl (f__elist->cierr, 113, where0);
+   for (;;)
+     {
+       for (;;)
+ 	switch (GETC (ch))
+ 	  {
+ 	  case EOF:
+ 	    if (got1)
+ 	      return 0;
+ 	    err (a->ciend, EOF, where0);
+ 	  case '/':
+ 	  case '$':
+ 	  case '&':
+ 	    return 0;
+ 	  default:
+ 	    if ((ch <= ' ' && ch >= 0) || ch == ',')
+ 	      continue;
+ 	    Ungetc (ch, f__cf);
+ 	    if ((ch = getname (buf, sizeof (buf))))
+ 	      return ch;
+ 	    goto havename;
+ 	  }
+     havename:
+       v = hash (ht, buf);
+       if (!v)
+ 	errfl (a->cierr, 119, where);
+       while (GETC (ch) <= ' ' && ch >= 0);
+       vaddr = v->addr;
+       type = v->type;
+       if (type < 0)
  	{
! 	  size = -type;
! 	  type = TYCHAR;
! 	}
!       else
! 	size = f__typesize[type];
!       ivae = size;
!       iva = readall = 0;
!       if (ch == '(' /*) */ )
! 	{
! 	  dn = dimens;
! 	  if (!(dims = v->dims))
! 	    {
! 	      if (type != TYCHAR)
! 		errfl (a->cierr, 122, where);
! 	      if ((k = getdimen (&ch, dn, (ftnlen) size, (ftnlen) size, &b)))
! 		errfl (a->cierr, k, where);
! 	      if (ch != ')')
! 		errfl (a->cierr, 115, where);
! 	      b1 = dn->extent;
! 	      if (--b < 0 || b + b1 > size)
! 		return 124;
! 	      iva += b;
! 	      size = b1;
! 	      while (GETC (ch) <= ' ' && ch >= 0);
! 	      goto scalar;
! 	    }
! 	  nd = (int) dims[0];
! 	  nomax = span = dims[1];
! 	  ivae = iva + size * nomax;
! 	  colonseen = 0;
! 	  if ((k = getdimen (&ch, dn, size, nomax, &b)))
! 	    errfl (a->cierr, k, where);
! 	  no = dn->extent;
! 	  b0 = dims[2];
! 	  dims1 = dims += 3;
! 	  ex = 1;
! 	  for (n = 1; n++ < nd; dims++)
! 	    {
! 	      if (ch != ',')
! 		errfl (a->cierr, 115, where);
! 	      dn1 = dn + 1;
! 	      span /= *dims;
! 	      if ((k = getdimen (&ch, dn1, dn->delta ** dims, span, &b1)))
! 		errfl (a->cierr, k, where);
! 	      ex *= *dims;
! 	      b += b1 * ex;
! 	      no *= dn1->extent;
! 	      dn = dn1;
! 	    }
! 	  if (ch != ')')
! 	    errfl (a->cierr, 115, where);
! 	  readall = 1 - colonseen;
! 	  b -= b0;
! 	  if (b < 0 || b >= nomax)
! 	    errfl (a->cierr, 125, where);
! 	  iva += size * b;
! 	  dims = dims1;
! 	  while (GETC (ch) <= ' ' && ch >= 0);
! 	  no1 = 1;
! 	  dn0 = dimens;
! 	  if (type == TYCHAR && ch == '(' /*) */ )
! 	    {
! 	      if ((k = getdimen (&ch, &substr, size, size, &b)))
! 		errfl (a->cierr, k, where);
! 	      if (ch != ')')
! 		errfl (a->cierr, 115, where);
! 	      b1 = substr.extent;
! 	      if (--b < 0 || b + b1 > size)
! 		return 124;
! 	      iva += b;
! 	      b0 = size;
! 	      size = b1;
! 	      while (GETC (ch) <= ' ' && ch >= 0);
! 	      if (b1 < b0)
! 		goto delta_adj;
! 	    }
! 	  if (readall)
! 	    goto delta_adj;
! 	  for (; dn0 < dn; dn0++)
! 	    {
! 	      if (dn0->extent != *dims++ || dn0->stride != 1)
! 		break;
! 	      no1 *= dn0->extent;
! 	    }
! 	  if (dn0 == dimens && dimens[0].stride == 1)
! 	    {
! 	      no1 = dimens[0].extent;
! 	      dn0++;
! 	    }
! 	delta_adj:
! 	  ex = 0;
! 	  for (dn1 = dn0; dn1 <= dn; dn1++)
! 	    ex += (dn1->extent - 1) * (dn1->delta *= dn1->stride);
! 	  for (dn1 = dn; dn1 > dn0; dn1--)
! 	    {
! 	      ex -= (dn1->extent - 1) * dn1->delta;
! 	      dn1->delta -= ex;
! 	    }
! 	}
!       else if ((dims = v->dims))
! 	{
! 	  no = no1 = dims[1];
! 	  ivae = iva + no * size;
! 	}
!       else
!       scalar:
! 	no = no1 = 1;
!       if (ch != '=')
! 	errfl (a->cierr, 115, where);
!       got1 = nml_read = 1;
!       f__lcount = 0;
!     readloop:
!       for (;;)
! 	{
! 	  if (iva >= ivae || iva < 0)
! 	    {
! 	      f__lquit = 1;
! 	      goto mustend;
! 	    }
! 	  else if (iva + no1 * size > ivae)
! 	    no1 = (ivae - iva) / size;
! 	  f__lquit = 0;
! 	  if ((k = l_read (&no1, vaddr + iva, size, type)))
! 	    return k;
! 	  if (f__lquit == 1)
! 	    return 0;
! 	  if (readall)
! 	    {
! 	      iva += dn0->delta;
! 	      if (f__lcount > 0)
! 		{
! 		  ftnint no2 = (ivae - iva) / size;
! 		  if (no2 > f__lcount)
! 		    no2 = f__lcount;
! 		  if ((k = l_read (&no2, vaddr + iva, size, type)))
! 		    return k;
! 		  iva += no2 * dn0->delta;
  		}
! 	    }
! 	mustend:
! 	  GETC (ch);
! 	  if (readall)
! 	    {
! 	      if (iva >= ivae)
! 		readall = 0;
! 	      else
! 		for (;;)
! 		  {
! 		    switch (ch)
! 		      {
! 		      case ' ':
! 		      case '\t':
! 		      case '\n':
! 			GETC (ch);
! 			continue;
! 		      }
! 		    break;
! 		  }
! 	    }
! 	  if (ch == '/' || ch == '$' || ch == '&')
! 	    {
! 	      f__lquit = 1;
! 	      return 0;
! 	    }
! 	  else if (f__lquit)
! 	    {
! 	      while (ch <= ' ' && ch >= 0)
! 		GETC (ch);
! 	      Ungetc (ch, f__cf);
! 	      if (!Alpha[ch & 0xff] && ch >= 0)
! 		errfl (a->cierr, 125, where);
! 	      break;
! 	    }
! 	  Ungetc (ch, f__cf);
! 	  if (readall && !Alpha[ch & 0xff])
! 	    goto readloop;
! 	  if ((no -= no1) <= 0)
! 	    break;
! 	  for (dn1 = dn0; dn1 <= dn; dn1++)
! 	    {
! 	      if (++dn1->curval < dn1->extent)
! 		{
! 		  iva += dn1->delta;
! 		  goto readloop;
  		}
+ 	      dn1->curval = 0;
+ 	    }
+ 	  break;
  	}
+     }
+ }
  
! integer
! s_rsne (cilist * a)
  {
!   extern int l_eof;
!   int n;
  
!   f__external = 1;
!   l_eof = 0;
!   if ((n = c_le (a)))
!     return n;
!   if (f__curunit->uwrt && f__nowreading (f__curunit))
!     err (a->cierr, errno, where0);
!   l_getc = t_getc;
!   l_ungetc = un_getc;
!   f__doend = xrd_SL;
!   n = x_rsne (a);
!   nml_read = 0;
!   if (n)
!     return n;
!   return e_rsle ();
! }
diff -Nrc3pad gcc-3.2.3/libf2c/libI77/sfe.c gcc-3.3/libf2c/libI77/sfe.c
*** gcc-3.2.3/libf2c/libI77/sfe.c	2001-07-07 18:51:58.000000000 +0000
--- gcc-3.3/libf2c/libI77/sfe.c	2002-06-02 13:01:12.000000000 +0000
***************
*** 5,39 ****
  
  extern char *f__fmtbuf;
  
! integer e_rsfe(Void)
! {	int n;
! 	f__init = 1;
! 	n=en_fio();
! 	f__fmtbuf=NULL;
! 	return(n);
  }
! #ifdef KR_headers
! c_sfe(a) cilist *a; /* check */
! #else
! c_sfe(cilist *a) /* check */
! #endif
! {	unit *p;
! 	if(a->ciunit >= MXUNIT || a->ciunit<0)
! 		err(a->cierr,101,"startio");
! 	p = &f__units[a->ciunit];
! 	if(p->ufd==NULL && fk_open(SEQ,FMT,a->ciunit)) err(a->cierr,114,"sfe");
! 	if(!p->ufmt) err(a->cierr,102,"sfe");
! 	return(0);
  }
! integer e_wsfe(Void)
  {
! 	int n;
! 	f__init = 1;
! 	n = en_fio();
! 	f__fmtbuf=NULL;
  #ifdef ALWAYS_FLUSH
! 	if (!n && fflush(f__cf))
! 		err(f__elist->cierr, errno, "write end");
  #endif
! 	return n;
  }
--- 5,44 ----
  
  extern char *f__fmtbuf;
  
! integer
! e_rsfe (void)
! {
!   int n;
!   f__init = 1;
!   n = en_fio ();
!   f__fmtbuf = NULL;
!   return (n);
  }
! 
! int
! c_sfe (cilist * a)		/* check */
! {
!   unit *p;
!   if (a->ciunit >= MXUNIT || a->ciunit < 0)
!     err (a->cierr, 101, "startio");
!   p = &f__units[a->ciunit];
!   if (p->ufd == NULL && fk_open (SEQ, FMT, a->ciunit))
!     err (a->cierr, 114, "sfe");
!   if (!p->ufmt)
!     err (a->cierr, 102, "sfe");
!   return (0);
  }
! 
! integer
! e_wsfe (void)
  {
!   int n;
!   f__init = 1;
!   n = en_fio ();
!   f__fmtbuf = NULL;
  #ifdef ALWAYS_FLUSH
!   if (!n && fflush (f__cf))
!     err (f__elist->cierr, errno, "write end");
  #endif
!   return n;
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libI77/sue.c gcc-3.3/libf2c/libI77/sue.c
*** gcc-3.2.3/libf2c/libI77/sue.c	2001-07-06 12:09:39.000000000 +0000
--- gcc-3.3/libf2c/libI77/sue.c	2002-06-02 14:34:31.000000000 +0000
***************
*** 4,88 ****
  extern uiolen f__reclen;
  off_t f__recloc;
  
! #ifdef KR_headers
! c_sue(a) cilist *a;
! #else
! c_sue(cilist *a)
! #endif
  {
! 	f__external=f__sequential=1;
! 	f__formatted=0;
! 	f__curunit = &f__units[a->ciunit];
! 	if(a->ciunit >= MXUNIT || a->ciunit < 0)
! 		err(a->cierr,101,"startio");
! 	f__elist=a;
! 	if(f__curunit->ufd==NULL && fk_open(SEQ,UNF,a->ciunit))
! 		err(a->cierr,114,"sue");
! 	f__cf=f__curunit->ufd;
! 	if(f__curunit->ufmt) err(a->cierr,103,"sue");
! 	if(!f__curunit->useek) err(a->cierr,103,"sue");
! 	return(0);
  }
! #ifdef KR_headers
! integer s_rsue(a) cilist *a;
! #else
! integer s_rsue(cilist *a)
! #endif
  {
! 	int n;
! 	if(f__init != 1) f_init();
! 	f__init = 3;
! 	f__reading=1;
! 	if(n=c_sue(a)) return(n);
! 	f__recpos=0;
! 	if(f__curunit->uwrt && f__nowreading(f__curunit))
! 		err(a->cierr, errno, "read start");
! 	if(fread((char *)&f__reclen,sizeof(uiolen),1,f__cf)
! 		!= 1)
! 	{	if(feof(f__cf))
! 		{	f__curunit->uend = 1;
! 			err(a->ciend, EOF, "start");
! 		}
! 		clearerr(f__cf);
! 		err(a->cierr, errno, "start");
  	}
! 	return(0);
  }
! #ifdef KR_headers
! integer s_wsue(a) cilist *a;
! #else
! integer s_wsue(cilist *a)
! #endif
  {
! 	int n;
! 	if(f__init != 1) f_init();
! 	f__init = 3;
! 	if(n=c_sue(a)) return(n);
! 	f__reading=0;
! 	f__reclen=0;
! 	if(f__curunit->uwrt != 1 && f__nowwriting(f__curunit))
! 		err(a->cierr, errno, "write start");
! 	f__recloc=FTELL(f__cf);
! 	FSEEK(f__cf,(off_t)sizeof(uiolen),SEEK_CUR);
! 	return(0);
  }
! integer e_wsue(Void)
! {	off_t loc;
! 	f__init = 1;
! 	fwrite((char *)&f__reclen,sizeof(uiolen),1,f__cf);
  #ifdef ALWAYS_FLUSH
! 	if (fflush(f__cf))
! 		err(f__elist->cierr, errno, "write end");
  #endif
! 	loc=FTELL(f__cf);
! 	FSEEK(f__cf,f__recloc,SEEK_SET);
! 	fwrite((char *)&f__reclen,sizeof(uiolen),1,f__cf);
! 	FSEEK(f__cf,loc,SEEK_SET);
! 	return(0);
  }
! integer e_rsue(Void)
  {
! 	f__init = 1;
! 	FSEEK(f__cf,(off_t)(f__reclen-f__recpos+sizeof(uiolen)),SEEK_CUR);
! 	return(0);
  }
--- 4,93 ----
  extern uiolen f__reclen;
  off_t f__recloc;
  
! int
! c_sue (cilist * a)
  {
!   f__external = f__sequential = 1;
!   f__formatted = 0;
!   f__curunit = &f__units[a->ciunit];
!   if (a->ciunit >= MXUNIT || a->ciunit < 0)
!     err (a->cierr, 101, "startio");
!   f__elist = a;
!   if (f__curunit->ufd == NULL && fk_open (SEQ, UNF, a->ciunit))
!     err (a->cierr, 114, "sue");
!   f__cf = f__curunit->ufd;
!   if (f__curunit->ufmt)
!     err (a->cierr, 103, "sue");
!   if (!f__curunit->useek)
!     err (a->cierr, 103, "sue");
!   return (0);
  }
! 
! integer
! s_rsue (cilist * a)
  {
!   int n;
!   if (f__init != 1)
!     f_init ();
!   f__init = 3;
!   f__reading = 1;
!   if ((n = c_sue (a)))
!     return (n);
!   f__recpos = 0;
!   if (f__curunit->uwrt && f__nowreading (f__curunit))
!     err (a->cierr, errno, "read start");
!   if (fread ((char *) &f__reclen, sizeof (uiolen), 1, f__cf) != 1)
!     {
!       if (feof (f__cf))
! 	{
! 	  f__curunit->uend = 1;
! 	  err (a->ciend, EOF, "start");
  	}
!       clearerr (f__cf);
!       err (a->cierr, errno, "start");
!     }
!   return (0);
  }
! 
! integer
! s_wsue (cilist * a)
  {
!   int n;
!   if (f__init != 1)
!     f_init ();
!   f__init = 3;
!   if ((n = c_sue (a)))
!     return (n);
!   f__reading = 0;
!   f__reclen = 0;
!   if (f__curunit->uwrt != 1 && f__nowwriting (f__curunit))
!     err (a->cierr, errno, "write start");
!   f__recloc = FTELL (f__cf);
!   FSEEK (f__cf, (off_t) sizeof (uiolen), SEEK_CUR);
!   return (0);
  }
! 
! integer
! e_wsue (void)
! {
!   off_t loc;
!   f__init = 1;
!   fwrite ((char *) &f__reclen, sizeof (uiolen), 1, f__cf);
  #ifdef ALWAYS_FLUSH
!   if (fflush (f__cf))
!     err (f__elist->cierr, errno, "write end");
  #endif
!   loc = FTELL (f__cf);
!   FSEEK (f__cf, f__recloc, SEEK_SET);
!   fwrite ((char *) &f__reclen, sizeof (uiolen), 1, f__cf);
!   FSEEK (f__cf, loc, SEEK_SET);
!   return (0);
  }
! 
! integer
! e_rsue (void)
  {
!   f__init = 1;
!   FSEEK (f__cf, (off_t) (f__reclen - f__recpos + sizeof (uiolen)), SEEK_CUR);
!   return (0);
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libI77/typesize.c gcc-3.3/libf2c/libI77/typesize.c
*** gcc-3.2.3/libf2c/libI77/typesize.c	2001-05-16 18:59:29.000000000 +0000
--- gcc-3.3/libf2c/libI77/typesize.c	2002-06-01 12:38:30.000000000 +0000
***************
*** 1,13 ****
  #include "config.h"
  #include "f2c.h"
  
! ftnlen f__typesize[] = { 0, 0, sizeof(shortint), sizeof(integer),
! 			sizeof(real), sizeof(doublereal),
! 			sizeof(complex), sizeof(doublecomplex),
! 			sizeof(logical), sizeof(char),
! 			0, sizeof(integer1),
! 			sizeof(logical1), sizeof(shortlogical),
  #ifdef Allow_TYQUAD
! 			sizeof(longint),
  #endif
! 			0};
--- 1,14 ----
  #include "config.h"
  #include "f2c.h"
  
! ftnlen f__typesize[] = { 0, 0, sizeof (shortint), sizeof (integer),
!   sizeof (real), sizeof (doublereal),
!   sizeof (complex), sizeof (doublecomplex),
!   sizeof (logical), sizeof (char),
!   0, sizeof (integer1),
!   sizeof (logical1), sizeof (shortlogical),
  #ifdef Allow_TYQUAD
!   sizeof (longint),
  #endif
!   0
! };
diff -Nrc3pad gcc-3.2.3/libf2c/libI77/uio.c gcc-3.3/libf2c/libI77/uio.c
*** gcc-3.2.3/libf2c/libI77/uio.c	1999-09-04 15:09:18.000000000 +0000
--- gcc-3.3/libf2c/libI77/uio.c	2002-06-04 02:25:47.000000000 +0000
***************
*** 1,69 ****
  #include "f2c.h"
  #include "fio.h"
  #include <sys/types.h>
  uiolen f__reclen;
  
! #ifdef KR_headers
! do_us(number,ptr,len) ftnint *number; char *ptr; ftnlen len;
! #else
! do_us(ftnint *number, char *ptr, ftnlen len)
! #endif
  {
! 	if(f__reading)
! 	{
! 		f__recpos += (int)(*number * len);
! 		if(f__recpos>f__reclen)
! 			err(f__elist->cierr, 110, "do_us");
! 		if (fread(ptr,(size_t)len,(size_t)(*number),f__cf) != *number)
! 			err(f__elist->ciend, EOF, "do_us");
! 		return(0);
! 	}
! 	else
! 	{
! 		f__reclen += *number * len;
! 		(void) fwrite(ptr,(size_t)len,(size_t)(*number),f__cf);
! 		return(0);
! 	}
  }
! #ifdef KR_headers
! integer do_ud(number,ptr,len) ftnint *number; char *ptr; ftnlen len;
! #else
! integer do_ud(ftnint *number, char *ptr, ftnlen len)
! #endif
  {
! 	f__recpos += (int)(*number * len);
! 	if(f__recpos > f__curunit->url && f__curunit->url!=1)
! 		err(f__elist->cierr,110,"do_ud");
! 	if(f__reading)
! 	{
  #ifdef Pad_UDread
! #ifdef KR_headers
! 	int i;
! #else
! 	size_t i;
! #endif
! 		if (!(i = fread(ptr,(size_t)len,(size_t)(*number),f__cf))
! 		 && !(f__recpos - *number*len))
! 			err(f__elist->cierr,EOF,"do_ud");
! 		if (i < *number)
! 			memset(ptr + i*len, 0, (*number - i)*len);
! 		return 0;
  #else
! 		if(fread(ptr,(size_t)len,(size_t)(*number),f__cf) != *number)
! 			err(f__elist->cierr,EOF,"do_ud");
! 		else return(0);
  #endif
! 	}
! 	(void) fwrite(ptr,(size_t)len,(size_t)(*number),f__cf);
! 	return(0);
  }
! #ifdef KR_headers
! integer do_uio(number,ptr,len) ftnint *number; char *ptr; ftnlen len;
! #else
! integer do_uio(ftnint *number, char *ptr, ftnlen len)
! #endif
  {
! 	if(f__sequential)
! 		return(do_us(number,ptr,len));
! 	else	return(do_ud(number,ptr,len));
  }
--- 1,60 ----
+ #include "config.h"
  #include "f2c.h"
  #include "fio.h"
  #include <sys/types.h>
  uiolen f__reclen;
  
! int
! do_us (ftnint * number, char *ptr, ftnlen len)
  {
!   if (f__reading)
!     {
!       f__recpos += (int) (*number * len);
!       if (f__recpos > f__reclen)
! 	err (f__elist->cierr, 110, "do_us");
!       if (fread (ptr, (size_t) len, (size_t) (*number), f__cf) != (size_t) *number)
! 	err (f__elist->ciend, EOF, "do_us");
!       return (0);
!     }
!   else
!     {
!       f__reclen += *number * len;
!       (void) fwrite (ptr, (size_t) len, (size_t) (*number), f__cf);
!       return (0);
!     }
  }
! integer
! do_ud (ftnint * number, char *ptr, ftnlen len)
  {
!   f__recpos += (int) (*number * len);
!   if (f__recpos > f__curunit->url && f__curunit->url != 1)
!     err (f__elist->cierr, 110, "do_ud");
!   if (f__reading)
!     {
  #ifdef Pad_UDread
!       size_t i;
!       if (!(i = fread (ptr, (size_t) len, (size_t) (*number), f__cf))
! 	  && !(f__recpos - *number * len))
! 	err (f__elist->cierr, EOF, "do_ud");
!       if (i < (size_t) *number)
! 	memset (ptr + i * len, 0, (*number - i) * len);
!       return 0;
  #else
!       if (fread (ptr, (size_t) len, (size_t) (*number), f__cf) != *number)
! 	err (f__elist->cierr, EOF, "do_ud");
!       else
! 	return (0);
  #endif
!     }
!   (void) fwrite (ptr, (size_t) len, (size_t) (*number), f__cf);
!   return (0);
  }
! 
! integer
! do_uio (ftnint * number, char *ptr, ftnlen len)
  {
!   if (f__sequential)
!     return (do_us (number, ptr, len));
!   else
!     return (do_ud (number, ptr, len));
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libI77/util.c gcc-3.3/libf2c/libI77/util.c
*** gcc-3.2.3/libf2c/libI77/util.c	2001-05-16 18:59:29.000000000 +0000
--- gcc-3.3/libf2c/libI77/util.c	2002-06-01 12:38:30.000000000 +0000
***************
*** 8,54 ****
  #include "f2c.h"
  #include "fio.h"
  
!  VOID
! #ifdef KR_headers
! g_char(a,alen,b) char *a,*b; ftnlen alen;
! #else
! g_char(char *a, ftnlen alen, char *b)
! #endif
  {
! 	char *x = a + alen, *y = b + alen;
  
! 	for(;; y--) {
! 		if (x <= a) {
! 			*b = 0;
! 			return;
! 			}
! 		if (*--x != ' ')
! 			break;
! 		}
! 	*y-- = 0;
! 	do *y-- = *x;
! 		while(x-- > a);
  	}
  
!  VOID
! #ifdef KR_headers
! b_char(a,b,blen) char *a,*b; ftnlen blen;
! #else
! b_char(char *a, char *b, ftnlen blen)
! #endif
! {	int i;
! 	for(i=0;i<blen && *a!=0;i++) *b++= *a++;
! 	for(;i<blen;i++) *b++=' ';
  }
  #ifndef NON_UNIX_STDIO
! #ifdef KR_headers
! long f__inode(a, dev) char *a; int *dev;
! #else
! long f__inode(char *a, int *dev)
! #endif
! {	struct stat x;
! 	if(stat(a,&x)<0) return(-1);
! 	*dev = x.st_dev;
! 	return(x.st_ino);
  }
  #endif
--- 8,52 ----
  #include "f2c.h"
  #include "fio.h"
  
! void
! g_char (char *a, ftnlen alen, char *b)
  {
!   char *x = a + alen, *y = b + alen;
  
!   for (;; y--)
!     {
!       if (x <= a)
! 	{
! 	  *b = 0;
! 	  return;
  	}
+       if (*--x != ' ')
+ 	break;
+     }
+   *y-- = 0;
+   do
+     *y-- = *x;
+   while (x-- > a);
+ }
  
! void
! b_char (char *a, char *b, ftnlen blen)
! {
!   int i;
!   for (i = 0; i < blen && *a != 0; i++)
!     *b++ = *a++;
!   for (; i < blen; i++)
!     *b++ = ' ';
  }
+ 
  #ifndef NON_UNIX_STDIO
! long
! f__inode (char *a, int *dev)
! {
!   struct stat x;
!   if (stat (a, &x) < 0)
!     return (-1);
!   *dev = x.st_dev;
!   return (x.st_ino);
  }
  #endif
diff -Nrc3pad gcc-3.2.3/libf2c/libI77/Version.c gcc-3.3/libf2c/libI77/Version.c
*** gcc-3.2.3/libf2c/libI77/Version.c	2003-04-22 00:16:27.000000000 +0000
--- gcc-3.3/libf2c/libI77/Version.c	2002-09-24 03:44:35.000000000 +0000
***************
*** 1,9 ****
! static char junk[] = "\n@(#) LIBI77 VERSION pjw,dmg-mods 20001205\n";
! 
! /*
! */
! 
! char __G77_LIBI77_VERSION__[] = "3.2.2 20030422 (release)";
  
  /*
  2.01	$ format added
--- 1,4 ----
! const char __LIBI77_VERSION__[] = "@(#) LIBI77 VERSION pjw,dmg-mods 20001205\n";
  
  /*
  2.01	$ format added
*************** wrtfmt.c:
*** 324,340 ****
  /*		treat Tstuff= and Fstuff= as new assignments rather than as */
  /*		logical constants. */
  
- 
- 
  /* Changes for GNU Fortran (g77) version of libf2c:  */
  
  /* 17 June 1997: detect recursive I/O and call f__fatal explaining it. */
- 
- #include <stdio.h>
- 
- void
- g77__ivers__ ()
- {
-   fprintf (stderr, "__G77_LIBI77_VERSION__: %s", __G77_LIBI77_VERSION__);
-   fputs (junk, stderr);
- }
--- 319,324 ----
diff -Nrc3pad gcc-3.2.3/libf2c/libI77/wref.c gcc-3.3/libf2c/libI77/wref.c
*** gcc-3.2.3/libf2c/libI77/wref.c	1999-09-04 15:09:18.000000000 +0000
--- gcc-3.3/libf2c/libI77/wref.c	2002-06-04 02:25:47.000000000 +0000
***************
*** 4,276 ****
  #include <ctype.h>
  #endif
  
- #ifndef KR_headers
  #undef abs
  #undef min
  #undef max
  #include <stdlib.h>
  #include <string.h>
- #endif
  
  #include "fmt.h"
  #include "fp.h"
  
! #ifdef KR_headers
! wrt_E(p,w,d,e,len) ufloat *p; ftnlen len;
! #else
! wrt_E(ufloat *p, int w, int d, int e, ftnlen len)
! #endif
  {
! 	char buf[FMAX+EXPMAXDIGS+4], *s, *se;
! 	int d1, delta, e1, i, sign, signspace;
! 	double dd;
  #ifdef WANT_LEAD_0
! 	int insert0 = 0;
  #endif
  #ifndef VAX
! 	int e0 = e;
  #endif
  
! 	if(e <= 0)
! 		e = 2;
! 	if(f__scale) {
! 		if(f__scale >= d + 2 || f__scale <= -d)
! 			goto nogood;
! 		}
! 	if(f__scale <= 0)
! 		--d;
! 	if (len == sizeof(real))
! 		dd = p->pf;
! 	else
! 		dd = p->pd;
! 	if (dd < 0.) {
! 		signspace = sign = 1;
! 		dd = -dd;
! 		}
! 	else {
! 		sign = 0;
! 		signspace = (int)f__cplus;
  #ifndef VAX
! 		if (!dd)
! 			dd = 0.;	/* avoid -0 */
  #endif
! 		}
! 	delta = w - (2 /* for the . and the d adjustment above */
! 			+ 2 /* for the E+ */ + signspace + d + e);
  #ifdef WANT_LEAD_0
! 	if (f__scale <= 0 && delta > 0) {
! 		delta--;
! 		insert0 = 1;
! 		}
! 	else
  #endif
! 	if (delta < 0) {
! nogood:
! 		while(--w >= 0)
! 			PUT('*');
! 		return(0);
! 		}
! 	if (f__scale < 0)
! 		d += f__scale;
! 	if (d > FMAX) {
! 		d1 = d - FMAX;
! 		d = FMAX;
! 		}
! 	else
! 		d1 = 0;
! 	sprintf(buf,"%#.*E", d, dd);
  #ifndef VAX
! 	/* check for NaN, Infinity */
! 	if (!isdigit(buf[0])) {
! 		switch(buf[0]) {
! 			case 'n':
! 			case 'N':
! 				signspace = 0;	/* no sign for NaNs */
! 			}
! 		delta = w - strlen(buf) - signspace;
! 		if (delta < 0)
! 			goto nogood;
! 		while(--delta >= 0)
! 			PUT(' ');
! 		if (signspace)
! 			PUT(sign ? '-' : '+');
! 		for(s = buf; *s; s++)
! 			PUT(*s);
! 		return 0;
! 		}
  #endif
! 	se = buf + d + 3;
! #ifdef GOOD_SPRINTF_EXPONENT /* When possible, exponent has 2 digits. */
! 	if (f__scale != 1 && dd)
! 		sprintf(se, "%+.2d", atoi(se) + 1 - f__scale);
  #else
! 	if (dd)
! 		sprintf(se, "%+.2d", atoi(se) + 1 - f__scale);
! 	else
! 		strcpy(se, "+00");
  #endif
! 	s = ++se;
! 	if (e < 2) {
! 		if (*s != '0')
! 			goto nogood;
! 		}
  #ifndef VAX
! 	/* accommodate 3 significant digits in exponent */
! 	if (s[2]) {
  #ifdef Pedantic
! 		if (!e0 && !s[3])
! 			for(s -= 2, e1 = 2; s[0] = s[1]; s++);
  
! 	/* Pedantic gives the behavior that Fortran 77 specifies,	*/
! 	/* i.e., requires that E be specified for exponent fields	*/
! 	/* of more than 3 digits.  With Pedantic undefined, we get	*/
! 	/* the behavior that Cray displays -- you get a bigger		*/
! 	/* exponent field if it fits.	*/
  #else
! 		if (!e0) {
! 			for(s -= 2, e1 = 2; s[0] = s[1]; s++)
  #ifdef CRAY
! 				delta--;
! 			if ((delta += 4) < 0)
! 				goto nogood
  #endif
! 				;
! 			}
  #endif
! 		else if (e0 >= 0)
! 			goto shift;
! 		else
! 			e1 = e;
! 		}
! 	else
!  shift:
  #endif
! 		for(s += 2, e1 = 2; *s; ++e1, ++s)
! 			if (e1 >= e)
! 				goto nogood;
! 	while(--delta >= 0)
! 		PUT(' ');
! 	if (signspace)
! 		PUT(sign ? '-' : '+');
! 	s = buf;
! 	i = f__scale;
! 	if (f__scale <= 0) {
  #ifdef WANT_LEAD_0
! 		if (insert0)
! 			PUT('0');
  #endif
! 		PUT('.');
! 		for(; i < 0; ++i)
! 			PUT('0');
! 		PUT(*s);
! 		s += 2;
! 		}
! 	else if (f__scale > 1) {
! 		PUT(*s);
! 		s += 2;
! 		while(--i > 0)
! 			PUT(*s++);
! 		PUT('.');
! 		}
! 	if (d1) {
! 		se -= 2;
! 		while(s < se) PUT(*s++);
! 		se += 2;
! 		do PUT('0'); while(--d1 > 0);
! 		}
! 	while(s < se)
! 		PUT(*s++);
! 	if (e < 2)
! 		PUT(s[1]);
! 	else {
! 		while(++e1 <= e)
! 			PUT('0');
! 		while(*s)
! 			PUT(*s++);
! 		}
! 	return 0;
! 	}
  
! #ifdef KR_headers
! wrt_F(p,w,d,len) ufloat *p; ftnlen len;
! #else
! wrt_F(ufloat *p, int w, int d, ftnlen len)
! #endif
  {
! 	int d1, sign, n;
! 	double x;
! 	char *b, buf[MAXINTDIGS+MAXFRACDIGS+4], *s;
  
! 	x= (len==sizeof(real)?p->pf:p->pd);
! 	if (d < MAXFRACDIGS)
! 		d1 = 0;
! 	else {
! 		d1 = d - MAXFRACDIGS;
! 		d = MAXFRACDIGS;
! 		}
! 	if (x < 0.)
! 		{ x = -x; sign = 1; }
! 	else {
! 		sign = 0;
  #ifndef VAX
! 		if (!x)
! 			x = 0.;
  #endif
! 		}
  
! 	if (n = f__scale)
! 		if (n > 0)
! 			do x *= 10.; while(--n > 0);
! 		else
! 			do x *= 0.1; while(++n < 0);
  
  #ifdef USE_STRLEN
! 	sprintf(b = buf, "%#.*f", d, x);
! 	n = strlen(b) + d1;
  #else
! 	n = sprintf(b = buf, "%#.*f", d, x) + d1;
  #endif
  
  #ifndef WANT_LEAD_0
! 	if (buf[0] == '0' && d)
! 		{ ++b; --n; }
  #endif
! 	if (sign) {
! 		/* check for all zeros */
! 		for(s = b;;) {
! 			while(*s == '0') s++;
! 			switch(*s) {
! 				case '.':
! 					s++; continue;
! 				case 0:
! 					sign = 0;
! 				}
! 			break;
! 			}
! 		}
! 	if (sign || f__cplus)
! 		++n;
! 	if (n > w) {
  #ifdef WANT_LEAD_0
! 		if (buf[0] == '0' && --n == w)
! 			++b;
! 		else
  #endif
! 		{
! 			while(--w >= 0)
! 				PUT('*');
! 			return 0;
! 			}
! 		}
! 	for(w -= n; --w >= 0; )
! 		PUT(' ');
! 	if (sign)
! 		PUT('-');
! 	else if (f__cplus)
! 		PUT('+');
! 	while(n = *b++)
! 		PUT(n);
! 	while(--d1 >= 0)
! 		PUT('0');
! 	return 0;
  	}
--- 4,306 ----
  #include <ctype.h>
  #endif
  
  #undef abs
  #undef min
  #undef max
  #include <stdlib.h>
  #include <string.h>
  
  #include "fmt.h"
  #include "fp.h"
  
! int
! wrt_E (ufloat * p, int w, int d, int e, ftnlen len)
  {
!   char buf[FMAX + EXPMAXDIGS + 4], *s, *se;
!   int d1, delta, e1, i, sign, signspace;
!   double dd;
  #ifdef WANT_LEAD_0
!   int insert0 = 0;
  #endif
  #ifndef VAX
!   int e0 = e;
  #endif
  
!   if (e <= 0)
!     e = 2;
!   if (f__scale)
!     {
!       if (f__scale >= d + 2 || f__scale <= -d)
! 	goto nogood;
!     }
!   if (f__scale <= 0)
!     --d;
!   if (len == sizeof (real))
!     dd = p->pf;
!   else
!     dd = p->pd;
!   if (dd < 0.)
!     {
!       signspace = sign = 1;
!       dd = -dd;
!     }
!   else
!     {
!       sign = 0;
!       signspace = (int) f__cplus;
  #ifndef VAX
!       if (!dd)
! 	dd = 0.;		/* avoid -0 */
  #endif
!     }
!   delta = w - (2		/* for the . and the d adjustment above */
! 	       + 2 /* for the E+ */  + signspace + d + e);
  #ifdef WANT_LEAD_0
!   if (f__scale <= 0 && delta > 0)
!     {
!       delta--;
!       insert0 = 1;
!     }
!   else
  #endif
!   if (delta < 0)
!     {
!     nogood:
!       while (--w >= 0)
! 	PUT ('*');
!       return (0);
!     }
!   if (f__scale < 0)
!     d += f__scale;
!   if (d > FMAX)
!     {
!       d1 = d - FMAX;
!       d = FMAX;
!     }
!   else
!     d1 = 0;
!   sprintf (buf, "%#.*E", d, dd);
  #ifndef VAX
!   /* check for NaN, Infinity */
!   if (!isdigit ((unsigned char) buf[0]))
!     {
!       switch (buf[0])
! 	{
! 	case 'n':
! 	case 'N':
! 	  signspace = 0;	/* no sign for NaNs */
! 	}
!       delta = w - strlen (buf) - signspace;
!       if (delta < 0)
! 	goto nogood;
!       while (--delta >= 0)
! 	PUT (' ');
!       if (signspace)
! 	PUT (sign ? '-' : '+');
!       for (s = buf; *s; s++)
! 	PUT (*s);
!       return 0;
!     }
  #endif
!   se = buf + d + 3;
! #ifdef GOOD_SPRINTF_EXPONENT	/* When possible, exponent has 2 digits. */
!   if (f__scale != 1 && dd)
!     sprintf (se, "%+.2d", atoi (se) + 1 - f__scale);
  #else
!   if (dd)
!     sprintf (se, "%+.2d", atoi (se) + 1 - f__scale);
!   else
!     strcpy (se, "+00");
  #endif
!   s = ++se;
!   if (e < 2)
!     {
!       if (*s != '0')
! 	goto nogood;
!     }
  #ifndef VAX
!   /* accommodate 3 significant digits in exponent */
!   if (s[2])
!     {
  #ifdef Pedantic
!       if (!e0 && !s[3])
! 	for (s -= 2, e1 = 2; s[0] = s[1]; s++);
  
!       /* Pedantic gives the behavior that Fortran 77 specifies,       */
!       /* i.e., requires that E be specified for exponent fields       */
!       /* of more than 3 digits.  With Pedantic undefined, we get      */
!       /* the behavior that Cray displays -- you get a bigger          */
!       /* exponent field if it fits.   */
  #else
!       if (!e0)
! 	{
! 	  for (s -= 2, e1 = 2; (s[0] = s[1]); s++)
  #ifdef CRAY
! 	    delta--;
! 	  if ((delta += 4) < 0)
! 	    goto nogood
  #endif
! 	      ;
! 	}
  #endif
!       else if (e0 >= 0)
! 	goto shift;
!       else
! 	e1 = e;
!     }
!   else
!   shift:
  #endif
!     for (s += 2, e1 = 2; *s; ++e1, ++s)
!       if (e1 >= e)
! 	goto nogood;
!   while (--delta >= 0)
!     PUT (' ');
!   if (signspace)
!     PUT (sign ? '-' : '+');
!   s = buf;
!   i = f__scale;
!   if (f__scale <= 0)
!     {
  #ifdef WANT_LEAD_0
!       if (insert0)
! 	PUT ('0');
  #endif
!       PUT ('.');
!       for (; i < 0; ++i)
! 	PUT ('0');
!       PUT (*s);
!       s += 2;
!     }
!   else if (f__scale > 1)
!     {
!       PUT (*s);
!       s += 2;
!       while (--i > 0)
! 	PUT (*s++);
!       PUT ('.');
!     }
!   if (d1)
!     {
!       se -= 2;
!       while (s < se)
! 	PUT (*s++);
!       se += 2;
!       do
! 	PUT ('0');
!       while (--d1 > 0);
!     }
!   while (s < se)
!     PUT (*s++);
!   if (e < 2)
!     PUT (s[1]);
!   else
!     {
!       while (++e1 <= e)
! 	PUT ('0');
!       while (*s)
! 	PUT (*s++);
!     }
!   return 0;
! }
  
! int
! wrt_F (ufloat * p, int w, int d, ftnlen len)
  {
!   int d1, sign, n;
!   double x;
!   char *b, buf[MAXINTDIGS + MAXFRACDIGS + 4], *s;
  
!   x = (len == sizeof (real) ? p->pf : p->pd);
!   if (d < MAXFRACDIGS)
!     d1 = 0;
!   else
!     {
!       d1 = d - MAXFRACDIGS;
!       d = MAXFRACDIGS;
!     }
!   if (x < 0.)
!     {
!       x = -x;
!       sign = 1;
!     }
!   else
!     {
!       sign = 0;
  #ifndef VAX
!       if (!x)
! 	x = 0.;
  #endif
!     }
  
!   if ((n = f__scale))
!     {
!       if (n > 0)
! 	do
! 	  x *= 10.;
! 	while (--n > 0);
!       else
! 	do
! 	  x *= 0.1;
! 	while (++n < 0);
!     }
  
  #ifdef USE_STRLEN
!   sprintf (b = buf, "%#.*f", d, x);
!   n = strlen (b) + d1;
  #else
!   n = sprintf (b = buf, "%#.*f", d, x) + d1;
  #endif
  
  #ifndef WANT_LEAD_0
!   if (buf[0] == '0' && d)
!     {
!       ++b;
!       --n;
!     }
  #endif
!   if (sign)
!     {
!       /* check for all zeros */
!       for (s = b;;)
! 	{
! 	  while (*s == '0')
! 	    s++;
! 	  switch (*s)
! 	    {
! 	    case '.':
! 	      s++;
! 	      continue;
! 	    case 0:
! 	      sign = 0;
! 	    }
! 	  break;
! 	}
!     }
!   if (sign || f__cplus)
!     ++n;
!   if (n > w)
!     {
  #ifdef WANT_LEAD_0
!       if (buf[0] == '0' && --n == w)
! 	++b;
!       else
  #endif
! 	{
! 	  while (--w >= 0)
! 	    PUT ('*');
! 	  return 0;
  	}
+     }
+   for (w -= n; --w >= 0;)
+     PUT (' ');
+   if (sign)
+     PUT ('-');
+   else if (f__cplus)
+     PUT ('+');
+   while ((n = *b++))
+     PUT (n);
+   while (--d1 >= 0)
+     PUT ('0');
+   return 0;
+ }
diff -Nrc3pad gcc-3.2.3/libf2c/libI77/wrtfmt.c gcc-3.3/libf2c/libI77/wrtfmt.c
*** gcc-3.2.3/libf2c/libI77/wrtfmt.c	2001-05-16 18:59:29.000000000 +0000
--- gcc-3.3/libf2c/libI77/wrtfmt.c	2002-06-02 13:01:12.000000000 +0000
***************
*** 6,366 ****
  extern icilist *f__svic;
  extern char *f__icptr;
  
!  static int
! mv_cur(Void)	/* shouldn't use fseek because it insists on calling fflush */
  		/* instead we know too much about stdio */
  {
! 	int cursor = f__cursor;
! 	f__cursor = 0;
! 	if(f__external == 0) {
! 		if(cursor < 0) {
! 			if(f__hiwater < f__recpos)
! 				f__hiwater = f__recpos;
! 			f__recpos += cursor;
! 			f__icptr += cursor;
! 			if(f__recpos < 0)
! 				err(f__elist->cierr, 110, "left off");
! 		}
! 		else if(cursor > 0) {
! 			if(f__recpos + cursor >= f__svic->icirlen)
! 				err(f__elist->cierr, 110, "recend");
! 			if(f__hiwater <= f__recpos)
! 				for(; cursor > 0; cursor--)
! 					(*f__putn)(' ');
! 			else if(f__hiwater <= f__recpos + cursor) {
! 				cursor -= f__hiwater - f__recpos;
! 				f__icptr += f__hiwater - f__recpos;
! 				f__recpos = f__hiwater;
! 				for(; cursor > 0; cursor--)
! 					(*f__putn)(' ');
! 			}
! 			else {
! 				f__icptr += cursor;
! 				f__recpos += cursor;
! 			}
! 		}
! 		return(0);
  	}
! 	if (cursor > 0) {
! 		if(f__hiwater <= f__recpos)
! 			for(;cursor>0;cursor--) (*f__putn)(' ');
! 		else if(f__hiwater <= f__recpos + cursor) {
! 			cursor -= f__hiwater - f__recpos;
! 			f__recpos = f__hiwater;
! 			for(; cursor > 0; cursor--)
! 				(*f__putn)(' ');
! 		}
! 		else {
! 			f__recpos += cursor;
! 		}
  	}
! 	else if (cursor < 0)
  	{
! 		if(cursor + f__recpos < 0)
! 			err(f__elist->cierr,110,"left off");
! 		if(f__hiwater < f__recpos)
! 			f__hiwater = f__recpos;
! 		f__recpos += cursor;
  	}
! 	return(0);
  }
  
!  static int
! #ifdef KR_headers
! wrt_Z(n,w,minlen,len) Uint *n; int w, minlen; ftnlen len;
! #else
! wrt_Z(Uint *n, int w, int minlen, ftnlen len)
! #endif
  {
! 	register char *s, *se;
! 	register int i, w1;
! 	static int one = 1;
! 	static char hex[] = "0123456789ABCDEF";
! 	s = (char *)n;
! 	--len;
! 	if (*(char *)&one) {
! 		/* little endian */
! 		se = s;
! 		s += len;
! 		i = -1;
! 		}
! 	else {
! 		se = s + len;
! 		i = 1;
! 		}
! 	for(;; s += i)
! 		if (s == se || *s)
! 			break;
! 	w1 = (i*(se-s) << 1) + 1;
! 	if (*s & 0xf0)
! 		w1++;
! 	if (w1 > w)
! 		for(i = 0; i < w; i++)
! 			(*f__putn)('*');
! 	else {
! 		if ((minlen -= w1) > 0)
! 			w1 += minlen;
! 		while(--w >= w1)
! 			(*f__putn)(' ');
! 		while(--minlen >= 0)
! 			(*f__putn)('0');
! 		if (!(*s & 0xf0)) {
! 			(*f__putn)(hex[*s & 0xf]);
! 			if (s == se)
! 				return 0;
! 			s += i;
! 			}
! 		for(;; s += i) {
! 			(*f__putn)(hex[*s >> 4 & 0xf]);
! 			(*f__putn)(hex[*s & 0xf]);
! 			if (s == se)
! 				break;
! 			}
! 		}
! 	return 0;
  	}
  
!  static int
! #ifdef KR_headers
! wrt_I(n,w,len, base) Uint *n; ftnlen len; register int base;
! #else
! wrt_I(Uint *n, int w, ftnlen len, register int base)
! #endif
! {	int ndigit,sign,spare,i;
! 	longint x;
! 	char *ans;
! 	if(len==sizeof(integer)) x=n->il;
! 	else if(len == sizeof(char)) x = n->ic;
  #ifdef Allow_TYQUAD
! 	else if (len == sizeof(longint)) x = n->ili;
  #endif
! 	else x=n->is;
! 	ans=f__icvt(x,&ndigit,&sign, base);
! 	spare=w-ndigit;
! 	if(sign || f__cplus) spare--;
! 	if(spare<0)
! 		for(i=0;i<w;i++) (*f__putn)('*');
! 	else
! 	{	for(i=0;i<spare;i++) (*f__putn)(' ');
! 		if(sign) (*f__putn)('-');
! 		else if(f__cplus) (*f__putn)('+');
! 		for(i=0;i<ndigit;i++) (*f__putn)(*ans++);
! 	}
! 	return(0);
  }
!  static int
! #ifdef KR_headers
! wrt_IM(n,w,m,len,base) Uint *n; ftnlen len; int base;
! #else
! wrt_IM(Uint *n, int w, int m, ftnlen len, int base)
! #endif
! {	int ndigit,sign,spare,i,xsign;
! 	longint x;
! 	char *ans;
! 	if(sizeof(integer)==len) x=n->il;
! 	else if(len == sizeof(char)) x = n->ic;
  #ifdef Allow_TYQUAD
! 	else if (len == sizeof(longint)) x = n->ili;
  #endif
! 	else x=n->is;
! 	ans=f__icvt(x,&ndigit,&sign, base);
! 	if(sign || f__cplus) xsign=1;
! 	else xsign=0;
! 	if(ndigit+xsign>w || m+xsign>w)
! 	{	for(i=0;i<w;i++) (*f__putn)('*');
! 		return(0);
! 	}
! 	if(x==0 && m==0)
! 	{	for(i=0;i<w;i++) (*f__putn)(' ');
! 		return(0);
! 	}
! 	if(ndigit>=m)
! 		spare=w-ndigit-xsign;
! 	else
! 		spare=w-m-xsign;
! 	for(i=0;i<spare;i++) (*f__putn)(' ');
! 	if(sign) (*f__putn)('-');
! 	else if(f__cplus) (*f__putn)('+');
! 	for(i=0;i<m-ndigit;i++) (*f__putn)('0');
! 	for(i=0;i<ndigit;i++) (*f__putn)(*ans++);
! 	return(0);
  }
!  static int
! #ifdef KR_headers
! wrt_AP(s) char *s;
! #else
! wrt_AP(char *s)
! #endif
! {	char quote;
! 	int i;
  
! 	if(f__cursor && (i = mv_cur()))
! 		return i;
! 	quote = *s++;
! 	for(;*s;s++)
! 	{	if(*s!=quote) (*f__putn)(*s);
! 		else if(*++s==quote) (*f__putn)(*s);
! 		else return(1);
! 	}
! 	return(1);
  }
!  static int
! #ifdef KR_headers
! wrt_H(a,s) char *s;
! #else
! wrt_H(int a, char *s)
! #endif
  {
! 	int i;
  
! 	if(f__cursor && (i = mv_cur()))
! 		return i;
! 	while(a--) (*f__putn)(*s++);
! 	return(1);
  }
! #ifdef KR_headers
! wrt_L(n,len, sz) Uint *n; ftnlen sz;
! #else
! wrt_L(Uint *n, int len, ftnlen sz)
! #endif
! {	int i;
! 	long x;
! 	if(sizeof(long)==sz) x=n->il;
! 	else if(sz == sizeof(char)) x = n->ic;
! 	else x=n->is;
! 	for(i=0;i<len-1;i++)
! 		(*f__putn)(' ');
! 	if(x) (*f__putn)('T');
! 	else (*f__putn)('F');
! 	return(0);
  }
!  static int
! #ifdef KR_headers
! wrt_A(p,len) char *p; ftnlen len;
! #else
! wrt_A(char *p, ftnlen len)
! #endif
  {
! 	while(len-- > 0) (*f__putn)(*p++);
! 	return(0);
  }
!  static int
! #ifdef KR_headers
! wrt_AW(p,w,len) char * p; ftnlen len;
! #else
! wrt_AW(char * p, int w, ftnlen len)
! #endif
  {
! 	while(w>len)
! 	{	w--;
! 		(*f__putn)(' ');
! 	}
! 	while(w-- > 0)
! 		(*f__putn)(*p++);
! 	return(0);
  }
  
!  static int
! #ifdef KR_headers
! wrt_G(p,w,d,e,len) ufloat *p; ftnlen len;
! #else
! wrt_G(ufloat *p, int w, int d, int e, ftnlen len)
! #endif
! {	double up = 1,x;
! 	int i=0,oldscale,n,j;
! 	x = len==sizeof(real)?p->pf:p->pd;
! 	if(x < 0 ) x = -x;
! 	if(x<.1) {
! 		if (x != 0.)
! 			return(wrt_E(p,w,d,e,len));
! 		i = 1;
! 		goto have_i;
! 		}
! 	for(;i<=d;i++,up*=10)
! 	{	if(x>=up) continue;
!  have_i:
! 		oldscale = f__scale;
! 		f__scale = 0;
! 		if(e==0) n=4;
! 		else	n=e+2;
! 		i=wrt_F(p,w-n,d-i,len);
! 		for(j=0;j<n;j++) (*f__putn)(' ');
! 		f__scale=oldscale;
! 		return(i);
! 	}
! 	return(wrt_E(p,w,d,e,len));
  }
! #ifdef KR_headers
! w_ed(p,ptr,len) struct syl *p; char *ptr; ftnlen len;
! #else
! w_ed(struct syl *p, char *ptr, ftnlen len)
! #endif
  {
! 	int i;
  
! 	if(f__cursor && (i = mv_cur()))
! 		return i;
! 	switch(p->op)
! 	{
! 	default:
! 		fprintf(stderr,"w_ed, unexpected code: %d\n", p->op);
! 		sig_die(f__fmtbuf, 1);
! 	case I:	return(wrt_I((Uint *)ptr,p->p1,len, 10));
! 	case IM:
! 		return(wrt_IM((Uint *)ptr,p->p1,p->p2.i[0],len,10));
  
! 		/* O and OM don't work right for character, double, complex, */
! 		/* or doublecomplex, and they differ from Fortran 90 in */
! 		/* showing a minus sign for negative values. */
  
! 	case O:	return(wrt_I((Uint *)ptr, p->p1, len, 8));
! 	case OM:
! 		return(wrt_IM((Uint *)ptr,p->p1,p->p2.i[0],len,8));
! 	case L:	return(wrt_L((Uint *)ptr,p->p1, len));
! 	case A: return(wrt_A(ptr,len));
! 	case AW:
! 		return(wrt_AW(ptr,p->p1,len));
! 	case D:
! 	case E:
! 	case EE:
! 		return(wrt_E((ufloat *)ptr,p->p1,p->p2.i[0],p->p2.i[1],len));
! 	case G:
! 	case GE:
! 		return(wrt_G((ufloat *)ptr,p->p1,p->p2.i[0],p->p2.i[1],len));
! 	case F:	return(wrt_F((ufloat *)ptr,p->p1,p->p2.i[0],len));
  
! 		/* Z and ZM assume 8-bit bytes. */
  
! 	case Z: return(wrt_Z((Uint *)ptr,p->p1,0,len));
! 	case ZM:
! 		return(wrt_Z((Uint *)ptr,p->p1,p->p2.i[0],len));
! 	}
  }
! #ifdef KR_headers
! w_ned(p) struct syl *p;
! #else
! w_ned(struct syl *p)
! #endif
  {
! 	switch(p->op)
! 	{
! 	default: fprintf(stderr,"w_ned, unexpected code: %d\n", p->op);
! 		sig_die(f__fmtbuf, 1);
! 	case SLASH:
! 		return((*f__donewrec)());
! 	case T: f__cursor = p->p1-f__recpos - 1;
! 		return(1);
! 	case TL: f__cursor -= p->p1;
! 		if(f__cursor < -f__recpos)	/* TL1000, 1X */
! 			f__cursor = -f__recpos;
! 		return(1);
! 	case TR:
! 	case X:
! 		f__cursor += p->p1;
! 		return(1);
! 	case APOS:
! 		return(wrt_AP(p->p2.s));
! 	case H:
! 		return(wrt_H(p->p1,p->p2.s));
! 	}
  }
--- 6,401 ----
  extern icilist *f__svic;
  extern char *f__icptr;
  
! static int
! mv_cur (void)			/* shouldn't use fseek because it insists on calling fflush */
  		/* instead we know too much about stdio */
  {
!   int cursor = f__cursor;
!   f__cursor = 0;
!   if (f__external == 0)
!     {
!       if (cursor < 0)
! 	{
! 	  if (f__hiwater < f__recpos)
! 	    f__hiwater = f__recpos;
! 	  f__recpos += cursor;
! 	  f__icptr += cursor;
! 	  if (f__recpos < 0)
! 	    err (f__elist->cierr, 110, "left off");
  	}
!       else if (cursor > 0)
! 	{
! 	  if (f__recpos + cursor >= f__svic->icirlen)
! 	    err (f__elist->cierr, 110, "recend");
! 	  if (f__hiwater <= f__recpos)
! 	    for (; cursor > 0; cursor--)
! 	      (*f__putn) (' ');
! 	  else if (f__hiwater <= f__recpos + cursor)
! 	    {
! 	      cursor -= f__hiwater - f__recpos;
! 	      f__icptr += f__hiwater - f__recpos;
! 	      f__recpos = f__hiwater;
! 	      for (; cursor > 0; cursor--)
! 		(*f__putn) (' ');
! 	    }
! 	  else
! 	    {
! 	      f__icptr += cursor;
! 	      f__recpos += cursor;
! 	    }
  	}
!       return (0);
!     }
!   if (cursor > 0)
!     {
!       if (f__hiwater <= f__recpos)
! 	for (; cursor > 0; cursor--)
! 	  (*f__putn) (' ');
!       else if (f__hiwater <= f__recpos + cursor)
  	{
! 	  cursor -= f__hiwater - f__recpos;
! 	  f__recpos = f__hiwater;
! 	  for (; cursor > 0; cursor--)
! 	    (*f__putn) (' ');
  	}
!       else
! 	{
! 	  f__recpos += cursor;
! 	}
!     }
!   else if (cursor < 0)
!     {
!       if (cursor + f__recpos < 0)
! 	err (f__elist->cierr, 110, "left off");
!       if (f__hiwater < f__recpos)
! 	f__hiwater = f__recpos;
!       f__recpos += cursor;
!     }
!   return (0);
  }
  
! static int
! wrt_Z (Uint * n, int w, int minlen, ftnlen len)
  {
!   register char *s, *se;
!   register int i, w1;
!   static int one = 1;
!   static char hex[] = "0123456789ABCDEF";
!   s = (char *) n;
!   --len;
!   if (*(char *) &one)
!     {
!       /* little endian */
!       se = s;
!       s += len;
!       i = -1;
!     }
!   else
!     {
!       se = s + len;
!       i = 1;
!     }
!   for (;; s += i)
!     if (s == se || *s)
!       break;
!   w1 = (i * (se - s) << 1) + 1;
!   if (*s & 0xf0)
!     w1++;
!   if (w1 > w)
!     for (i = 0; i < w; i++)
!       (*f__putn) ('*');
!   else
!     {
!       if ((minlen -= w1) > 0)
! 	w1 += minlen;
!       while (--w >= w1)
! 	(*f__putn) (' ');
!       while (--minlen >= 0)
! 	(*f__putn) ('0');
!       if (!(*s & 0xf0))
! 	{
! 	  (*f__putn) (hex[*s & 0xf]);
! 	  if (s == se)
! 	    return 0;
! 	  s += i;
  	}
+       for (;; s += i)
+ 	{
+ 	  (*f__putn) (hex[*s >> 4 & 0xf]);
+ 	  (*f__putn) (hex[*s & 0xf]);
+ 	  if (s == se)
+ 	    break;
+ 	}
+     }
+   return 0;
+ }
  
! static int
! wrt_I (Uint * n, int w, ftnlen len, register int base)
! {
!   int ndigit, sign, spare, i;
!   longint x;
!   char *ans;
!   if (len == sizeof (integer))
!     x = n->il;
!   else if (len == sizeof (char))
!     x = n->ic;
  #ifdef Allow_TYQUAD
!   else if (len == sizeof (longint))
!     x = n->ili;
  #endif
!   else
!     x = n->is;
!   ans = f__icvt (x, &ndigit, &sign, base);
!   spare = w - ndigit;
!   if (sign || f__cplus)
!     spare--;
!   if (spare < 0)
!     for (i = 0; i < w; i++)
!       (*f__putn) ('*');
!   else
!     {
!       for (i = 0; i < spare; i++)
! 	(*f__putn) (' ');
!       if (sign)
! 	(*f__putn) ('-');
!       else if (f__cplus)
! 	(*f__putn) ('+');
!       for (i = 0; i < ndigit; i++)
! 	(*f__putn) (*ans++);
!     }
!   return (0);
  }
! static int
! wrt_IM (Uint * n, int w, int m, ftnlen len, int base)
! {
!   int ndigit, sign, spare, i, xsign;
!   longint x;
!   char *ans;
!   if (sizeof (integer) == len)
!     x = n->il;
!   else if (len == sizeof (char))
!     x = n->ic;
  #ifdef Allow_TYQUAD
!   else if (len == sizeof (longint))
!     x = n->ili;
  #endif
!   else
!     x = n->is;
!   ans = f__icvt (x, &ndigit, &sign, base);
!   if (sign || f__cplus)
!     xsign = 1;
!   else
!     xsign = 0;
!   if (ndigit + xsign > w || m + xsign > w)
!     {
!       for (i = 0; i < w; i++)
! 	(*f__putn) ('*');
!       return (0);
!     }
!   if (x == 0 && m == 0)
!     {
!       for (i = 0; i < w; i++)
! 	(*f__putn) (' ');
!       return (0);
!     }
!   if (ndigit >= m)
!     spare = w - ndigit - xsign;
!   else
!     spare = w - m - xsign;
!   for (i = 0; i < spare; i++)
!     (*f__putn) (' ');
!   if (sign)
!     (*f__putn) ('-');
!   else if (f__cplus)
!     (*f__putn) ('+');
!   for (i = 0; i < m - ndigit; i++)
!     (*f__putn) ('0');
!   for (i = 0; i < ndigit; i++)
!     (*f__putn) (*ans++);
!   return (0);
  }
! static int
! wrt_AP (char *s)
! {
!   char quote;
!   int i;
  
!   if (f__cursor && (i = mv_cur ()))
!     return i;
!   quote = *s++;
!   for (; *s; s++)
!     {
!       if (*s != quote)
! 	(*f__putn) (*s);
!       else if (*++s == quote)
! 	(*f__putn) (*s);
!       else
! 	return (1);
!     }
!   return (1);
  }
! static int
! wrt_H (int a, char *s)
  {
!   int i;
  
!   if (f__cursor && (i = mv_cur ()))
!     return i;
!   while (a--)
!     (*f__putn) (*s++);
!   return (1);
  }
! 
! int
! wrt_L (Uint * n, int len, ftnlen sz)
! {
!   int i;
!   long x;
!   if (sizeof (long) == sz)
!     x = n->il;
!   else if (sz == sizeof (char))
!     x = n->ic;
!   else
!     x = n->is;
!   for (i = 0; i < len - 1; i++)
!     (*f__putn) (' ');
!   if (x)
!     (*f__putn) ('T');
!   else
!     (*f__putn) ('F');
!   return (0);
  }
! static int
! wrt_A (char *p, ftnlen len)
  {
!   while (len-- > 0)
!     (*f__putn) (*p++);
!   return (0);
  }
! static int
! wrt_AW (char *p, int w, ftnlen len)
  {
!   while (w > len)
!     {
!       w--;
!       (*f__putn) (' ');
!     }
!   while (w-- > 0)
!     (*f__putn) (*p++);
!   return (0);
  }
  
! static int
! wrt_G (ufloat * p, int w, int d, int e, ftnlen len)
! {
!   double up = 1, x;
!   int i = 0, oldscale, n, j;
!   x = len == sizeof (real) ? p->pf : p->pd;
!   if (x < 0)
!     x = -x;
!   if (x < .1)
!     {
!       if (x != 0.)
! 	return (wrt_E (p, w, d, e, len));
!       i = 1;
!       goto have_i;
!     }
!   for (; i <= d; i++, up *= 10)
!     {
!       if (x >= up)
! 	continue;
!     have_i:
!       oldscale = f__scale;
!       f__scale = 0;
!       if (e == 0)
! 	n = 4;
!       else
! 	n = e + 2;
!       i = wrt_F (p, w - n, d - i, len);
!       for (j = 0; j < n; j++)
! 	(*f__putn) (' ');
!       f__scale = oldscale;
!       return (i);
!     }
!   return (wrt_E (p, w, d, e, len));
  }
! 
! int
! w_ed (struct syl * p, char *ptr, ftnlen len)
  {
!   int i;
  
!   if (f__cursor && (i = mv_cur ()))
!     return i;
!   switch (p->op)
!     {
!     default:
!       fprintf (stderr, "w_ed, unexpected code: %d\n", p->op);
!       sig_die (f__fmtbuf, 1);
!     case I:
!       return (wrt_I ((Uint *) ptr, p->p1, len, 10));
!     case IM:
!       return (wrt_IM ((Uint *) ptr, p->p1, p->p2.i[0], len, 10));
  
!       /* O and OM don't work right for character, double, complex, */
!       /* or doublecomplex, and they differ from Fortran 90 in */
!       /* showing a minus sign for negative values. */
  
!     case O:
!       return (wrt_I ((Uint *) ptr, p->p1, len, 8));
!     case OM:
!       return (wrt_IM ((Uint *) ptr, p->p1, p->p2.i[0], len, 8));
!     case L:
!       return (wrt_L ((Uint *) ptr, p->p1, len));
!     case A:
!       return (wrt_A (ptr, len));
!     case AW:
!       return (wrt_AW (ptr, p->p1, len));
!     case D:
!     case E:
!     case EE:
!       return (wrt_E ((ufloat *) ptr, p->p1, p->p2.i[0], p->p2.i[1], len));
!     case G:
!     case GE:
!       return (wrt_G ((ufloat *) ptr, p->p1, p->p2.i[0], p->p2.i[1], len));
!     case F:
!       return (wrt_F ((ufloat *) ptr, p->p1, p->p2.i[0], len));
  
!       /* Z and ZM assume 8-bit bytes. */
  
!     case Z:
!       return (wrt_Z ((Uint *) ptr, p->p1, 0, len));
!     case ZM:
!       return (wrt_Z ((Uint *) ptr, p->p1, p->p2.i[0], len));
!     }
  }
! 
! int
! w_ned (struct syl * p)
  {
!   switch (p->op)
!     {
!     default:
!       fprintf (stderr, "w_ned, unexpected code: %d\n", p->op);
!       sig_die (f__fmtbuf, 1);
!     case SLASH:
!       return ((*f__donewrec) ());
!     case T:
!       f__cursor = p->p1 - f__recpos - 1;
!       return (1);
!     case TL:
!       f__cursor -= p->p1;
!       if (f__cursor < -f__recpos)	/* TL1000, 1X */
! 	f__cursor = -f__recpos;
!       return (1);
!     case TR:
!     case X:
!       f__cursor += p->p1;
!       return (1);
!     case APOS:
!       return (wrt_AP (p->p2.s));
!     case H:
!       return (wrt_H (p->p1, p->p2.s));
!     }
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libI77/wsfe.c gcc-3.3/libf2c/libI77/wsfe.c
*** gcc-3.2.3/libf2c/libI77/wsfe.c	2001-07-07 18:51:58.000000000 +0000
--- gcc-3.3/libf2c/libI77/wsfe.c	2002-06-02 14:34:31.000000000 +0000
***************
*** 5,76 ****
  #include "fmt.h"
  extern int f__hiwater;
  
!  int
! x_wSL(Void)
  {
! 	int n = f__putbuf('\n');
! 	f__hiwater = f__recpos = f__cursor = 0;
! 	return(n == 0);
  }
  
!  static int
! xw_end(Void)
  {
! 	int n;
  
! 	if(f__nonl) {
! 		f__putbuf(n = 0);
! 		fflush(f__cf);
! 		}
! 	else
! 		n = f__putbuf('\n');
! 	f__hiwater = f__recpos = f__cursor = 0;
! 	return n;
  }
  
!  static int
! xw_rev(Void)
  {
! 	int n = 0;
! 	if(f__workdone) {
! 		n = f__putbuf('\n');
! 		f__workdone = 0;
! 		}
! 	f__hiwater = f__recpos = f__cursor = 0;
! 	return n;
  }
  
! #ifdef KR_headers
! integer s_wsfe(a) cilist *a;	/*start*/
! #else
! integer s_wsfe(cilist *a)	/*start*/
! #endif
! {	int n;
! 	if(f__init != 1) f_init();
! 	f__init = 3;
! 	f__reading=0;
! 	f__sequential=1;
! 	f__formatted=1;
! 	f__external=1;
! 	if(n=c_sfe(a)) return(n);
! 	f__elist=a;
! 	f__hiwater = f__cursor=f__recpos=0;
! 	f__nonl = 0;
! 	f__scale=0;
! 	f__fmtbuf=a->cifmt;
! 	f__curunit = &f__units[a->ciunit];
! 	f__cf=f__curunit->ufd;
! 	if(pars_f(f__fmtbuf)<0) err(a->cierr,100,"startio");
! 	f__putn= x_putc;
! 	f__doed= w_ed;
! 	f__doned= w_ned;
! 	f__doend=xw_end;
! 	f__dorevert=xw_rev;
! 	f__donewrec=x_wSL;
! 	fmt_bg();
! 	f__cplus=0;
! 	f__cblank=f__curunit->ublnk;
! 	if(f__curunit->uwrt != 1 && f__nowwriting(f__curunit))
! 		err(a->cierr,errno,"write start");
! 	return(0);
  }
--- 5,79 ----
  #include "fmt.h"
  extern int f__hiwater;
  
! int
! x_wSL (void)
  {
!   int n = f__putbuf ('\n');
!   f__hiwater = f__recpos = f__cursor = 0;
!   return (n == 0);
  }
  
! static int
! xw_end (void)
  {
!   int n;
  
!   if (f__nonl)
!     {
!       f__putbuf (n = 0);
!       fflush (f__cf);
!     }
!   else
!     n = f__putbuf ('\n');
!   f__hiwater = f__recpos = f__cursor = 0;
!   return n;
  }
  
! static int
! xw_rev (void)
  {
!   int n = 0;
!   if (f__workdone)
!     {
!       n = f__putbuf ('\n');
!       f__workdone = 0;
!     }
!   f__hiwater = f__recpos = f__cursor = 0;
!   return n;
  }
  
! integer
! s_wsfe (cilist * a)		/*start */
! {
!   int n;
!   if (f__init != 1)
!     f_init ();
!   f__init = 3;
!   f__reading = 0;
!   f__sequential = 1;
!   f__formatted = 1;
!   f__external = 1;
!   if ((n = c_sfe (a)))
!     return (n);
!   f__elist = a;
!   f__hiwater = f__cursor = f__recpos = 0;
!   f__nonl = 0;
!   f__scale = 0;
!   f__fmtbuf = a->cifmt;
!   f__curunit = &f__units[a->ciunit];
!   f__cf = f__curunit->ufd;
!   if (pars_f (f__fmtbuf) < 0)
!     err (a->cierr, 100, "startio");
!   f__putn = x_putc;
!   f__doed = w_ed;
!   f__doned = w_ned;
!   f__doend = xw_end;
!   f__dorevert = xw_rev;
!   f__donewrec = x_wSL;
!   fmt_bg ();
!   f__cplus = 0;
!   f__cblank = f__curunit->ublnk;
!   if (f__curunit->uwrt != 1 && f__nowwriting (f__curunit))
!     err (a->cierr, errno, "write start");
!   return (0);
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libI77/wsle.c gcc-3.3/libf2c/libI77/wsle.c
*** gcc-3.2.3/libf2c/libI77/wsle.c	2001-05-16 18:59:29.000000000 +0000
--- gcc-3.3/libf2c/libI77/wsle.c	2002-06-02 14:34:31.000000000 +0000
***************
*** 5,39 ****
  #include "lio.h"
  #include "string.h"
  
! #ifdef KR_headers
! integer s_wsle(a) cilist *a;
! #else
! integer s_wsle(cilist *a)
! #endif
  {
! 	int n;
! 	if(n=c_le(a)) return(n);
! 	f__reading=0;
! 	f__external=1;
! 	f__formatted=1;
! 	f__putn = x_putc;
! 	f__lioproc = l_write;
! 	L_len = LINE;
! 	f__donewrec = x_wSL;
! 	if(f__curunit->uwrt != 1 && f__nowwriting(f__curunit))
! 		err(a->cierr, errno, "list output start");
! 	return(0);
! 	}
  
! integer e_wsle(Void)
  {
! 	int n;
! 	f__init = 1;
! 	n = f__putbuf('\n');
! 	f__recpos=0;
  #ifdef ALWAYS_FLUSH
! 	if (!n && fflush(f__cf))
! 		err(f__elist->cierr, errno, "write end");
  #endif
! 	return(n);
! 	}
--- 5,38 ----
  #include "lio.h"
  #include "string.h"
  
! integer
! s_wsle (cilist * a)
  {
!   int n;
!   if ((n = c_le (a)))
!     return (n);
!   f__reading = 0;
!   f__external = 1;
!   f__formatted = 1;
!   f__putn = x_putc;
!   f__lioproc = l_write;
!   L_len = LINE;
!   f__donewrec = x_wSL;
!   if (f__curunit->uwrt != 1 && f__nowwriting (f__curunit))
!     err (a->cierr, errno, "list output start");
!   return (0);
! }
  
! integer
! e_wsle (void)
  {
!   int n;
!   f__init = 1;
!   n = f__putbuf ('\n');
!   f__recpos = 0;
  #ifdef ALWAYS_FLUSH
!   if (!n && fflush (f__cf))
!     err (f__elist->cierr, errno, "write end");
  #endif
!   return (n);
! }
diff -Nrc3pad gcc-3.2.3/libf2c/libI77/wsne.c gcc-3.3/libf2c/libI77/wsne.c
*** gcc-3.2.3/libf2c/libI77/wsne.c	1998-05-19 10:51:19.000000000 +0000
--- gcc-3.3/libf2c/libI77/wsne.c	2002-06-02 14:34:31.000000000 +0000
***************
*** 2,26 ****
  #include "fio.h"
  #include "lio.h"
  
!  integer
! #ifdef KR_headers
! s_wsne(a) cilist *a;
! #else
! s_wsne(cilist *a)
! #endif
  {
! 	int n;
  
! 	if(n=c_le(a))
! 		return(n);
! 	f__reading=0;
! 	f__external=1;
! 	f__formatted=1;
! 	f__putn = x_putc;
! 	L_len = LINE;
! 	f__donewrec = x_wSL;
! 	if(f__curunit->uwrt != 1 && f__nowwriting(f__curunit))
! 		err(a->cierr, errno, "namelist output start");
! 	x_wsne(a);
! 	return e_wsle();
! 	}
--- 2,22 ----
  #include "fio.h"
  #include "lio.h"
  
! integer
! s_wsne (cilist * a)
  {
!   int n;
  
!   if ((n = c_le (a)))
!     return (n);
!   f__reading = 0;
!   f__external = 1;
!   f__formatted = 1;
!   f__putn = x_putc;
!   L_len = LINE;
!   f__donewrec = x_wSL;
!   if (f__curunit->uwrt != 1 && f__nowwriting (f__curunit))
!     err (a->cierr, errno, "namelist output start");
!   x_wsne (a);
!   return e_wsle ();
! }
diff -Nrc3pad gcc-3.2.3/libf2c/libI77/xwsne.c gcc-3.3/libf2c/libI77/xwsne.c
*** gcc-3.2.3/libf2c/libI77/xwsne.c	2001-05-16 18:59:29.000000000 +0000
--- gcc-3.3/libf2c/libI77/xwsne.c	2002-06-01 12:38:30.000000000 +0000
***************
*** 6,72 ****
  
  extern int f__Aquote;
  
!  static VOID
! nl_donewrec(Void)
  {
! 	(*f__donewrec)();
! 	PUT(' ');
! 	}
  
- #ifdef KR_headers
- x_wsne(a) cilist *a;
- #else
  #include <string.h>
  
!  VOID
! x_wsne(cilist *a)
! #endif
  {
! 	Namelist *nl;
! 	char *s;
! 	Vardesc *v, **vd, **vde;
! 	ftnint number, type;
! 	ftnlen *dims;
! 	ftnlen size;
! 	extern ftnlen f__typesize[];
  
! 	nl = (Namelist *)a->cifmt;
! 	PUT('&');
! 	for(s = nl->name; *s; s++)
! 		PUT(*s);
! 	PUT(' ');
! 	f__Aquote = 1;
! 	vd = nl->vars;
! 	vde = vd + nl->nvars;
! 	while(vd < vde) {
! 		v = *vd++;
! 		s = v->name;
  #ifdef No_Extra_Namelist_Newlines
! 		if (f__recpos+strlen(s)+2 >= L_len)
  #endif
! 			nl_donewrec();
! 		while(*s)
! 			PUT(*s++);
! 		PUT(' ');
! 		PUT('=');
! 		number = (dims = v->dims) ? dims[1] : 1;
! 		type = v->type;
! 		if (type < 0) {
! 			size = -type;
! 			type = TYCHAR;
! 			}
! 		else
! 			size = f__typesize[type];
! 		l_write(&number, v->addr, size, type);
! 		if (vd < vde) {
! 			if (f__recpos+2 >= L_len)
! 				nl_donewrec();
! 			PUT(',');
! 			PUT(' ');
! 			}
! 		else if (f__recpos+1 >= L_len)
! 			nl_donewrec();
! 		}
! 	f__Aquote = 0;
! 	PUT('/');
  	}
--- 6,71 ----
  
  extern int f__Aquote;
  
! static void
! nl_donewrec (void)
  {
!   (*f__donewrec) ();
!   PUT (' ');
! }
  
  #include <string.h>
  
! void
! x_wsne (cilist * a)
  {
!   Namelist *nl;
!   char *s;
!   Vardesc *v, **vd, **vde;
!   ftnint number, type;
!   ftnlen *dims;
!   ftnlen size;
!   extern ftnlen f__typesize[];
  
!   nl = (Namelist *) a->cifmt;
!   PUT ('&');
!   for (s = nl->name; *s; s++)
!     PUT (*s);
!   PUT (' ');
!   f__Aquote = 1;
!   vd = nl->vars;
!   vde = vd + nl->nvars;
!   while (vd < vde)
!     {
!       v = *vd++;
!       s = v->name;
  #ifdef No_Extra_Namelist_Newlines
!       if (f__recpos + strlen (s) + 2 >= L_len)
  #endif
! 	nl_donewrec ();
!       while (*s)
! 	PUT (*s++);
!       PUT (' ');
!       PUT ('=');
!       number = (dims = v->dims) ? dims[1] : 1;
!       type = v->type;
!       if (type < 0)
! 	{
! 	  size = -type;
! 	  type = TYCHAR;
  	}
+       else
+ 	size = f__typesize[type];
+       l_write (&number, v->addr, size, type);
+       if (vd < vde)
+ 	{
+ 	  if (f__recpos + 2 >= L_len)
+ 	    nl_donewrec ();
+ 	  PUT (',');
+ 	  PUT (' ');
+ 	}
+       else if (f__recpos + 1 >= L_len)
+ 	nl_donewrec ();
+     }
+   f__Aquote = 0;
+   PUT ('/');
+ }
diff -Nrc3pad gcc-3.2.3/libf2c/libU77/access_.c gcc-3.3/libf2c/libU77/access_.c
*** gcc-3.2.3/libf2c/libU77/access_.c	1999-09-04 15:09:18.000000000 +0000
--- gcc-3.3/libf2c/libU77/access_.c	2002-06-02 12:59:22.000000000 +0000
*************** Boston, MA 02111-1307, USA.  */
*** 45,79 ****
  #  define F_OK 0
  #endif
  
! #ifdef KR_headers
! void g_char ();
! 
! integer G77_access_0 (name, mode, Lname, Lmode)
!      char *name, *mode;
!      ftnlen Lname, Lmode;
! #else
! void g_char(const char *a, ftnlen alen, char *b);
  
! integer G77_access_0 (const char *name, const char *mode, ftnlen Lname, ftnlen Lmode)
! #endif
  {
    char *buff;
-   char *bp, *blast;
    int amode, i;
  
!   buff = malloc (Lname+1);
!   if (!buff) return -1;
    g_char (name, Lname, buff);
    amode = 0;
!   for (i=0;i<Lmode;i++) {
!     switch (mode[i]) {
!     case 'r': amode |= R_OK; break;
!     case 'w': amode |= W_OK; break;
!     case 'x': amode |= X_OK; break;
!     case ' ': amode |= F_OK; break; /* as per Sun, at least */
!     default: return EINVAL;
      }
-   }
    i = access (buff, amode);
    free (buff);
    return i;
--- 45,83 ----
  #  define F_OK 0
  #endif
  
! void g_char (const char *a, ftnlen alen, char *b);
  
! integer
! G77_access_0 (const char *name, const char *mode, ftnlen Lname, ftnlen Lmode)
  {
    char *buff;
    int amode, i;
  
!   buff = malloc (Lname + 1);
!   if (!buff)
!     return -1;
    g_char (name, Lname, buff);
    amode = 0;
!   for (i = 0; i < Lmode; i++)
!     {
!       switch (mode[i])
! 	{
! 	case 'r':
! 	  amode |= R_OK;
! 	  break;
! 	case 'w':
! 	  amode |= W_OK;
! 	  break;
! 	case 'x':
! 	  amode |= X_OK;
! 	  break;
! 	case ' ':
! 	  amode |= F_OK;
! 	  break;		/* as per Sun, at least */
! 	default:
! 	  return EINVAL;
! 	}
      }
    i = access (buff, amode);
    free (buff);
    return i;
diff -Nrc3pad gcc-3.2.3/libf2c/libU77/alarm_.c gcc-3.3/libf2c/libU77/alarm_.c
*** gcc-3.2.3/libf2c/libU77/alarm_.c	2001-01-25 05:11:38.000000000 +0000
--- gcc-3.3/libf2c/libU77/alarm_.c	2002-06-01 12:38:32.000000000 +0000
*************** Boston, MA 02111-1307, USA.  */
*** 29,64 ****
  
  #ifndef RETSIGTYPE
  /* we shouldn't rely on this... */
- #ifdef KR_headers
- #define RETSIGTYPE int
- #else
  #define RETSIGTYPE void
  #endif
! #endif
! typedef RETSIGTYPE (*sig_type)();
  
- #ifdef KR_headers
- extern sig_type signal();
- #else
  #include <signal.h>
! typedef int (*sig_proc)(int);
! #endif
  
  #ifndef SIG_ERR
  #define SIG_ERR ((sig_type) -1)
  #endif
  
! #ifdef KR_headers
! integer G77_alarm_0 (seconds, proc)
!      integer *seconds;
!      sig_type proc;
! #else
! integer G77_alarm_0 (integer *seconds, sig_proc proc)
! #endif
  {
    int status;
  #if defined (HAVE_ALARM) && defined (SIGALRM)
!   if (signal(SIGALRM, (sig_type)proc) == SIG_ERR)
      status = -1;
    else
      status = alarm (*seconds);
--- 29,51 ----
  
  #ifndef RETSIGTYPE
  /* we shouldn't rely on this... */
  #define RETSIGTYPE void
  #endif
! typedef RETSIGTYPE (*sig_type) ();
  
  #include <signal.h>
! typedef int (*sig_proc) (int);
  
  #ifndef SIG_ERR
  #define SIG_ERR ((sig_type) -1)
  #endif
  
! integer
! G77_alarm_0 (integer * seconds, sig_proc proc)
  {
    int status;
  #if defined (HAVE_ALARM) && defined (SIGALRM)
!   if (signal (SIGALRM, (sig_type) proc) == SIG_ERR)
      status = -1;
    else
      status = alarm (*seconds);
diff -Nrc3pad gcc-3.2.3/libf2c/libU77/bes.c gcc-3.3/libf2c/libU77/bes.c
*** gcc-3.2.3/libf2c/libU77/bes.c	1999-09-04 15:09:18.000000000 +0000
--- gcc-3.3/libf2c/libU77/bes.c	2002-06-01 12:38:32.000000000 +0000
*************** License along with GNU Fortran; see the 
*** 16,46 ****
  not, write to the Free Software Foundation, Inc., 59 Temple Place - Suite 330,
  Boston, MA 02111-1307, USA.  */
  
! #if 0 	/* Don't include these unless necessary -- jcb. */
  #include "f2c.h"
  #include <math.h>
  
! double G77_besj0_0 (const real *x) {
!     return j0 (*x);
  }
  
! double G77_besj1_0 (const real *x) {
!     return j1 (*x);
  }
  
! double G77_besjn_0 (const integer *n, real *x) {
!      return jn (*n, *x);
!  }
  
! double G77_besy0_0 (const real *x) {
!     return y0 (*x);
  }
  
! double G77_besy1_0 (const real *x) {
!     return y1 (*x);
  }
  
! double G77_besyn_0 (const integer *n, real *x) {
!     return yn (*n, *x);
  }
  #endif
--- 16,58 ----
  not, write to the Free Software Foundation, Inc., 59 Temple Place - Suite 330,
  Boston, MA 02111-1307, USA.  */
  
! #if 0				/* Don't include these unless necessary -- jcb. */
  #include "f2c.h"
  #include <math.h>
  
! double
! G77_besj0_0 (const real * x)
! {
!   return j0 (*x);
  }
  
! double
! G77_besj1_0 (const real * x)
! {
!   return j1 (*x);
  }
  
! double
! G77_besjn_0 (const integer * n, real * x)
! {
!   return jn (*n, *x);
! }
  
! double
! G77_besy0_0 (const real * x)
! {
!   return y0 (*x);
  }
  
! double
! G77_besy1_0 (const real * x)
! {
!   return y1 (*x);
  }
  
! double
! G77_besyn_0 (const integer * n, real * x)
! {
!   return yn (*n, *x);
  }
  #endif
diff -Nrc3pad gcc-3.2.3/libf2c/libU77/chdir_.c gcc-3.3/libf2c/libU77/chdir_.c
*** gcc-3.2.3/libf2c/libU77/chdir_.c	1999-09-04 15:09:18.000000000 +0000
--- gcc-3.3/libf2c/libU77/chdir_.c	2002-06-02 12:59:22.000000000 +0000
*************** Boston, MA 02111-1307, USA.  */
*** 32,55 ****
  #include "f2c.h"
  
  
! #ifdef KR_headers
! void g_char ();
! 
! integer G77_chdir_0 (name, Lname)
!      char *name;
!      ftnlen Lname;
! #else
! void g_char(const char *a, ftnlen alen, char *b);
  
! integer G77_chdir_0 (const char *name, const ftnlen Lname)
! #endif
  {
    char *buff;
-   char *bp, *blast;
    int i;
  
!   buff = malloc (Lname+1);
!   if (!buff) return -1;
    g_char (name, Lname, buff);
    i = chdir (buff);
    free (buff);
--- 32,48 ----
  #include "f2c.h"
  
  
! void g_char (const char *a, ftnlen alen, char *b);
  
! integer
! G77_chdir_0 (const char *name, const ftnlen Lname)
  {
    char *buff;
    int i;
  
!   buff = malloc (Lname + 1);
!   if (!buff)
!     return -1;
    g_char (name, Lname, buff);
    i = chdir (buff);
    free (buff);
diff -Nrc3pad gcc-3.2.3/libf2c/libU77/chmod_.c gcc-3.3/libf2c/libU77/chmod_.c
*** gcc-3.2.3/libf2c/libU77/chmod_.c	1999-09-04 15:09:18.000000000 +0000
--- gcc-3.3/libf2c/libU77/chmod_.c	2002-06-02 12:59:22.000000000 +0000
*************** Boston, MA 02111-1307, USA.  */
*** 41,81 ****
  #define CHMOD_PATH "/bin/chmod"
  #endif
  
! #ifdef KR_headers
! extern void s_cat ();
! void g_char ();
! 
! integer G77_chmod_0 (name, mode, Lname, Lmode)
!      char *name, *mode;
!      ftnlen Lname, Lmode;
! #else
! extern void s_cat(char *lp, char *rpp[], ftnlen rnp[], ftnlen *np, ftnlen ll);
! void g_char(const char *a, ftnlen alen, char *b);
  
! integer G77_chmod_0 (/* const */ char *name, /* const */ char *mode, const ftnlen Lname, const ftnlen Lmode)
! #endif
  {
    char *buff;
-   char *bp, *blast;
    int i;
    ftnlen l, l2;
    ftnlen six = 6;
    address a[6];
    ftnlen ii[6];
!   char chmod_path [] = CHMOD_PATH;
    l = strlen (chmod_path);
!   buff = malloc (Lname+Lmode+l+3+13+1);
!   if (!buff) return -1;
!   ii[0] = l; a[0] = chmod_path;
!   ii[1] = 1; a[1] = " ";
!   ii[2] = Lmode; a[2] = mode;
!   ii[3] = 2; a[3] = " '";
!   for (l2=Lname; (l2 > 1) && (name[l2-1] == ' '); )
      l2--;
!   ii[4] = l2; a[4] = name;
!   ii[5] = 13; a[5] = "' 2>/dev/null";
!   s_cat (buff, a, ii, &six, Lname+Lmode+l+3+13);
!   buff[Lname+Lmode+l+3+13] = '\0';
    i = system (buff);
    free (buff);
    return i;
--- 41,81 ----
  #define CHMOD_PATH "/bin/chmod"
  #endif
  
! extern void s_cat (char *lp, char *rpp[], ftnlen rnp[], ftnlen * np,
! 		   ftnlen ll);
! void g_char (const char *a, ftnlen alen, char *b);
  
! integer
! G77_chmod_0 ( /* const */ char *name, /* const */ char *mode,
! 	     const ftnlen Lname, const ftnlen Lmode)
  {
    char *buff;
    int i;
    ftnlen l, l2;
    ftnlen six = 6;
    address a[6];
    ftnlen ii[6];
!   char chmod_path[] = CHMOD_PATH;
    l = strlen (chmod_path);
!   buff = malloc (Lname + Lmode + l + 3 + 13 + 1);
!   if (!buff)
!     return -1;
!   ii[0] = l;
!   a[0] = chmod_path;
!   ii[1] = 1;
!   a[1] = " ";
!   ii[2] = Lmode;
!   a[2] = mode;
!   ii[3] = 2;
!   a[3] = " '";
!   for (l2 = Lname; (l2 > 1) && (name[l2 - 1] == ' ');)
      l2--;
!   ii[4] = l2;
!   a[4] = name;
!   ii[5] = 13;
!   a[5] = "' 2>/dev/null";
!   s_cat (buff, a, ii, &six, Lname + Lmode + l + 3 + 13);
!   buff[Lname + Lmode + l + 3 + 13] = '\0';
    i = system (buff);
    free (buff);
    return i;
diff -Nrc3pad gcc-3.2.3/libf2c/libU77/config.hin gcc-3.3/libf2c/libU77/config.hin
*** gcc-3.2.3/libf2c/libU77/config.hin	2001-09-30 22:50:54.000000000 +0000
--- gcc-3.3/libf2c/libU77/config.hin	2002-06-01 01:53:53.000000000 +0000
***************
*** 33,38 ****
--- 33,44 ----
  /* Define as the path of the `chmod' program. */
  #undef CHMOD_PATH
  
+ /* Define if your gettimeofday takes only one argument. */
+ #undef GETTIMEOFDAY_ONE_ARGUMENT
+ 
+ /* Define if your gettimeofday takes a time zome argument. */
+ #undef HAVE_TIMEZONE
+ 
  /* Define if you have the alarm function.  */
  #undef HAVE_ALARM
  
***************
*** 54,59 ****
--- 60,68 ----
  /* Define if you have the getrusage function.  */
  #undef HAVE_GETRUSAGE
  
+ /* Define if you have the gettimeofday function.  */
+ #undef HAVE_GETTIMEOFDAY
+ 
  /* Define if you have the getuid function.  */
  #undef HAVE_GETUID
  
diff -Nrc3pad gcc-3.2.3/libf2c/libU77/configure gcc-3.3/libf2c/libU77/configure
*** gcc-3.2.3/libf2c/libU77/configure	2002-01-29 13:21:08.000000000 +0000
--- gcc-3.3/libf2c/libU77/configure	2003-04-24 01:58:04.000000000 +0000
*************** program_suffix=NONE
*** 28,33 ****
--- 28,34 ----
  program_transform_name=s,x,x,
  silent=
  site=
+ sitefile=
  srcdir=
  target=NONE
  verbose=
*************** Configuration:
*** 142,147 ****
--- 143,149 ----
    --help                  print this message
    --no-create             do not create output files
    --quiet, --silent       do not print \`checking...' messages
+   --site-file=FILE        use FILE as the site file
    --version               print the version of autoconf that created configure
  Directory and file names:
    --prefix=PREFIX         install architecture-independent files in PREFIX
*************** EOF
*** 312,317 ****
--- 314,324 ----
    -site=* | --site=* | --sit=*)
      site="$ac_optarg" ;;
  
+   -site-file | --site-file | --site-fil | --site-fi | --site-f)
+     ac_prev=sitefile ;;
+   -site-file=* | --site-file=* | --site-fil=* | --site-fi=* | --site-f=*)
+     sitefile="$ac_optarg" ;;
+ 
    -srcdir | --srcdir | --srcdi | --srcd | --src | --sr)
      ac_prev=srcdir ;;
    -srcdir=* | --srcdir=* | --srcdi=* | --srcd=* | --src=* | --sr=*)
*************** fi
*** 477,488 ****
  srcdir=`echo "${srcdir}" | sed 's%\([^/]\)/*$%\1%'`
  
  # Prefer explicitly selected file to automatically selected ones.
! if test -z "$CONFIG_SITE"; then
!   if test "x$prefix" != xNONE; then
!     CONFIG_SITE="$prefix/share/config.site $prefix/etc/config.site"
!   else
!     CONFIG_SITE="$ac_default_prefix/share/config.site $ac_default_prefix/etc/config.site"
    fi
  fi
  for ac_site_file in $CONFIG_SITE; do
    if test -r "$ac_site_file"; then
--- 484,499 ----
  srcdir=`echo "${srcdir}" | sed 's%\([^/]\)/*$%\1%'`
  
  # Prefer explicitly selected file to automatically selected ones.
! if test -z "$sitefile"; then
!   if test -z "$CONFIG_SITE"; then
!     if test "x$prefix" != xNONE; then
!       CONFIG_SITE="$prefix/share/config.site $prefix/etc/config.site"
!     else
!       CONFIG_SITE="$ac_default_prefix/share/config.site $ac_default_prefix/etc/config.site"
!     fi
    fi
+ else
+   CONFIG_SITE="$sitefile"
  fi
  for ac_site_file in $CONFIG_SITE; do
    if test -r "$ac_site_file"; then
*************** fi
*** 523,550 ****
  
  
  
- # These defines are necessary to get 64-bit file size support.
- 
- cat >> confdefs.h <<\EOF
- #define _XOPEN_SOURCE 500L
- EOF
- 
- # The following is needed by irix6.2 so that struct timeval is declared.
- cat >> confdefs.h <<\EOF
- #define _XOPEN_SOURCE_EXTENDED 1
- EOF
- 
- # The following is needed by Solaris2.5.1 so that struct timeval is declared.
- cat >> confdefs.h <<\EOF
- #define __EXTENSIONS__ 1
- EOF
- 
- cat >> confdefs.h <<\EOF
- #define _FILE_OFFSET_BITS 64
- EOF
- 
- 
- 
  
  
  # For g77 we'll set CC to point at the built gcc, but this will get it into
--- 534,539 ----
*************** EOF
*** 552,558 ****
  # Extract the first word of "gcc", so it can be a program name with args.
  set dummy gcc; ac_word=$2
  echo $ac_n "checking for $ac_word""... $ac_c" 1>&6
! echo "configure:556: checking for $ac_word" >&5
  if eval "test \"`echo '$''{'ac_cv_prog_CC'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
--- 541,547 ----
  # Extract the first word of "gcc", so it can be a program name with args.
  set dummy gcc; ac_word=$2
  echo $ac_n "checking for $ac_word""... $ac_c" 1>&6
! echo "configure:545: checking for $ac_word" >&5
  if eval "test \"`echo '$''{'ac_cv_prog_CC'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
*************** if test -z "$CC"; then
*** 582,588 ****
    # Extract the first word of "cc", so it can be a program name with args.
  set dummy cc; ac_word=$2
  echo $ac_n "checking for $ac_word""... $ac_c" 1>&6
! echo "configure:586: checking for $ac_word" >&5
  if eval "test \"`echo '$''{'ac_cv_prog_CC'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
--- 571,577 ----
    # Extract the first word of "cc", so it can be a program name with args.
  set dummy cc; ac_word=$2
  echo $ac_n "checking for $ac_word""... $ac_c" 1>&6
! echo "configure:575: checking for $ac_word" >&5
  if eval "test \"`echo '$''{'ac_cv_prog_CC'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
*************** fi
*** 633,639 ****
        # Extract the first word of "cl", so it can be a program name with args.
  set dummy cl; ac_word=$2
  echo $ac_n "checking for $ac_word""... $ac_c" 1>&6
! echo "configure:637: checking for $ac_word" >&5
  if eval "test \"`echo '$''{'ac_cv_prog_CC'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
--- 622,628 ----
        # Extract the first word of "cl", so it can be a program name with args.
  set dummy cl; ac_word=$2
  echo $ac_n "checking for $ac_word""... $ac_c" 1>&6
! echo "configure:626: checking for $ac_word" >&5
  if eval "test \"`echo '$''{'ac_cv_prog_CC'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
*************** fi
*** 666,672 ****
  
  
  echo $ac_n "checking whether we are using GNU C""... $ac_c" 1>&6
! echo "configure:670: checking whether we are using GNU C" >&5
  if eval "test \"`echo '$''{'ac_cv_prog_gcc'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
--- 655,661 ----
  
  
  echo $ac_n "checking whether we are using GNU C""... $ac_c" 1>&6
! echo "configure:659: checking whether we are using GNU C" >&5
  if eval "test \"`echo '$''{'ac_cv_prog_gcc'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
*************** else
*** 675,681 ****
    yes;
  #endif
  EOF
! if { ac_try='${CC-cc} -E conftest.c'; { (eval echo configure:679: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; }; } | egrep yes >/dev/null 2>&1; then
    ac_cv_prog_gcc=yes
  else
    ac_cv_prog_gcc=no
--- 664,670 ----
    yes;
  #endif
  EOF
! if { ac_try='${CC-cc} -E conftest.c'; { (eval echo configure:668: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; }; } | egrep yes >/dev/null 2>&1; then
    ac_cv_prog_gcc=yes
  else
    ac_cv_prog_gcc=no
*************** ac_test_CFLAGS="${CFLAGS+set}"
*** 694,700 ****
  ac_save_CFLAGS="$CFLAGS"
  CFLAGS=
  echo $ac_n "checking whether ${CC-cc} accepts -g""... $ac_c" 1>&6
! echo "configure:698: checking whether ${CC-cc} accepts -g" >&5
  if eval "test \"`echo '$''{'ac_cv_prog_cc_g'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
--- 683,689 ----
  ac_save_CFLAGS="$CFLAGS"
  CFLAGS=
  echo $ac_n "checking whether ${CC-cc} accepts -g""... $ac_c" 1>&6
! echo "configure:687: checking whether ${CC-cc} accepts -g" >&5
  if eval "test \"`echo '$''{'ac_cv_prog_cc_g'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
*************** else
*** 726,731 ****
--- 715,767 ----
  fi
  
  
+ # These defines are necessary to get 64-bit file size support.
+ # NetBSD 1.4 header files does not support XOPEN_SOURCE == 600, but it
+ # handles 64-bit file sizes without needing these defines.
+ echo $ac_n "checking whether _XOPEN_SOURCE may be defined""... $ac_c" 1>&6
+ echo "configure:723: checking whether _XOPEN_SOURCE may be defined" >&5
+ cat > conftest.$ac_ext <<EOF
+ #line 725 "configure"
+ #include "confdefs.h"
+ #define _XOPEN_SOURCE 600L
+ #include <unistd.h>
+ int main() {
+ 
+ ; return 0; }
+ EOF
+ if { (eval echo configure:733: \"$ac_compile\") 1>&5; (eval $ac_compile) 2>&5; }; then
+   rm -rf conftest*
+   may_use_xopen_source=yes
+ else
+   echo "configure: failed program was:" >&5
+   cat conftest.$ac_ext >&5
+   rm -rf conftest*
+   may_use_xopen_source=no
+ fi
+ rm -f conftest*
+ echo "$ac_t""$may_use_xopen_source" 1>&6
+ if test $may_use_xopen_source = yes; then
+   cat >> confdefs.h <<\EOF
+ #define _XOPEN_SOURCE 600L
+ EOF
+ 
+   # The following is needed by irix6.2 so that struct timeval is declared.
+   cat >> confdefs.h <<\EOF
+ #define _XOPEN_SOURCE_EXTENDED 1
+ EOF
+ 
+   # The following is needed by Solaris2.5.1 so that struct timeval is declared.
+   cat >> confdefs.h <<\EOF
+ #define __EXTENSIONS__ 1
+ EOF
+ 
+   cat >> confdefs.h <<\EOF
+ #define _FILE_OFFSET_BITS 64
+ EOF
+ 
+ fi
+ 
+ 
  LIBTOOL='$(SHELL) ../libtool'
  
  
*************** fi
*** 738,744 ****
  test "$AR" || AR=ar
  
  echo $ac_n "checking whether ${MAKE-make} sets \${MAKE}""... $ac_c" 1>&6
! echo "configure:742: checking whether ${MAKE-make} sets \${MAKE}" >&5
  set dummy ${MAKE-make}; ac_make=`echo "$2" | sed 'y%./+-%__p_%'`
  if eval "test \"`echo '$''{'ac_cv_prog_make_${ac_make}_set'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
--- 774,780 ----
  test "$AR" || AR=ar
  
  echo $ac_n "checking whether ${MAKE-make} sets \${MAKE}""... $ac_c" 1>&6
! echo "configure:778: checking whether ${MAKE-make} sets \${MAKE}" >&5
  set dummy ${MAKE-make}; ac_make=`echo "$2" | sed 'y%./+-%__p_%'`
  if eval "test \"`echo '$''{'ac_cv_prog_make_${ac_make}_set'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
*************** fi
*** 768,774 ****
  # Extract the first word of "chmod", so it can be a program name with args.
  set dummy chmod; ac_word=$2
  echo $ac_n "checking for $ac_word""... $ac_c" 1>&6
! echo "configure:772: checking for $ac_word" >&5
  if eval "test \"`echo '$''{'ac_cv_path_ac_cv_prog_chmod'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
--- 804,810 ----
  # Extract the first word of "chmod", so it can be a program name with args.
  set dummy chmod; ac_word=$2
  echo $ac_n "checking for $ac_word""... $ac_c" 1>&6
! echo "configure:808: checking for $ac_word" >&5
  if eval "test \"`echo '$''{'ac_cv_path_ac_cv_prog_chmod'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
*************** else
*** 812,818 ****
  fi
  
  echo $ac_n "checking how to run the C preprocessor""... $ac_c" 1>&6
! echo "configure:816: checking how to run the C preprocessor" >&5
  # On Suns, sometimes $CPP names a directory.
  if test -n "$CPP" && test -d "$CPP"; then
    CPP=
--- 848,854 ----
  fi
  
  echo $ac_n "checking how to run the C preprocessor""... $ac_c" 1>&6
! echo "configure:852: checking how to run the C preprocessor" >&5
  # On Suns, sometimes $CPP names a directory.
  if test -n "$CPP" && test -d "$CPP"; then
    CPP=
*************** else
*** 827,839 ****
    # On the NeXT, cc -E runs the code through the compiler's parser,
    # not just through cpp.
    cat > conftest.$ac_ext <<EOF
! #line 831 "configure"
  #include "confdefs.h"
  #include <assert.h>
  Syntax Error
  EOF
  ac_try="$ac_cpp conftest.$ac_ext >/dev/null 2>conftest.out"
! { (eval echo configure:837: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; }
  ac_err=`grep -v '^ *+' conftest.out | grep -v "^conftest.${ac_ext}\$"`
  if test -z "$ac_err"; then
    :
--- 863,875 ----
    # On the NeXT, cc -E runs the code through the compiler's parser,
    # not just through cpp.
    cat > conftest.$ac_ext <<EOF
! #line 867 "configure"
  #include "confdefs.h"
  #include <assert.h>
  Syntax Error
  EOF
  ac_try="$ac_cpp conftest.$ac_ext >/dev/null 2>conftest.out"
! { (eval echo configure:873: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; }
  ac_err=`grep -v '^ *+' conftest.out | grep -v "^conftest.${ac_ext}\$"`
  if test -z "$ac_err"; then
    :
*************** else
*** 844,856 ****
    rm -rf conftest*
    CPP="${CC-cc} -E -traditional-cpp"
    cat > conftest.$ac_ext <<EOF
! #line 848 "configure"
  #include "confdefs.h"
  #include <assert.h>
  Syntax Error
  EOF
  ac_try="$ac_cpp conftest.$ac_ext >/dev/null 2>conftest.out"
! { (eval echo configure:854: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; }
  ac_err=`grep -v '^ *+' conftest.out | grep -v "^conftest.${ac_ext}\$"`
  if test -z "$ac_err"; then
    :
--- 880,892 ----
    rm -rf conftest*
    CPP="${CC-cc} -E -traditional-cpp"
    cat > conftest.$ac_ext <<EOF
! #line 884 "configure"
  #include "confdefs.h"
  #include <assert.h>
  Syntax Error
  EOF
  ac_try="$ac_cpp conftest.$ac_ext >/dev/null 2>conftest.out"
! { (eval echo configure:890: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; }
  ac_err=`grep -v '^ *+' conftest.out | grep -v "^conftest.${ac_ext}\$"`
  if test -z "$ac_err"; then
    :
*************** else
*** 861,873 ****
    rm -rf conftest*
    CPP="${CC-cc} -nologo -E"
    cat > conftest.$ac_ext <<EOF
! #line 865 "configure"
  #include "confdefs.h"
  #include <assert.h>
  Syntax Error
  EOF
  ac_try="$ac_cpp conftest.$ac_ext >/dev/null 2>conftest.out"
! { (eval echo configure:871: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; }
  ac_err=`grep -v '^ *+' conftest.out | grep -v "^conftest.${ac_ext}\$"`
  if test -z "$ac_err"; then
    :
--- 897,909 ----
    rm -rf conftest*
    CPP="${CC-cc} -nologo -E"
    cat > conftest.$ac_ext <<EOF
! #line 901 "configure"
  #include "confdefs.h"
  #include <assert.h>
  Syntax Error
  EOF
  ac_try="$ac_cpp conftest.$ac_ext >/dev/null 2>conftest.out"
! { (eval echo configure:907: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; }
  ac_err=`grep -v '^ *+' conftest.out | grep -v "^conftest.${ac_ext}\$"`
  if test -z "$ac_err"; then
    :
*************** fi
*** 892,903 ****
  echo "$ac_t""$CPP" 1>&6
  
  echo $ac_n "checking for ANSI C header files""... $ac_c" 1>&6
! echo "configure:896: checking for ANSI C header files" >&5
  if eval "test \"`echo '$''{'ac_cv_header_stdc'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 901 "configure"
  #include "confdefs.h"
  #include <stdlib.h>
  #include <stdarg.h>
--- 928,939 ----
  echo "$ac_t""$CPP" 1>&6
  
  echo $ac_n "checking for ANSI C header files""... $ac_c" 1>&6
! echo "configure:932: checking for ANSI C header files" >&5
  if eval "test \"`echo '$''{'ac_cv_header_stdc'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 937 "configure"
  #include "confdefs.h"
  #include <stdlib.h>
  #include <stdarg.h>
*************** else
*** 905,911 ****
  #include <float.h>
  EOF
  ac_try="$ac_cpp conftest.$ac_ext >/dev/null 2>conftest.out"
! { (eval echo configure:909: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; }
  ac_err=`grep -v '^ *+' conftest.out | grep -v "^conftest.${ac_ext}\$"`
  if test -z "$ac_err"; then
    rm -rf conftest*
--- 941,947 ----
  #include <float.h>
  EOF
  ac_try="$ac_cpp conftest.$ac_ext >/dev/null 2>conftest.out"
! { (eval echo configure:945: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; }
  ac_err=`grep -v '^ *+' conftest.out | grep -v "^conftest.${ac_ext}\$"`
  if test -z "$ac_err"; then
    rm -rf conftest*
*************** rm -f conftest*
*** 922,928 ****
  if test $ac_cv_header_stdc = yes; then
    # SunOS 4.x string.h does not declare mem*, contrary to ANSI.
  cat > conftest.$ac_ext <<EOF
! #line 926 "configure"
  #include "confdefs.h"
  #include <string.h>
  EOF
--- 958,964 ----
  if test $ac_cv_header_stdc = yes; then
    # SunOS 4.x string.h does not declare mem*, contrary to ANSI.
  cat > conftest.$ac_ext <<EOF
! #line 962 "configure"
  #include "confdefs.h"
  #include <string.h>
  EOF
*************** fi
*** 940,946 ****
  if test $ac_cv_header_stdc = yes; then
    # ISC 2.0.2 stdlib.h does not declare free, contrary to ANSI.
  cat > conftest.$ac_ext <<EOF
! #line 944 "configure"
  #include "confdefs.h"
  #include <stdlib.h>
  EOF
--- 976,982 ----
  if test $ac_cv_header_stdc = yes; then
    # ISC 2.0.2 stdlib.h does not declare free, contrary to ANSI.
  cat > conftest.$ac_ext <<EOF
! #line 980 "configure"
  #include "confdefs.h"
  #include <stdlib.h>
  EOF
*************** if test "$cross_compiling" = yes; then
*** 961,967 ****
    :
  else
    cat > conftest.$ac_ext <<EOF
! #line 965 "configure"
  #include "confdefs.h"
  #include <ctype.h>
  #define ISLOWER(c) ('a' <= (c) && (c) <= 'z')
--- 997,1003 ----
    :
  else
    cat > conftest.$ac_ext <<EOF
! #line 1001 "configure"
  #include "confdefs.h"
  #include <ctype.h>
  #define ISLOWER(c) ('a' <= (c) && (c) <= 'z')
*************** if (XOR (islower (i), ISLOWER (i)) || to
*** 972,978 ****
  exit (0); }
  
  EOF
! if { (eval echo configure:976: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest${ac_exeext} && (./conftest; exit) 2>/dev/null
  then
    :
  else
--- 1008,1014 ----
  exit (0); }
  
  EOF
! if { (eval echo configure:1012: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest${ac_exeext} && (./conftest; exit) 2>/dev/null
  then
    :
  else
*************** EOF
*** 995,1008 ****
  
  fi
  
- 
  echo $ac_n "checking whether time.h and sys/time.h may both be included""... $ac_c" 1>&6
! echo "configure:1001: checking whether time.h and sys/time.h may both be included" >&5
  if eval "test \"`echo '$''{'ac_cv_header_time'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 1006 "configure"
  #include "confdefs.h"
  #include <sys/types.h>
  #include <sys/time.h>
--- 1031,1043 ----
  
  fi
  
  echo $ac_n "checking whether time.h and sys/time.h may both be included""... $ac_c" 1>&6
! echo "configure:1036: checking whether time.h and sys/time.h may both be included" >&5
  if eval "test \"`echo '$''{'ac_cv_header_time'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 1041 "configure"
  #include "confdefs.h"
  #include <sys/types.h>
  #include <sys/time.h>
*************** int main() {
*** 1011,1017 ****
  struct tm *tp;
  ; return 0; }
  EOF
! if { (eval echo configure:1015: \"$ac_compile\") 1>&5; (eval $ac_compile) 2>&5; }; then
    rm -rf conftest*
    ac_cv_header_time=yes
  else
--- 1046,1052 ----
  struct tm *tp;
  ; return 0; }
  EOF
! if { (eval echo configure:1050: \"$ac_compile\") 1>&5; (eval $ac_compile) 2>&5; }; then
    rm -rf conftest*
    ac_cv_header_time=yes
  else
*************** for ac_hdr in limits.h unistd.h sys/time
*** 1036,1052 ****
  do
  ac_safe=`echo "$ac_hdr" | sed 'y%./+-%__p_%'`
  echo $ac_n "checking for $ac_hdr""... $ac_c" 1>&6
! echo "configure:1040: checking for $ac_hdr" >&5
  if eval "test \"`echo '$''{'ac_cv_header_$ac_safe'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 1045 "configure"
  #include "confdefs.h"
  #include <$ac_hdr>
  EOF
  ac_try="$ac_cpp conftest.$ac_ext >/dev/null 2>conftest.out"
! { (eval echo configure:1050: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; }
  ac_err=`grep -v '^ *+' conftest.out | grep -v "^conftest.${ac_ext}\$"`
  if test -z "$ac_err"; then
    rm -rf conftest*
--- 1071,1087 ----
  do
  ac_safe=`echo "$ac_hdr" | sed 'y%./+-%__p_%'`
  echo $ac_n "checking for $ac_hdr""... $ac_c" 1>&6
! echo "configure:1075: checking for $ac_hdr" >&5
  if eval "test \"`echo '$''{'ac_cv_header_$ac_safe'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 1080 "configure"
  #include "confdefs.h"
  #include <$ac_hdr>
  EOF
  ac_try="$ac_cpp conftest.$ac_ext >/dev/null 2>conftest.out"
! { (eval echo configure:1085: \"$ac_try\") 1>&5; (eval $ac_try) 2>&5; }
  ac_err=`grep -v '^ *+' conftest.out | grep -v "^conftest.${ac_ext}\$"`
  if test -z "$ac_err"; then
    rm -rf conftest*
*************** done
*** 1074,1085 ****
  
  
  echo $ac_n "checking for working const""... $ac_c" 1>&6
! echo "configure:1078: checking for working const" >&5
  if eval "test \"`echo '$''{'ac_cv_c_const'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 1083 "configure"
  #include "confdefs.h"
  
  int main() {
--- 1109,1120 ----
  
  
  echo $ac_n "checking for working const""... $ac_c" 1>&6
! echo "configure:1113: checking for working const" >&5
  if eval "test \"`echo '$''{'ac_cv_c_const'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 1118 "configure"
  #include "confdefs.h"
  
  int main() {
*************** ccp = (char const *const *) p;
*** 1128,1134 ****
  
  ; return 0; }
  EOF
! if { (eval echo configure:1132: \"$ac_compile\") 1>&5; (eval $ac_compile) 2>&5; }; then
    rm -rf conftest*
    ac_cv_c_const=yes
  else
--- 1163,1169 ----
  
  ; return 0; }
  EOF
! if { (eval echo configure:1167: \"$ac_compile\") 1>&5; (eval $ac_compile) 2>&5; }; then
    rm -rf conftest*
    ac_cv_c_const=yes
  else
*************** EOF
*** 1149,1160 ****
  fi
  
  echo $ac_n "checking for size_t""... $ac_c" 1>&6
! echo "configure:1153: checking for size_t" >&5
  if eval "test \"`echo '$''{'ac_cv_type_size_t'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 1158 "configure"
  #include "confdefs.h"
  #include <sys/types.h>
  #if STDC_HEADERS
--- 1184,1195 ----
  fi
  
  echo $ac_n "checking for size_t""... $ac_c" 1>&6
! echo "configure:1188: checking for size_t" >&5
  if eval "test \"`echo '$''{'ac_cv_type_size_t'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 1193 "configure"
  #include "confdefs.h"
  #include <sys/types.h>
  #if STDC_HEADERS
*************** EOF
*** 1182,1193 ****
  fi
  
  echo $ac_n "checking for mode_t""... $ac_c" 1>&6
! echo "configure:1186: checking for mode_t" >&5
  if eval "test \"`echo '$''{'ac_cv_type_mode_t'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 1191 "configure"
  #include "confdefs.h"
  #include <sys/types.h>
  #if STDC_HEADERS
--- 1217,1228 ----
  fi
  
  echo $ac_n "checking for mode_t""... $ac_c" 1>&6
! echo "configure:1221: checking for mode_t" >&5
  if eval "test \"`echo '$''{'ac_cv_type_mode_t'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 1226 "configure"
  #include "confdefs.h"
  #include <sys/types.h>
  #if STDC_HEADERS
*************** fi
*** 1216,1227 ****
  
  
  echo $ac_n "checking for pid_t""... $ac_c" 1>&6
! echo "configure:1220: checking for pid_t" >&5
  if eval "test \"`echo '$''{'ac_cv_type_pid_t'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 1225 "configure"
  #include "confdefs.h"
  #include <sys/types.h>
  #if STDC_HEADERS
--- 1251,1262 ----
  
  
  echo $ac_n "checking for pid_t""... $ac_c" 1>&6
! echo "configure:1255: checking for pid_t" >&5
  if eval "test \"`echo '$''{'ac_cv_type_pid_t'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 1260 "configure"
  #include "confdefs.h"
  #include <sys/types.h>
  #if STDC_HEADERS
*************** EOF
*** 1249,1260 ****
  fi
  
  echo $ac_n "checking for st_blksize in struct stat""... $ac_c" 1>&6
! echo "configure:1253: checking for st_blksize in struct stat" >&5
  if eval "test \"`echo '$''{'ac_cv_struct_st_blksize'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 1258 "configure"
  #include "confdefs.h"
  #include <sys/types.h>
  #include <sys/stat.h>
--- 1284,1295 ----
  fi
  
  echo $ac_n "checking for st_blksize in struct stat""... $ac_c" 1>&6
! echo "configure:1288: checking for st_blksize in struct stat" >&5
  if eval "test \"`echo '$''{'ac_cv_struct_st_blksize'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 1293 "configure"
  #include "confdefs.h"
  #include <sys/types.h>
  #include <sys/stat.h>
*************** int main() {
*** 1262,1268 ****
  struct stat s; s.st_blksize;
  ; return 0; }
  EOF
! if { (eval echo configure:1266: \"$ac_compile\") 1>&5; (eval $ac_compile) 2>&5; }; then
    rm -rf conftest*
    ac_cv_struct_st_blksize=yes
  else
--- 1297,1303 ----
  struct stat s; s.st_blksize;
  ; return 0; }
  EOF
! if { (eval echo configure:1301: \"$ac_compile\") 1>&5; (eval $ac_compile) 2>&5; }; then
    rm -rf conftest*
    ac_cv_struct_st_blksize=yes
  else
*************** EOF
*** 1283,1294 ****
  fi
  
  echo $ac_n "checking for st_blocks in struct stat""... $ac_c" 1>&6
! echo "configure:1287: checking for st_blocks in struct stat" >&5
  if eval "test \"`echo '$''{'ac_cv_struct_st_blocks'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 1292 "configure"
  #include "confdefs.h"
  #include <sys/types.h>
  #include <sys/stat.h>
--- 1318,1329 ----
  fi
  
  echo $ac_n "checking for st_blocks in struct stat""... $ac_c" 1>&6
! echo "configure:1322: checking for st_blocks in struct stat" >&5
  if eval "test \"`echo '$''{'ac_cv_struct_st_blocks'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 1327 "configure"
  #include "confdefs.h"
  #include <sys/types.h>
  #include <sys/stat.h>
*************** int main() {
*** 1296,1302 ****
  struct stat s; s.st_blocks;
  ; return 0; }
  EOF
! if { (eval echo configure:1300: \"$ac_compile\") 1>&5; (eval $ac_compile) 2>&5; }; then
    rm -rf conftest*
    ac_cv_struct_st_blocks=yes
  else
--- 1331,1337 ----
  struct stat s; s.st_blocks;
  ; return 0; }
  EOF
! if { (eval echo configure:1335: \"$ac_compile\") 1>&5; (eval $ac_compile) 2>&5; }; then
    rm -rf conftest*
    ac_cv_struct_st_blocks=yes
  else
*************** else
*** 1319,1330 ****
  fi
  
  echo $ac_n "checking for st_rdev in struct stat""... $ac_c" 1>&6
! echo "configure:1323: checking for st_rdev in struct stat" >&5
  if eval "test \"`echo '$''{'ac_cv_struct_st_rdev'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 1328 "configure"
  #include "confdefs.h"
  #include <sys/types.h>
  #include <sys/stat.h>
--- 1354,1365 ----
  fi
  
  echo $ac_n "checking for st_rdev in struct stat""... $ac_c" 1>&6
! echo "configure:1358: checking for st_rdev in struct stat" >&5
  if eval "test \"`echo '$''{'ac_cv_struct_st_rdev'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 1363 "configure"
  #include "confdefs.h"
  #include <sys/types.h>
  #include <sys/stat.h>
*************** int main() {
*** 1332,1338 ****
  struct stat s; s.st_rdev;
  ; return 0; }
  EOF
! if { (eval echo configure:1336: \"$ac_compile\") 1>&5; (eval $ac_compile) 2>&5; }; then
    rm -rf conftest*
    ac_cv_struct_st_rdev=yes
  else
--- 1367,1373 ----
  struct stat s; s.st_rdev;
  ; return 0; }
  EOF
! if { (eval echo configure:1371: \"$ac_compile\") 1>&5; (eval $ac_compile) 2>&5; }; then
    rm -rf conftest*
    ac_cv_struct_st_rdev=yes
  else
*************** EOF
*** 1353,1364 ****
  fi
  
  echo $ac_n "checking whether struct tm is in sys/time.h or time.h""... $ac_c" 1>&6
! echo "configure:1357: checking whether struct tm is in sys/time.h or time.h" >&5
  if eval "test \"`echo '$''{'ac_cv_struct_tm'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 1362 "configure"
  #include "confdefs.h"
  #include <sys/types.h>
  #include <time.h>
--- 1388,1399 ----
  fi
  
  echo $ac_n "checking whether struct tm is in sys/time.h or time.h""... $ac_c" 1>&6
! echo "configure:1392: checking whether struct tm is in sys/time.h or time.h" >&5
  if eval "test \"`echo '$''{'ac_cv_struct_tm'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 1397 "configure"
  #include "confdefs.h"
  #include <sys/types.h>
  #include <time.h>
*************** int main() {
*** 1366,1372 ****
  struct tm *tp; tp->tm_sec;
  ; return 0; }
  EOF
! if { (eval echo configure:1370: \"$ac_compile\") 1>&5; (eval $ac_compile) 2>&5; }; then
    rm -rf conftest*
    ac_cv_struct_tm=time.h
  else
--- 1401,1407 ----
  struct tm *tp; tp->tm_sec;
  ; return 0; }
  EOF
! if { (eval echo configure:1405: \"$ac_compile\") 1>&5; (eval $ac_compile) 2>&5; }; then
    rm -rf conftest*
    ac_cv_struct_tm=time.h
  else
*************** fi
*** 1388,1394 ****
  
  
  echo $ac_n "checking for gethostname in -lsocket""... $ac_c" 1>&6
! echo "configure:1392: checking for gethostname in -lsocket" >&5
  ac_lib_var=`echo socket'_'gethostname | sed 'y%./+-%__p_%'`
  if eval "test \"`echo '$''{'ac_cv_lib_$ac_lib_var'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
--- 1423,1429 ----
  
  
  echo $ac_n "checking for gethostname in -lsocket""... $ac_c" 1>&6
! echo "configure:1427: checking for gethostname in -lsocket" >&5
  ac_lib_var=`echo socket'_'gethostname | sed 'y%./+-%__p_%'`
  if eval "test \"`echo '$''{'ac_cv_lib_$ac_lib_var'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
*************** else
*** 1396,1402 ****
    ac_save_LIBS="$LIBS"
  LIBS="-lsocket  $LIBS"
  cat > conftest.$ac_ext <<EOF
! #line 1400 "configure"
  #include "confdefs.h"
  /* Override any gcc2 internal prototype to avoid an error.  */
  /* We use char because int might match the return type of a gcc2
--- 1431,1437 ----
    ac_save_LIBS="$LIBS"
  LIBS="-lsocket  $LIBS"
  cat > conftest.$ac_ext <<EOF
! #line 1435 "configure"
  #include "confdefs.h"
  /* Override any gcc2 internal prototype to avoid an error.  */
  /* We use char because int might match the return type of a gcc2
*************** int main() {
*** 1407,1413 ****
  gethostname()
  ; return 0; }
  EOF
! if { (eval echo configure:1411: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest${ac_exeext}; then
    rm -rf conftest*
    eval "ac_cv_lib_$ac_lib_var=yes"
  else
--- 1442,1448 ----
  gethostname()
  ; return 0; }
  EOF
! if { (eval echo configure:1446: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest${ac_exeext}; then
    rm -rf conftest*
    eval "ac_cv_lib_$ac_lib_var=yes"
  else
*************** for ac_func in symlink getcwd getwd lsta
*** 1433,1444 ****
    getrusage times alarm getlogin getgid getuid kill link ttyname
  do
  echo $ac_n "checking for $ac_func""... $ac_c" 1>&6
! echo "configure:1437: checking for $ac_func" >&5
  if eval "test \"`echo '$''{'ac_cv_func_$ac_func'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 1442 "configure"
  #include "confdefs.h"
  /* System header to define __stub macros and hopefully few prototypes,
      which can conflict with char $ac_func(); below.  */
--- 1468,1479 ----
    getrusage times alarm getlogin getgid getuid kill link ttyname
  do
  echo $ac_n "checking for $ac_func""... $ac_c" 1>&6
! echo "configure:1472: checking for $ac_func" >&5
  if eval "test \"`echo '$''{'ac_cv_func_$ac_func'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 1477 "configure"
  #include "confdefs.h"
  /* System header to define __stub macros and hopefully few prototypes,
      which can conflict with char $ac_func(); below.  */
*************** $ac_func();
*** 1461,1467 ****
  
  ; return 0; }
  EOF
! if { (eval echo configure:1465: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest${ac_exeext}; then
    rm -rf conftest*
    eval "ac_cv_func_$ac_func=yes"
  else
--- 1496,1502 ----
  
  ; return 0; }
  EOF
! if { (eval echo configure:1500: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest${ac_exeext}; then
    rm -rf conftest*
    eval "ac_cv_func_$ac_func=yes"
  else
*************** done
*** 1490,1501 ****
    for ac_func in gettimeofday
  do
  echo $ac_n "checking for $ac_func""... $ac_c" 1>&6
! echo "configure:1494: checking for $ac_func" >&5
  if eval "test \"`echo '$''{'ac_cv_func_$ac_func'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 1499 "configure"
  #include "confdefs.h"
  /* System header to define __stub macros and hopefully few prototypes,
      which can conflict with char $ac_func(); below.  */
--- 1525,1536 ----
    for ac_func in gettimeofday
  do
  echo $ac_n "checking for $ac_func""... $ac_c" 1>&6
! echo "configure:1529: checking for $ac_func" >&5
  if eval "test \"`echo '$''{'ac_cv_func_$ac_func'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 1534 "configure"
  #include "confdefs.h"
  /* System header to define __stub macros and hopefully few prototypes,
      which can conflict with char $ac_func(); below.  */
*************** $ac_func();
*** 1518,1524 ****
  
  ; return 0; }
  EOF
! if { (eval echo configure:1522: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest${ac_exeext}; then
    rm -rf conftest*
    eval "ac_cv_func_$ac_func=yes"
  else
--- 1553,1559 ----
  
  ; return 0; }
  EOF
! if { (eval echo configure:1557: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest${ac_exeext}; then
    rm -rf conftest*
    eval "ac_cv_func_$ac_func=yes"
  else
*************** done
*** 1544,1562 ****
  
    if test "$ac_cv_func_gettimeofday" = yes; then
      echo $ac_n "checking for struct timezone""... $ac_c" 1>&6
! echo "configure:1548: checking for struct timezone" >&5
  if eval "test \"`echo '$''{'g77_cv_struct_timezone'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 1553 "configure"
  #include "confdefs.h"
  #include <sys/time.h>
  int main() {
  struct timezone tz;
  ; return 0; }
  EOF
! if { (eval echo configure:1560: \"$ac_compile\") 1>&5; (eval $ac_compile) 2>&5; }; then
    rm -rf conftest*
    g77_cv_struct_timezone=yes
  else
--- 1579,1597 ----
  
    if test "$ac_cv_func_gettimeofday" = yes; then
      echo $ac_n "checking for struct timezone""... $ac_c" 1>&6
! echo "configure:1583: checking for struct timezone" >&5
  if eval "test \"`echo '$''{'g77_cv_struct_timezone'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 1588 "configure"
  #include "confdefs.h"
  #include <sys/time.h>
  int main() {
  struct timezone tz;
  ; return 0; }
  EOF
! if { (eval echo configure:1595: \"$ac_compile\") 1>&5; (eval $ac_compile) 2>&5; }; then
    rm -rf conftest*
    g77_cv_struct_timezone=yes
  else
*************** EOF
*** 1577,1583 ****
  
  else
    cat > conftest.$ac_ext <<EOF
! #line 1581 "configure"
  #include "confdefs.h"
  
  #ifdef TIME_WITH_SYS_TIME
--- 1612,1618 ----
  
  else
    cat > conftest.$ac_ext <<EOF
! #line 1616 "configure"
  #include "confdefs.h"
  
  #ifdef TIME_WITH_SYS_TIME
*************** main ()
*** 1600,1606 ****
      exit (0);
  }
  EOF
! if { (eval echo configure:1604: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest${ac_exeext} && (./conftest; exit) 2>/dev/null
  then
    cat >> confdefs.h <<\EOF
  #define HAVE_TIMEZONE 1
--- 1635,1641 ----
      exit (0);
  }
  EOF
! if { (eval echo configure:1639: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest${ac_exeext} && (./conftest; exit) 2>/dev/null
  then
    cat >> confdefs.h <<\EOF
  #define HAVE_TIMEZONE 1
*************** fi
*** 1616,1627 ****
      fi
      
      echo $ac_n "checking whether gettimeofday can accept two arguments""... $ac_c" 1>&6
! echo "configure:1620: checking whether gettimeofday can accept two arguments" >&5
  if eval "test \"`echo '$''{'emacs_cv_gettimeofday_two_arguments'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 1625 "configure"
  #include "confdefs.h"
  
  #ifdef TIME_WITH_SYS_TIME
--- 1651,1662 ----
      fi
      
      echo $ac_n "checking whether gettimeofday can accept two arguments""... $ac_c" 1>&6
! echo "configure:1655: checking whether gettimeofday can accept two arguments" >&5
  if eval "test \"`echo '$''{'emacs_cv_gettimeofday_two_arguments'+set}'`\" = set"; then
    echo $ac_n "(cached) $ac_c" 1>&6
  else
    cat > conftest.$ac_ext <<EOF
! #line 1660 "configure"
  #include "confdefs.h"
  
  #ifdef TIME_WITH_SYS_TIME
*************** int main() {
*** 1647,1653 ****
        gettimeofday (&time, DUMMY);
  ; return 0; }
  EOF
! if { (eval echo configure:1651: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest${ac_exeext}; then
    rm -rf conftest*
    emacs_cv_gettimeofday_two_arguments=yes
  else
--- 1682,1688 ----
        gettimeofday (&time, DUMMY);
  ; return 0; }
  EOF
! if { (eval echo configure:1686: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest${ac_exeext}; then
    rm -rf conftest*
    emacs_cv_gettimeofday_two_arguments=yes
  else
diff -Nrc3pad gcc-3.2.3/libf2c/libU77/configure.in gcc-3.3/libf2c/libU77/configure.in
*** gcc-3.2.3/libf2c/libU77/configure.in	2001-09-30 22:06:23.000000000 +0000
--- gcc-3.3/libf2c/libU77/configure.in	2003-04-24 01:58:04.000000000 +0000
*************** AC_PREREQ(2.12.1)
*** 23,39 ****
  AC_INIT(access_.c)
  AC_CONFIG_HEADER(config.h:config.hin)
  
- # These defines are necessary to get 64-bit file size support.
- 
- AC_DEFINE(_XOPEN_SOURCE, 500L, [Get Single Unix Specification semantics])
- # The following is needed by irix6.2 so that struct timeval is declared.
- AC_DEFINE(_XOPEN_SOURCE_EXTENDED, 1, [Get Single Unix Specification semantics])
- # The following is needed by Solaris2.5.1 so that struct timeval is declared.
- AC_DEFINE(__EXTENSIONS__, 1, [Solaris extensions])
- AC_DEFINE(_FILE_OFFSET_BITS, 64, [Get 64-bit file size support])
- 
- dnl Checks for programs.
- 
  dnl FIXME AC_PROG_CC wants CC to be able to link things, but it may
  dnl not be able to.
  define([AC_PROG_CC_WORKS],[])
--- 23,28 ----
*************** define([AC_PROG_CC_WORKS],[])
*** 42,47 ****
--- 31,56 ----
  # the makefiles
  AC_PROG_CC
  
+ # These defines are necessary to get 64-bit file size support.
+ # NetBSD 1.4 header files does not support XOPEN_SOURCE == 600, but it
+ # handles 64-bit file sizes without needing these defines.
+ AC_MSG_CHECKING(whether _XOPEN_SOURCE may be defined)
+ AC_TRY_COMPILE([#define _XOPEN_SOURCE 600L
+ #include <unistd.h>],,
+ may_use_xopen_source=yes,
+ may_use_xopen_source=no)
+ AC_MSG_RESULT($may_use_xopen_source)
+ if test $may_use_xopen_source = yes; then
+   AC_DEFINE(_XOPEN_SOURCE, 600L, [Get Single Unix Specification semantics])
+   # The following is needed by irix6.2 so that struct timeval is declared.
+   AC_DEFINE(_XOPEN_SOURCE_EXTENDED, 1, [Get Single Unix Specification semantics])
+   # The following is needed by Solaris2.5.1 so that struct timeval is declared.
+   AC_DEFINE(__EXTENSIONS__, 1, [Solaris extensions])
+   AC_DEFINE(_FILE_OFFSET_BITS, 64, [Get 64-bit file size support])
+ fi
+ 
+ dnl Checks for programs.
+ 
  LIBTOOL='$(SHELL) ../libtool'
  AC_SUBST(LIBTOOL)
  
*************** fi
*** 70,86 ****
  
  dnl Checks for header files.
  AC_HEADER_STDC
- dnl We could do this if we didn't know we were using gcc
- dnl AC_MSG_CHECKING(for prototype-savvy compiler)
- dnl AC_CACHE_VAL(ac_cv_sys_proto,                
- dnl   [AC_TRY_LINK(,                             
- dnl dnl looks screwy because TRY_LINK expects a function body
- dnl    [return 0;} int foo (int * bar) {],       
- dnl    ac_cv_sys_proto=yes,                      
- dnl    [ac_cv_sys_proto=no                       
- dnl     AC_DEFINE(KR_headers)])])                
- dnl AC_MSG_RESULT($ac_cv_sys_proto)              
- 
  AC_HEADER_TIME
  AC_CHECK_HEADERS(limits.h unistd.h sys/time.h string.h stdlib.h \
    sys/param.h sys/times.h)
--- 79,84 ----
diff -Nrc3pad gcc-3.2.3/libf2c/libU77/ctime_.c gcc-3.3/libf2c/libU77/ctime_.c
*** gcc-3.2.3/libf2c/libU77/ctime_.c	2001-01-23 23:20:29.000000000 +0000
--- gcc-3.3/libf2c/libU77/ctime_.c	2002-06-02 12:59:22.000000000 +0000
*************** Boston, MA 02111-1307, USA.  */
*** 39,54 ****
  
  /* may need sys/time.h & long arg for stime (bsd, svr1-3) */
  
! #ifdef KR_headers
! /* Character */ void G77_ctime_0 (chtime, Lchtime, xstime)
!      char *chtime;
!      longint * xstime;
!      ftnlen Lchtime;
! #else
! /* Character */ void G77_ctime_0 (char *chtime, const ftnlen Lchtime, longint * xstime)
! #endif
  {
-   int i, l;
    int s_copy ();
    time_t stime = *xstime;
  
--- 39,47 ----
  
  /* may need sys/time.h & long arg for stime (bsd, svr1-3) */
  
! /* Character */ void
! G77_ctime_0 (char *chtime, const ftnlen Lchtime, longint * xstime)
  {
    int s_copy ();
    time_t stime = *xstime;
  
diff -Nrc3pad gcc-3.2.3/libf2c/libU77/date_.c gcc-3.3/libf2c/libU77/date_.c
*** gcc-3.2.3/libf2c/libU77/date_.c	2001-09-30 22:06:23.000000000 +0000
--- gcc-3.3/libf2c/libU77/date_.c	2002-06-05 19:07:10.000000000 +0000
***************
*** 9,55 ****
  
  static integer c__5 = 5;
  
! /* Subroutine */ int G77_date_y2kbug_0 (char *buf, ftnlen buf_len)
  {
!     /* System generated locals */
!     address a__1[5];
!     longint i__1;
!     integer i__2[5];
!     char ch__1[24];
  
!     /* Builtin functions */
!     /* Subroutine */ int s_copy(), s_cat();
  
!     /* Local variables */
!     static char cbuf[24];
!     extern longint G77_time_0 ();
!     extern /* Character */ VOID G77_ctime_0 ();
  
!     i__1 = G77_time_0 ();
!     G77_ctime_0 (ch__1, 24L, &i__1);
!     s_copy(cbuf, ch__1, 24L, 24L);
  /* Writing concatenation */
!     i__2[0] = 2, a__1[0] = cbuf + 8;
!     i__2[1] = 1, a__1[1] = "-";
!     i__2[2] = 3, a__1[2] = cbuf + 4;
!     i__2[3] = 1, a__1[3] = "-";
!     i__2[4] = 2, a__1[4] = cbuf + 22;
!     s_cat(buf, a__1, i__2, &c__5, buf_len);
!     return 0;
! } /* date_ */
  
  #ifdef PIC
  #  include <stdio.h>
  
  const char *G77_Non_Y2K_Compliance_Message =
!    "Call to non Y2K compliant subroutine detected.";
  
! int G77_date_y2kbuggy_0 (char *buf, ftnlen buf_len)
  {
!   extern int G77_abort_0();
    fprintf (stderr, "%s\n", G77_Non_Y2K_Compliance_Message);
!   G77_abort_0();
  }
  #endif
- 
- 
--- 9,56 ----
  
  static integer c__5 = 5;
  
! /* Subroutine */ int
! G77_date_y2kbug_0 (char *buf, ftnlen buf_len)
  {
!   /* System generated locals */
!   address a__1[5];
!   longint i__1;
!   integer i__2[5];
!   char ch__1[24];
  
!   /* Builtin functions */
!   /* Subroutine */ int s_copy (), s_cat ();
  
!   /* Local variables */
!   static char cbuf[24];
!   extern longint G77_time_0 ();
!   extern /* Character */ void G77_ctime_0 ();
  
!   i__1 = G77_time_0 ();
!   G77_ctime_0 (ch__1, 24L, &i__1);
!   s_copy (cbuf, ch__1, 24L, 24L);
  /* Writing concatenation */
!   i__2[0] = 2, a__1[0] = cbuf + 8;
!   i__2[1] = 1, a__1[1] = "-";
!   i__2[2] = 3, a__1[2] = cbuf + 4;
!   i__2[3] = 1, a__1[3] = "-";
!   i__2[4] = 2, a__1[4] = cbuf + 22;
!   s_cat (buf, a__1, i__2, &c__5, buf_len);
!   return 0;
! }				/* date_ */
  
  #ifdef PIC
  #  include <stdio.h>
  
  const char *G77_Non_Y2K_Compliance_Message =
!   "Call to non Y2K compliant subroutine detected.";
  
! int
! G77_date_y2kbuggy_0 (char *buf __attribute__ ((__unused__)),
! 		     ftnlen buf_len __attribute__ ((__unused__)))
  {
!   extern int G77_abort_0 ();
    fprintf (stderr, "%s\n", G77_Non_Y2K_Compliance_Message);
!   G77_abort_0 ();
  }
  #endif
diff -Nrc3pad gcc-3.2.3/libf2c/libU77/datetime_.c gcc-3.3/libf2c/libU77/datetime_.c
*** gcc-3.2.3/libf2c/libU77/datetime_.c	2001-01-23 23:20:30.000000000 +0000
--- gcc-3.3/libf2c/libU77/datetime_.c	2002-09-14 12:50:40.000000000 +0000
*************** Boston, MA 02111-1307, USA.  */
*** 31,70 ****
  #  include <time.h>
  # endif
  #endif
  #include "f2c.h"
  
! #ifdef KR_headers
! VOID s_copy ();
! #else
! void s_copy(register char *a, register char *b, ftnlen la, ftnlen lb);
! #endif
  
! int G77_date_and_time_0 (char *date, char *fftime, char *zone,
! 			 integer *values, ftnlen date_len,
! 			 ftnlen fftime_len, ftnlen zone_len)
  {
!   time_t lt=time(&lt);
!   struct tm ltime = *localtime(&lt), gtime = *gmtime(&lt);
    char dat[9], zon[6], ftim[11];
    int i, vals[8];
  
    vals[0] = 1900 + ltime.tm_year;
    vals[1] = 1 + ltime.tm_mon;
    vals[2] = ltime.tm_mday;
    /* fixme: year boundaries */
    vals[3] = (ltime.tm_min - gtime.tm_min +
! 	     60*(ltime.tm_hour - gtime.tm_hour +
! 		 24*(ltime.tm_yday -gtime.tm_yday)));
    vals[4] = ltime.tm_hour;
    vals[5] = ltime.tm_min;
    vals[6] = ltime.tm_sec;
-   vals[7] = 0;                  /* no STDC/POSIX way to get this */
-   /* GNUish way; maybe use `ftime' on other systems. */
  #if HAVE_GETTIMEOFDAY
    {
      struct timeval tp;
  #  if GETTIMEOFDAY_ONE_ARGUMENT
!     if (! gettimeofday (&tp))
  #  else
  #    if HAVE_STRUCT_TIMEZONE
      struct timezone tzp;
--- 31,78 ----
  #  include <time.h>
  # endif
  #endif
+ #if defined (_WIN32)
+ #include <windows.h>
+ #undef min
+ #undef max
+ #endif
  #include "f2c.h"
  
! void s_copy (register char *a, register char *b, ftnlen la, ftnlen lb);
  
! int
! G77_date_and_time_0 (char *date, char *fftime, char *zone,
! 		     integer * values, ftnlen date_len,
! 		     ftnlen fftime_len, ftnlen zone_len)
  {
!   time_t lt = time (&lt);
!   struct tm ltime = *localtime (&lt), gtime = *gmtime (&lt);
    char dat[9], zon[6], ftim[11];
    int i, vals[8];
+ #if defined (_WIN32)
+     struct _SYSTEMTIME wdattim;
+     GetLocalTime(&wdattim);
+     vals[7] = wdattim.wMilliseconds;
+ #else
+   vals[7] = 0;                  /* no STDC/POSIX way to get this */
+   /* GNUish way; maybe use `ftime' on other systems. */
+ #endif
  
    vals[0] = 1900 + ltime.tm_year;
    vals[1] = 1 + ltime.tm_mon;
    vals[2] = ltime.tm_mday;
    /* fixme: year boundaries */
    vals[3] = (ltime.tm_min - gtime.tm_min +
! 	     60 * (ltime.tm_hour - gtime.tm_hour +
! 		   24 * (ltime.tm_yday - gtime.tm_yday)));
    vals[4] = ltime.tm_hour;
    vals[5] = ltime.tm_min;
    vals[6] = ltime.tm_sec;
  #if HAVE_GETTIMEOFDAY
    {
      struct timeval tp;
  #  if GETTIMEOFDAY_ONE_ARGUMENT
!     if (!gettimeofday (&tp))
  #  else
  #    if HAVE_STRUCT_TIMEZONE
      struct timezone tzp;
*************** int G77_date_and_time_0 (char *date, cha
*** 74,99 ****
         HPUX.  Configure checks if gettimeofday actually fails with a
         non-NULL arg and pretends that struct timezone is missing if it
         does fail.  */
!     if (! gettimeofday (&tp, &tzp))
  #    else
!     if (! gettimeofday (&tp, (void *) 0))
  #    endif /* HAVE_STRUCT_TIMEZONE */
  #  endif /* GETTIMEOFDAY_ONE_ARGUMENT */
!       vals[7] = tp.tv_usec/1000;
    }
  #endif /* HAVE_GETTIMEOFDAY */
    if (values)			/* null pointer for missing optional */
!     for (i=0; i<=7; i++)
        values[i] = vals[i];
    sprintf (dat, "%04d%02d%02d", vals[0], vals[1], vals[2]);
!   s_copy(date, dat, date_len, 8);
!   if (zone) {
!     sprintf(zon, "%+03d%02d", vals[3] / 60, abs(vals[3] % 60));
!     s_copy(zone, zon, zone_len, 5);
!   }
!   if (fftime) {
!     sprintf (ftim, "%02d%02d%02d.%03d", vals[4], vals[5], vals[6], vals[7]);
!     s_copy(fftime, ftim, fftime_len, 10);
!   }
    return 0;
  }
--- 82,109 ----
         HPUX.  Configure checks if gettimeofday actually fails with a
         non-NULL arg and pretends that struct timezone is missing if it
         does fail.  */
!     if (!gettimeofday (&tp, &tzp))
  #    else
!     if (!gettimeofday (&tp, (void *) 0))
  #    endif /* HAVE_STRUCT_TIMEZONE */
  #  endif /* GETTIMEOFDAY_ONE_ARGUMENT */
!       vals[7] = tp.tv_usec / 1000;
    }
  #endif /* HAVE_GETTIMEOFDAY */
    if (values)			/* null pointer for missing optional */
!     for (i = 0; i <= 7; i++)
        values[i] = vals[i];
    sprintf (dat, "%04d%02d%02d", vals[0], vals[1], vals[2]);
!   s_copy (date, dat, date_len, 8);
!   if (zone)
!     {
!       sprintf (zon, "%+03d%02d", vals[3] / 60, abs (vals[3] % 60));
!       s_copy (zone, zon, zone_len, 5);
!     }
!   if (fftime)
!     {
!       sprintf (ftim, "%02d%02d%02d.%03d", vals[4], vals[5], vals[6], vals[7]);
!       s_copy (fftime, ftim, fftime_len, 10);
!     }
    return 0;
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libU77/dbes.c gcc-3.3/libf2c/libU77/dbes.c
*** gcc-3.2.3/libf2c/libU77/dbes.c	1998-05-19 11:01:52.000000000 +0000
--- gcc-3.3/libf2c/libU77/dbes.c	2002-06-01 12:38:32.000000000 +0000
*************** License along with GNU Fortran; see the 
*** 16,46 ****
  not, write to the Free Software Foundation, Inc., 59 Temple Place - Suite 330,
  Boston, MA 02111-1307, USA.  */
  
! #if 0 	/* Don't include these unless necessary -- dnp. */
  #include "f2c.h"
  #include <math.h>
  
! double G77_dbesj0_0 (const double *x) {
!     return j0 (*x);
  }
  
! double G77_dbesj1_0 (const double *x) {
!     return j1 (*x);
  }
  
! double G77_dbesjn_0 (const integer *n, double *x) {
!      return jn (*n, *x);
!  }
  
! double G77_dbesy0_0 (const double *x) {
!     return y0 (*x);
  }
  
! double G77_dbesy1_0 (const double *x) {
!     return y1 (*x);
  }
  
! double G77_dbesyn_0 (const integer *n, double *x) {
!     return yn (*n, *x);
  }
  #endif
--- 16,58 ----
  not, write to the Free Software Foundation, Inc., 59 Temple Place - Suite 330,
  Boston, MA 02111-1307, USA.  */
  
! #if 0				/* Don't include these unless necessary -- dnp. */
  #include "f2c.h"
  #include <math.h>
  
! double
! G77_dbesj0_0 (const double *x)
! {
!   return j0 (*x);
  }
  
! double
! G77_dbesj1_0 (const double *x)
! {
!   return j1 (*x);
  }
  
! double
! G77_dbesjn_0 (const integer * n, double *x)
! {
!   return jn (*n, *x);
! }
  
! double
! G77_dbesy0_0 (const double *x)
! {
!   return y0 (*x);
  }
  
! double
! G77_dbesy1_0 (const double *x)
! {
!   return y1 (*x);
  }
  
! double
! G77_dbesyn_0 (const integer * n, double *x)
! {
!   return yn (*n, *x);
  }
  #endif
diff -Nrc3pad gcc-3.2.3/libf2c/libU77/dtime_.c gcc-3.3/libf2c/libU77/dtime_.c
*** gcc-3.2.3/libf2c/libU77/dtime_.c	2000-06-21 20:13:23.000000000 +0000
--- gcc-3.3/libf2c/libU77/dtime_.c	2002-06-04 02:25:48.000000000 +0000
*************** Boston, MA 02111-1307, USA.  */
*** 44,62 ****
  #include <errno.h>		/* for ENOSYS */
  #include "f2c.h"
  
! /* For dtime, etime we store the clock tick parameter (clk_tck) the
!    first time either of them is invoked rather than each time.  This
!    approach probably speeds up each invocation by avoiding a system
!    call each time, but means that the overhead of the first call is
!    different to all others. */
! static long clk_tck = 0;
! 
! #ifdef KR_headers
! double G77_dtime_0 (tarray)
!      real tarray[2];
! #else
! double G77_dtime_0 (real tarray[2])
! #endif
  {
  #if defined (_WIN32)
    static int win32_platform = -1;
--- 44,51 ----
  #include <errno.h>		/* for ENOSYS */
  #include "f2c.h"
  
! double
! G77_dtime_0 (real tarray[2])
  {
  #if defined (_WIN32)
    static int win32_platform = -1;
*************** double G77_dtime_0 (real tarray[2])
*** 68,74 ****
        GetVersionEx (&osv);
        win32_platform = osv.dwPlatformId;
      }
!   
    /* We need to use this hack on non-NT platforms, where the first call
       returns 0.0 and subsequent ones return the correct value. */
    if (win32_platform != VER_PLATFORM_WIN32_NT)
--- 57,63 ----
        GetVersionEx (&osv);
        win32_platform = osv.dwPlatformId;
      }
! 
    /* We need to use this hack on non-NT platforms, where the first call
       returns 0.0 and subsequent ones return the correct value. */
    if (win32_platform != VER_PLATFORM_WIN32_NT)
*************** double G77_dtime_0 (real tarray[2])
*** 82,88 ****
        if (clock_freq == 0)
  	{
  	  LARGE_INTEGER freq;
! 	  if (! QueryPerformanceFrequency (&freq))
  	    {
  	      errno = ENOSYS;
  	      return 0.0;
--- 71,77 ----
        if (clock_freq == 0)
  	{
  	  LARGE_INTEGER freq;
! 	  if (!QueryPerformanceFrequency (&freq))
  	    {
  	      errno = ENOSYS;
  	      return 0.0;
*************** double G77_dtime_0 (real tarray[2])
*** 90,104 ****
  	  else
  	    {
  	      clock_freq = ((unsigned long long) freq.HighPart << 32)
!                            + ((unsigned) freq.LowPart);
  	    }
  	}
  
!       if (! QueryPerformanceCounter (&counter_val))
  	return -1.0;
  
        count = ((unsigned long long) counter_val.HighPart << 32)
!               + (unsigned) counter_val.LowPart;
        delta = ((double) (count - old_count)) / clock_freq;
        tarray[0] = (float) delta;
        tarray[1] = 0.0;
--- 79,93 ----
  	  else
  	    {
  	      clock_freq = ((unsigned long long) freq.HighPart << 32)
! 		+ ((unsigned) freq.LowPart);
  	    }
  	}
  
!       if (!QueryPerformanceCounter (&counter_val))
  	return -1.0;
  
        count = ((unsigned long long) counter_val.HighPart << 32)
! 	+ (unsigned) counter_val.LowPart;
        delta = ((double) (count - old_count)) / clock_freq;
        tarray[0] = (float) delta;
        tarray[1] = 0.0;
*************** double G77_dtime_0 (real tarray[2])
*** 112,121 ****
  
        GetProcessTimes (GetCurrentProcess (), &creation_time, &exit_time,
  		       &kernel_time, &user_time);
!       utime = ((unsigned long long) user_time.dwHighDateTime << 32) 
! 	      + (unsigned) user_time.dwLowDateTime;
!       stime = ((unsigned long long) kernel_time.dwHighDateTime << 32) 
! 	      + (unsigned) kernel_time.dwLowDateTime;
  
        tarray[0] = (utime - old_utime) / 1.0e7;
        tarray[1] = (stime - old_stime) / 1.0e7;
--- 101,110 ----
  
        GetProcessTimes (GetCurrentProcess (), &creation_time, &exit_time,
  		       &kernel_time, &user_time);
!       utime = ((unsigned long long) user_time.dwHighDateTime << 32)
! 	+ (unsigned) user_time.dwLowDateTime;
!       stime = ((unsigned long long) kernel_time.dwHighDateTime << 32)
! 	+ (unsigned) kernel_time.dwLowDateTime;
  
        tarray[0] = (utime - old_utime) / 1.0e7;
        tarray[1] = (stime - old_stime) / 1.0e7;
*************** double G77_dtime_0 (real tarray[2])
*** 131,145 ****
    static float old_utime = 0.0, old_stime = 0.0;
    struct rusage rbuff;
  
!    if (getrusage (RUSAGE_SELF, &rbuff) != 0)
!      abort ();
!    utime = (float) (rbuff.ru_utime).tv_sec +
! 	   (float) (rbuff.ru_utime).tv_usec/1000000.0;
!    tarray[0] = utime - (float) old_utime;
!    stime = (float) (rbuff.ru_stime).tv_sec +
! 	   (float) (rbuff.ru_stime).tv_usec/1000000.0;
    tarray[1] = stime - old_stime;
! #else  /* HAVE_GETRUSAGE */
    time_t utime, stime;
    static time_t old_utime = 0, old_stime = 0;
    struct tms buffer;
--- 120,140 ----
    static float old_utime = 0.0, old_stime = 0.0;
    struct rusage rbuff;
  
!   if (getrusage (RUSAGE_SELF, &rbuff) != 0)
!     abort ();
!   utime = (float) (rbuff.ru_utime).tv_sec +
!     (float) (rbuff.ru_utime).tv_usec / 1000000.0;
!   tarray[0] = utime - (float) old_utime;
!   stime = (float) (rbuff.ru_stime).tv_sec +
!     (float) (rbuff.ru_stime).tv_usec / 1000000.0;
    tarray[1] = stime - old_stime;
! #else /* HAVE_GETRUSAGE */
!   /* For dtime, etime we store the clock tick parameter (clk_tck) the
!      first time either of them is invoked rather than each time.  This
!      approach probably speeds up each invocation by avoiding a system
!      call each time, but means that the overhead of the first call is
!      different to all others. */
!   static long clk_tck = 0;
    time_t utime, stime;
    static time_t old_utime = 0, old_stime = 0;
    struct tms buffer;
*************** double G77_dtime_0 (real tarray[2])
*** 147,170 ****
  /* NeXTStep seems to define _SC_CLK_TCK but not to have sysconf;
     fixme: does using _POSIX_VERSION help? */
  #  if defined _SC_CLK_TCK && defined _POSIX_VERSION
!   if (! clk_tck) clk_tck = sysconf(_SC_CLK_TCK);
  #  elif defined CLOCKS_PER_SECOND
!   if (! clk_tck) clk_tck = CLOCKS_PER_SECOND;
  #  elif defined CLK_TCK
!   if (! clk_tck) clk_tck = CLK_TCK;
  #  elif defined HZ
!   if (! clk_tck) clk_tck = HZ;
  #  elif defined HAVE_GETRUSAGE
  #  else
!   #error Dont know clock tick length
  #  endif
!   if (times(&buffer) == (clock_t)-1) return -1.0;
!   utime = buffer.tms_utime; stime = buffer.tms_stime;
!   tarray[0] = ((float)(utime - old_utime)) / (float)clk_tck;
!   tarray[1] = ((float)(stime - old_stime)) / (float)clk_tck;
  #endif /* HAVE_GETRUSAGE */
!   old_utime = utime; old_stime = stime;
!   return (tarray[0]+tarray[1]);
  #else /* ! HAVE_GETRUSAGE && ! HAVE_TIMES */
    errno = ENOSYS;
    return 0.0;
--- 142,172 ----
  /* NeXTStep seems to define _SC_CLK_TCK but not to have sysconf;
     fixme: does using _POSIX_VERSION help? */
  #  if defined _SC_CLK_TCK && defined _POSIX_VERSION
!   if (!clk_tck)
!     clk_tck = sysconf (_SC_CLK_TCK);
  #  elif defined CLOCKS_PER_SECOND
!   if (!clk_tck)
!     clk_tck = CLOCKS_PER_SECOND;
  #  elif defined CLK_TCK
!   if (!clk_tck)
!     clk_tck = CLK_TCK;
  #  elif defined HZ
!   if (!clk_tck)
!     clk_tck = HZ;
  #  elif defined HAVE_GETRUSAGE
  #  else
! #error Dont know clock tick length
  #  endif
!   if (times (&buffer) == (clock_t) - 1)
!     return -1.0;
!   utime = buffer.tms_utime;
!   stime = buffer.tms_stime;
!   tarray[0] = ((float) (utime - old_utime)) / (float) clk_tck;
!   tarray[1] = ((float) (stime - old_stime)) / (float) clk_tck;
  #endif /* HAVE_GETRUSAGE */
!   old_utime = utime;
!   old_stime = stime;
!   return (tarray[0] + tarray[1]);
  #else /* ! HAVE_GETRUSAGE && ! HAVE_TIMES */
    errno = ENOSYS;
    return 0.0;
diff -Nrc3pad gcc-3.2.3/libf2c/libU77/etime_.c gcc-3.3/libf2c/libU77/etime_.c
*** gcc-3.2.3/libf2c/libU77/etime_.c	2000-06-21 20:13:23.000000000 +0000
--- gcc-3.3/libf2c/libU77/etime_.c	2002-06-04 02:25:48.000000000 +0000
*************** Boston, MA 02111-1307, USA.  */
*** 44,62 ****
  #include <errno.h>		/* for ENOSYS */
  #include "f2c.h"
  
! /* For dtime, etime we store the clock tick parameter (clk_tck) the
!    first time either of them is invoked rather than each time.  This
!    approach probably speeds up each invocation by avoiding a system
!    call each time, but means that the overhead of the first call is
!    different to all others. */
! static long clk_tck = 0;
! 
! #ifdef KR_headers
! double G77_etime_0 (tarray)
!      real tarray[2];
! #else
! double G77_etime_0 (real tarray[2])
! #endif
  {
  #if defined (_WIN32)
    static int win32_platform = -1;
--- 44,51 ----
  #include <errno.h>		/* for ENOSYS */
  #include "f2c.h"
  
! double
! G77_etime_0 (real tarray[2])
  {
  #if defined (_WIN32)
    static int win32_platform = -1;
*************** double G77_etime_0 (real tarray[2])
*** 69,75 ****
        GetVersionEx (&osv);
        win32_platform = osv.dwPlatformId;
      }
!   
    /* non-NT platforms don't have a clue as to how long a process has
       been running, so simply return the uptime. Bad judgement call? */
    if (win32_platform != VER_PLATFORM_WIN32_NT)
--- 58,64 ----
        GetVersionEx (&osv);
        win32_platform = osv.dwPlatformId;
      }
! 
    /* non-NT platforms don't have a clue as to how long a process has
       been running, so simply return the uptime. Bad judgement call? */
    if (win32_platform != VER_PLATFORM_WIN32_NT)
*************** double G77_etime_0 (real tarray[2])
*** 82,88 ****
        if (clock_freq == 0)
  	{
  	  LARGE_INTEGER freq;
! 	  if (! QueryPerformanceFrequency (&freq))
  	    {
  	      errno = ENOSYS;
  	      return 0.0;
--- 71,77 ----
        if (clock_freq == 0)
  	{
  	  LARGE_INTEGER freq;
! 	  if (!QueryPerformanceFrequency (&freq))
  	    {
  	      errno = ENOSYS;
  	      return 0.0;
*************** double G77_etime_0 (real tarray[2])
*** 90,108 ****
  	  else
  	    {
  	      clock_freq = ((unsigned long long) freq.HighPart << 32)
!                            + ((unsigned) freq.LowPart);
! 	      if (! QueryPerformanceCounter (&counter_val))
  		return -1.0;
  	      old_count = ((unsigned long long) counter_val.HighPart << 32)
! 	                  + (unsigned) counter_val.LowPart;
  	    }
  	}
  
!       if (! QueryPerformanceCounter (&counter_val))
  	return -1.0;
  
        count = ((unsigned long long) counter_val.HighPart << 32)
!               + (unsigned) counter_val.LowPart;
        tarray[0] = usertime = (double) (count - old_count) / clock_freq;
        tarray[1] = systime = 0.0;
      }
--- 79,97 ----
  	  else
  	    {
  	      clock_freq = ((unsigned long long) freq.HighPart << 32)
! 		+ ((unsigned) freq.LowPart);
! 	      if (!QueryPerformanceCounter (&counter_val))
  		return -1.0;
  	      old_count = ((unsigned long long) counter_val.HighPart << 32)
! 		+ (unsigned) counter_val.LowPart;
  	    }
  	}
  
!       if (!QueryPerformanceCounter (&counter_val))
  	return -1.0;
  
        count = ((unsigned long long) counter_val.HighPart << 32)
! 	+ (unsigned) counter_val.LowPart;
        tarray[0] = usertime = (double) (count - old_count) / clock_freq;
        tarray[1] = systime = 0.0;
      }
*************** double G77_etime_0 (real tarray[2])
*** 114,126 ****
        GetProcessTimes (GetCurrentProcess (), &creation_time, &exit_time,
  		       &kernel_time, &user_time);
        utime = ((unsigned long long) user_time.dwHighDateTime << 32)
! 	      + (unsigned) user_time.dwLowDateTime;
        stime = ((unsigned long long) kernel_time.dwHighDateTime << 32)
! 	      + (unsigned) kernel_time.dwLowDateTime;
  
        tarray[0] = usertime = utime / 1.0e7;
        tarray[1] = systime = stime / 1.0e7;
!   }
    return usertime + systime;
  
  #elif defined (HAVE_GETRUSAGE) || defined (HAVE_TIMES)
--- 103,115 ----
        GetProcessTimes (GetCurrentProcess (), &creation_time, &exit_time,
  		       &kernel_time, &user_time);
        utime = ((unsigned long long) user_time.dwHighDateTime << 32)
! 	+ (unsigned) user_time.dwLowDateTime;
        stime = ((unsigned long long) kernel_time.dwHighDateTime << 32)
! 	+ (unsigned) kernel_time.dwLowDateTime;
  
        tarray[0] = usertime = utime / 1.0e7;
        tarray[1] = systime = stime / 1.0e7;
!     }
    return usertime + systime;
  
  #elif defined (HAVE_GETRUSAGE) || defined (HAVE_TIMES)
*************** double G77_etime_0 (real tarray[2])
*** 128,161 ****
  #ifdef HAVE_GETRUSAGE
    struct rusage rbuff;
  
!    if (getrusage (RUSAGE_SELF, &rbuff) != 0)
!      abort ();
!    tarray[0] = ((float) (rbuff.ru_utime).tv_sec +
! 	       (float) (rbuff.ru_utime).tv_usec/1000000.0);
!    tarray[1] = ((float) (rbuff.ru_stime).tv_sec +
! 	       (float) (rbuff.ru_stime).tv_usec/1000000.0);
! #else  /* HAVE_GETRUSAGE */
    struct tms buffer;
  
  /* NeXTStep seems to define _SC_CLK_TCK but not to have sysconf;
     fixme: does using _POSIX_VERSION help? */
  #  if defined _SC_CLK_TCK && defined _POSIX_VERSION
!   if (! clk_tck) clk_tck = sysconf(_SC_CLK_TCK);
  #  elif defined CLOCKS_PER_SECOND
!   if (! clk_tck) clk_tck = CLOCKS_PER_SECOND;
  #  elif defined CLK_TCK
!   if (! clk_tck) clk_tck = CLK_TCK;
  #  elif defined HZ
!   if (! clk_tck) clk_tck = HZ;
  #  elif defined HAVE_GETRUSAGE
  #  else
!   #error Dont know clock tick length
  #  endif
!   if (times(&buffer) == (clock_t)-1) return -1.0;
!   tarray[0] = (float) buffer.tms_utime / (float)clk_tck;
!   tarray[1] = (float) buffer.tms_stime / (float)clk_tck;
  #endif /* HAVE_GETRUSAGE */
!   return (tarray[0]+tarray[1]);
  #else /* ! HAVE_GETRUSAGE && ! HAVE_TIMES */
    errno = ENOSYS;
    return 0.0;
--- 117,161 ----
  #ifdef HAVE_GETRUSAGE
    struct rusage rbuff;
  
!   if (getrusage (RUSAGE_SELF, &rbuff) != 0)
!     abort ();
!   tarray[0] = ((float) (rbuff.ru_utime).tv_sec +
! 	       (float) (rbuff.ru_utime).tv_usec / 1000000.0);
!   tarray[1] = ((float) (rbuff.ru_stime).tv_sec +
! 	       (float) (rbuff.ru_stime).tv_usec / 1000000.0);
! #else /* HAVE_GETRUSAGE */
!   /* For dtime, etime we store the clock tick parameter (clk_tck) the
!      first time either of them is invoked rather than each time.  This
!      approach probably speeds up each invocation by avoiding a system
!      call each time, but means that the overhead of the first call is
!      different to all others. */
!   static long clk_tck = 0;
    struct tms buffer;
  
  /* NeXTStep seems to define _SC_CLK_TCK but not to have sysconf;
     fixme: does using _POSIX_VERSION help? */
  #  if defined _SC_CLK_TCK && defined _POSIX_VERSION
!   if (!clk_tck)
!     clk_tck = sysconf (_SC_CLK_TCK);
  #  elif defined CLOCKS_PER_SECOND
!   if (!clk_tck)
!     clk_tck = CLOCKS_PER_SECOND;
  #  elif defined CLK_TCK
!   if (!clk_tck)
!     clk_tck = CLK_TCK;
  #  elif defined HZ
!   if (!clk_tck)
!     clk_tck = HZ;
  #  elif defined HAVE_GETRUSAGE
  #  else
! #error Dont know clock tick length
  #  endif
!   if (times (&buffer) == (clock_t) - 1)
!     return -1.0;
!   tarray[0] = (float) buffer.tms_utime / (float) clk_tck;
!   tarray[1] = (float) buffer.tms_stime / (float) clk_tck;
  #endif /* HAVE_GETRUSAGE */
!   return (tarray[0] + tarray[1]);
  #else /* ! HAVE_GETRUSAGE && ! HAVE_TIMES */
    errno = ENOSYS;
    return 0.0;
diff -Nrc3pad gcc-3.2.3/libf2c/libU77/fdate_.c gcc-3.3/libf2c/libU77/fdate_.c
*** gcc-3.2.3/libf2c/libU77/fdate_.c	2001-01-23 23:20:30.000000000 +0000
--- gcc-3.3/libf2c/libU77/fdate_.c	2002-06-01 12:38:32.000000000 +0000
*************** Boston, MA 02111-1307, USA.  */
*** 43,54 ****
     also a subroutine version.  Of course, the calling convention is
     essentially the same for both. */
  
! /* Character *24 */ void G77_fdate_0 (char *ret_val, ftnlen ret_val_len)
  {
!     int s_copy ();
!     time_t tloc;
!     tloc = time (NULL);
!     /* Allow a length other than 24 for compatibility with what other
!        systems do, despite it being documented as 24. */
!     s_copy (ret_val, ctime ((time_t *) &tloc), ret_val_len, 24);
  }
--- 43,55 ----
     also a subroutine version.  Of course, the calling convention is
     essentially the same for both. */
  
! /* Character *24 */ void
! G77_fdate_0 (char *ret_val, ftnlen ret_val_len)
  {
!   int s_copy ();
!   time_t tloc;
!   tloc = time (NULL);
!   /* Allow a length other than 24 for compatibility with what other
!      systems do, despite it being documented as 24. */
!   s_copy (ret_val, ctime ((time_t *) & tloc), ret_val_len, 24);
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libU77/fgetc_.c gcc-3.3/libf2c/libU77/fgetc_.c
*** gcc-3.2.3/libf2c/libU77/fgetc_.c	1999-09-04 15:09:19.000000000 +0000
--- gcc-3.3/libf2c/libU77/fgetc_.c	2002-06-01 12:38:32.000000000 +0000
*************** Boston, MA 02111-1307, USA.  */
*** 26,68 ****
  #include "f2c.h"
  #include "fio.h"
  
! #ifdef KR_headers
! integer G77_fgetc_0 (lunit, c, Lc)
!      integer *lunit;
!      ftnlen Lc;			/* should be 1 */
!      char *c;
! #else
! integer G77_fgetc_0 (const integer *lunit, char *c, ftnlen Lc)
! #endif
  {
    int err;
    FILE *f = f__units[*lunit].ufd;
  
!   if (*lunit>=MXUNIT || *lunit<0)
      return 101;			/* bad unit error */
    err = getc (f);
!   if (err == EOF) {
!     if (feof (f))
!       return -1;
!     else
!       return ferror (f); }
!   else {
!     if (Lc == 0)
!       return 0;
  
!     c[0] = err;
!     while (--Lc)
!       *++c = ' ';
!     return 0; }
  }
  
! #ifdef KR_headers
! integer G77_fget_0 (c, Lc)
!      ftnlen Lc;			/* should be 1 */
!      char *c;
! #else
! integer G77_fget_0 (char *c, const ftnlen Lc)
! #endif
  {
    integer five = 5;
  
--- 26,61 ----
  #include "f2c.h"
  #include "fio.h"
  
! integer
! G77_fgetc_0 (const integer * lunit, char *c, ftnlen Lc)
  {
    int err;
    FILE *f = f__units[*lunit].ufd;
  
!   if (*lunit >= MXUNIT || *lunit < 0)
      return 101;			/* bad unit error */
    err = getc (f);
!   if (err == EOF)
!     {
!       if (feof (f))
! 	return -1;
!       else
! 	return ferror (f);
!     }
!   else
!     {
!       if (Lc == 0)
! 	return 0;
  
!       c[0] = err;
!       while (--Lc)
! 	*++c = ' ';
!       return 0;
!     }
  }
  
! integer
! G77_fget_0 (char *c, const ftnlen Lc)
  {
    integer five = 5;
  
diff -Nrc3pad gcc-3.2.3/libf2c/libU77/flush1_.c gcc-3.3/libf2c/libU77/flush1_.c
*** gcc-3.2.3/libf2c/libU77/flush1_.c	1999-09-04 15:09:19.000000000 +0000
--- gcc-3.3/libf2c/libU77/flush1_.c	2002-06-01 12:38:32.000000000 +0000
*************** Boston, MA 02111-1307, USA.  */
*** 25,46 ****
  
  /* This flushes a single unit, c.f. libI77 version. */
  
- #ifdef KR_headers
- extern integer G77_fnum_0 ();
- 
- /* Subroutine */ int G77_flush1_0 (lunit)
-      integer *lunit;
- #else
  extern integer G77_fnum_0 (integer *);
  
! /* Subroutine */ int G77_flush1_0 (const integer *lunit)
! #endif
  {
!   if (*lunit>=MXUNIT || *lunit<0)
!     err(1,101,"flush");
    /* f__units is a table of descriptions for the unit numbers (defined
       in io.h) with file descriptors rather than streams */
    if (f__units[*lunit].ufd != NULL && f__units[*lunit].uwrt)
!     fflush(f__units[*lunit].ufd);
    return 0;
  }
--- 25,40 ----
  
  /* This flushes a single unit, c.f. libI77 version. */
  
  extern integer G77_fnum_0 (integer *);
  
! /* Subroutine */ int
! G77_flush1_0 (const integer * lunit)
  {
!   if (*lunit >= MXUNIT || *lunit < 0)
!     err (1, 101, "flush");
    /* f__units is a table of descriptions for the unit numbers (defined
       in io.h) with file descriptors rather than streams */
    if (f__units[*lunit].ufd != NULL && f__units[*lunit].uwrt)
!     fflush (f__units[*lunit].ufd);
    return 0;
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libU77/fnum_.c gcc-3.3/libf2c/libU77/fnum_.c
*** gcc-3.2.3/libf2c/libU77/fnum_.c	1999-09-04 15:09:19.000000000 +0000
--- gcc-3.3/libf2c/libU77/fnum_.c	2002-06-01 12:38:32.000000000 +0000
*************** Boston, MA 02111-1307, USA.  */
*** 22,38 ****
  #include "f2c.h"
  #include "fio.h"
  
! #ifdef KR_headers
! integer G77_fnum_0 (lunit)
!      integer *lunit;
! #else
! integer G77_fnum_0 (integer *lunit)
! #endif
  {
!   if (*lunit>=MXUNIT || *lunit<0)
!     err(1,101,"fnum");
    /* f__units is a table of descriptions for the unit numbers (defined
       in io.h).  Use file descriptor (ufd) and fileno rather than udev
       field since udev is unix specific */
!   return fileno(f__units[*lunit].ufd);
  }
--- 22,34 ----
  #include "f2c.h"
  #include "fio.h"
  
! integer
! G77_fnum_0 (integer * lunit)
  {
!   if (*lunit >= MXUNIT || *lunit < 0)
!     err (1, 101, "fnum");
    /* f__units is a table of descriptions for the unit numbers (defined
       in io.h).  Use file descriptor (ufd) and fileno rather than udev
       field since udev is unix specific */
!   return fileno (f__units[*lunit].ufd);
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libU77/fputc_.c gcc-3.3/libf2c/libU77/fputc_.c
*** gcc-3.2.3/libf2c/libU77/fputc_.c	1999-09-04 15:09:19.000000000 +0000
--- gcc-3.3/libf2c/libU77/fputc_.c	2002-06-05 19:07:11.000000000 +0000
*************** Boston, MA 02111-1307, USA.  */
*** 26,63 ****
  #include "f2c.h"
  #include "fio.h"
  
! #ifdef KR_headers
! integer G77_fputc_0 (lunit, c, Lc)
!      integer *lunit;
!      ftnlen Lc;			/* should be 1 */
!      char *c;
! #else
! integer G77_fputc_0 (const integer *lunit, const char *c, const ftnlen Lc)
! #endif
  {
    int err;
    FILE *f = f__units[*lunit].ufd;
  
!   if (*lunit>=MXUNIT || *lunit<0)
      return 101;			/* bad unit error */
    err = putc (c[0], f);
!   if (err == EOF) {
!     if (feof (f))
!       return -1;
!     else
!       return ferror (f);
!   }
    else
      return 0;
  }
  
! #ifdef KR_headers
! integer G77_fput_0 (c, Lc)
!      ftnlen Lc;			/* should be 1 */
!      char *c;
! #else
! integer G77_fput_0 (const char *c, const ftnlen Lc)
! #endif
  {
    integer six = 6;
  
--- 26,54 ----
  #include "f2c.h"
  #include "fio.h"
  
! integer
! G77_fputc_0 (const integer * lunit, const char *c,
! 	     const ftnlen Lc __attribute__ ((__unused__)))
  {
    int err;
    FILE *f = f__units[*lunit].ufd;
  
!   if (*lunit >= MXUNIT || *lunit < 0)
      return 101;			/* bad unit error */
    err = putc (c[0], f);
!   if (err == EOF)
!     {
!       if (feof (f))
! 	return -1;
!       else
! 	return ferror (f);
!     }
    else
      return 0;
  }
  
! integer
! G77_fput_0 (const char *c, const ftnlen Lc)
  {
    integer six = 6;
  
diff -Nrc3pad gcc-3.2.3/libf2c/libU77/fstat_.c gcc-3.3/libf2c/libU77/fstat_.c
*** gcc-3.2.3/libf2c/libU77/fstat_.c	1999-09-04 15:09:19.000000000 +0000
--- gcc-3.3/libf2c/libU77/fstat_.c	2002-06-01 12:38:32.000000000 +0000
*************** Boston, MA 02111-1307, USA.  */
*** 26,42 ****
  #include <sys/types.h>
  #include <sys/stat.h>
  
- #ifdef KR_headers
- extern integer G77_fnum_0 ();
- 
- integer G77_fstat_0 (lunit, statb)
-      integer *lunit;
-      integer statb[13];
- #else
  extern integer G77_fnum_0 (const integer *);
  
! integer G77_fstat_0 (const integer *lunit, integer statb[13])
! #endif
  {
    int err;
    struct stat buf;
--- 26,35 ----
  #include <sys/types.h>
  #include <sys/stat.h>
  
  extern integer G77_fnum_0 (const integer *);
  
! integer
! G77_fstat_0 (const integer * lunit, integer statb[13])
  {
    int err;
    struct stat buf;
diff -Nrc3pad gcc-3.2.3/libf2c/libU77/gerror_.c gcc-3.3/libf2c/libU77/gerror_.c
*** gcc-3.2.3/libf2c/libU77/gerror_.c	1999-09-04 15:09:19.000000000 +0000
--- gcc-3.3/libf2c/libU77/gerror_.c	2002-06-01 12:38:32.000000000 +0000
*************** Boston, MA 02111-1307, USA.  */
*** 29,49 ****
  #include "f2c.h"
  
  #ifndef HAVE_STRERROR
!      extern char *sys_errlist [];
  #    define strerror(i) (sys_errlist[i])
  #endif
! #ifdef KR_headers
! extern void s_copy ();
! /* Subroutine */ int G77_gerror_0 (str, Lstr)
!      char *str; ftnlen Lstr;
! #else
! extern void s_copy(register char *a, register char *b, ftnlen la, ftnlen lb);
! /* Subroutine */ int G77_gerror_0 (char *str, ftnlen Lstr)
! #endif
  {
!   char * s;
  
!   s = strerror(errno);
    s_copy (str, s, Lstr, strlen (s));
    return 0;
  }
--- 29,44 ----
  #include "f2c.h"
  
  #ifndef HAVE_STRERROR
! extern char *sys_errlist[];
  #    define strerror(i) (sys_errlist[i])
  #endif
! extern void s_copy (register char *a, register char *b, ftnlen la, ftnlen lb);
! /* Subroutine */ int
! G77_gerror_0 (char *str, ftnlen Lstr)
  {
!   char *s;
  
!   s = strerror (errno);
    s_copy (str, s, Lstr, strlen (s));
    return 0;
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libU77/getcwd_.c gcc-3.3/libf2c/libU77/getcwd_.c
*** gcc-3.2.3/libf2c/libU77/getcwd_.c	1999-09-04 15:09:19.000000000 +0000
--- gcc-3.3/libf2c/libU77/getcwd_.c	2002-06-01 12:38:32.000000000 +0000
*************** Boston, MA 02111-1307, USA.  */
*** 34,59 ****
  #ifdef HAVE_UNISTD_H
  #  include <unistd.h>
  #else
!   extern char *getcwd ();
  #endif
  
! #ifdef KR_headers
! extern void s_copy ();
! integer G77_getcwd_0 (str, Lstr)
!      char *str; ftnlen Lstr;
! #else
! extern void s_copy(register char *a, register char *b, ftnlen la, ftnlen lb);
! integer G77_getcwd_0 (char *str, const ftnlen Lstr)
! #endif
  {
!     int i;
!     char *ret;
  
!     ret = getcwd (str, Lstr);
!     if (ret == NULL) return errno;
!     for (i=strlen(str); i<Lstr; i++)
! 	str[i] = ' ';
!     return 0;
  }
  
  #elif HAVE_GETWD		/* HAVE_GETCWD */
--- 34,55 ----
  #ifdef HAVE_UNISTD_H
  #  include <unistd.h>
  #else
! extern char *getcwd ();
  #endif
  
! extern void s_copy (register char *a, register char *b, ftnlen la, ftnlen lb);
! integer
! G77_getcwd_0 (char *str, const ftnlen Lstr)
  {
!   int i;
!   char *ret;
  
!   ret = getcwd (str, Lstr);
!   if (ret == NULL)
!     return errno;
!   for (i = strlen (str); i < Lstr; i++)
!     str[i] = ' ';
!   return 0;
  }
  
  #elif HAVE_GETWD		/* HAVE_GETCWD */
*************** integer G77_getcwd_0 (char *str, const f
*** 61,97 ****
  /* getwd usage taken from SunOS4 man */
  
  #  include <sys/param.h>
!   extern char *getwd ();
! #ifdef KR_headers
! extern VOID s_copy ();
! integer G77_getcwd_0 (str, Lstr)
!      char *str; ftnlen Lstr;
! #else
! extern void s_copy(register char *a, register char *b, ftnlen la, ftnlen lb);
! integer G77_getcwd_0 (char *str, const ftnlen Lstr)
! #endif
  {
    char pathname[MAXPATHLEN];
    size_t l;
  
!   if (getwd (pathname) == NULL) {
!     return errno;
!   } else {
!     s_copy (str, pathname, Lstr, strlen (str));
!     return 0;
!   }
  }
  
! #else  /* !HAVE_GETWD && !HAVE_GETCWD */
  
! #ifdef KR_headers
! extern VOID s_copy ();
! integer G77_getcwd_0 (str, Lstr)
!      char *str; ftnlen Lstr;
! #else
! extern void s_copy(register char *a, register char *b, ftnlen la, ftnlen lb);
! integer G77_getcwd_0 (char *str, const ftnlen Lstr)
! #endif
  {
    return errno = ENOSYS;
  }
--- 57,86 ----
  /* getwd usage taken from SunOS4 man */
  
  #  include <sys/param.h>
! extern char *getwd ();
! extern void s_copy (register char *a, register char *b, ftnlen la, ftnlen lb);
! integer
! G77_getcwd_0 (char *str, const ftnlen Lstr)
  {
    char pathname[MAXPATHLEN];
    size_t l;
  
!   if (getwd (pathname) == NULL)
!     {
!       return errno;
!     }
!   else
!     {
!       s_copy (str, pathname, Lstr, strlen (str));
!       return 0;
!     }
  }
  
! #else /* !HAVE_GETWD && !HAVE_GETCWD */
  
! extern void s_copy (register char *a, register char *b, ftnlen la, ftnlen lb);
! integer
! G77_getcwd_0 (char *str, const ftnlen Lstr)
  {
    return errno = ENOSYS;
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libU77/getgid_.c gcc-3.3/libf2c/libU77/getgid_.c
*** gcc-3.2.3/libf2c/libU77/getgid_.c	1999-09-04 15:09:19.000000000 +0000
--- gcc-3.3/libf2c/libU77/getgid_.c	2002-06-01 12:38:32.000000000 +0000
*************** Boston, MA 02111-1307, USA.  */
*** 26,36 ****
  #include <errno.h>		/* for ENOSYS */
  #include "f2c.h"
  
! #ifdef KR_headers
! integer G77_getgid_0 ()
! #else
! integer G77_getgid_0 (void)
! #endif
  {
  #if defined (HAVE_GETGID)
    return getgid ();
--- 26,33 ----
  #include <errno.h>		/* for ENOSYS */
  #include "f2c.h"
  
! integer
! G77_getgid_0 (void)
  {
  #if defined (HAVE_GETGID)
    return getgid ();
diff -Nrc3pad gcc-3.2.3/libf2c/libU77/getlog_.c gcc-3.3/libf2c/libU77/getlog_.c
*** gcc-3.2.3/libf2c/libU77/getlog_.c	1999-09-04 15:09:19.000000000 +0000
--- gcc-3.3/libf2c/libU77/getlog_.c	2002-06-01 12:38:32.000000000 +0000
*************** Boston, MA 02111-1307, USA.  */
*** 41,54 ****
  
  /* SGI also has character*(*) function getlog() */
  
! #ifdef KR_headers
! extern VOID s_copy ();
! /* Subroutine */ int G77_getlog_0 (str, Lstr)
!      char *str; ftnlen Lstr;
! #else
! extern void s_copy(register char *a, register char *b, ftnlen la, ftnlen lb);
! /* Subroutine */ int G77_getlog_0 (char *str, const ftnlen Lstr)
! #endif
  {
    size_t i;
    char *p;
--- 41,49 ----
  
  /* SGI also has character*(*) function getlog() */
  
! extern void s_copy (register char *a, register char *b, ftnlen la, ftnlen lb);
! /* Subroutine */ int
! G77_getlog_0 (char *str, const ftnlen Lstr)
  {
    size_t i;
    char *p;
*************** extern void s_copy(register char *a, reg
*** 56,67 ****
  
  #if defined (HAVE_GETLOGIN)
    p = getlogin ();
!   if (p != NULL) {
!     i = strlen (p);
!     s_copy (str, p, Lstr, i);
!   } else {
!     s_copy (str, " ", Lstr, 1);
!   }
    status = 0;
  #else
    errno = ENOSYS;
--- 51,65 ----
  
  #if defined (HAVE_GETLOGIN)
    p = getlogin ();
!   if (p != NULL)
!     {
!       i = strlen (p);
!       s_copy (str, p, Lstr, i);
!     }
!   else
!     {
!       s_copy (str, " ", Lstr, 1);
!     }
    status = 0;
  #else
    errno = ENOSYS;
diff -Nrc3pad gcc-3.2.3/libf2c/libU77/getpid_.c gcc-3.3/libf2c/libU77/getpid_.c
*** gcc-3.2.3/libf2c/libU77/getpid_.c	1999-09-04 15:09:19.000000000 +0000
--- gcc-3.3/libf2c/libU77/getpid_.c	2002-06-01 12:38:32.000000000 +0000
*************** Boston, MA 02111-1307, USA.  */
*** 25,35 ****
  #include <sys/types.h>
  #include "f2c.h"
  
! #ifdef KR_headers
! integer G77_getpid_0 ()
! #else
! integer G77_getpid_0 (void)
! #endif
  {
    return getpid ();
  }
--- 25,32 ----
  #include <sys/types.h>
  #include "f2c.h"
  
! integer
! G77_getpid_0 (void)
  {
    return getpid ();
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libU77/getuid_.c gcc-3.3/libf2c/libU77/getuid_.c
*** gcc-3.2.3/libf2c/libU77/getuid_.c	1999-09-04 15:09:19.000000000 +0000
--- gcc-3.3/libf2c/libU77/getuid_.c	2002-06-01 12:38:32.000000000 +0000
*************** Boston, MA 02111-1307, USA.  */
*** 26,36 ****
  #include <errno.h>		/* for ENOSYS */
  #include "f2c.h"
  
! #ifdef KR_headers
! integer G77_getuid_0 ()
! #else
! integer G77_getuid_0 (void)
! #endif
  {
  #if defined (HAVE_GETUID)
    return getuid ();
--- 26,33 ----
  #include <errno.h>		/* for ENOSYS */
  #include "f2c.h"
  
! integer
! G77_getuid_0 (void)
  {
  #if defined (HAVE_GETUID)
    return getuid ();
diff -Nrc3pad gcc-3.2.3/libf2c/libU77/gmtime_.c gcc-3.3/libf2c/libU77/gmtime_.c
*** gcc-3.2.3/libf2c/libU77/gmtime_.c	2001-01-23 23:20:30.000000000 +0000
--- gcc-3.3/libf2c/libU77/gmtime_.c	2002-06-01 12:38:32.000000000 +0000
*************** Boston, MA 02111-1307, USA.  */
*** 33,44 ****
  #endif
  #include "f2c.h"
  
! #ifdef KR_headers
! /* Subroutine */ int G77_gmtime_0 (xstime, tarray)
!      integer *xstime, tarray[9];
! #else
! /* Subroutine */ int G77_gmtime_0 (const integer * xstime, integer tarray[9])
! #endif
  {
    struct tm *lt;
    time_t stime = *xstime;
--- 33,40 ----
  #endif
  #include "f2c.h"
  
! /* Subroutine */ int
! G77_gmtime_0 (const integer * xstime, integer tarray[9])
  {
    struct tm *lt;
    time_t stime = *xstime;
diff -Nrc3pad gcc-3.2.3/libf2c/libU77/hostnm_.c gcc-3.3/libf2c/libU77/hostnm_.c
*** gcc-3.2.3/libf2c/libU77/hostnm_.c	1998-04-27 10:11:57.000000000 +0000
--- gcc-3.3/libf2c/libU77/hostnm_.c	2002-06-01 12:38:32.000000000 +0000
*************** Boston, MA 02111-1307, USA.  */
*** 30,49 ****
  #include <errno.h>		/* for ENOSYS */
  #include "f2c.h"
  
! integer G77_hostnm_0 (char *name, ftnlen Lname)
  {
!     int ret, i;
  
  #if HAVE_GETHOSTNAME
!     ret = gethostname (name, Lname);
!     if (ret==0) {
! 	/* Pad with blanks (assuming gethostname will make an error
!            return if it can't fit in the null). */
! 	for (i=strlen(name); i<Lname; i++)
! 	    name[i] = ' ';
      }
!     return ret;
  #else
!     return errno = ENOSYS;
  #endif
  }
--- 30,51 ----
  #include <errno.h>		/* for ENOSYS */
  #include "f2c.h"
  
! integer
! G77_hostnm_0 (char *name, ftnlen Lname)
  {
!   int ret, i;
  
  #if HAVE_GETHOSTNAME
!   ret = gethostname (name, Lname);
!   if (ret == 0)
!     {
!       /* Pad with blanks (assuming gethostname will make an error
!          return if it can't fit in the null). */
!       for (i = strlen (name); i < Lname; i++)
! 	name[i] = ' ';
      }
!   return ret;
  #else
!   return errno = ENOSYS;
  #endif
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libU77/idate_.c gcc-3.3/libf2c/libU77/idate_.c
*** gcc-3.2.3/libf2c/libU77/idate_.c	2001-01-23 23:20:30.000000000 +0000
--- gcc-3.3/libf2c/libU77/idate_.c	2002-06-01 12:38:32.000000000 +0000
*************** Boston, MA 02111-1307, USA.  */
*** 37,53 ****
  
  /* libU77 one: */
  
! #ifdef KR_headers
! /* Subroutine */ int G77_idate_0 (iarray)
!      int iarray[3];
! #else
! /* Subroutine */ int G77_idate_0 (int iarray[3])
! #endif
  {
    struct tm *lt;
    time_t tim;
!   tim = time(NULL);
!   lt = localtime(&tim);
    iarray[0] = lt->tm_mday;
    iarray[1] = lt->tm_mon + 1;	/* in range 1-12 in SunOS (experimentally) */
    /* The `+1900' is consistent with SunOS and Irix, but they don't say
--- 37,49 ----
  
  /* libU77 one: */
  
! /* Subroutine */ int
! G77_idate_0 (int iarray[3])
  {
    struct tm *lt;
    time_t tim;
!   tim = time (NULL);
!   lt = localtime (&tim);
    iarray[0] = lt->tm_mday;
    iarray[1] = lt->tm_mon + 1;	/* in range 1-12 in SunOS (experimentally) */
    /* The `+1900' is consistent with SunOS and Irix, but they don't say
diff -Nrc3pad gcc-3.2.3/libf2c/libU77/ierrno_.c gcc-3.3/libf2c/libU77/ierrno_.c
*** gcc-3.2.3/libf2c/libU77/ierrno_.c	1999-09-04 15:09:19.000000000 +0000
--- gcc-3.3/libf2c/libU77/ierrno_.c	2002-06-01 12:38:32.000000000 +0000
*************** Boston, MA 02111-1307, USA.  */
*** 22,32 ****
  #include <errno.h>
  #include "f2c.h"
  
! #ifdef KR_headers
! integer G77_ierrno_0 ()
! #else
! integer G77_ierrno_0 (void)
! #endif
  {
    return errno;
  }
--- 22,29 ----
  #include <errno.h>
  #include "f2c.h"
  
! integer
! G77_ierrno_0 (void)
  {
    return errno;
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libU77/irand_.c gcc-3.3/libf2c/libU77/irand_.c
*** gcc-3.2.3/libf2c/libU77/irand_.c	1999-09-04 15:09:19.000000000 +0000
--- gcc-3.3/libf2c/libU77/irand_.c	2002-06-01 12:38:32.000000000 +0000
*************** Boston, MA 02111-1307, USA.  */
*** 31,57 ****
  
  /* Note this is per SunOS -- other s may have no arg. */
  
! #ifdef KR_headers
! integer G77_irand_0 (flag)
!   integer *flag;
! #else
! integer G77_irand_0 (integer *flag)
! #endif
  {
!   switch (*flag) {
!   case 0:
!     break;
!   case 1:
!     srand (0);			/* Arbitrary choice of initialiser. */
!     break;
!   default:
!     srand (*flag);
!   }
    return rand ();
  }
- 
- 
- 
- 
- 
- 
--- 31,48 ----
  
  /* Note this is per SunOS -- other s may have no arg. */
  
! integer
! G77_irand_0 (integer * flag)
  {
!   switch (*flag)
!     {
!     case 0:
!       break;
!     case 1:
!       srand (0);		/* Arbitrary choice of initialiser. */
!       break;
!     default:
!       srand (*flag);
!     }
    return rand ();
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libU77/isatty_.c gcc-3.3/libf2c/libU77/isatty_.c
*** gcc-3.2.3/libf2c/libU77/isatty_.c	1999-09-04 15:09:19.000000000 +0000
--- gcc-3.3/libf2c/libU77/isatty_.c	2002-06-01 12:38:32.000000000 +0000
*************** Boston, MA 02111-1307, USA.  */
*** 25,44 ****
  #include "f2c.h"
  #include "fio.h"
  
- #ifdef KR_headers
- extern integer G77_fnum_0 ();
- 
- logical G77_isatty_0 (lunit)
-      integer *lunit;
- #else
  extern integer G77_fnum_0 (integer *);
  
! logical G77_isatty_0 (integer *lunit)
! #endif
  {
!   if (*lunit>=MXUNIT || *lunit<0)
!     err(1,101,"isatty");
    /* f__units is a table of descriptions for the unit numbers (defined
       in io.h) with file descriptors rather than streams */
!   return (isatty(G77_fnum_0 (lunit)) ? TRUE_ : FALSE_);
  }
--- 25,38 ----
  #include "f2c.h"
  #include "fio.h"
  
  extern integer G77_fnum_0 (integer *);
  
! logical
! G77_isatty_0 (integer * lunit)
  {
!   if (*lunit >= MXUNIT || *lunit < 0)
!     err (1, 101, "isatty");
    /* f__units is a table of descriptions for the unit numbers (defined
       in io.h) with file descriptors rather than streams */
!   return (isatty (G77_fnum_0 (lunit)) ? TRUE_ : FALSE_);
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libU77/itime_.c gcc-3.3/libf2c/libU77/itime_.c
*** gcc-3.2.3/libf2c/libU77/itime_.c	2001-01-23 23:20:30.000000000 +0000
--- gcc-3.3/libf2c/libU77/itime_.c	2002-06-01 12:38:32.000000000 +0000
*************** Boston, MA 02111-1307, USA.  */
*** 33,50 ****
  #endif
  #include "f2c.h"
  
! #ifdef KR_headers
! /* Subroutine */ int G77_itime_0 (tarray)
!      integer tarray[3];
! #else
! /* Subroutine */ int G77_itime_0 (integer tarray[3])
! #endif
  {
    struct tm *lt;
    time_t tim;
  
!   tim = time(NULL);
!   lt = localtime(&tim);
    tarray[0] = lt->tm_hour;
    tarray[1] = lt->tm_min;
    tarray[2] = lt->tm_sec;
--- 33,46 ----
  #endif
  #include "f2c.h"
  
! /* Subroutine */ int
! G77_itime_0 (integer tarray[3])
  {
    struct tm *lt;
    time_t tim;
  
!   tim = time (NULL);
!   lt = localtime (&tim);
    tarray[0] = lt->tm_hour;
    tarray[1] = lt->tm_min;
    tarray[2] = lt->tm_sec;
diff -Nrc3pad gcc-3.2.3/libf2c/libU77/kill_.c gcc-3.3/libf2c/libU77/kill_.c
*** gcc-3.2.3/libf2c/libU77/kill_.c	1999-09-04 15:09:19.000000000 +0000
--- gcc-3.3/libf2c/libU77/kill_.c	2002-06-01 12:38:32.000000000 +0000
*************** Boston, MA 02111-1307, USA.  */
*** 26,40 ****
  
  /* fixme: bsd, svr1-3 use int, not pid_t */
  
! #ifdef KR_headers
! integer G77_kill_0 (pid, signum)
!      integer *pid, *signum;
! #else
! integer G77_kill_0 (const integer *pid, const integer *signum)
! #endif
  {
  #if defined (HAVE_KILL)
!   return kill ((pid_t) *pid, *signum) ? errno : 0;
  #else
    errno = ENOSYS;
    return -1;
--- 26,36 ----
  
  /* fixme: bsd, svr1-3 use int, not pid_t */
  
! integer
! G77_kill_0 (const integer * pid, const integer * signum)
  {
  #if defined (HAVE_KILL)
!   return kill ((pid_t) * pid, *signum) ? errno : 0;
  #else
    errno = ENOSYS;
    return -1;
diff -Nrc3pad gcc-3.2.3/libf2c/libU77/link_.c gcc-3.3/libf2c/libU77/link_.c
*** gcc-3.2.3/libf2c/libU77/link_.c	1999-09-04 15:09:19.000000000 +0000
--- gcc-3.3/libf2c/libU77/link_.c	2002-06-02 12:59:22.000000000 +0000
*************** Boston, MA 02111-1307, USA.  */
*** 34,63 ****
  #include <errno.h>		/* for ENOSYS */
  #include "f2c.h"
  
! #ifdef KR_headers
! void g_char ();
! 
! integer G77_link_0 (path1, path2, Lpath1, Lpath2)
!      char *path1, *path2; ftnlen Lpath1, Lpath2;
! #else
! void g_char(const char *a, ftnlen alen, char *b);
  
! integer G77_link_0 (const char *path1, const char *path2, const ftnlen Lpath1, const ftnlen Lpath2)
! #endif
  {
  #if defined (HAVE_LINK)
    char *buff1, *buff2;
-   char *bp, *blast;
    int i;
  
!   buff1 = malloc (Lpath1+1);
!   if (buff1 == NULL) return -1;
    g_char (path1, Lpath1, buff1);
!   buff2 = malloc (Lpath2+1);
!   if (buff2 == NULL) return -1;
    g_char (path2, Lpath2, buff2);
    i = link (buff1, buff2);
!   free (buff1); free (buff2);
    return i ? errno : 0;
  #else /* ! HAVE_LINK */
    errno = ENOSYS;
--- 34,60 ----
  #include <errno.h>		/* for ENOSYS */
  #include "f2c.h"
  
! void g_char (const char *a, ftnlen alen, char *b);
  
! integer
! G77_link_0 (const char *path1, const char *path2, const ftnlen Lpath1,
! 	    const ftnlen Lpath2)
  {
  #if defined (HAVE_LINK)
    char *buff1, *buff2;
    int i;
  
!   buff1 = malloc (Lpath1 + 1);
!   if (buff1 == NULL)
!     return -1;
    g_char (path1, Lpath1, buff1);
!   buff2 = malloc (Lpath2 + 1);
!   if (buff2 == NULL)
!     return -1;
    g_char (path2, Lpath2, buff2);
    i = link (buff1, buff2);
!   free (buff1);
!   free (buff2);
    return i ? errno : 0;
  #else /* ! HAVE_LINK */
    errno = ENOSYS;
diff -Nrc3pad gcc-3.2.3/libf2c/libU77/lnblnk_.c gcc-3.3/libf2c/libU77/lnblnk_.c
*** gcc-3.2.3/libf2c/libU77/lnblnk_.c	1999-09-04 15:09:19.000000000 +0000
--- gcc-3.3/libf2c/libU77/lnblnk_.c	2002-06-01 12:38:32.000000000 +0000
*************** Boston, MA 02111-1307, USA.  */
*** 21,35 ****
  
  #include "f2c.h"
  
! integer G77_lnblnk_0 (char *str, ftnlen str_len)
  {
!     integer ret_val;
!     integer i_len();
  
!     for (ret_val = str_len; ret_val >= 1; --ret_val) {
! 	if (*(unsigned char *)&str[ret_val - 1] != ' ') {
! 	    return ret_val;
  	}
      }
!     return ret_val;
  }
--- 21,38 ----
  
  #include "f2c.h"
  
! integer
! G77_lnblnk_0 (char *str, ftnlen str_len)
  {
!   integer ret_val;
!   integer i_len ();
  
!   for (ret_val = str_len; ret_val >= 1; --ret_val)
!     {
!       if (*(unsigned char *) &str[ret_val - 1] != ' ')
! 	{
! 	  return ret_val;
  	}
      }
!   return ret_val;
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libU77/lstat_.c gcc-3.3/libf2c/libU77/lstat_.c
*** gcc-3.2.3/libf2c/libU77/lstat_.c	1999-02-20 14:55:52.000000000 +0000
--- gcc-3.3/libf2c/libU77/lstat_.c	2002-06-02 12:59:22.000000000 +0000
*************** Boston, MA 02111-1307, USA.  */
*** 30,56 ****
  
  /* lstat isn't posix */
  
! #ifdef KR_headers
! void g_char();
! 
! integer G77_lstat_0 (name, statb, Lname)
!      char *name;
!      integer statb[13];
!      ftnlen Lname;
! #else
! void g_char(const char *a, ftnlen alen, char *b);
  
! integer G77_lstat_0 (const char *name, integer statb[13], const ftnlen Lname)
! #endif
  {
  #if HAVE_LSTAT
    char *buff;
-   char *bp, *blast;
    int err;
    struct stat buf;
  
!   buff = malloc (Lname+1);
!   if (buff == NULL) return -1;
    g_char (name, Lname, buff);
    err = lstat (buff, &buf);
    free (buff);
--- 30,48 ----
  
  /* lstat isn't posix */
  
! void g_char (const char *a, ftnlen alen, char *b);
  
! integer
! G77_lstat_0 (const char *name, integer statb[13], const ftnlen Lname)
  {
  #if HAVE_LSTAT
    char *buff;
    int err;
    struct stat buf;
  
!   buff = malloc (Lname + 1);
!   if (buff == NULL)
!     return -1;
    g_char (name, Lname, buff);
    err = lstat (buff, &buf);
    free (buff);
*************** integer G77_lstat_0 (const char *name, i
*** 80,86 ****
    statb[12] = -1;
  #endif
    return err;
! #else	/* !HAVE_LSTAT */
    return errno = ENOSYS;
! #endif	/* !HAVE_LSTAT */
  }
--- 72,78 ----
    statb[12] = -1;
  #endif
    return err;
! #else /* !HAVE_LSTAT */
    return errno = ENOSYS;
! #endif /* !HAVE_LSTAT */
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libU77/ltime_.c gcc-3.3/libf2c/libU77/ltime_.c
*** gcc-3.2.3/libf2c/libU77/ltime_.c	2001-01-23 23:20:30.000000000 +0000
--- gcc-3.3/libf2c/libU77/ltime_.c	2002-06-01 12:38:32.000000000 +0000
*************** Boston, MA 02111-1307, USA.  */
*** 33,44 ****
  #endif
  #include "f2c.h"
  
! #ifdef KR_headers
! /* Subroutine */ int G77_ltime_0 (xstime, tarray)
!      integer *xstime, tarray[9];
! #else
! /* Subroutine */ int G77_ltime_0 (const integer * xstime, integer tarray[9])
! #endif
  {
    struct tm *lt;
    time_t stime = *xstime;
--- 33,40 ----
  #endif
  #include "f2c.h"
  
! /* Subroutine */ int
! G77_ltime_0 (const integer * xstime, integer tarray[9])
  {
    struct tm *lt;
    time_t stime = *xstime;
diff -Nrc3pad gcc-3.2.3/libf2c/libU77/Makefile.in gcc-3.3/libf2c/libU77/Makefile.in
*** gcc-3.2.3/libf2c/libU77/Makefile.in	2001-12-04 09:53:18.000000000 +0000
--- gcc-3.3/libf2c/libU77/Makefile.in	2002-05-31 03:07:21.000000000 +0000
*************** CFLAGS = @CFLAGS@
*** 37,49 ****
  CPPFLAGS = @CPPFLAGS@
  @SET_MAKE@
  
! SHELL = /bin/sh
  
  #### End of system configuration section. ####
  
  # fio.h is in libI77.  config.h is in `.'.
  ALL_CFLAGS = -I. -I$(srcdir) -I$(F2C_H_DIR)/libI77 -I$(G2C_H_DIR) \
!              -I$(F2C_H_DIR) $(CPPFLAGS) $(DEFS) $(CFLAGS)
  
  # This could probably be done more elegantly, but it's currently
  # just for running the u77-test test.
--- 37,49 ----
  CPPFLAGS = @CPPFLAGS@
  @SET_MAKE@
  
! SHELL = @SHELL@
  
  #### End of system configuration section. ####
  
  # fio.h is in libI77.  config.h is in `.'.
  ALL_CFLAGS = -I. -I$(srcdir) -I$(F2C_H_DIR)/libI77 -I$(G2C_H_DIR) \
!              -I$(F2C_H_DIR) $(CPPFLAGS) $(DEFS) $(WARN_CFLAGS) $(CFLAGS)
  
  # This could probably be done more elegantly, but it's currently
  # just for running the u77-test test.
diff -Nrc3pad gcc-3.2.3/libf2c/libU77/mclock_.c gcc-3.3/libf2c/libU77/mclock_.c
*** gcc-3.2.3/libf2c/libU77/mclock_.c	1999-09-04 15:09:19.000000000 +0000
--- gcc-3.3/libf2c/libU77/mclock_.c	2002-06-01 12:38:32.000000000 +0000
*************** Boston, MA 02111-1307, USA.  */
*** 33,43 ****
  
  /* Reported by wd42ej@sgi83.wwb.noaa.gov (Russ Jones AUTO-Sun3) on AIX. */
  
! #ifdef KR_headers
! longint G77_mclock_0 ()
! #else
! longint G77_mclock_0 (void)
! #endif
  {
  #if HAVE_CLOCK
    return clock ();
--- 33,40 ----
  
  /* Reported by wd42ej@sgi83.wwb.noaa.gov (Russ Jones AUTO-Sun3) on AIX. */
  
! longint
! G77_mclock_0 (void)
  {
  #if HAVE_CLOCK
    return clock ();
diff -Nrc3pad gcc-3.2.3/libf2c/libU77/perror_.c gcc-3.3/libf2c/libU77/perror_.c
*** gcc-3.2.3/libf2c/libU77/perror_.c	1999-09-04 15:09:19.000000000 +0000
--- gcc-3.3/libf2c/libU77/perror_.c	2002-06-01 12:38:32.000000000 +0000
*************** Boston, MA 02111-1307, USA.  */
*** 28,46 ****
  #endif
  #include "f2c.h"
  
! #ifdef KR_headers
! /* Subroutine */ int G77_perror_0 (str, Lstr)
!      char *str; ftnlen Lstr;
! #else
! /* Subroutine */ int G77_perror_0 (const char *str, const ftnlen Lstr)
! #endif
  {
    char buff[1000];
    char *bp, *blast;
  
    /* same technique as `system' -- what's wrong with malloc? */
    blast = buff + (Lstr < 1000 ? Lstr : 1000);
!   for (bp = buff ; bp<blast && *str!='\0' ; )
      *bp++ = *str++;
    *bp = '\0';
    perror (buff);
--- 28,42 ----
  #endif
  #include "f2c.h"
  
! /* Subroutine */ int
! G77_perror_0 (const char *str, const ftnlen Lstr)
  {
    char buff[1000];
    char *bp, *blast;
  
    /* same technique as `system' -- what's wrong with malloc? */
    blast = buff + (Lstr < 1000 ? Lstr : 1000);
!   for (bp = buff; bp < blast && *str != '\0';)
      *bp++ = *str++;
    *bp = '\0';
    perror (buff);
diff -Nrc3pad gcc-3.2.3/libf2c/libU77/rand_.c gcc-3.3/libf2c/libU77/rand_.c
*** gcc-3.2.3/libf2c/libU77/rand_.c	1999-09-04 15:09:19.000000000 +0000
--- gcc-3.3/libf2c/libU77/rand_.c	2002-06-01 12:38:32.000000000 +0000
*************** Boston, MA 02111-1307, USA.  */
*** 34,54 ****
  
  /* Note this is per SunOS -- other s may have no arg. */
  
! #ifdef KR_headers
! double G77_rand_0 (flag)
!   integer *flag;
! #else
! double G77_rand_0 (integer *flag)
! #endif
  {
!   switch (*flag) {
!   case 0:
!     break;
!   case 1:
!     srand (0);			/* Arbitrary choice of initialiser. */
!     break;
!   default:
!     srand (*flag);
!   }
    return (float) rand () / RAND_MAX;
  }
--- 34,51 ----
  
  /* Note this is per SunOS -- other s may have no arg. */
  
! double
! G77_rand_0 (integer * flag)
  {
!   switch (*flag)
!     {
!     case 0:
!       break;
!     case 1:
!       srand (0);		/* Arbitrary choice of initialiser. */
!       break;
!     default:
!       srand (*flag);
!     }
    return (float) rand () / RAND_MAX;
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libU77/rename_.c gcc-3.3/libf2c/libU77/rename_.c
*** gcc-3.2.3/libf2c/libU77/rename_.c	1999-09-04 15:09:19.000000000 +0000
--- gcc-3.3/libf2c/libU77/rename_.c	2002-06-02 12:59:22.000000000 +0000
*************** Boston, MA 02111-1307, USA.  */
*** 29,56 ****
  #include <errno.h>
  #include "f2c.h"
  
! #ifdef KR_headers
! void g_char ();
! 
! integer G77_rename_0 (path1, path2, Lpath1, Lpath2)
!      char *path1, *path2; ftnlen Lpath1, Lpath2;
! #else
! void g_char(const char *a, ftnlen alen, char *b);
  
! integer G77_rename_0 (const char *path1, const char *path2, const ftnlen Lpath1, const ftnlen Lpath2)
! #endif
  {
    char *buff1, *buff2;
-   char *bp, *blast;
    int i;
  
!   buff1 = malloc (Lpath1+1);
!   if (buff1 == NULL) return -1;
    g_char (path1, Lpath1, buff1);
!   buff2 = malloc (Lpath2+1);
!   if (buff2 == NULL) return -1;
    g_char (path2, Lpath2, buff2);
    i = rename (buff1, buff2);
!   free (buff1); free (buff2);
    return i ? errno : 0;
  }
--- 29,53 ----
  #include <errno.h>
  #include "f2c.h"
  
! void g_char (const char *a, ftnlen alen, char *b);
  
! integer
! G77_rename_0 (const char *path1, const char *path2, const ftnlen Lpath1,
! 	      const ftnlen Lpath2)
  {
    char *buff1, *buff2;
    int i;
  
!   buff1 = malloc (Lpath1 + 1);
!   if (buff1 == NULL)
!     return -1;
    g_char (path1, Lpath1, buff1);
!   buff2 = malloc (Lpath2 + 1);
!   if (buff2 == NULL)
!     return -1;
    g_char (path2, Lpath2, buff2);
    i = rename (buff1, buff2);
!   free (buff1);
!   free (buff2);
    return i ? errno : 0;
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libU77/secnds_.c gcc-3.3/libf2c/libU77/secnds_.c
*** gcc-3.2.3/libf2c/libU77/secnds_.c	1999-09-04 15:09:19.000000000 +0000
--- gcc-3.3/libf2c/libU77/secnds_.c	2002-06-01 12:38:32.000000000 +0000
*************** Boston, MA 02111-1307, USA.  */
*** 36,51 ****
  
  /* This is a VMS intrinsic. */
  
! double G77_secnds_0 (real *r)
  {
!     struct tm *lt;
!     time_t clock;
!     float f;
  
!     clock = time (NULL);
!     lt = localtime (&clock);
!     f= (3600.0*((real)lt->tm_hour) + 60.0*((real)lt->tm_min) +
! 	    (real)lt->tm_sec - *r);
!     return f;
  }
- 
--- 36,51 ----
  
  /* This is a VMS intrinsic. */
  
! double
! G77_secnds_0 (real * r)
  {
!   struct tm *lt;
!   time_t clock;
!   float f;
  
!   clock = time (NULL);
!   lt = localtime (&clock);
!   f = (3600.0 * ((real) lt->tm_hour) + 60.0 * ((real) lt->tm_min) +
!        (real) lt->tm_sec - *r);
!   return f;
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libU77/second_.c gcc-3.3/libf2c/libU77/second_.c
*** gcc-3.2.3/libf2c/libU77/second_.c	1999-09-04 15:09:19.000000000 +0000
--- gcc-3.3/libf2c/libU77/second_.c	2002-06-01 12:38:32.000000000 +0000
*************** Boston, MA 02111-1307, USA.  */
*** 18,24 ****
  
  #include "f2c.h"
  
! double G77_second_0 () {
    extern double G77_etime_0 ();
    real tarray[2];
  
--- 18,26 ----
  
  #include "f2c.h"
  
! double
! G77_second_0 ()
! {
    extern double G77_etime_0 ();
    real tarray[2];
  
diff -Nrc3pad gcc-3.2.3/libf2c/libU77/sleep_.c gcc-3.3/libf2c/libU77/sleep_.c
*** gcc-3.2.3/libf2c/libU77/sleep_.c	1999-09-04 15:09:19.000000000 +0000
--- gcc-3.3/libf2c/libU77/sleep_.c	2002-06-01 12:38:32.000000000 +0000
*************** Boston, MA 02111-1307, USA.  */
*** 25,36 ****
  #include "f2c.h"
  
  /* Subroutine */
! #ifdef KR_headers
! int G77_sleep_0 (seconds)
!      integer *seconds;
! #else
! int G77_sleep_0 (const integer *seconds)
! #endif
  {
    (void) sleep ((unsigned int) *seconds);
    return 0;
--- 25,32 ----
  #include "f2c.h"
  
  /* Subroutine */
! int
! G77_sleep_0 (const integer * seconds)
  {
    (void) sleep ((unsigned int) *seconds);
    return 0;
diff -Nrc3pad gcc-3.2.3/libf2c/libU77/srand_.c gcc-3.3/libf2c/libU77/srand_.c
*** gcc-3.2.3/libf2c/libU77/srand_.c	1999-09-04 15:09:19.000000000 +0000
--- gcc-3.3/libf2c/libU77/srand_.c	2002-06-01 12:38:32.000000000 +0000
*************** Boston, MA 02111-1307, USA.  */
*** 24,36 ****
  #endif
  #include "f2c.h"
  
! /* Subroutine */ 
! #ifdef KR_headers
! int G77_srand_0 (seed)
!      integer *seed;
! #else
! int G77_srand_0 (const integer *seed)
! #endif
  {
    srand ((unsigned int) *seed);
    return 0;
--- 24,32 ----
  #endif
  #include "f2c.h"
  
! /* Subroutine */
! int
! G77_srand_0 (const integer * seed)
  {
    srand ((unsigned int) *seed);
    return 0;
diff -Nrc3pad gcc-3.2.3/libf2c/libU77/stat_.c gcc-3.3/libf2c/libU77/stat_.c
*** gcc-3.2.3/libf2c/libU77/stat_.c	1999-09-04 15:09:19.000000000 +0000
--- gcc-3.3/libf2c/libU77/stat_.c	2002-06-02 12:59:22.000000000 +0000
*************** Boston, MA 02111-1307, USA.  */
*** 27,52 ****
  #include <sys/stat.h>
  #include "f2c.h"
  
! #ifdef KR_headers
! void g_char ();
! 
! integer G77_stat_0 (name, statb, Lname)
!      char *name;
!      integer statb[13];
!      ftnlen Lname;
! #else
! void g_char(const char *a, ftnlen alen, char *b);
  
! integer G77_stat_0 (const char *name, integer statb[13], const ftnlen Lname)
! #endif
  {
    char *buff;
-   char *bp, *blast;
    int err;
    struct stat buf;
  
!   buff = malloc (Lname+1);
!   if (buff == NULL) return -1;
    g_char (name, Lname, buff);
    err = stat (buff, &buf);
    free (buff);
--- 27,44 ----
  #include <sys/stat.h>
  #include "f2c.h"
  
! void g_char (const char *a, ftnlen alen, char *b);
  
! integer
! G77_stat_0 (const char *name, integer statb[13], const ftnlen Lname)
  {
    char *buff;
    int err;
    struct stat buf;
  
!   buff = malloc (Lname + 1);
!   if (buff == NULL)
!     return -1;
    g_char (name, Lname, buff);
    err = stat (buff, &buf);
    free (buff);
diff -Nrc3pad gcc-3.2.3/libf2c/libU77/symlnk_.c gcc-3.3/libf2c/libU77/symlnk_.c
*** gcc-3.2.3/libf2c/libU77/symlnk_.c	1999-09-04 15:09:19.000000000 +0000
--- gcc-3.3/libf2c/libU77/symlnk_.c	2002-06-02 12:59:22.000000000 +0000
*************** Boston, MA 02111-1307, USA.  */
*** 33,64 ****
  #endif
  #include "f2c.h"
  
! #ifdef KR_headers
! void g_char ();
! 
! integer G77_symlnk_0 (path1, path2, Lpath1, Lpath2)
!      char *path1, *path2; ftnlen Lpath1, Lpath2;
! #else
! void g_char(const char *a, ftnlen alen, char *b);
  
! integer G77_symlnk_0 (const char *path1, const char *path2, const ftnlen Lpath1, const ftnlen Lpath2)
! #endif
  {
  #if HAVE_SYMLINK
    char *buff1, *buff2;
-   char *bp, *blast;
    int i;
  
!   buff1 = (char *) malloc (Lpath1+1);
!   if (buff1 == NULL) return -1;
    g_char (path1, Lpath1, buff1);
!   buff2 = (char *) malloc (Lpath2+1);
!   if (buff2 == NULL) return -1;
    g_char (path2, Lpath2, buff2);
    i = symlink (buff1, buff2);
!   free (buff1); free (buff2);
    return i ? errno : 0;
! #else	/* !HAVE_SYMLINK */
    return errno = ENOSYS;
! #endif	/* !HAVE_SYMLINK */
  }
--- 33,61 ----
  #endif
  #include "f2c.h"
  
! void g_char (const char *a, ftnlen alen, char *b);
  
! integer
! G77_symlnk_0 (const char *path1, const char *path2, const ftnlen Lpath1,
! 	      const ftnlen Lpath2)
  {
  #if HAVE_SYMLINK
    char *buff1, *buff2;
    int i;
  
!   buff1 = (char *) malloc (Lpath1 + 1);
!   if (buff1 == NULL)
!     return -1;
    g_char (path1, Lpath1, buff1);
!   buff2 = (char *) malloc (Lpath2 + 1);
!   if (buff2 == NULL)
!     return -1;
    g_char (path2, Lpath2, buff2);
    i = symlink (buff1, buff2);
!   free (buff1);
!   free (buff2);
    return i ? errno : 0;
! #else /* !HAVE_SYMLINK */
    return errno = ENOSYS;
! #endif /* !HAVE_SYMLINK */
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libU77/sys_clock_.c gcc-3.3/libf2c/libU77/sys_clock_.c
*** gcc-3.2.3/libf2c/libU77/sys_clock_.c	2001-01-23 23:20:30.000000000 +0000
--- gcc-3.3/libf2c/libU77/sys_clock_.c	2002-06-01 12:38:32.000000000 +0000
*************** Boston, MA 02111-1307, USA.  */
*** 43,73 ****
  #include <errno.h>		/* for ENOSYS */
  #include "f2c.h"
  
! #ifdef KR_headers
! int G77_system_clock_0 (count, count_rate, count_max)
!      integer *count, *count_rate, *count_max;
! #else
! int G77_system_clock_0 (integer *count, integer *count_rate, integer *count_max)
! #endif
  {
  #if defined (HAVE_TIMES)
    struct tms buffer;
    unsigned long cnt;
!   if (count_rate) {
  #ifdef _SC_CLK_TCK
!     *count_rate = sysconf(_SC_CLK_TCK);
  #elif defined CLOCKS_PER_SECOND
!     *count_rate = CLOCKS_PER_SECOND;
  #elif defined CLK_TCK
!     *count_rate = CLK_TCK;
  #elif defined HZ
!     *count_rate = HZ;
  #else
  #error Dont know clock tick length
  #endif
!   }
    if (count_max)		/* optional arg present? */
!     *count_max = INT_MAX;		/* dubious */
    cnt = times (&buffer);
    if (cnt > (unsigned long) (INT_MAX))
      *count = INT_MAX;		/* also dubious */
--- 43,71 ----
  #include <errno.h>		/* for ENOSYS */
  #include "f2c.h"
  
! int
! G77_system_clock_0 (integer * count, integer * count_rate,
! 		    integer * count_max)
  {
  #if defined (HAVE_TIMES)
    struct tms buffer;
    unsigned long cnt;
!   if (count_rate)
!     {
  #ifdef _SC_CLK_TCK
!       *count_rate = sysconf (_SC_CLK_TCK);
  #elif defined CLOCKS_PER_SECOND
!       *count_rate = CLOCKS_PER_SECOND;
  #elif defined CLK_TCK
!       *count_rate = CLK_TCK;
  #elif defined HZ
!       *count_rate = HZ;
  #else
  #error Dont know clock tick length
  #endif
!     }
    if (count_max)		/* optional arg present? */
!     *count_max = INT_MAX;	/* dubious */
    cnt = times (&buffer);
    if (cnt > (unsigned long) (INT_MAX))
      *count = INT_MAX;		/* also dubious */
diff -Nrc3pad gcc-3.2.3/libf2c/libU77/time_.c gcc-3.3/libf2c/libU77/time_.c
*** gcc-3.2.3/libf2c/libU77/time_.c	1999-09-04 15:09:19.000000000 +0000
--- gcc-3.3/libf2c/libU77/time_.c	2002-06-01 12:38:32.000000000 +0000
*************** Boston, MA 02111-1307, USA.  */
*** 35,45 ****
  /* As well as this external function some compilers have an intrinsic
     subroutine which fills a character argument (which is the VMS way)
     -- caveat emptor. */
! #ifdef KR_headers
! longint G77_time_0 ()
! #else
! longint G77_time_0 (void)
! #endif
  {
    /* There are potential problems with the cast of the time_t here. */
    return time (NULL);
--- 35,42 ----
  /* As well as this external function some compilers have an intrinsic
     subroutine which fills a character argument (which is the VMS way)
     -- caveat emptor. */
! longint
! G77_time_0 (void)
  {
    /* There are potential problems with the cast of the time_t here. */
    return time (NULL);
diff -Nrc3pad gcc-3.2.3/libf2c/libU77/ttynam_.c gcc-3.3/libf2c/libU77/ttynam_.c
*** gcc-3.2.3/libf2c/libU77/ttynam_.c	1999-06-18 08:41:09.000000000 +0000
--- gcc-3.3/libf2c/libU77/ttynam_.c	2002-06-01 12:38:32.000000000 +0000
*************** Boston, MA 02111-1307, USA.  */
*** 35,62 ****
  #include <errno.h>		/* for ENOSYS */
  #include "f2c.h"
  
! #ifdef KR_headers
! extern void s_copy ();
! extern integer G77_fnum_0 ();
! /* Character */ void G77_ttynam_0 (ret_val, ret_val_len, lunit)
!      char *ret_val; ftnlen ret_val_len; integer *lunit
! #else
! extern integer G77_fnum_0 (integer *lunit);
! extern void s_copy(register char *a, register char *b, ftnlen la, ftnlen lb);
! /* Character */ void G77_ttynam_0 (char *ret_val, ftnlen ret_val_len, integer *lunit)
! #endif
  {
  #if defined (HAVE_TTYNAME)
    size_t i;
    char *p;
  
    p = ttyname (G77_fnum_0 (lunit));
!   if (p != NULL) {
!     i = strlen (p);
!     s_copy (ret_val, p, ret_val_len, i);
!   } else {
!     s_copy (ret_val, " ", ret_val_len, 1);
!   }
  #else
    errno = ENOSYS;
    s_copy (ret_val, " ", ret_val_len, 1);
--- 35,59 ----
  #include <errno.h>		/* for ENOSYS */
  #include "f2c.h"
  
! extern integer G77_fnum_0 (integer * lunit);
! extern void s_copy (register char *a, register char *b, ftnlen la, ftnlen lb);
! /* Character */ void
! G77_ttynam_0 (char *ret_val, ftnlen ret_val_len, integer * lunit)
  {
  #if defined (HAVE_TTYNAME)
    size_t i;
    char *p;
  
    p = ttyname (G77_fnum_0 (lunit));
!   if (p != NULL)
!     {
!       i = strlen (p);
!       s_copy (ret_val, p, ret_val_len, i);
!     }
!   else
!     {
!       s_copy (ret_val, " ", ret_val_len, 1);
!     }
  #else
    errno = ENOSYS;
    s_copy (ret_val, " ", ret_val_len, 1);
diff -Nrc3pad gcc-3.2.3/libf2c/libU77/umask_.c gcc-3.3/libf2c/libU77/umask_.c
*** gcc-3.2.3/libf2c/libU77/umask_.c	1999-09-04 15:09:19.000000000 +0000
--- gcc-3.3/libf2c/libU77/umask_.c	2002-06-01 12:38:32.000000000 +0000
*************** Boston, MA 02111-1307, USA.  */
*** 23,34 ****
  #include <sys/stat.h>
  #include "f2c.h"
  
! #ifdef KR_headers
! integer G77_umask_0 (mask)
!      integer *mask;
! #else
! integer G77_umask_0 (integer *mask)
! #endif
  {
!   return umask ((mode_t) *mask);
  }
--- 23,30 ----
  #include <sys/stat.h>
  #include "f2c.h"
  
! integer
! G77_umask_0 (integer * mask)
  {
!   return umask ((mode_t) * mask);
  }
diff -Nrc3pad gcc-3.2.3/libf2c/libU77/unlink_.c gcc-3.3/libf2c/libU77/unlink_.c
*** gcc-3.2.3/libf2c/libU77/unlink_.c	1999-09-04 15:09:19.000000000 +0000
--- gcc-3.3/libf2c/libU77/unlink_.c	2002-06-02 12:59:22.000000000 +0000
*************** Boston, MA 02111-1307, USA.  */
*** 33,55 ****
  #endif
  #include "f2c.h"
  
! #ifdef KR_headers
! void g_char ();
! 
! integer G77_unlink_0 (str, Lstr)
!      char *str; ftnlen  Lstr;
! #else
! void g_char(const char *a, ftnlen alen, char *b);
  
! integer G77_unlink_0 (const char *str, const ftnlen Lstr)
! #endif
  {
    char *buff;
-   char *bp, *blast;
    int i;
  
!   buff = malloc (Lstr+1);
!   if (buff == NULL) return -1;
    g_char (str, Lstr, buff);
    i = unlink (buff);
    free (buff);
--- 33,49 ----
  #endif
  #include "f2c.h"
  
! void g_char (const char *a, ftnlen alen, char *b);
  
! integer
! G77_unlink_0 (const char *str, const ftnlen Lstr)
  {
    char *buff;
    int i;
  
!   buff = malloc (Lstr + 1);
!   if (buff == NULL)
!     return -1;
    g_char (str, Lstr, buff);
    i = unlink (buff);
    free (buff);
diff -Nrc3pad gcc-3.2.3/libf2c/libU77/Version.c gcc-3.3/libf2c/libU77/Version.c
*** gcc-3.2.3/libf2c/libU77/Version.c	2003-04-22 00:16:27.000000000 +0000
--- gcc-3.3/libf2c/libU77/Version.c	2002-09-24 03:44:35.000000000 +0000
***************
*** 1,12 ****
! static char junk[] = "\n@(#) LIBU77 VERSION 19980709\n";
! 
! char __G77_LIBU77_VERSION__[] = "3.2.2 20030422 (release)";
! 
! #include <stdio.h>
! 
! void
! g77__uvers__ ()
! {
!   fprintf (stderr, "__G77_LIBU77_VERSION__: %s", __G77_LIBU77_VERSION__);
!   fputs (junk, stderr);
! }
--- 1 ----
! const char __LIBU77_VERSION__[] = "@(#) LIBU77 VERSION 19980709\n";
diff -Nrc3pad gcc-3.2.3/libf2c/libU77/vxtidate_.c gcc-3.3/libf2c/libU77/vxtidate_.c
*** gcc-3.2.3/libf2c/libU77/vxtidate_.c	2001-09-30 22:06:23.000000000 +0000
--- gcc-3.3/libf2c/libU77/vxtidate_.c	2002-06-05 19:07:11.000000000 +0000
*************** Boston, MA 02111-1307, USA.  */
*** 38,71 ****
  /* VMS style: */
  
  /* Subroutine */
! #ifdef KR_headers
! int G77_vxtidate_y2kbug_0 (m, d, y)
!      integer *y, *m, *d;
! #else
! int G77_vxtidate_y2kbug_0 (integer *m, integer *d, integer *y)
! #endif
  {
    struct tm *lt;
    time_t tim;
!   tim = time(NULL);
!   lt = localtime(&tim);
    *y = lt->tm_year % 100;
!   *m = lt->tm_mon+1;
    *d = lt->tm_mday;
    return 0;
  }
  
  #ifdef PIC
  extern const char *G77_Non_Y2K_Compliance_Message;
! #  ifdef KR_headers
! int G77_vxtidate_y2kbuggy_0 (m, d, y)
!      integer *y, *m, *d;
! #  else
! int G77_vxtidate_y2kbuggy_0 (integer *m, integer *d, integer *y)
! #  endif
  {
!   extern int G77_abort_0();
    fprintf (stderr, "%s\n", G77_Non_Y2K_Compliance_Message);
!   G77_abort_0();
  }
  #endif
--- 38,65 ----
  /* VMS style: */
  
  /* Subroutine */
! int
! G77_vxtidate_y2kbug_0 (integer * m, integer * d, integer * y)
  {
    struct tm *lt;
    time_t tim;
!   tim = time (NULL);
!   lt = localtime (&tim);
    *y = lt->tm_year % 100;
!   *m = lt->tm_mon + 1;
    *d = lt->tm_mday;
    return 0;
  }
  
  #ifdef PIC
  extern const char *G77_Non_Y2K_Compliance_Message;
! int
! G77_vxtidate_y2kbuggy_0 (integer * m __attribute__ ((__unused__)),
! 			 integer * d __attribute__ ((__unused__)),
! 			 integer * y __attribute__ ((__unused__)))
  {
!   extern int G77_abort_0 ();
    fprintf (stderr, "%s\n", G77_Non_Y2K_Compliance_Message);
!   G77_abort_0 ();
  }
  #endif
diff -Nrc3pad gcc-3.2.3/libf2c/libU77/vxttime_.c gcc-3.3/libf2c/libU77/vxttime_.c
*** gcc-3.2.3/libf2c/libU77/vxttime_.c	2001-01-23 23:20:30.000000000 +0000
--- gcc-3.3/libf2c/libU77/vxttime_.c	2002-06-05 19:07:11.000000000 +0000
*************** Boston, MA 02111-1307, USA.  */
*** 39,55 ****
  #include "f2c.h"
  
  /* Subroutine */
! #ifdef KR_headers
! void G77_vxttime_0 (chtime, Lchtime)
!      char chtime[8];
!      ftnlen Lchtime;
! #else
! void G77_vxttime_0 (char chtime[8], const ftnlen Lchtime)
! #endif
  {
    time_t tim;
    char *ctim;
!   tim = time(NULL);
    ctim = ctime (&tim);
!   strncpy (chtime, ctim+11, 8);
  }
--- 39,51 ----
  #include "f2c.h"
  
  /* Subroutine */
! void
! G77_vxttime_0 (char chtime[8],
! 	       const ftnlen Lchtime __attribute__ ((__unused__)))
  {
    time_t tim;
    char *ctim;
!   tim = time (NULL);
    ctim = ctime (&tim);
!   strncpy (chtime, ctim + 11, 8);
  }
diff -Nrc3pad gcc-3.2.3/libf2c/Makefile.in gcc-3.3/libf2c/Makefile.in
*** gcc-3.2.3/libf2c/Makefile.in	2003-01-28 21:52:30.000000000 +0000
--- gcc-3.3/libf2c/Makefile.in	2003-01-28 01:45:12.000000000 +0000
***************
*** 19,25 ****
  #the Free Software Foundation, 59 Temple Place - Suite 330, Boston, MA
  #02111-1307, USA.
  
! SHELL = /bin/sh
  MAKEOVERRIDES=
  .NOEXPORTS:
  
--- 19,26 ----
  #the Free Software Foundation, 59 Temple Place - Suite 330, Boston, MA
  #02111-1307, USA.
  
! SHELL = @SHELL@
! PWD = $${PWDCMD-pwd}
  MAKEOVERRIDES=
  .NOEXPORTS:
  
*************** INSTALL_DATA = @INSTALL_DATA@
*** 66,71 ****
--- 67,73 ----
  
  LIBTOOL = @LIBTOOL@
  CC = @CC@
+ WARN_CFLAGS = -W -Wall
  CFLAGS = @CFLAGS@
  AR = @AR@
  RANLIB = @RANLIB@
*************** FLAGS_TO_PASS= \
*** 76,81 ****
--- 78,84 ----
  	CC='$(CC)' \
  	LD='$(LD)' \
  	LIBTOOL='$(LIBTOOL)' \
+ 	WARN_CFLAGS='$(WARN_CFLAGS)' \
  	CFLAGS='$(CFLAGS)' \
  	CPPFLAGS='$(CPPFLAGS)' \
  	DESTDIR='$(DESTDIR)' \
*************** s-libe77: f2cext.c
*** 173,179 ****
  	do \
  	  echo $${name}; \
  	  $(LIBTOOL) --mode=compile $(CC) -c -I. -I$(srcdir) -I../../include \
! 	    $(CPPFLAGS) $(CFLAGS) -DL$${name} $(srcdir)/f2cext.c \
  	    -o libE77/L$${name}.lo ; \
  	  if [ $$? -eq 0 ] ; then true; else exit 1; fi; \
  	  echo libE77/L$${name}.lo >> $@.T; \
--- 176,182 ----
  	do \
  	  echo $${name}; \
  	  $(LIBTOOL) --mode=compile $(CC) -c -I. -I$(srcdir) -I../../include \
! 	    $(CPPFLAGS) $(WARN_CFLAGS) $(CFLAGS) -DL$${name} $(srcdir)/f2cext.c \
  	    -o libE77/L$${name}.lo ; \
  	  if [ $$? -eq 0 ] ; then true; else exit 1; fi; \
  	  echo libE77/L$${name}.lo >> $@.T; \
*************** rebuilt: configure
*** 256,263 ****
          installcheck installdirs all-unilib
  
  subdir_do:
! 	@rootpre=`pwd`/; export rootpre; \
! 	srcrootpre=`cd $(srcdir); pwd`/; export srcrootpre; \
  	for i in .. $(DODIRS); do \
  	  if [ x$$i != x.. ]; then \
  	    if [ -f ./$$i/Makefile ]; then \
--- 259,266 ----
          installcheck installdirs all-unilib
  
  subdir_do:
! 	@rootpre=`${PWD}`/; export rootpre; \
! 	srcrootpre=`cd $(srcdir); ${PWD}`/; export srcrootpre; \
  	for i in .. $(DODIRS); do \
  	  if [ x$$i != x.. ]; then \
  	    if [ -f ./$$i/Makefile ]; then \