Announcement

Collapse
No announcement yet.

Khronos Releases OpenCL 2.2-11 While Still Waiting For OpenCL-Next

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Khronos Releases OpenCL 2.2-11 While Still Waiting For OpenCL-Next

    Phoronix: Khronos Releases OpenCL 2.2-11 While Still Waiting For OpenCL-Next

    The Khronos Group has released the OpenCL 2.2-11 specification to address various issues with the existing OpenCL specification while the next major release as "OpenCL-Next" is likely still a number of months away...

    http://www.phoronix.com/scan.php?pag....2-11-Released

  • #2
    The adoption rate of newer OpenCL versions is very poor. Is their framework approach supposed to fix that? I cannot see that it would improve adoption if important features are not supported by all vendors.

    Comment


    • #3
      Originally posted by ms178 View Post
      The adoption rate of newer OpenCL versions is very poor.
      For us, the massive inconvenience of it not working on a specific platform configuration easily outweighs the small conveniences of the newer spec.

      We stick with OpenCL 1.2 as the lowest common denominator approach.

      What we find interesting is that currently CUDA is more readily available than newer versions of OpenCL and tying ourselves down to that is also not acceptable.

      Though as with OpenGL certainly all blame belongs to the GPU manufacturers more than OpenCL or Khronos.

      Comment


      • #4
        Just yesterday watched interesting presentation from Dave about state of CUDA, OpenCL, etc. on Linux.
        https://www.youtube.com/watch?v=ZTq8wKnVUZ8

        Comment


        • #5
          Originally posted by pkunk View Post
          Just yesterday watched interesting presentation from Dave about state of CUDA, OpenCL, etc. on Linux.
          https://www.youtube.com/watch?v=ZTq8wKnVUZ8

          Comment


          • #6
            I wonder what is the difference between OpenCL and compute shaders. I'm no expert but it seems to me that they both do the same job.. what's the difference?

            Edit: Google already has an answer for me: https://stackoverflow.com/questions/...compute-shader
            Last edited by Creak; 08-07-2019, 09:04 AM.

            Comment


            • #7
              Originally posted by ms178 View Post
              The adoption rate of newer OpenCL versions is very poor. Is their framework approach supposed to fix that? I cannot see that it would improve adoption if important features are not supported by all vendors.
              If OpenCL-Next follows Vulkan's approach the adoption should be much smoother than OpenCL, because newer features should be easier to implement.

              Comment


              • #8
                And people balked at the idea of Metal being an infusion of OpenCL and low level API for graphics on OS X. Apple keeps moving rapidly forward while OCL languishes with the level of adoption support, creating tiers based upon the graphics cards as selling points for Compute capabilities or not.

                Comment


                • #9
                  The main question is: will OpenCL-Next be a completely different API like Vulkan is to OpenGL, or just a big upgrade - basically OpenCL 3.0?

                  Comment


                  • #10
                    Khronos should really bundle all of their APIs together. It’s a real pain having various versions of CL GL Vulkan video deciding not standardised together...

                    Comment

                    Working...
                    X