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: fac41,dad65365cb2b3396
X-Google-Attributes: gidfac41,public
X-Google-Thread: 109fba,dad65365cb2b3396
X-Google-Attributes: gid109fba,public
X-Google-Thread: 1014db,dad65365cb2b3396
X-Google-Attributes: gid1014db,public
X-Google-Thread: 103376,dad65365cb2b3396
X-Google-Attributes: gid103376,public
From: dewar@merv.cs.nyu.edu (Robert Dewar)
Subject: Re: The disturbing myth of Eiffel portability
Date: 1996/12/01
Message-ID: <dewar.849443758@merv>#1/1
X-Deja-AN: 201703296
references: <3294e64b.74799475@news2.ibm.net> <56t1m4$nis@bcrkh13.bnr.ca>
 <dewar.848444338@merv> <1996Nov20.065345.1@eisner> <dewar.848592914@merv>
 <1996Nov22.074528.1@eisner> <dewar.848713436@merv>
 <57rgc3$rnh@booboo.cs.ucsb.edu>
organization: New York University
newsgroups: comp.lang.eiffel,comp.lang.ada,comp.lang.c,comp.lang.c++
Date: 1996-12-01T00:00:00+00:00
List-Id: <comp.lang.ada>


Graham asks

"I'm going out on a wing here, but do Crays use IEEE?  Crays have a long
and established tradition of going their own separate ways on many things
(_Computer Organization and Design_ by Patterson and Hennessy mentions
the ... amusing ability of a Cray to generate a floating-point overflow
when computing z/x if x is very small but not zero).  And nobody's going
to claim you don't use Crays for serious work.

If Java fails to work on Crays, it makes my day ;)"

The old style vector machine Crays (to which P&H refers) definitely are
NOT IEEE, or even close, and as per my previous message use reciprocal
hardware for division, meaning that division results can be off by one bit.
Implementing Java efficiently on those machines, which are now largely
obsolete, is out of the question.

Newer Crays are multiprocessors using at the moment Alpha's, although
considering the ownership, one might expect them to shift to MIPS chips
in the future. But in either case, we are talking about chips that are
subtly IEEE incompatible, as per my previous message.

P.S. for another source of amusing war stories on bogus floating-point
implementations, and an easy introduction to IEEE arithmetic aimed at
software folks rather than hardware folks, see chapter 5 of my book
on Microprocessors (Microprocessors: A Programmer's View, McGraw Hill,
1990, Dewar & Smosna).