From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31658 invoked by alias); 27 Mar 2013 16:58:56 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 31396 invoked by uid 89); 27 Mar 2013 16:58:48 -0000 X-Spam-SWARE-Status: No, score=-7.1 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,RCVD_IN_DNSWL_HI,RCVD_IN_HOSTKARMA_W,RP_MATCHES_RCVD,SPF_HELO_PASS autolearn=ham version=3.3.1 Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Wed, 27 Mar 2013 16:58:46 +0000 Received: from int-mx02.intmail.prod.int.phx2.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id r2RGwj1G001774 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Wed, 27 Mar 2013 12:58:45 -0400 Received: from barimba (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by int-mx02.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id r2RGwi7q001199 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Wed, 27 Mar 2013 12:58:44 -0400 From: Tom Tromey To: Phil Muldoon Cc: "gdb-patches\@sourceware.org" Subject: Re: [patch][python] 1 of 5 - Frame filter Python C code changes. References: <513E56EC.2050802@redhat.com> <87vc8kzd5d.fsf@fleche.redhat.com> <5151B6DE.80703@redhat.com> Date: Wed, 27 Mar 2013 18:36:00 -0000 In-Reply-To: <5151B6DE.80703@redhat.com> (Phil Muldoon's message of "Tue, 26 Mar 2013 14:55:26 +0000") Message-ID: <87boa4hj98.fsf@fleche.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-SW-Source: 2013-03/txt/msg01025.txt.bz2 >>>>> "Phil" == Phil Muldoon writes: Phil> I think a frame stash using a hash table is doable, but I think it is Phil> overkill because I am extremely suspicious of the frame to frame Phil> object code. I assume you are going to fix the frame to frame object code instead? And this will fix the 20% penalty? I'm not totally sure it should be "instead" rather than "as well as", since it seems like some gdb.Frame access patterns will have bad behavior with the current stash. Tom