Draft
Conversation
abhinav92003
approved these changes
Jan 11, 2024
Contributor
|
Looks like the clang-format workflow failures are from libipt. Can we somehow disable clang for that dir? |
Contributor
Saw later that the failures are also there in other workflows. So it's a real build issue with the new libipt? Maybe some changes are needed to our build? |
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
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.
This update upgrades libipt to its latest stable version (v2.1). The new version of libipt introduces support for newer CPU models and addresses several decoding-related bugs.
Issue: #6486