Revision as of 21:50, 8 June 2015 edit Quondum (talk \| contribs) Extended confirmed users 38,926 edits →IEEE 754 octuple-precision binary floating-point format: binary256: binary256 is a symbol (so cannot insert a space); updating caption ← Previous edit		Revision as of 22:01, 8 June 2015 edit undo Quondum (talk \| contribs) Extended confirmed users 38,926 edits →Hardware support: removing statement – not of encyclopaedic value Next edit →
Line 66: === Hardware support === There is little to no hardware support for octuple-precision arithmetic. 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 packages of information (at least) in order to transport this across the main data bus * [[16-bit\|x16 architecture]] -– 16 separate packages of information (at least) in order to transport this across the main data bus * [[x86\|x86 architecture]] -– 8 separate packages of information (at least) in order to transport this across the main data bus * [[x86-64\|x64 architecture]] -– 4 separate packages of information (at least) in order to transport this across the main data bus ~~<br />~~ ~~So, usage of this on modern architecture computers would create tremendous lag compared to other precision arithmetic.~~ == See also ==

Octuple-precision floating-point format: Difference between revisions