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 29D583856DF7; Fri, 20 May 2022 15:13:30 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 29D583856DF7
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: Fri, 20 May 2022 15:13:29 +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: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-29105-4717-AV0R1arK9n@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
X-BeenThere: gdb-prs@sourceware.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gdb-prs mailing list <gdb-prs.sourceware.org>
List-Unsubscribe: <https://sourceware.org/mailman/options/gdb-prs>,
 <mailto:gdb-prs-request@sourceware.org?subject=unsubscribe>
List-Archive: <https://sourceware.org/pipermail/gdb-prs/>
List-Help: <mailto:gdb-prs-request@sourceware.org?subject=help>
List-Subscribe: <https://sourceware.org/mailman/listinfo/gdb-prs>,
 <mailto:gdb-prs-request@sourceware.org?subject=subscribe>
X-List-Received-Date: Fri, 20 May 2022 15:13:30 -0000

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

--- Comment #6 from Tom Tromey <tromey at sourceware dot org> ---
> So having debug info for libc is important for reproducing this

I suppose it has to be a libc that has debug info but does not
use .gdb_index.

> When doing "print sizeof(short)", it eventually looks up the "int" type,
> (since short means "short int")

That seems peculiar.

> Previously with partial symbols, I don't think we had entries for those.

Probably they got unified by the bcache.

> What is the problem here?
>=20
> - Do we want entries for base types in the index?
> - Should the type search algorithm expand all CUs that contain a matching
> type?  Couldn't it stop at the first CU that has a matching type?

I think you can't really avoid base types in the index.
That seems like it would open up a number of problems.

Maybe just stopping on the first type would be ok.  We'll have to investiga=
te.
Otherwise some kind of de-duplication can be done; though I'd prefer
to push this kind of thing from read-time to lookup-time.

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