This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
| Other format: | [Raw text] | |
On 01/25/2017 05:36 PM, H.J. Lu wrote:
On Wed, Jan 25, 2017 at 5:57 AM, Florian Weimer <fweimer@redhat.com> wrote:In retrospect, adding IFUNCs as a user-visible feature looks like a mistake, but now we have to live with them.Probably. Now we are making it even more complex. Doesn't it make the situation worse?
The x86-64 IFUNC resolvers rely on relocated data, which breaks existing binaries which worked before. I'm trying to fix that.
Would you prefer that we rolled back the IFUNC resolver changes instead? I have seen zero movement in that direction, so I assumed you would not consider this approach acceptable.
And it's not just x86-64. I don't see a coordinated effort to comply with the requirements on IFUNC resolvers spelled out here:
<https://sourceware.org/glibc/wiki/GNU_IFUNC> (And this document is not particularly helpful as developer documentation.) Thanks, Florian
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |