YJIT: Avoid register allocation conflict with a higher stack_idx #9143
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.
RegTemps::conflicts_with
currently checks if it conflicts with indexes lower than the argument stack_idx. Therefore it does not detect a conflict with indexes higher than the argument stack_idx. While it works fine in most cases, it leads to a wrong allocation in the scenario demonstrated in this test_yjit script.This PR fixes it to check both lower indexes and higher indexes than the argument stack_idx.