Skip to content

Elaborate open issue with free function kernels #15463

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.

Sign up for GitHub

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
merged 1 commit into from
Oct 8, 2024
Merged

Elaborate open issue with free function kernels #15463

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions sycl/doc/extensions/proposed/sycl_ext_oneapi_free_function_kernels.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -963,6 +963,13 @@ int main() {
```
+
Where `kfp` would have some nicer name.
+
With either form above, it seems like we have enough type information for the
header to check that the types of the actual kernel arguments are implicitly
convertible to the types of the formal kernel parameters, and we can raise a
compile-time error if they are not.
In addition, the header can perform any necessary implicit conversions when
setting the kernel argument values.

* We are debating whether we should allow a free function kernel to be defined
with an initial "iteration index" parameter such as:
Expand Down