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,FREEMAIL_FROM,
	INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,dec0a6ed5b5044de
X-Google-Attributes: gid103376,public
From: Corey Ashford <yeroca@rocketmail.com>
Subject: Re: Code portability question
Date: 1999/01/24
Message-ID: <36AB878E.F51CA837@rocketmail.com>#1/1
X-Deja-AN: 436424013
Content-Transfer-Encoding: 7bit
References: <36A94B78.963F3215@wvu.edu> <36A9849C.A9FE01E4@rocketmail.com>
 <36AABFAA.2D844356@wvu.edu>
X-Accept-Language: en
Content-Type: text/plain; charset=us-ascii
Organization: Rational Software
Mime-Version: 1.0
Newsgroups: comp.lang.ada
Date: 1999-01-24T00:00:00+00:00
List-Id: <comp.lang.ada>

Mike Werner wrote:
[snip]
> All he could supply at this point was that the error concerned
> initialization of floats.  He also indicated that the rewrite needed was
> fairly major.  What had me so suspicious was that he was blaming his
> woes on the fact that his computer had a K6 as the CPU.  His claim was
> that the K6 handled floats so differently that it messed up his
> program.  I didn't see how this was possible.  Or does Ada now
> discriminate against the AMD?

Not unless your compiler emits code for the AMD/Cyrix 3DNow instructions!
(not likely)

The AMD processor is supposed to be an exact clean-room implementation of the
IA32 architecture (plus their 3D enhancements).

I think the chances of the problem being due to a difference in the floating
point register implementation are about, as you surmised, zero.

- Corey