[2/6] Fix transposition table with proper bounds #32
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.
Summary
Boundenum (EXACT, LOWER_BOUND, UPPER_BOUND) for correct TT behaviornull_moveparameter check)Details
The transposition table now correctly stores and uses bound information:
This prevents incorrect cutoffs and score usage that can cause search instability.
Parallel Engine Updates
All parallel engines (lazy_smp, l1p, l2p) updated to:
Test plan
🤖 Generated with Claude Code