build: add more missing headers for GCC 15 #871
+1
−0
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
Contributor
|
@dbermond please correct commit msg according to https://github.com/intel/compute-runtime/blob/master/CONTRIBUTING.md
|
Needed for building with GCC 15 and later. Otherwise, a build error happens. Same situation of commit e0362a7. See the mentioned commit message for the full explanation. Signed-off-by: Daniel Bermond <[email protected]>
dbermond
force-pushed
the
gcc15-fix-more
branch
from
ffd2423 to
6984e12
Compare
Contributor
Author
|
Thank you for the reply. Commit message updated. Please let me know if something else needs to be changed. |
Contributor
|
one more issue, the commit type should be "test" as only test files are modified (change doesn't impact runtime behavior) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Needed for building with GCC 15 and later. Otherwise, a build error happens.
This seems to affect only the unit tests of the legacy version, as unit tests of the non-legacy version can be built fine without this change.
Same situation of commit: e0362a7
See the mentioned commit message for the full explanation.