Displaying 20 results from an estimated 10000 matches similar to: "[LLVMdev] User-specified JIT passes"
2007 Oct 29
0
[LLVMdev] User-specified JIT passes
On Oct 28, 2007, at 10:38 PM, Warren Armstrong wrote:
> Greetings,
>
> I have a plan to use LLVM to undertake runtime optimisation of
> computational chemistry programs.
Ok.
> As part of this, I'd like to be able
> to invoke lli and pass it a list of passes to run, in the manner of
> opt. For example:
>
>> lli -load=llvm/mem_trace_pass/bin/lib/hello.so -hello
2008 Oct 16
2
[LLVMdev] Requiring a pass to run before/after a pass? (Adding PHIs and updating uses)
Is there a simple way to require a pass, e.g., Reg2Mem/Mem2Reg, to run
before/after my transformation pass? Or do I do something like:
struct myOpt {
myOpt() {
mBefore = createDemoteRegisterToMemoryPass();
mAfter = createPromoteMemoryToRegisterPass();
}
getAnalysisUsage(AU) {
AU.addRequired(my stuff);
mBefore.getAnalysisUsage(AU);
mAfter.getAnalysisUsage(AU);
}
2006 May 18
1
[LLVMdev] Runtime optimisation in the JIT
Hi All,
I've just started investigating LLVM for use in a project of mine,
and I've got a couple of questions:
1. How does LLVM support run-time optimisation - i.e: which
elements of the toolchain will optimise a running bytecode / binary?
2. Is there a way, with the existing infrastructure, to do adaptive
compilation using the JIT interpreter?
Watching said interpreter through GDB
2013 Oct 06
1
[LLVMdev] Resolving a function symbol using JIT.
Hey,
I have a situation where in I need to intercept a call to a particular
function and return a pointer to a separate implementation of that function
using JIT. The scenario is like this:
1. A test code or client code calls a function A() for which a dummy
implementation is provided in a library which the test code/client links
with during compilation.
2. I create the .bc using -emit-llvm and
2009 Jun 22
0
[LLVMdev] X86 JIT
On Jun 22, 2009, at 2:19 PM, Kasra wrote:
> Hi,
>
> for some reason I could not get the machine code generator for x86
> working. The interpreter is the only thing that works, is there
> anything that I am missing here?
This recently changed. In your main program, please #include "llvm/
Target/TargetSelect.h" and call InitializeNativeTarget(); before
setting up
2009 Jun 22
2
[LLVMdev] X86 JIT
Hi,
for some reason I could not get the machine code generator for x86 working. The interpreter is the only thing that works, is there anything that I am missing here?
-- Kasra
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20090622/89dca208/attachment.html>
2009 Dec 31
3
[LLVMdev] How does JIT/lli work with bc file?
Dear all,
I hope you enjoy your christmas! Recently I started to play lli with
bc. I found that the lli only calls the main() function in bc file and then
does nothing before the main() function returns, which means that the
JIT::runFunction() function is involved only once with the main() function
in bc file. If this was true, then lli does not have any control
to the execution of program.
2009 Dec 31
0
[LLVMdev] How does JIT/lli work with bc file?
On Wed, Dec 30, 2009 at 7:53 PM, Heming Cui <heming at cs.columbia.edu> wrote:
> Dear all,
> I hope you enjoy your christmas! Recently I started to play lli with
> bc. I found that the lli only calls the main() function in bc file and then
> does nothing before the main() function returns, which means that the
> JIT::runFunction() function is involved only once with the
2012 May 07
2
[LLVMdev] JIT support for inline asm on Linux
On 5/7/2012 12:21 AM, Bendersky, Eli wrote:
<snip>
>
> MCJIT is functional in trunk (and the 3.1 branch). While it doesn't include all the features of the old JIT quite yet, it's complete enough to pass all of JIT's execution tests on Linux and Mac OS X (no Windows yet). As for directions on how to enable it, follow the path of the "use-mcjit" flag passed to lli
2010 Apr 29
3
[LLVMdev] Why the same code is much slower in JIT compared to separate executable?
Török Edwin wrote:
> Are you using 2.6 or 2.7, 32-bit or 64-bit?
>
I use 2.7 on i386. lli has debug asserts enabled, but I guess this
shouldn't matter for JIT code speed.
jit: 11.32 real
exe: 7.64 user
Both have -O3 option. Speed should be the same.
Yuri
2012 Apr 29
1
[LLVMdev] Running LLVM JIT on qemu-system-arm
Hi all,
I'm struggling to get lli work on qemu-system-arm. I already boot the system
with a debian squeeze rootfs which contains a statically cross-compiled lli
for armel. When I run ./lli hello.bc, I got the following error msg:
./lli: error creating EE: /lib/: cannot read file data: Is a directory
afaik, this error is related to lli using dlopen() with a NULL path to
resolve symbols for
2012 May 07
2
[LLVMdev] JIT support for inline asm on Linux
Hi,
I'm using LLVM/clang from release 3.0. I have a program (C++) that
will load a library in the form of LLVM bit code using the JIT. However,
I see JIT errors when loading the bit code:
"LLVM ERROR: JIT does not support inline asm"
I read that MC JIT intends to fix this. I'm trying to build LLVM from
the lastest trunk. Is there any special/extra thing to do to use
2017 Aug 24
2
JIT Optimization Levels
Hello,
there are several optimization levels in lli like O0, O1, O2, O3. What does
they mean? how the run time optimization is performed in LLVM JIT?
I am working on a project where my goal is to study the impact of lli
optimizations. here my IR is already optimized through opt. now i have to
perform lli optimizations provided i am giving varying inputs at run time.
so i suppose here my
2012 May 07
0
[LLVMdev] JIT support for inline asm on Linux
> Hi,
> I'm using LLVM/clang from release 3.0. I have a program (C++) that will load
> a library in the form of LLVM bit code using the JIT. However, I see JIT errors
> when loading the bit code:
>
> "LLVM ERROR: JIT does not support inline asm"
>
> I read that MC JIT intends to fix this. I'm trying to build LLVM from the
> lastest trunk. Is
2009 Jun 23
3
[LLVMdev] X86 JIT
On Mon, Jun 22, 2009 at 4:43 PM, Chris Lattner <clattner at apple.com>
wrote:
>
> On Jun 22, 2009, at 2:19 PM, Kasra wrote:
>
> Hi,
>
> for some reason I could not get the machine code generator for x86
> working. The interpreter is the only thing that works, is there
> anything that I am missing here?
>
> This recently changed. In your main program, please
2010 Aug 10
4
[LLVMdev] sqlite3 crashing jit
On Tue, Aug 10, 2010 at 1:35 PM, Eric Christopher <echristo at apple.com> wrote:
>
> On Aug 10, 2010, at 1:30 PM, Bueno, Denis wrote:
>
>> Running lli under gdb gives
>>
>> Program received signal SIGSEGV, Segmentation fault.
>> [address] in ?? ()
>> (gdb) bt
>> #0 [address] in ?? ()
>> Cannot access memory at address [address2]
>>
2011 Nov 10
3
optim seems to be finding a local minimum
Hello!
I am trying to create an R optimization routine for a task that's
currently being done using Excel (lots of tables, formulas, and
Solver).
However, otpim seems to be finding a local minimum.
Example data, functions, and comparison with the solution found in
Excel are below.
I am not experienced in optimizations so thanks a lot for your advice!
Dimitri
### 2 Inputs:
2012 May 08
0
[LLVMdev] JIT support for inline asm on Linux
> On 5/7/2012 12:21 AM, Bendersky, Eli wrote:
> <snip>
> >
> > MCJIT is functional in trunk (and the 3.1 branch). While it doesn't include all
> the features of the old JIT quite yet, it's complete enough to pass all of JIT's
> execution tests on Linux and Mac OS X (no Windows yet). As for directions
> on how to enable it, follow the path of the
2009 Aug 09
3
[LLVMdev] Signals: interpreter vs. JIT
Just a quick question on LLVM, signals, and the lli interpreter. A sample
program is included at the end. Platform is x86, Linux, 32-bit, GCC 4.2.4.
Does lli -force-interpreter support signals, or is it only the JIT that
does? The following sample program crashes with lli 2.5 and lli
top-of-tree.
Thanks and regards,
Matt
=============================
#include <stdio.h>
#include
2012 May 08
2
[LLVMdev] JIT support for inline asm on Linux
On 5/7/2012 10:17 PM, Bendersky, Eli wrote:
<snip>
>>> $lli -entry-function="ISimEngine_GetVersion" -use-mcjit libengine.bc
>>> LLVM ERROR: Inline asm not supported by this streamer because we don't
>>> have an asm parser for this target
>>
>> I also tried other variations of the call with the same result:
>>> $lli