From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31014 invoked by alias); 23 Jul 2006 22:03:33 -0000 Received: (qmail 31005 invoked by uid 22791); 23 Jul 2006 22:03:32 -0000 X-Spam-Check-By: sourceware.org Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.31.1) with ESMTP; Sun, 23 Jul 2006 22:03:30 +0000 Received: from drow by nevyn.them.org with local (Exim 4.54) id 1G4m2q-0004Ls-PI; Sun, 23 Jul 2006 18:03:28 -0400 Date: Sun, 23 Jul 2006 22:03:00 -0000 From: Daniel Jacobowitz To: Mark Kettenis Cc: gdb-patches@sourceware.org Subject: Re: [RFC] Add expat to the GDB sources Message-ID: <20060723220328.GA16590@nevyn.them.org> Mail-Followup-To: Mark Kettenis , gdb-patches@sourceware.org References: <20060718134048.GA15685@nevyn.them.org> <20060718135718.GA16876@nevyn.them.org> <200607232151.k6NLpuAC014332@elgar.sibelius.xs4all.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200607232151.k6NLpuAC014332@elgar.sibelius.xs4all.nl> User-Agent: Mutt/1.5.11+cvs20060403 X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2006-07/txt/msg00321.txt.bz2 On Sun, Jul 23, 2006 at 11:51:56PM +0200, Mark Kettenis wrote: > My main concern here, is how much the new xml-based developments this > will grow GDB. Linking the final gdb executable is already getting > problematic on small memory systems. How big is libexpat.a, and how > much does a flash-enabled GDB grow? Ah, that's why I picked expat, instead of the more convenient DOM implementations (which are huge). On x86_64, libexpat.a is 600K, with debugging information enabled. Code size is only about 140K of that. For comparison, remote.o is 70K code size and 280K with debug info. So it's two to three new files worth of code - in my opinion, this is an acceptable cost. What do you think - workable? > Another question I have is about how we think to handle expat in the > future. Is expat still undergoing much development? Are you planning > to update expat regularly? Not particularly. Expat 2.0.0 was released in January 2006, so it's still maintained, but there haven't been any releases since then, so it's not churning particularly. I don't think it likely that we'll need any cutting edge features from it, either. My plan was to import 2.0.0 and leave it alone as much as possible, unless we encountered a bug in it. -- Daniel Jacobowitz CodeSourcery