-
Notifications
You must be signed in to change notification settings - Fork 787
[sycl-rel] Cherry-pick sanitizer patches #18885
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
[sycl-rel] Cherry-pick sanitizer patches #18885
Conversation
…d (#133046) When builtins are built with runtimes, it is built before compiler-rt, and this makes some of the HAS_XXX_FLAGs missing. In this case, the COMPILER_RT_HAS_FCF_PROTECTION_FLAG is missing which makes it impossible to enable CET in this case. This patch addresses this issue by also check for such flag in standalone build instead of relying on the compiler-rt's detection.
…bundler symbol table (intel#17399) `__MsanDeviceGlobalMetadata` etc are sanitizer internal variables, and should not be bundled to the symbol table.
Can we get some inputs about the test failures seen here? Thanks |
I retried the UR jobs and they are green now. |
Thanks @kbenzie. Can anyone comment on the other failures? Thanks |
Failures are unrelated, the pre-commit on this branch is broken. Will be tested separately, I will provide a link a bit later. |
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.
Cherry picks look good from 'offload bundler' perspective. It is interesting that offload bundler and the tests are inside the 'Driver' directory. But that concern is out-of-scope for this PR.
Thanks
Ignore the pre-commit, it's broken. The actual test run - https://github.com/intel/llvm/actions/runs/15631542807 |
@AlexeySachkov, does it make sense to request code owners review for cherry-picks to the release branch? All these patches were reviewed when being committed to the |
Since we're (not the authors of original commits) cherry-picking these patches ourselves, we may cherry-pick something excessive (like this compiler-rt patch), so it's good to have someone double-checking it (though it slows down the process). I believe in the future we'll update the process so that authors cherry-pick their patches themselves, maybe then we can update the protection rules to not require an approval. |
…one build (#133046)" This reverts commit fdf345b.
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.
Please, remove llvm/llvm-project@e54f31a changes.
@bader done |
My concerns are addressed. I leave it @AlexeySachkov to follow-up.
Cherry-pick commits that reached the internal branch between intel/llvm cutoff and release branch pulldown.