From: Florian Weimer <fweimer@redhat.com>
To: Alessandro Carminati via Libc-help <libc-help@sourceware.org>
Cc: Alessandro Carminati <alessandro.carminati@gmail.com>
Subject: Re: Fwd: MIPSEL GLIBC sem_init() not shared
Date: Sat, 13 Mar 2021 08:05:24 +0100 [thread overview]
Message-ID: <87r1kjy1mz.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <CAPp5cGTVm4LuYAMcMhSaBq28Z-9YJss8ifno2s3EUNHMSB9rNA@mail.gmail.com> (Alessandro Carminati via Libc-help's message of "Sat, 13 Mar 2021 07:53:38 +0100")
* Alessandro Carminati via Libc-help:
> Reflecting on my scenario I see that the dynamic linker finds quite unusual
> situation where the symbol is required and there's no dependency on the DSO
> containing it, and no indication (.gnu.version_r) about how to handle it.
> My assumption was that the double @@ would handle these situation, but it
> is reasonable that this situation to have another handling.
> For this reason my current understanding is that the dynamic linker would
> use default the double @@ indicated function, where the .gnu.version_r is
> present but not populated, and use the older symbol where
> the .gnu.version_r is missing. This way it would handle correctly the
> situation where old executables do not have the section because it didn't
> exist yet.
We could have done this for glibc itself perhaps, but it would break in
the case of another shared object adding symbol versions after a release
without symbols.
Thanks,
Florian
prev parent reply other threads:[~2021-03-13 7:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-12 9:31 Alessandro Carminati
2021-03-12 10:49 ` Florian Weimer
[not found] ` <CAPp5cGTfu38orQNtDRXrxenPDKYbJgEmFHjcw8QspURmCkZL0Q@mail.gmail.com>
2021-03-12 11:37 ` Fwd: " Alessandro Carminati
2021-03-12 12:17 ` Florian Weimer
2021-03-12 13:41 ` Alessandro Carminati
2021-03-12 16:04 ` Florian Weimer
2021-03-13 6:53 ` Alessandro Carminati
2021-03-13 7:05 ` Florian Weimer [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=87r1kjy1mz.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=alessandro.carminati@gmail.com \
--cc=libc-help@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).