From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29982 invoked by alias); 12 Jun 2003 22:17:05 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 29969 invoked from network); 12 Jun 2003 22:17:04 -0000 Received: from unknown (HELO smtp3.Stanford.EDU) (171.64.14.172) by sources.redhat.com with SMTP; 12 Jun 2003 22:17:04 -0000 Received: (from root@localhost) by smtp3.Stanford.EDU (8.12.9/8.12.9) id h5CMH3Mx017702 for gdb@sources.redhat.com; Thu, 12 Jun 2003 15:17:03 -0700 (PDT) Received: from jackfruit.Stanford.EDU (jackfruit.Stanford.EDU [171.64.38.136]) by smtp3.Stanford.EDU (8.12.9/8.12.9) with ESMTP id h5CMGwRY017659; Thu, 12 Jun 2003 15:16:59 -0700 (PDT) Received: (from carlton@localhost) by jackfruit.Stanford.EDU (8.11.6/8.11.6) id h5CMGwH13686; Thu, 12 Jun 2003 15:16:58 -0700 X-Authentication-Warning: jackfruit.Stanford.EDU: carlton set sender to carlton@math.stanford.edu using -f To: Elena Zannoni Cc: Daniel Jacobowitz , gdb , Jim Blandy Subject: Re: DW_AT_specification and partial symtabs References: <20030612170545.GA16995@nevyn.them.org> <16104.47067.182016.78574@localhost.redhat.com> From: David Carlton Date: Thu, 12 Jun 2003 22:17:00 -0000 In-Reply-To: <16104.47067.182016.78574@localhost.redhat.com> Message-ID: User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Common Lisp) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2003-06/txt/msg00228.txt.bz2 On Thu, 12 Jun 2003 13:26:51 -0400, Elena Zannoni said: > I wonder, if we are not reaching the end of the usefulness of the > psymtabs. I mean, if we start making the psymtab reader behave like > the symtab reader, how much faster is that going to be, how much > smaller, etc. Yeah, I'm starting to wonder that, too. This particular situation is enough of an edge case that I'm actually tempted not to fix the psymtab reader until I get bug reports from users complaining about it, because if I do fix it completely then I'll probably make the psymtab reader slow, make it duplicate lots and lots of the functionality of the symtab reader, and do it in such a way as to cause code duplication that will lead to bugs as the two versions slip out of sync. So I'm tempted to let things be for now, and wait until .debug_pubtypes comes along to save the day. I guess another possibility would be to merge the symtab reader and psymtab reader, and have there be some variable 'reading_psyms' or whatever to control what sort of symbols we're creating, how deeply we descend into trees, etc. It would be interesting to find out the following: 1) How much is the savings for building a psymtab vs. building a symtab? 2) Where is that savings coming from? If the savings largely comes from not descending into the bodies of functions, then the current structure should go: we should just merge the psymtab and symtab readers, but have some flag floating around that controls whether or not we descend into bodies of functions. David Carlton carlton@math.stanford.edu