-
Notifications
You must be signed in to change notification settings - Fork 787
[SYCL] persistent cache fix - directory creation and reporting improvements #13019
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
againull
merged 14 commits into
intel:sycl
from
cperkinsintel:cperkins-minor-err-report-improvement
Mar 28, 2024
Merged
Changes from all commits
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
99c54b9
minor improvement to reporting system err on cache file creation
cperkinsintel 9febda6
interim commit, need to switch
cperkinsintel bbee794
overly cautious error reporting
cperkinsintel 5ff82ea
clang-format
cperkinsintel 4e55d59
experimental
cperkinsintel a234292
inclusion
cperkinsintel fc6095c
adding arbitrary traces to try and understand what's going on.
cperkinsintel 79d2e28
working and tested
cperkinsintel 94eca4f
ensure no abi break
cperkinsintel ecffb6b
rework makeDir fix, but leaving old version intact for GCC < 8
cperkinsintel 4bc8642
resolve merge conflicts
cperkinsintel 533cbd4
dupes in merge. hmm
cperkinsintel d53d95d
another dupe from the merge
cperkinsintel 912e565
reviewer feedback
cperkinsintel File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we throw in this case as well, to align the two branches?
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
changing the signature of this function leads to an ABI break. Since we need to keep this old stuff anyway, I was thinking to keep it as is.
My preference would be to change the signature, throw always, and drop GCC < 8 support, but that decision isn't mine to make.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can keep the signature as is and still throw when we would have returned a non-zero code. I don't think we're handling non-zero codes returned from this anyway, are we?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
std::fileystem::create_directories
throws astd::filesystem::filesystem_error
but the "old" code doesn't havestd::filesystem
so can't throw that. I'm modifying it to throw std::runtime_error