[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug gold/14614] New: gold 2.22 test failure (initpri3b) on gcc 4.7.2
From: |
ncahill_alt at yahoo dot com |
Subject: |
[Bug gold/14614] New: gold 2.22 test failure (initpri3b) on gcc 4.7.2 |
Date: |
Mon, 24 Sep 2012 20:37:27 +0000 |
http://sourceware.org/bugzilla/show_bug.cgi?id=14614
Bug #: 14614
Summary: gold 2.22 test failure (initpri3b) on gcc 4.7.2
Product: binutils
Version: 2.22
Status: NEW
Severity: normal
Priority: P2
Component: gold
AssignedTo: address@hidden
ReportedBy: address@hidden
CC: address@hidden
Classification: Unclassified
The test initpri3b for the gold linker fails for me when built with gcc 4.7.2.
GCC 4.7.1, though, works.
I reported this to GCC, which can be seen here:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54671
The question put to me was, who needs the --no-ctors-in-init-array option when
gcc was configured against a binutils that by default placed constructors in
the .init_array section? If it is needed, a configure option could be added to
gcc to disable the new default behaviour that deprecates this
--no-ctors-in-init-array functionality.
I hope in fact that this is not needed, and the initpri3b test can be given a
message or be ran only when on a system without init-array support, thereby
assuming that only the system default needs to be tested.
But if this is not the case, then please follow up with gcc for the necessary
addition of a configure option.
At the moment, the test fails without explanation, which is a bit
disconcerting.
Thank you.
Neil.
PS. Please see the gcc bug report for more information.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Bug gold/14614] New: gold 2.22 test failure (initpri3b) on gcc 4.7.2,
ncahill_alt at yahoo dot com <=