mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Fangrui Song <i@maskray.me>
To: musl@lists.openwall.com, Rich Felker <dalias@libc.org>
Subject: Re: [musl] [PATCH] elf.h: add ELFCOMPRESS_ZSTD
Date: Sat, 4 Feb 2023 14:02:34 -0800	[thread overview]
Message-ID: <DS7PR12MB576510C58D4CA2122A99B0A8CBD49@DS7PR12MB5765.namprd12.prod.outlook.com> (raw)
In-Reply-To: <CAN30aBEOE2pr_5SfM4fyw5i-UUEwdDzvv9uXY+Fj7TyUqS9ktw@mail.gmail.com>

On Mon, Nov 7, 2022 at 11:21 PM Fangrui Song <i@maskray.me> wrote:
>
> On Wed, Aug 3, 2022 at 3:00 AM Szabolcs Nagy <nsz@port70.net> wrote:
> >
> > * Fangrui Song <i@maskray.me> [2022-08-02 13:01:26 -0700]:
> > > On 2022-08-02, Rich Felker wrote:
> > > >
> > > > 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.
> > >
> > > 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:".
> >
> > i think at this point the closest to a single point of truth for
> > the elf spec is cary's approval mails on the generic abi list.
>
> Can this be picked? glibc and FreeBSD have defined this for a few months now...

Ping:)   Hope that https://www.openwall.com/lists/musl/2022/07/26/1
can land in the 1.2.4 release.

  parent reply	other threads:[~2023-02-04 22:10 UTC|newest]

Thread overview: 8+ 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
2022-08-03 10:00     ` Szabolcs Nagy
2022-11-08  7:21       ` Fangrui Song
     [not found]       ` <CAN30aBEOE2pr_5SfM4fyw5i-UUEwdDzvv9uXY+Fj7TyUqS9ktw@mail.gmail.com>
2023-02-04 22:02         ` Fangrui Song [this message]
2023-02-05 23:51           ` Rich Felker

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=DS7PR12MB576510C58D4CA2122A99B0A8CBD49@DS7PR12MB5765.namprd12.prod.outlook.com \
    --to=i@maskray.me \
    --cc=dalias@libc.org \
    --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).