This is used for secondary scoring so it does not
changes the fact that Rml[0].pv[0] is always tried
as first anyhow.
It happens this is even a no functional change patch
becuase we reinsert PV in TT after a search so that
TT move is actually Rml[0].pv[0].
No functional change.
Signed-off-by: Marco Costalba <mcostalba@gmail.com>
// before to search them.
template<> struct MovePickerExt<false, true> : public MovePicker {
// before to search them.
template<> struct MovePickerExt<false, true> : public MovePicker {
- MovePickerExt(const Position& p, Move, Depth d, const History& h, SearchStack* ss, Value b)
- : MovePicker(p, Rml[0].pv[0], d, h, ss, b), firstCall(true) {
+ MovePickerExt(const Position& p, Move ttm, Depth d, const History& h, SearchStack* ss, Value b)
+ : MovePicker(p, ttm, d, h, ss, b), firstCall(true) {
Move move;
Value score = VALUE_ZERO;
Move move;
Value score = VALUE_ZERO;