Skip to content

[SYCL][ABI-break] Introduce fusion properties #6619

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

Closed

Conversation

sommerlukas
Copy link
Contributor

Introduces properties for accessors and buffers related to the kernel fusion extension proposal.

Stores the value of the property in the accessor host implementation (AccessorImplHost), which is an ABI-breaking change. The property is only needed by the runtime on the host side, so it is not stored on the device side.

This is of course not a complete port of the kernel fusion extension. However, as storing the corresponding properties that can be attached to accessor requires an ABI-breaking change, we propose this change for early integration while the ABI-breaking window is still open.

Introduces properties for accessors and buffers related to kernel fusion.

Stores the value of the property in the accessor host implementation
(AccessorHostImpl), which is an ABI-breaking change.
@sommerlukas sommerlukas requested a review from a team as a code owner August 22, 2022 15:16
@romanovvlad
Copy link
Contributor

Probably, this patch needs to be rebased on the work being done in #6614.

@sommerlukas
Copy link
Contributor Author

Probably, this patch needs to be rebased on the work being done in #6614.

Agreed, thanks for pointing this out.

If the implementation and ABI-breaking change in #6614 would already allow to store all runtime-properties in the AccessorImplHost, we could use that solution and most likely wouldn't need to add another ABI-breaking change.
See my comment in the other PR.

@sommerlukas
Copy link
Contributor Author

Closing this, as the ABI-breaking changes are superseded by #6614, because their implementation allows to store all runtime-properties on accessors, not just the fusion-specific.

The remaining changes in this PR can be introduced properly together with the rest of kernel fusion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants