[SYCL RTC] Make resource.cpp independent of any includes
#20115
+43
−21
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
The rest of the project can use flags like `-stdlib=<...>` or `--sysroot` that might affect ABI. Rather than trying to propagate those through our fragile CMake hacks to compile that file with freshly built `clang`, make sure that the file is as self-sufficient as possible (i.e, no STL/libc usage) as that seems to be a more stable solution.
aelovikov-intel
temporarily deployed
to
WindowsCILock
GitHub Actions
Inactive
aelovikov-intel
had a problem deploying
to
WindowsCILock
GitHub Actions
Failure
aelovikov-intel
temporarily deployed
to
WindowsCILock
GitHub Actions
Inactive
aelovikov-intel
temporarily deployed
to
WindowsCILock
GitHub Actions
Inactive
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.
The rest of the project can use flags like
-stdlib=<...>or--sysrootthat might affect ABI. Rather than trying to propagate those through our fragile CMake hacks to compile that file with freshly builtclang, make sure that the file is as self-sufficient as possible (i.e, no STL/libc usage) as that seems to be a more stable solution.