From: Richard Pennington <rich@pennware.com>
To: "musl@lists.openwall.com" <musl@lists.openwall.com>
Subject: Re: _GLOBAL_OFFSET_TABLE_ in ldso/*/start.s?
Date: Fri, 8 Jun 2012 17:43:31 -0500 [thread overview]
Message-ID: <1607F838-B823-40E7-882F-B4D24852AE94@pennware.com> (raw)
In-Reply-To: <20120608223138.GW163@brightrain.aerifal.cx>
Thanks Rich. Becoming familiar with git is definitely on my todo list.
-Rich
Sent from my iPhone
On Jun 8, 2012, at 5:31 PM, Rich Felker <dalias@aerifal.cx> wrote:
> On Fri, Jun 08, 2012 at 03:54:46PM -0500, Richard Pennington wrote:
>> What is the purpose of the _GLOBAL_OFFSET_TABLE_ reference in these files? It
>> doesn't seem to be used by __dynlink(), although it seems to be passed a a
>> third parameter.
>
> If you check git, you'll see that this code was removed. A much older
> version of __dynlink took a third argument that was the base address
> of the GOT, which was used to find a pointer to _DYNAMIC in the first
> GOT slot (traditionally, it was stored there). Then people started
> reporting crashes when linking with a non-binutils linker (gold? or
> something from clang/llvm? I don't remember...) that didn't follow
> this practice, so I replaced it with more elaborate code to find
> _DYNAMIC. The unneeded code in the asm was not removed until much
> later. I actually have a new idea for simplifying/replacing some of
> the C code, but it won't affect the asm.
>
> By the way, it might be a good idea to familiarize yourself with git
> or even the gitweb interface. Questions like the one you had just now
> can usually be answered quickly by checking the history of the
> relevant files.
>
> Rich
next prev parent reply other threads:[~2012-06-08 22:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-08 20:54 Richard Pennington
2012-06-08 22:31 ` Rich Felker
2012-06-08 22:43 ` Richard Pennington [this message]
2012-06-08 23:21 ` Ivan Kanakarakis
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=1607F838-B823-40E7-882F-B4D24852AE94@pennware.com \
--to=rich@pennware.com \
--cc=musl@lists.openwall.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).