search for: lly

...vm-dev < > llvm-dev at lists.llvm.org> wrote: > >> Hi all, >> as usual I'm playing with the Interpreter and unfortunately I hit a >> crash. I have narrowed down the problem an the crash happens inside the >> inflate function which is part of zlib and specifically at the instruction: >> >> store <2 x %struct.code*> <%struct.code* getelementptr inbounds ([512 x >> %struct.code], [512 x %struct.code]* @fixedtables.lenfix.681, i64 0, i64 >> 0), %struct.code* getelementptr inbounds ([32 x %struct.code], [32 x >> %struct.cod...

Hi,  I am trying to run a simple qt 5 application compiled to bitcode on OS X. I am getting the following error. I have modified lli to load qt libraries. When I use with option mcjit, I get the following error lli -use-mcjit -debug-ir bitcodetestqtapp Assertion failed: (Ty->isSized() && "Cannot getTypeInfo() on a type that is unsized!"), function getTypeSizeInBits, file

Hi all, as usual I'm playing with the Interpreter and unfortunately I hit a crash. I have narrowed down the problem an the crash happens inside the inflate function which is part of zlib and specifically at the instruction: store <2 x %struct.code*> <%struct.code* getelementptr inbounds ([512 x %struct.code], [512 x %struct.code]* @fixedtables.lenfix.681, i64 0, i64 0), %struct.code* getelementptr inbounds ([32 x %struct.code], [32 x %struct.code]* @fixedtables.distfix.682, i64 0, i64 0)&...

Hi Everyone, When I compile a program with clang with debug symbols enabled and I try to run it using the JIT (lli) I get the following error message. I am running on Lion (10.7.4). Thanks. George >> pseudo instructions should be removed before code emission UNREACHABLE executed at /Users/JD/Software/llvm3.1/llvm-3.1.src/lib/Target/X86/X86CodeEmitter.cpp:736! 0 lli

...org> wrote: >>> >>>> Hi all, >>>> as usual I'm playing with the Interpreter and unfortunately I hit a >>>> crash. I have narrowed down the problem an the crash happens inside the >>>> inflate function which is part of zlib and specifically at the instruction: >>>> >>>> store <2 x %struct.code*> <%struct.code* getelementptr inbounds ([512 x >>>> %struct.code], [512 x %struct.code]* @fixedtables.lenfix.681, i64 0, i64 >>>> 0), %struct.code* getelementptr inbounds ([32 x %struct.c...

Looks like a bug in the DebugIR pass. I imagine that without the -debug–ir flag, you will be able to get a little further. Nonetheless, can you send me the "bitcodetestqtapp" that you're running, or steps to reproduce? I'd love to take a look. Thanks, Dan From: Shailesh Kumar <shaileshkumar41 at yahoo.com<mailto:shaileshkumar41 at yahoo.com>> Reply-To: Shailesh

>>>>> I am using GCC 4.3.2 ( Debian 4.3.2-1.1) on x86. I will try out a different compiler. I tried out Sourcery G++ Lite 2009q1-203 (GCC 4.3.3). I still can't get lli to run. This time the error is like this: 0 lli 0x00651128 1 lli 0x00651960 2 libc.so.6 0x40212600 __default_sa_restorer_v1 + 0 3 lli 0x00282ef0 4 lli 0x00283cec

...>>>>> Hi all, >>>>>> as usual I'm playing with the Interpreter and unfortunately I hit a >>>>>> crash. I have narrowed down the problem an the crash happens inside the >>>>>> inflate function which is part of zlib and specifically at the instruction: >>>>>> >>>>>> store <2 x %struct.code*> <%struct.code* getelementptr inbounds ([512 >>>>>> x %struct.code], [512 x %struct.code]* @fixedtables.lenfix.681, i64 0, i64 >>>>>> 0), %struct.code* getelem...

