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 C98203858C2C; Thu, 19 Jan 2023 12:36:52 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C98203858C2C
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1674131812;
	bh=/O2Jv6bQxdmohaSpfnkUed6+A/qa/zod6sFv86fGGEw=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=DchMZJshj14It1ybl6oO1W5HYqImp0Ti62sCN3R8wULG8JMIRqlpHASVZuXQP8qcK
	 sq2QMUeUhOLsWKWkj5VXjHorDo3JcUyoqHmbBx8y3gTGoWegY2VK2AAIJmN7mHgodF
	 ChHJ4W0C3FWRpfePgOBdNnW6pQtFspP7CEUgegJ4=
From: "rguenth 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: Thu, 19 Jan 2023 12:36:51 +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: rguenth 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-xfMzH0vEh9@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 #10 from Richard Biener <rguenth at gcc dot gnu.org> ---
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?

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/?=