LLC(1)

๐Ÿ’… LLC(1) โ€” the LLVM static compiler, bestie edition โœจ

okay so welcome to llc, aka the LLVM static compiler, living in section 1 of the manual (LLC(1)), brought to you by the LLVM girlies. this page is literally your group chat with the compiler. let's go ๐ŸŽ€


โœจ SYNOPSIS โœจ

llc [options] [filename]

๐ŸŒธ DESCRIPTION ๐ŸŒธ

The llc command compiles LLVM source inputs into assembly language for a specified architecture. no cap, that's the whole vibe ๐Ÿ’… The assembly language output can then be passed through a native assembler and linker to generate a native executable.

The choice of architecture for the output assembly code is automatically determined from the input file, unless the -march option is used to override the default. so it just knows, iykyk ๐Ÿฆ‹


๐Ÿ‘‘ OPTIONS ๐Ÿ‘‘

If filename is "-" or omitted, llc reads from standard input. Otherwise, it will read from filename. Inputs can be in either the LLVM assembly language format (.ll) or the LLVM bitcode format (.bc). both slay, honestly ๐Ÿ’–

If the -o option is omitted, then llc will send its output to standard output if the input is from standard input. If the -o option specifies "-", then the output will also be sent to standard output. very "wherever you go, there you are" of it โœจ

If no -o option is specified and an input file other than "-" is specified, then llc creates the output filename by taking the input filename, removing any existing .bc extension, and adding a .s suffix. automatic glow-up, no notes ๐ŸŽ€

Other llc options are described below.

๐Ÿ’– End-user Options ๐Ÿ’–

  • -help โ€” Print a summary of command line options. your little map, bestie ๐Ÿ—บ๏ธ
  • -M โ€” Pass target-specific InstPrinter options. Refer to the -M option of llvm-objdump(1) <llvm-objdump.html>.
  • -o <filename> โ€” Use <filename> as the output filename. See the summary above for more details.
  • -O=uint โ€” Generate code at different optimization levels. These correspond to the -O0, -O1, -O2, and -O3 optimization levels used by clang. pick your fighter โœจ
  • -mtriple=<target triple> โ€” Override the target triple specified in the input file with the specified string.
  • -march=<arch> โ€” Specify the architecture for which to generate assembly, overriding the target encoded in the input file. See the output of llc -help for a list of valid architectures. By default this is inferred from the target triple or autodetected to the current architecture.
  • -mcpu=<cpuname> โ€” Specify a specific chip in the current architecture to generate code for. By default this is inferred from the target triple and autodetected to the current architecture. For a list of available CPUs, use:
llvm-as < /dev/null | llc -march=xyz -mcpu=help
  • -mtune=<cpuname> โ€” Specify a specific chip microarchitecture in the current architecture to tune code for. By default this is inferred from the target triple and autodetected to the current architecture. For a list of available tuning CPUs, use:
llvm-as < /dev/null | llc -march=xyz -mtune=help
  • -filetype=<output file type> โ€” Specify what kind of output llc should generated. Options are: asm for textual assembly ('.s'), obj for native object files ('.o') and null for not emitting anything (for performance testing).
ngl, not all targets support all options. check your fave's compatibility first ๐Ÿซถ
  • -mattr=a1,+a2,-a3,... โ€” Override or control specific attributes of the target, such as whether SIMD operations are enabled or not. The default set of attributes is set by the current CPU. For a list of available attributes, use:
llvm-as < /dev/null | llc -march=xyz -mattr=help
  • --frame-pointer โ€” Specify effect of frame pointer elimination optimization (all,non-leaf,none).
  • --disable-excess-fp-precision โ€” Disable optimizations that may produce excess precision for floating point. note that this option can dramatically slow down code on some systems (e.g. X86). it's giving "beauty is pain" but for your runtime ๐Ÿ˜ญ
  • --enable-no-infs-fp-math โ€” Enable optimizations that assume no Inf values.
  • --enable-no-nans-fp-math โ€” Enable optimizations that assume no NAN values.
  • --enable-no-signed-zeros-fp-math โ€” Enable FP math optimizations that assume the sign of 0 is insignificant.
  • --enable-no-trapping-fp-math โ€” Enable setting the FP exceptions build attribute not to use exceptions.
  • --stats โ€” Print statistics recorded by code-generation passes. numbers!! ๐Ÿ“Š
  • --save-stats, --save-stats=cwd, --save-stats=obj โ€” Save LLVM statistics to a file in the current directory (--save-stats/--save-stats=cwd) or the directory of the output file (--save-stats=obj) in JSON format.
  • --time-passes โ€” Record the amount of time needed for each pass and print a report to standard error. clocking every single pass, we love an accountable queen โฑ๏ธ
  • --load=<dso_path> โ€” Dynamically load dso_path (a path to a dynamically shared object) that implements an LLVM target. This will permit the target name to be used with the -march option so that code can be generated for that target.
  • -meabi=[default|gnu|4|5] โ€” Specify which EABI version should conform to. Valid EABI versions are gnu, 4 and 5. Default value (default) depends on the triple.
  • -stack-size-section โ€” Emit the .stack_sizes section which contains stack size metadata. The section contains an array of pairs of function symbol values (pointer size) and stack sizes (unsigned LEB128). The stack size values only include the space allocated in the function prologue. Functions with dynamic stack allocations are not included. no dynamic allocations allowed at this party ๐Ÿ™ˆ
  • -remarks-section โ€” Emit the __remarks (MachO) section which contains metadata about remark diagnostics.

๐Ÿฆ‹ Tuning/Configuration Options ๐Ÿฆ‹

  • --print-after-isel โ€” Print generated machine code after instruction selection (useful for debugging). peek behind the curtain, bestie ๐Ÿ’œ
  • --regalloc=<allocator> โ€” Specify the register allocator to use. Valid register allocators are:
    • basic โ€” Basic register allocator.
    • fast โ€” Fast register allocator. It is the default for unoptimized code.
    • greedy โ€” Greedy register allocator. It is the default for optimized code.
    • pbqp โ€” Register allocator based on 'Partitioned Boolean Quadratic Programming'.
  • --spiller=<spiller> โ€” Specify the spiller to use for register allocators that support it. Currently this option is used only by the linear scan register allocator. The default spiller is local. Valid spillers are:
    • simple โ€” Simple spiller
    • local โ€” Local spiller

โญ Intel IA-32-specific Options โญ

  • --x86-asm-syntax=[att|intel] โ€” Specify whether to emit assembly code in AT&T syntax (the default) or Intel syntax. choose your aesthetic ๐ŸŽ€

๐Ÿ’€ EXIT STATUS ๐Ÿ’€

If llc succeeds, it will exit with 0. Otherwise, if an error occurs, it will exit with a non-zero value. zero is the slay number, anything else is a vibe check fail โœจ


๐ŸŒˆ SEE ALSO ๐ŸŒˆ

lli(1) <lli.html>


๐Ÿซถ Author ๐Ÿซถ

Maintained by the LLVM Team (https://llvm.org/). protect them at all costs ๐Ÿ‘‘

2003-2026, LLVM Project


okay that's the whole page, mwah ๐Ÿ’‹ this was LLC(1) โ€” LLVM manual page 23, dated 2026-10-20 โ€” and the LLVM girlies ate, periodt. go compile something iconic โœจ๐Ÿ”ฅ

๐Ÿ“ฆ where this page comes from
  • arch rolling: llvm 23.1.4-1 ยท Apache-2.0 WITH LLVM-exception
  • ๐Ÿ’– girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms