[ELDK] Recent valgrind on libc 2.6, ELDK 4.2 (ppc_4xx) ?

[Stefan Strobl]

Hi

I'm also having trouble compiling valgrind under ELDK-4.2.

When building valgrind-3.5.0 natively on MPC5200 it fails with:

Error: Unrecognized opcode: `stvx'

Error: Unrecognized opcode: `vspltisw'

Error: Unrecognized opcode: `mtvscr'

Error: Unrecognized opcode: `vspltisw'

Error: Unrecognized opcode: `vspltisw'

Error: Unrecognized opcode: `vsldoi'

Error: Unrecognized opcode: `mfvscr'

Error: Unrecognized opcode: `vand'

Error: Unrecognized opcode: `vspltw'

Error: Unrecognized opcode: `vcmpequw.'

Error: Unrecognized opcode: `lvx'


Any ideas what I'm doing wrong? Do I need newer binutils?
Did anyone succeed in building valgrind on 5200 with eldk-4.2?

Many thanks
Stefan.

Detlev Zundel wrote:
> Hi Charles,
> 
>> I found it impossible to compile a recent version of valgrind because
>> of unsupported/unrecognized assembler commands using the DENX ELDK
>> 4.2/ppc_4xx toolchain.
> 
> Can you give more details on why this fails?  I was under the impression
> that this should work pretty flawlessly, but I haven;t checked lately.
> 
>> A fellow coworker pointed me to
>> ftp://ftp.denx.de/pub/tmp/valgrind-2.4.1-ppc.tar.gz which compiles and
>> works (once you remove the glibc version check from the configure
>> script).  At this point, valgrind works on our target, but it keeps
>> reporting "Conditional jump or move depends on uninitialised value(s)"
>> error within libstdc++. Also, it doesn't seem to follow memory
>> allocation using the c++ 'new' operator.  I haven't gone more in depth
>> with that version, because it seems it wasn't made to work with glibc
>> 2.6 (the configure script checked for 2.1, 2.2, 2.3, or 2.4), and
>> because it's an old version of valgrind.
> 
> I agree.  You should concentrate on getting a recent version to work.
> So maybe if you show us more details on what fails, we can help.
> 
> Cheers
>   Detlev
>