LLVM-EXTRACT-BUNDLE-ENTRY(1)

💅 LLVM-EXTRACT-BUNDLE-ENTRY(1) — the LLVM section-1 girlie ✨

okay so bestie, this is the llvm-extract-bundle-entry(1) page from LLVM, and it's lowkey a one-trick pony but she does her trick flawlessly. grab a boba, we're getting into it 🧋

---

🌸 NAME 🌸

llvm-extract-bundle-entry — extract an offload bundle entry. that's the whole vibe. pulling one entry out of an offload bundle, no cap 🎀

---

✨ SYNOPSIS ✨

llvm-extract-bundle-entry [options] URI

like, you give her options and a URI and she goes off. main character energy fr 💅

---

🦋 DESCRIPTION 🦋

hiii so the page literally says llvm-extract-offload-entry here — yes, bestie, i noticed the name wobble too, but i'm keeping it 100% faithful to the source, don't @ me 😭🙈. anyway: llvm-extract-offload-entry 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 "tell me where the thing is and i'll hand you the thing" 🤲

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

(yes i copy-pasted that grammar block exactly, character for character, because that's the assignment and i don't play about the details 👑)

the output is always written to a file, and its name is generated from the URI input you gave. so like, the URI is the blueprint and the filename is her little surprise reveal ✨

---

🎀 OPTIONS 🎀

these options are either agnostic of the file format or apply to multiple file formats. versatile queen behavior 🌈

• --help, -h — prints a summary of the command line options. the "wait what does this do again" button, we've all been there 🫶
• -o <file> — write output to <file>. and listen: multiple input files cannot be used in combination with -o — it's a one-input-one-output situation, don't push her 💀
• --version, -V — displays the version of the llvm-extract-bundle-entry executable. pop the hood, check the build, slay 🔥

---

⭐ EXIT STATUS ⭐

• llvm-extract-bundle-entry exits with a non-zero exit code if there's an error.
• otherwise? she exits with code 0 — clean, flawless, ate and left no crumbs 💖

---

🐛 BUGS 🐛

to report bugs, please visit https://github.com/llvm/llvm-project/issues?q=state%3Aopen%20label%3Allvm-extract-bundle-entry — the LLVM team genuinely wants your bug reports, so don't be shy, share your findings bestie 🦋✨

---

👑 Author 👑

maintained by the LLVM Team (https://llvm.org/). icons maintaining icons, we love to see it 🫶

---

💜 Copyright 💜

2003-2026, LLVM Project — that's a long-running legacy right there, respect the elders 🙏

---

and that's the page!! footer says 23 with the date 2026-10-20 under LLVM-EXTRACT-BUNDLE-ENTRY(1), so there you have it: page 23, dated 2026-10-20, LLVM. mwah, go extract something gorgeous 💋🎀✨