Home
last modified time | relevance | path

Searched refs:bitcode (Results 1 – 25 of 33) sorted by relevance

12

/external/llvm/docs/CommandGuide/
Dllvm-nm.pod5 llvm-nm - list LLVM bitcode file's symbol table
13 The B<llvm-nm> utility lists the names of symbols from the LLVM bitcode files,
14 or B<ar> archives containing LLVM bitcode files, named on the command line.
17 process a bitcode file on its standard input stream.
31 Named object is referenced but undefined in this bitcode file
63 Because LLVM bitcode files typically contain objects that are not considered to
66 even symbols which are defined in the bitcode file.
86 Print only symbols defined in this bitcode file (as opposed to
93 from other bitcode files.
97 Print only symbols referenced but not defined in this bitcode file.
Dllvm-extract.pod14 the specified LLVM bitcode file. It is primarily used as a debugging tool to
17 In addition to extracting the bitcode of the specified function,
32 write raw bitcode output if the output stream is a terminal. With this option,
33 B<llvm-extract> will write raw bitcode regardless of the output device.
37 Extract the function named I<function-name> from the LLVM bitcode. May be
42 Extract the function(s) matching I<function-regular-expr> from the LLVM bitcode.
48 Extract the global variable named I<global-name> from the LLVM bitcode. May be
54 bitcode. All global variables matching the regular expression will be extracted.
68 Write output in LLVM intermediate language (instead of bitcode).
Dllvm-bcanalyzer.pod5 llvm-bcanalyzer - LLVM bitcode analyzer
13 The B<llvm-bcanalyzer> command is a small utility for analyzing bitcode files.
14 The tool reads a bitcode file (such as generated with the B<llvm-as> tool) and
15 produces a statistical report on the contents of the bitcode file. The tool
16 can also dump a low level but human readable version of the bitcode file.
18 directly with the bitcode file format. Most LLVM users can just ignore
36 Causes B<llvm-bcanalyzer> to dump the bitcode in a human readable format. This
38 the encoding of the bitcode file.
43 bitcode. This ensures that the statistics generated are based on a consistent
66 This just provides the name of the module for which bitcode analysis is being
[all …]
Dllvm-link.pod13 B<llvm-link> takes several LLVM bitcode files and links them together into a
14 single LLVM bitcode file. It writes the output file to standard output, unless
37 write raw bitcode output if the output stream is a terminal. With this option,
38 B<llvm-link> will write raw bitcode regardless of the output device.
47 Write output in LLVM intermediate language (instead of bitcode).
52 bitcode file to standard error.
61 typically includes a message for each bitcode file linked in and for each
Dllvm-ld.pod13 The B<llvm-ld> tool takes a set of LLVM bitcode files and links them
14 together into a single LLVM bitcode file. The output bitcode file can be
15 another bitcode file or an executable bitcode program. Using additional
50 All object and bitcode files are linked first in the order they were
56 Object files and static bitcode objects are always linked into the output
67 performed by converting the linked bitcode into native assembly (.s) or C code
109 This option can be used to override the output bitcode file name. By default,
110 the name of the bitcode output file is one more ".bc" suffix added to the name
130 Link the bitcode files together as a library, not an executable. In this mode,
141 When generating native executables, B<llvm-ld> first checks for a bitcode
[all …]
Dllvm-dis.pod14 bitcode file and converts it into human-readable LLVM assembly language.
33 write raw bitcode output if the output stream is a terminal. With this option,
34 B<llvm-dis> will write raw bitcode regardless of the output device.
Dllvm-prof.pod9 B<llvm-prof> [I<options>] [I<bitcode file>] [I<llvmprof.out>]
14 optionally use a specific file with the third program argument), a bitcode file
50 B<llvm-prof> returns 1 if it cannot load the bitcode file or the profile
Dllvm-as.pod14 LLVM assembly language, translates it to LLVM bitcode, and writes the result
50 write raw bitcode output if the output stream is a terminal. With this option,
51 B<llvm-as> will write raw bitcode regardless of the output device.
Dlli.pod5 lli - directly execute programs from LLVM bitcode
13 B<lli> directly executes programs in LLVM bitcode format. It takes a program
14 in LLVM bitcode format and executes it using a just-in-time compiler, if one is
19 If I<filename> is not specified, then B<lli> reads the LLVM bitcode for the
69 Override the target triple specified in the input bitcode file with the
76 encoded in the bitcode file. See the output of B<llc -help> for a list of
Dopt.pod32 format (.ll) or the LLVM bitcode format (.bc).
44 write raw bitcode output if the output stream is a terminal. With this option,
45 B<opt> will write raw bitcode regardless of the output device.
57 Write output in LLVM intermediate language (instead of bitcode).
Dllvm-ar.pod16 to produce archive libraries by LLVM bitcode that can be linked into an
47 Since B<llvm-ar> is intended to archive bitcode files, the symbol table
81 the file is compressed. A 'B' means the file is an LLVM bitcode file. An
126 Printing bitcode files is ill-advised as they might confuse your terminal
149 B<llvm-ar> also prints out the file type (B=bitcode, Z=compressed, S=symbol
199 Normally, B<llvm-ar> will not print the contents of bitcode files when the
201 bitcode members to be printed.
233 modifier is safe to use when (previously) compressed bitcode files are added to
234 the archive; the compressed bitcode files will not be doubly compressed.
255 bitcode files in the archive. Using this modifier is more efficient that using
[all …]
Dllvm-ranlib.pod17 implementations of C<ranlib>, B<llvm-ranlib> indexes LLVM bitcode files, not
Dbugpoint.pod147 B<--safe-custom> options to execute the bitcode testcase. This can
153 option to compile the bitcode testcase. This can be useful for
163 will be the minimum bitcode that passes FileCheck.
Dllvm-diff.pod19 ends in '.ll'; otherwise it will be read in as a bitcode file.
Dllvm-config.pod118 Includes either a native JIT or the bitcode interpreter.
/external/llvm/bindings/ocaml/bitwriter/
Dllvm_bitwriter.mli12 This interface provides an ocaml API for the LLVM bitcode writer, the
15 (** [write_bitcode_file m path] writes the bitcode for module [m] to the file at
20 (** [write_bitcode_to_fd ~unbuffered fd m] writes the bitcode for module
27 (** [output_bitcode ~unbuffered c m] writes the bitcode for module [m]
Dllvm_bitwriter.ml16 (* Writes the bitcode for module the given path. Returns true if successful. *)
/external/llvm/bindings/ocaml/bitreader/
Dllvm_bitreader.mli12 This interface provides an ocaml API for the LLVM bitcode reader, the
17 (** [get_module context mb] reads the bitcode for a new module [m] from the
24 (** [parse_bitcode context mb] parses the bitcode for a new module [m] from the
/external/llvm/
DREADME.android36 * This downstreaming could have broken bitcode compatibility
37 * Upstream was migrating from 2.7 bitcode to 3.0 bitcode.
45 …==> * 020a5a4 - remove bitcode reader support for LLVM 2.7 metadata encoding. (13 days ago) <Chris…
47 * Our bitcode reader can read both 2.7 and 3.0 versions. Writer is tracking upstream.
/external/llvm/test/Other/
Dextract.ll7 ; llvm-extract uses lazy bitcode loading, so make sure it correctly reads
8 ; from bitcode files in addition to assembly files.
/external/llvm/test/Bindings/Ocaml/
Dbitreader.ml55 (* corrupt the bitcode *)
58 output_string oc "not a bitcode file\n";
/external/llvm/examples/ModuleMaker/
DREADME.txt7 LLVM bitcode file to standard output. It is designed to show some basic
/external/llvm/lib/Support/
DPath.cpp218 return type == fs::file_magic::bitcode; in isBitcodeFile()
DPathV2.cpp751 return file_magic::bitcode; in identify_magic()
755 return file_magic::bitcode; in identify_magic()
/external/llvm/include/llvm/Support/
DFileSystem.h129 bitcode, ///< Bitcode file enumerator

12