Updates for oneAPI 2025.1 and client GPU debugging #2644
Conversation
This file contains 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.
Existing Sample Changes
Description
Behavior/output changed between 2025.0 and 2025.1, so updated for the changes. I also changed to a new debugging approach that does not rely on segfault functionality in the GPU driver (doesn't rely on GPU debugging at all), and re-ordered two operations to make it easier to demonstrate correct vs. incorrect configurations
Fixes Issue#
External Dependencies
Behavior depends on specific oneAPI (2025.1) and driver versions (Rolling Stable 2507.12) to attain desired behavior.
Type of change
How Has This Been Tested?