[llvm-dev] ThinLTO status in trunk?

Adve, Vikram Sadanand via llvm-dev llvm-dev at lists.llvm.org
Fri Jul 22 14:19:55 PDT 2016

On Jul 22, 2016, at 2:36 PM, Teresa Johnson <tejohnson at google.com<mailto:tejohnson at google.com>> wrote:

Hi Vikram,


I'm not sure what part got committed in the 3.8 timeframe - it looks like that was released back in March? A number of fixes have gone in since then so I would stick with a more recent version. The ThinLTO in trunk and (presumably 3.9 which seems to have not yet gone out?) is complete and working with multiple threads using gold.

Sounds good.  I will give this a spin.

The distributed build support is also in (which needs support in the build system however), although I am fixing a few bugs right now that popped up in testing our internal apps.

OK it will be a little while before I get to try that.  And the build system for the set of applications I’m working with is quite painful, so I don’t know how long that will take, sigh.

Which distributed build system do you use? We have support coming out in Bazel, which is our open sourced distributed build system.

I don’t know yet — I’ll find out when I get to that stage.  But it’s almost certainly something very simple or home-brewed.

Let me know if you run into any issues or have any other questions!




// Vikram S. Adve
// Professor, Department of Computer Science
// University of Illinois at Urbana-Champaign
// vadve at illinois.edu<mailto:vadve at illinois.edu>
// http://llvm.org

On Fri, Jul 22, 2016 at 12:15 PM, Adve, Vikram Sadanand via llvm-dev <llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>> wrote:
First, kudos on the ThinLTO results reported in your blog post — they’re impressive and the system sounds really well engineered.

I’m starting to try it out on a large piece of software and I’d like to make sure I know what to expect.  The blog said it will be available in clang-3.9 but both clang-3.8 and trunk seem to have some degree of support for it.  What is the status of ThinLTO in 3.8 (preferably) or trunk (otherwise)?  Are either of these usable with multiple threads?  What about for a distributed build?



// Vikram S. Adve
// Professor, Department of Computer Science
// University of Illinois at Urbana-Champaign
// vadve at illinois.edu<mailto:vadve at illinois.edu>
// http://llvm.org<https://urldefense.proofpoint.com/v2/url?u=http-3A__llvm.org&d=CwMFaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=b7uK7dJM4Fx7J_ehsuohEdD-6NdkoLyTwBFfHX-XKcc&m=px4LMbEtuCuyquW6qSGKnKyFZb4fKwVt3Wz8PbAyOLg&s=4cBsKK5PujU5xK3e6qJKaS_SAErck-yyileHZDHs-Gg&e=>

LLVM Developers mailing list
llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>

Teresa Johnson |         Software Engineer |     tejohnson at google.com<mailto:tejohnson at google.com> |     408-460-2413

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160722/26400b48/attachment.html>

More information about the llvm-dev mailing list