From: "H.J. Lu" <hjl.tools@gmail.com>
To: Vivek Das Mohapatra <vivek@collabora.com>,
GNU gABI gnu-gabi <gnu-gabi@sourceware.org>,
GNU C Library <libc-alpha@sourceware.org>,
Binutils <binutils@sourceware.org>
Subject: Re: [RFC][PATCH v3 0/6] binutils patches to add DF_1_UNIQUE
Date: Fri, 26 Jun 2020 11:34:02 -0700 [thread overview]
Message-ID: <CAMe9rOoDBpjDiofmSBpu-BUOWeibpTvf6KoTEp-BpUVyFeQvsA@mail.gmail.com> (raw)
In-Reply-To: <CAMe9rOorOgV6wT3gHVdfK-zKp11kUVcqtBZHSSd__EdQtWvcKw@mail.gmail.com>
On Fri, Jun 26, 2020 at 10:38 AM H.J. Lu <hjl.tools@gmail.com> wrote:
>
> On Fri, Jun 26, 2020 at 10:35 AM 'Fangrui Song' via Generic System V
> Application Binary Interface <generic-abi@googlegroups.com> wrote:
> >
> > On 2020-06-26, Ali Bahrami wrote:
> > >On 6/26/20 9:49 AM, H.J. Lu wrote:
> > >>> I don't know about DF_1_UNIQUE specifically,
> > >>>but on Solaris, all 32-bits of DT_FLAGS_1
> > >>>have already been defined, so we have a conflict.
> > >>>
> > >>>Perhaps this should move to a DT_GNU_* dynamic
> > >>>entry that's part of the GNU OSABI?
> > >>>
> > >>How about DT_GNU_FLAGS_1 and DF_GNU_1_UNIQUE?
> > >
> > >
> > > That would work for me.
> > >
> > >- Ali
> >
> > It seems that GNU specific dlmopen wants to have a libc.so/libpthread.so instance per namespace, but they need to
> > share some data structures. (https://sourceware.org/pipermail/libc-alpha/2020-June/115139.html )
> >
> > Even on Linux, I think this is very unlikely adopted by musl.
> > It is said this flag may have something to do with LD_AUDIT.
> >
> > DT_GNU_FLAGS_1 and DF_GNU_1_UNIQUE are definitely fine.
> >
>
> I will propose to gnu-gABI:
>
> #define DT_GNU_FLAGS_1 0x6ffffdf4
> #define DF_GNU_1_UNIQUE 0x00000001
>
Here is the merge request to define DT_GNU_FLAGS_1 and
DF_GNU_1_UNIQUE:
https://gitlab.com/x86-psABIs/Linux-ABI/-/merge_requests/1
--
H.J.
prev parent reply other threads:[~2020-06-26 18:34 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 ` [RFC][PATCH v2 0/6] binutils patches to add DT_GNU_UNIQUE Vivek Das Mohapatra
2020-06-17 16:16 ` Michael Matz
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 [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=CAMe9rOoDBpjDiofmSBpu-BUOWeibpTvf6KoTEp-BpUVyFeQvsA@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=binutils@sourceware.org \
--cc=gnu-gabi@sourceware.org \
--cc=libc-alpha@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).