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.
Currently, checkers create graphs for real and try to catch exceptions to decide whether a config is supported. This hides unintentional failures in graph creation, leading to suboptimal UX.
For example, if I put an
assert False
at the beginning of_make_cudnn_sdpa_backward_graph
, I got the following mysterious error that doesn't point to the real error at all.This PR will remove those dry-runs and rely on existing heuristics to reject unsupported SDPA operations. This will, unfortunately, make cudnnex overtly aggressive because the existing heuristics don't reject all unsupported cases. Therefore, cudnnex will claim more SDPA operations than it can support. It may happen that during execution that support is actually missing and then it would be on thunder to somehow try another executor from its list. This behaviour is probably fine as cudnn is not a default executor yet.