public inbox for gnu-gabi@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: Mark Wielaard <mark@klomp.org>,
	GNU gABI gnu-gabi <gnu-gabi@sourceware.org>
Subject: Re: ABI document
Date: Wed, 29 Jul 2020 14:22:37 +0200	[thread overview]
Message-ID: <87ime6pl2q.fsf@oldenburg2.str.redhat.com> (raw)
In-Reply-To: <CAMe9rOqSexN8m6J4w3dYXvw4cW3iQzY+7vg5HKG47AcDp9S4Ug@mail.gmail.com> (H. J. Lu's message of "Wed, 29 Jul 2020 05:15:20 -0700")

* H. J. Lu:

> On Wed, Jul 29, 2020 at 4:53 AM Mark Wielaard <mark@klomp.org> wrote:
>>
>> On Wed, 2020-07-29 at 13:47 +0200, Florian Weimer via Gnu-gabi wrote:
>> > Is there an ABI document somewhere for the generic GNU ABI?
>> >
>> > It would eventually collect things like symbol versioning, TLS, and some
>> > of the smaller stuff.  I understand those have been documented
>> > separately so far, but the question is what we should do for new
>> > features?
>>
>> There isn't a formal one specific to the generic GNU ABI. But we can
>> set up a gnu-gabi git repo on sourceware for it, so we can collect
>> those things. Or do you prefer a wiki?
>>
>
> I started one:
>
> https://gitlab.com/x86-psABIs/Linux-ABI

But we are not supposed to talk about GNU there, so I think it's not
helpful for describing GNU features.

If I'm wrong about that and we can document glibc specifics there (such
as DF_GNU_1_UNIQUE), then I guess that's fine, except that you will be
hard-pressed to find a glibc target that implements dynamic linking, but
not these ELF extensions (because they will be in generic code).  So the
processor-independent GNU/Linux ABI isn't really the right place.

These features are also not likely to be implemented by musl, ucLibc,
LLVM libc, even on Linux, because they *are* GNU features, not Linux
platform features.

Thanks,
Florian


  reply	other threads:[~2020-07-29 12:22 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-29 11:47 Florian Weimer
2020-07-29 11:53 ` Mark Wielaard
2020-07-29 12:15   ` H.J. Lu
2020-07-29 12:22     ` Florian Weimer [this message]
2020-08-14  9:51       ` Vivek Das Mohapatra
2020-08-14 10:58         ` Mark Wielaard
2020-08-14 11:33           ` Vivek Das Mohapatra
2020-08-14 15:17             ` Mark Wielaard
2020-08-27 16:52               ` Vivek Das Mohapatra
2020-08-31 12:54                 ` Florian Weimer
2020-09-02 17:29                   ` Vivek Das Mohapatra
2020-09-08 12:09                     ` Vivek Das Mohapatra
2020-09-16 13:57                       ` Vivek Das Mohapatra
2020-09-21 13:03                       ` Florian Weimer
2020-09-21 12:36                     ` Florian Weimer
2020-11-27 15:40                       ` Vivek Das Mohapatra
2020-11-30 17:36                         ` Florian Weimer
2020-12-09 16:59                           ` Vivek Das Mohapatra
2022-08-25  8:11                             ` Florian Weimer
2022-08-25 15:38                               ` Carlos O'Donell
2022-08-30 11:55                               ` Vivek Dasmohapatra
2022-08-30 12:12                                 ` Florian Weimer
2022-08-30 15:17                                   ` Vivek Dasmohapatra
2020-07-29 12:56   ` Jose E. Marchesi

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=87ime6pl2q.fsf@oldenburg2.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=gnu-gabi@sourceware.org \
    --cc=hjl.tools@gmail.com \
    --cc=mark@klomp.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).