From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,d053083f91c271b2
X-Google-Attributes: gid103376,public
From: kilgallen@eisner.decus.org (Larry Kilgallen)
Subject: Re: floating point problem
Date: 1997/03/12
Message-ID: <1997Mar12.095335.1@eisner>#1/1
X-Deja-AN: 224966737
X-Nntp-Posting-Host: eisner.decus.org
References: <5f0faa$6ok@mtinsc04.worldnet.att.net>
 <331ace4d.1427558395@news.mwci.net> <dewar.857535729@merv>
 <1997Mar5.083938.1@eisner> <dewar.857586895@merv> <1997Mar6.080211.1@eisner>
 <dewar.857911706@merv> <5fvqkr$7n7@mulga.cs.mu.OZ.AU> <dewar.857974200@merv>
 <1997Mar10.074953.1@eisner> <dewar.858142750@merv>
X-Nntp-Posting-User: KILGALLEN
X-Trace: 858178419/3330
Organization: LJK Software
Newsgroups: comp.lang.ada
Date: 1997-03-12T00:00:00+00:00
List-Id: <comp.lang.ada>


In article <dewar.858142750@merv>, dewar@merv.cs.nyu.edu (Robert Dewar) writes:
> Larry asks
> 
> <<So can anyone give an example for the Intel-challenged regarding how
> one would easily detect this float-challenged hardware at runtime in
> order to issue a nastygram ?>>
> 
> The proper code is a little delicate, but is documented in the relevant
> Intel microprocessor manuals. Note that all DX chips, and of course all
> Pentiums have built-in floating-point, so this is really only a concern
> with ancient machines that you cannot purchase any longer.

So I would gather one cannot do this test from Ada.

As to machine models affected, my concern is that when my program is
put onto the wrong machine (regardless of any documentation I might
provide) an unambiguous message regarding the nature of the problem
is issued to the naive user.  Support calls cost money.

Larry Kilgallen