Results 1 to 10 of 31

Thread: In Road To OpenCL, R600g LLVM Back-End Arrives

Hybrid View

  1. #1
    Join Date
    Jan 2007
    Posts
    15,130

    Default In Road To OpenCL, R600g LLVM Back-End Arrives

    Phoronix: In Road To OpenCL, R600g LLVM Back-End Arrives

    Before calling it a week, Tom Stellard at AMD published a Git branch that offers up an LLVM shader back-end for the AMD R600 Gallium3D driver. This is one of the steps in bringing Compute/OpenCL support to the open-source AMD Radeon Linux graphics drivers...

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

  2. #2
    Join Date
    Nov 2008
    Location
    Madison, WI, USA
    Posts
    877

    Default

    Quote Originally Posted by phoronix View Post
    Phoronix: In Road To OpenCL, R600g LLVM Back-End Arrives

    Before calling it a week, Tom Stellard at AMD published a Git branch that offers up an LLVM shader back-end for the AMD R600 Gallium3D driver. This is one of the steps in bringing Compute/OpenCL support to the open-source AMD Radeon Linux graphics drivers...

    http://www.phoronix.com/vr.php?view=MTAyNTg
    Very cool. I'll be anxiously awaiting more news about this.

  3. #3
    Join Date
    Jan 2009
    Posts
    1,709

    Default

    this are the stuf that will make Clover HW accelerated right?

  4. #4
    Join Date
    Nov 2007
    Posts
    77

    Default

    Quote Originally Posted by 89c51 View Post
    this are the stuf that will make Clover HW accelerated right?
    This will make any gallium interface accelerated. Clover needs to support HW acceleration on a gallium interface first though, but this is a step in the right direction.

  5. #5
    Join Date
    Jan 2009
    Posts
    1,709

    Default

    Quote Originally Posted by Laughing1 View Post
    This will make any gallium interface accelerated. Clover needs to support HW acceleration on a gallium interface first though, but this is a step in the right direction.
    if i get the whole G3D thing right (which i probably don't) the order is somehow like App(graphics or something) >> OpenGL >> TGSI >> HW >>magic on the screen

    with toms work App(graphics or something) >> OpenGL >> LLVM to TGSI >> HW >> magic on the screen

    so if Clover has (or gets) an llvm backend will be accelerated



    yes the question might be stupid or trivial to some so i appologize

  6. #6
    Join Date
    Feb 2009
    Location
    France
    Posts
    309

    Default

    Quote Originally Posted by 89c51 View Post
    with toms work App(graphics or something) >> OpenGL >> LLVM to TGSI >> HW >> magic on the screen
    Well, that would actually look like this:

    App(graphics or something) >> OpenGL (G3D state tracker) >> TGSI (G3D's IR of choice) >> LLVM IR >> LLVM backend for AMD cards >> HW >> magic on the screen

    I'm just speaking about the code, no runtime or anything.

  7. #7
    Join Date
    Oct 2008
    Posts
    3,174

    Default

    It currently looks something like this:

    App -> OpenGL -> GLSL IR -> TGSI -> hardware

    The new stack allows this:

    App -> OpenGL -> GLSL IR -> TGSI -> LLVM -> hardware

    But in the long run, it would make this possible:

    App -> OpenCL -> LLVM -> hardware,

    as well as

    App -> OpenGL -> GLSL IR -> LLVM -> hardware

Posting Permissions

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