From: Michael Matz <matz@suse.de>
To: "Vivek Das Mohapatra" <vivek@collabora.com>
Cc: gnu-gabi@sourceware.org
Subject: Re: [RFC][PATCH v2 0/6] binutils patches to add DT_GNU_UNIQUE
Date: Wed, 17 Jun 2020 16:16:22 +0000 (UTC) [thread overview]
Message-ID: <alpine.LSU.2.20.2006171601340.22600@wotan.suse.de> (raw)
In-Reply-To: <alpine.DEB.2.20.2006171657120.2022@noise.cbg.collabora.co.uk>
Hello,
On Wed, 17 Jun 2020, Vivek Das Mohapatra via Gnu-gabi wrote:
> Hi - notifying this list (as requested) of a patchset to binutils-gdb,
> described below:
>
> https://sourceware.org/pipermail/binutils/2020-June/111747.html
Can you describe the purpose and semantics of the new dynamic tag in
textual form that doesn't refer to glibc functions and terms? I.e.
something that we can actually discuss on this mailing list?
Because the best description in the patch series seems to be what you
quoted:
> > It adds a DT_GNU_UNIQUE dynamic section which is intended to mark
> > libraries which should implicitly be opened as if RTLD_SHARED
> > had been passed to dlmopen when the target namespace is not
> > LM_ID_BASE.
and that doesn't seem to be text we want to put into the GNU variant
of the gABI, e.g. it talks about namespaces (no gABI concept) and dlmopen
(also no gABI function).
I mean, we could just reserve value 0x6ffffdf4 with name DT_GNU_UNIQUE in
the GNU/Linux gABI and be done. But it seems saner to actually document
the intended semantics of it at the same place where it's reserved.
Ciao,
Michael.
next prev parent reply other threads:[~2020-06-17 16:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200617135945.12716-1-vivek@collabora.com>
[not found] ` <CAMe9rOr7PVkz1k8dAPXoJjiCjiQ32f26ZduMX6xuxbGzguG=zQ@mail.gmail.com>
2020-06-17 16:00 ` Vivek Das Mohapatra
2020-06-17 16:16 ` Michael Matz [this message]
2020-06-17 16:37 ` Vivek Das Mohapatra
2020-06-17 18:23 ` Cary Coutant
2020-06-17 19:13 ` Vivek Das Mohapatra
2020-06-26 15:12 ` [RFC][PATCH v3 0/6] binutils patches to add DF_1_UNIQUE Vivek Das Mohapatra
2020-06-26 15:29 ` H.J. Lu
[not found] ` <ca72c789-f60c-2eaf-18e9-a7e59fcb0319@Oracle.COM>
[not found] ` <CAMe9rOqF-zUUsCeyiT8s20bhTeVhozZtGkAD-JRrNiEOaju7jQ@mail.gmail.com>
[not found] ` <8af0af5a-9fd4-2e80-1dff-ff714a15a6b2@Oracle.COM>
[not found] ` <20200626173513.22arn2ihwgxudmjf@google.com>
[not found] ` <CAMe9rOorOgV6wT3gHVdfK-zKp11kUVcqtBZHSSd__EdQtWvcKw@mail.gmail.com>
2020-06-26 18:34 ` 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=alpine.LSU.2.20.2006171601340.22600@wotan.suse.de \
--to=matz@suse.de \
--cc=gnu-gabi@sourceware.org \
--cc=vivek@collabora.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).