LLVM-EXTRACT-BUNDLE-ENTRY(1)

💅 LLVM-EXTRACT-BUNDLE-ENTRY(1) — like, the whole manual, bestie

okay so real talk, this is llvm-extract-bundle-entry from the LLVM gang, and I'm gonna walk you through the whole thing. no cap, every flag stays. let's go 🫶

---

✨ NAME ✨

llvm-extract-bundle-entry — extract an offload bundle entry 🌸

---

🎀 SYNOPSIS 🎀

llvm-extract-bundle-entry [options] URI

---

🦋 DESCRIPTION 🦋

so llvm-extract-offload-entry (yes, the page says that name right there, I'm not making it up 😭) is a tool that takes a URI argument and generates a code object file by extracting an offload bundle entry specified by the URI you gave it. it's giving "point at a thing, get a file back." iconic.

the URI syntax is defined as:

<code_object_uri> ::== <file_uri> | <memory_uri> <file_uri>
::== "file://"<extract_file><range_specifier> <memory_uri>
::== "memory://"<process_id><range_specifier> <range_specifier>
::== [ "#" | "?" ]"offset="<number>"&size="<number>
<extract_file>    ::== URI_ENCODED_OS_FILE_PATH <process_id>
::== DECIMAL_NUMBER <number>          ::== DECIMAL_NUMBER

and the output? always written to a file, literally always 🫶 and its name is generated from the URI input you gave. so you don't even gotta name it yourself, the tool picks for you. slay.

---

✨ OPTIONS ✨

these options are either agnostic of the file format or apply to multiple file formats. iykyk 💅

• --help, -h — prints a summary of the command line options. the classic "what does anything do again" button 🎀
• -o <file> — write output to <file>. bestie, listen: multiple input files cannot be used in combination with -o. that's a hard no, fr fr 🙈
• --version, -V — displays the version of the llvm-extract-bundle-entry executable. cute lil flex 💖

---

💀 EXIT STATUS 💀

llvm-extract-bundle-entry exits with a non-zero exit code if there is an error. otherwise? it exits with code 0. clean, no drama, we love a well-behaved binary ✨

---

🐛 BUGS 🐛

found a bug? don't suffer in silence, go report it here:

https://github.com/llvm/llvm-project/issues?q=state%3Aopen%20label%3Allvm-extract-bundle-entry

that's the whole vibe. take it to the issue tracker 📮

---

👑 AUTHOR 👑

maintained by the LLVM Team (https://llvm.org/). they're literally the main characters of this whole toolchain, periodt.

---

🌈 COPYRIGHT 🌈

2003-2026, LLVM Project

---

and that's the page!! signing off with the deets: this was the 23-flavored version, dated 2026-10-06, from LLVM, and the manual name is LLVM-EXTRACT-BUNDLE-ENTRY(1) in case you forgot already 😭💜 go extract something, bestie — you got this 🦋⭐