Octuple-precision floating-point format: Difference between revisions

Content deleted Content added
Undid revision 668018095 by 74.128.68.119 (talk) binary256 is the IEEE 754 format, but this article is about other formats too (e.g. Apple)
Implementations: Added content and made it more legible and improved organization
Tags: Mobile edit Mobile web edit
Line 60:
 
=== Hardware support ===
There is little to no hardware support for octupleit. Octuple-precision arithmetic. Theis requirementstoo in-orderimpractical tofor transportmost thiscommercial pieceuses of datait, making implementation of it very arerare as(if followsany).
<br />
* [[8-bit|8-bit architecture]] (statistical extrapolation since it would take 1/8 of the entire memory just to store 1 octuple-precision numeral so it would be impractical) – 32 separate packets of information (at least) in order to transport this across the main data bus
 
==Processing Statistics==
Since a octuple percision numeral takes up 32 bytes of storage, the requirements in-order to transport this piece of data are as follows.
* [[8-bit|8-bit architecture]] (statistical extrapolation since it would take 1/8 of the entire memory just to store 1 octuple-precision numeral so it would be impractical) – 32 separate packets<sup>1</sup> of information (at least) in order to transport this across the main data bus
* [[16-bit|x16 architecture]] – 16 separate packets of information (at least) in order to transport this across the main data bus
* [[x86|x86 architecture]] – 8 separate packets of information (at least) in order to transport this across the main data bus
* [[x86-64|x64 architecture]] – 4 separate packets of information (at least) in order to transport this across the main data bus
<br />
<sup>1</sup>statistical extrapolation since it would take 1/8 of the entire memory just to store 1 binary256 numeral, making it compleately impractical
<br />
 
== See also ==