unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fw@deneb.enyo.de>
To: "Vivek Das Mohapatra via Libc-alpha" <libc-alpha@sourceware.org>
Cc: vivek@etla.org
Subject: Re: [RFC][PATCH 0/6] binutils patches to add DT_FLAGS_1 / DF_1_UNIQUE
Date: Mon, 30 Mar 2020 20:06:53 +0200	[thread overview]
Message-ID: <87h7y5vhs2.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <cover.1585587351.git.vivek@collabora.com> ("Vivek Das Mohapatra via Libc-alpha"'s message of "Mon, 30 Mar 2020 18:42:01 +0100")

* Vivek Das Mohapatra via Libc-alpha:

> This patch series is in support of the glibc RTLD_SHARED work
> discussed in https://sourceware.org/bugzilla/show_bug.cgi?id=22745.
>
> It adds a DT_FLAGS_1 value DF_1_UNIQUE 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.
>
> This patch series adds support for DF_1_UNIQUE to ld, gold, and
> readelf (and documents it in the help text and so forth).

I think you should repost this series to the binutils list.

It would perhaps be less controversial to add a new dynamic tag in the
GNU range for this, rather than a global flag value (in the space
shared with other operating systems).

  parent reply	other threads:[~2020-03-30 18:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-30 17:42 [RFC][PATCH 0/6] binutils patches to add DT_FLAGS_1 / DF_1_UNIQUE Vivek Das Mohapatra via Libc-alpha
2020-03-30 17:42 ` [RFC][PATCH 1/6] Define a new DT_FLAGS_1 flag DF_1_UNIQUE for ld, readelf et al Vivek Das Mohapatra via Libc-alpha
2020-03-30 17:42 ` [RFC][PATCH 2/6] Handle DF_1_UNIQUE in ld Vivek Das Mohapatra via Libc-alpha
2020-03-30 17:42 ` [RFC][PATCH 3/6] Document DF_1_UNIQUE in the man page and ld help output Vivek Das Mohapatra via Libc-alpha
2020-03-30 17:42 ` [RFC][PATCH 4/6] Handle DF_1_UNIQUE in readelf Vivek Das Mohapatra via Libc-alpha
2020-03-30 17:42 ` [RFC][PATCH 5/6] Define DT_FLAGS_1 flag DF_1_UNIQUE for gold Vivek Das Mohapatra via Libc-alpha
2020-03-30 17:42 ` [RFC][PATCH 6/6] Implement and document DF_1_UNIQUE handling in gold Vivek Das Mohapatra via Libc-alpha
2020-03-30 18:06 ` Florian Weimer [this message]
2020-03-31 12:11   ` [RFC][PATCH 0/6] binutils patches to add DT_FLAGS_1 / DF_1_UNIQUE Vivek Das Mohapatra via Libc-alpha
2020-05-29 14:00     ` Vivek Das Mohapatra via Libc-alpha
2020-05-29 16:13       ` Florian Weimer via Libc-alpha

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

  List information: https://www.gnu.org/software/libc/involved.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87h7y5vhs2.fsf@mid.deneb.enyo.de \
    --to=fw@deneb.enyo.de \
    --cc=libc-alpha@sourceware.org \
    --cc=vivek@etla.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).