-
Notifications
You must be signed in to change notification settings - Fork 42
Merge v0.11.x into main #1302
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
lukaszstolarczuk
merged 19 commits into
oneapi-src:main
from
lukaszstolarczuk:merge-v0.11.x-into-main
May 8, 2025
Merged
Merge v0.11.x into main #1302
lukaszstolarczuk
merged 19 commits into
oneapi-src:main
from
lukaszstolarczuk:merge-v0.11.x-into-main
May 8, 2025
Conversation
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
Search for autoreconf package in the Linux system before trying to fetch and build the hwloc library.
[0.11.x] Disable hwloc in case of missing autoreconf
when UMF_USE_DEBUG_POSTFIX CMake option is set.
- add installation tests step to Windows generators nightly tests
Signed-off-by: Lukasz Dorau <[email protected]>
In case of error in the init function, cleanup was being called on 'provider' which was being initialized at the very end of init function, instead of 'ze_provider'.
Signed-off-by: Lukasz Dorau <[email protected]>
`new_offset_mmap` can be greater than `file_provider->size_mmap`, so `file_provider->size_mmap - new_offset_mmap` would be an underflow in this case. Signed-off-by: Lukasz Dorau <[email protected]>
Signed-off-by: Lukasz Dorau <[email protected]>
…for-v0.11.0 Merge fixes for v0.11.0
In some cases the global state may have been destroyed when we reach `umfDestroyPool` or `umfDestroyProvider`, in which case actually going through with the destruction will cause segmentation faults. The way the global state is managed should maybe be re-worked, but this should be an okay workaround to avoid segmentation faults until then.
[v0.11.x] Check global state destruction in destructors
They are misleadingly read as errors, while they are simply debug information that these targets aren't accessible on a machine.
[v0.11.x] Downgrade error logs to debug in memspaces and memtargets
bratpiorka
approved these changes
May 8, 2025
lplewa
approved these changes
May 8, 2025
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.
Merge back stable branch into main, mainly to get the release notes. All fixes were cherry-picked from main to stable, anyway.