| /external/llvm/docs/CommandGuide/ |
| D | llvm-link.rst | 1 llvm-link - LLVM bitcode linker
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,
22 to write raw bitcode output if the output stream is a terminal. With this
23 option, :program:`llvm-link` will write raw bitcode regardless of the output
33 Write output in LLVM intermediate language (instead of bitcode).
38 output bitcode file to standard error.
47 This typically includes a message for each bitcode file linked in and for each
|
| 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-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).
|
| /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]
|
| /external/chromium_org/native_client_sdk/src/doc/reference/ |
| D | pnacl-bitcode-abi.rst | 13 This document is a reference manual for the PNaCl bitcode format. It describes
14 the bitcode on a *semantic* level; the physical encoding level will be described
16 used to describe instructions and other bitcode constructs.
18 Since the PNaCl bitcode is based to a large extent on LLVM IR, many sections
32 The data model for PNaCl bitcode is fixed at little-endian ILP32: pointers are
48 The linkage types supported by PNaCl bitcode are ``internal`` and ``external``.
59 The only calling convention supported by PNaCl bitcode is ``ccc`` - the C
68 PNaCl bitcode does not support visibility styles.
80 * PNaCl bitcode does not support LLVM IR TLS models. See
134 PNaCl bitcode does not support aliases.
[all …]
|
| /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/mesa3d/src/gallium/drivers/r600/ |
| D | llvm_wrapper.cpp | 11 extern "C" LLVMModuleRef llvm_parse_bitcode(const unsigned char * bitcode, unsigned bitcode_len) in llvm_parse_bitcode() argument
14 llvm::StringRef str((const char*)bitcode, bitcode_len); in llvm_parse_bitcode()
|
| D | llvm_wrapper.h | 10 LLVMModuleRef llvm_parse_bitcode(const unsigned char * bitcode, unsigned bitcode_len);
|
| /external/chromium_org/third_party/mesa/src/src/gallium/drivers/r600/ |
| D | llvm_wrapper.cpp | 11 extern "C" LLVMModuleRef llvm_parse_bitcode(const unsigned char * bitcode, unsigned bitcode_len) in llvm_parse_bitcode() argument
14 llvm::StringRef str((const char*)bitcode, bitcode_len); in llvm_parse_bitcode()
|
| D | llvm_wrapper.h | 10 LLVMModuleRef llvm_parse_bitcode(const unsigned char * bitcode, unsigned bitcode_len);
|
| /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:
|
| /external/chromium_org/native_client_sdk/src/tools/ |
| D | nacl_llvm.mk | 103 $(call LOG,TRANSLATE,$$@,$(PNACL_TRANSLATE) --allow-llvm-bitcode-input -arch x86-32 $$^ -o $$@)
106 $(call LOG,TRANSLATE,$$@,$(PNACL_TRANSLATE) --allow-llvm-bitcode-input -arch x86-64 $$^ -o $$@)
109 $(call LOG,TRANSLATE,$$@,$(PNACL_TRANSLATE) --allow-llvm-bitcode-input -arch arm $$^ -o $$@)
|
| /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 | 47 * This downstreaming could have broken bitcode compatibility
48 * Upstream was migrating from 2.7 bitcode to 3.0 bitcode.
56 …==> * 020a5a4 - remove bitcode reader support for LLVM 2.7 metadata encoding. (13 days ago) <Chris…
58 * 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/mesa3d/src/gallium/drivers/radeon/ |
| D | radeon_llvm_emit.h | 37 unsigned char * bitcode, unsigned bitcode_len,
|
| /external/chromium_org/third_party/mesa/src/src/gallium/drivers/radeon/ |
| D | radeon_llvm_emit.h | 37 unsigned char * bitcode, unsigned bitcode_len,
|