While build tests(`make check') on mips32-linux, there are serial failures such as: [snip] | mips-wrsmllib32-linux-gcc -meb -mabi=32 -mhard-float -c -o atomic_incs-atomic_incs.o `test -f 'atomic_incs.c' || echo '../../../valgrind-3.13.0/memcheck/tests/'`atomic_incs.c | /tmp/ccqrmINN.s: Assembler messages: | /tmp/ccqrmINN.s:247: Error: opcode not supported on this processor: mips1 (mips1) `ll $t3,0($t1)' | /tmp/ccqrmINN.s:249: Error: opcode not supported on this processor: mips1 (mips1) `sc $t3,0($t1)' [snip]
Created attachment 114163 [details] fix opcode not supported on mips32-linux Since the following commit applied, it defines CLFAGS for mips32, but missed to pass them to tests which caused the failure ... 3e344c57f Merge in a port for mips32-linux ...
Hi, Unfortunately, this kind of fix makes troubles in case of specific CFLAGS are passed. However, build whole Valgrind for the "mips1" isn't good idea at all. From `README.mips`: >> The build system expects that native GCC is configured correctly and optimized for the platform. Yet, this may not be the case with some Debian distributions which configure GCC to compile to "mips1" by default. Depending on a target platform, using CFLAGS="-mips32r2", CFLAGS="-mips32" or CFLAGS="-mips64" or CFLAGS="-mips64 -mabi=64" will do the trick and compile Valgrind correctly. << Please let us know if ./configure CFLAGS="-mips32" doesn't work for you. Regards, Aleksandar
Does Aleksandar's comment and suggestion work for you?
Changing status to NEEDSINFO.
Closing this as "WORKSFORME". Reopen this issue if you are still having problems.
I dropped Hongxu's patch in the Yocto/oe-core valgrind recipe that I'm updating and it works for me now too.