From: Andrew Cagney <ac131313@cygnus.com>
To: Jim Blandy <jimb@cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA: relax restrictions on per-architecture data registration
Date: Wed, 06 Jun 2001 09:35:00 -0000 [thread overview]
Message-ID: <3B1E5AAF.6070005@cygnus.com> (raw)
In-Reply-To: <np4rtt659m.fsf@zwingli.cygnus.com>
> Okay. My first patch was exactly that, but then I felt like I was
> assuming that all per-architecture data would be registered by the
> time initialization was done, which wasn't a documented requirement in
> gdbarch.h. So I made it more dynamic.
Ah.
My e-mail actually contained a white lie. At present it really does:
o compile in a static dummy architecture and
wire things to use that
o call _initialize_*()
o create the real architecture
the first step, a hack, is to get around a chicken/egg problem with the
current GDB code. gdbtypes.[hc] assumes that there is an architecture
_before_ anything has been initialized (ulgh).
As usual, the long term objective is to eliminate the hack :-) Tweeking
the ``create the real architecture'' code to create the data vector in
both the multi-arch and non-multi-arch cases will actually take this a
step closer - chunks of GDB can be rewritten to just use the
register_gdbarch_data() mechanism.
I'll add a comment to top.c / gdbint.texinfo to explain this.
Andrew
next prev parent reply other threads:[~2001-06-06 9:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20010601233233.C19845E9CB@zwingli.cygnus.com>
2001-06-01 20:54 ` PATCH: " Jim Blandy
2001-06-06 4:59 ` RFA: " Andrew Cagney
2001-06-06 7:39 ` Jim Blandy
2001-06-06 9:35 ` Andrew Cagney [this message]
2001-06-06 6:34 ` Andrew Cagney
2001-06-06 9:59 ` RFA: initialize per-arch data in startup_gdbarch Jim Blandy
2001-06-06 10:13 ` Andrew Cagney
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=3B1E5AAF.6070005@cygnus.com \
--to=ac131313@cygnus.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@cygnus.com \
/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