Results 1 to 10 of 10

Thread: Radeon R600 Back-End Merged Into LLVM

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

    Default Radeon R600 Back-End Merged Into LLVM

    Phoronix: Radeon R600 Back-End Merged Into LLVM

    After being in development for the past year, AMD's Radeon R600 LLVM back-end has been merged into the upstream LLVM code-base...

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

  2. #2
    Join Date
    Oct 2012
    Location
    Washington State
    Posts
    527

    Default

    ``It took a while of pushing?''

    It took months of Tom getting phenomenal free advice on architecture and development which provided a dramatically improved code base that now meets all the criteria required to get this back-end into LLVM proper. That's what it took.

    Kudos to Tom and all his hard work and kudos to all the main players in LLVM/Clang who took the time to help out and we all get a better code base.

  3. #3
    Join Date
    Jul 2011
    Location
    Paris/France
    Posts
    40

    Default So.... will it be in llvm 3.2 ?

    On one hand, LLVM 3.2 will be released soon and current(git) mesa requires it.
    On the other hand, i suppose LLVM 3.2 is already feature-frozen.

    So I think the question is quite legitimate and the information would belong to a complete news/article!

  4. #4
    Join Date
    Dec 2007
    Posts
    2,404

    Default

    Quote Originally Posted by orzel View Post
    On one hand, LLVM 3.2 will be released soon and current(git) mesa requires it.
    On the other hand, i suppose LLVM 3.2 is already feature-frozen.

    So I think the question is quite legitimate and the information would belong to a complete news/article!
    It will be in 3.3.

  5. #5
    Join Date
    Oct 2008
    Posts
    3,248

    Default

    Quote Originally Posted by Marc Driftmeyer View Post
    ``It took a while of pushing?''

    It took months of Tom getting phenomenal free advice on architecture and development which provided a dramatically improved code base that now meets all the criteria required to get this back-end into LLVM proper. That's what it took.

    Kudos to Tom and all his hard work and kudos to all the main players in LLVM/Clang who took the time to help out and we all get a better code base.
    Heh, it also took weeks where he asked for anyone to do a final review of the code so it could get merged, and no one stepping up. But it's in now, so all is good.

  6. #6
    Join Date
    Nov 2008
    Location
    Madison, WI, USA
    Posts
    884

    Default

    Follow-up question: Does this mean that the R600 LLVM-backend instance that's living in the Mesa tree will be removed in the near-ish future? I'd hate to see them diverge too much.

  7. #7
    Join Date
    Jan 2009
    Posts
    1,769

    Default

    Will nouveau have to write their own llvm backend in order to get OpenCl support also??


    Props to Tom.

  8. #8
    Join Date
    Dec 2007
    Posts
    2,404

    Default

    Quote Originally Posted by Veerappan View Post
    Follow-up question: Does this mean that the R600 LLVM-backend instance that's living in the Mesa tree will be removed in the near-ish future? I'd hate to see them diverge too much.
    I believe the current plan is to maintain a separate LLVM 3.2 tree with the R600 backend for the next mesa release (taking care to port fixes to both LLVM trees), then switch to upstream LLVM once the R600 backend is available in a stable LLVM release.

  9. #9
    Join Date
    Dec 2007
    Posts
    2,404

    Default

    Quote Originally Posted by 89c51 View Post
    Will nouveau have to write their own llvm backend in order to get OpenCl support also??


    Props to Tom.
    I think they currently convert LLVM into TGSI and then use their existing shader compiler.

  10. #10
    Join Date
    Dec 2012
    Posts
    6

    Default

    Keep up the good work
    Last edited by Robert932; 12-16-2012 at 05:26 AM.

Posting Permissions

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