From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4674 invoked by alias); 5 Oct 2007 16:54:26 -0000 Received: (qmail 4666 invoked by uid 22791); 5 Oct 2007 16:54:26 -0000 X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (65.74.133.4) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 05 Oct 2007 16:54:23 +0000 Received: (qmail 8534 invoked from network); 5 Oct 2007 16:54:22 -0000 Received: from unknown (HELO localhost) (jimb@127.0.0.2) by mail.codesourcery.com with ESMTPA; 5 Oct 2007 16:54:22 -0000 To: gdb-patches@sourceware.org Subject: Re: [rfc] Pre-parse XML target descriptions References: <20071005153350.GA23583@caradoc.them.org> From: Jim Blandy Date: Fri, 05 Oct 2007 16:54:00 -0000 In-Reply-To: <20071005153350.GA23583@caradoc.them.org> (Daniel Jacobowitz's message of "Fri, 5 Oct 2007 11:33:50 -0400") Message-ID: User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-IsSubscribed: yes 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 X-SW-Source: 2007-10/txt/msg00057.txt.bz2 Actually, the mechanism I suggested could be incorporated in any case. The GDB build process should always check the checksums of the XML input files against those stored in the files built from them, simply to remind developers when they need to regenerate the C files. It's just a good general principle for dealing with pre-generated files.