Skip to content
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.

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

[BUG]: PTXAS emits advisory regarding cp.async.bulk.*.multicast use on sm_90 #1733

Closed
1 task done
ahendriksen opened this issue May 13, 2024 · 0 comments · Fixed by #1734
Closed
1 task done

[BUG]: PTXAS emits advisory regarding cp.async.bulk.*.multicast use on sm_90 #1733

ahendriksen opened this issue May 13, 2024 · 0 comments · Fixed by #1734
Labels
bug Something isn't working right.

Comments

@ahendriksen
Copy link
Contributor

Is this a duplicate?

Type of Bug

Something else

Component

libcu++

Describe the bug

nvbug 4598481

Tests:
cuda/ptx/ptx.cp.async.bulk.tensor.compile.pass.cpp
cuda/ptx/ptx.cp.async.bulk.compile.pass.cpp

  1. PTXAS emits an advisory about multicast being advised to be used on sm90a when compiled for sm90.
  2. Lit and/or nvcc considers this a warning
  3. we compile with warnings as errors
  4. tests fail

When compiling with NVRTC, 1, 2, 3, or 4 doesn't trigger so the test doesn't fail.

So we have a test that we cannot make behave consistently on all platforms.

How to Reproduce

Run cuda/ptx/ptx.cp.async.bulk.tensor.compile.pass.cpp with -arch sm_90 flags

Expected behavior

Should either fail on all platforms or not fail.

Best behavior would be to not consider any output from ptxas as a warning or error, but that is not something we can fix here..

Reproduction link

No response

Operating System

No response

nvidia-smi output

No response

NVCC version

No response

@ahendriksen ahendriksen added the bug Something isn't working right. label May 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working right.
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

1 participant