Page 2 of 2 FirstFirst 12
Results 11 to 14 of 14

Thread: Official SYCL 1.2 Provisional feedback thread

  1. #11
    Junior Member
    Join Date
    Feb 2012
    Posts
    10
    Do I take it correctly from the specs, that now structs or classes can be passed to kernels? Or what exactly is the difference in capturing variables and passing them as lamdba parameters?

  2. #12
    Yes, SYCL allows you to pass any struct that is POD and doesn't contain pointers.

    Variables that are captured by the lambda are kernel arguments, these can be accessors, samplers and POD data types which don't contain pointers. The lambda parameters are specific types that are constructed within the kernel that are used to give host/device compatible access to the current work item's id information. For example, the parallel_for API takes an item object as the lambda's parameter.

  3. #13
    Junior Member
    Join Date
    Feb 2012
    Posts
    10
    Is there any way to get early access to the reference implementation done by Codeplay? Or at least get an estimate, as to when it will be available? (Although I would be glad to give it a spin)

  4. #14
    The Codeplay implementation of SYCL is not a reference implementation and is currently still in development, however anyone looking to get involved with the development of SYCL can contact us to discuss it further. Additionally there is an open source implementation of SYCL called triSYCL, which is still in the early stages of development, this can be found here.

Page 2 of 2 FirstFirst 12

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •