Path: utzoo!attcan!uunet!mcsun!hp4nl!philapd!ssp1!roelof
From: roelof@idca.tds.PHILIPS.nl (R. Vuurboom)
Newsgroups: comp.arch
Subject: Re: (Im)precise exceptions
Summary: Ignorance is not always bliss :-)
Message-ID: <269@ssp1.idca.tds.philips.nl>
Date: 4 Oct 89 08:39:02 GMT
References: <2353@oakhill.UUCP> <261500010@S34.Prime.COM> <34701@apple.Apple.COM> <2451@wyse.wyse.com> <477@ctycal.UUCP> <265@ssp1.idca.tds.philips.nl> <4796@orca.WV.TEK.COM> <27659@shemp.CS.UCLA.EDU>
Organization: Philips Telecommunication and Data Systems, The Netherlands
Lines: 16

In article <27659@shemp.CS.UCLA.EDU> marc@oahu.UUCP (Marc Tremblay) writes:

>Fortunately the 88000 provides special registers which contain the
>necessary information for the software to complete an instruction
>that caused an imprecise exception.
		^^^^^^^^^

Ok, this term has been bandied about on the net before. When (precisely :-)
is an exception imprecise? When is it precise? Does it affect ones handling
of the exception? When does one need to differentiate between the two?

-- 
"Geld groeit me niet op de rug." Literally: "Money doesn't grow on my back."
(Often overheard at the supermarket counter from mothers to their kids.)
Roelof Vuurboom  SSP/V3   Philips TDS Apeldoorn, The Netherlands   +31 55 432226
domain: roelof@idca.tds.philips.nl             uucp:  ...!mcvax!philapd!roelof