From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 51CC83858C83; Mon, 23 Jan 2023 10:19:58 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 51CC83858C83
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1674469198;
	bh=q6YJdjKXBlIzIQOsfGsqFDhz7zQtUlOfxxe/B5jLx3A=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=fPuFTvvS+QgTw7dmn5J4tRvGz99UL+28bLPvuUXtxuumOUXkYjs6/JoBv7uqxZ7qr
	 l8ot6JfFPidj/Vmr0bJw3mJPm3MQQS+8l60USGvLN0Vo8Q0NuM2Dna/TwP/UkCPUDx
	 xVKREq619PJK4LaT3E1oTeGfv0lL/3+B7stXfEbI=
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.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, 23 Jan 2023 10:19:55 +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: <bug-107950-4-DEiSe0GBaM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-107950-4@http.gcc.gnu.org/bugzilla/>
References: <bug-107950-4@http.gcc.gnu.org/bugzilla/>
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: <gcc-bugs.sourceware.org>

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

--- Comment #12 from Martin Li=C5=A1ka <marxin at gcc dot gnu.org> ---
> So moving range_label_for_type_mismatch *and* binary_op_rich_location to
> c/cp/c-family might be a fix for this; I'm not sure.

I don't think so as any other (non-C family) FE will fail to link against
libbackend.a.=