🚀 go-pugleaf

In article <767@ark.UUCP> gijs@vu44.UUCP (Mos Gijs) writes:
>	...
>	Although this information is not sufficient in general to effect full
>	recovery from the bus error, it does allow software diagnosis.
>	...
>You cannot do virtual memory, you cannot auto-allocate stack space, but you
>*can* do multitasking. 
>

Actually, with a small compiler hack, you *can* auto-allocate stack
space.  The trick is that while in general you can't restart, there
are specific instructions that can be restarted.  tstb is one such
instruction.  The hack to the compiler is to make it generate a
tstb in the function entry code to access the lowest stack address
that the function will use.

I have heard people claim that there is enough information around
after a bus error ( or address error ) to restart most instructions,
if the bus error handler is willing to be clever.  However, I haven't
seen any actual code...  Anyone know if this is true?  If so, what
are the instructions that can't be restarted?
-- 
"I *DO* believe in Mary Worth"

Tim Smith       USENET: sdcrdcf!ism780c!tim || ima!ism780!tim
		Compuserve: 72257,3706          Delphi || GEnie: mnementh