-
Notifications
You must be signed in to change notification settings - Fork 1k
[EXPER] Use improved thrust execution-policy checker #21061
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
base: main
Are you sure you want to change the base?
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. |
|
/ok to test |
|
/ok to test |
|
/ok to test |
|
/ok to test |
|
/ok to test |
|
/ok to test |
|
/ok to test |
|
/ok to test |
|
CCCL already guarantees that if a value is returned, a sync is required even with a nosync policy, regardless of whether that returned value is used or discarded. See docs linked here (also copied below for simplicity). That means we can simplify our usage to "always nosync." We never have to think about the differences and the correctness is self-enforcing. |
Description
Experimental script for checking thrust calls are execution policy nosync compliant.
If a thrust call returns a value, then nosync is not required.
Checklist