Files
Stockfish/src
joergoster 72a501c6fe Fix zugzwang pruning issues
By adding pos.non_pawn_material(pos.side_to_move()) as a precondition in step 13,
which is already in use in Futility Pruning (child node) and Null Move Pruning for similar reasons.

Pawn endgames, especially those with only 1 or 2 pawns, are simply heavily influenced by zugzwang situations.

Since we are using a bitbase for KPK endgames, I see no reason to accept buggy evals as shown in #760

Patch looks neutral at STC
LLR: 2.32 (-2.94,2.94) [-3.00,1.00]
Total: 79580 W: 10789 L: 10780 D: 58011

and LTC
LLR: 2.95 (-2.94,2.94) [-3.00,1.00]
Total: 27071 W: 3502 L: 3390 D: 20179

Bench: 6259071

Closes #1051
Closes #760
2017-04-07 17:15:00 -07:00
..
2017-01-17 14:50:03 +01:00
2017-03-25 10:22:20 -07:00
2017-03-14 21:02:21 -07:00
2017-02-23 21:33:03 -08:00
2017-03-14 20:56:26 -07:00
2017-03-14 20:56:26 -07:00
2017-03-25 17:57:07 -07:00
2017-03-05 18:20:27 -08:00
2017-02-19 14:00:44 -08:00
2017-04-07 17:15:00 -07:00
2017-01-11 08:46:29 +01:00
2017-01-11 08:46:29 +01:00
2017-02-19 14:00:44 -08:00
2017-01-11 08:46:29 +01:00