From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19683 invoked by alias); 28 Mar 2007 18:09:12 -0000 Received: (qmail 19664 invoked by uid 22791); 28 Mar 2007 18:09:11 -0000 X-Spam-Check-By: sourceware.org Received: from igw1.br.ibm.com (HELO igw1.br.ibm.com) (32.104.18.24) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 28 Mar 2007 19:09:04 +0100 Received: from mailhub1.br.ibm.com (mailhub1 [9.18.232.109]) by igw1.br.ibm.com (Postfix) with ESMTP id 72CED14811B for ; Wed, 28 Mar 2007 15:00:02 -0300 (BRT) Received: from d24av02.br.ibm.com (d24av02.br.ibm.com [9.18.232.47]) by mailhub1.br.ibm.com (8.13.8/8.13.8/NCO v8.3) with ESMTP id l2SI91Xo1224908 for ; Wed, 28 Mar 2007 15:09:01 -0300 Received: from d24av02.br.ibm.com (loopback [127.0.0.1]) by d24av02.br.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id l2SI7urM006074 for ; Wed, 28 Mar 2007 15:07:56 -0300 Received: from dyn531804.br.ibm.com (dyn531804.br.ibm.com [9.18.238.71]) by d24av02.br.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id l2SI7u6T006071 for ; Wed, 28 Mar 2007 15:07:56 -0300 Subject: Re: gdbarch script's purpose From: Luis Machado Reply-To: luisgpm@linux.vnet.ibm.com To: gdb@sourceware.org In-Reply-To: <20070328175818.GE3866@adacore.com> References: <1175104141.4417.3.camel@localhost> <20070328175818.GE3866@adacore.com> Content-Type: text/plain Date: Wed, 28 Mar 2007 18:09:00 -0000 Message-Id: <1175105340.4417.7.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.6.1 Content-Transfer-Encoding: 7bit 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: 2007-03/txt/msg00333.txt.bz2 On Wed, 2007-03-28 at 10:58 -0700, Joel Brobecker wrote: > > What is exactly the purpose of the gdb/gdbarch.sh script and where in > > the build process it's used? > > The purpose of this script is to generate the gdbarch.[hc] files. > Most of this file is very repetitive, so gdbarch.sh contains the > useful info, without any of the repetition, and then generates > the C files that we then compile. > > This script is not invoked during the build, but only manually, > when the gdbarch vector is modified. In other words, when we modify > gdbarch.sh, we rerun it, and commit a new version of gdbarch.[ch]. > It's clear now. Thanks for the info Joel. Regards, Luis