From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 9EF023858D32; Mon, 16 Jan 2023 12:35:34 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 9EF023858D32 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1673872534; bh=t4zhyIdGb5I/IICTdLorxtlw2/S6vrxX+ZoHq7Gygv8=; h=From:To:Subject:Date:In-Reply-To:References:From; b=PM43pqsAdiJyImfxXpzkoJC2kmUtJiWc2kxk8eXrF3w3t7BAjIpFISIRuuuPnuVkR MpftrD6KW8sZKDUTXeUbuG/lHxZjNNHpNvqh0lWyPg8CBl42J8B+DjuLkkhswyA+gU KxlyvyhzrLW69r4lqt9OdAjRhVSRDcqo5TpYtx9s= From: "marxin at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/107950] partial LTO linking of libbackend.a: gcc/gcc-rich-location.cc:207: undefined reference to `range_label_for_type_mismatch::get_text(unsigned int) const' Date: Mon, 16 Jan 2023 12:35:32 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: bootstrap X-Bugzilla-Version: 13.0 X-Bugzilla-Keywords: lto X-Bugzilla-Severity: normal X-Bugzilla-Who: marxin 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: 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=3D107950 --- Comment #8 from Martin Li=C5=A1ka --- (In reply to Jan Hubicka from comment #7) > Thanks for looking into the incremental link of libbackend. I had it in my > tree for a while but never got around implementing correct way to enable = it > only during bootstrap since host compiler may not support it. It would be > nice to have it in since it should reduce WPA memory use and also test th= is > code path. Feel free to grab my initial patch in c#0 and upstream it. I tried that some time ago in the following email thread: https://gcc.gnu.org/pipermail/gcc/2021-May/236096.html >=20 > I also think it is the case where partial linking makes the symbol to be > pulled into LTO binary at the initial link time. It should be optimized > away if linker was not complaining. Optimize away during the partial linking? So you think it's a GCC issue whe= n it comes to partial linking?=