Announcement

Collapse
No announcement yet.

OpenCL 2.2-10 Released With Fixes

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

  • OpenCL 2.2-10 Released With Fixes

    Phoronix: OpenCL 2.2-10 Released With Fixes

    While "OpenCL-Next" will hopefully be on track for releasing later this year as the next big update to OpenCL, OpenCL 2.2-10 was released today by The Khronos Group as the latest maintenance update to the nearly two year old OpenCL 2.2 specification...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite

  • #2
    Originally posted by phoronix View Post
    OpenCL-Next can't come soon enough to hopefully bolster OpenCL GPU programming adoption
    Raspberry Pi v4 can't come soon enough to hopefully bolster OpenCL GPU programming adoption.

    Comment


    • #3
      OpenCL-Next can't come soon enough to hopefully bolster OpenCL GPU programming adoption and OpenCL 2.2 showing its age with the provisional specification for it approaching three years old
      The 90% of OpenCl projects use OpenCl 1.2 (source: Neil Trevett), so the slow update of OpenCl is not a problem.

      Comment


      • #4
        Originally posted by boboviz View Post
        The 90% of OpenCl projects use OpenCl 1.2 (source: Neil Trevett), so the slow update of OpenCl is not a problem.
        That might be rather self-serving of him. If Nvidia (of which he's a VP) would support anything higher, that number would certainly drop.

        Comment


        • #5
          Originally posted by coder View Post
          That might be rather self-serving of him. If Nvidia (of which he's a VP) would support anything higher, that number would certainly drop.
          Nvidia actively supporting OpenCL or promoting it at all would be foolish so they are not going to do that. There's this proprietary alternative called CUDA and it's exclusive to NVidia products. Make your code in OpenCL and you'll be able to use whatever GPU happens to provide the best price/performance when you upgrade your hardware down the line, choose CUDA and you're forever locked into using NVidia products. That's obviously not something NVidia wants, why would they? There's a reason AMD is hell-bent on promoting their open source ROCm alternative.

          As for OpenCL 2.0: It's interesting to note that MESA's clover OpenCL for AMD GPUs is stuck at OpenCL 1.2.

          Comment


          • #6
            Originally posted by coder View Post
            That might be rather self-serving of him. If Nvidia (of which he's a VP) would support anything higher, that number would certainly drop.
            That's a great point. I cannot understand why the president of Kronos (leader in open source code) is a VP of a company devoted to closed source.

            Returning to argument: i think that AMD is the disappointment of OpenCl ecosystem. They are working slowly and, seems to me, without conviction.

            Comment


            • #7
              Originally posted by coder View Post
              That might be rather self-serving of him. If Nvidia (of which he's a VP) would support anything higher, that number would certainly drop.
              NVIDIA will support OpenCL Next.
              Michael Larabel
              https://www.michaellarabel.com/

              Comment


              • #8
                P.S. It's not only Trevett that says that most used version is 1.2.

                Comment


                • #9
                  Originally posted by Michael View Post
                  NVIDIA will support OpenCL Next.
                  5 years after the release :-P

                  Comment


                  • #10
                    Originally posted by boboviz View Post
                    P.S. It's not only Trevett that says that most used version is 1.2.
                    Oh, I didn't say he's lying (though it would be interesting to know his sources).

                    My point is that highlighting it leads to somewhat circular reasoning that could justify why Nvidia hasn't moved beyond 1.2.

                    Comment

                    Working...
                    X