LLVM-TLI-CHECKER(1)

📦
version 16.0.6 · 3 versions
, in ubuntu noble

🦋 LLVM-TLI-CHECKER(1) — the TargetLibraryInfo vs library checker, bestie edition

okay so this is a page from the LLVM manual suite, and it's about a little tool that goes by llvm-tli-checker. she's a vibe checker, but for symbols. let's get into it 💅

✨ NAME ✨

llvm-tli-checker — TargetLibraryInfo vs library checker. literally what it says on the tin, no cap.

🌸 SYNOPSIS 🌸

llvm-tli-checker [options] [library-file…]

that's it. that's the whole entry point. you give her some options, you give her some library files, she goes to work 🫶

💖 DESCRIPTION 💖

so here's the tea, bestie 🍓

llvm-tli-checker takes TargetLibraryInfo's opinion about whether library functions are available, and it compares that opinion against the actual set of functions exported by the library files you told it about. then it reports every single disagreement — like, every place where TLI thinks one thing and reality thinks another.

basically it's checking "does TLI say this function is there?" vs "is this function actually there?" and calling out the drama when those two don't match. 🔥

who is this for? primarily vendors — people who need to make sure the TLI for their target is correct. because if it's not, the compiler will "optimize" some code sequence into a library call that isn't actually available, and that is not the moment you want to be having. 💀

🎀 EXAMPLE 🎀

here's her serving a real example, look at her go:

$ llvm-tli-checker --triple x86_64-scei-ps4 example.so
TLI knows 466 symbols, 235 available for 'x86_64-scei-ps4'

Looking for symbols in 'example.so'
Found 235 global function symbols in 'example.so'
Found a grand total of 235 library symbols
<< TLI yes SDK no:  '_ZdaPv' aka operator delete[](void*)
>> TLI no  SDK yes: '_ZdaPvj' aka operator delete[](void*, unsigned int)
<< Total TLI yes SDK no:  1
>> Total TLI no  SDK yes: 1
== Total TLI yes SDK yes: 234
FAIL: LLVM TLI doesn't match SDK libraries.

see the << and >> arrows? that's her pointing at the mismatches. << is "TLI said yes, SDK said no" and >> is "TLI said no, SDK said yes". she's dramatic about it and honestly? deserved. 😭

⭐ OPTIONS ⭐

one bullet per flag, no skipping, we respect all of them equally:

  • --dump-tli — prints "available"/"not available" for every single library function, based on what TargetLibraryInfo knows for the triple you specified, and then exits. and listen — this one does not read any input files at all. she just dumps the TLI and dips. 💅
  • --help, -h — prints a summary of the command line options and exits. your classic "wait what were the flags again" move 🫶
  • --libdir=<directory> — a base directory that gets prepended to each library file path. this is so handy when you've got a bunch of library files all chilling in the same directory, or when your list of input filenames is sitting in a response file. queen of convenience 👑
  • --report=<level> — how much info she spills. <level> can be summary, discrepancy, or full.
    • summary → only gives you the count of matching and mis-matching symbols
    • discrepancy → lists the mis-matching symbols
    • full → lists all symbols known to TLI, matching or mis-matching

the default is discrepancy. so by default she names names. 🍓

  • --separate — reads and reports a summary for each library file separately. lowkey useful when you're trying to identify library files that don't contribute anything TLI knows about. this implies --report=summary (and yes, you can override that). 🙈
  • --triple=<triple> — the triple to use for initializing TargetLibraryInfo. that's the whole job of this flag, she's very focused ✨
  • @<FILE> — read command-line options and/or library names from the response file <FILE>. group-chat style: you don't type everything, you forward the whole thread 🌈

🧚 EXIT STATUS 🧚

okay this part is important, pay attention:

llvm-tli-checker returns 0 even if there are mismatches. yes really. she found the drama, she told you about it, she's still gonna exit clean. 💀

she returns a non-zero exit code if:

  • there's an unrecognized option, or
  • no input files are provided

so if you get a non-zero, it's not about the symbols — it's about you. (lovingly.) 🫶

💜 AUTHOR 💜

maintained by the LLVM Team (https://llvm.org/). they're the ones keeping this whole thing alive, periodt. 👑

2003-2024, LLVM Project

and that's the whole page bestie 🎀 she's LLVM manual page 15, dated 2024-04-14, from the LLVM suite itself — go check your target's TLI, iykyk 💅✨🦋

📦 where this page comes from