maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
378,448 Commits 23 Branches 0 Tags 2.2 GiB
Commit Graph

6 Commits

Author SHA1 Message Date
Nico Weber b570f82f43 docs: Add pointer to cmake caches for PGO 
Also add a link to end-user PGO documentation.

Differential Revision: https://reviews.llvm.org/D92768
 2020-12-07 15:55:26 -05:00
Kristof Beyls 424fdbc3de collect_and_build_with_pgo.py: adapt to monorepo 
Differential Revision: https://reviews.llvm.org/D92328
 2020-12-01 09:16:12 +01:00
Fangrui Song ab7a3ad4b3 [utils] collect_and_build_with_pgo.py: revert part already fixed in rL345461 
The change was inadvertently included in my last commit.

llvm-svn: 345467
 2018-10-27 23:10:09 +00:00
Fangrui Song 442e17ca5a [utils] Fix _run_benchmark in collect_and_build_with_pgo.py 
Summary: Also fix a FIXME in _build_stage1_clang: clang llvm-profdata profile are sufficient

Reviewers: george.burgess.iv

Subscribers: llvm-commits

Differential Revision: https://reviews.llvm.org/D53795

llvm-svn: 345466
 2018-10-27 22:56:04 +00:00
George Burgess IV e61b0d772c [utils] Run tests in the proper directory. 
The intent here was to run check-llvm/check-clang in the instrumented
clang's build directory, not the maybe-not-yet-created uninstrumented
clang's. Oops. :)

llvm-svn: 345461
 2018-10-27 20:02:06 +00:00
George Burgess IV cf477f4e41 Add docs+a script for building clang/LLVM with PGO 
Depending on who you ask, PGO grants a 15%-25% improvement in build
times when using clang. Sadly, hooking everything up properly to
generate a profile and apply it to clang isn't always straightforward.
This script (and the accompanying docs) aim to make this process easier;
ideally, a single invocation of the given script.

In terms of testing, I've got a cronjob on my Debian box that's meant to
run this a few times per week, and I tried manually running it on a puny
Gentoo box I have (four whole Atom cores!). Nothing obviously broke.
¯\_(ツ)_/¯

I don't know if we have a Python style guide, so I just shoved this
through yapf with all the defaults on.

Finally, though the focus is clang at the moment, the hope is that this
is easily applicable to other LLVM-y tools with minimal effort (e.g.
lld, opt, ...). Hence, this lives in llvm/utils and tries to be somewhat
ambiguous about naming.

Differential Revision: https://reviews.llvm.org/D53598

llvm-svn: 345427
 2018-10-26 20:56:03 +00:00