Skip to content

[DeviceMSAN] Check use-of-uninitialized value on private memory #17309

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

Merged
merged 17 commits into from
Mar 19, 2025

Conversation

AllanZyne
Copy link
Contributor

@AllanZyne AllanZyne commented Mar 5, 2025

Support check use-of-uninitialized value on private memory

@AllanZyne AllanZyne marked this pull request as ready for review March 5, 2025 06:21
@AllanZyne AllanZyne requested review from a team as code owners March 5, 2025 06:21
@AllanZyne
Copy link
Contributor Author

@intel/unified-runtime-reviewers, please review. Thanks.

@AllanZyne
Copy link
Contributor Author

@intel/llvm-gatekeepers, this pr is ready to merge. Thanks.

@kbenzie kbenzie merged commit 9ad2e87 into sycl Mar 19, 2025
31 checks passed
@AllanZyne AllanZyne deleted the review/yang/msan_private_mem_2 branch March 19, 2025 13:05
@@ -1,19 +0,0 @@
; RUN: opt < %s -passes=msan -msan-instrumentation-with-call-threshold=0 -msan-eager-checks=1 -S | FileCheck %s
Copy link
Contributor Author

@AllanZyne AllanZyne Apr 17, 2025

Choose a reason for hiding this comment

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

This test is removed because we have removed "tls" and needn't check function parameter.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants