Searched refs:bitcode (Results 1 – 25 of 90) sorted by relevance
1234
1 llvm-link - LLVM bitcode linker14 :program:`llvm-link` takes several LLVM bitcode files and links them together15 into a single LLVM bitcode file. It writes the output file to standard output,24 to write raw bitcode output if the output stream is a terminal. With this25 option, :program:`llvm-link` will write raw bitcode regardless of the output35 Write output in LLVM intermediate language (instead of bitcode).40 output bitcode file to standard error.49 This typically includes a message for each bitcode file linked in and for each
1 llvm-bcanalyzer - LLVM bitcode analyzer14 The :program:`llvm-bcanalyzer` command is a small utility for analyzing bitcode15 files. The tool reads a bitcode file (such as generated with the17 the bitcode file. The tool can also dump a low level but human readable18 version of the bitcode file. This tool is probably not of much interest or19 utility except for those working directly with the bitcode file format. Most33 Causes :program:`llvm-bcanalyzer` to dump the bitcode in a human readable35 provides details about the encoding of the bitcode file.55 This just provides the name of the module for which bitcode analysis is being60 The bitcode version (not LLVM version) of the file read by the analyzer.[all …]
15 it from the specified LLVM bitcode file. It is primarily used as a debugging18 In addition to extracting the bitcode of the specified function,31 Extract the alias named *function-name* from the LLVM bitcode. May be36 Extract the alias matching *alias-regular-expr* from the LLVM bitcode.54 refuse to write raw bitcode output if the output stream is a terminal. With55 this option, :program:`llvm-extract` will write raw bitcode regardless of the60 Extract the function named *function-name* from the LLVM bitcode. May be65 Extract the function(s) matching *function-regular-expr* from the LLVM bitcode.71 Extract the global variable named *global-name* from the LLVM bitcode. May be77 bitcode. All global variables matching the regular expression will be[all …]
15 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 **llvm-dis** will write raw bitcode regardless of the output device.
15 LLVM assembly language, translates it to LLVM bitcode, and writes the result39 write raw bitcode output if the output stream is a terminal. With this option,40 **llvm-as** will write raw bitcode regardless of the output device.
1 lli - directly execute programs from LLVM bitcode14 :program:`lli` directly executes programs in LLVM bitcode format. It takes a program15 in LLVM bitcode format and executes it using a just-in-time compiler or an24 If `filename` is not specified, then :program:`lli` reads the LLVM bitcode for the70 Override the target triple specified in the input bitcode file with the77 encoded in the bitcode file. See the output of **llc -help** for a list of
23 language format (``.ll``) or the LLVM bitcode format (``.bc``).34 write raw bitcode output if the output stream is a terminal. With this option,35 :program:`opt` will write raw bitcode regardless of the output device.47 Write output in LLVM intermediate language (instead of bitcode).
1 llvm-nm - list LLVM bitcode and object file's symbol table14 The :program:`llvm-nm` utility lists the names of symbols from LLVM bitcode114 Because LLVM bitcode files typically contain objects that are not considered to117 symbol in an LLVM bitcode file, even symbols which are defined in the bitcode203 Disable the LLVM bitcode reader.
11 This interface provides an OCaml API for the LLVM bitcode writer, the14 (** [write_bitcode_file m path] writes the bitcode for module [m] to the file at20 (** [write_bitcode_to_fd ~unbuffered fd m] writes the bitcode for module28 the bitcode for module [m]. *)33 (** [output_bitcode ~unbuffered c m] writes the bitcode for module [m]
1 //===-- BitcodeStripOpts.td - llvm-bitcode-strip options ---------------*-===//9 // This file describes the command line options of llvm-bitcode-strip.27 HelpText<"Remove the __LLVM bitcode segment entirely">;
38 add_llvm_tool_symlink(llvm-bitcode-strip llvm-objcopy)48 add_llvm_tool_symlink(bitcode_strip llvm-bitcode-strip)
11 This interface provides an OCaml API for the LLVM bitcode reader, the16 (** [get_module context mb] reads the bitcode for a new module [m] from the22 (** [parse_bitcode context mb] parses the bitcode for a new module [m] from the
33 --bitcode-library=<kind>-<triple>-<arch>=<path>34 Extra bitcode library to link40 --embed-bitcode Embed linked bitcode in the module
48 * Compile the input file for the host to produce a bitcode file. Lower ``#pragma56 * Run the backend on the host bitcode file and create a :ref:`fat object file196 ``-fopenmp-is-device`` flag to the front-end. We use the host bitcode to197 determine which symbols to export from the device. The bitcode file is passed in208 by linking in a special bitcode library during compilation, (e.g.209 ``libomptarget-nvptx64-sm_70.bc``) using the ``-mlink-builtin-bitcode`` flag.265 The linker wrapper tool supports linking bitcode files through link time267 contain LLVM bitcode. Bitcode will be embedded for architectures that do not
24 treats LLVM bitcode files like native object files and allows mixing and26 bitcode files. This tight integration between the linker and LLVM optimizer40 * Input source file ``a.c`` is compiled into LLVM bitcode form.90 % clang -flto -c a.c -o a.o # <-- a.o is LLVM bitcode file95 visible symbol defined in LLVM bitcode file. The linker completes its usual152 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 the172 content of input LLVM bitcode files. If dead code stripping is enabled then the183 native object file creating by merging the LLVM bitcode files and applying191 information about any changes in use of external symbols by LLVM bitcode[all …]
20 As of LLVM 15, the gold plugin will ignore bitcode from the ``.llvmbc``21 section inside of ELF object files. However, LTO with bitcode files78 You should produce bitcode files from ``clang`` with the option95 bitcode and native code.133 $ clang -flto a.c -c -o a.o # <-- a.o is LLVM bitcode file134 $ ar q a.a a.o # <-- a.a is an archive with LLVM bitcode145 Once your system ``ld``, ``ar``, and ``nm`` all support LLVM bitcode,
180 causes an error, and simplify the bitcode file as much as it can to assist202 bugpoint -run-jit -output=[correct output file] [bitcode file] \210 bugpoint -run-llc -output=[correct output file] [bitcode file] \225 with two bitcode files: a *safe* file which can be compiled with the C232 #. Regenerate the shared object from the safe bitcode file:239 #. If debugging LLC, compile test bitcode native and link with the shared249 bitcode:
87 For ``dxil`` targeting, bitcode emission into ``DXContainer`` files follows a88 similar model to the ``-fembed-bitcode`` flag supported by clang for other
25 def bitcode_library_EQ : Joined<["--"], "bitcode-library=">,27 HelpText<"Extra bitcode library to link">;36 def embed_bitcode : Flag<["--"], "embed-bitcode">,37 Flags<[WrapperOnlyOption]>, HelpText<"Embed linked bitcode in the module">;
47 case file_magic::bitcode: in createSymbolicFile()100 case file_magic::bitcode: in isSymbolicFile()
84 return file_magic::bitcode; in identify_magic()88 return file_magic::bitcode; in identify_magic()
7 LLVM bitcode file to standard output. It is designed to show some basic
23 bitcode, ///< Bitcode file enumerator
11 This interface provides an OCaml API for LLVM bitcode linker,
63 case file_magic::bitcode: in hasObjCSection()