RE: What should a CPU simulator support?

["Robert Norton" <rnorton@broadcom.com>]

> -----Original Message-----
> From: Daniel Jacobowitz [mailto:drow@false.org] 
> Sent: 06 July 2007 13:02
> To: Robert Norton
> Cc: Jim Blandy; s88; Wenbo Yang; gdb@sourceware.org
> Subject: Re: What should a CPU simulator support?
> 
> 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).

OK. That's interesting. We support this too but I've always thought it a
little cumbersome compared to built in simulator. Your stdin / out
comment was interesting: I may look into this.
 
> > 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 :-)

Yeah that's pretty much what I figured. It'd be great if we could
contribute, but unfortunately it's not my decision. All I can do is give
bug reports and trivial fixes. I really appreciate your support though.

Robert