| "Michael Gogins" wrote:
> I again move for the canonical Csound build to use double-precision floating
> point numbers for all real numbers. I would add also to use 32-bit signed
> ints for all integers (unless there is a need for 64 bits).
Ouch! Except in limited circumstances, is there any perceivable gain
from doubling the size of virtually all data in Csound? Not only does
it greatly increase memory requirements, but on many architectures 64-bit
FP computations are significantly slower. Main memories have certainly
grown enough to support larger data in the past few years, but all-important
cache memories have not--halving the number of cachable data elements is
going to hit performance pretty hard even if the CPU is as fast for 64-bit
FP as 32-bit.
I'd like to have an option for 64-bit floating point (especially if it
can be requested on a per-variable and per-table basis), but burdening
Csound with a 64-bit default seems entirely unnecessary.
-Ed
|