From: Daniel Jacobowitz <drow@false.org>
To: Robert Norton <rnorton@broadcom.com>
Cc: Jim Blandy <jimb@codesourcery.com>, s88 <dave.tw@gmail.com>,
Wenbo Yang <wenbo.yang@simplnano.com>,
gdb@sourceware.org
Subject: Re: What should a CPU simulator support?
Date: Fri, 06 Jul 2007 12:02:00 -0000 [thread overview]
Message-ID: <20070706120229.GB10648@caradoc.them.org> (raw)
In-Reply-To: <B0D822BFECD50F4991F2516EA50F273C01E4DFD8@NT-IRVA-0752.brcm.ad.broadcom.com>
On Fri, Jul 06, 2007 at 03:26:48AM -0700, Robert Norton wrote:
> Is this still the recommended way of making a built-in simulator? I
Depends what you mean. I suppose it is, but I recommend not making a
built-in simulator at all (using TCP to talk to your simulator).
> noticed when upgrading our port that the api for simulator implemented
> breakpoints has been removed! We're not interested in implementing soft
> breakpoints so I had to resurrect this support in remote-sim.c.
Do you mean SIM_HAS_BREAKPOINT? I believe it was removed four years
ago for lack of any simulators in the tree which used it. That's life
with an uncontributed port :-)
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-07-06 12:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-05 2:30 Wenbo Yang
2007-07-05 19:14 ` Jim Blandy
[not found] ` <c9d32f760707051300r192ea70bj3edcfc00892c5714@mail.gmail.com>
2007-07-05 21:32 ` Jim Blandy
2007-07-06 10:27 ` Robert Norton
2007-07-06 12:02 ` Daniel Jacobowitz [this message]
2007-07-06 12:10 ` Robert Norton
2007-07-06 12:20 ` Daniel Jacobowitz
2007-07-06 21:56 ` Eric Weddington
2007-07-06 22:13 ` 'Daniel Jacobowitz'
[not found] <c9d32f760707031824u7836642aud35629ae88fbfe3@mail.gmail.com>
2007-07-04 1:26 ` s88
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=20070706120229.GB10648@caradoc.them.org \
--to=drow@false.org \
--cc=dave.tw@gmail.com \
--cc=gdb@sourceware.org \
--cc=jimb@codesourcery.com \
--cc=rnorton@broadcom.com \
--cc=wenbo.yang@simplnano.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