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 99D433858C50; Fri, 20 Jan 2023 15:16:46 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 99D433858C50
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1674227806;
	bh=advxc8ZUrFssDYKN0EMLymnrLoaRTCYkhZKd5YsxHQ0=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=v731mYNE6ylJFcBubqc45Psy/ZkSodf7+EgCYo3rA3UEb6yT7npaBXhs5TsANg7oG
	 c7oi//LDJZeTIR9+VsrxubFh+R425BJ5oH/6C+4TaURH1KqPrAIVl5vdO45VHn4WNy
	 LCnD3xbCFp7+XdDzX91AXY4WjAngKe3jujiEto0Y=
From: "dmalcolm 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: Fri, 20 Jan 2023 15:16:45 +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: dmalcolm 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-3lbKnZHDSI@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 #11 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #10)
> I suppose a fix would be to provide a dummy implementation for
> range_label_for_type_mismatch::get_text in lto/, but I wonder how
> for example the fortran frontend avoids this issue?
>=20
> f951 has rich_location uses but no range_label_for_type_mismatch, it looks
> like range_label_for_* is used only from the C family frontends, so maybe
> another fix would be to move that class and implementation somewhere to
> c-family/?

AIUI class range_label_for_type_mismatch is only used:
  * by the C and C++ frontends (directly, and by
range_label_for_format_type_mismatch), and
  * by maybe_range_label_for_tree_type_mismatch::get_text in
gcc/gcc-rich-location.cc, which is used by class binary_op_rich_location in
gcc/gcc-rich-location.{h,cc}; the latter is only used by the C/C++ frontend=
s.

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.=