From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 08D33385C6EE; Thu, 28 Mar 2024 00:17:07 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 08D33385C6EE DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1711585028; bh=zB6uBzPUQoltRAzdfzSJwjVIc7CHI1h3maA7RzEq2xo=; h=From:To:Subject:Date:In-Reply-To:References:From; b=mgk6EPXGTdQqI18i7CDWiHrpAdj0Coz/ePz4ssVPmDwIe/sNOrQc5m21sQRk7lnYS y5kubXcAPSZTdSQb28Oly5HqeZxkp/gv0RddtVibKX1lj9Zbeh4D/gleapAMERTbPF j2tC/NoEvyjeiaA+kd6cVDtYaGcsV4aru7DU+Kq4= From: "xry111 at gcc dot 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:16:46 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: lto X-Bugzilla-Version: 13.2.1 X-Bugzilla-Keywords: lto X-Bugzilla-Severity: normal X-Bugzilla-Who: xry111 at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc everconfirmed keywords Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D114505 Xi Ruoyao changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2024-03-28 CC| |xry111 at gcc dot gnu.org Ever confirmed|0 |1 Keywords| |lto --- Comment #1 from Xi Ruoyao --- Confirmed as I've seen it before. At least we should turn it into a "norma= l" 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 wit= h 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.=