From: Luis Machado <luisgpm@linux.vnet.ibm.com>
To: gdb@sourceware.org
Subject: Re: gdbarch script's purpose
Date: Wed, 28 Mar 2007 18:09:00 -0000 [thread overview]
Message-ID: <1175105340.4417.7.camel@localhost> (raw)
In-Reply-To: <20070328175818.GE3866@adacore.com>
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
next prev parent reply other threads:[~2007-03-28 18:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-28 17:49 Luis Machado
2007-03-28 17:57 ` Joel Brobecker
2007-03-28 18:09 ` Luis Machado [this message]
2007-03-28 17:59 ` Daniel Jacobowitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1175105340.4417.7.camel@localhost \
--to=luisgpm@linux.vnet.ibm.com \
--cc=gdb@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox