bcm5719-llvm - Project Ortega BCM5719 LLVM

	Commit message (Collapse)	Author	Age	Files	Lines
*	[utils] collect_and_build_with_pgo.py: revert part already fixed in rL345461	Fangrui Song	2018-10-27	1	-8/+8
\| \| \| \| \| \|	The change was inadvertently included in my last commit. llvm-svn: 345467
*	[utils] Fix _run_benchmark in collect_and_build_with_pgo.py	Fangrui Song	2018-10-27	1	-15/+8
\| \| \| \| \| \| \| \| \| \| \| \|	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
*	[utils] Run tests in the proper directory.	George Burgess IV	2018-10-27	1	-1/+1
\| \| \| \| \| \| \| \|	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
*	Add docs+a script for building clang/LLVM with PGO	George Burgess IV	2018-10-26	1	-0/+487
	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