Core:Rec: Adjust bounds check asserts to not erroneously trip #12459
+3
−3
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
|
So the 64kb between |
TheLastRar
approved these changes
Mar 26, 2025
From what I can tell, yes. |
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.
Description of Changes
Adjusts some asserts to not trip every time we run out of rec code space
(They should now only trip if we actually start writing out of bounds)
Rationale behind Changes
We shouldn't be tripping asserts during normal operation
Suggested Testing Steps
Play R&C 2 or 3 for a few hours in a Devel build
(Or just pretend you did and say it's fine)