This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug bootstrap/50237] [4.7 regression] bootstrap comparison failure for libcpp/lex.o
- From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Thu, 19 Jan 2012 16:36:56 +0000
- Subject: [Bug bootstrap/50237] [4.7 regression] bootstrap comparison failure for libcpp/lex.o
- Auto-submitted: auto-generated
- References: <bug-50237-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50237
--- Comment #42 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> 2012-01-19 16:36:56 UTC ---
> --- Comment #41 from Jakub Jelinek <jakub at gcc dot gnu.org> 2012-01-19 16:32:08 UTC ---
> It isn't mandated by the ELF spec, but if the linker doesn't do that and either
> keeps .ctors and .init_array etc. separate, or merges them but without ensuring
> the right order, ctor/dtor priorities won't work correctly.
I know. The question is if adding this gld extension to Sun ld could be
justified and if there's a spec the Oracle guys could use without
reading the gld code. Especially in Solaris 11, many gld command line
options and features have been added this name to improve compatibility.
IIRC, there are other cases where gld merges sections when Sun ld does
not.
Rainer