search for: mutexguard

On Sat, 2005-08-27 at 11:47 -0700, Reid Spencer wrote: > Alkis Evlogimenos wrote: > > It seems that these two classes are the same... Maybe they should be > > merged into 1 class? > > > I think you're looking at something old. MutexLocker doesn't exist any more. llvm/Support/ThreadSupport.h is not generated anymore? -- Alkis

It seems that these two classes are the same... Maybe they should be merged into 1 class? -- Alkis

Alkis Evlogimenos wrote: > It seems that these two classes are the same... Maybe they should be > merged into 1 class? > I think you're looking at something old. MutexLocker doesn't exist any more. Reid.

...$ ./total __l_personality called$ Of course it is probably supposed to work from the JIT too (I don't know anything about the JIT), but it clearly doesn't: when I tried I got: lli: lib/ExecutionEngine/JIT/JIT.cpp:624: void llvm::JIT::runJITOnFunctionUnlocked(llvm::Function*, const llvm::MutexGuard&): Assertion `!isAlreadyCodeGenerating && "Error: Recursive compilation detected!"' failed. ... 6 lli 0x0000000000d3f5e2 llvm::JIT::runJITOnFunctionUnlocked(llvm::Function*, llvm::MutexGuard const&) + 62 7 lli 0x0000000000d3f9c6 llvm::JIT::getPointerTo...

...lang++ -emit-llvm -S example.cc -o example.S $ llvm-as example.S -o example.bc $ lli example.bc and get the "Recursive compilation" error output: lli: /home/dongpeng/Program/llvm/lib/ExecutionEngine/JIT/JIT.cpp:467: void llvm::JIT::runJITOnFunctionUnlocked(llvm::Function*, const llvm::MutexGuard&): Assertion `!isAlreadyCodeGenerating && "Error: Recursive compilation detected!"' failed. 0 lli 0x0000000001323d37 llvm::sys::PrintStackTrace(_IO_FILE*) + 38 1 lli 0x0000000001323fbe 2 lli 0x0000000001323a02 3 libpthread.so.0 0x000...

...mp;) + 445 11 lli 0x00000001034815d1 llvm::FunctionPassManagerImpl::run(llvm::Function&) + 129 12 lli 0x0000000103481542 llvm::FunctionPassManager::run(llvm::Function&) + 162 13 lli 0x0000000102ebb2cf llvm::JIT::jitTheFunction(llvm::Function*, llvm::MutexGuard const&) + 63 14 lli 0x0000000102ebb17a llvm::JIT::runJITOnFunctionUnlocked(llvm::Function*, llvm::MutexGuard const&) + 122 15 lli 0x0000000102ebb5b7 llvm::JIT::getPointerToFunction(llvm::Function*) + 695 16 lli 0x0000000102eb9bfb llvm::JIT::runFunct...

...tion&) + 427 11 lli 0x0000000001168777 llvm::FunctionPassManagerImpl::run(llvm::Function&) + 119 12 lli 0x00000000011686e7 llvm::FunctionPassManager::run(llvm::Function&) + 167 13 lli 0x0000000000ac478f llvm::JIT::jitTheFunction(llvm::Function*, llvm::MutexGuard const&) + 63 14 lli 0x0000000000ac467e llvm::JIT::runJITOnFunctionUnlocked(llvm::Function*, llvm::MutexGuard const&) + 94 15 lli 0x0000000000ac4a9e llvm::JIT::getPointerToFunction(llvm::Function*) + 734 16 lli 0x0000000000ad7e18 17 lli 0x00000...

