Skip to content

updated cudnn frontend to v0.6.1 #75615

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
wants to merge 1 commit into from
Closed

updated cudnn frontend to v0.6.1 #75615

wants to merge 1 commit into from

Conversation

@dzdang
Copy link
Contributor

@dzdang dzdang commented Apr 11, 2022 •
edited
Loading

cudnn frontend v0.6.0 had an issue. we upgrade to cudnn frontend to v0.6.1. see reverted PR: #75481

@facebook-github-bot
Copy link
Contributor

facebook-github-bot commented Apr 11, 2022 •
edited
Loading

🔗 Helpful links

💊 CI failures summary and remediations

As of commit d6e0d36 (more details on the Dr. CI page):

💚 💚 Looks good so far! There are no failures yet. 💚 💚

This comment was automatically generated by Dr. CI (expand for details).

Please report bugs/suggestions to the (internal) Dr. CI Users group.

Click here to manually regenerate this comment.

@dzdang
Copy link
Contributor Author

dzdang commented Apr 11, 2022

@jjsjann123 hey, are you able to check if this PR breaks your build (just updated to the latest v0.6.1 that fixes the return error)? it seems to fine with gnu compilers but wanted to make sure it works with your clang compilers before I land it

@dzdang dzdang requested a review from jerryzh168 April 11, 2022 20:38
@facebook-github-bot
Copy link
Contributor

@dzdang has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

@facebook-github-bot
Copy link
Contributor

@dzdang has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

@facebook-github-bot
Copy link
Contributor

@pytorchbot merge this

(Initiating merge automatically since Phabricator Diff has merged)

@github-actions
Copy link
Contributor

Hey @dzdang.
You've committed this PR, but it does not have both a 'release notes: ...' and 'topics: ...' label. Please add one of each to the PR. The 'release notes: ...' label should represent the part of PyTorch that this PR changes (fx, autograd, distributed, etc) and the 'topics: ...' label should represent the kind of PR it is (not user facing, new feature, bug fix, perf improvement, etc). The list of valid labels can be found here for the 'release notes: ...' and here for the 'topics: ...'.
For changes that are 'topic: not user facing' there is no need for a release notes label.

facebook-github-bot pushed a commit that referenced this pull request Apr 12, 2022
@dzdang @facebook-github-bot
updated cudnn frontend to v0.6.1 (#75615)
035e196 
Summary:
cudnn frontend v0.6.0 had an issue. we upgrade to cudnn frontend to v0.6.1

Pull Request resolved: #75615

Reviewed By: jerryzh168

Differential Revision: D35559232

Pulled By: dzdang

fbshipit-source-id: a249a5c7d18b85861d4c1e8ac9ea27b5d26457ba
@dzdang dzdang added module: cudnn Related to torch.backends.cudnn, and CuDNN support module: third_party labels Apr 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@jerryzh168 jerryzh168 jerryzh168 approved these changes

Assignees

No one assigned

Labels

cla signed module: cudnn Related to torch.backends.cudnn, and CuDNN support module: third_party

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@dzdang @facebook-github-bot @jerryzh168