From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24402 invoked by alias); 1 Jun 2004 01:31:03 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 24386 invoked from network); 1 Jun 2004 01:31:03 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org with SMTP; 1 Jun 2004 01:31:03 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.10/8.12.10) with ESMTP id i511V2i7005651 for ; Mon, 31 May 2004 21:31:02 -0400 Received: from localhost.redhat.com (porkchop.devel.redhat.com [172.16.58.2]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id i511V2030187; Mon, 31 May 2004 21:31:02 -0400 Received: from gnu.org (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 157232B9D; Mon, 31 May 2004 21:30:59 -0400 (EDT) Message-ID: <40BBDC52.7060106@gnu.org> Date: Tue, 01 Jun 2004 01:31:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-GB; rv:1.4.1) Gecko/20040217 MIME-Version: 1.0 To: Daniel Jacobowitz Cc: Randolph Chung , gdb-patches@sources.redhat.com Subject: Re: [patch/rfc] New program_changed event, cleanup some HPUXHPPA mess References: <20040519204003.GU566@tausq.org> <40AE4F0C.6050407@gnu.org> <20040521190242.GB7207@tausq.org> <40AE6260.2090205@gnu.org> <20040526052753.GU7207@tausq.org> <20040526132546.GB7594@nevyn.them.org> <20040526153530.GZ7207@tausq.org> <40B4D9D6.7040302@gnu.org> <20040528234344.GA11062@nevyn.them.org> <40BB8AD5.3020504@gnu.org> <20040531204318.GA29687@nevyn.them.org> In-Reply-To: <20040531204318.GA29687@nevyn.them.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-06/txt/msg00000.txt.bz2 > On Mon, May 31, 2004 at 03:43:17PM -0400, Andrew Cagney wrote: > >>> We'll find out - the change will put the additional lookups will put the >>> symtab under extra strain. > > > I have trouble thinking anything will break. Both minimal and full > symbol lookups are O(1) already and have been for at least two years. In that case, since the cache was originally added to work around what was a >>O(1) lookup, it should no longer be needed. Of course, if that isn't the case, we'll find out. When it comes to fixing the problem, we can extend/tighten the symtab interface so that other code can also benefit. That is where the cache mechanism belongs - not in hp specific code. Andrew