Most of Coverity Scan reports are false
positives, but in rare cases we have
confirmed (very small) issues.
No functional change.
case EVASION: case QSEARCH_0: case QSEARCH_1: case PROBCUT: case RECAPTURE:
stage = STOP;
+ /* Fall through */
+
case STOP:
end = cur + 1; // Avoid another next_phase() call
return;
}
if (!others)
- { /* disambiguation is not needed */ }
+ { /* Disambiguation is not needed */ }
else if (!(others & file_bb(from)))
san += to_char(file_of(from));
struct ThreadBase {
- ThreadBase() : exit(false) {}
+ ThreadBase() : handle(NativeHandle()), exit(false) {}
virtual ~ThreadBase() {}
virtual void idle_loop() = 0;
void notify_one();
<< "position key: " << setw(16) << pos.key()
<< "\nmaterial key: " << setw(16) << pos.material_key()
<< "\npawn key: " << setw(16) << pos.pawn_key()
- << dec << sync_endl;
+ << dec << nouppercase << setfill(' ') << sync_endl;
else if (token == "uci")
sync_cout << "id name " << engine_info(true)