IEEE754标准：二进制浮点运算的基石与挑战

4星 · 超过85%的资源需积分: 10 38 浏览量更新于2024-07-30 收藏 115KB PDF 举报

"IEEE754标准是关于浮点数处理的国际标准，旨在解决不同计算机系统间浮点计算的不一致性问题，降低软件移植的成本。该标准由电气和电子工程师协会（IEEE）制定，对二进制浮点算术进行了详细规范。" 正文：在计算机科学领域，浮点数是一种用于表示实数的近似值，特别是在需要大量计算但又受限于存储空间和计算速度的情况下。IEEE754标准，自1985年发布以来，已成为全球广泛采用的浮点运算标准，对C语言等编程语言以及硬件设计有着深远的影响。该标准的核心内容包括以下几个方面： 1. **格式定义**：IEEE754定义了多种浮点数格式，包括单精度（32位）和双精度（64位）等，每种格式都包含了符号位、指数部分和尾数（或称小数部分）。这些格式允许在有限的存储空间内表示广泛的数值范围和精度。 2. **编码规则**：对于指数和尾数，IEEE754规定了特定的二进制编码方式，如偏移量编码（bias）用于指数部分，以减少零和无穷大的表示复杂性。 3. **运算规则**：标准详细规定了加减乘除、开方、比较、舍入等基本运算的行为，确保跨平台的一致性。例如，它定义了四种舍入模式：向最接近的数舍入（默认）、向零、向上（或称为“天花板”）和向下（或称为“地板”）。 4. **异常处理**：IEEE754还涵盖了浮点运算可能出现的异常情况，如除以零、无穷大、非数字（NaN）以及溢出和下溢。这些异常可以有不同的处理策略，如信号（trap）或者静默（通过特殊值返回）。 5. **精度和稳定性**：为了提高计算的精度和稳定性，标准推荐使用特定的算法和方法，如高精度除法和乘法，以及避免某些可能导致错误放大的运算顺序。 6. **兼容性和扩展性**：随着技术的发展，IEEE754标准也不断更新，增加了半精度（16位）和四倍精度（128位）格式，并对软件和硬件的交互提供了指导，以适应新的应用场景。 7. **标准化的影响**：由于 IEEE754 的广泛采用，现代计算机系统中的浮点运算变得高度一致，使得编写跨平台的高性能科学计算和工程应用变得更加容易。尽管 IEEE754 在很大程度上解决了早期浮点计算的混乱，但随着技术的进步，新问题也逐渐浮现，如浮点计算的可预测性和性能优化。标准中的某些特性可能会导致复杂性和效率的问题，尤其是在硬件实现和软件优化时。因此，持续的讨论和改进始终是这个领域的重要课题。

Work in Progress: Lecture Notes on the Status of IEEE 754 October 1, 1997 3:36 am

Page 6

Exceptions in General.

Designers of operating systems tend to incorporate all trap-handling into their handiwork, thereby burdening

floating-point exception-handling with unnecessary and intolerable overheads. Better designs should incorporate

all floating-point trap-handling into a run-time math. library, along with logarithms and cosines, which the

operating system merely loads. To this end, the operating system has only to provide default handlers ( in case the

loaded library neglects trap-handling ) and secure trap re-vectoring functions for libraries that take up that duty and

later, at the end of a task, relinquish it.

To Disable an exception's trap is to let the numeric (co)processor respond to every instance of that exception by

raising its Flag and delivering the result specified as its “ Default ” in IEEE 754. For example, the default result

for 3.0/0.0 is ∞ with the same sign as that 0.0 . The raised flag stays raised until later set down by the program,

perhaps after it has been sensed. IEEE 754 allows for the possibility that raised flags be non-null pointers, but

most microprocessors keep one or two bits per flag in a Status register whose sensing and clearing fall outside the

scope of these notes. The same goes for bits in a Control register that Enable/Disable traps; see manuals for your

chip and for the programming environment ( e.g. compiler ) that concerns you.

+-------------------------------------------------------------------+

| CAUTION: Do not change ( enable or disable ) exception traps |

| in a way contrary to what is expected by your programming |

| environment or application program, lest unpredictable |

| consequences ensue for lack of a handler or its action. |

+-------------------------------------------------------------------+

Disputes over exceptions are unavoidable. In fact, one definition for “ Exception ” is ...

“ Event for which any policy chosen in advance will subsequently

give some reasonable person cause to take exception.”

A common mistake is to treat exceptions as errors and punish the presumed perpetrators; usually punishment falls

not upon deserving perpetrators but upon whatever interested parties happen to be in attendance later when

exceptions arise from what was perpetrated, error or not.

+-------------------------------------------------------------------+

| Exceptions that reveal errors are merely messengers. What |

| turns an exception into an error is bad exception-handling. |

+-------------------------------------------------------------------+

Attempts to cope decently with all exceptions inevitably run into unresolved dilemmas sooner or later unless the

computing environment provides what I call “ Retrospective Diagnostics.”. These exist in a rudimentary form in

Sun Microsystems' operating system on SPARCs. The idea is to log ( in the sense of a ship's log ) every

suspicious event that is noticed during a computation. These events are logged not by time of occurrence ( which

could fill a disk very soon ) but by site in a program. A hashing scheme ensures that events repeated at the same

site will perhaps update but certainly not add entries to the log. Neither need an exception that occurs while its flag

is still raised by a previous exception of the same kind add a new entry to the log. After a program finishes ( if it

ever does ), its user may be notified discreetly if a dangerous flag like INVALID is still raised; then that flag can

serve as a pointer to its entry in the log. The log cannot grow intolerably long, so unusual entries stand out and

point to whatever software module put them there. The user of that software can then identify the module in

question and ask its supplier whether an entry is something to worry about.

剩余29页未读，继续阅读

狂且

粉丝: 17
资源: 17

IEEE754标准：二进制浮点运算的基石与挑战

浮点型数据格式IEEE754标准的详细解释

IEEE 754 Floating point Arithmetic

浮点数IEEE754标准

IEEE754.rar_IEEE754_ieee754标准_labvIEW 754_labview ieee754_浮点数

IEEE754标准-英文版

IEEE754标准的32位浮点数

IEEE754标准的32位浮点数格式

IEEE 754标准及转换程序.rar

基于IEEE754标准的浮点乘法器

IEEE 754标准：浮点数算术规范

最新资源