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

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

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 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.

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...

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

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

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 --ldflags

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

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

Thank you very much. The code to initialize h1 to non-zero values was what I was looking for. It's almost working except for a type mismatch wrt dlist* llist field of h1. dlist static_lst[10] = { {1, 5, NULL}, ... }; dhash h1[10] = {{"myfile.txt", static_lst}, ... }; Along the lines of the code you had sent, I created a GlobalVariable* llist of type [10 x %struct.dlist]* for the

>The type you pass to GlobalVariable's constructor for that variable should be "[10 x %struct.dlist]" because that's what you want storage for. Then the GlobalVariable itself will be a Constant of type "[10 x %struct.dlist]*". Yes, I verified that this is the case. I enabled assertions and the error seems to occur while creating GlobalVariable for both struct dhash

GlobalVariable::copyAttributesFrom sets the target thread local mode to either general dynamic or not thread local rather than copying the thread local mode from the source. Is that intentional or an oversight? Thanks, Keno -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20140208/2686fdfa/attachment.html>

recently, i use LLVM API to write a program to read *.ll and excute it automatically. Further more, i want to change some global variables inside a module. i tried some functions provided by Module.h and ExecutionEngine.h but none were seemed to match my need. did someone have the experience or some advices? thank you ;) -- View this message in context:

On 05/12/12 12:07, Dong Chen wrote: > recently, i use LLVM API to write a program to read *.ll and excute it > automatically. > Further more, i want to change some global variables inside a module. > i tried some functions provided by Module.h and ExecutionEngine.h but none > were seemed to match my need. > did someone have the experience or some advices? > thank you ;) You

Hello everybody, I have a problem that is bothering me for quite a while now and I don't know the answer... I want to create global variables (out of a function) which I can access from all other functions... But somehow that does not work too well. Attached some code for an example: function_called <- function (){ result = globalvariable*globalvariable print(result) }

I am new to LLVM API. and I am experimenting with it. I want to create Global Variables in a module. I am able to create local variables using IRBuilder class. I tried using GlobalVariable class to create global variables. but it doesn't work. my code looks like this: Module* mod = new Module("test", getGlobalContext()); Constant* c = mod->getOrInsertFunction("main",

Can you guys tell how to recognize local & global variables ? Is there any macro on Value* defined in LLVM? -- regards, soumya prasad ukil -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20100721/cdc89d56/attachment.html>

Hi, I try to create a array that has a nonzero initialiser: What i do is, first create the array type. > const ArrayType *ATy = ArrayType::get(Type::Int32Ty, NumEdges); Then create some constant values for the initializer. > std::vector<Constant*> Initializer; Initializer.reserve(NumEdges); > APInt zero(32,0); Constant* zeroc = ConstantInt::get(zero); > APInt