From: Alan Modra <amodra@gmail.com>
To: "Martin Liška" <mliska@suse.cz>
Cc: binutils@sourceware.org, Fangrui Song <maskray@google.com>
Subject: Re: [PATCH] compress .gnu.debuglto_.debug_* sections if requested
Date: Wed, 5 Oct 2022 00:11:01 +1030 [thread overview]
Message-ID: <Yzw37djOG/I8DsP+@squeak.grove.modra.org> (raw)
In-Reply-To: <373ed7fc-5b05-0049-7df0-35958fd2857c@suse.cz>
On Tue, Oct 04, 2022 at 10:12:46AM +0200, Martin Liška wrote:
> On 10/4/22 10:07, Alan Modra wrote:
> > On Fri, Sep 30, 2022 at 09:19:49AM +0200, Martin Liška wrote:
> >> * write.c (compress_debug): Compress also ".gnu.debuglto_.debug_"
> >> if the compression algorithm is different from zlib-gnu.
> >
> > OK, choosing to skip compression for zlib-gnu is a reasonable approach
> > given that zlib-gnu has the clunky .debug_* to .zdebug_* section
> > renaming scheme. I'm going to commit your patch, but then enable
> > zlib-gnu with a followup patch of mine that doesn't rename the lto
> > debug sections. ld.bfd and the binutils work fine without renaming,
> > but there may be some other reason why zlib-gnu must have .zdebug
> > sections. If that turns out to be the case, my patch below can be
> > reverted.
>
> Makes sense. On the other hand, I would somehow slowly (but surely) make zlib-gnu
> obsolete. What do you think?
I don't see that happening in a hurry. We'd want to keep the ability
to handle zlib-gnu compressed object files for as long as such objects
are still in use. So decompression will stay supported for a long
time, and since we need to test decompression support it is also
necessary to support compression.
> For the future, people will likely move to the more
> modern and faster zstd compression algorithm. We're planning doing that once
> new binutils is released in openSUSE Tumbleweed.
Sure, that's fine.
--
Alan Modra
Australia Development Lab, IBM
prev parent reply other threads:[~2022-10-04 13:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-29 13:35 Martin Liška
2022-09-30 0:20 ` Alan Modra
2022-09-30 7:19 ` Martin Liška
2022-10-04 8:07 ` Alan Modra
2022-10-04 8:12 ` Martin Liška
2022-10-04 13:41 ` Alan Modra [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=Yzw37djOG/I8DsP+@squeak.grove.modra.org \
--to=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=maskray@google.com \
--cc=mliska@suse.cz \
/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).