Skip to content

Add note about compute sanitizer for ccx.Device() - #733

Closed
ZzEeKkAa wants to merge 2 commits into
NVIDIA:mainfrom
ZzEeKkAa:yhavrylko/docs/cxx_device_cs_note
Closed

Add note about compute sanitizer for ccx.Device()#733
ZzEeKkAa wants to merge 2 commits into
NVIDIA:mainfrom
ZzEeKkAa:yhavrylko/docs/cxx_device_cs_note

Conversation

@ZzEeKkAa

@ZzEeKkAa ZzEeKkAa commented Jun 27, 2025

Copy link
Copy Markdown
Contributor

Description

Add note on using ccx.Device() with compute-sanitizer.

Related issue: #562

Checklist

  • I am familiar with the Contributing Guidelines.
  • n/a New or existing tests cover these changes.
  • The documentation is up to date with these changes.

@copy-pr-bot

copy-pr-bot Bot commented Jun 27, 2025

Copy link
Copy Markdown
Contributor

Auto-sync is disabled for ready for review pull requests in this repository. Workflows must be run manually.

Contributors can view more details about this message here.

@leofang

leofang commented Jun 27, 2025

Copy link
Copy Markdown
Member

Thanks, Yevhenii! I think this impacts to all cuda.core objects, not just Device. I am thinking we should create a new "Tips & Tricks" page like what we did for cuda.bindings, and move this note there. WDYT?

@leofang
leofang self-requested a review June 27, 2025 14:57
@leofang leofang added this to the cuda.core beta 5 milestone Jun 27, 2025
@leofang leofang added documentation Improvements or additions to documentation P1 Medium priority - Should do cuda.core Everything related to the cuda.core module labels Jun 27, 2025
@ZzEeKkAa

Copy link
Copy Markdown
Contributor Author

Yeah, we can do that. I'm wondering how to do it the way, so if user face this problem, they will navigate to the correct place...

@leofang

leofang commented Jun 28, 2025

Copy link
Copy Markdown
Member

What do you mean?

@cpcloud cpcloud left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems fine to merge after fixing up conflicts.

Extending this to other objects/writing up tips and tricks can be done in a follow-up.

@github-project-automation github-project-automation Bot moved this from Todo to In Review in CCCL Oct 30, 2025
@cpcloud

cpcloud commented Nov 10, 2025

Copy link
Copy Markdown
Contributor

@ZzEeKkAa Can you fix conflicts so we can merge?

@leofang

leofang commented Nov 10, 2025

Copy link
Copy Markdown
Member

I suggest we close this and work on #1223. It does not make sense to add such a note to the device class.

@leofang leofang closed this Nov 13, 2025
@github-project-automation github-project-automation Bot moved this from In Review to Done in CCCL Nov 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cuda.core Everything related to the cuda.core module documentation Improvements or additions to documentation P1 Medium priority - Should do

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

3 participants