Page 1 of 3 123 LastLast
Results 1 to 10 of 26

Thread: A Mesa Branch Provides GLSL IR To TGSI Translator

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

    Default A Mesa Branch Provides GLSL IR To TGSI Translator

    Phoronix: A Mesa Branch Provides GLSL IR To TGSI Translator

    What's been talked about extensively and for quite a while but not acted upon too much is ridding Mesa of Mesa IR, it's intermediate representation used internally by core Mesa and its drivers. It was also talked about as a possible summer project of replacing Mesa IR with GLSL IR. Now though an individual has begun gutting out Mesa IR and providing a direct GL Shading Language IR to TGSI (the Gallium3D IR) translator...

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

  2. #2
    Join Date
    Sep 2010
    Posts
    146

    Default GLSL IR To TGSI Translator

    I figured this would become a Phoronix article. Anyway, I'm the author of the GLSL IR to TGSI translator that this article is about.

    Not sure why Michael didn't mention my name a single time in the entire article, though.

  3. #3
    Join Date
    Feb 2009
    Location
    France
    Posts
    289

    Default

    Quote Originally Posted by Plombo View Post
    I figured this would become a Phoronix article. Anyway, I'm the author of the GLSL IR to TGSI translator that this article is about.

    Not sure why Michael didn't mention my name a single time in the entire article, though.
    He didn't want to associate you with nouveau and/or the video-pipe branch

    Anyway, keep up the good work!

  4. #4
    Join Date
    Nov 2009
    Location
    Italy
    Posts
    911

    Default

    Quote Originally Posted by MPF View Post
    Anyway, keep up the good work!
    Yeah, keep up the good work

  5. #5
    Join Date
    Sep 2008
    Posts
    989

    Default

    Quote Originally Posted by Plombo View Post
    I figured this would become a Phoronix article. Anyway, I'm the author of the GLSL IR to TGSI translator that this article is about.

    Not sure why Michael didn't mention my name a single time in the entire article, though.
    Best of luck in this effort! Once you have something that's somewhat testable, let Michael know so he can put out an article about it. I don't know if you will need to write driver-specific code for this work (for r600g, r300g, i965g, svga, nouveau, etc) -- but if not, I will be able to help test on r600g/evergreen and i965g and svga. And if you do need driver-specific code, be sure to ask the individual driver maintainers to take a look and see if they can help with that.

  6. #6
    Join Date
    Sep 2010
    Posts
    146

    Default

    Quote Originally Posted by allquixotic View Post
    Best of luck in this effort! Once you have something that's somewhat testable, let Michael know so he can put out an article about it. I don't know if you will need to write driver-specific code for this work (for r600g, r300g, i965g, svga, nouveau, etc) -- but if not, I will be able to help test on r600g/evergreen and i965g and svga. And if you do need driver-specific code, be sure to ask the individual driver maintainers to take a look and see if they can help with that.
    It's quite testable already, actually. It's working on nv50 for me with no noticeable regressions.

    Some testing using r600g would be really nice, since all of my development and testing is done using nv50.

  7. #7
    Join Date
    Apr 2009
    Posts
    35

    Default

    i'll test it with my rv620 chipset (r600g) .

    Thanks for your works !

  8. #8

    Default

    Hi, this is great news!

    But what are the main differences between the Plombo and the LunarGLASS versions?

  9. #9
    Join Date
    Oct 2007
    Location
    Toronto-ish
    Posts
    7,404

    Default

    Quote Originally Posted by oibaf View Post
    But what are the main differences between the Plombo and the LunarGLASS versions?
    Think of a line between the common code in Mesa and the HW-specific driver code.

    Plombo's work is "above the line", shortening the path used to generate TGSI from GLSL by going from GLSL IR directly to TGSI rather than the current GLSL IR => Mesa IR => TGSI path.

    Most of the LunarGlass work so far has been "below the line", implementing a more flexible mechanism for converting and optimizing a HW-independent IR (such as TGSI) into HW-specific instructions.

  10. #10
    Join Date
    Sep 2010
    Posts
    146

    Default

    I've just pushed to my branch again. Before, the translator still generated Mesa IR that wasn't ultimately used, but still depended on some information from it. Now, that information has been moved elsewhere in the translator, so I was able to remove the generation of Mesa IR instructions completely.

Posting Permissions

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