From: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
To: Khem Raj <raj.khem@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] gcc: enable zstd compression of LTO bytecode
Date: Thu, 03 Feb 2022 22:40:42 +0100 [thread overview]
Message-ID: <lyczk37hnp.fsf@ensc-virt.intern.sigma-chemnitz.de> (raw)
In-Reply-To: <CAMKF1sqp=KjKrgVb-FCLr29UTmxaGQ4_w=qrOU+6wvdR5NA_oQ@mail.gmail.com> (Khem Raj's message of "Thu, 3 Feb 2022 11:23:41 -0800")
Khem Raj <raj.khem@gmail.com> writes:
>> gcc-10+ supports zstd compression of LTO bytecode. Install the
>> corresponding package to enable this feature in a deterministic way.
>>
>> NOTE: previously built LTO object files (without this compression)
>> must be regenerated; gcc will fail else with
>>
>> | lto1: internal compiler error: original not compressed with zstd
>>
>> in this case.
>>
>> NOTE: it seems to be possible that zstd support is enabled non
>> deterministically (perhaps by host system pollution).
>>
>> I had the problem that the SDK gcc was built with zstd while the
>> cross gcc was built without it. Libraries (built by cross gcc and
>> uncompressed hence) could not be used with the SDK gcc.
>
> this means regenerating entire shared state isnt it ?
yes (at least when lto.inc is used (which is *not* by default)). When a
bad sstate really matters for 'master', perhaps there can be wait for a
change in glibc or so before applying this patch.
Or do you think that adding a DISTRO_FEATURE like 'lto-zstd' would make
sense? When this flag is missing, '--without-zstd' must be added to
EXTRA_OECONF. Also some early [vardeps] must be set (where?) to avoid
the sstate problem.
Globally enabling 'zstd' appears easier because drawbacks (costs for
compression + decompression) should be negligible for zstd.
Enrico
next prev parent reply other threads:[~2022-02-03 21:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 17:26 [PATCH] gcc: enable zstd compression of LTO bytecode Enrico Scholz
2022-02-03 19:23 ` [OE-core] " Khem Raj
2022-02-03 21:40 ` Enrico Scholz [this message]
2022-02-03 21:48 ` Khem Raj
2022-02-03 21:59 ` Richard Purdie
2022-02-03 22:11 ` Khem Raj
2022-02-03 22:21 ` Richard Purdie
2022-02-04 19:00 ` Enrico Scholz
2022-02-04 21:00 ` Khem Raj
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=lyczk37hnp.fsf@ensc-virt.intern.sigma-chemnitz.de \
--to=enrico.scholz@sigma-chemnitz.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@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