From 9c8886127699971164cbec9baa15d7f0cdd9617a Mon Sep 17 00:00:00 2001 From: Gerald Pfeifer Date: Sun, 12 Mar 2017 17:31:00 +0000 Subject: [PATCH] install.texi (Specific): Remove description of issue that only occurred with binutils below 2.18. * doc/install.texi (Specific) : Remove description of issue that only occurred with binutils below 2.18. From-SVN: r246079 --- gcc/ChangeLog | 5 +++++ gcc/doc/install.texi | 8 -------- 2 files changed, 5 insertions(+), 8 deletions(-) diff --git a/gcc/ChangeLog b/gcc/ChangeLog index 1c490cb..d3e671b 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,5 +1,10 @@ 2017-03-12 Gerald Pfeifer + * doc/install.texi (Specific) : Remove description of + issue that only occurred with binutils below 2.18. + +2017-03-12 Gerald Pfeifer + * doc/install.texi (Specific) : No longer refer to binutils 2.11/2.12 minimum. diff --git a/gcc/doc/install.texi b/gcc/doc/install.texi index 3e40b3e..dced17d 100644 --- 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
@end html -- 2.7.4