From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 6E012385DC1C; Sun, 17 May 2020 09:05:41 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 6E012385DC1C DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1589706341; bh=DxMLqtAWm1RthfC5GxMGWUYQ3rxILYQzE8mBd2l1UHM=; h=From:To:Subject:Date:In-Reply-To:References:From; b=HyTWFxagjmSN7pOm892MurYTSCX2m09ZxBdVA9MOlh8Ojn/8BGhkK0EI456DDWCSJ XEhp9sc9zE1PoO0lWgNzgfJUjx4GaBHqmN7sZZ8B5dyxnXIRsTtyql+DJRabnPkSb3 ktmkOH6eZZbxyqsMaZcZ+Qo1QUBu7WNthrXRJcCs= From: "bernd.edlinger at hotmail dot de" To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/94474] Incorrect DWARF range information for inlined function Date: Sun, 17 May 2020 09:05:41 +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: bernd.edlinger at hotmail dot de 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: Sun, 17 May 2020 09:05:41 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D94474 --- Comment #13 from Bernd Edlinger --- Hi Andrew, You are right about the instruction re-ordering, that is done in a compiler pass, which simply re-orders RTL instruction lists. But I think when the code motion happens, we just have no easy access to the range markers. And it may be the case that this is-stmt location mentions a register value that is indeed the parameter of the inline function, so it may be no instruction but only a side note, to the debugger, that a certain value would be already here available in a certain register. Also that is only a vague guess, since although I did already a number of gcc patches, I learn new things each time :-) Bernd.=