1LLVM-TLI-CHECKER(1) LLVM LLVM-TLI-CHECKER(1)
2
3
4
6 llvm-tli-checker - TargetLibraryInfo vs library checker
7
9 llvm-tli-checker [options] [library-file...]
10
12 llvm-tli-checker compares TargetLibraryInfo's opinion of the availabil‐
13 ity of library functions against the set of functions exported by the
14 specified library files, reporting any disagreements between TLI's
15 opinion and whether the function is actually present. This is primarily
16 useful for vendors to ensure the TLI for their target is correct, and
17 the compiler will not "optimize" some code sequence into a library call
18 that is not actually available.
19
21 $ llvm-tli-checker --triple x86_64-scei-ps4 example.so
22 TLI knows 466 symbols, 235 available for 'x86_64-scei-ps4'
23
24 Looking for symbols in 'example.so'
25 Found 235 global function symbols in 'example.so'
26 Found a grand total of 235 library symbols
27 << TLI yes SDK no: '_ZdaPv' aka operator delete[](void*)
28 >> TLI no SDK yes: '_ZdaPvj' aka operator delete[](void*, unsigned int)
29 << Total TLI yes SDK no: 1
30 >> Total TLI no SDK yes: 1
31 == Total TLI yes SDK yes: 234
32 FAIL: LLVM TLI doesn't match SDK libraries.
33
35 --dump-tli
36 Print "available"/"not available" for each library function, ac‐
37 cording to TargetLibraryInfo's information for the specified
38 triple, and exit. This option does not read any input files.
39
40 --help, -h
41 Print a summary of command line options and exit.
42
43 --libdir=<directory>
44 A base directory to prepend to each library file path. This is
45 handy when there are a number of library files all in the same
46 directory, or a list of input filenames are kept in a response
47 file.
48
49 --report=<level>
50 The amount of information to report. <level> can be summary,
51 discrepancy, or full. A summary report gives only the count of
52 matching and mis-matching symbols; discrepancy lists the
53 mis-matching symbols; and full lists all symbols known to TLI,
54 matching or mis-matching. The default is discrepancy.
55
56 --separate
57 Read and report a summary for each library file separately.
58 This can be useful to identify library files that don't contrib‐
59 ute anything that TLI knows about. Implies --report=summary (can
60 be overridden).
61
62 --triple=<triple>
63 The triple to use for initializing TargetLibraryInfo.
64
65 @<FILE>
66 Read command-line options and/or library names from response
67 file <FILE>.
68
70 llvm-tli-checker returns 0 even if there are mismatches. It returns a
71 non-zero exit code if there is an unrecognized option, or no input
72 files are provided.
73
75 Maintained by the LLVM Team (https://llvm.org/).
76
78 2003-2023, LLVM Project
79
80
81
82
8315 2023-07-20 LLVM-TLI-CHECKER(1)