Octuple-precision floating-point format: Difference between revisions

Content deleted Content added
m Fixed broken reference link
Int512 (talk | contribs)
remove incorrect statistics, x86 and x86-64 is much more complicated than "read size = general purpose register size" and would be too much detail
Line 61:
=== Hardware support ===
There is little to no hardware support for it. Octuple-precision arithmetic is too impractical for most commercial uses of it, making implementation of it very rare (if any).
 
==Processing Statistics==
Since an octuple precision 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]] – 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 completely impractical.
 
== See also ==