Commit 51e9a60c by Eric Botcazou Committed by Eric Botcazou

re PR target/16007 (Use of static template members results in broken executables)

	PR target/16007
	* doc/install.texi (*-*-solaris2*): Mention potential problem
	with Sun assembler + GNU linker and C++ programs.
	Document status of binutils 2.15 release.

From-SVN: r88595
parent 7e0b5752
2004-10-06 Eric Botcazou <ebotcazou@libertysurf.fr>
PR target/16007
* doc/install.texi (*-*-solaris2*): Mention potential problem
with Sun assembler + GNU linker and C++ programs.
Document status of binutils 2.15 release.
2004-10-06 Jan Hubicka <jh@suse.cz>
* cse.c (cse_main): Kill push/pop context.
......
......@@ -3478,8 +3478,19 @@ have @file{/usr/xpg4/bin} in your @env{PATH}, we recommend that you place
@file{/usr/bin} before @file{/usr/xpg4/bin} for the duration of the build.
All releases of GNU binutils prior to 2.11.2 have known bugs on this
platform. We recommend the use of GNU binutils 2.11.2 or the vendor
tools (Sun @command{as}, Sun @command{ld}).
platform. We recommend the use of GNU binutils 2.11.2 or later, or the
vendor tools (Sun @command{as}, Sun @command{ld}). Note that your mileage
may vary if you use a combination of the GNU tools and the Sun tools: while
the combination GNU @command{as} + Sun @command{ld} should reasonably work,
the reverse combination Sun @command{as} + GNU @command{ld} is known to
cause memory corruption at runtime in some cases for C++ programs.
The stock GNU binutils 2.15 release is broken on this platform because of a
single bug. It has been fixed on the 2.15 branch in the CVS repository.
You can obtain a working version by checking out the binutils-2_15-branch
from the CVS repository or applying the patch
`http://sources.redhat.com/ml/binutils-cvs/2004-09/msg00036.html' to the
release.
Sun bug 4296832 turns up when compiling X11 headers with GCC 2.95 or
newer: @command{g++} will complain that types are missing. These headers assume
......
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