From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id BBE7B3858C83; Tue, 28 Feb 2023 13:11:57 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org BBE7B3858C83 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1677589917; bh=u2j/8BVIAaMebP+aCCJVrxXEwNqpVqt9T58OIrFjBq0=; h=From:To:Subject:Date:In-Reply-To:References:From; b=sFi/wMOEI8AmvOAPtx0ZM2kemzJy+nBpibUMiolXsmeo/1Wh9UP2FmGZYAQ7uN+QT fWPd/DKomVMlaehzw/9mCvuE/bWBN9NDnshAEnGU0Hy89b0dZKvvKSigt1i0iHR70i sBRY/sRvVa5jOf1C64GvzL7i3jsAXz/MOChmfOns= From: "redi at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/108630] build failure with LTO enabled Date: Tue, 28 Feb 2023 13:11:56 +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: see_also 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=3D108630 Jonathan Wakely changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://gcc.gnu.org/bugzill | |a/show_bug.cgi?id=3D92192 --- Comment #5 from Jonathan Wakely --- (In reply to Jonathan Wakely from comment #4) > I suggest simply not using LTO for libstdc++. LTO will almost certainly break src/c++98/globals_io.cc so I don'tthink we = can support building libstdc++ with LTO for now.=