[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: small integers
- To: email@example.com
- Subject: Re: small integers
- From: firstname.lastname@example.org (James E. O'Dell)
- Date: Wed, 14 Oct 1992 20:04:59 -4
- Cc: Scott_Fahlman@SEF-PMAX.SLISP.CS.CMU.EDU, email@example.com
- Organization: Fort Pond Research
- Reply-to: firstname.lastname@example.org
On Wed, 14 Oct 92, email@example.com (David A. Moon) wrote:
>> Date: Tue, 13 Oct 1992 22:33:27 -4
>> From: firstname.lastname@example.org (James E. O'Dell)
>> ...garbled line-wrapped message elided...
>When I said "often" I meant that the compiler can often optimize the code,
>that the code would often return the correct answer. The infrequent case
>would be slightly slower code that has to do an overflow check, not code
>returns the wrong answer!
Yeah, thats what I thought you meant. I still think you need a mode that
arithmetic with complete disregard for correctness. Real numerical types
a single calculation anyway. There are too many other ways to get
instabilities in a complicated numerical program. To check a single op for
in a large code may be seen by many as penny wise and pound foolish.
Many complicated codes are checked for correctness by varying input values
slightly to see if the results are stable. Another method of doing a
analysis is performing the same calculation in both single and double
checking the results for stability.
I don't believe Seymour Cray built his machines the way he did because he
getting incorrect answers.