Separate threads for search and uci loop #16
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The UCI loop now makes a new thread to perform the search after seeing a go command. This frees the search from the responsibility of detecting input during the search as the UCI loop is still running. Should be a slight speed-up as well as a bit cleaner, especially getting rid of the code in misc.c.
Also changed behaviour upon receiving 'ucinewgame' command: Since a 'ucinewgame' command should always be followed by a 'position' command, there is no need to set the position to the starting position. However the hash table should be reset, as otherwise the engine will have a slight edge when playing a second game in a row by having the hash table filled with potentially useful information.