...d$ > > Of course it is probably supposed to work from the JIT too (I don't know > anything about the JIT), but it clearly doesn't: when I tried I got: > > lli: lib/ExecutionEngine/JIT/JIT.cpp:624: void > llvm::JIT::runJITOnFunctionUnlocked(llvm::Function*, const > llvm::MutexGuard&): Assertion `!isAlreadyCodeGenerating && "Error: Recursive > compilation detected!"' failed. > ... > 6 lli 0x0000000000d3f5e2 > llvm::JIT::runJITOnFunctionUnlocked(llvm::Function*, llvm::MutexGuard > const&) + 62 > 7 lli 0x0000000000d3f...

...se it is probably supposed to work from the JIT too (I don't know >> anything about the JIT), but it clearly doesn't: when I tried I got: >> >> lli: lib/ExecutionEngine/JIT/JIT.cpp:624: void >> llvm::JIT::runJITOnFunctionUnlocked(llvm::Function*, const >> llvm::MutexGuard&): Assertion `!isAlreadyCodeGenerating && "Error: Recursive >> compilation detected!"' failed. >> ... >> 6 lli 0x0000000000d3f5e2 >> llvm::JIT::runJITOnFunctionUnlocked(llvm::Function*, llvm::MutexGuard >> const&) + 62 >> 7 l...

...ction&) + 424 8 libLLVM-2.8.so 0x0000003cc33307cb llvm::FunctionPassManagerImpl::run(llvm::Function&) + 91 9 libLLVM-2.8.so 0x0000003cc33309bd llvm::FunctionPassManager::run(llvm::Function&) + 173 10 libLLVM-2.8.so 0x0000003cc33e8647 llvm::JIT::jitTheFunction(llvm::Function*, llvm::MutexGuard const&) + 39 11 libLLVM-2.8.so 0x0000003cc33e8a2f llvm::JIT::runJITOnFunctionUnlocked(llvm::Function*, llvm::MutexGuard const&) + 15 12 libLLVM-2.8.so 0x0000003cc33e8cde llvm::JIT::getPointerToFunction(llvm::Function*) + 606 13 libLLVM-2.8.so 0x0000003cc33ea253 llvm::JIT::runFunction(llv...

...> llvm::FunctionPassManagerImpl::run(llvm::Function&) + 91 > > 9 libLLVM-2.8.so 0x0000003cc33309bd > > llvm::FunctionPassManager::run(llvm::Function&) + 173 > > 10 libLLVM-2.8.so 0x0000003cc33e8647 > > llvm::JIT::jitTheFunction(llvm::Function*, llvm::MutexGuard const&) + 39 > > 11 libLLVM-2.8.so 0x0000003cc33e8a2f > > llvm::JIT::runJITOnFunctionUnlocked(llvm::Function*, llvm::MutexGuard > > const&) + 15 > > 12 libLLVM-2.8.so 0x0000003cc33e8cde > > llvm::JIT::getPointerToFunction(llvm::Function*) + 606 >...

...ty called$ > > Of course it is probably supposed to work from the JIT too (I don't know > anything about the JIT), but it clearly doesn't: when I tried I got: > > lli: lib/ExecutionEngine/JIT/JIT.cpp:624: void llvm::JIT::runJITOnFunctionUnlocked(llvm::Function*, const llvm::MutexGuard&): Assertion `!isAlreadyCodeGenerating && "Error: Recursive compilation detected!"' failed. > ... > 6 lli 0x0000000000d3f5e2 llvm::JIT::runJITOnFunctionUnlocked(llvm::Function*, llvm::MutexGuard const&) + 62 > 7 lli 0x0000000000d3f9c6 llvm::JIT::...

...:FunctionPassManagerImpl::run(llvm::Function&) + 91 >>> 9 libLLVM-2.8.so 0x0000003cc33309bd >>> llvm::FunctionPassManager::run(llvm::Function&) + 173 >>> 10 libLLVM-2.8.so 0x0000003cc33e8647 >>> llvm::JIT::jitTheFunction(llvm::Function*, llvm::MutexGuard const&) + 39 >>> 11 libLLVM-2.8.so 0x0000003cc33e8a2f >>> llvm::JIT::runJITOnFunctionUnlocked(llvm::Function*, llvm::MutexGuard >>> const&) + 15 >>> 12 libLLVM-2.8.so 0x0000003cc33e8cde >>> llvm::JIT::getPointerToFunction(llvm::Function*...

...JIT compiler was working on sigsegv_handler before it attempted to start on timer_handler. ===================================== Recursive compilation: Function: timer_handler, existing function sigsegv_handler lli: JIT.cpp:579: void llvm::JIT::runJITOnFunctionUnlocked(llvm::Function*, const llvm::MutexGuard&): Assertion `!isAlreadyCodeGenerating && "Error: Recursive compilation detected!"' failed. 0 lli 0x08a5308e 1 lli 0x08a53601 2 0x008e0420 __kernel_sigreturn + 0 3 libc.so.6 0x00146ac1 abort + 257 4 libc.so.6 0x0013e39e __assert_fail + 238 5...

2010/1/22 Duncan Sands <baldrick at free.fr> > Hi James, > > > Yes - sorry I was unclear. I have pruned everything down to a pretty >> minimal test: >> - LLVM 2.6 compiled from source >> - A slightly modified version of Duncan's example ll assembly posted >> earlier >> - A minimal personality function (just a call to fprintf()) in a separate

...ling separate, unrelated code. I'm compiling using the JIT so I can execute the code as soon as it's compiled. How should I use LLVM? Should I create an ExecutionEngine for each thread, or only a single, global instance? I noticed that JIT::getPointerToFunction() contains: MutexGuard locked(lock); and it seems to hold the lock until the method returns. Does this mean that lazy compilation will be serialized? Would non-lazy compilation be any better? Can compilation be done in parallel by different threads? Thanks, Martin -------------- next part -------------- An H...

...ction&) + 424 8 libLLVM-2.8.so 0x0000003cc33307cb llvm::FunctionPassManagerImpl::run(llvm::Function&) + 91 9 libLLVM-2.8.so 0x0000003cc33309bd llvm::FunctionPassManager::run(llvm::Function&) + 173 10 libLLVM-2.8.so 0x0000003cc33e8647 llvm::JIT::jitTheFunction(llvm::Function*, llvm::MutexGuard const&) + 39 11 libLLVM-2.8.so 0x0000003cc33e8a2f llvm::JIT::runJITOnFunctionUnlocked(llvm::Function*, llvm::MutexGuard const&) + 15 12 libLLVM-2.8.so 0x0000003cc33e8cde llvm::JIT::getPointerToFunction(llvm::Function*) + 606 13 libLLVM-2.8.so 0x0000003cc33ea253 llvm::JIT::runFunction(llv...

Hi Chia Lun Liu, > The reason why I take such indirect method is that as I know, JIT is not > able to > > do with LLVM GlobalVariable with ThreadLocal type. did you try mcjit? Run lli with -use-mcjit Ciao, Duncan.

...VM-3.4.so 0x00007f1250a464fe llvm::legacy::FunctionPassManagerImpl::run(llvm::Function&) + 238 11 libLLVM-3.4.so 0x00007f1250a4639d llvm::legacy::FunctionPassManager::run(llvm::Function&) + 93 12 libLLVM-3.4.so 0x00007f1250bca1dd llvm::JIT::runJITOnFunctionUnlocked(llvm::Function*, llvm::MutexGuard const&) + 45 13 libLLVM-3.4.so 0x00007f1250bca435 llvm::JIT::getPointerToFunction(llvm::Function*) + 261 14 lli 0x0000000000409f95 main + 4437 15 libc.so.6 0x00007f124effcf45 __libc_start_main + 245 16 lli 0x00000000004069bd Stack dump: 0. Program arguments: ll...

Hi James, > Yes - sorry I was unclear. I have pruned everything down to a pretty > minimal test: > - LLVM 2.6 compiled from source > - A slightly modified version of Duncan's example ll assembly posted earlier > - A minimal personality function (just a call to fprintf()) in a > separate C file compiled with gcc-llvm > - A single C++ function in a third file that simply