mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Fangrui Song <>
Cc: Cary Coutant <>
Subject: Re: [musl] [PATCH] elf.h: add ELFCOMPRESS_ZSTD
Date: Tue, 2 Aug 2022 13:01:26 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 2022-08-02, Rich Felker wrote:
>On Mon, Jul 25, 2022 at 07:14:33PM -0700, Fangrui Song wrote:
>> see
>>   Add new ch_type value: ELFCOMPRESS_ZSTD
>> ---
>>  include/elf.h | 1 +
>>  1 file changed, 1 insertion(+)
>> diff --git a/include/elf.h b/include/elf.h
>> index 86e2f0bb..d2231ba0 100644
>> --- a/include/elf.h
>> +++ b/include/elf.h
>> @@ -436,6 +436,7 @@ typedef struct {
>>  } Elf64_Chdr;
>>  #define ELFCOMPRESS_ZLIB	1
>> +#define ELFCOMPRESS_ZSTD	2
>>  #define ELFCOMPRESS_LOOS	0x60000000
>>  #define ELFCOMPRESS_HIOS	0x6fffffff
>>  #define ELFCOMPRESS_LOPROC	0x70000000
>> --
>> 2.37.1
>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
"I will add this to the ELF spec, as proposed below:".

This question isn't alone. Carlos O'Donell asked on
"Is there a public repo that I can use to cross-check the glibc value with the accepted ELF gABI value?"

Let me summarize the history:

Roughly since 2015
("Heads Up: John Wolfe no longer at Xinuos Inc"), the official generic ABI website no longer gets update. (I believe the last
change was
"Proposed gABI addition: SHF_COMPRESS").

Since ("Ongoing Maintenance of the gABI"), 
Cary Coutant takes on the maintenance of the gABI spec.

At the moment there is no repository. If help is needed, I am happy to convert the
/developers/gabi/latest .html files to Markdown or reST.

  reply	other threads:[~2022-08-02 20:01 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 [this message]
2022-08-02 23:09     ` Cary Coutant
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:

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

  git send-email \ \ \ \ \

* 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

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).