-
Notifications
You must be signed in to change notification settings - Fork 796
[DeviceSanitizer] Only allows to report one error per each kernel launch #15326
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
[DeviceSanitizer] Only allows to report one error per each kernel launch #15326
Conversation
When error is detected, the corresponding work-item will exit without unpoisoning local/private shadow memory. Then other work-items are eary to cause false alarms. So, we only allows to report one error per each kernel launch by default.
|
How about skipping sanitizer when "UR_SANITIZER_INCLUDE_DIR" is empty string? |
Done. |
|
please rebase (and ping me, I want to merge this asap) |
@pbalcer, thanks, done. |
|
@intel/llvm-reviewers-runtime can you please review? thanks. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! We need the repo redirect addressed before we merge however.
|
@intel/llvm-gatekeepers please merge |
When error is detected, the corresponding work-item will exit without unpoisoning local/private shadow memory. Then other work-items are easy to cause false alarms. So, we only allows to report one error per each kernel launch by default.
UR Part: oneapi-src/unified-runtime#2069