LLVM-PROFGEN(1)

📦
version 23.1.4 · 9 versions
, in arch rolling

👑 LLVM-PROFGEN(1) — the llvm-profgen page, bestie edition

okay so you're reading the llvm-profgen manual page (section 1, the "user commands" girlies 💅) and honestly? you came to the right place. let's get into it. 🎀

✨ NAME ✨

llvm-profgen — the LLVM SPGO profile generation tool. that's it. that's the name. she generates. 💖

🦋 SYNOPSIS 🦋

llvm-profgen [commands] [options]

🌸 DESCRIPTION 🌸

so basically the llvm-profgen utility generates a profile data file from given perf script data files, for sample-based profile guided optimization (SPGO). iconic behaviour, no notes. 🔥

🌈 COMMANDS 🌈

you need at least one of these bad boys (well — one of the trace-y ones, see the note below, don't come for me):

  • --perfscript=<string[,string,...]> — path of the perf-script trace, created by the Linux perf tool with the script command (and psst: the raw perf.data should be profiled with -b). 🍓
  • --etm=<string> — path of the ETM trace file created by the ARM CoreSight trace tools. heads up: this one needs the OpenCSD library version 1.5.4 or higher enabled during the build. no OpenCSD, no ETM, iykyk. 🧚
  • --perfdata=<perfdata>, --pd — path of the raw perf data created by the Linux perf tool (it should be profiled with -b). she's the raw one. 💜
  • --unsymbolized-profile=<unsymbolized profile>, --up — path of the unsymbolized profile created by llvm-profgen with --skip-symbolization. yes she can read her own output, self-sufficient queen. ✨
  • --llvm-sample-profile=<llvm sample profile> — path of the LLVM sample profile. straightforward. slay. 🌸
note: only one of --perfscript, --perfdata, --unsymbolized-profile, --llvm-sample-profile, or --etm may be specified at a time. one. singular. pick your fighter and commit. 💀
  • --binary=<string[,string,...]> — path of the input profiled binary files. 🫶
  • --output=<string> — path of the output profile file. the whole point, honestly. 👑

💅 OPTIONS 💅

llvm-profgen supports the following options — buckle up bestie, there's a whole list:

  • --format=[text|binary|extbinary|compbinary|gcc] — specify the format of the generated profile. the supported <format> values are text, binary, extbinary, compbinary, gcc — and if you want the full lore on what each of those means, see llvm-profdata, she explains it better. 📚
  • --show-mmap-events — print mmap events. that's literally it. 🗺️
  • --show-disassembly — print disassembled code. assembly girlies rise. 🔍
  • --x86-asm-syntax=[att|intel] — specify whether to print assembly code in AT&T syntax (which is the default, fyi 🌟) or Intel syntax. choose your vibe.
  • --debug-binary=<debug-binary> — path of the debug info binary. llvm-profgen will load the DWARF info from it instead of the executable binary. so she's reading the debug twin, not the main character. 🦋
  • --target-triple=<triple> — override the target triple for the binary. this is useful for ETM trace decoding, to specify the correct Arm M-profile target. very "let me be clear about who i am" energy. 🎯
  • --pid — Process Id for the profiled executable binary. 🆔
  • --output=<output> — path of the output profile file. yes she shows up twice (once up in commands, once here) and honestly? she's allowed. consistency queen. 👑💖
  • --data-access-perftrace=<data-access-perftrace> — file path of a Linux perf raw trace (generated by perf report -D) consisting of memory access events. 🍓

🌟 Author 🌟

maintained by the LLVM Team (https://llvm.org/). literal legends, we stan. 🫶

2003-2026, LLVM Project. periodt. 💜

and that's the whole page, bestie — this was the LLVM manual, version 23, dated 2026-10-20, page LLVM-PROFGEN(1), brought to you with love and way too many emoji. mwah. 💋✨🌸

📦 where this page comes from