Announcement

Collapse
No announcement yet.

OpenGL 4 Shader Image Extensions Land Today In RadeonSI Gallium3D

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

  • OpenGL 4 Shader Image Extensions Land Today In RadeonSI Gallium3D

    Phoronix: OpenGL 4 Shader Image Extensions Land Today In RadeonSI Gallium3D

    There are some notable improvements that landed today in RadeonSI Gallium3D for AMD GCN graphics processors...

    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
    GL_ARB_internalformat_query2 also committed for all drivers

    Comment


    • #3
      OpenGL 4.2 for RadeonSI in 11.3 would be amazing!

      Maybe even 4.3 the release after that, but that is being fairly hopeful. Intel might get 4.3 by then, though.

      Comment


      • #4
        Might want to check that Michael .. ARB_shader_atomic_counters hit the Mesa mailing list also though you'll need to wait for LLVM to get the patches merged into LLVM trunk (3.9). We'll be at OpenGL 4.2 very shortly once that's all reviewed!

        Comment


        • #5
          Originally posted by zanny View Post
          OpenGL 4.2 for RadeonSI in 11.3 would be amazing!

          Maybe even 4.3 the release after that, but that is being fairly hopeful
          4.3 is almost done
          4.4 is almost done
          and 4.5 is almost done
          by june you better spend your hope on polaris support or something like that

          Comment


          • #6
            Originally posted by pal666 View Post
            4.3 is almost done
            4.4 is almost done
            and 4.5 is almost done
            by june you better spend your hope on polaris support or something like that
            4.2 has been "almost" done in every driver since late 2015, and we are now almost 4 months into 2016, yet nobody is advertising 4.2 yet. Features do not come that fast, especially the last ones missing from each OGL version because they are often the hardest. Getting 60% of the way through any given version of OGL compliance is often only a quarter the work to advertise that version completely, especially considering how many GLSL changes can happen to make GLSL version compliance look a lot easier than it actually is.

            4.3 might be done for Mesa 11.3 / 12, and 4.4 might be done the release after that (unlikely, there is a lot of big functionality missing, and 4.3 is still compute shaders, which are a bucketload of work that is still not actually done yet) but 4.5 is certainly not going to come in 2016.

            Comment


            • #7
              Originally posted by zanny View Post
              4.2 has been "almost" done in every driver since late 2015, and we are now almost 4 months into 2016, yet nobody is advertising 4.2 yet. Features do not come that fast, especially the last ones missing from each OGL version because they are often the hardest. Getting 60% of the way through any given version of OGL compliance is often only a quarter the work to advertise that version completely, especially considering how many GLSL changes can happen to make GLSL version compliance look a lot easier than it actually is.
              that was wall of useless text. when i say almost done i mean few remaining extensions are almost done each. and they are developed by different people
              Originally posted by zanny View Post
              4.3 might be done for Mesa 11.3 / 12, and 4.4 might be done the release after that (unlikely, there is a lot of big functionality missing, and 4.3 is still compute shaders, which are a bucketload of work that is still not actually done yet) but 4.5 is certainly not going to come in 2016.
              where do you get that shit from? 4.4 has two simple extensions which are already done for nvc0(i.e. for gallium) and one which was already posted for review. compute shaders are done for opencl and were waiting for images which are done already. 4.5 consists of duplicate extenstions from es31, cull distance and robustness which i'm pretty sure do not need another year

              Comment


              • #8
                Originally posted by spstarr View Post
                Might want to check that Michael .. ARB_shader_atomic_counters hit the Mesa mailing list also though you'll need to wait for LLVM to get the patches merged into LLVM trunk (3.9). We'll be at OpenGL 4.2 very shortly once that's all reviewed!
                I was referirng to what's merged.
                Michael Larabel
                https://www.michaellarabel.com/

                Comment


                • #9
                  Remaining... Still need robust_buffer_access_behaviour for 4.3. I'd expect the rest of 4.3 to be done in both radeonsi and intel by the time 12.0 is released.

                  all drivers
                  4.3 robust_buffer_access_behavior (not started)
                  4.4 enhanced_layouts (in progress - patches are out, needs lots of review)
                  4.5 ES3_1_compatibility (in progress - needs some ES extensions but they're mostly just different entry points to existing code/features)
                  4.5 cull_distance (not started)


                  intel
                  4.0/4.2 fp64 (patches are done, needs lots of review)
                  4.4 texture_stencil8
                  4.4 query_buffer_object


                  radeonsi
                  4.2 atomic counters (patches out)
                  4.3 shader_storage_buffer_object (patches out)
                  4.3 fbo no attachments (in progress, should be soon)
                  4.3 compute shaders (presumably just hooking up existing functionality, so i'd expect it not to be too hard)
                  4.4 clear_texture
                  4.4 query_buffer_object


                  nvc0
                  4.2 shader_image_load_store and shader_image_size
                  4.3 fbo no attachments (in progress, should be soon)

                  Comment


                  • #10
                    Note: You need LLVM 3.9 for this support. Hopefully the various driver repos can support that quickly.

                    Comment

                    Working...
                    X