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 103F9385B832; Mon,  6 Apr 2020 10:54:05 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 103F9385B832
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
 s=default; t=1586170445;
 bh=BgtyB338AP7r9v6TxwQV6gzazZsx6xkkiuv4VzUn96Q=;
 h=From:To:Subject:Date:In-Reply-To:References:From;
 b=SkzOJeSmAc+lpIMsu/XVnW6zSfnE3GXzuWY0XEzDIhHUecJHWk6WLk/IacH4AXTLD
 7aJz5nWC4UrQJZJzI3k4zNy9mlnlqB+t53krIOCHmQmLrN/o0jkpeyR07LhE8J/yVL
 sJOCjxLVUMMlY9iCUD/EKjM3m4MOFpftp8Fn+PnY=
From: "andrew.burgess at embecosm dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/94474] Incorrect DWARF range information for inlined
 function
Date: Mon, 06 Apr 2020 10:54:04 +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: <bug-94474-4-6KKfcdOdUh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-94474-4@http.gcc.gnu.org/bugzilla/>
References: <bug-94474-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
X-BeenThere: gcc-bugs@gcc.gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gcc-bugs mailing list <gcc-bugs.gcc.gnu.org>
List-Unsubscribe: <http://gcc.gnu.org/mailman/options/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-request@gcc.gnu.org?subject=help>
List-Subscribe: <http://gcc.gnu.org/mailman/listinfo/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Apr 2020 10:54:05 -0000

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D94474

--- Comment #2 from Andrew Burgess <andrew.burgess at embecosm dot com> ---
Sorry for including the wrong DWARF dump output in the bug report.  I too h=
ad
seen the DW_AT_GNU_entry_view using a more recent binutils.

When you pose the question:

  I am not sure if there are any view numbers when the inline has multiple
ranges, (I dont remember)

I think you're asking do we get DW_AT_GNU_entry_view when we have multiple
ranges.  And the answer is yes, this case already has multiple ranges (it h=
as a
DW_AT_ranges, which contains multiple ranges), and this is super confusing,
because each range could, I guess, could have a different view number for i=
ts
start, right?

It seems that, when a debug entity has a single range defined within the en=
tity
then we need a start and end view number.

When a debug entity makes use of separate range information, each range will
need its own start and end view number.

If the above requires new DWARF extensions, then GCC might just decide to t=
ry
and make the best with the version of DWARF it currently has available.=