From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sourceware-bugzilla@sourceware.org>
Received: by sourceware.org (Postfix, from userid 48)
	id B5BAC3858404; Thu,  6 Oct 2022 20:44:08 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B5BAC3858404
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org;
	s=default; t=1665089048;
	bh=3qJ0tUQxRH9f+KttJYNd7wuKBd6wCWoRQmik+w5K2eY=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=xsRVHHXKoAXvYhf3NYLkMVNnjeZ/IKNUB4mpliI9XYGMHcAuEHPiGriumvp/HLAsf
	 8Km3w+WnbWk55Ly5tMIr011t3Z2hCsSMGSiz3YDjuokww7Bu2lucQ8uNeeZQmoO7M9
	 ClPcT2i9Vqf+XbNrzXwftWGzGQSQlClQk3qMzQqI=
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug symtab/29105] new DWARF reader still slow
Date: Thu, 06 Oct 2022 20:44:08 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: symtab
X-Bugzilla-Version: HEAD
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tromey at sourceware dot org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: tromey at sourceware dot org
X-Bugzilla-Target-Milestone: 13.1
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-29105-4717-hzbOHaDUom@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-29105-4717@http.sourceware.org/bugzilla/>
References: <bug-29105-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <gdb-prs.sourceware.org>

https://sourceware.org/bugzilla/show_bug.cgi?id=3D29105

--- Comment #13 from Tom Tromey <tromey at sourceware dot org> ---
(In reply to Joel Brobecker from comment #12)

> I'm wondering whether this PR is still about the performance of the new
> DWARF reader, or is it now about some bug(s?). As this PR is marked as
> targeting GDB 13, would you mind telling us more about what's left to do =
for
> it?

With the new reader, gdb seems to expand too many CUs in some cases,
and we should probably fix this before 13.  Comment #5 describes the
scenario but I imagine it can be reproduced in other ways as well.

--=20
You are receiving this mail because:
You are on the CC list for the bug.=