Searched refs:bitcode (Results 1 – 25 of 50) sorted by relevance
12
| /external/llvm/docs/CommandGuide/ |
| D | llvm-extract.rst | 17 the specified LLVM bitcode file. It is primarily used as a debugging tool to
20 In addition to extracting the bitcode of the specified function,
37 write raw bitcode output if the output stream is a terminal. With this option,
38 **llvm-extract** will write raw bitcode regardless of the output device.
44 Extract the function named *function-name* from the LLVM bitcode. May be
51 Extract the function(s) matching *function-regular-expr* from the LLVM bitcode.
59 Extract the global variable named *global-name* from the LLVM bitcode. May be
67 bitcode. All global variables matching the regular expression will be extracted.
87 Write output in LLVM intermediate language (instead of bitcode).
|
| D | llvm-bcanalyzer.rst | 1 llvm-bcanalyzer - LLVM bitcode analyzer
12 The :program:`llvm-bcanalyzer` command is a small utility for analyzing bitcode
13 files. The tool reads a bitcode file (such as generated with the
15 the bitcode file. The tool can also dump a low level but human readable
16 version of the bitcode file. This tool is probably not of much interest or
17 utility except for those working directly with the bitcode file format. Most
37 Causes :program:`llvm-bcanalyzer` to dump the bitcode in a human readable
39 provides details about the encoding of the bitcode file.
44 bitcode. This ensures that the statistics generated are based on a consistent
65 This just provides the name of the module for which bitcode analysis is being
[all …]
|
| D | llvm-link.rst | 12 :program:`llvm-link` takes several LLVM bitcode files and links them together
13 into a single LLVM bitcode file. It writes the output file to standard output,
36 to write raw bitcode output if the output stream is a terminal. With this
37 option, :program:`llvm-link` will write raw bitcode regardless of the output
47 Write output in LLVM intermediate language (instead of bitcode).
52 bitcode file to standard error.
61 This typically includes a message for each bitcode file linked in and for each
|
| D | llvm-nm.rst | 1 llvm-nm - list LLVM bitcode and object file's symbol table
16 The :program:`llvm-nm` utility lists the names of symbols from the LLVM bitcode
33 Named object is referenced but undefined in this bitcode file
79 Because LLVM bitcode files typically contain objects that are not considered to
82 symbol in a LLVM bitcode file, even symbols which are defined in the bitcode
|
| D | llvm-dis.rst | 17 bitcode file and converts it into human-readable LLVM assembly language.
38 write raw bitcode output if the output stream is a terminal. With this option,
39 **llvm-dis** will write raw bitcode regardless of the output device.
|
| D | llvm-prof.rst | 9 **llvm-prof** [*options*] [*bitcode file*] [*llvmprof.out*]
17 optionally use a specific file with the third program argument), a bitcode file
62 **llvm-prof** returns 1 if it cannot load the bitcode file or the profile
|
| D | llvm-as.rst | 13 LLVM assembly language, translates it to LLVM bitcode, and writes the result
37 write raw bitcode output if the output stream is a terminal. With this option,
38 **llvm-as** will write raw bitcode regardless of the output device.
|
| D | lli.rst | 1 lli - directly execute programs from LLVM bitcode
16 **lli** directly executes programs in LLVM bitcode format. It takes a program
17 in LLVM bitcode format and executes it using a just-in-time compiler, if one is
22 If *filename* is not specified, then **lli** reads the LLVM bitcode for the
88 Override the target triple specified in the input bitcode file with the
97 encoded in the bitcode file. See the output of **llc -help** for a list of
|
| D | opt.rst | 32 language format (``.ll``) or the LLVM bitcode format (``.bc``).
43 write raw bitcode output if the output stream is a terminal. With this option,
44 :program:`opt` will write raw bitcode regardless of the output device.
56 Write output in LLVM intermediate language (instead of bitcode).
|
| D | llvm-ar.rst | 18 to produce archive libraries by LLVM bitcode that can be linked into an
48 Since **llvm-ar** is intended to archive bitcode files, the symbol table
80 the file is an LLVM bitcode file. An 'S' means the file is the symbol table.
132 Printing bitcode files is ill-advised as they might confuse your terminal
161 **llvm-ar** also prints out the file type (B=bitcode, S=symbol
223 Normally, **llvm-ar** will not print the contents of bitcode files when the
225 bitcode members to be printed.
286 bitcode files in the archive. Using this modifier is more efficient that using
414 The offset item provides the offset into the archive file where the bitcode
|
| D | llvm-ranlib.rst | 20 implementations of ``ranlib``, **llvm-ranlib** indexes LLVM bitcode files, not
|
| D | bugpoint.rst | 152 **--safe-custom** options to execute the bitcode testcase. This can
158 option to compile the bitcode testcase. This can be useful for
170 will be the minimum bitcode that passes FileCheck.
|
| /external/llvm/bindings/ocaml/bitwriter/ |
| D | llvm_bitwriter.mli | 12 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]
|
| D | llvm_bitwriter.ml | 16 (* Writes the bitcode for module the given path. Returns true if successful. *)
|
| /external/llvm/bindings/ocaml/bitreader/ |
| D | llvm_bitreader.mli | 12 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/docs/ |
| D | LinkTimeOptimization.rst | 24 treates LLVM bitcode files like native object files and allows mixing and
26 bitcode files. This tight integration between the linker and LLVM optimizer
40 * Input source file ``a.c`` is compiled into LLVM bitcode form.
90 % clang -emit-llvm -c a.c -o a.o # <-- a.o is LLVM bitcode file
95 visible symbol defined in LLVM bitcode file. The linker completes its usual
152 information. This includes native object files as well as LLVM bitcode files.
156 returns that the file is an LLVM bitcode file, the linker then iterates over the
172 content of input LLVM bitcode files. If dead code stripping is enabled then the
183 native object file creating by merging the LLVM bitcode files and applying
191 information about any changes in use of external symbols by LLVM bitcode
[all …]
|
| D | GoldPlugin.rst | 69 You can produce bitcode files from ``clang`` using ``-emit-llvm`` or
86 bitcode and native code.
124 $ clang -flto a.c -c -o a.o # <-- a.o is LLVM bitcode file
125 $ ar q a.a a.o # <-- a.a is an archive with LLVM bitcode
136 Once your system ``ld``, ``ar``, and ``nm`` all support LLVM bitcode,
|
| D | HowToSubmitABug.rst | 159 causes an error, and simplify the bitcode file as much as it can to assist
178 bugpoint -run-jit -output=[correct output file] [bitcode file] \
186 bugpoint -run-llc -output=[correct output file] [bitcode file] \
201 with two bitcode files: a *safe* file which can be compiled with the C
208 #. Regenerate the shared object from the safe bitcode file:
215 #. If debugging LLC, compile test bitcode native and link with the shared
225 bitcode:
|
| D | GettingStarted.rst | 16 contains an assembler, disassembler, bitcode analyzer and bitcode optimizer. It
22 bitcode. Once compiled into LLVM bitcode, a program can be manipulated with the
196 assemble, disassemble, analyze, and optimize LLVM bitcode. Code generation
431 ``LLVM_LIB_SEARCH_PATH=/path/to/your/bitcode/libs``
434 locations of your bitcode libraries. It is provided only as a convenience
436 C/C++ front-end will automatically use the bitcode files installed in its
856 install bitcode libraries into the GCC front end's bitcode library directory.
857 If you need to update your bitcode libraries, this is the target to use once
996 execute LLVM bitcode files directly. To do this, use commands like this (the
1006 This allows you to execute LLVM bitcode files directly. On Debian, you can also
[all …]
|
| D | GettingStartedVS.rst | 18 bitcode analyzer and bitcode optimizer. It also contains a test suite that can
26 most standard C programs do compile. Clang can be used to emit bitcode,
164 2. Next, compile the C file into a LLVM bitcode file:
170 This will create the result file ``hello.bc`` which is the LLVM bitcode
|
| D | MakefileGuide.rst | 178 In some situations, it is desirable to build a single bitcode module from a
179 variety of sources, instead of an archive, shared library, or bitcode
190 module will be an aggregation of all the bitcode modules derived from the
191 sources. The example will also build a bitcode archive containing a bitcode
490 If set to any value, causes a bitcode library (.bc) to be built.
596 Specifies the name of a bitcode module to be created. A bitcode module can
598 itself. It constructs from the sources a single linked bitcode file.
755 Specifies the path to the LLVM bitcode linker tool
814 The directory into which bitcode libraries will ultimately be installed.
|
| /external/llvm/test/Other/ |
| D | extract.ll | 7 ; llvm-extract uses lazy bitcode loading, so make sure it correctly reads
8 ; from bitcode files in addition to assembly files.
|
| /external/llvm/ |
| D | README.android | 43 * This downstreaming could have broken bitcode compatibility
44 * Upstream was migrating from 2.7 bitcode to 3.0 bitcode.
52 …==> * 020a5a4 - remove bitcode reader support for LLVM 2.7 metadata encoding. (13 days ago) <Chris…
54 * Our bitcode reader can read both 2.7 and 3.0 versions. Writer is tracking upstream.
|
| /external/llvm/test/Bindings/Ocaml/ |
| D | bitreader.ml | 55 (* corrupt the bitcode *)
58 output_string oc "not a bitcode file\n";
|
| /external/llvm/examples/ModuleMaker/ |
| D | README.txt | 7 LLVM bitcode file to standard output. It is designed to show some basic
|
12