This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Patch to update more version numbers on branch
- To: <gcc-patches at gcc dot gnu dot org>
- Subject: Patch to update more version numbers on branch
- From: "Joseph S. Myers" <jsm28 at cam dot ac dot uk>
- Date: Mon, 19 Feb 2001 19:24:50 +0000 (GMT)
This patch to the branch updates to 3.0 various version numbers not
previously updated. OK to commit to branch only? (A separate patch
will be sent to update all version numbers on the mainline. Separate
patches will also be sent to update last-modified dates in manuals.)
2001-02-19 Joseph S. Myers <jsm28@cam.ac.uk>
* REAMDE, cpp.texi, gcc.texi: Update version number to 3.0
* cpp.1, gcov.1, gcc.1: Regenerate.
gcc/f/ChangeLog:
2001-02-19 Joseph S. Myers <jsm28@cam.ac.uk>
* root.texi: Clear DEVELOPMENT. Update GCC version number to 3.0.
* BUGS, NEWS: Regenerate.
Index: README
===================================================================
RCS file: /cvs/gcc/gcc/gcc/README,v
retrieving revision 1.8
diff -u -r1.8 README
--- README 1999/07/28 19:50:47 1.8
+++ README 2001/02/19 19:09:42
@@ -1,4 +1,4 @@
-This directory contains the GNU Compiler Collection (GCC) version 2.96.
+This directory contains the GNU Compiler Collection (GCC) version 3.0.
It includes all of the support for compiling C, C++, Objective C, Fortran,
Java, and Chill.
Index: cpp.texi
===================================================================
RCS file: /cvs/gcc/gcc/gcc/cpp.texi,v
retrieving revision 1.46.2.1
diff -u -r1.46.2.1 cpp.texi
--- cpp.texi 2001/02/14 10:02:35 1.46.2.1
+++ cpp.texi 2001/02/19 19:09:43
@@ -43,7 +43,7 @@
@c @finalout
@title The C Preprocessor
@subtitle Last revised January 2001
-@subtitle for GCC version 2
+@subtitle for GCC version 3
@author Richard M. Stallman
@page
@vskip 2pc
Index: gcc.texi
===================================================================
RCS file: /cvs/gcc/gcc/gcc/gcc.texi,v
retrieving revision 1.75.2.1
diff -u -r1.75.2.1 gcc.texi
--- gcc.texi 2001/02/17 10:25:01 1.75.2.1
+++ gcc.texi 2001/02/19 19:09:44
@@ -170,13 +170,13 @@
@sp 1
@c The version number appears five times more in this file.
-@center for gcc-2.97
+@center for gcc-3.0
@page
@vskip 0pt plus 1filll
Copyright @copyright{} 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1998,
1999, 2000, 2001 Free Software Foundation, Inc.
@sp 2
-For GCC Version 2.97@*
+For GCC Version 3.0@*
@sp 1
Published by the Free Software Foundation @*
59 Temple Place - Suite 330@*
@@ -213,19 +213,19 @@
@ifset USING
This manual documents how to run, install and port the GNU
compiler, as well as its new features and incompatibilities, and how to
-report bugs. It corresponds to GCC version 2.97.
+report bugs. It corresponds to GCC version 3.0.
@end ifset
@end ifset
@ifclear INTERNALS
This manual documents how to run and install the GNU compiler,
as well as its new features and incompatibilities, and how to report
-bugs. It corresponds to GCC version 2.97.
+bugs. It corresponds to GCC version 3.0.
@end ifclear
@ifclear USING
This manual documents how to port the GNU compiler,
as well as its new features and incompatibilities, and how to report
-bugs. It corresponds to GCC version 2.97.
+bugs. It corresponds to GCC version 3.0.
@end ifclear
@menu
Index: gcov.1
===================================================================
RCS file: /cvs/gcc/gcc/gcc/gcov.1,v
retrieving revision 1.2
diff -u -r1.2 gcov.1
--- gcov.1 2001/01/03 20:15:01 1.2
+++ gcov.1 2001/02/19 19:09:44
@@ -1,5 +1,5 @@
.\" Automatically generated by Pod::Man version 1.1
-.\" Wed Jan 3 20:06:14 2001
+.\" Mon Feb 19 19:07:09 2001
.\"
.\" Standard preamble:
.\" ======================================================================
@@ -138,7 +138,7 @@
.\" ======================================================================
.\"
.IX Title "GCOV 1"
-.TH GCOV 1 "gcc-2.97" "2001-01-03" "GNU"
+.TH GCOV 1 "gcc-3.0" "2001-02-19" "GNU"
.UC
.SH "NAME"
gcov \- coverage testing tool
Index: cpp.1
===================================================================
RCS file: /cvs/gcc/gcc/gcc/cpp.1,v
retrieving revision 1.10
diff -u -r1.10 cpp.1
--- cpp.1 2001/01/24 19:47:47 1.10
+++ cpp.1 2001/02/19 19:09:45
@@ -1,5 +1,5 @@
.\" Automatically generated by Pod::Man version 1.1
-.\" Wed Jan 24 19:43:25 2001
+.\" Mon Feb 19 19:08:02 2001
.\"
.\" Standard preamble:
.\" ======================================================================
@@ -138,7 +138,7 @@
.\" ======================================================================
.\"
.IX Title "CPP 1"
-.TH CPP 1 "gcc-2.97" "2001-01-24" "GNU"
+.TH CPP 1 "gcc-3.0" "2001-02-19" "GNU"
.UC
.SH "NAME"
cpp \- The C Preprocessor
@@ -385,6 +385,36 @@
.IX Item "-Wtraditional"
Warn about certain constructs that behave differently in traditional and
\&\s-1ISO\s0 C.
+.RS 4
+.Ip "\(bu" 4
+Macro parameters that appear within string literals in the macro body.
+In traditional C macro replacement takes place within string literals,
+but does not in \s-1ISO\s0 C.
+.Ip "\(bu" 4
+In traditional C, some preprocessor directives did not exist.
+Traditional preprocessors would only consider a line to be a directive
+if the \fB#\fR appeared in column 1 on the line. Therefore
+\&\fB\-Wtraditional\fR warns about directives that traditional C
+understands but would ignore because the \fB#\fR does not appear as the
+first character on the line. It also suggests you hide directives like
+\&\fB#pragma\fR not understood by traditional C by indenting them. Some
+traditional implementations would not recognise \fB#elif\fR, so it
+suggests avoiding it altogether.
+.Ip "\(bu" 4
+A function-like macro that appears without arguments.
+.Ip "\(bu" 4
+The unary plus operator.
+.Ip "\(bu" 4
+The `U' integer constant suffix. (Traditonal C does support the `L'
+suffix on integer constants.) Note, these suffixes appear in macros
+defined in the system headers of most modern systems, e.g. the _MIN/_MAX
+macros in limits.h. Use of these macros can lead to spurious warnings
+as they do not necessarily reflect whether the code in question is any
+less portable to traditional C given that suitable backup definitions
+are provided.
+.RE
+.RS 4
+.RE
.Ip "\fB\-Wundef\fR" 4
.IX Item "-Wundef"
Warn if an undefined identifier is evaluated in an \fB#if\fR directive.
@@ -510,7 +540,10 @@
file. The preprocessor outputs one \f(CW\*(C`make\*(C'\fR rule containing the
object file name for that source file, a colon, and the names of all the
included files, including those coming from \fB\-include\fR or
-\&\fB\-imacros\fR command line options. If there are many included files
+\&\fB\-imacros\fR command line options. Unless specified explicitly (with
+\&\fB\-MT\fR or \fB\-MQ\fR), the object file name consists of the basename
+of the source file with any suffix replaced with object file suffix.
+If there are many included files
then the rule is split into several lines using \fB\e\fR\-newline.
.Ip "\fB\-MM\fR" 4
.IX Item "-MM"
Index: gcc.1
===================================================================
RCS file: /cvs/gcc/gcc/gcc/gcc.1,v
retrieving revision 1.20
diff -u -r1.20 gcc.1
--- gcc.1 2001/01/24 19:47:47 1.20
+++ gcc.1 2001/02/19 19:09:50
@@ -1,5 +1,5 @@
.\" Automatically generated by Pod::Man version 1.1
-.\" Wed Jan 24 19:43:11 2001
+.\" Mon Feb 19 19:07:27 2001
.\"
.\" Standard preamble:
.\" ======================================================================
@@ -138,7 +138,7 @@
.\" ======================================================================
.\"
.IX Title "GCC 1"
-.TH GCC 1 "gcc-2.97" "2001-01-24" "GNU"
+.TH GCC 1 "gcc-3.0" "2001-02-19" "GNU"
.UC
.SH "NAME"
gcc \- \s-1GNU\s0 project C and \*(C+ compiler
@@ -217,9 +217,9 @@
\&\-fhuge-objects \-fno-implicit-templates
\&\-fno-implicit-inline-templates
\&\-fno-implement-inlines \-fms-extensions
-\&\-fname-mangling-version-\fR\fIn\fR \fB\-fno-operator-names
+\&\-fno-operator-names
\&\-fno-optional-diags \-fpermissive
-\&\-frepo \-fno-rtti \-fsquangle \-ftemplate-depth-\fR\fIn\fR
+\&\-frepo \-fno-rtti \-ftemplate-depth-\fR\fIn\fR
\&\fB\-fuse-cxa-atexit \-fvtable-thunks \-nostdinc++
\&\-fno-default-inline \-Wctor-dtor-privacy
\&\-Wnon-virtual-dtor \-Wreorder
@@ -261,8 +261,8 @@
\&\-Wstrict-prototypes \-Wtraditional\fR
.Ip "\fIDebugging Options\fR" 4
.IX Item "Debugging Options"
-\&\fB\-a \-ax \-d\fR\fIletters\fR \fB\-fdump-unnumbered \-fdump-translation-unit-\fR\fIfile\fR
-\&\fB\-fpretend-float \-fprofile-arcs \-ftest-coverage
+\&\fB\-a \-ax \-d\fR\fIletters\fR \fB\-fdump-unnumbered \-fdump-translation-unit=\fR\fIfile\fR
+\&\fB\-fdump-class-layout=\fR\fIfile\fR \fB\-fpretend-float \-fprofile-arcs \-ftest-coverage
\&\-g \-g\fR\fIlevel\fR \fB\-gcoff \-gdwarf \-gdwarf-1 \-gdwarf-1+ \-gdwarf-2
\&\-ggdb \-gstabs \-gstabs+ \-gxcoff \-gxcoff+
\&\-p \-pg \-print-file-name=\fR\fIlibrary\fR \fB\-print-libgcc-file-name
@@ -869,7 +869,7 @@
.Ip "\fBiso9899:1999\fR" 4
.IX Item "iso9899:1999"
\&\s-1ISO\s0 C99. Note that this standard is not yet fully supported; see
-<\fBhttp://gcc.gnu.org/c99status.html\fR> for more information.
+<\fBhttp://gcc.gnu.org/gcc-3.0/c99status.html\fR> for more information.
.Ip "\fBc89\fR" 4
.IX Item "c89"
same as \fB\-std=iso9899:1990\fR
@@ -1246,19 +1246,6 @@
.IX Item "-fms-extensions"
Disable pedantic warnings about constructs used in \s-1MFC\s0, such as implicit
int and getting a pointer to member function via non-standard syntax.
-.Ip "\fB\-fname-mangling-version-\fR\fIn\fR" 4
-.IX Item "-fname-mangling-version-n"
-Control the way in which names are mangled. Version 0 is compatible
-with versions of g++ before 2.8. Version 1 is the default. Version 1
-will allow correct mangling of function templates. For example,
-version 0 mangling does not mangle foo<int, double> and foo<int, char>
-given this declaration:
-.Sp
-.Vb 1
-\& template <class T, class U> void foo(T t);
-.Ve
-Like all options that change the \s-1ABI\s0, all \*(C+ code, \fIincluding
-libgcc\fR must be built with the same setting of this option.
.Ip "\fB\-fno-operator-names\fR" 4
.IX Item "-fno-operator-names"
Do not treat the operator name keywords \f(CW\*(C`and\*(C'\fR, \f(CW\*(C`bitand\*(C'\fR,
@@ -1287,21 +1274,6 @@
of the language, you can save some space by using this flag. Note that
exception handling uses the same information, but it will generate it as
needed.
-.Ip "\fB\-fsquangle\fR" 4
-.IX Item "-fsquangle"
-.PD 0
-.Ip "\fB\-fno-squangle\fR" 4
-.IX Item "-fno-squangle"
-.PD
-\&\fB\-fsquangle\fR will enable a compressed form of name mangling for
-identifiers. In particular, it helps to shorten very long names by recognizing
-types and class names which occur more than once, replacing them with special
-short \s-1ID\s0 codes. This option also requires any \*(C+ libraries being used to
-be compiled with this option as well. The compiler has this disabled (the
-equivalent of \fB\-fno-squangle\fR) by default.
-.Sp
-Like all options that change the \s-1ABI\s0, all \*(C+ code, \fIincluding
-libgcc.a\fR must be built with the same setting of this option.
.Ip "\fB\-ftemplate-depth-\fR\fIn\fR" 4
.IX Item "-ftemplate-depth-n"
Set the maximum instantiation depth for template classes to \fIn\fR.
@@ -1940,11 +1912,33 @@
Warn about certain constructs that behave differently in traditional and
\&\s-1ISO\s0 C.
.RS 4
+.Ip "\(bu" 4
+Macro parameters that appear within string literals in the macro body.
+In traditional C macro replacement takes place within string literals,
+but does not in \s-1ISO\s0 C.
+.Ip "\(bu" 4
+In traditional C, some preprocessor directives did not exist.
+Traditional preprocessors would only consider a line to be a directive
+if the \fB#\fR appeared in column 1 on the line. Therefore
+\&\fB\-Wtraditional\fR warns about directives that traditional C
+understands but would ignore because the \fB#\fR does not appear as the
+first character on the line. It also suggests you hide directives like
+\&\fB#pragma\fR not understood by traditional C by indenting them. Some
+traditional implementations would not recognise \fB#elif\fR, so it
+suggests avoiding it altogether.
.Ip "\(bu" 4
-Macro arguments occurring within string constants in the macro body.
-These would substitute the argument in traditional C, but are part of
-the constant in \s-1ISO\s0 C.
+A function-like macro that appears without arguments.
+.Ip "\(bu" 4
+The unary plus operator.
.Ip "\(bu" 4
+The `U' integer constant suffix, or the `F' or `L' floating point
+constant suffixes. (Traditonal C does support the `L' suffix on integer
+constants.) Note, these suffixes appear in macros defined in the system
+headers of most modern systems, e.g. the _MIN/_MAX macros in limits.h.
+Use of these macros can lead to spurious warnings as they do not
+necessarily reflect whether the code in question is any less portable to
+traditional C given that suitable backup definitions are provided.
+.Ip "\(bu" 4
A function declared external in one block and then used after the end of
the block.
.Ip "\(bu" 4
@@ -1960,10 +1954,6 @@
.Ip "\(bu" 4
Usage of \s-1ISO\s0 string concatenation is detected.
.Ip "\(bu" 4
-A function macro appears without arguments.
-.Ip "\(bu" 4
-The unary plus operator.
-.Ip "\(bu" 4
Initialization of automatic aggregates.
.Ip "\(bu" 4
Identifier conflicts with labels. Traditional C lacks a separate
@@ -1974,14 +1964,6 @@
user code appears conditioned on e.g. \f(CW\*(C`_\|_STDC_\|_\*(C'\fR to avoid missing
initializer warnings and relies on default initialization to zero in the
traditional C case.
-.Ip "\(bu" 4
-The `U' integer constant suffix, or the `F' or `L' floating point
-constant suffixes. (Traditonal C does support the `L' suffix on integer
-constants.) Note, these suffixes appear in macros defined in the system
-headers of most modern systems, e.g. the _MIN/_MAX macros in limits.h.
-Use of these macros can lead to spurious warnings as they do not
-necessarily reflect whether the code in question is any less portable to
-traditional C given that suitable backup definitions are provided.
.RE
.RS 4
.RE
@@ -2572,10 +2554,18 @@
numbers and line number note output. This makes it more feasible to
use diff on debugging dumps for compiler invocations with different
options, in particular with and without \-g.
-.Ip "\fB\-fdump-translation-unit-\fR\fIfile\fR \fB(C and \*(C+ only)\fR" 4
-.IX Item "-fdump-translation-unit-file (C and only)"
+.Ip "\fB\-fdump-translation-unit=\fR\fIfile\fR \fB(C and \*(C+ only)\fR" 4
+.IX Item "-fdump-translation-unit=file (C and only)"
Dump a representation of the tree structure for the entire translation
unit to \fIfile\fR.
+.Ip "\fB\-fdump-class_layout=\fR\fIfile\fR \fB(\*(C+ only)\fR" 4
+.IX Item "-fdump-class_layout=file ( only)"
+.PD 0
+.Ip "\fB\-fdump-class_layout (\*(C+ only)\fR" 4
+.IX Item "-fdump-class_layout ( only)"
+.PD
+Dump a representation of each class's heirarchy to \fIfile\fR, or
+\&\f(CW\*(C`stderr\*(C'\fR if not specified.
.Ip "\fB\-fpretend-float\fR" 4
.IX Item "-fpretend-float"
When running a cross-compiler, pretend that the target machine uses the
@@ -3220,8 +3210,10 @@
suitable for \f(CW\*(C`make\*(C'\fR describing the dependencies of the main source
file. The preprocessor outputs one \f(CW\*(C`make\*(C'\fR rule containing the
object file name for that source file, a colon, and the names of all the
-included files. If there are many included files then the rule is split
-into several lines using \fB\e\fR\-newline.
+included files. Unless overridden explicitly, the object file name
+consists of the basename of the source file with any suffix replaced with
+object file suffix. If there are many included files then the
+rule is split into several lines using \fB\e\fR\-newline.
.Sp
\&\fB\-M\fR implies \fB\-E\fR.
.Ip "\fB\-MM\fR" 4
@@ -3528,11 +3520,16 @@
across different shared libraries. In that case, each of the libraries
as well as the application itself should use the shared \fIlibgcc\fR.
.Sp
-At present the \s-1GCC\s0 driver makes no attempt to recognize the situations
-in which the shared \fIlibgcc\fR should be used, and defaults to using
-the static \fIlibgcc\fR always. This will likely change in the future,
-at which time \fB\-static-libgcc\fR becomes useful as a means for
-overriding \s-1GCC\s0's choice.
+Therefore, whenever you specify the \fB\-shared\fR option, the \s-1GCC\s0
+driver automatically adds \fB\-shared-libgcc\fR, unless you explicitly
+specify \fB\-static-libgcc\fR. The G++ driver automatically adds
+\&\fB\-shared-libgcc\fR when you build a main executable as well because
+for \*(C+ programs that is typically the right thing to do.
+(Exception-handling will not work reliably otherwise.)
+.Sp
+However, when linking a main executable written in C, you must
+explicitly say \fB\-shared-libgcc\fR if you want to use the shared
+\&\fIlibgcc\fR.
.Ip "\fB\-symbolic\fR" 4
.IX Item "-symbolic"
Bind references to global symbols when building a shared object. Warn
@@ -3569,8 +3566,10 @@
Add the directory \fIdir\fR to the head of the list of directories to be
searched for header files. This can be used to override a system header
file, substituting your own version, since these directories are
-searched before the system header file directories. If you use more
-than one \fB\-I\fR option, the directories are scanned in left-to-right
+searched before the system header file directories. However, you should
+not use this option to add directories that contain vendor-supplied
+system header files (use \fB\-isystem\fR for that). If you use more than
+one \fB\-I\fR option, the directories are scanned in left-to-right
order; the standard system directories come after.
.Ip "\fB\-I-\fR" 4
.IX Item "-I-"
@@ -5970,6 +5969,8 @@
supported letters are: \f(CW\*(C`a\*(C'\fR allocate \s-1EAX\s0; \f(CW\*(C`b\*(C'\fR allocate \s-1EBX\s0;
\&\f(CW\*(C`c\*(C'\fR allocate \s-1ECX\s0; \f(CW\*(C`d\*(C'\fR allocate \s-1EDX\s0; \f(CW\*(C`S\*(C'\fR allocate \s-1ESI\s0;
\&\f(CW\*(C`D\*(C'\fR allocate \s-1EDI\s0; \f(CW\*(C`B\*(C'\fR allocate \s-1EBP\s0.
+This option is deprecated and will not be supported by future releases
+of gcc.
.Ip "\fB\-mregparm=\fR\fInum\fR" 4
.IX Item "-mregparm=num"
Control how many registers are used to pass integer arguments. By
Index: f/root.texi
===================================================================
RCS file: /cvs/gcc/gcc/gcc/f/root.texi,v
retrieving revision 1.9
diff -u -r1.9 root.texi
--- root.texi 2000/11/26 20:02:40 1.9
+++ root.texi 2001/02/19 19:09:50
@@ -2,9 +2,9 @@
@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.
-@set DEVELOPMENT
+@clear DEVELOPMENT
@set version-g77 0.5.26
-@set version-gcc 2.97
+@set version-gcc 3.0
@set email-general gcc@@gcc.gnu.org
@set email-bugs gcc-bugs@@gcc.gnu.org or bug-gcc@@gnu.org
Index: f/BUGS
===================================================================
RCS file: /cvs/gcc/gcc/gcc/f/BUGS,v
retrieving revision 1.16
diff -u -r1.16 BUGS
--- BUGS 2000/12/21 20:03:41 1.16
+++ BUGS 2001/02/19 19:09:50
@@ -2,17 +2,16 @@
`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-2.97 version of the GNU
-Fortran compiler. Copyright (C) 1995,1996,1997,1998,1999,2000 Free
-Software Foundation, Inc. You may copy, distribute, and modify it
-freely as long as you preserve this copyright notice and permission
-notice.
+ This file lists known bugs in the GCC-3.0 version of the GNU Fortran
+compiler. Copyright (C) 1995,1996,1997,1998,1999,2000 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-2.97 version of `g77'. This includes bugs that are actually in
+the GCC-3.0 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.
@@ -20,17 +19,6 @@
For information on bugs in _other_ versions of `g77', see
`gcc/gcc/f/NEWS'. There, lists of bugs fixed in various versions of
`g77' can help determine what bugs existed in prior versions.
-
- _Warning:_ The information below is still under development, and
-might not accurately reflect the `g77' code base of which it is a part.
-Efforts are made to keep it somewhat up-to-date, but they are
-particularly concentrated on any version of this information that is
-distributed as part of a _released_ `g77'.
-
- In particular, while this information is intended to apply to the
-GCC-2.97 version of `g77', only an official _release_ of that version
-is expected to contain documentation that is most consistent with the
-`g77' product in that version.
An online, "live" version of this document (derived directly from
the mainline, development version of `g77' within `gcc') is available
Index: f/NEWS
===================================================================
RCS file: /cvs/gcc/gcc/gcc/f/NEWS,v
retrieving revision 1.30
diff -u -r1.30 NEWS
--- NEWS 2000/12/21 20:03:41 1.30
+++ NEWS 2001/02/19 19:09:51
@@ -2,7 +2,7 @@
`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-2.97 version (and some other
+ This file lists news about the GCC-3.0 version (and some other
versions) of the GNU Fortran compiler. Copyright (C)
1995,1996,1997,1998,1999,2000 Free Software Foundation, Inc. You may
copy, distribute, and modify it freely as long as you preserve this
@@ -44,25 +44,6 @@
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.
-
- _Warning:_ The information below is still under development, and
-might not accurately reflect the `g77' code base of which it is a part.
-Efforts are made to keep it somewhat up-to-date, but they are
-particularly concentrated on any version of this information that is
-distributed as part of a _released_ `g77'.
-
- In particular, while this information is intended to apply to the
-GCC-2.97 version of `g77', only an official _release_ of that version
-is expected to contain documentation that is most consistent with the
-`g77' product in that version.
-
- Nevertheless, information on _previous_ releases of `g77', below, is
-likely to be more up-to-date and accurate than the equivalent
-information that accompanied those releases, assuming the last-updated
-date of the information below is later than the dates of those releases.
-
- That's due to attempts to keep this development version of news
-about previous `g77' versions up-to-date.
An online, "live" version of this document (derived directly from
the mainline, development version of `g77' within `gcc') is available at
--
Joseph S. Myers
jsm28@cam.ac.uk