[Bug target/42920] gcc does not produce necessary vec_lvrx instructions

[ryan dot sammartino at gmail dot com]

------- Comment #5 from ryan dot sammartino at gmail dot com  2010-02-01 00:12 -------
(In reply to comment #4)
> Actually can you paste the output of ppu-g++?  

You mean -v, I hope:

$ ppu-g++ --v
Using built-in specs.
Target: ppu
Configured with: ../toolchain/gcc/configure --prefix=/usr/lib/cell/toolchain
--libexecdir=/usr/lib/cell/toolchain/lib --mandir=/usr/lib/cell/toolchain/man
--infodir=/usr/lib/cell/toolchain/info --with-sysroot=/usr/lib/cell/sysroot
--with-as=/usr/bin/ppu-as --with-ld=/usr/bin/ppu-ld --enable-threads
--disable-checking --with-system-zlib --enable-__cxa_atexit
--disable-libunwind-exceptions --enable-languages=c,c++,fortran --disable-nls
--enable-version-specific-runtime-libs --with-long-double-128
--disable-bootstrap --program-prefix=ppu- --build=x86_64-linux-gnu
--host=x86_64-linux-gnu --target=ppu
Thread model: posix
gcc version 4.1.1

This is the latest available in Ubuntu repos (4.1.1r840-0ubuntu7).

> I think this has been fixed on
> the trunk already.  Also can you try 4.4 which has Cell support in it, though I
> cannot remember when I submitted the Cell Altivec support.  It might be only
> included on the trunk.
> 

I'll try, but I'm getting to be a very lazy Linux user... if it ain't in Ubuntu
repos anymore, I can't remember how to build these things. :)

> I fixed at least a bug like this in the PS3 GCC based toolchain and made sure
> that the fix made it into the FSF when I submitted the Cell Altivec support. 

No, this is different.  I think I know the bug you're talking about and in that
case it was a problem with using something like &array[1] producing extra
splats.  In that case the fix was to use array+1 ... it doesn't fix it in this
case.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42920