[SYCL] Use -fsemantic-interposition for device_selector.cpp #7022
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We build the whole project with -fno-semantic-interposition by default and it gets miscompiled by clang after intel#6896. It's not yet clear if this would be a permanent fix or if there is a bug in clang. The issue is being tracked at llvm/llvm-project#58295.
KseniyaTikhomirova
approved these changes
Oct 13, 2022
|
@intel/llvm-gatekeepers , this PR is ready. |
aelovikov-intel
added a commit
to aelovikov-intel/llvm
that referenced
this pull request
Oct 13, 2022
Fixes the issue introduced by intel#7022.
pvchupin
pushed a commit
that referenced
this pull request
Oct 13, 2022
Fixes the issue introduced by #7022.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We build the whole project with -fno-semantic-interposition by default and it gets miscompiled by clang after #6896.
It's not yet clear if this would be a permanent fix or if there is a bug in clang. The issue is being tracked at llvm/llvm-project#58295.