Skip to content
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

Jump to bottom

Proposal to replace "3.2. Anatomy of a SYCL application" by a USM example #703

Open
TApplencourt opened this issue Jan 29, 2025 · 1 comment
Open

Proposal to replace "3.2. Anatomy of a SYCL application" by a USM example #703

TApplencourt opened this issue Jan 29, 2025 · 1 comment
Labels
editorial Some purely editorial problem

Comments

@TApplencourt
Copy link
Contributor

When people read the spec, the first example of SYCL they see (https://registry.khronos.org/SYCL/specs/sycl-2020/html/sycl-2020.html#sec:anatomy) is a buffer example. It doesn't represent the reality of how people are using SYCL.

I would suggest replacing it with a USM example.
@TApplencourt TApplencourt added the editorial Some purely editorial problem label Jan 29, 2025
@keryell
Copy link
Member

keryell commented Jan 30, 2025

On the other hand I cry when I see pointers in some modern C++ code.

@keryell keryell mentioned this issue Jan 30, 2025
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
editorial Some purely editorial problem
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@keryell @TApplencourt