Searched refs:lli (Results 1 – 25 of 270) sorted by relevance
1234567891011
40 add_llvm_tool(lli41 lli.cpp44 export_executable_symbols(lli)
2 // lli command line tool6 name: "lli",9 "lli.cpp",
1 ;===- ./tools/lli/LLVMBuild.txt --------------------------------*- Conf -*--===;23 name = lli
5 lli - directly execute programs from LLVM bitcode9 B<lli> [I<options>] [I<filename>] [I<program args>]13 B<lli> directly executes programs in LLVM bitcode format. It takes a program15 available for the current architecture, or an interpreter. B<lli> takes all of17 B<lli> is using the just-in-time compiler.19 If I<filename> is not specified, then B<lli> reads the LLVM bitcode for the44 Causes B<lli> to load the plugin (shared object) named I<pluginfilename> and use59 Print out the version of B<lli> and exit without doing anything else.115 Causes B<lli> to enable optimizations that may decrease floating point120 Causes B<lli> to generate software floating point library calls instead of[all …]
1 ;===- ./tools/lli/ChildTarget/LLVMBuild.txt --------------------*- Conf -*--===;20 name = lli-child-target21 parent = lli
2 // lli-child-target command line tool6 name: "lli-child-target",
51 long long int lli; in test() local52 lli = INT_MIN << 2; // expected-warning {{shifting a negative signed value is undefined}} in test()53 lli = 1LL << (sizeof(long long) * CHAR_BIT - 2); in test()
1 lli - directly execute programs from LLVM bitcode7 :program:`lli` [*options*] [*filename*] [*program args*]12 :program:`lli` directly executes programs in LLVM bitcode format. It takes a program16 :program:`lli` is *not* an emulator. It will not execute IR of different architectures22 If `filename` is not specified, then :program:`lli` reads the LLVM bitcode for the46 Causes :program:`lli` to load the plugin (shared object) named *pluginfilename* and use61 Print out the version of :program:`lli` and exit without doing anything else.110 Causes :program:`lli` to enable optimizations that may decrease floating point115 Causes :program:`lli` to generate software floating point library calls instead of208 If :program:`lli` fails to load the program, it will exit with an exit code of 1.
42 Note that lli has to be passed the ``-use-mcjit`` flag to JIT the code with84 code via ``lli`` inside GDB:89 $ gdb --quiet --args $BINPATH/lli -use-mcjit showdebug.ll 590 Reading symbols from $BINPATH/lli...done.96 Starting program: $BINPATH/lli -use-mcjit showdebug.ll 5127 … argv=0x7fffffffe018, envp=0x7fffffffe040) at /home/ebenders_test/llvm_svn_rw/tools/lli/lli.cpp:324
4 ; RUN: %lli -jit-kind=orc-mcjit -extra-module=%p/Inputs/multi-module-b.ll -extra-module=%p/Inputs/m…10 ; RUN: %lli -jit-kind=orc-mcjit -extra-object=%t.cachedir2/multi-module-b.o -extra-object=%t.cached…17 ; RUN: %lli -jit-kind=orc-mcjit -extra-archive=%t.cachedir3/load-object.a %s
4 ; RUN: %lli -extra-module=%p/Inputs/multi-module-b.ll -extra-module=%p/Inputs/multi-module-c.ll -en…10 ; RUN: %lli -extra-object=%t.cachedir2/multi-module-b.o -extra-object=%t.cachedir2/multi-module-c.o…17 ; RUN: %lli -extra-archive=%t.cachedir3/load-object.a %s
1 ; RUN: %lli -remote-mcjit -mcjit-remote-process=lli-child-target%exeext %s > /dev/null
1 ; RUN: %lli -extra-module=%p/Inputs/cross-module-b.ll -disable-lazy-compilation=true -remote-mcjit …
1 …lli -extra-module=%p/Inputs/multi-module-b.ll -extra-module=%p/Inputs/multi-module-c.ll -disable-l…
1 ; RUN: %lli -remote-mcjit -O0 -mcjit-remote-process=lli-child-target%exeext %s
1 ; RUN: %lli -remote-mcjit -mcjit-remote-process=lli-child-target%exeext \
1 ; RUN: %lli -jit-kind=orc-mcjit -remote-mcjit -mcjit-remote-process=lli-child-target%exeext %s > /d…
1 ; RUN: %lli -jit-kind=orc-mcjit -extra-module=%p/Inputs/cross-module-b.ll -disable-lazy-compilation…
1 …lli -jit-kind=orc-mcjit -extra-module=%p/Inputs/multi-module-b.ll -extra-module=%p/Inputs/multi-mo…
1 ; RUN: %lli -jit-kind=orc-mcjit -remote-mcjit -O0 -mcjit-remote-process=lli-child-target%exeext %s
1 ; RUN: %lli -jit-kind=orc-mcjit -remote-mcjit -mcjit-remote-process=lli-child-target%exeext \