install.texi (Specific): Remove description of issue that only occurred with binutils...

	* doc/install.texi (Specific) <mips-*-*>: Remove description of
	issue that only occurred with binutils below 2.18.

From-SVN: r246079

diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index 1c490cbd806e63e1fc5ae03d846fbda9fb897db2..d3e671b9663fb8500e5a543dcc7814158ec4de71 100644 (file)
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,8 @@
+2017-03-12  Gerald Pfeifer  <gerald@pfeifer.com>
+
+       * doc/install.texi (Specific) <mips-*-*>: Remove description of
+       issue that only occurred with binutils below 2.18.
+       
 2017-03-12  Gerald Pfeifer  <gerald@pfeifer.com>
 
        * doc/install.texi (Specific) <cris-axis-elf>: No longer

diff --git a/gcc/doc/install.texi b/gcc/doc/install.texi
index 3e40b3eddd269925bf174538985d34d1df91bcf8..dced17d650f9c0ddf82dce69c24715a1de5f24d0 100644 (file)
--- a/gcc/doc/install.texi
+++ b/gcc/doc/install.texi
@@ -4122,14 +4122,6 @@ the use of break, use the @option{--with-divide=breaks}
 @command{configure} option when configuring GCC@.  The default is to
 use traps on systems that support them.
 
-The assembler from GNU binutils 2.17 and earlier has a bug in the way
-it sorts relocations for REL targets (o32, o64, EABI).  This can cause
-bad code to be generated for simple C++ programs.  Also the linker
-from GNU binutils versions prior to 2.17 has a bug which causes the
-runtime linker stubs in very large programs to
-be incorrectly generated.  GNU Binutils 2.18 and later (and snapshots
-made after Nov. 9, 2006) should be free from both of these problems.
-
 @html
 <hr />
 @end html