Discofork
Repository brief

llvm/llvm-project

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis
cached 2026-03-30T15:32:53.443Z
1mo ago

llvm/llvm-project

llvm/llvm-project is the upstream LLVM monorepo: a large, active compiler and toolchain codebase with many reusable components, including LLVM core, Clang, LLD, LLDB, libc++, compiler-rt, MLIR, OpenMP, Flang, and more. It is highly active and widely forked, so forks are likely to be interesting if you care about compilers, language tooling, runtimes, or low-level infrastructure.

GitHub
Loading tags...
Stars37,650
Forks16,714
Default branchmain
Last pushed2026-03-30T15:12:45Z
Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs
Selected

Choose this fork if Fil-C’s memory-safety goal is the priority. Avoid it if you need close upstream LLVM compatibility, low-maintenance rebasing, or the latest LLVM changes with minimal fork-specific behavior.

Choose this fork if your work depends on Swift-specific LLVM/Clang/LLDB behavior or on the release process around Swift. Choose upstream if you want the broadest, least-opinionated LLVM base and the fastest access to mainline changes.

Choose this fork if you need Espressif-specific LLVM support and are prepared to live with a heavily diverged downstream branch. If you mainly want current upstream LLVM, this fork is too specialized and too far from main to be the safer default.

Choose this fork if your priority is AMD/ROCm support and you want an LLVM tree already carrying AMD-specific compiler, header, and offload work. Prefer upstream LLVM if you want the broadest compatibility and the lowest maintenance burden for non-AMD use cases.

Choose this fork if your priority is P2996 reflection experimentation in Clang. Choose upstream LLVM if you need the widest, most current compiler-toolchain surface with lower merge and maintenance risk.

Choose this fork if your goal is Z80/eZ80 LLVM support. Choose upstream LLVM if you want the latest mainstream compiler, linker, and runtime work with minimal maintenance burden.

Choose this fork if you need LLVM in a Rust-centered workflow and are prepared to manage substantial upstream drift. Choose upstream llvm/llvm-project if you want the broadest, freshest, least-surprising LLVM base.

Choose this fork if your priority is LLVM-integrated obfuscation and anti-analysis functionality. Avoid it if you mainly want upstream LLVM stability, latest fixes, and minimal maintenance overhead, because this fork is substantially specialized and already behind upstream.

Prefer this fork only if you need its MSVC-focused downstream direction and can own the maintenance cost. If you want current LLVM behavior, security fixes, and active upstream compatibility, upstream is the safer choice.

Choose this fork if you need reverse-engineering-specific LLVM extensions and can tolerate substantial upstream divergence. Choose upstream LLVM instead if you need maximum compatibility, fresh upstream fixes, and a lower-maintenance toolchain.