Use double everywhere

Rationale:

- Speed of double and float is about the same (not on the hot path anyway)

- Double makes code prettier (no need to write 1.0f, just 1.0)

- Only practical advantage of float is to use less memory, but since we never
  store large arrays of double, we don't care.

No functional change.
This commit is contained in:
Lucas Braesch
2013-10-03 12:05:58 +08:00
committed by Marco Costalba
parent 7f142d6817
commit a0cc15ccbc
5 changed files with 12 additions and 12 deletions

View File

@@ -84,7 +84,7 @@ namespace {
size_t PVSize, PVIdx;
TimeManager TimeMgr;
float BestMoveChanges;
double BestMoveChanges;
Value DrawValue[COLOR_NB];
HistoryStats History;
GainsStats Gains;
@@ -333,7 +333,7 @@ namespace {
while (++depth <= MAX_PLY && !Signals.stop && (!Limits.depth || depth <= Limits.depth))
{
// Age out PV variability metric
BestMoveChanges *= 0.8f;
BestMoveChanges *= 0.8;
// Save last iteration's scores before first PV line is searched and all
// the move scores but the (new) PV are set to -VALUE_INFINITE.