public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "eschwartz93 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/114505] static archives built with gcc --without-zstd cause ICE when read by gcc with zstd support
Date: Thu, 28 Mar 2024 00:40:03 +0000	[thread overview]
Message-ID: <bug-114505-4-CGQGHs4YMK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114505-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114505

--- Comment #12 from Eli Schwartz <eschwartz93 at gmail dot com> ---
(In reply to Xi Ruoyao from comment #1)
> Confirmed as I've seen it before.  At least we should turn it into a
> "normal" error message instead of ICE.
> 
> But note that even "downgrading the compression algorithm" is supported, it
> won't really help rolling-release distros.  When GCC itself is upgraded with
> a LTO API version change, all previous LTO static archives will be unusable
> anyway.  Generally the distros should not ship LTO static archives at all.

Agreed, figuring out how to solve that is an open ticket too:
https://bugs.gentoo.org/926120

Still would like to solve the zstd case :D especially since I am sure given the
flexibility of a from-source distro there will be users who insist they'd
rather rebuild the entire OS on a GCC upgrade, so reducing the compression
algorithm edge case will come in use.


(In reply to Andrew Pinski from comment #2)
> On the input side:
> Wait this should not happen.
> 
>       lto_end_uncompression (stream,
>                              file_data->lto_section_header.get_compression
> ());


I cannot swear this was the case but the error very specifically occurred as
part of a Gentoo profile change that caused zstd to be enabled.

The version of zstd should be the same, at least...

  parent reply	other threads:[~2024-03-28  0:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-28  0:06 [Bug lto/114505] New: " eschwartz93 at gmail dot com
2024-03-28  0:16 ` [Bug lto/114505] " xry111 at gcc dot gnu.org
2024-03-28  0:21 ` pinskia at gcc dot gnu.org
2024-03-28  0:23 ` pinskia at gcc dot gnu.org
2024-03-28  0:24 ` pinskia at gcc dot gnu.org
2024-03-28  0:25 ` xry111 at gcc dot gnu.org
2024-03-28  0:26 ` sjames at gcc dot gnu.org
2024-03-28  0:29 ` pinskia at gcc dot gnu.org
2024-03-28  0:32 ` pinskia at gcc dot gnu.org
2024-03-28  0:32 ` pinskia at gcc dot gnu.org
2024-03-28  0:34 ` pinskia at gcc dot gnu.org
2024-03-28  0:35 ` pinskia at gcc dot gnu.org
2024-03-28  0:40 ` eschwartz93 at gmail dot com [this message]
2024-03-28  0:45 ` pinskia at gcc dot gnu.org
2024-03-28  8:28 ` rguenth at gcc dot gnu.org

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=bug-114505-4-CGQGHs4YMK@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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).