Re: Make remote-sim target always have a thread

Pedro Alves
2008-07-09T11:11:33Z

A Monday 07 July 2008 20:15:18, Daniel Jacobowitz wrote:
> On Thu, Jul 03, 2008 at 07:04:20PM +0100, Pedro Alves wrote:
> > Default results look much better than I was expecting without
> > tweaking the boardfile.
>
> If you'd like, I believe arm*-*-eabi and arm*-*-elf should XFAIL the
> args.exp and fileio.exp failures. I believe they're inherent; ARM
> defined the semihosting interface (long ago), and it does not include
> the necessary bits for some of this. For instance, the command line
> is passed as a string. It's possible some of the fileio.exp failures
> are bugs in the simulator though - I haven't checked them exhaustively.

I'd prefer to investigate better the failures than XFAILing them
blindly. Not all the args.exp tests fail for instance, and I just
noticed that there are more failures in other tests than I
originally reported. I'll have to pass for now, and defer to someone
who's more caring for the sim target.

> > +/* This is the ptid we use while we're connected to the simulator.
> > + It's value is arbitrary, as the simulator target don't have a
> > + notion or processes or threads, but we need something non-null to
> > + place in inferior_ptid. */
> > +static ptid_t remote_sim_ptid;
>
> Same spelling errors as last patch.
>
> > + /* The simulators' task is always alive. */
>
> simulator's
>
> OK.

Thanks, I've checked it in with those changed, after rerunning
the testsuite (without skipping most tests...). There were
no regressions (actually fixed some MI issues than I posted about
a couple of emails ago).

--
Pedro Alves