-
Notifications
You must be signed in to change notification settings - Fork 201
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
Forward declare half types in cuda::ptx
#2981
Forward declare half types in cuda::ptx
#2981
Conversation
Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually. Contributors can view more details about this message here. |
🟩 CI finished in 1h 46m: Pass: 100%/396 | Total: 7d 15h | Avg: 27m 43s | Max: 1h 13m | Hits: 81%/22090
|
Project | |
---|---|
CCCL Infrastructure | |
+/- | libcu++ |
CUB | |
Thrust | |
CUDA Experimental | |
python | |
CCCL C Parallel Library | |
Catch2Helper |
Modifications in project or dependencies?
Project | |
---|---|
CCCL Infrastructure | |
+/- | libcu++ |
+/- | CUB |
+/- | Thrust |
+/- | CUDA Experimental |
+/- | python |
+/- | CCCL C Parallel Library |
+/- | Catch2Helper |
🏃 Runner counts (total jobs: 396)
# | Runner |
---|---|
327 | linux-amd64-cpu16 |
28 | linux-arm64-cpu16 |
26 | linux-amd64-gpu-v100-latest-1 |
15 | windows-amd64-cpu16 |
I am not a fan of this, because it might break existing code that looks whether those names are available. We should guard those with the macros and only replace the include with the forward declaration |
Can you elaborate what you mean with "those names"? Are you referring to whether the types So we should guard the forward declaratiions by |
Yes unconditionally forward declaring names might break code. We should guard that with the feature macros |
PR up: #2998 |
Description
closes #2933
Forward declare half types to avoid including the (expensive) fp16 headers.
Checklist