similar to: [LLVMdev] UNREACHABLE executed ! error

On 5/6/11 3:31 PM, pracheeyogi at cse.iitb.ac.in wrote: > Hi, > > On LLVM 2.8, on executing following command > ../install/bin/lli test.bc > > It gives following error > > "UNREACHABLE executed! > 0 lli 0x08699718 > Stack dump: > 0. Program arguments: ../install/bin/lli test.bc > 1. Running pass 'X86 Machine Code Emitter' on function

Hi Andy, > I am currently using llvm to compile memcache to get the bitcode. I simply > change all the "gcc -c" command to "clang -emit-llvm -c", and output ".o" to > ".bc". And all gcc link command to llvm-ld. By these means, I successfully get > the bitcode file, but when I run it using "lli", it fails with the error: > >

Hi, I am currently using llvm to compile memcache to get the bitcode. I simply change all the "gcc -c" command to "clang -emit-llvm -c", and output ".o" to ".bc". And all gcc link command to llvm-ld. By these means, I successfully get the bitcode file, but when I run it using "lli", it fails with the error: UNREACHABLE executed!0 lli

Dear Ciao, Duncan, Thank you for replying. I tried and the error goes away. But there comes a new error: LLVM ERROR: Unknown object format! How can I solve this problem? Thank you! BestAndy --- 12年9月18日，周二, Duncan Sands <baldrick at free.fr> 写道： 发件人: Duncan Sands <baldrick at free.fr> 主题: Re: [LLVMdev] Problems on getting UNREACHABLE executed 收件人: llvmdev at cs.uiuc.edu 日期:

Dear all The following process is about trying to do the " live migration at the same time with 5 Virtual machines ", but there is somthing problem with it. Process: yogi-pc2: # xm migrate --live vm01 pc2 & xm migrate --live vm02 pc2 & xm migrate --live vm03 pc2 & xm migrate --live vm04 pc2 & xm migrate --live vm05 pc2[1] 29983 [2] 29984 [3] 29985 [4]

Hi, Please tell how can I add a pass in the JIT (Just-in-time) compiler of LLVM? Thanks.

Hi Everyone, When I compile a program with clang with debug symbols enabled and I try to run it using the JIT (lli) I get the following error message. I am running on Lion (10.7.4). Thanks. George >> pseudo instructions should be removed before code emission UNREACHABLE executed at /Users/JD/Software/llvm3.1/llvm-3.1.src/lib/Target/X86/X86CodeEmitter.cpp:736! 0 lli

Hi there, I think I've found a bug in the x86 JIT. I get an assertion failure when using thread-local variables and the fast emitter. It only happens with the JIT, the fast emiiter and thread-locals. (The IR passes the verifier) Here's the failure: X86CodeEmitter.cpp:516: void<unnamed>::Emitter::emitInstruction(const llvm::MachineInstr&, const llvm::TargetInstrDesc*):

On Fri, Jul 8, 2011 at 9:30 AM, Karel Gardas <karel.gardas at centrum.cz> wrote: > On 07/ 8/11 05:26 PM, Eli Friedman wrote: >> >> Given that revision range, the only remotely likely culprit is 131463. >>  Which basically means that it "broke" because the default target >> features changed. > > And you are right here. 131463 == 131464 which is

On 07/ 8/11 05:26 PM, Eli Friedman wrote: > Given that revision range, the only remotely likely culprit is 131463. > Which basically means that it "broke" because the default target > features changed. And you are right here. 131463 == 131464 which is buggy. 131462 is OK. Thanks, Karel

hi, when using the execution engine (no matter, if JIT or Interpreter) i get the following assertion as soon as i use boost::shared_ptr: /build/buildd/llvm-2.5/lib/Target/X86/X86CodeEmitter.cpp:522: void<unnamed>::Emitter::emitInstruction(const llvm::MachineInstr&, const llvm::TargetInstrDesc*): Assertion `0 && "JIT does not support inline asm!\n"' failed.

Hi, I am new to R. I need help with regards to box cox transformation. I have phenotypic data for e.g. plant height. data is non-normal. Skewness is 0.34. Could you please help me? Regards, Yogi -- View this message in context: http://r.789695.n4.nabble.com/boxcox-transformations-tp4682077.html Sent from the R help mailing list archive at Nabble.com. [[alternative HTML version deleted]]

Is it possible to get llvm to generate native machine code without using gcc and friends ? Do I use lli ? I'd like to directly create executable code that i can stick in memory somewhere and jump into (call). (I'm looking to use llvm in a BSD licensed project). Simon. -- Simon Burton, B.Sc. Licensed PO Box 8066 ANU Canberra 2601 Australia Ph. 61 02 6249 6940 http://arrowtheory.com

Hi, I want to write a piece of code to instrument c++ programs. I have finished writing the pass, but I do not know how to get the resultant bitcode I ran OPT with the following arguments: opt -basiccg -basicaa -load /home/andy/llvm-3.0.src/Release/lib/InstTest.so -InstTest </home/andy/llvm-3.0.src/workspace/threadTest/Debug/threadTest.bc> -o=</home/andy/output/out.bc> /dev/null

Dear all I use the command( xm mem-set ID mem ) trying to understand the memory allocation between the Dom0 and the Guests(vm), but there is still some confusion about this. As the above /proc/xen/balloon list I set xm mem-set Domain-0 128 and changing the vm memory from 256 to 128: xm mem-set vm01 128 (...from vm01 to vm08) before mem-setCurrent allocation: 427792 kB

Hey, I have a situation where in I need to intercept a call to a particular function and return a pointer to a separate implementation of that function using JIT. The scenario is like this: 1. A test code or client code calls a function A() for which a dummy implementation is provided in a library which the test code/client links with during compilation. 2. I create the .bc using -emit-llvm and

Hi, I have a problem that was reported some time ago but never received any solution. See http://lists.cs.uiuc.edu/pipermail/llvmdev/2010-November/036113.html http://llvm.org/bugs/show_bug.cgi?id=6981 JIT emitter for X86 aborts when is asked to emit instruction for opcode 11 (DBG_VALUE). That opcode comes from @llvm.dbg.declare intrinsic function. Should this intrinsic be removed in some

Hi everyone, I compiled grep with llvm-3.4(because consumer tool uses llvm3.4 bit code) and generate bit-code for this. When I am running with lli output is pseudo instructions should be removed before code emission UNREACHABLE executed at /home/awanish/llvm/llvm-3.4.2/lib/Target/X86/X86CodeEmitter.cpp:1176! 0 libLLVM-3.4.so 0x00007f1250f655d5 llvm::sys::PrintStackTrace(_IO_FILE*) + 37 1

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.

On Thu, Jul 26, 2012 at 5:25 PM, Duncan Sands <baldrick at free.fr> wrote: > Hi Paweł, >> I have a problem that was reported some time ago but never received >> any solution. > > probably the reason that there is no action is surely that the old JIT > implementation is being replaced with the new MCJIT implementation, so > no-one feels very motivated to fix the old