search for: isalreadycodegenerating

...to output DWARF information for f(). -- James #0 0x00007ffff6ed84b5 in *__GI_raise (sig=<value optimised out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #1 0x00007ffff6edbf50 in *__GI_abort () at abort.c:92 #2 0x00007ffff6ed1481 in *__GI___assert_fail ( assertion=0x11acb18 "!isAlreadyCodeGenerating && \"Error: Recursive compilation detected!\"", file=<value optimised out>, line=624, function=0x11ad740 "void llvm::JIT::runJITOnFunctionUnlocked(llvm::Function*, const llvm::MutexGuard&)") at assert.c:81 #3 0x0000000000d3e2c2 in llvm::JIT::runJI...

...ed$ 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::getPointerToFunction(llvm::Function*) + 686 8 lli...

.../////////////////////////////////////#include "test.h" TestClass::TestClass() { fTotal = 2; } TestClass::~TestClass() { fTotal = 3; } int main() { TestClass short_name; return 0; } and I run: clang++ -c test.cpp -emit-llvm -o test.bc and lli test.bc, I get follow error: assert(!isAlreadyCodeGenerating && "Error: Recursive compilation detected!"); How can I fix it? Thank you. p.s I try on llvm 2.9/3.0/3.1 and they all get that error, by the way I compile llvm used VS2010 on win7. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.l...

Interesting. Was this the reason you were getting the recursive compilation error in JIT::runJITOnFunctionUnlocked(...) (isAlreadyCodeGenerating)? Do you have the time to try your test with 2.7? Garrison On Jan 22, 2010, at 17:37, James Williams wrote: > I've worked around this issue in my test case by simply calling my personality function on program to ensure it's JIT'ed before any unwind happens. > > -- James &g...

...ed to output DWARF information for f(). > > -- James > > [snip] > > On 22/01/2010, Garrison Venn <gvenn.cfe.dev at gmail.com> wrote: >> Interesting. Was this the reason you were getting the recursive compilation >> error in JIT::runJITOnFunctionUnlocked(...) (isAlreadyCodeGenerating)? >> Do you have the time to try your test with 2.7? >> >> Garrison >> [snip]

...robably 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::getPointerToFunction(ll...

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

I've worked around this issue in my test case by simply calling my personality function on program to ensure it's JIT'ed before any unwind happens. -- James 2010/1/22 Garrison Venn <gvenn.cfe.dev at gmail.com> > No, there is no magic. :-) > > To me though, the tools are magic, because I have no clue what they are > doing without looking at them and using them. >

...e 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::getPointerToFunction(llvm::Function*) + 686...

...c -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 0x00007fd4c168b210 4 libc.so.6 0x00007fd4...

...on the C files, I can generate a functioning executable. However, if I use llvm-gcc with -emit-llvm, then run lli on the resulting bitcode, I get the following error: lli: /x/jeffhao/llvm/llvm-2.4/lib/ExecutionEngine/JIT/JIT.cpp:467: void llvm::JIT::runJITOnFunction(llvm::Function*): Assertion `!isAlreadyCodeGenerating && "Error: Recursive compilation detected!"' failed. Anyone know how to fix this? Jeff

...on the C files, I can generate a functioning executable. However, if I use llvm-gcc with -emit-llvm, then run lli on the resulting bitcode, I get the following error: lli: /x/jeffhao/llvm/llvm-2.4/lib/ExecutionEngine/JIT/JIT.cpp:467: void llvm::JIT::runJITOnFunction(llvm::Function*): Assertion `! isAlreadyCodeGenerating && "Error: Recursive compilation detected!"' failed. Anyone know how to fix this? Jeff

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

Hello, As the title line says, I'm getting assertions on recursive JIT compiation, like this: opt: JIT.cpp:627: void llvm::JIT::runJITOnFunctionUnlocked(llvm::Function*, const llvm::MutexGuard&): Assertion `!isAlreadyCodeGenerating && "Error: Recursive compilation detected!"' failed. 0 libLLVM-2.7.so 0x012eb2c8 Stack dump: 0. Program arguments: opt -load=/home/gregory/thesis/llvm/Release/lib/LLVMmergebb.so -mergebb -stats bullet.linked.bc -o bullet.linked.bc.opt 1. Running pass 'Merge similar basic...

.../////////////////////////////////////// #include "test.h" TestClass::TestClass() { fTotal = 2; } TestClass::~TestClass() { fTotal = 3; } int main() { TestClass short_name; return 0; } and I run: clang++ -c test.cpp -emit-llvm -o test.bc and lli test.bc, I get follow error: assert(!isAlreadyCodeGenerating && "Error: Recursive compilation detected!"); How can I fix it? Thank you. p.s I try on llvm 2.9/3.0/3.1 and they all get that error, by the way I compile llvm used VS2010 on win7.

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

...igsegv_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 lli 0x08738aa4 llvm::JIT::runJITOn...

I just got the CVS version of LLVM running tonight. On my PowerBook, one of the examples (HowToUseJIT) has an assertion error when I try and run it: Running foo: JIT.cpp:217: failed assertion `!isAlreadyCodeGenerating && "Error: Recursive compilation detected!"' However, when I compile and run the same program on x86 Linux, it runs fine (Running foo: Result: 11). I can run the Fibonacci example, and I can execute simple C programs compiled with llvm-gcc. I couldn't see anythin...

...o (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 0x00000000...

Hi Olivier, Thanks for responding! I get to learn this way. On Feb 17, 2010, at 12:50, Olivier Meurant wrote: > Hi Garrison, > > I am not a specialist of the code but here is my 2 cents: > > - I like the idea that in lazy-mode the call (in module or not) is treated by a stub (like every calls). If we go further with this, I'll have to add test cases for lazy mode. I kind