Page 1 of 2 12 LastLast
Results 1 to 10 of 11

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

  1. #1
    Join Date
    Jan 2007
    Posts
    14,324

    Default 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. #2
    Join Date
    Sep 2008
    Location
    Vilnius, Lithuania
    Posts
    2,518

    Default

    Also having Catalyst there would be interesting.

  3. #3
    Join Date
    Feb 2008
    Location
    Linuxland
    Posts
    4,988

    Default

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

  4. #4
    Join Date
    Jan 2009
    Posts
    1,591

    Default

    Those optimizations are part of 9.2 right??

  5. #5
    Join Date
    Jan 2007
    Location
    Germany
    Posts
    2,116

    Default

    Quote Originally Posted by 89c51 View Post
    Those optimizations are part of 9.2 right??
    Not enabled by default.

  6. #6
    Join Date
    Apr 2013
    Posts
    101

    Default

    How can I enable this features in mesa 9.2?

  7. #7
    Join Date
    Aug 2009
    Posts
    20

    Default

    Quote 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.

  8. #8
    Join Date
    Apr 2013
    Posts
    101

    Default

    Quote 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.

  9. #9

    Default

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

  10. #10
    Join Date
    Apr 2013
    Posts
    101

    Default

    Quote 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?

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •