Announcement

Collapse
No announcement yet.

OpenCL 1.2 Support Merged For Mesa's Gallium3D Clover While OpenCL 3.0 Is Being Tackled

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

  • #11
    This is good news. Brings us one step closer to being able to ditch closed-source drivers.

    Comment


    • #12
      Originally posted by Black_Fox View Post
      Does this mean I could run [email protected] on my RX 570 on Mesa 20.3 fully? Last time I tried I had to kludge together a hybrid of AMDGPU OpenCL + Mesa everything else.
      It indeed works here on Polaris, which is a great achievement. Though ppd are still way lower than with amdgpu-pro Orca CL driver.
      clinfo also still reports CL 1.1 for whatever reason.

      Comment


      • #13
        Originally posted by aufkrawall View Post
        It indeed works here on Polaris, which is a great achievement. Though ppd are still way lower than with amdgpu-pro Orca CL driver.
        clinfo also still reports CL 1.1 for whatever reason.
        That's great! Thanks for trying it out. While not fully ready yet, I'm curious what more the devs will achieve in this area before the stable 20.3 release comes out.

        Comment


        • #14
          Originally posted by aufkrawall View Post
          It indeed works here on Polaris, which is a great achievement. Though ppd are still way lower than with amdgpu-pro Orca CL driver.
          clinfo also still reports CL 1.1 for whatever reason.
          clover still only advertises OpenCL 1.1 as printf() is not supported yet.

          Comment


          • #15
            Originally posted by aufkrawall View Post
            It indeed works here on Polaris, which is a great achievement. Though ppd are still way lower than with amdgpu-pro Orca CL driver.
            clinfo also still reports CL 1.1 for whatever reason.
            woow, nice
            It means that no more proprietary opencl( on non-Rocm hardware )

            Comment


            • #16
              Originally posted by LinAGKar View Post
              Only ROCm, which only works on some systems.
              Some? Vega and newer should work everywhere.

              Comment


              • #17
                Originally posted by oleid View Post

                Some? Vega and newer should work everywhere.
                Polaris is probably more common, and needs PCIe 3.0 for ROCm unless that's changed?

                Comment


                • #18
                  Originally posted by s_j_newbury View Post

                  Polaris is probably more common, and needs PCIe 3.0 for ROCm unless that's changed?
                  AFAIK no atomics are required from Vega on. Not sure why Polaris would still need them.
                  But isn't PCIe 3.0 common nowadays? I mean, PCIe 3.0 specs was released in 2010.

                  Comment


                  • #19
                    But does [email protected] even work with rocm? If not, why not, and why does clover already work? I'd assume that you can simply forget about rocm for consumer/prosumer purposes. It's such a relief that work is going on for clover...

                    Comment


                    • #20
                      Originally posted by aufkrawall View Post
                      It indeed works here on Polaris, which is a great achievement. Though ppd are still way lower than with amdgpu-pro Orca CL driver.
                      clinfo also still reports CL 1.1 for whatever reason.
                      If the program you want to run doesn't require printf() support, you can force CL 1.2 using the following environment variables:
                      Code:
                      CLOVER_PLATFORM_VERSION_OVERRIDE=1.2 CLOVER_DEVICE_VERSION_OVERRIDE=1.2 CLOVER_DEVICE_CLC_VERSION_OVERRIDE=1.2  ./your_program

                      Comment

                      Working...
                      X