On Fri, 2015-01-30 at 18:42 +0100, Andreas Cadhalpun wrote:
> Hi James,
> 
> On 30.01.2015 18:34, James Cowgill wrote:
> > On Fri, 2015-01-30 at 18:13 +0100, Andreas Cadhalpun wrote:
> >> However, I wonder if mipsdspr1, mipsdspr2 and mipsfpu really have to be
> >> disabled on mips64.
> >> Can you test, if it works with only disabling mips32r2?
> >
> > I'm about to go home now, I'll let you know how the build goes on
> > Monday.
> 
> OK, thanks.

It failed with:
> /tmp/ccAK6rnm.s: Assembler messages:
> /tmp/ccAK6rnm.s:15: Warning: the `dspr2' extension requires MIPS64 revision 2 
> or greater
> /tmp/ccAK6rnm.s:17316: Error: opcode not supported on this processor: mips64 
> (mips64) `ext $5,$2,4,4'
> /tmp/ccAK6rnm.s:17544: Error: opcode not supported on this processor: mips64 
> (mips64) `ext $6,$3,2,2'
> /tmp/ccAK6rnm.s:17545: Error: opcode not supported on this processor: mips64 
> (mips64) `ext $7,$3,4,2'
> /tmp/ccAK6rnm.s:17546: Error: opcode not supported on this processor: mips64 
> (mips64) `ext $17,$3,6,2'
> /tmp/ccAK6rnm.s:17556: Error: opcode not supported on this processor: mips64 
> (mips64) `ext $6,$3,12,1'
> /tmp/ccAK6rnm.s:17557: Error: opcode not supported on this processor: mips64 
> (mips64) `ext $7,$3,13,1'
> /tmp/ccAK6rnm.s:17558: Error: opcode not supported on this processor: mips64 
> (mips64) `ext $17,$3,14,1'
> /tmp/ccAK6rnm.s:17784: Error: opcode not supported on this processor: mips64 
> (mips64) `ext $5,$2,2,2'
> /tmp/ccAK6rnm.s:17785: Error: opcode not supported on this processor: mips64 
> (mips64) `ext $7,$2,4,2'
> /tmp/ccAK6rnm.s:17786: Error: opcode not supported on this processor: mips64 
> (mips64) `ext $8,$2,6,2'
> /tmp/ccAK6rnm.s:18028: Error: opcode not supported on this processor: mips64 
> (mips64) `ext $5,$4,4,4'
> common.mak:49: recipe for target 'libavcodec/aacdec.o' failed
> make[2]: *** [libavcodec/aacdec.o] Error 1

Which I find curious because ext is a mips(32|64)r2 instruction and I
thought I had just disabled those :)

> > Just off the top of my head (I haven't looked at the code), if
> > any of those features use assembly and do any pointer arithmetic they
> > might need a small amount of porting.
> 
> These features are about the assembler optimizations found in 
> libavcodec/mips/* and libavutil/mips/*. I don't know if they do any 
> pointer arithmetic, though.

Like Timothy said, yes they use some pointer arithmetic so they will
need porting to MIPS64.

Also since the Debian mips port is hard-float, you should be able to
enable the FPU instruction even on mips and mipsel (it fails at the
moment).

I can have a look at all this and submit some patches upstream when
they're ready (don't know how long it will take to do this though).

James


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to