LLVM-RTDYLD(1)

πŸ“¦
version 22.1.8 Β· 3 versions
, in ubuntu stonking

πŸ’– NAME πŸ’–

llvm-rtdyld β€” okay bestie, this is the manual page for llvm-rtdyld 22, and it is the llvm MC-JIT tool. that's the whole vibe. it takes your object files, links them up in memory, and actually runs them. no cap. πŸ¦‹


✨ DESCRIPTION ✨

OVERVIEW: llvm MC-JIT tool 🌈

USAGE:

llvm-rtdyld [options] <input files> --args <program arguments>...

so like, you feed it <input files>, sprinkle your <program arguments> in after --args, and it goes to work. underneath all of that is a big pile of OPTIONS, and we are gonna go through every single one, because that's what we do here. πŸ’…


πŸŽ€ Color Options πŸŽ€

  • --color β€” use colors in output. default is autodetect, so it decides for itself whether your terminal is cute enough. πŸ‘‘

🫢 Generic Options 🫢

  • --help β€” display the available options. want the spicy hidden ones? that's --help-hidden for more. 😌
  • --help-list β€” display a list of the available options. again, --help-list-hidden gives you more if you're nosy (and you should be). πŸ’–
  • --version β€” display the version of this program. slay.

πŸ”₯ RTDyld Options πŸ”₯

  • --args <string>... β€” your <program arguments>... fr fr.
  • --check=<string> β€” a file containing RuntimeDyld verifier checks. it's giving "the receipts". 🧾
  • --dylib=<string> β€” add a library. yes, just add it, bestie. πŸ“š
  • --entry=<string> β€” the function to call as the entry point. that's the main character. πŸ‘‘
  • --mcpu=<cpu-name> β€” target a specific cpu type. and if you don't know your cpu types, -mcpu=help has the details for you. πŸ–₯️
  • --preallocate=<ulong> β€” allocate memory upfront instead of on-demand. impatient icon behavior, and honestly? valid. ⚑
  • --show-times β€” show times for llvm-rtdyld phases. the stopwatch is ON. ⏱️
  • --triple=<string> β€” target triple for the disassembler. 🎯

🎬 Action to perform 🎬

pick your adventure, bestie β€” you gotta tell it what to do:

  • --execute β€” load, link, and execute the inputs. the full send. πŸš€
  • --printline β€” load, link, and print line information for each function. πŸ“
  • --printdebugline β€” load, link, and print line information for each function, using the debug object. πŸ›βœ¨
  • --printobjline β€” like -printlineinfo but does not load the object first. subtle but so important. πŸ’…
  • --verify β€” load, link and verify the resulting memory image. vibe check, but for bytes. πŸ”
no cap: --printobjline skips loading the object first β€” that's genuinely different from the -printlineinfo behavior, so don't come for me when it behaves differently. πŸ’€

okay that's the whole page, you ate it, periodt. πŸ«ΆπŸ’–βœ¨

this lil sign-off is for llvm-rtdyld 22, dated September 2026, served piping hot from the LLVM source. bye bestie, go link something iconic. πŸŒΈπŸ’œπŸŒˆ

πŸ“¦ where this page comes from