Fix native CUDA cache retention in fill_holes early returns#32
Open
luca-888 wants to merge 1 commit into
Open
Conversation
This file contains hidden or 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
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.
Summary
This PR fixes native CUDA cache retention in
CuMesh::fill_holes()early-return paths.fill_holes()already callsclear_cache()on the successful fill path. This PR makes the no-op / no-fill paths consistent with that behavior.Changes
Call
clear_cache()before returning when:max_hole_perimeterThis clears connectivity/boundary cache created during
fill_holes()before the function exits.Verification
Used the following repro script:
Before:
After: