[SYCL][RTC] Cache frontend invocation #16823
Draft
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
Signed-off-by: Julian Oppermann <[email protected]>
jopperm
had a problem deploying
to
WindowsCILock
GitHub Actions
Failure
jopperm
had a problem deploying
to
WindowsCILock
GitHub Actions
Failure
jopperm
had a problem deploying
to
WindowsCILock
GitHub Actions
Failure
jopperm
had a problem deploying
to
WindowsCILock
GitHub Actions
Failure
Signed-off-by: Julian Oppermann <[email protected]>
|
@sommerlukas @cperkinsintel I'll leave this PR in draft mode until discussions settle, but this is how I'd do the basic mechanism, to be extended with a more sophisticated cache lookup. |
jopperm
had a problem deploying
to
WindowsCILock
GitHub Actions
Failure
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.
Adds
sycl_jit-RTC-specific persistent caching to the runtime. The basic idea is to cache only the LLVM module resulting from the device compilation in bitcode format. Device linking and post-link would be run always (even for a cache hit), as invoking the frontend is the most expensive step in the pipeline right now.