From: Ulrich Drepper <drepper@redhat.com>
To: libc-hacker@sourceware.org
Subject: Re: [PATCH] Fix handling of STB_GNU_UNIQUE in LD_TRACE_PRELINKING
Date: Wed, 24 Mar 2010 17:16:00 -0000 [thread overview]
Message-ID: <4BAA48D7.3010308@redhat.com> (raw)
In-Reply-To: <20100323103348.GE3601@sunsite.ms.mff.cuni.cz>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 03/23/2010 03:33 AM, Jakub Jelinek wrote:
> Attached are two possible patches. The second, shorter one, is all that is
> needed currently (I believe). The difference between the patches is in
> handling libraries with DT_SYMBOLIC and STB_GNU_UNIQUE symbols. Apparently
> current GNU ld if there is a relocation against STB_GNU_UNIQUE symbol
> defined in the library itself, doesn't emit any relocation and resolves at
> link time (possibly through a relative relocation). Is that what we want
> though? Then the STB_GNU_UNIQUE symbols aren't really unique...
Right. The linker has to be fixed. I've applied the first patch.
- --
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA â–
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
iEYEARECAAYFAkuqSNcACgkQ2ijCOnn/RHQkNACgu14Wmhn6JxpmuDbE3PEUG82a
qO8AniThFZts0yE1zJ+IXaBQjD3P1XOW
=2rjh
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2010-03-24 17:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-23 10:34 Jakub Jelinek
2010-03-24 17:16 ` Ulrich Drepper [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BAA48D7.3010308@redhat.com \
--to=drepper@redhat.com \
--cc=libc-hacker@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).