LLUBI(1)

πŸ“¦ version 23.1.3, in centos-stream 9

πŸ’… LLUBI(1) β€” LLVM UB-aware Interpreter ✨

🌸 NAME 🌸

llubi β€” LLVM UB-aware Interpreter. That's the name, bestie, and it's iconic. 🫢

✨ SYNOPSIS ✨

llubi [options] [filename] [program args]

πŸ¦‹ DESCRIPTION πŸ¦‹

Okay so llubi directly executes programs in LLVM bitcode format and tracks values in LLVM IR semantics. Unlike lli, llubi is designed to be aware of undefined behaviors during execution. It detects immediate undefined behaviors such as integer division by zero, and respects poison generating flags like nsw and nuw. As it captures most of the guardable undefined behaviors, it is highly suitable for constructing an interesting-ness test for miscompilation bugs. No cap, that's the whole point. πŸ’…

If filename is not specified, then llubi reads the LLVM bitcode for the program from standard input.

The optional args specified on the command line are passed to the program as arguments.

πŸŽ€ GENERAL OPTIONS πŸŽ€

  • -fake-argv0=executable β€” Override the argv[0] value passed into the executing program. Yes bestie, you can fake the name it thinks it has. πŸͺͺ
  • -entry-function=function β€” Specify the name of the function to execute as the program's entry point. By default, llubi uses the function named main.
  • -help β€” Print a summary of command line options. Your little cheat sheet. ✨
  • -verbose β€” Print results for each instruction executed. It's giving main character energy for every single instruction. πŸ‘‘
  • -version β€” Print out the version of llubi and exit without doing anything else. Short and iconic.

🌈 INTERPRETER OPTIONS 🌈

  • -max-mem=N β€” Limit the amount of memory (in bytes) that can be allocated by the program, including stack, heap, and global variables. If the limit is exceeded, execution will be terminated. By default, there is no limit (N = 0). Memory cap? Not today, bestie. πŸ’€
  • -max-stack-depth=N β€” Limit the maximum stack depth to N. If the limit is exceeded, execution will be terminated. The default limit is 256. Set N to 0 to disable the limit. Deep recursion? The limit said not today. 🫢
  • -max-steps=N β€” Limit the number of instructions executed to N. If the limit is reached, execution will be terminated. By default, there is no limit (N = 0). Step budget: unlimited by default, periodt. πŸ’…
  • -vscale=N β€” Set the value of llvm.vscale to N. The default value is 4.
  • -seed=N β€” Set the seed for random number generator to N. By default, the seed is 0.
  • -undef-behavior=mode β€” Set the behavior for undefined values (e.g., load from uninitialized memory or freeze a poison value). The options for mode are:
    • nondet: Each load from the same uninitialized byte yields a freshly random value. This is the default behavior.
    • zero: Uninitialized values are treated as zero.
  • -nan-behavior=mode β€” Set the behavior for payload preserving behavior of floating-point NaN values. The options for mode are:
    • nondet: The actual behavior is randomly chosen from the modes below. This is the default behavior.
    • preferred: The quiet bit is set and the payload is all-zero.
    • quieting: The quiet bit is set and the payload is copied from any input operand that is a NaN.
    • unchanged: The quiet bit and payload are copied from any input operand that is a NaN.
    • target-specific: The quiet bit is set and the payload is picked from a known target-specific set of extra possible NaN payloads.
  • -deterministic β€” Disable interpreter-introduced non-determinism (off by default). This option implies -undef-behavior=zero and -nan-behavior=preferred. Chaos off, predictability on. πŸŽ€
  • -fuse-fmuladd β€” Treat llvm.fmuladd.* as llvm.fma.*. It is the default behavior. Otherwise, it is expanded into a * b + c. Math but make it fused. πŸ”₯
  • -disable-verify β€” Disable the validation of the input LLVM IR. The user is responsible for the validity of inputs. The verifier is executed by default.
🚨 Careful bestie: with -disable-verify, you are responsible for the validity of inputs. The verifier is executed by default.

πŸ’€ EXIT STATUS πŸ’€

If llubi fails to load the program, or an error occurs during execution (e.g., an immediate undefined behavior is triggered), it will exit with an exit code of 1. If the return type of entry function is not an integer type, it will return 0. Otherwise, it will return the exit code of the program. That's the vibe check at the door. πŸšͺ

πŸ‘‘ AUTHOR πŸ‘‘

Maintained by the LLVM Team (https://llvm.org/). Yes, the whole team. Iconic. πŸ’œ

2003-2026, LLVM Project β€” there it is, bestie, the copyright line, untouched and slaying. 🌸


πŸ’– That's a wrap on LLUBI(1) β€” sourced from LLVM version 23, dated 2026-10-06. No cap, that's the cute little footer energy. Periodt. πŸ’…

πŸ“¦ where this page comes from