From: Tom Tromey <tromey@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 0/4] baby step toward multi-target
Date: Tue, 29 Jul 2014 15:15:00 -0000 [thread overview]
Message-ID: <87lhrccja2.fsf@fleche.redhat.com> (raw)
In-Reply-To: <53D7AE46.8080303@redhat.com> (Pedro Alves's message of "Tue, 29 Jul 2014 15:23:02 +0100")
Tom> If this approach seems reasonable then it's not too hard to pull over
Tom> some of the other target conversions from the branch.
Pedro> Seems reasonable. We may or not end up doing things completely
Pedro> different wrt to the identify issue and target is pushed/not pushed,
Pedro> but meanwhile this lets us progress with making it possible to have
Pedro> different instances of a target, so it seems good forward progress.
Pedro> The series looked good to me.
Thanks for looking.
I actually went a bit farther down this path on my branch, adding:
0249cca turn remote into a to_xclose target
84e2677 turn linux-thread-db into a to_xclose target
9fdaa64 fix exec_close to be multi-target-aware
7fd03ff introduce the target stack
698a56f convert current_target to be a pointer
68520c8 convert exec target to to_xclose
These are all things pulled over from the mostly-defunct multi-target
branch.
I probably wouldn't be inclined to put these -- or maybe even the bulk
of the "baby step" series -- in right now. They aren't really that
useful until some other things are finished, like adding the target ID
to ptid.
However, it's probably useful as a starting point for the next attempt
at multi-target. In particular it's much less invasive than the earlier
approach, and the "convert current_target to be a pointer" patch (the
biggest one) was mostly done with a perl one-liner.
Tom
next prev parent reply other threads:[~2014-07-29 15:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-18 19:27 Tom Tromey
2014-07-18 19:27 ` [PATCH 2/4] simplify target_is_pushed Tom Tromey
2014-07-29 13:22 ` Joel Brobecker
2014-07-29 15:16 ` Tom Tromey
2014-07-18 19:27 ` [PATCH 1/4] move core_bfd to program space Tom Tromey
2014-07-18 19:45 ` [PATCH 3/4] add to_identity Tom Tromey
2014-07-29 14:56 ` Joel Brobecker
2014-07-29 15:11 ` Tom Tromey
2014-07-18 20:44 ` [PATCH 4/4] convert corelow to to_xclose Tom Tromey
2014-07-29 15:11 ` [PATCH 0/4] baby step toward multi-target Pedro Alves
2014-07-29 15:15 ` Tom Tromey [this message]
2014-07-29 16:32 ` Pedro Alves
2014-07-29 19:04 ` Tom Tromey
2014-07-29 21:32 ` Doug Evans
2014-08-11 5:54 ` Doug Evans
2014-07-29 15:40 ` Doug Evans
2014-08-10 20:02 ` Doug Evans
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=87lhrccja2.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@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