Announcement

Collapse
No announcement yet.

AMD Drops TGSI Support From Their RadeonSI OpenGL Driver

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

  • AMD Drops TGSI Support From Their RadeonSI OpenGL Driver

    Phoronix: AMD Drops TGSI Support From Their RadeonSI OpenGL Driver

    It was just shy of a month ago in Mesa 20.0-devel code that RadeonSI enabled NIR by default to enjoy OpenGL 4.6 support and now already ahead of the Mesa 20.0 branching the previous TGSI code-path has been removed. TGSI has been the default intermediate representation of RadeonSI and other Gallium3D drivers but these days NIR has become the go-to IR for Mesa drivers...

    http://www.phoronix.com/scan.php?pag...nSI-Drops-TGSI

  • #2
    that is certainly a good development - here is to uncovering all the edge cases in the new 20 release :P

    Comment


    • #3
      Code removal feels so nice

      Comment


      • #4
        Is there an impact to certain state trackers, like nine?

        Comment


        • #5
          Originally posted by geearf View Post
          Is there an impact to certain state trackers, like nine?
          Nine should continue to work—radeonsi will translate the TGSI supplied by nine to NIR via tgsi_to_nir, like iris does. So everything is still supported, but now everything goes through NIR and there's one fewer path in the driver.

          (I wondered this myself, so I looked at the patches earlier.)
          Free Software Developer .:. Mesa and Xorg
          Opinions expressed in these forum posts are my own.

          Comment


          • #6
            Originally posted by Kayden View Post

            Nine should continue to work—radeonsi will translate the TGSI supplied by nine to NIR via tgsi_to_nir, like iris does. So everything is still supported, but now everything goes through NIR and there's one fewer path in the driver.

            (I wondered this myself, so I looked at the patches earlier.)
            Awesome, thank you for looking it up and answering!

            Comment


            • #7
              I believe this is the right decision, the NIR environment variable caused some confusion in the past, so it's good to drop TGSI and to focus on just one path.

              Comment


              • #8
                Originally posted by Kayden View Post

                Nine should continue to work—radeonsi will translate the TGSI supplied by nine to NIR via tgsi_to_nir, like iris does. So everything is still supported, but now everything goes through NIR and there's one fewer path in the driver.

                (I wondered this myself, so I looked at the patches earlier.)
                I was going to ask basically the same question, but for the video-decoding state trackers. Hopefully the TGSI->NIR pass doesn't have any oddball corner cases that we haven't stumbled upon yet.

                Comment


                • #9
                  Originally posted by Veerappan View Post

                  I was going to ask basically the same question, but for the video-decoding state trackers. Hopefully the TGSI->NIR pass doesn't have any oddball corner cases that we haven't stumbled upon yet.
                  Yeah, that's another reason for TGSI->NIR. If there are any, we'll have to fix them :)
                  Free Software Developer .:. Mesa and Xorg
                  Opinions expressed in these forum posts are my own.

                  Comment


                  • #10
                    That's not very impressive. Still waiting for ACO in radeonsi. =P

                    Comment

                    Working...
                    X