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.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Thread: 103376,7e8cebf09cf80560
X-Google-NewGroupId: yes
X-Google-Attributes: gida07f3367d7,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news2.google.com!news4.google.com!feeder2.cambriumusenet.nl!feed.tweaknews.nl!217.73.144.44.MISMATCH!ecngs!feeder.ecngs.de!130.59.10.21.MISMATCH!kanaga.switch.ch!news-zh.switch.ch!switch.ch!news.belwue.de!LF.net!news.enyo.de!not-for-mail
From: Florian Weimer <fw@deneb.enyo.de>
Newsgroups: comp.lang.ada
Subject: Re: How would Ariane 5 have behaved if overflow checking were not
 turned off?
Date: Sun, 20 Mar 2011 14:00:49 +0100
Message-ID: <87y64ac5fi.fsf@mid.deneb.enyo.de>
References: 
 <a8387564-0835-467d-a461-60a093c38133@k15g2000prk.googlegroups.com>
	<82d3lsvqw7.fsf@stephe-leake.org> <87ipvk6vva.fsf@mid.deneb.enyo.de>
	<op.vsehqfxolzeukk@jellix.jlfencey.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Trace: ruchba.enyo.de 1300626049 18694 172.17.135.6 (20 Mar 2011 13:00:49
 GMT)
X-Complaints-To: news@enyo.de
Cancel-Lock: sha1:WxCPgkDWfB3mOpkEGcoIztZ6UtI=
Xref: g2news2.google.com comp.lang.ada:19297
Date: 2011-03-20T14:00:49+01:00
List-Id: <comp.lang.ada>

* Vinzent Hoefler:

> Florian Weimer wrote:
>
>> It's odd that after all those years, little hard data is available on
>> the defect.  The published report uses terminology which is a slightly
>> bit off in the Ada context, so it led only to further speculation.
>
> Hmm? From the report:
>
> |The internal SRI software exception was caused during execution of a
> |data conversion from 64-bit floating point to 16-bit signed integer
> |value. The floating point number which was converted had a value greater
> |than what could be represented by a 16-bit signed integer. This resulted
> |in an Operand Error. The data conversion instructions (in Ada code) were
> |not protected from causing an Operand Error, although other conversions
> |of comparable variables in the same place in the code were protected.
>
> "Operand Error" is what Motorola (now Freescale) just calls it in their
> CPU manual.

"Operand Error" is not the only odd thing.  "Protected" operations
which are subject to exception handling are used in Lisp (and, based
on that, Lua).  And I think we wouldn't call an expression an
"instruction", either.  Without the explicit reference to Ada, I
wouldn't think that this paragraph describes something related to an
Ada program.  That's why I think it uses odd language.