Commit 52a11d15 by Joseph Myers Committed by Joseph Myers

gcc.texi: Remove more obsolete documentation of bugs and installation problems.

	* gcc.texi: Remove more obsolete documentation of bugs and
	installation problems.

From-SVN: r40735
parent a96237da
2001-03-22 Joseph S. Myers <jsm28@cam.ac.uk>
* gcc.texi: Remove more obsolete documentation of bugs and
installation problems.
2001-03-21 Kazu Hirata <kazu@hxi.com> 2001-03-21 Kazu Hirata <kazu@hxi.com>
* config/h8300/h8300.md (movsi_h8300hs): Split the 2nd alternative * config/h8300/h8300.md (movsi_h8300hs): Split the 2nd alternative
......
...@@ -166,7 +166,7 @@ instead of in the original English. ...@@ -166,7 +166,7 @@ instead of in the original English.
@sp 2 @sp 2
@center Richard M. Stallman @center Richard M. Stallman
@sp 3 @sp 3
@center Last updated 18 March 2001 @center Last updated 22 March 2001
@sp 1 @sp 1
@c The version number appears five times more in this file. @c The version number appears five times more in this file.
...@@ -540,11 +540,6 @@ prototypes. ...@@ -540,11 +540,6 @@ prototypes.
When @samp{-pedantic-errors} is specified, GCC will incorrectly give When @samp{-pedantic-errors} is specified, GCC will incorrectly give
an error message when a function name is specified in an expression an error message when a function name is specified in an expression
involving the comma operator. involving the comma operator.
@item
Loop unrolling doesn't work properly for certain C++ programs. This is
a bug in the C++ front end. It sometimes emits incorrect debug info, and
the loop unrolling code is unable to recover from this error.
@end itemize @end itemize
@node Installation Problems @node Installation Problems
...@@ -577,17 +572,6 @@ that type mismatches occur, this could be the cause. ...@@ -577,17 +572,6 @@ that type mismatches occur, this could be the cause.
The solution is not to use such a directory for building GCC. The solution is not to use such a directory for building GCC.
@item @item
In previous versions of GCC, the @code{gcc} driver program looked for
@code{as} and @code{ld} in various places; for example, in files
beginning with @file{/usr/local/lib/gcc-}. GCC version 2 looks for
them in the directory
@file{/usr/local/lib/gcc-lib/@var{target}/@var{version}}.
Thus, to use a version of @code{as} or @code{ld} that is not the system
default, for example @code{gas} or GNU @code{ld}, you must put them in
that directory (or make links to them from that directory).
@item
Some commands executed when making the compiler may fail (return a Some commands executed when making the compiler may fail (return a
non-zero status) and be ignored by @code{make}. These failures, which non-zero status) and be ignored by @code{make}. These failures, which
are often due to files that were not found, are expected, and can safely are often due to files that were not found, are expected, and can safely
...@@ -675,25 +659,6 @@ It would be nice to extend GAS to produce the gp tables, but they are ...@@ -675,25 +659,6 @@ It would be nice to extend GAS to produce the gp tables, but they are
optional, and there should not be a warning about their absence. optional, and there should not be a warning about their absence.
@item @item
In Ultrix 4.0 on the MIPS machine, @file{stdio.h} does not work with GNU
CC at all unless it has been fixed with @code{fixincludes}. This causes
problems in building GCC. Once GCC is installed, the problems go
away.
To work around this problem, when making the stage 1 compiler, specify
this option to Make:
@example
GCC_FOR_TARGET="./xgcc -B./ -I./include"
@end example
When making stage 2 and stage 3, specify this option:
@example
CFLAGS="-g -I./include"
@end example
@item
Users have reported some problems with version 2.0 of the MIPS Users have reported some problems with version 2.0 of the MIPS
compiler tools that were shipped with Ultrix 4.1. Version 2.10 compiler tools that were shipped with Ultrix 4.1. Version 2.10
which came with Ultrix 4.2 seems to work fine. which came with Ultrix 4.2 seems to work fine.
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment