From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 4089039450EB; Mon, 6 Apr 2020 14:16:05 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 4089039450EB DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1586182565; bh=Z7zLnfqEKnXdrAQazZcAhEpGkeS4Ecu7Ews8KX771NI=; h=From:To:Subject:Date:In-Reply-To:References:From; b=aYR0YXD3qAXiSm5pUclwqS9WxbjyKbtW8V6cC73zgsJOFnzCUGndMav2XAVWFfMqk JV2oDZUJqaRhQ8qWDUTFUOqGu9YMtRmDXZYuM+aRA9fWIz2aSxS61sxJ+VJsg6cO3N DzipyUVYAOLWIQK8xkm2w1j4+2J4gMUrNsoe+yE0= From: "andrew.burgess at embecosm dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/94474] Incorrect DWARF range information for inlined function Date: Mon, 06 Apr 2020 14:16:05 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: debug X-Bugzilla-Version: 9.2.0 X-Bugzilla-Keywords: wrong-debug X-Bugzilla-Severity: normal X-Bugzilla-Who: andrew.burgess at embecosm dot com 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: 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 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Apr 2020 14:16:05 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D94474 --- Comment #8 from Andrew Burgess --- Bernd,=20 Please could you keep discussion of GDB patches to the GDB mailing list unl= ess it is required to move this bug forward. In this bug I make the claim that the DWARF GCC produces is not correct. So far I don't think you are disagreeing with that. You are, I think, proposing that we should add range end view numbers to the range table. I'm not disagreeing that this would solve the problem. However, Right now I don't think such a feature is currently in the DWARF standard, maybe it exists as part of a DWARF proposal? Or maybe as a GCC extension? = I don't know. The question I'm asking to the wider GCC community would be, given the (I claim) current incorrect DWARF, should GCC be changed to produce something better using existing standard DWARF? Should a new GCC DWARF extension be invented? I certainly don't claim to have the answer here, but hopefully someone else might have a concrete proposal.=