From: Tom Tromey <tom@tromey.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] sim: testsuite: push $arch out to targets
Date: Fri, 22 Jan 2021 09:29:29 -0700 [thread overview]
Message-ID: <87lfclndee.fsf@tromey.com> (raw)
In-Reply-To: <YAjM2T2Wsc3CpXx4@vapier> (Mike Frysinger via Gdb-patches's message of "Wed, 20 Jan 2021 19:37:45 -0500")
Mike> at the very least, i have it working now where each subdir can be built
Mike> and installed in a single build.
Nice.
Mike> this is helpful for doing quick tests
Mike> that changes at least compile. obviously can't link a single gdb from
Mike> this, but gotta start somewhere.
One thing that I think would be nice is if we removed remote-sim.c and
instead had the sim act as a gdbserver. This could be done either by
reusing gdbserver (writing a new sim-based back end) or by reusing one
of the tiny gdbserver stubs from gdb/stubs/.
This would support my long-term goal of making gdb always target-async.
Not all the targets are async-ready, but remote-sim is one that really
cannot be made async at all...
One problem with this idea is that the sim can renumber registers.
So I guess the sims would have to send over an XML register description.
Maybe there are gotchas here, I'm not sure.
Another problem is that this would lose CLI completion for sim commands.
However I suppose we could add a remote protocol request for this if we
really cared.
Curious to hear what you think of this.
Tom
next prev parent reply other threads:[~2021-01-22 16:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-17 16:09 Mike Frysinger via Gdb-patches
2021-01-18 9:52 ` Andrew Burgess
2021-01-18 18:01 ` Mike Frysinger via Gdb-patches
2021-01-20 19:53 ` Tom Tromey
2021-01-21 0:37 ` Mike Frysinger via Gdb-patches
2021-01-22 16:29 ` Tom Tromey [this message]
2021-01-23 4:35 ` Mike Frysinger via Gdb-patches
2021-01-23 17:33 ` Tom Tromey
2021-01-25 5:34 ` Mike Frysinger via Gdb-patches
2021-01-21 9:22 ` Andrew Burgess
2021-01-22 6:36 ` Mike Frysinger via Gdb-patches
2021-01-31 1:27 ` Mike Frysinger via Gdb-patches
2021-01-31 10:54 ` Andrew Burgess
2021-01-31 19:41 ` Mike Frysinger via Gdb-patches
2021-02-06 17:16 ` Mike Frysinger via Gdb-patches
2021-02-08 12:12 ` Andrew Burgess
2021-02-09 5:25 ` Mike Frysinger via Gdb-patches
2021-01-18 17:54 ` [PATCH 1/2] sim: switch top level to automake Mike Frysinger via Gdb-patches
2021-01-18 17:54 ` [PATCH 2/2] sim: testsuite: merge into toplevel automake Mike Frysinger via Gdb-patches
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=87lfclndee.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@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