similar to: [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

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

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

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

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 4:46 AM, Semion Prihodko wrote: > 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

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

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

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)

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,

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

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 didn't give any details at all! That's why I was only able to make a generic suggestion. Don't read too much into it. Ciao, Duncan. So > this is strange...

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.

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>

Hi, I have built a shared version of LLVM which I am now able to test in my Qt-based application. It all works fine on Windows, Linux and Mac OS X, except that whenever I exit my Qt-based application on Windows (everything is fine on Linux and Mac OS X), I get a message that reads that "this application has requested the Runtime to terminate it in an unusual way". 'My'

On Jun 17, 2009, at 9:46 AM, Paul Melis wrote: > FWIW, I'm also suddenly experiencing segfaults in code that used to > work > a few days ago (I'm using svn). This may be unrelated to the problem > described below, but perhaps it's the same thing. > > In my case it seems that creating an ExecutionEngine has changed. I > used > to do > > Module* Mod

> > Now, I may be wrong, but I was under the impression that a call to > > InitializeNativeTarget was recommended, if not compulsory, so. why > > commenting it out not only makes my LLVM code still work, but also > > prevent my application from generating the above error.?! > > My bet is that your code is writing through a stray pointer. By removing the > call to

Hello All, I'm building an F# binding for LLVM and it seems to be working for the parts of Core and BitWriter that I've tested but I've hit problems with Target/ExecutionEngine. The following test code works with the initializeNativeTarget line commented out like so: <https://github.com/keithshep/llvm-fs/blob/b7050b841108dc703e58563a4cff8845603c950d/test/simpletest2.fs> ...

What are the limitations on size of matrix for MDS functions? steve -- Steve Antos Priva-Technologies 847-640-9020 x3114 cell (540)409-1231 [[alternative HTML version deleted]]

Hi, Why are there so many undocumented (and as I far I can see) unnecessary API changes? Recently there has been: 1. For JIT applications, please include llvm/Target/TargetSelect.h and call the llvm::InitializeNativeTarget() function before creating an EE. 2. The major CHANGE is: the JIT will no longer be safe for executing threaded applications without first invoking

Hi Semion, > 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? build LLVM with assertions enabled. Then you may well get an assertion failure with a helpful error message rather than an obscure crash. Ciao, Duncan.