mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Cary Coutant <ccoutant@gmail.com>
To: Fangrui Song <i@maskray.me>
Cc: musl@lists.openwall.com
Subject: Re: [musl] [PATCH] elf.h: add ELFCOMPRESS_ZSTD
Date: Tue, 2 Aug 2022 16:09:22 -0700	[thread overview]
Message-ID: <CAJimCsGGr3+Rfio5HDPgSd3AsgqCt_ddJt=-pwCsN663i5sTYQ@mail.gmail.com> (raw)
In-Reply-To: <20220802200126.7mnqo67w7aegtog7@gmail.com>

> >Is this actually an adopted standard? It's not clear from the link
> >above whether there's anything authoritative going on or a proposal
> >that some people like.
> >
> >Rich
>
> I think so, from Cary's https://groups.google.com/g/generic-abi/c/satyPkuMisk/m/KwTF_U8rBAAJ
> "I will add this to the ELF spec, as proposed below:".
>
> This question isn't alone. Carlos O'Donell asked on https://sourceware.org/pipermail/libc-alpha/2022-July/141130.html
> "Is there a public repo that I can use to cross-check the glibc value with the accepted ELF gABI value?"

Yes, this is officially approved. The gABI committee runs mostly on
consensus, but as a representative for Xinuos, I can offer the formal
stamp of approval.

I am under contract with Xinuos to maintain the ELF standard, and I
have converted it from raw HTML to ReStructuredText format, with the
goal of placing it into a github repository. That last part is not yet
done, but as soon as I can, I'll make an updated version of the spec
available. Until then, you'll need to reference the June 2013 version,
with various gABI discussions to serve as amendments. As another
quasi-authoritative source, the ELF include files in the binutils git
repository are kept up to date with the gABI changes, and I'm about to
commit a change there to reflect the new compression type.

-cary

  reply	other threads:[~2022-08-03 10:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-26  2:14 Fangrui Song
2022-08-02 17:55 ` Rich Felker
2022-08-02 20:01   ` Fangrui Song
2022-08-02 23:09     ` Cary Coutant [this message]
2022-08-03 10:00     ` Szabolcs Nagy

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='CAJimCsGGr3+Rfio5HDPgSd3AsgqCt_ddJt=-pwCsN663i5sTYQ@mail.gmail.com' \
    --to=ccoutant@gmail.com \
    --cc=i@maskray.me \
    --cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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 NNTP newsgroup(s).