Install wllvm with Homebrew, Nix

Project links

• Homepage
• Repository
• Upstream docs
• Package manager page

Commands and aliases

• extract-bc
• wfortran
• wllvm
• wllvm++
• wllvm-as
• wllvm-sanity-checker
• wparse-args

Project history

The public GitHub repository for travitch/whole-program-llvm was created in 2011, and the package later became available on PyPI, whose JSON metadata records release 1.0.0 in August 2016 and release 1.3.1 in April 2021. The README describes the design as a two-step compiler-wrapper approach: build real object files first, generate matching LLVM bitcode second, and record bitcode paths in a dedicated object-file section so a post-build tool can link them into a whole-program bitcode file.

WLLVM's design grew around a practical limitation of link-time optimization workflows: GCC LTO and gold-plugin approaches can work for some programs but become awkward around static libraries and build systems that expect native objects during the build. By keeping the native build intact and delaying bitcode collection until after linking, WLLVM became useful for analysis workflows that need LLVM IR without forcing upstream projects to adopt LLVM-specific build logic.

Adoption history

Adoption has remained specialized but durable in the LLVM static-analysis ecosystem. The PyPI classifiers identify developers and science/research users, while the repository has accumulated hundreds of public stars and forks. The existence of SRI-CSL's gllvm, documented as a Go port of wllvm, is a useful sign of the idea's persistence: the wrapper-plus-extract pattern was important enough to be reimplemented for users who wanted a compiled toolchain wrapper.

How it is used

A typical user exports WLLVM's compiler wrappers, builds an unmodified upstream package, then runs extract-bc on the resulting executable or archive to recover a linked LLVM bitcode module. That makes it a package-nerd tool for turning traditional Unix source packages into LLVM IR inputs for static analysis, symbolic execution, decompilation research, and whole-program optimization experiments.

Why package nerds care

WLLVM matters because it sits at the border between normal distribution builds and research tooling. It lets a package be built the way its maintainers intended while still producing LLVM bitcode artifacts that package managers and analysis frameworks can consume later.

Timeline

• 2011: travitch/whole-program-llvm public repository created on GitHub.
• 2016: wllvm 1.0.0 uploaded to PyPI.
• 2021: wllvm 1.3.1 uploaded to PyPI.
• 2020s: gllvm documents itself as a Go port of wllvm, preserving the same whole-program bitcode workflow.

Related projects

• gllvm is a Go port of WLLVM with analogous wrapper commands and a get-bc extraction workflow.
• LLVM, clang, llvm-link, and llvm-ar are the underlying compiler and bitcode tools that make WLLVM's output useful.

Sources

• https://api.github.com/repos/travitch/whole-program-llvm
• https://github.com/SRI-CSL/gllvm
• https://github.com/klee/legacy-wllvm
• https://github.com/travitch/whole-program-llvm
• https://pypi.org/project/wllvm/
• https://pypi.org/pypi/wllvm/json