Searched refs:bitcode (Results 1 – 25 of 347) sorted by relevance
12345678910>>...14
| /external/clang/test/Frontend/ |
| D | embed-bitcode.ll | 5 ; RUN: -fembed-bitcode=all -x ir %s -o - \
8 ; RUN: -fembed-bitcode=marker -x ir %s -o - \
11 ; RUN: -fembed-bitcode=all -x ir %s -o - \
18 ; RUN: -fembed-bitcode=all -x ir %t.bc -o - \
21 ; RUN: -fembed-bitcode=bitcode -x ir %t.bc -o - \
24 ; RUN: -fembed-bitcode=marker -x ir %t.bc -o - \
27 ; run through -fembed-bitcode twice and make sure it doesn't crash
29 ; RUN: -fembed-bitcode=all -x ir %s -o - \
31 ; RUN: -fembed-bitcode=all -x ir - -o /dev/null
33 ; check the magic number of bitcode at the beginning of the string
|
| /external/swiftshader/third_party/llvm-7.0/llvm/test/Transforms/ThinLTOBitcodeWriter/ |
| D | no-type-md.ll | 1 ; Generate bitcode files with summary, as well as minimized bitcode without
3 ; RUN: opt -thinlto-bc -thin-link-bitcode-file=%t.thinlink.bc -o %t.bc %s
8 ; thin link bitcode files are identical
10 ; Copy the minimized bitcode to the regular bitcode path so the module
11 ; paths in the index are the same (save and restore the regular bitcode
22 ; Copy the minimized bitcode to the regular bitcode path so the module
|
| D | split.ll | 1 ; Generate bitcode files with summary, as well as minimized bitcode without
3 ; RUN: opt -thinlto-bc -thin-link-bitcode-file=%t2 -o %t %s
15 ; thin link bitcode files are identical
17 ; Copy the minimized bitcode to the regular bitcode path so the module
23 ; ERROR: llvm-modextract: error: module index out of range; bitcode file contains 2 module(s)
|
| /external/swiftshader/third_party/llvm-7.0/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-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-extract.rst | 13 it from the specified LLVM bitcode file. It is primarily used as a debugging
16 In addition to extracting the bitcode of the specified function,
30 refuse to write raw bitcode output if the output stream is a terminal. With
31 this option, :program:`llvm-extract` will write raw bitcode regardless of the
36 Extract the function named *function-name* from the LLVM bitcode. May be
41 Extract the function(s) matching *function-regular-expr* from the LLVM bitcode.
47 Extract the global variable named *global-name* from the LLVM bitcode. May be
53 bitcode. All global variables matching the regular expression will be
67 Write output in LLVM intermediate language (instead of bitcode).
|
| /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-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-extract.rst | 13 it from the specified LLVM bitcode file. It is primarily used as a debugging
16 In addition to extracting the bitcode of the specified function,
30 refuse to write raw bitcode output if the output stream is a terminal. With
31 this option, :program:`llvm-extract` will write raw bitcode regardless of the
36 Extract the function named *function-name* from the LLVM bitcode. May be
41 Extract the function(s) matching *function-regular-expr* from the LLVM bitcode.
47 Extract the global variable named *global-name* from the LLVM bitcode. May be
53 bitcode. All global variables matching the regular expression will be
67 Write output in LLVM intermediate language (instead of bitcode).
|
| /external/swiftshader/third_party/LLVM/docs/CommandGuide/ |
| D | llvm-bcanalyzer.pod | 5 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 …]
|
| D | llvm-nm.pod | 5 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.
|
| D | llvm-extract.pod | 14 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).
|
| D | llvm-link.pod | 13 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
|
| D | llvm-ld.pod | 13 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 …]
|
| /external/swiftshader/third_party/subzero/tests_lit/parse_errs/ |
| D | multiple-modules.test | 1 ; Tests that we check for multiple modules in the bitcode file.
5 ; RUN: not %pnacl_sz -bitcode-as-text \
7 ; RUN: -bitcode-format=pnacl -notranslate -build-on-read 2>&1 \
12 ; RUN: pnacl-bcfuzz -bitcode-as-text \
22 ; ASM: Error(38:4): Expected 1 top level block in bitcode: Found:2
|
| D | dup-module-vst.test | 1 ; Test if we detect multiple module-level symbol tables in bitcode.
5 ; RUN: not %pnacl_sz -bitcode-as-text %p/Inputs/dup-module-vst.tbc \
6 ; RUN: -bitcode-format=pnacl -notranslate -build-on-read 2>&1 \
11 ; RUN: pnacl-bcfuzz -bitcode-as-text %p/Inputs/dup-module-vst.tbc \
|
| /external/swiftshader/third_party/llvm-7.0/llvm/test/ThinLTO/X86/ |
| D | lazyload_metadata.ll | 1 ; Do setup work for all below tests: generate bitcode and combined index
2 ; RUN: opt -module-summary %s -o %t.bc -bitcode-mdindex-threshold=0
3 ; RUN: opt -module-summary %p/Inputs/lazyload_metadata.ll -o %t2.bc -bitcode-mdindex-threshold=0
13 ; LAZY: 55 bitcode-reader - Number of Metadata records loaded
14 ; LAZY: 2 bitcode-reader - Number of MDStrings loaded
19 ; NOTLAZY: 64 bitcode-reader - Number of Metadata records loaded
20 ; NOTLAZY: 7 bitcode-reader - Number of MDStrings loaded
|
| D | distributed_import.ll | 3 ; Generate bitcode files with summary, as well as minimized bitcode without
5 ; RUN: opt -thinlto-bc %s -thin-link-bitcode-file=%t1.thinlink.bc -o %t1.bc
6 ; RUN: opt -thinlto-bc %p/Inputs/distributed_import.ll -thin-link-bitcode-file=%t2.thinlink.bc -o %…
9 ; First perform the thin link on the normal bitcode file.
27 ; Copy the minimized bitcode to the regular bitcode path so the module
28 ; paths in the index are the same (save the regular bitcode for use again
35 ; Next perform the thin link on the minimized bitcode files, and compare dumps
|
| /external/swiftshader/third_party/llvm-7.0/llvm/test/tools/gold/X86/ |
| D | thinlto_object_suffix_replace.ll | 4 ; Generate bitcode file with summary, as well as a minimized bitcode without
6 ; RUN: opt -thinlto-bc %s -thin-link-bitcode-file=%t1.thinlink.bc -o %t1.o
8 ; First perform the thin link on the normal bitcode file, and save the
17 ; Next perform the thin link on the minimized bitcode file, and compare dump
20 ; Make sure it isn't inadvertently using the regular bitcode file.
|
| /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
21 (** [write_bitcode_to_fd ~unbuffered fd m] writes the bitcode for module
29 the bitcode for module [m]. *)
34 (** [output_bitcode ~unbuffered c m] writes the bitcode for module [m]
|
| /external/swiftshader/third_party/llvm-7.0/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
21 (** [write_bitcode_to_fd ~unbuffered fd m] writes the bitcode for module
29 the bitcode for module [m]. *)
34 (** [output_bitcode ~unbuffered c m] writes the bitcode for module [m]
|
| /external/swiftshader/third_party/llvm-7.0/llvm/test/Bindings/OCaml/ |
| D | diagnostic_handler.ml | 3 * RUN: %t/executable %t/bitcode.bc | FileCheck %s
5 * RUN: %t/executable %t/bitcode.bc | FileCheck %s
25 (* corrupt the bitcode *)
28 output_string oc "not a bitcode file\n";
36 (* CHECK: Diagnostic handler called: Invalid bitcode signature
|
| D | bitreader.ml | 3 * RUN: %t/executable %t/bitcode.bc
5 * RUN: %t/executable %t/bitcode.bc
6 * RUN: llvm-dis < %t/bitcode.bc
62 (* corrupt the bitcode *)
65 output_string oc "not a bitcode file\n";
|
| /external/swiftshader/third_party/subzero/pydir/ |
| D | crosstest.py | 122 bitcode = arg
126 bitcode = os.path.join(args.dir, base + '.' + key + '.pnacl.ll')
139 bitcode_nonfinal, '-S', '-o', bitcode])
158 bitcode] + arch_sz_flags[args.target])
191 bitcode] + llc_flags)
237 bitcode = os.path.join(args.dir, base + '.' + key + '.pnacl.ll')
257 bitcode_nonfinal, '-S', '-o', bitcode])
265 bitcode] + llc_flags)
|
| /external/swiftshader/third_party/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]
|
12345678910>>...14