DPD is intended for HW implementations.
Software implementation are expected to use BID.
> It's probably OK if someone else makes the effort to implement it in
> hardware. But not as it is.
Under given constrains of fitting into 64 bits decimal64 in BID encoding
is not horrible at all.
Software implementation could to be rather fast on modern 64-bit processors.
Intel's reference library implementation from 15+ plus years ago is slow
not because it should be, but probably because it was done in hurry and
never improved after that.
The real problem with IEEE decimal64 is completely different.
It's just not useful.
For accountants it's o.k. for input/output but does not have enough of
precision to hold intermediate results. In theory, higher precision
could be used when needed, but that defeats the primary purpose
of decimal floating-point, which is to make life of accountants simpler.
So, the part of accountants that wants their lives simpler (and got
brains) will use decimal128 from start to finish. Bigger fraction
of accountants will continue to use fix-point and ignore decimal
FP as too innovative and breaking existing practices.
And the rest of the world is happy with binary and never wanted
decimal to start with.
So, no place for decimal64 in the world, as I understand it, except
possibly, as a storage format for big missives of financial
data. But even in this role zipped decimal128 can probably do
at least as well if not better.