search for: movepctolroffset

Displaying 14 results from an estimated 14 matches for "movepctolroffset".

2010 Oct 18
4
[LLVMdev] PowerPC : Assertion `MovePCtoLROffset && "MovePCtoLR not seen yet?"' failed.
...g current SVN HEAD on Linux/x86. The tests are failing on PowerPC due to the following assertion failure : JITTests: PPCCodeEmitter.cpp:152: unsigned int<unnamed>::PPCCodeEmitter:: getMachineOpValue(const llvm::MachineInstr&, const llvm::MachineOperand&) const: Assertion `MovePCtoLROffset && "MovePCtoLR not seen yet?"' failed. Is anyone working on the PowerPC backend? Erik -- ---------------------------------------------------------------------- Erik de Castro Lopo http://www.mega-nerd.com/
2010 Oct 27
0
[LLVMdev] PowerPC : Assertion `MovePCtoLROffset &amp;&amp; &quot;MovePCtoLR not seen yet?&quot;' failed.
...ux/x86. The tests are failing > on PowerPC due to the following assertion failure : > > JITTests: PPCCodeEmitter.cpp:152: unsigned int<unnamed>::PPCCodeEmitter:: > getMachineOpValue(const llvm::MachineInstr&, const llvm::MachineOperand&) > const: Assertion `MovePCtoLROffset && "MovePCtoLR not seen yet?"' failed. > > Is anyone working on the PowerPC backend? > > Erik I'm seeing these same errors on powerpc-yellowdog-linux-gnu. Causes failures on some LLVM :: ExecutionEngine and LLVM-Unit :: ExecutionEngine/JIT/Release+Asserts/JI...
2010 Oct 30
0
[LLVMdev] PowerPC : Assertion `MovePCtoLROffset &amp;&amp; &quot;MovePCtoLR not seen yet?&quot;' failed.
...ux/x86. The tests are failing > on PowerPC due to the following assertion failure : > > JITTests: PPCCodeEmitter.cpp:152: unsigned int<unnamed>::PPCCodeEmitter:: > getMachineOpValue(const llvm::MachineInstr&, const llvm::MachineOperand&) > const: Assertion `MovePCtoLROffset && "MovePCtoLR not seen yet?"' failed. > > Is anyone working on the PowerPC backend? > > Erik I added build, host, target = ppc-unknown-linux-gnu and enabled libffi. One of hese gets rid of the assert errors. I'm guessing the B,H,T addition. Configure scrip...
2010 Oct 27
3
[LLVMdev] PowerPC : Assertion `MovePCtoLROffset &amp; &amp; &quot; MovePCtoLR not seen yet?&quot; ' failed.
...are failing >> on PowerPC due to the following assertion failure : >> >> JITTests: PPCCodeEmitter.cpp:152: unsigned int<unnamed>::PPCCodeEmitter:: >> getMachineOpValue(const llvm::MachineInstr&, const llvm::MachineOperand&) >> const: Assertion `MovePCtoLROffset && "MovePCtoLR not seen yet?"' failed. >> >> Is anyone working on the PowerPC backend? >> >> Erik > > I'm seeing these same errors on powerpc-yellowdog-linux-gnu. > Causes failures on some LLVM :: ExecutionEngine and LLVM-Unit :: > Ex...
2010 Oct 31
2
[LLVMdev] PowerPC : Assertion `MovePCtoLROffset &amp; &amp; &quot; MovePCtoLR not seen yet?&quot; ' failed.
D. Johnson wrote: > I added build, host, target = ppc-unknown-linux-gnu and enabled libffi. One of > hese gets rid of the assert errors. I'm guessing the B,H,T addition. Confirmed. Configuring with: ./configure --host=ppc-unknown-linux-gnu --build=ppc-unknown-linux-gnu \ --target=ppc-unknown-linux-gnu passed all tests. > Configure script guessed ppc64. I
2010 Nov 04
0
[LLVMdev] PowerPC : Assertion `MovePCtoLROffset &amp; &amp; &quot; MovePCtoLR not seen yet?&quot; ' failed.
On Sun, 31 Oct 2010 13:31:58 +1100 Erik de Castro Lopo <mle+cl at mega-nerd.com> wrote: > D. Johnson wrote: > > > I added build, host, target = ppc-unknown-linux-gnu and enabled > > libffi. One of hese gets rid of the assert errors. I'm guessing the > > B,H,T addition. > > Confirmed. Configuring with: > > ./configure
2010 Oct 28
0
[LLVMdev] PowerPC : Assertion `MovePCtoLROffset &amp; &amp; &quot; MovePCtoLR not seen yet?&quot; ' failed.
Dale Johannesen wrote: > I'm not working on it, but I might be able to help find the problem. > What this means is that you're generating code in PIC mode, and an > object that requires a PIC register to reference is being addressed, > and no PIC register was allocated. The allocation was supposed to > happen in PPCDAGtoDAGISel::Select when the reference was processed,
2011 Mar 25
0
[LLVMdev] Calling external functions failed on PowerPC
Hi, all I found the example code examples/HowToUseJIT.cpp also shows the same error. Attachment is the LLVM module created by HowToUseJIT. And here is the error, Running foo: %X4<def> = LDtoc <ga:@add1>, %X2 UNREACHABLE executed! Stack dump: 0. Running pass 'PowerPC Machine Code Emitter' on function '@foo' Aborted Currently, I use gdb try to track down
2011 Mar 23
4
[LLVMdev] Calling external functions failed on PowerPC
Hi, all I have a trouble with calling external functions on PowerPC. What I am doing is generating a LLVM IR first like this, - x86 call void @helper_shack_flush(%struct.CPUX86State* %62) noinline, !flags !12 - ppc call void @helper_shack_flush(%struct.CPUX86State* %62) noinline, !flags !10 After lowering above LLVM IR for x86 and ppc, it becomes: - x86 %RAX<def> = MOV64ri
2007 Dec 11
0
[LLVMdev] Exception handling in JIT
...tionModel() != Reloc::Default || > MF.getTarget().getRelocationModel() != Reloc::Static) && > "JIT relocation model must be set to static or default!"); > + > + MCE.setModuleInfo(&getAnalysis<MachineModuleInfo>()); > do { > MovePCtoLROffset = 0; > MCE.startFunction(MF); > @@ -101,6 +108,9 @@ > default: > MCE.emitWordBE(getBinaryCodeForInstr(*I)); > break; > + case TargetInstrInfo::LABEL: > + MCE.EmitLabel(MI.getOperand(0).getImm()); > + break; > case PPC::IMPLICIT_DE...
2007 Dec 12
3
[LLVMdev] Exception handling in JIT
...fault || >> MF.getTarget().getRelocationModel() != Reloc::Static) && >> "JIT relocation model must be set to static or default!"); >> + >> + MCE.setModuleInfo(&getAnalysis<MachineModuleInfo>()); >> do { >> MovePCtoLROffset = 0; >> MCE.startFunction(MF); >> @@ -101,6 +108,9 @@ >> default: >> MCE.emitWordBE(getBinaryCodeForInstr(*I)); >> break; >> + case TargetInstrInfo::LABEL: >> + MCE.EmitLabel(MI.getOperand(0).getImm()); >> + break;...
2007 Dec 10
2
[LLVMdev] Exception handling in JIT
Hi everyone, Here's a patch that enables exception handling when jitting. I've copy/pasted _many_code from lib/Codegen/DwarfWriter.cpp, so we may need to factorize it, but the functionality is there and I'm very happy with it :) lli should now be able to execute the output from llvm-gcc when using exceptions (the UnwindInst instruction is not involved in this patch). Just add the
2008 Feb 04
0
[LLVMdev] Exception handling in JIT
...locationModel() != Reloc::Default || > MF.getTarget().getRelocationModel() != Reloc::Static) && > "JIT relocation model must be set to static or default!"); > + > + MCE.setModuleInfo(&getAnalysis<MachineModuleInfo>()); > do { > MovePCtoLROffset = 0; > MCE.startFunction(MF); > @@ -101,6 +109,9 @@ > default: > MCE.emitWordBE(getBinaryCodeForInstr(*I)); > break; > + case TargetInstrInfo::LABEL: > + MCE.emitLabel(MI.getOperand(0).getImm()); > + break; > case PPC::IMPLICIT_DEF_GPR...
2008 Feb 01
2
[LLVMdev] Exception handling in JIT
Dear all, Here's a new patch with Evan's comments (thx Evan!) and some cleanups. Now the (duplicated) exception handling code is in a new file: lib/ExecutionEngine/JIT/JITDwarfEmitter. This patch should work on linux/x86 and linux/ppc (tested). Nicolas -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: jit-exceptions.patch URL: