public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Fangrui Song <i@maskray.me>
To: Cary Coutant <ccoutant@gmail.com>
Cc: Binutils <binutils@sourceware.org>
Subject: Re: [ELF commit] Add new zstd compression algorithm
Date: Tue, 2 Aug 2022 15:43:05 -0700	[thread overview]
Message-ID: <20220802224305.xoivjndxydsrjzbq@gmail.com> (raw)
In-Reply-To: <CAJimCsGywbO1c+mNC-rCUW610cCkU8VHtG3mWtmyMq0i2DFPtQ@mail.gmail.com>

On 2022-08-02, Cary Coutant via Binutils wrote:
>In the gABI group, we have approved the addition of a new compression
>type, using the zstd library (zstandard.org). I'm about to commit this
>patch to add the new value to <elf/common.h>.
>
>https://groups.google.com/g/generic-abi/c/satyPkuMisk/m/dP2pPh9mAwAJ
>
>-cary
>
>
>include/elf/
>        * common.h: Add ELFCOMPRESS_ZSTD.
>
>
>diff --git a/include/elf/common.h b/include/elf/common.h
>index e4bc53e35b4..ebcd8f9e82c 100644
>--- a/include/elf/common.h
>+++ b/include/elf/common.h
>@@ -588,6 +588,8 @@
>
> /* Compression types.  */
> #define ELFCOMPRESS_ZLIB   1           /* Compressed with zlib.  */
>+#define ELFCOMPRESS_ZSTD   2           /* Compressed with zstd  */
>+                                       /* (see http://www.zstandard.org). */
> #define ELFCOMPRESS_LOOS   0x60000000  /* OS-specific semantics, lo */
> #define ELFCOMPRESS_HIOS   0x6FFFFFFF  /* OS-specific semantics, hi */
> #define ELFCOMPRESS_LOPROC 0x70000000  /* Processor-specific semantics, lo */

Thanks:)

Interested folks may help
https://sourceware.org/bugzilla/show_bug.cgi?id=29397 ("binutils: support zstd for SHF_COMPRESSED debug sections")

The build system change is probably the most difficult one ;-)

      reply	other threads:[~2022-08-02 22:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-02 21:31 Cary Coutant
2022-08-02 22:43 ` Fangrui Song [this message]

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=20220802224305.xoivjndxydsrjzbq@gmail.com \
    --to=i@maskray.me \
    --cc=binutils@sourceware.org \
    --cc=ccoutant@gmail.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.
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).