From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2713 invoked by alias); 31 Oct 2003 15:19:29 -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 2700 invoked from network); 31 Oct 2003 15:19:28 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sources.redhat.com with SMTP; 31 Oct 2003 15:19:28 -0000 Received: from drow by nevyn.them.org with local (Exim 4.24 #1 (Debian)) id 1AFb3f-0008W7-Ht; Fri, 31 Oct 2003 10:19:27 -0500 Date: Fri, 31 Oct 2003 15:19:00 -0000 From: Daniel Jacobowitz To: Andrew Cagney Cc: binutils@sources.redhat.com, gdb@sources.redhat.com Subject: Re: A gdb+bfd string pool? Message-ID: <20031031151927.GA32700@nevyn.them.org> Mail-Followup-To: Andrew Cagney , binutils@sources.redhat.com, gdb@sources.redhat.com References: <3FA27C9B.1000702@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3FA27C9B.1000702@redhat.com> User-Agent: Mutt/1.5.1i X-SW-Source: 2003-10/txt/msg00346.txt.bz2 On Fri, Oct 31, 2003 at 10:15:39AM -0500, Andrew Cagney wrote: > Hello, > > GDB, to contain its run-time size is, uses gdb/bcaches where ... > /* A bcache is a data structure for factoring out duplication in > read-only structures. You give the bcache some string of bytes S. > If the bcache already contains a copy of S, it hands you back a > pointer to its copy. Otherwise, it makes a fresh copy of S, and > hands you back a pointer to that. In either case, you can throw > away your copy of S, and use the bcache's. > One notable feature of this mechanism is that it lets you eliminate > string equality comparisons - equal bcache values implies equal strings. > > Now, if I'm reading the BFD elf reader correctly, elf-strtab implements > a similar mechanism (But I think it is currently only used by the linker?). > > Should/could BFD export a string pool that GDB could use and then use > that for any slurped symbol names? Well, if so, it should go in libiberty - and in fact, is the hash table in libiberty in any way unsuited to replace bcache? -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer