From 4e2e9e9b0180729138e73488f421848178b27e3f Mon Sep 17 00:00:00 2001 From: David Daney Date: Mon, 28 Jan 2008 17:01:05 +0000 Subject: [PATCH] install.texi (mips-*-*): Recommend binutils 2.18. 2008-01-28 David Daney * doc/install.texi (mips-*-*): Recommend binutils 2.18. From-SVN: r131911 --- gcc/ChangeLog | 4 ++++ gcc/doc/install.texi | 4 ++-- 2 files changed, 6 insertions(+), 2 deletions(-) diff --git a/gcc/ChangeLog b/gcc/ChangeLog index cd415a4facd..46fabaad016 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,7 @@ +2008-01-28 David Daney + + * doc/install.texi (mips-*-*): Recommend binutils 2.18. + 2008-01-28 David Daney * doc/install.texi (--disable-libgcj-bc): Reword documentation. diff --git a/gcc/doc/install.texi b/gcc/doc/install.texi index 7fed5695211..4cdc76da4e0 100644 --- a/gcc/doc/install.texi +++ b/gcc/doc/install.texi @@ -3643,8 +3643,8 @@ 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, like @file{libgcj.so}, to -be incorrectly generated. Binutils CVS snapshots and releases made -after Nov. 9, 2006 are thought to be free from both of these problems. +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
-- 2.30.2