Skip to content

[DeviceSanitizer] Change "TargetTriple.isSPIR()" to "TargetTriple.isSPIROrSPIRV()" in AddressSanitizer.cpp #14413

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 2 commits into from
Jul 4, 2024

Conversation

AllanZyne
Copy link
Contributor

@AllanZyne AllanZyne commented Jul 3, 2024

SYCL is going to switch to SPIR-V backend soon, this PR changed "TargetTriple.isSPIR()" to "TargetTriple.isSPIROrSPIRV()" to improve compatibility

Copy link
Contributor

@sarnex sarnex left a comment

Choose a reason for hiding this comment

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

TY!

Copy link
Contributor

@zhaomaosu zhaomaosu left a comment

Choose a reason for hiding this comment

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

lgtm

@asudarsa
Copy link
Contributor

asudarsa commented Jul 3, 2024

It seems like this change might have exposed a latent bug in the SPIR-V backend code. @michalpaszkowski, can you please comment how to address the windows failure reported in the CI?

Thanks

@asudarsa
Copy link
Contributor

asudarsa commented Jul 3, 2024

@AllanZyne

Can you please add a line or two in the PR description about the need for this change? Just for logging purposes.

Thanks

@AllanZyne AllanZyne changed the title [DeviceSanitizer] Change "isSPIR" to "isSPIROrSPIRV" in AddressSanitizer.cpp [DeviceSanitizer] Change "TargetTriple.isSPIR()" to "TargetTriple.isSPIROrSPIRV()" in AddressSanitizer.cpp Jul 3, 2024
@AllanZyne
Copy link
Contributor Author

@AllanZyne

Can you please add a line or two in the PR description about the need for this change? Just for logging purposes.

Thanks

Done.

@AllanZyne
Copy link
Contributor Author

Hi @intel/llvm-gatekeepers, the failed test is not related to this test, this patch needs test using"-fsanitize=address" flag.
Thanks!

@michalpaszkowski
Copy link
Contributor

michalpaszkowski commented Jul 3, 2024

It seems like this change might have exposed a latent bug in the SPIR-V backend code. @michalpaszkowski, can you please comment how to address the windows failure reported in the CI?

Thanks

I wasn't able to reproduce the failure on a Windows build of SPIR-V backend both from this branch or the llvm-project repository. It might be the case that there is some memory leak/ownership issues inside LLVM (either in SPIR-V backend or otherplace), but this will require a bit more investigation. Unfortunately, rerunning this test many times does not help much.

@asudarsa @AllanZyne Would it be possible to rerun the Windows CI run? (I don't have such access in this repository to do this myself)

@sommerlukas
Copy link
Contributor

Can you try merging the latest changes from the sycl branch into your branch? There was some improvements made to Windows CI yesterday.

@AllanZyne
Copy link
Contributor Author

Can you try merging the latest changes from the sycl branch into your branch? There was some improvements made to Windows CI yesterday.

Sure

@AllanZyne
Copy link
Contributor Author

Hi @intel/llvm-gatekeepers, please merge.
Thanks!

@steffenlarsen steffenlarsen merged commit f57c921 into sycl Jul 4, 2024
14 checks passed
@bader bader deleted the review/yang/fix_spir_spirv branch September 17, 2024 00:16
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.

7 participants