Announcement

Collapse
No announcement yet.

R600 Gallium3D LLVM & SB Shader Back-End Tests

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

  • R600 Gallium3D LLVM & SB Shader Back-End Tests

    Phoronix: R600 Gallium3D LLVM & SB Shader Back-End Tests

    In recent months I have delivered a number of R600 SB shader optimization benchmarks for the AMD Gallium3D shader back-end that's part of Mesa 9.2. I've also delivered tests of the R600 LLVM back-end that's also been progressing in recent months and viewed as the future for AMD's open-source driver. This weekend are some independent tests of the R600 LLVM and SB back-ends...

    http://www.phoronix.com/vr.php?view=MTQzODc

  • #2
    Also having Catalyst there would be interesting.

    Comment


    • #3
      Yep, I checked the latest catalyst comparison and it didn't have reaction quake results.

      Comment


      • #4
        Those optimizations are part of 9.2 right??

        Comment


        • #5
          Originally posted by 89c51 View Post
          Those optimizations are part of 9.2 right??
          Not enabled by default.

          Comment


          • #6
            How can I enable this features in mesa 9.2?

            Comment


            • #7
              Originally posted by edoantonioco View Post
              How can I enable this features in mesa 9.2?
              You can choose sb+llvm backend by setting: export R600_DEBUG=sb

              for just sb backend export R600_DEBUG=sb,nollvm

              If you use KDE you can create file in /.kde4/env called for example export.sh then add to it export R600_DEBUG=<backend> and give executable right to it.

              cheers

              ps sorry for my english.

              Comment


              • #8
                Originally posted by Tommy666 View Post
                You can choose sb+llvm backend by setting: export R600_DEBUG=sb

                for just sb backend export R600_DEBUG=sb,nollvm

                If you use KDE you can create file in /.kde4/env called for example export.sh then add to it export R600_DEBUG=<backend> and give executable right to it.

                cheers

                ps sorry for my english.
                Thanks for the info
                Luckily, I use KDE too.

                Comment


                • #9
                  Edit /etc/environment and put
                  Code:
                  R600_DEBUG=sb,nollvm
                  in it (without 'export'). This will set it system wide after reboot.

                  Comment


                  • #10
                    Originally posted by gradinaruvasile View Post
                    Edit /etc/environment and put
                    Code:
                    R600_DEBUG=sb,nollvm
                    in it (without 'export'). This will set it system wide after reboot.
                    Thanks a lot for the info, but I have to ask: Why "nollvm"? Is there a reason for not to enable it?

                    Comment

                    Working...
                    X