From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4871 invoked by alias); 29 Nov 2012 01:24:40 -0000 Received: (qmail 4853 invoked by uid 22791); 29 Nov 2012 01:24:39 -0000 X-SWARE-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RCVD_IN_BRBL_LASTEXT,RCVD_IN_HOSTKARMA_YE,RCVD_IN_MSPIKE_BL,RCVD_IN_MSPIKE_L3,RCVD_IN_NJABL_RELAY,RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from new.toad.com (HELO new.toad.com) (209.237.225.253) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 29 Nov 2012 01:24:33 +0000 Received: from new.toad.com (localhost.localdomain [127.0.0.1]) by new.toad.com (8.12.9/8.12.9) with ESMTP id qAT1OQ2N007037; Wed, 28 Nov 2012 17:24:26 -0800 Message-Id: <201211290124.qAT1OQ2N007037@new.toad.com> To: Tom Tromey cc: GDB Development Subject: Re: RFC: free pending blocks In-reply-to: <87vccp8lm8.fsf@fleche.redhat.com> References: <87vccp8lm8.fsf@fleche.redhat.com> Comments: In-reply-to Tom Tromey message dated "Wed, 28 Nov 2012 14:26:39 -0700." Date: Thu, 29 Nov 2012 01:24:00 -0000 From: John Gilmore X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2012-11/txt/msg00088.txt.bz2 That's a nice improvement. Would it perhaps be better to just allocate these pending blocks on their own obstack, so they can all be freed at once without doing a lot of pointer walking? (Or, deallocate them as they are walked to make the blockvector, to improve cache locality, rather than in a separate pointer chain walk.) I don't know how many such blocks are likely to exist in typical programs, but I suspect there could be thousands. John