Received: (from major@localhost)
	by minnie.cs.adfa.oz.au (8.8.5/8.8.5) id EAA10782
	for pups-liszt; Thu, 23 Apr 1998 04:48:47 +1000 (EST)
X-Authentication-Warning: minnie.cs.adfa.oz.au: major set sender to owner-pups@minnie.cs.adfa.oz.au using -f
Received: from alph02.triumf.ca (alph02.Triumf.CA [142.90.114.18])
	by minnie.cs.adfa.oz.au (8.8.5/8.8.5) with SMTP id EAA10772
	for <pups@minnie.cs.ADFA.OZ.AU>; Thu, 23 Apr 1998 04:48:39 +1000 (EST)
Received: by alph02.triumf.ca; id AA04273; Wed, 22 Apr 1998 11:48:31 -0700
From: Tim Shoppa <shoppa@alph02.triumf.ca>
Message-Id: <9804221848.AA04273@alph02.triumf.ca>
Subject: Re: Floating Point-How Important
To: edgee@cyberpass.net
Date: Wed, 22 Apr 1998 11:48:31 -0800 (PDT)
Cc: pups@minnie.cs.adfa.oz.au
In-Reply-To: <199804221431.JAA01744@mail1.kcnet.com> from "Ed G." at Apr 22, 98 09:31:05 am
X-Mailer: ELM [version 2.4 PL22]
Content-Type: text
Sender: owner-pups@minnie.cs.adfa.oz.au
Precedence: bulk

> How about this approach to determine how many words to skip when 
> scanning for floating point op codes:
> 
> Assuming Bob's summary is complete, my program could classify
> instructions as either double, single or no operand based on the
> range they fall in. No operand cases could be discarded.  Single and
> double operands would have to be further decoded to see if they use
> any of the PC addressing modes (immediate, absolute, relative, and
> relative deferred) and the appropriate number of words skipped.

An even better approach - one that would avoid the problem of confusing
code with data - would be to use Bob Supnik's emulator to *run*
the code in question, and bump an appropriate counter depending on
whether the operation is floating-point or not.

Tim.

