From: Tom Tromey <tom@tromey.com>
To: Simon Marchi <simark@simark.ca>
Cc: Andreas Schwab <schwab@linux-m68k.org>,
Guinevere Larsen <guinevere@redhat.com>,
Andrew Oates <andrew@andrewoates.com>,
gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix compile error due to [[noreturn]] with clang
Date: Fri, 25 Oct 2024 09:36:11 -0600 [thread overview]
Message-ID: <87bjz89ous.fsf@tromey.com> (raw)
In-Reply-To: <9f436087-d5c5-449a-b80c-da896989fc4e@simark.ca> (Simon Marchi's message of "Tue, 22 Oct 2024 16:37:07 -0400")
>>>>> "Simon" == Simon Marchi <simark@simark.ca> writes:
Simon> But nowadays, --enable-targets=all builds the sim for all targets (that
Simon> have a sim), not only the main target. Would it be possible to build
Simon> remote-sim.o in that case, and use the simulator for any target, from a
Simon> single --enable-targets=all gdb build?
Andreas pointed out why this doesn't work today, but I wanted to mention
that I think we should have a goal of removing remote-sim.o entirely.
In particular I think the the sim should run as a separate process and
talk to gdb via the remote protocol. "target sim" would be
reimplemented as "target remote | arch-name-whatever".
This way, the sim could be made multi-target-capable and also wouldn't
block the goal of always using target async.
I started work on this a bit, turning gdbserver into a library and
writing a gdbserver target layer for the sim. However, I'm a little
blocked on figuring out how to handle register descriptions. There's
also the gdbarch "register_sim_regno" hook to remove.
IMO the sims are a bit of an albatross. Mike did a bunch of work on
them a while ago, but for the most part they don't seem to be actively
developed.
Tom
prev parent reply other threads:[~2024-10-25 15:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-20 18:00 andrew
2024-10-22 18:28 ` Guinevere Larsen
2024-10-22 18:50 ` Andrew Oates
2024-10-22 19:10 ` Guinevere Larsen
2024-10-22 19:25 ` Andrew Oates
2024-10-22 19:37 ` Simon Marchi
2024-10-22 20:20 ` Andreas Schwab
2024-10-22 20:37 ` Simon Marchi
2024-10-22 20:53 ` Andreas Schwab
2024-10-24 0:40 ` Andrew Oates
2024-10-25 15:36 ` Tom Tromey [this message]
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=87bjz89ous.fsf@tromey.com \
--to=tom@tromey.com \
--cc=andrew@andrewoates.com \
--cc=gdb-patches@sourceware.org \
--cc=guinevere@redhat.com \
--cc=schwab@linux-m68k.org \
--cc=simark@simark.ca \
/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