From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc] Simplify target stack
Date: Thu, 16 Oct 2003 13:16:00 -0000 [thread overview]
Message-ID: <20031016131613.GB14202@nevyn.them.org> (raw)
In-Reply-To: <3F8DCC3A.4030201@redhat.com>
On Wed, Oct 15, 2003 at 06:37:46PM -0400, Andrew Cagney wrote:
> Hello,
>
> The attached patch simplifies the target-stack by folding the "struct
> target_stack_item" into the "struct target_ops". The field "struct
> target_ops . beneath" being added.
>
> This in turn greatly simplifies the logic needed to walk the target
> stack (target_beneath becomes a one-liner), and that in turn lets me
> correctly implement the new target read/write partial methods I just posted.
>
> Note that this implementation is still limited to a single target stack
> (due to all the target_ops vectors being static). Follow-on changes can
> eliminate that restriction.
>
> Once I've finished testing, I'll look to commit it in a day or so,
> Andrew
You're moving beneath into target_ops, but aren't you going to have to
either move it out again or move everything else from target_ops? It
seems to me that we want the method vector to be constant eventually
(kill the INHERIT mess), but the target to have local data. Just seems
like this is happening in the wrong order. Another way would be:
- rename target_ops and target_item
- make access to target go through the renamed version of target_item
- add a target_data member to the renamed target_data
Other than that seems good.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-10-16 13:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-15 22:37 Andrew Cagney
2003-10-16 13:16 ` Daniel Jacobowitz [this message]
2003-10-16 15:27 ` Andrew Cagney
2003-10-16 23:07 ` Daniel Jacobowitz
2003-10-17 0:21 ` Andrew Cagney
2003-10-23 3:58 ` Daniel Jacobowitz
2003-10-23 5:06 ` Andrew Cagney
2003-10-17 13:57 ` 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=20031016131613.GB14202@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb-patches@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