public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Fangrui Song <maskray@google.com>
To: Carlos O'Donell <carlos@redhat.com>
Cc: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>,
	Cary Coutant <ccoutant@gmail.com>,
	Florian Weimer <fweimer@redhat.com>,
	libc-alpha <libc-alpha@sourceware.org>
Subject: Re: [PATCH] elf.h: Add ELFCOMPRESS_ZSTD
Date: Thu, 4 Aug 2022 13:04:42 -0700	[thread overview]
Message-ID: <20220804200442.sypcy42jyqmlmoqs@google.com> (raw)
In-Reply-To: <8c2e6f15-c08c-9872-3b53-f514ead5692f@redhat.com>

On 2022-07-29, Carlos O'Donell wrote:
>On 7/26/22 16:30, Fangrui Song wrote:
>> On Tue, Jul 26, 2022 at 1:24 PM Adhemerval Zanella Netto
>> <adhemerval.zanella@linaro.org> wrote:
>>>
>>>
>>>
>>> On 22/07/22 20:08, Fangrui Song via Libc-alpha wrote:
>>>> On 2022-07-18, Carlos O'Donell via Libc-alpha wrote:
>>>>> On 7/11/22 00:58, Florian Weimer via Libc-alpha wrote:
>>>>>> * Fangrui Song via Libc-alpha:
>>>>>>
>>>>>>> I wish that the macro definition can catch up the upcoming
>>>>>>> https://sourceware.org/glibc/wiki/Release/2.36 [1], so that
>>>>>>> projects can expect the value ELFCOMPRESS_ZSTD from elf.h.
>>>>>>> The projects may choose to define the macro themselves,
>>>>>>> but having the definition in an earlier release seems a good idea
>>>>>>> anyway, and it the glibc definition makes it clearer ELFCOMPRESS_ZSTD
>>>>>>> is standard and vendors can start adding support.
>>>>>>>
>>>>>>> [1]: https://sourceware.org/pipermail/libc-alpha/2022-July/140352.html
>>>>>>> ("Release of glibc 2.36 in 1 month! Please add blockers and desirable for release.")
>>>>>>
>>>>>> This looks quite backportable to me, so it should not be a release
>>>>>> blocker.  It's only a blocker if we apply the patch today, then we'd
>>>>>> have to wait until the gABI assignment actually happens as expected.
>>>>>
>>>>> Agreed. This is a NACK from me as the RM until the gABI assignment happens.
>>>>>
>>>>
>>>> Cary has accepted this value: https://groups.google.com/g/generic-abi/c/satyPkuMisk/m/KwTF_U8rBAAJ
>>>> (Thanks!)
>>>>
>>>> Ed Maste from FreeBSD wants to define this in FreeBSD.
>>>>
>>>> Shall we define it for glibc as well? :)
>>>
>>> I think this is ok, we are already fixing bad designs so we most likely need
>>> more time for testing.
>>
>> Thanks.  Now that it is approved, the commit message can be changed to
>> the following if you want to push it to the 2.36 release branch.
>>
>> elf.h: Add ELFCOMPRESS_ZSTD
>>
>> From the approved generic ABI proposal
>> https://groups.google.com/g/generic-abi/c/satyPkuMisk
>> ("Add new ch_type value: ELFCOMPRESS_ZSTD").
>
>Cary,
>
>Is there a public repo that I can use to cross-check the glibc value with
>the accepted ELF gABI value?
>
>A public repo would make the process of adding matching constants
>easier because I could review what went into the public repository.
>
>Fangrui,
>
>Just for clarity, I don't consider this a release blocker for 2.36.

Cary pushed a similar change to binutils-gdb
https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=03d0ae791f7dca2006b924e90ee4e4944b848260

Cary mentioned it on the musl mailing list
https://www.openwall.com/lists/musl/2022/08/03/3 "Yes, this is officially approved."

  reply	other threads:[~2022-08-04 20:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-08 23:32 Fangrui Song
2022-07-11  4:58 ` Florian Weimer
2022-07-18 14:01   ` Carlos O'Donell
2022-07-22 23:08     ` Fangrui Song
2022-07-26 20:23       ` Adhemerval Zanella Netto
2022-07-26 20:30         ` Fangrui Song
2022-07-29 15:44           ` Carlos O'Donell
2022-08-04 20:04             ` Fangrui Song [this message]
2022-08-10  7:09               ` Fangrui Song
2022-08-10  7:46 ` Florian Weimer

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=20220804200442.sypcy42jyqmlmoqs@google.com \
    --to=maskray@google.com \
    --cc=adhemerval.zanella@linaro.org \
    --cc=carlos@redhat.com \
    --cc=ccoutant@gmail.com \
    --cc=fweimer@redhat.com \
    --cc=libc-alpha@sourceware.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).