[CUDA][avgpool2d] Fix backward launch bounds again for sm100, sm120
#150640
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/150640
Note: Links to docs will display an error until the docs builds have been completed. ✅ You can merge normally! (2 Unrelated Failures)As of commit 2ede186 with merge base 51da241 ( BROKEN TRUNK - The following job failed but were present on the merge base:👉 Rebase onto the `viable/strict` branch to avoid these failures
UNSTABLE - The following job is marked as unstable, possibly due to flakiness on trunk:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
|
@pytorchbot merge |
Merge startedYour change will be merged once all checks pass (ETA 0-4 Hours). Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
Merge failedReason: 1 mandatory check(s) failed. The first few are: Dig deeper by viewing the failures on hud |
|
@pytorchmergebot merge -f "failure already existing, lint is green" |
Merge startedYour change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Please use Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
|
@pytorchbot cherry-pick --onto release/2.7 -c critical |
…0` (#150640) `__CUDA_ARCH__` is not visible in host code, which causes incorrect launch bounds and `too many resources requested for launch` on blackwell CC @atalman @malfet as we would want this in 2.7 @nWEIdia Pull Request resolved: #150640 Approved by: https://github.com/malfet, https://github.com/drisspg, https://github.com/atalman (cherry picked from commit 09c4da9)
Cherry picking #150640The cherry pick PR is at #150676 and it is recommended to link a critical cherry pick PR with an issue. The following tracker issues are updated: Details for Dev Infra teamRaised by workflow job |
…0` (#150676) [CUDA][avgpool2d] Fix backward launch bounds again for `sm100`, `sm120` (#150640) `__CUDA_ARCH__` is not visible in host code, which causes incorrect launch bounds and `too many resources requested for launch` on blackwell Pull Request resolved: #150640 Approved by: https://github.com/malfet, https://github.com/drisspg, https://github.com/atalman (cherry picked from commit 09c4da9) Co-authored-by: Eddie Yan <eddiey@nvidia.com>
…0` (pytorch#150640) `__CUDA_ARCH__` is not visible in host code, which causes incorrect launch bounds and `too many resources requested for launch` on blackwell CC @atalman @malfet as we would want this in 2.7 @nWEIdia Pull Request resolved: pytorch#150640 Approved by: https://github.com/malfet, https://github.com/drisspg, https://github.com/atalman
…0` (pytorch#150640) `__CUDA_ARCH__` is not visible in host code, which causes incorrect launch bounds and `too many resources requested for launch` on blackwell CC @atalman @malfet as we would want this in 2.7 @nWEIdia Pull Request resolved: pytorch#150640 Approved by: https://github.com/malfet, https://github.com/drisspg, https://github.com/atalman
__CUDA_ARCH__is not visible in host code, which causes incorrect launch bounds andtoo many resources requested for launchon blackwellCC @atalman @malfet as we would want this in 2.7 @nWEIdia
cc @ptrblck @msaroufim