-
Notifications
You must be signed in to change notification settings - Fork 788
[AsyncAlloc][SYCL][ABI-BREAK] Use the SYCL properties extension for memory pool creation #17955
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
[AsyncAlloc][SYCL][ABI-BREAK] Use the SYCL properties extension for memory pool creation #17955
Conversation
dcb5523
to
8712e9f
Compare
…emory pool creation Introduce initial_threshold, maximum_size, read_only, and zero_init runtime properties conforming to the SYCL properties extension, and apply these properties to the creation of memory pools.
We are not allowed to break ABI outside of the window, is it possible to guard the breaking changes with __INTEL_PREVIEW_BREAKING_CHANGES macro? |
8712e9f
to
b615655
Compare
b615655
to
6171ed8
Compare
6171ed8
to
599af2f
Compare
599af2f
to
b0e7b06
Compare
7cd8ba7
to
5d77b23
Compare
@omarahmed1111 @Seanst98 I'm very sorry, I completely missed that this is an experimental extension which has been just recently implemented (so, as far as I understand it hasn't even made it to the previous release). For experimental extensions it is allowed to break ABI, so initial version of the PR was good (i.e. there is no necessity to guard with __INTEL_PREVIEW_BREAKING_CHANGES). Again, really sorry for false alarm |
b79af62
to
2b43de3
Compare
2b43de3
to
19971e8
Compare
05164ff
to
f9761f8
Compare
Introduce initial_threshold, maximum_size, read_only, and zero_init runtime properties conforming to the SYCL properties extension, and apply these properties to the creation of memory pools.
This PR is a draft until the feature has been added to the sycl_ext_oneapi_async_memory_alloc spec.