search for: movepctolr

Displaying 9 results from an estimated 9 matches for "movepctolr".

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
3
[LLVMdev] PowerPC : Assertion `MovePCtoLROffset &amp; &amp; &quot; MovePCtoLR not seen yet?&quot; ' failed.
...ind 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, and a MovePCtoLR instruction inserted at that time. Somebody can probably figure it out by stepping through that. On Oct 27, 2010, at 10:16 AMPDT, D. Johnson wrote: > Erik de Castro Lopo <mle+cl <at> mega-nerd.com> writes: > >> >> Hi all, >> >> I'm compiling curre...
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+Asse...
2010 Oct 28
0
[LLVMdev] PowerPC : Assertion `MovePCtoLROffset &amp; &amp; &quot; MovePCtoLR not seen yet?&quot; ' failed.
...at 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, > and a MovePCtoLR instruction inserted at that time. Somebody can > probably figure it out by stepping through that. I'm an LLVM user, not and LLVM dev. I've read the above and and get the basic idea, but I can't find PPCDAGtoDAGISel::Select anywhere in the sources. Erik -- ----------------------...
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...
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
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