From: David Edelsohn <dje.gcc@gmail.com>
To: Michael Haubenwallner <michael.haubenwallner@ssi-schaefer.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] AIX: Filename-based shared library versioning for libgcc_s
Date: Tue, 25 Nov 2014 14:25:00 -0000 [thread overview]
Message-ID: <CAGWvnyk3mNnY1-zOqGofD2RrBzW26-_1yTkx7-D7BX+M8SD3GA@mail.gmail.com> (raw)
In-Reply-To: <54622E80.904@ssi-schaefer.com>
On Tue, Nov 11, 2014 at 10:42 AM, Michael Haubenwallner
<michael.haubenwallner@ssi-schaefer.com> wrote:
>
>
> On 11/11/2014 04:02 PM, David Edelsohn wrote:
>> Michael,
>>
>> Why does the configure change match with p*-*-aix... instead of power*
>> or powerpc*? Yes, it's unique and will match, but why make it as
>> short as possible, which doesn't match other uses?
>
> Actually I did have powerpc* initially, but gmp-6.0.0 config.guess'ed
> power7-ibm-aix6.1.0.0 now. Then I've thought that one may use ppc as well,
> but now I see this config.sub's to powerpc anyway, so power* is fine.
> Patch updated.
>
>> In your documentation, how are you distinguishing between Dynamic
>> Linking and Runtime Linking?
>
> I've tried to use the same naming scheme as in the "ld Command Reference"
> and the "dlopen Subroutine" man pages.
>
> Actually, there is
> at linktime:
> Dynamic Linking: also known as Dynamic Mode or (more common)
> Shared Linking: record a shared object's name into the created binary
>
> at runtime:
> Runtime Loading: load these shared objects at process startup
> Runtime Linking: resolve the symbols after loading shared objects
> Dynamic Loading: load shared objects by application logic with dlopen()
>
> I'm unsure how to make this as clear as possible though.
Now that things have calmed down with respect to breakage on AIX, the
patch for building libgcc_s is okay.
Thanks, David
next prev parent reply other threads:[~2014-11-25 13:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-07 19:52 David Edelsohn
2014-11-10 10:01 ` Michael Haubenwallner
2014-11-10 16:17 ` David Edelsohn
2014-11-10 18:01 ` Michael Haubenwallner
2014-11-11 15:03 ` David Edelsohn
2014-11-11 15:44 ` Michael Haubenwallner
2014-11-25 14:25 ` David Edelsohn [this message]
2014-12-05 12:56 ` Michael Haubenwallner
2014-12-05 14:06 ` David Edelsohn
-- strict thread matches above, loose matches on Subject: below --
2014-11-07 12:58 Michael Haubenwallner
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=CAGWvnyk3mNnY1-zOqGofD2RrBzW26-_1yTkx7-D7BX+M8SD3GA@mail.gmail.com \
--to=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=michael.haubenwallner@ssi-schaefer.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.
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).