Hi all, I am facing new problem with lli now. I am having a sample code in which I am doing malloc for two variables. If I compile the code with normal gcc the program runs without any warning of any sorts. If I compile the program to convert it into a bytecode file and then run it through lli it segfaults and the program aborts. This is the stack trace after execution. lli((anonymous

Hi, Is it possible to run Objective-C code in lli? lli does not seem to want to load Foundation.framework. Please see below. Thanks, Eric Brunstad #import <Foundation/Foundation.h> int main(int argc, char *argv[]) { NSAutoreleasePool *pool = [[NSAutoreleasePool alloc] init]; NSLog(@"test!"); [pool drain]; return EXIT_SUCCESS; } cmu-351714:llvm-2.5 ericbrunstad$

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

Hi all, I need to run c++ prgrams using lli. However, I find lli cannot handle the alias instruction correctly. Following is an example: ------------ example.cc ------------- #include <iostream> using namespace std; class cls { public: cls(); ~cls(); }; cls::cls() { cout << "constructor" << endl; }; cls::~cls() { cout <<

> > Hey Lang - does any of this look familiar to you? I'm afraid not: I know nothing about the interpreter. As far as I'm aware it's essentially abandonware. Alberto: The usual recommendation in these circumstances is to use a JIT class instead of the interpreter. You're using -force-interpreter though, so I assume you really want to use the interpreter for your use case? -- Lang. On Fri, Jan 3, 2020 at 3:04 PM David Blaikie <dbla...

...sa2, NULL); /* Set the timer to go off shortly */ if (setitimer(ITIMER_VIRTUAL, &timer, NULL) == -1) printf ("Failure!\n"); /* Send the SIGSEGV signal. This initiates JIT compilation of sigsegv_handler */ kill (getpid (), SIGSEGV); /* When the timer finally fires, assuming sigsegv_handler is still compiling, LLVM crashes */ for (;;); return 0; } ===================================== Compile the above program with: llvm-gcc -c -emit-llvm ./main.c -o main.bc And run it with: lli main.bc Here's the output from the debug version of the...

I've been using lli to do most of my unit tests for the compiler that I'm writing. However, when I get a test that crashes, its difficult to find which instruction it was that caused the crash. I tried running bugpoint, but it didn't seem to work for me, and upon reading the documentation, it seems to be intended for a different purpose than finding bugs in my source program; It

Hi,all I tried to run the generated whole-program bitcode of BIND,but I got some information: 0 lli 0x0000000000feda16 1 lli 0x0000000000fed88f 2 libpthread.so.0 0x0000003df340eee0 3 libc.so.6 0x0000003df28332f5 gsignal + 53 4 libc.so.6 0x0000003df2834b20 abort + 384 5 libc.so.6 0x0000003df282c2fa __assert_fail + 234 6 lli

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.

...n lli? lli does not seem to > want to load Foundation.framework. It is definitely possible, but we're not there yet. LLI would have to know about objective-c metadata to register it properly with the runtime. This is important for things like classes etc. This isn't conceptually hard, but noone has done it yet. -Chris > > Please see below. > > Thanks, > > Eric Brunstad > > #import <Foundation/Foundation.h> > > int main(int argc, char *argv[]) > { > NSAutoreleasePool *pool = [[NSAutoreleasePool alloc] init]; > NSLog(@"te...

Ping? Still looking for advice in figuring out how and why my generated code is causing lli to crash... Talin wrote: > I've been using lli to do most of my unit tests for the compiler that > I'm writing. However, when I get a test that crashes, its difficult to > find which instruction it was that caused the crash. I tried running > bugpoint, but it didn't seem to work

...;>>>>>>> as usual I'm playing with the Interpreter and unfortunately I hit >>>>>>>>> a crash. I have narrowed down the problem an the crash happens inside the >>>>>>>>> inflate function which is part of zlib and specifically at the instruction: >>>>>>>>> >>>>>>>>> store <2 x %struct.code*> <%struct.code* getelementptr inbounds >>>>>>>>> ([512 x %struct.code], [512 x %struct.code]* @fixedtables.lenfix.681, i64 >>>>>&...