mirror of
git://gcc.gnu.org/git/gcc.git
synced 2024-12-22 12:40:04 +08:00
root.texi, [...]: Remove non-historical references to egcs/EGCS.
2000-11-05 Toon Moene <toon@moene.indiv.nluug.nl> * root.texi, news.texi, g77install.texi, g77.texi, bugs.texi: Remove non-historical references to egcs/EGCS. From-SVN: r37266
This commit is contained in:
parent
436a88a6d4
commit
35f93a1e2d
@ -1,3 +1,8 @@
|
||||
2000-11-05 Toon Moene <toon@moene.indiv.nluug.nl>
|
||||
|
||||
* root.texi, news.texi, g77install.texi, g77.texi, bugs.texi:
|
||||
Remove non-historical references to egcs/EGCS.
|
||||
|
||||
2000-11-05 Joseph S. Myers <jsm28@cam.ac.uk>
|
||||
|
||||
* Make-lang.in: Remove f77.distdir and f/INSTALL.
|
||||
|
@ -77,7 +77,7 @@ most consistent with the @code{g77} product in that version.
|
||||
|
||||
An online, ``live'' version of this document
|
||||
(derived directly from the mainline, development version
|
||||
of @code{g77} within @code{egcs})
|
||||
of @code{g77} within @code{gcc})
|
||||
is available via
|
||||
@uref{http://www.gnu.org/software/gcc/onlinedocs/g77_bugs.html}.
|
||||
Follow the ``Known Bugs'' link.
|
||||
|
@ -751,7 +751,7 @@ So far, this has resulted in the three, somewhat
|
||||
experimental, options added by @code{g77} to the @code{gcc}
|
||||
compiler and its back end.
|
||||
|
||||
(These, in turn, have made their way into the @code{egcs}
|
||||
(These, in turn, had made their way into the @code{egcs}
|
||||
version of the compiler, and do not exist in @code{gcc}
|
||||
version 2.8 or versions of @code{g77} based on that version
|
||||
of @code{gcc}.)
|
||||
@ -1658,7 +1658,7 @@ This option is obsolete in @code{egcs}
|
||||
as of version 1.1.
|
||||
The effect is instead achieved
|
||||
by the @code{lang_init_options} routine
|
||||
in @file{egcs/gcc/f/com.c}.
|
||||
in @file{gcc/gcc/f/com.c}.
|
||||
|
||||
@cindex consistency checks
|
||||
@cindex internal consistency checks
|
||||
@ -10235,13 +10235,9 @@ introduced in version 0.5.20 and
|
||||
were withdrawn as of @code{g77} version 0.5.23
|
||||
due to their not being supported by @code{gcc} version 2.8.
|
||||
|
||||
These options, which control the assumptions regarding aliasing
|
||||
These options control the assumptions regarding aliasing
|
||||
(overlapping) of writes and reads to main memory (core) made
|
||||
by the @code{gcc} back end,
|
||||
might well be added back (in some form) in a future version
|
||||
of @code{gcc}.
|
||||
|
||||
However, these options @emph{are} supported by @code{egcs}.
|
||||
by the @code{gcc} back end.
|
||||
|
||||
The information below still is useful, but applies to
|
||||
only those versions of @code{g77} that support the
|
||||
@ -13951,8 +13947,8 @@ How to do this depends on the version of @code{g77}:
|
||||
|
||||
@table @code
|
||||
@item G77 0.5.24 (EGCS 1.1)
|
||||
@itemx G77 0.5.25 (EGCS 1.2)
|
||||
Change the @code{lang_init_options} routine in @file{egcs/gcc/f/com.c}.
|
||||
@itemx G77 0.5.25 (EGCS 1.2 - which became GCC 2.95)
|
||||
Change the @code{lang_init_options} routine in @file{gcc/gcc/f/com.c}.
|
||||
|
||||
(Note that these versions of @code{g77}
|
||||
perform internal consistency checking automatically
|
||||
@ -15061,7 +15057,7 @@ the problem by editing $@{srcdir@}/proj.c, and what else to do.
|
||||
this problem,
|
||||
which occurs only in releases of @code{g77}
|
||||
based on @code{gcc}.
|
||||
(It does not occur in @code{egcs}.)
|
||||
(It did not occur in @code{egcs}.)
|
||||
|
||||
On AIX 4.1, @code{g77} might not build with the native (non-GNU) tools
|
||||
due to a linker bug in coping with the @samp{-bbigtoc} option which
|
||||
|
@ -51,10 +51,6 @@ The following information describes how to install @code{g77}.
|
||||
|
||||
@clear OMIT-FSF-G77
|
||||
|
||||
@ifset EGCS-G77
|
||||
@set OMIT-FSF-G77
|
||||
@end ifset
|
||||
|
||||
@ifset GCC-G77
|
||||
@set OMIT-FSF-G77
|
||||
@end ifset
|
||||
@ -593,7 +589,6 @@ be fixed in a future version of @code{gcc}.
|
||||
@cindex AIX
|
||||
A linker bug on some versions of AIX 4.1 might prevent building
|
||||
when @code{g77} is built within @code{gcc}.
|
||||
It might also occur when building within @code{egcs}.
|
||||
@ifset DOC-G77
|
||||
@xref{LINKFAIL}.
|
||||
@end ifset
|
||||
|
@ -97,7 +97,9 @@ Note that two variants of @code{g77} are tracked below.
|
||||
The @code{egcs} variant is described vis-a-vis
|
||||
previous versions of @code{egcs} and/or
|
||||
an official FSF version,
|
||||
as appropriate.
|
||||
as appropriate. Note that all such variants are now
|
||||
obsolete - the information is retained here only for
|
||||
its historical value.
|
||||
|
||||
Therefore, @code{egcs} versions sometimes have multiple listings
|
||||
to help clarify how they differ from other versions,
|
||||
@ -144,7 +146,7 @@ of news about previous @code{g77} versions up-to-date.
|
||||
@ifclear USERVISONLY
|
||||
An online, ``live'' version of this document
|
||||
(derived directly from the mainline, development version
|
||||
of @code{g77} within @code{egcs})
|
||||
of @code{g77} within @code{gcc})
|
||||
is available at
|
||||
@uref{http://www.gnu.org/software/gcc/onlinedocs/g77_news.html}.
|
||||
@end ifclear
|
||||
|
@ -1,11 +1,10 @@
|
||||
@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 egcs),
|
||||
@c (e.g. a release branch in the CVS repository for gcc),
|
||||
@c clear this and set the version information correctly.
|
||||
@set DEVELOPMENT
|
||||
@set version-g77 0.5.25
|
||||
@set version-egcs 1.2
|
||||
@set version-gcc 2.95
|
||||
@set version-gcc 2.97
|
||||
|
||||
@c GCC-G77 indicates this is the GCC (2.95 or later) version of g77.
|
||||
@set GCC-G77
|
||||
@ -18,8 +17,8 @@
|
||||
|
||||
@set email-general gcc@@gcc.gnu.org
|
||||
@set email-bugs gcc-bugs@@gcc.gnu.org or bug-gcc@@gnu.org
|
||||
@set path-g77 egcs/gcc/f
|
||||
@set path-libf2c egcs/libf2c
|
||||
@set path-g77 gcc/gcc/f
|
||||
@set path-libf2c gcc/libf2c
|
||||
|
||||
@ifset GCC-G77
|
||||
@set which-g77 GCC-@value{version-gcc}
|
||||
|
Loading…
Reference in New Issue
Block a user