<< Previous Message Main Index Next Message >>
<< Previous Message in Thread This Month Next Message in Thread >>
Date   : Sat, 16 Sep 2006 07:08:00 +0100
From   : Sprow <info@...>
Subject: Re: Bugs in ArmCoPro OS

In article <20060915220026.96460.qmail@...>,
   Greg Cook <debounce@...> wrote:
> On Fri, 15 Sep 2006 09:12:10 +0100, Sprow <info@...> wrote:

[snip]

> > > The carry flag is very inconsistantly set correctly.
> > 
> > I was hinting to use C to tell if the call was implemented,
> > inspecting the
> > block to tell if anything actually happened is a wise addition.
>
> As the block seems to be the only thing that always gets returned, it's
> the only trustworthy source.  In at least one DFS the return state of
> the carry flag was undefined.

Sigh.

> > > Is there a spare SetSomething call the ARMCoPro OS could provide
> > > to make this selectable?
> > 
> > Great - a compromise to stop my fingers getting sore. You can already
> > do this, just intercept the SWI vector
>
> Presumably the intercepting code would have to source A itself?

The SWI interception code would need to do the Tube transfer itself, then it
can get the returned A and decide what to do with it,
Sprow.
<< Previous Message Main Index Next Message >>
<< Previous Message in Thread This Month Next Message in Thread >>