search for: ababo

Displaying 13 results from an estimated 13 matches for "ababo".

Did you mean: abab
2011 Sep 03
1
[LLVMdev] LLVM: Cannot instantiate JIT execution engine
Isn't there someone to help me with this issue? I'm very upset about this stupid problem which wasted the whole day. BTW, I can create JIT from main.cpp, but not in the required source file (runtime.cpp), so this is not about linking. Very weird. 2011/9/2 Semion Prihodko <semion.ababo at gmail.com> > I cannot call the constructor explicitly, because ForceJITLinking is a name > of structure and of it's instance at the same time. But it called implicitly > when the instance above is being instantiated. > As I mentioned before I already tried to include this he...
2011 Sep 02
3
[LLVMdev] LLVM: Cannot instantiate JIT execution engine
Hi, guys. Have a strange problem with LLVM in my project ( https://github.com/ababo/AntOS). Cannot instantiate JIT execution engine (NULL returns; message: Interpreter has not been linked in.). As you can see from the code I call InitializeNativeTarget. Also I tried to directly include the "llvm/ExecutionEngine/JIT.h" header, but with no success. I link with `llvm-config...
2011 Sep 03
0
[LLVMdev] LLVM: Cannot instantiate JIT execution engine
I see two problems in your code 1) you need to #include "llvm/ExecutionEngine/JIT.h" 2) you must pass an empty string to EngineBuilder::setErrorStr. See JIT::createJIT for the reason. Jeff On Sat, Sep 3, 2011 at 8:33 AM, Semion Prihodko <semion.ababo at gmail.com> wrote: > Isn't there someone to help me with this issue? I'm very upset about this > stupid problem which wasted the whole day. BTW, I can create JIT from > main.cpp, but not in the required source file (runtime.cpp), so this is not > about linking. Very weird....
2011 Aug 26
2
[LLVMdev] Dynamically allocate and free variables in stack
Hi, guys. I have a beginner's question. The virtual machine I develop have instructions to dynamically allocate variable in stack and to free it (consistency of such instructions is checked before the actual jitting). To allocate memory in stack we have alloca IR instruction, but I didn't find any instruction to free it (such variables will be freed only when an enclosing function will
2011 Nov 02
1
[LLVMdev] [LLVMDev]: UNREACHABLE executed!
Hi, guys! I write a virtual machine which uses LLVM as back-end code generator. The following function code causes strange "UNREACHABLE executed!" error: define void @p1(%1*) { %2 = call i8* @llvm.stacksave() %3 = alloca %0 %4 = getelementptr %0* %3, i64 1 %5 = ptrtoint %0* %3 to i64 %6 = ptrtoint %0* %4 to i64 %7 = sub i64 %6, %5 %8 = bitcast %0* %3 to i8* call void
2011 Nov 09
2
[LLVMdev] LLVM: segfault while modifying a thread-local global variable
Hi, guys. Really strange situation: when I modify a thread-local GlobalVariable I get a segfault. It seems to be a bug, doesn't it? Can u suggest me some solution? Thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20111109/679b7808/attachment.html>
2011 Nov 09
1
[LLVMdev] LLVM: segfault while modifying a thread-local global variable
I use LLVM 2.9. By the way, I have another question. Is landingpad instruction is already implemented in JIT or I should use the old approach with llvm.eh instrinsics? Thanks. 2011/11/9 Eric Christopher <echristo at apple.com> > Which version of LLVM? At any rate I don't recall TLS working for the JIT. > It may take some work. > > -eric > > > On Nov 9, 2011, at
2011 Nov 07
0
[LLVMdev] LLVM: to catch 'unwind' instruction from calling C++ code
oops... so how can unwind stack up to invoke call? Is there an alternative to establish a custom exception handling? 2011/11/7 Duncan Sands <baldrick at free.fr> > >> Hi Semion, the unwind instruction has been removed from LLVM. Also, the >> JIT >> and code generators never supported it: it never unwound the stack, it >> just >> resulted in a nasty crash.
2011 Nov 16
1
[LLVMdev] LLVM: Cannot build LLVM 3.0 (from SVN) in Cygwin (GCC 3.4.4)
Hi, I got the following error output: llvm[1]: Compiling llvm-config.cpp for Debug+Asserts build llvm-config.cpp:46:35: LibraryDependencies.inc: No such file or directory llvm-config.cpp:56: error: `AvailableComponent' was not declared in this scope llvm-config.cpp:56: error: template argument 1 is invalid llvm-config.cpp:57: error: `AvailableComponent' was not declared in this scope
2011 Nov 09
2
[LLVMdev] LLVM: segfault while modifying a thread-local global variable
In my case the LLVM is built with assertions, but this doesn't help. From your answer I conclude that thread-local globals are fully implemented in x86 JIT. So this is strange... 2011/11/9 Duncan Sands <baldrick at free.fr> > Hi Semion, > > > Really strange situation: when I modify a thread-local GlobalVariable I > get a > > segfault. It seems to be a bug,
2011 Aug 19
1
[LLVMdev] LLVM: Very simple question
Hi, guys. I'm a newbie to LLVM and have a very simple question. Which instructions should I use (in terms of IRBuilder calls) to allocate an array of bytes in stack (alloca?), then to work with it (from a given offset) as with integer (bitcast?). I mean something like that: unsigned char var[8]; unsigned int offset = 3; int val = *(int*)(&var+offset); /* read */ *(int*)(&var+offset)
2011 Nov 06
3
[LLVMdev] LLVM: to catch 'unwind' instruction from calling C++ code
Hi! I have a little problem using LLVM and will be happy to get a solution. I need to handle in C++ code an uncaught unwind instruction while calling JIT (now I get segfault). I mean something like nonexistent ExecutionEngine::invokeFunction instead of callFunction. Setting llvm::JITExceptionHandling to true and enclosing the JIT-call within try/catch block does not help here, because there is no
2011 Nov 09
2
[LLVMdev] LLVM: segfault while modifying a thread-local global variable
OK, that's my fault. I'm running jitted code on linux x86. 2011/11/9 Duncan Sands <baldrick at free.fr> > Hi Semion, > > > In my case the LLVM is built with assertions, but this doesn't help. From >> your >> answer I conclude that thread-local globals are fully implemented in x86 >> JIT. >> > > you didn't mention the JIT. You