From: "H.J. Lu" <hjl.tools@gmail.com>
To: Michael Matz <matz@suse.de>
Cc: gnu-gabi@sourceware.org
Subject: Re: Specify how undefined weak symbol should be resolved in executable
Date: Fri, 01 Jan 2016 00:00:00 -0000 [thread overview]
Message-ID: <CAMe9rOoqOvXXOjLKnyg0OPpPE4pEvN4kO6+e7nWz7Ng9LTBwSg@mail.gmail.com> (raw)
In-Reply-To: <alpine.LSU.2.20.1602221914130.20277@wotan.suse.de>
On Mon, Feb 22, 2016 at 10:17 AM, Michael Matz <matz@suse.de> wrote:
> Hi,
>
> On Mon, 22 Feb 2016, H.J. Lu wrote:
>
>> > Typo? What is the meaning of "dynamic relocation available at
>> > runtime". Are you talking about a relocation entry or the relocation
>> > process?
>>
>> Dynamic relocation isn't available with static linking.
>
> So you _are_ talking about the process. I think it's customary to call
> such executables "dynamic", or perhaps non-static, isn't it? (Why I'm
> confused with your wording: a dynamic executable which happens to have no
> dynamic reloc entries, has "no dynamic relocation available at runtime",
> and so we couldn't add one :))
>
>> > How about "When creating a dynamic executable the link editor should
>> > ..."?
>
> So, I still can understand my version better (possibly with
> s/dynamic/non-static/) :)
>
Let's go with:
When creating dynamic executable, the link editor should generate dynamic
relocations against unresolved weak symbols so that their values will be
resolved at run-time.
--
H.J.
next prev parent reply other threads:[~2016-02-22 18:28 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-01 0:00 H.J. Lu
2016-01-01 0:00 ` H.J. Lu
2016-01-01 0:00 ` Michael Matz
2016-01-01 0:00 ` H.J. Lu
2016-01-01 0:00 ` Michael Matz
2016-01-01 0:00 ` H.J. Lu [this message]
2016-01-01 0:00 ` H.J. Lu
2016-01-01 0:00 ` Alan Modra
2016-01-01 0:00 ` H.J. Lu
2016-01-01 0:00 ` Michael Matz
2016-01-01 0:00 ` H.J. Lu
2016-01-01 0:00 ` Michael Matz
2016-01-01 0:00 ` H.J. Lu
2016-01-01 0:00 ` Alan Modra
2016-01-01 0:00 ` H.J. Lu
2016-01-01 0:00 ` Alan Modra
2016-01-01 0:00 ` Carlos O'Donell
2016-01-01 0:00 ` H.J. Lu
2016-01-01 0:00 ` Michael Matz
2016-01-01 0:00 ` H.J. Lu
2016-01-01 0:00 ` Michael Matz
2016-01-01 0:00 ` H.J. Lu
2016-01-01 0:00 ` Michael Matz
2016-01-01 0:00 ` H.J. Lu
2016-01-01 0:00 ` H.J. Lu
2016-01-01 0:00 ` H.J. Lu
2016-01-01 0:00 ` Michael Matz
2016-01-01 0:00 ` H.J. Lu
2016-01-01 0:00 ` Michael Matz
2016-01-01 0:00 ` Szabolcs Nagy
2016-01-01 0:00 ` Michael Matz
2016-01-01 0:00 ` H.J. Lu
2016-01-01 0:00 ` H.J. Lu
2016-01-01 0:00 ` H.J. Lu
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=CAMe9rOoqOvXXOjLKnyg0OPpPE4pEvN4kO6+e7nWz7Ng9LTBwSg@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=gnu-gabi@sourceware.org \
--cc=matz@suse.de \
/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).