From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 7B8CD3858283; Tue, 27 Aug 2024 15:57:20 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 7B8CD3858283 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1724774240; bh=lZIINM3aWj+spi7uxi5rrKnubrpBly5bhiMz+464S48=; h=From:To:Subject:Date:In-Reply-To:References:From; b=eSN0NU6en6G18rqelmbZXQm2I7bdFIA9oESKhB+aYSEbc4PH/Qu1ag0FnsM7fB/QW gwUXxwTxZ/aSFCwwHZDEWiuTI5xasRE8ZzDS3kBGx2C0nqN8rD+g0/Zvtvdy/qASNu vjG+u+Ku+IcCQvU8leprpPTaevKoQ0INqOMN3fwQ= From: "simartin at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/116208] `__ct_base ` is used instead of the ctor name in warning's `inlined from` when using LTO Date: Tue, 27 Aug 2024 15:57:20 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 15.0 X-Bugzilla-Keywords: diagnostic, lto X-Bugzilla-Severity: normal X-Bugzilla-Who: simartin at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED 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: cc 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=3D116208 Simon Martin changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |simartin at gcc dot gnu.org --- Comment #8 from Simon Martin --- Thanks sjames@ for tagging me in https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D105483. My hunch is that we end up printing the internal name because of the if (!DECL_LANG_SPECIFIC (t)) in error.cc's dump_function_name (in which case I think the bug can't reall= y be fixed...), but I don't know how to be sure. How do you reproduce this? Are you configuring with --with-build-config=3Dbootstrap-lto?=