Switch from inverse to linalg_inv_ex to avoid sync#487
Merged
Conversation
Signed-off-by: Matthew Cong <mcong@nvidia.com>
fwilliams
approved these changes
Mar 2, 2026
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.
torch::inverse, an alias fortorch::linalg_inv, synchronizes the host with the device after computing the inverse in order to inspect error codes. To avoid this, we switch totorch::linalg_inv_ex(as suggested by the PyTorch documentation) which exposes acheck_errors=Falseparameter. This lets us avoid the synchronization by default but also enable it for debugging if needed.