Adds a new rematerialization method that focuses on rematerializing only the highest memory usage peak in the module at any given remat pass (instead of rematerializing the first point at which the memory limit is reached). Should result in more monotonic rematerialization and avoid rematerializing unecessary instructions. Usually not as efficient as regular rematerialization but can help in specific cases. The new mode is not enabled yet. Reworks Instruction List to use unique ptrs. #28935
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.
Adds a new rematerialization method that focuses on rematerializing only the highest memory usage peak in the module at any given remat pass (instead of rematerializing the first point at which the memory limit is reached). Should result in more monotonic rematerialization and avoid rematerializing unecessary instructions. Usually not as efficient as regular rematerialization but can help in specific cases. The new mode is not enabled yet. Reworks Instruction List to use unique ptrs.