LLI(1)

๐Ÿ’… lli โ€” the LLVM one, bestie

ok so this is the LLI(1) page from the LLVM manual, and I'm gonna walk you through it like we're on FaceTime at 1am. it's giving "run your bitcode directly," and honestly? iconic.


โœจ NAME โœจ

lli โ€” directly execute programs from LLVM bitcode ๐Ÿซถ


๐ŸŒธ SYNOPSIS ๐ŸŒธ

lli [options] [filename] [program args]

๐Ÿฆ‹ DESCRIPTION ๐Ÿฆ‹

okay so lli directly executes programs in LLVM bitcode format. like, it takes a program in LLVM bitcode format and executes it using a just-in-time compiler or an interpreter. no middleman, no drama, we love to see it โœจ

but heads up bestie: lli is not an emulator. it will not execute IR of different architectures, and it can only interpret (or JIT-compile) for the host architecture. so don't come crying to me when your cross-arch dreams get humbled ๐Ÿ˜ญ it's a whole different vibe and lli is simply not that girl.

the JIT compiler takes the same arguments as other tools, like llc, but they don't necessarily work for the interpreter. iykyk ๐Ÿ’…

if filename is not specified, then lli reads the LLVM bitcode for the program from standard input. yes, stdin. main character energy from a pipe ๐ŸŽ€

the optional args specified on the command line are passed to the program as arguments. slay, forwarding ๐Ÿซถ


๐Ÿ’– GENERAL OPTIONS ๐Ÿ’–

  • -fake-argv0=executable โ€” override the argv[0] value passed into the executing program. identity theft but make it legal โœจ
  • -force-interpreter={false,true} โ€” if set to true, use the interpreter even if a just-in-time compiler is available for this architecture. defaults to false. ngl sometimes you just wanna keep it old school ๐Ÿงš
  • -help โ€” print a summary of command line options. the classic.
  • -stats โ€” print statistics from the code-generation passes. this is only meaningful for the just-in-time compiler, at present. just so you know ๐Ÿซถ
  • -time-passes โ€” record the amount of time needed for each code-generation pass and print it to standard error. lowkey obsessed with timekeeping โฑ๏ธ
  • -version โ€” print out the version of lli and exit without doing anything else. it said "i'm out" ๐Ÿ’€

๐ŸŒˆ TARGET OPTIONS ๐ŸŒˆ

  • *-mtriple=target triple* โ€” override the target triple specified in the input bitcode file with the specified string. this may result in a crash if you pick an architecture which is not compatible with the current system. bestie. be careful. ๐Ÿ˜ญ
  • *-march=arch* โ€” specify the architecture for which to generate assembly, overriding the target encoded in the bitcode 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. autodetect ate, fr fr.
  • *-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 ๐Ÿงš
  • *-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 ๐Ÿ‘‘

๐ŸŽ€ FLOATING POINT OPTIONS ๐ŸŽ€

  • -disable-excess-fp-precision โ€” disable optimizations that may increase floating point precision.
  • -enable-no-infs-fp-math โ€” enable optimizations that assume no Inf values. infinity? never met her ๐Ÿ™ˆ
  • -enable-no-nans-fp-math โ€” enable optimizations that assume no NAN values.
  • -soft-float โ€” causes lli to generate software floating point library calls instead of equivalent hardware instructions. crunchy but valid ๐Ÿ“

๐Ÿ”ฅ CODE GENERATION OPTIONS ๐Ÿ”ฅ

  • *-code-model=model* โ€” choose the code model from:
    • default: Target default code model
    • tiny: Tiny code model
    • small: Small code model
    • kernel: Kernel code model
    • medium: Medium code model
    • large: Large code model

pick your fighter ๐Ÿ’…

  • -disable-post-RA-scheduler โ€” disable scheduling after register allocation.
  • -disable-spill-fusing โ€” disable fusing of spill code into instructions.
  • -jit-enable-eh โ€” exception handling should be enabled in the just-in-time compiler. messy girls stay ready ๐Ÿ˜ญ
  • -join-liveintervals โ€” coalesce copies (default=true). the default is already yes, she's that confident.
  • -nozero-initialized-in-bss โ€” don't place zero-initialized symbols into the BSS section.
  • *-pre-RA-sched=scheduler* โ€” instruction schedulers available (before register allocation):
    • =default: Best scheduler for the target
    • =none: No scheduling: breadth first sequencing
    • =simple: Simple two pass scheduling: minimize critical path and maximize processor utilization
    • =simple-noitin: Simple two pass scheduling: Same as simple except using generic latency
    • =list-burr: Bottom-up register reduction list scheduling
    • =list-tdrr: Top-down register reduction list scheduling
    • =list-td: Top-down list scheduler

the way there are so many optionsโ€ฆ choose wisely bestie โœจ

  • *-regalloc=allocator* โ€” register allocator to use (default=linearscan):
    • =bigblock: Big-block register allocator
    • =linearscan: linear scan register allocator
    • =local: local register allocator
    • =simple: simple register allocator
  • *-relocation-model=model* โ€” choose relocation model from:
    • =default: Target default relocation model
    • =static: Non-relocatable code
    • =pic: Fully relocatable, position independent code
    • =dynamic-no-pic: Relocatable external references, non-relocatable code
  • -spiller โ€” spiller to use (default=local):
    • =simple: simple spiller
    • =local: local spiller

spiller? more like spill the tea โ˜•

  • *-x86-asm-syntax=syntax* โ€” choose style of code to emit from X86 backend:
    • =att: Emit AT&T-style assembly
    • =intel: Emit Intel-style assembly

โญ EXIT STATUS โญ

if lli fails to load the program, it will exit with an exit code of 1. otherwise, it will return the exit code of the program it executes. so basically it's a good little messenger and hands you back whatever your program said ๐Ÿซถ


๐Ÿ‘‘ SEE ALSO ๐Ÿ‘‘

llc(1) <llc.html> โ€” go say hi ๐Ÿ’œ


๐Ÿงš Author ๐Ÿงš

maintained by the LLVM Team (https://llvm.org/). keeping it together for us all, no cap.

2003-2026, LLVM Project


and that's the whole page, bestie ๐ŸŽ€ this was LLI(1) from the LLVM manual, version 23, dated 2026-10-20 โ€” go forth and execute your bitcode, you absolute icon ๐Ÿ’…โœจ๐Ÿฆ‹

๐Ÿ“ฆ 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