Announcement

Collapse
No announcement yet.

In Road To OpenCL, R600g LLVM Back-End Arrives

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

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

    Comment


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

      Comment


      • #4
        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.

        Comment


        • #5
          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

          Comment


          • #6
            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.

            Comment


            • #7
              I think the idea is to let clover feed LLVM IR directly into the driver while continuing to support TGSI for graphics. Anyways, the cool thing is that once the code can go from LLVM IR to hardware instructions all kinds of interesting things can be built on top.

              Comment


              • #8
                I don't get all this hype about OpenCL. I'm sure that there are some specialized niche applications making use of OpenCL but as a consumer I'd rather see AMD devoting some manpower to finally get video decoding working on the open drivers.

                Comment


                • #9
                  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

                  Comment


                  • #10
                    If I remember correctly, clover already generates LLVM IR which it then usually compiles down to x86/x86_64. Hopefully it won't be too difficult to get clover to use the r600g LLVM back-end to compile the CL kernels for execution on a graphics card. Then the kernels just have to be copied to video memory and scheduled (yes, I'm simplifying a bit).

                    Comment


                    • #11
                      As I see in the git branch, thare is shitload of code ~85k locs, devoted to AMDIL. I believe this is the real AMD IL used in the proprietary driver, since I can't believe even Tom can't write so much code for 2 months. This is just fantastic, and really shows how much AMD are devoted to FOSS. This makes me proud owner of AMD's platform. Thanks Tom.

                      Comment


                      • #12
                        you will not (1) export, re-export or release to a national of a country in
                        Country Groups D:1, E:1 or E:2 any restricted technology, software, or source
                        code you receive hereunder.
                        -1000 for the license. This code is not open source.

                        Open source doesn't just mean access to the source code. The distribution terms of open-source software must comply with the following criteria:

                        1. Free Redistribution

                        The license shall not restrict any party from selling or giving away the software as a component of an aggregate software distribution containing programs from several different sources.

                        http://www.opensource.org/osd.html

                        Comment


                        • #13
                          Originally posted by AnonymousCoward View Post
                          -1000 for the license. This code is not open source.
                          i think this is just against the law "Country Group A - Bureau of Industry and Security (BIS)": http://www.google.de/url?sa=t&rct=j&...N1v5pA&cad=rja

                          a License can only be in the law not out of the law. http://www.bis.doc.gov/encryption/lechart1_sec508.htm

                          but this doesn't matter evil countries can easily transfer this code to russia,china,iran and so one.
                          Last edited by Qaridarium; 12-10-2011, 01:24 AM.

                          Comment


                          • #14
                            Exciting..One step closer to being able run FAH on the gpu under linux..
                            Those who would give up Essential Liberty to purchase a little Temporary Safety,deserve neither Liberty nor Safety.
                            Ben Franklin 1755

                            Comment


                            • #15
                              Originally posted by AnonymousCoward View Post
                              -1000 for the license. This code is not open source.
                              I'll check that with our legal folks. The license doesn't seem to conflict with the portion of the definition you quoted, but there's a section further down the definition text which says that reminding licensees about the need to comply with export control law is OK but adding restrictions directly is not.

                              The license text on the AMDIL bits appears to reference the current US export laws and qualifies the restriction based on the type of content (ie basically saying "if the US export control laws restrict it then you can't export...", not sure whether that qualifies or not since the restriction only applies to "restricted" content and the definition of restricted presumably comes from the current BIS regs.

                              any restricted technology, software, or source code you receive hereunder
                              Last edited by bridgman; 12-10-2011, 10:01 PM.

                              Comment

                              Working...
                              X