From: "H.J. Lu" <hjl.tools@gmail.com>
To: Vivek Das Mohapatra <vivek@collabora.com>,
Generic System V Application Binary Interface
<generic-abi@googlegroups.com>
Cc: Cary Coutant <ccoutant@gmail.com>,
Rahul Chaudhry via gnu-gabi <gnu-gabi@sourceware.org>
Subject: Re: [RFC][PATCH v3 0/6] binutils patches to add DF_1_UNIQUE
Date: Fri, 26 Jun 2020 08:29:28 -0700 [thread overview]
Message-ID: <CAMe9rOrKTFTBdzZt3Zaw4eug0sKxKMSg1GbPN3yMzTmKXEFO6Q@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.20.2006261610330.2022@noise.cbg.collabora.co.uk>
On Fri, Jun 26, 2020 at 8:12 AM Vivek Das Mohapatra via Gnu-gabi
<gnu-gabi@sourceware.org> wrote:
>
> I have submitted an updated patch series to the binutils list.
>
> DSOs are now tagged with a DT_FLAGS_1 value: DF_1_UNIQUE
> instead of a new dynamic section.
>
CC gABI:
https://sourceware.org/pipermail/binutils/2020-June/111925.html
Please create a merge request at
https://gitlab.com/x86-psABIs/Linux-ABI
to document DF_1_UNIQUE.
Thanks.
--
H.J.
next prev parent reply other threads:[~2020-06-26 15:30 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 [this message]
[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=CAMe9rOrKTFTBdzZt3Zaw4eug0sKxKMSg1GbPN3yMzTmKXEFO6Q@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=ccoutant@gmail.com \
--cc=generic-abi@googlegroups.com \
--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).