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 439EB3858D38; Mon,  6 Feb 2023 14:13:34 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 439EB3858D38
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1675692814;
	bh=FiFV+AiX8MKZ/A8LwCIlYct9yQ1Gm97oboHuRqbSikE=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=AZrFQNnlMpFO/ie80HYXRWum9+qurAsx38hajZP8KbXrC8kw98tvNUCbqC+pzsAOC
	 Yb1XNQbBferJuOtG5hb6NIHPtqCv8RjXZMM21/FObA5FzZy8v5F8+54QNRuXGxn0Ss
	 Y+VimtZuQzB20va1YCbAVBl9my8xmfVAz7hWoI7U=
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/108630] build failure with LTO enabled
Date: Mon, 06 Feb 2023 14:13:34 +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: redi 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-108630-4-ZwFDyLgCTp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-108630-4@http.gcc.gnu.org/bugzilla/>
References: <bug-108630-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=3D108630

--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> ---
The uses of .symver in src/c++98/compatibility.cc are hard to change, so th=
is
isn't going to be fixed any time soon.

I suggest simply not using LTO for libstdc++.=