Visit the main page
Building with Link Time Optimization and Profile Guided Optimization
This page provides instruction for building the TSV Utilities from source code using Link Time Optimization (LTO) and Profile Guided Optimization (PGO). LTO is enabled for all the tools, PGO is enabled for a select few. Both improve run-time performance, LTO has the additional effect of reducing binary sizes. Normally PGO and LTO can be used independently, however, the TSV Utilities build system only supports PGO when already using LTO.
- About Link Time Optimization
- About Profile Guided Optimization
- Building the TSV Utilities with LTO and PGO
- Additional options
- LDC command lines
Just want the build command lines? Skip down to Building the TSV Utilities with LTO and PGO.
About Link Time Optimization (LTO)
Link Time Optimization is an approach to whole program optimization that performs additional optimizations during link-time that are impossible to do at compile time when only a part of the program is available. LDC, the LLVM-based D compiler, supports Link Time Optimization via LLVM's LTO.
When LTO is used, the compiler saves its intermediate representation code in
.o files rather than machine code. In LLVM's case, LLVM bitcode. At link time the linker calls back into LLVM plugin modules that optimize code generation across the entire program. This enables optimizations that cross function and module boundaries (effectively, it's as if your whole program, including external libraries, were all in the same
.d file). Cross-module inlining is an example of an optimization that can often be done quite effectively via LTO.
This is a powerful technique, but involves more complex cooperation between compiler and linker than the traditional compile-link cycle. It is only recently that LTO has started to become widely supported by software development toolchains.
The LDC team introduced initial LTO support in LDC 1.1.0. LTO became available out-of-the-box on both Linux and macOS in LDC 1.5.0. Windows support was added in LDC 1.12.0.
A valuable enhancement introduced in LDC 1.5.0 is support for compiling the D runtime library and standard library (Phobos) with LTO. This enables interprocedural optimizations spanning both D libraries and application code. For the TSV Utilities this produces materially faster executables.
LTO compiled versions of druntime and phobos are shipped with the LDC compiler. This started with LDC 1.9.0. Prior to that a tool called
ldc-build-runtime was used. This tool was shipped with LDC starting with LDC 1.5.0. The TSV Utilities build system supports both methods.
There are two different forms of LTO available: Full and Thin. To build the TSV Utilities with LTO is sufficient to know that they exist. For information on the differences see the LLVM blog post ThinLTO: Scalable and Incremental LTO.
About Profile Guided Optimization (PGO)
Profile Guided Optimization (PGO) is an approach to optimization based on recording typical execution patterns. Execution behavior data enables better choices for branch prediction, inlining decisions, and other optimizations.
There are several ways to gather execution behavior statistics, the approach used by the TSV Utilities is to generate an instrumented build and run it on common inputs. The result of these runs is recorded and passed to the compiler and linker to generate the final executable.
The TSV Utilities build system supports PGO for a couple tools, those showing the most benefit. Currently, PGO is enabled only when also using LTO. The source repository contains everything needed to generate profile data for the build, including data files and scripts invoking the instrumented builds.
For a more detailed introduction to PGO see Profile-Guided Optimization with LDC on Johan Engelen's blog.
Building the TSV Utilities with LTO and PGO
The prebuilt binaries available from the releases page are compiled with LTO and PGO for both D libraries and the TSV Utilities code. This is not enabled by default when building from source code. The reason is simple: LTO is still an early stage technology. Testing on a wider variety of platforms is needed before making it the default.
However, LTO and PGO builds can be enabled by setting makefile parameters. Testing with the built-in test suite should provide confidence in the resulting applications. The TSV Utilities makefile takes care of invoking both
ldc2 with the necessary parameters.
- LDC 1.5.0 or later. See the LDC project README for installation instructions.
- TSV Utilities source code, 1.15.0-beta3 or later (1.16.0 for PGO).
- Linux or macOS. macOS requires Xcode 9.0.1 or later.
Linux builds have been tested on Ubuntu 14.04 and 16.04.
Retrieve the TSV Utilities source code:
Via git clone:
$ git clone https://github.com/eBay/tsv-utils.git $ cd tsv-utils
Via DUB (replace
1.3.2 with the version retrieved):
$ dub fetch tsv-utils --cache=local $ cd tsv-utils-1.3.2
Via the source from the GitHub releases page (replace
1.3.2 with the latest version):
$ curl -L https://github.com/eBay/tsv-utils/archive/v1.3.2.tar.gz | tar xz $ cd tsv-utils-1.3.2/tsv-utils
Build with LTO enabled:
The command lines below use the LTO compiled druntime and phobos libraries shipped with LDC. This requires LDC 1.9.0 or later and tsv-utils 1.3.1 or later. For tsv-utils 1.2.3 and earlier replace
LDC_BUILD_RUNTIME=1. This substitution is also needed when using LDC 1.5.0 - LDC 1.8.0.
$ make DCOMPILER=ldc2 LDC_LTO_RUNTIME=1 $ make test-nobuild
The above command builds with LTO on both the D libraries and the TSV Utilities code. The build should be good if the tests succeed.
Build with LTO and PGO enabled:
To use PGO, add either
LDC_PGO=2 to the above command:
$ make DCOMPILER=ldc2 LDC_LTO_RUNTIME=1 LDC_PGO=1 $ make test-nobuild
This turns on PGO for the tools supporting it. The two values are used to help with build times.
LDC_PGO=1- Enables PGO for those tools showing the largest performance gains.
LDC_PGO=2- Enable PGO for all tools that have been configured to use it.
The PGO setup creates and runs an instrumented build to collect profiling data, this is what increases build times. Build times are still not excessive, but
LDC_PGO=1 can be a nice compromise.
The above instructions should be sufficient to create valid LTO builds. This section describes a few additional choices.
Use LTO on the TSV Utilities code only
The largest gains come from using LTO on both the D libraries and the application code. However, LTO can also be used on the application code alone. For the TSV Utilities, this is the default on macOS. On Linux it needs to be enabled explicitly.
$ make DCOMPILER=ldc2 $ make test-nobuild
$ make DCOMPILER=ldc2 LDC_LTO=full $ make test-nobuild
Statically linking the C runtime library on Linux builds
The prebuilt Linux binaries statically link the C runtime library. This increases portability at the expense of increased binary sizes. The earlier instructions dynamically link the C runtime library. To use static linking, add
DFLAGS=-static to the build lines, as follows:
$ make DCOMPILER=ldc2 LDC_LTO_RUNTIME=1 DFLAGS=-static $ make test-nobuild
This is only applicable to Linux builds, and has only been tested on Ubuntu. On Ubuntu, release 16.04 or later is required.
Choosing between Thin and Full LTO
The makefile default settings choose between Thin and Full LTO builds based on the platform. At present, Thin is used on macOS, Full is used on Linux. This is based on the author's configuration testing. At the time this was written (LDC 1.5.0, TSV Utilities 1.1.15), issues have surfaced with other choices. These issues tend to be complex, involving a combination of LDC, LLVM, and the system linkers. These are likely to be fixed in future releases, but for now the default configurations are recommended. These problems surface primarily when building both D libraries and application code using LTO (
LDC_BUILD_RUNTIME=1). Building with LTO applied to the application code alone works fine in the configurations tested. For this, use
LDC_LTO=full, without specifying the
LDC_LTO=thin|full parameter can also be combined with
LDC_BUILD_RUNTIME=1 to set the Thin/Full type when building the D libraries with LTO.
It is also possible to turn off LTO on macOS builds. For this use
LDC command lines
make commands shown above will display the LDC command lines. They are a bit lengthy though. The examples below show the command lines for building a simple
helloworld program with LTO enabled. See the LDC documentation for up-to-date details. See the LDC documentation or Profile-Guided Optimization with LDC (Johan Engelen's blog) for PGO build parameters.
LDC 1.9.0 and later
Building with LTO became materially simpler in LDC 1.9.0. From the release notes:
Prebuilt Linux and macOS packages now ship with LTO default libs (druntime & Phobos). Keep on using -flto=<thin full> to restrict LTO to your code, or opt for -flto=<thin full> -defaultlib=phobos2-ldc-lto,druntime-ldc-lto to include the default libs.
An example build command:
$ ldc2 -flto=thin -defaultlib=phobos2-ldc-lto,druntime-ldc-lto helloworld.d
This can be combined with other build flags as well. For example, a release build might use:
$ ldc2 -O -release -flto=thin -defaultlib=phobos2-ldc-lto,druntime-ldc-lto helloworld.d
LDC 1.5.0 - LDC 1.8.0
These releases did not have LTO compiled runtime libraries shipped with them.
There are two steps for building with LTO. The first is downloading and building the D library code, the second is to reference the LTO built library from the application build command.
Download and build the D library code:
$ # Build with Thin LTO $ ldc-build-runtime --reset --dFlags="-flto=thin" BUILD_SHARED_LIBS=OFF $ # Build with Full LTO $ ldc-build-runtime --reset --dFlags="-flto=full" BUILD_SHARED_LIBS=OFF
This builds in the
ldc-build-runtime.tmp directory. The
--reset option avoids downloading the source code if it's already present, and instead does only the build. This is useful when switching between Thin and Full builds.
Note that the Thin/Full choice must match the command line used to build the application.
macOS build of helloworld:
$ # Thin LTO build $ ldc2 -flto=thin -L-L./ldc-build-runtime.tmp/lib helloworld.d
Linux build of helloworld:
$ # Full LTO build $ ldc2 -flto=full -linker=gold -L-L./ldc-build-runtime.tmp/lib helloworld.d
The main difference between Linux and macOS is that an alternate (non-default) linker must be specified on Linux.
Any other typical compiler options can be specified as well. For example, a Linux release mode build might be specified as follows:
$ # Full LTO release mode build $ ldc2 -O -release -flto=full -linker=gold -L-L./ldc-build-runtime.tmp/lib helloworld.d