From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id A0E863858C74; Thu, 2 Feb 2023 10:30:43 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org A0E863858C74 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1675333843; bh=KhIvvmrUVm2mtJsTPearsgNVMP5Bkb2BtZ6Qx/NqAaI=; h=From:To:Subject:Date:In-Reply-To:References:From; b=quo3X7rLcIzTnS52PR/4uG5CMUfbBJhJdi+hBDmTKVK2kFrnOXUdPstyjIfxg9Pq+ keCEG7tHcj9lWBAOX646BsaUTvjhwASd8B2a5YLsJiQTl7Vp5ePl5vAgZzehPOCT9P 38BaARU9eR2OVzFB6AET2rfRiKvxlAicEhPuBylU= From: "a.heider at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/108630] build failure with LTO enabled Date: Thu, 02 Feb 2023 10:30:43 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Version: 12.2.0 X-Bugzilla-Keywords: build, lto X-Bugzilla-Severity: normal X-Bugzilla-Who: a.heider at gmail dot com 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: 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=3D108630 --- Comment #3 from Andre Heider --- While this is a libstdc++ related LTO issue, there's at least another libgcc one, see the linked bug #60160. With the workaround here and the patch there the LTOed target libraries look alot more sane, but I can't judge if that solves everything that needs to be solved. Based on some light testing on qemu that's at least a "works for me now" st= ate ;)=