[SYCL] Use image pointer as a unique identifier for cache #7113
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.
Currently different paths for building programs use different cache keys. Specifically, one path uses the kernel-set-id while another uses the pointer to the binary image. This may cause device binaries built by both paths may cause the programs to be rebuilt. Additionally, since the kernel-set-id may cover multiple device binaries, it may make colliding cache kernels.
To fix the problems this commit will change the key use an image identifier rather than the kernel-set-id. We use the device binary pointer as the unique identifier.