From: Stan Shebs <stanshebs@earthlink.net>
To: Michael Eager <eager@eagercon.com>
Cc: gdb@sources.redhat.com
Subject: Re: What's an annex? stratum?
Date: Sat, 23 Jun 2007 18:57:00 -0000 [thread overview]
Message-ID: <467D6D1F.7090507@earthlink.net> (raw)
In-Reply-To: <467D5FEF.7010900@eagercon.com>
Michael Eager wrote:
> Looking at target.c, I see some terms which are less
> than clear: annex and stratum. Could someone tell me
> what these mean?
"Annex" is apparently an introduction of Andrew's from 2004, does kind
of look like an address space addition, although not clear that it's
fully implemented.
"Stratum" is an old concept, merely a way to talk about different levels
of the target stack. In practice, the stacking concept isn't as clean as
it must have seemed initially; sometimes you really want to run a target
op in a vector down in the stack, sometimes you want to replace a target
vector in the middle. So we introduce strata as a way to find a
mid-stack target vector of a desired type. First big block comment in
target.h goes into a bit more detail.
>
> Aside: there are comments in the gdb code which tell me
> that the previous code did things badly and that the new
> scheme is better. Usually there's no description of the
> new scheme. I don't know about others, but I find these
> comments are both distracting and unhelpful.
Probably not much consolation, but I'm having the same trouble with
Mozilla sources these days. :-)
Stan
next prev parent reply other threads:[~2007-06-23 18:57 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-23 18:01 Michael Eager
2007-06-23 18:57 ` Stan Shebs [this message]
2007-06-23 19:08 ` Michael Eager
2007-06-23 19:47 ` Eli Zaretskii
2007-06-23 20:51 ` Michael Eager
2007-06-23 21:23 ` Daniel Jacobowitz
2007-06-23 21:40 ` Michael Eager
2007-06-24 2:58 ` Eli Zaretskii
2007-06-24 4:32 ` Michael Eager
2007-06-25 18:03 ` Jim Blandy
2007-06-25 18:39 ` Michael Eager
2007-06-25 19:10 ` Jim Blandy
2007-06-25 19:26 ` Paul Koning
2007-06-25 19:32 ` Daniel Jacobowitz
2007-06-25 19:38 ` Robert Dewar
2007-06-25 19:48 ` Paul Koning
2007-06-25 20:09 ` Michael Eager
2007-06-25 20:40 ` Robert Dewar
2007-06-25 20:47 ` Robert Dewar
2007-06-25 20:31 ` Eli Zaretskii
2007-06-25 20:44 ` Robert Dewar
2007-06-25 21:00 ` Eli Zaretskii
2007-06-25 21:03 ` Robert Dewar
2007-06-25 21:06 ` Robert Dewar
2007-06-26 18:34 ` Markus Deuling
2007-06-26 18:36 ` Robert Dewar
2007-06-26 21:55 ` Jim Blandy
2007-06-26 22:14 ` Nick Roberts
2007-06-26 23:26 ` Robert Dewar
2007-06-26 23:39 ` Joel Brobecker
2007-06-26 23:43 ` Robert Dewar
2007-06-27 0:32 ` Jim Blandy
2007-06-27 0:42 ` Robert Dewar
2007-06-27 3:22 ` Eli Zaretskii
2007-06-27 0:23 ` Michael Eager
2007-06-25 20:42 ` Eli Zaretskii
2007-06-25 20:23 ` Eli Zaretskii
2007-06-25 21:52 ` Jim Blandy
2007-06-26 1:04 ` Paul Koning
2007-06-25 20:37 ` Eli Zaretskii
2007-06-25 20:15 ` Eli Zaretskii
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=467D6D1F.7090507@earthlink.net \
--to=stanshebs@earthlink.net \
--cc=eager@eagercon.com \
--cc=gdb@sources.redhat.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