[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug ld/15025] --enable-initfini-array creates .init_array where no inpu

From: rguenther at suse dot de
Subject: [Bug ld/15025] --enable-initfini-array creates .init_array where no input has one
Date: Wed, 23 Jan 2013 14:44:27 +0000


--- Comment #12 from rguenther at suse dot de 2013-01-23 14:44:27 UTC ---
"hjl.tools at gmail dot com" <address@hidden> wrote:

>--- Comment #11 from H.J. Lu <hjl.tools at gmail dot com> 2013-01-23
>14:34:09 UTC ---
>New binutils places input .ctor in .init_array to
>conform to gABI.

As I still have crtfiles with .ctor with gcc 4.3 the end result does not
"conform to gABI"

So what is the point of the exercise?

 I have no problems with GCC 4.1
>to 4.6.

I have the issue that new binutils can no longer be used to link old glibc. And
whatelse unknown for our ISVs. So I have to disable this "feature" in glibc.
Which forces me to disable is also in gcc 4.7 as I lost the feature
Of correctly handling mixed prioritized .ctor
And .init_array sections.

The situation is highly undesirable to me
And I question the value of this feature if
The resulting object does not conform to gABI

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.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]