Revision as of 11:48, 24 June 2015 edit Vincent Lefèvre (talk \| contribs) Extended confirmed users 5,215 edits Removed some links: [1] is not binary256; gawk doesn't implement octuple precision, just multiple precision via GNU MPFR (octuple is just an alias for particular parameters). ← Previous edit		Revision as of 11:53, 24 June 2015 edit undo Vincent Lefèvre (talk \| contribs) Extended confirmed users 5,215 edits m →Processing Statistics: Corrected spelling (but this section should probably be removed). Next edit →
Line 67: ==Processing Statistics== Since aan octuple ~~percision~~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 Line 73: * [[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~~completely impractical. == See also ==

Octuple-precision floating-point format: Difference between revisions