|
From: Cerion Armour-B. <ce...@op...> - 2006-01-10 00:10:28
|
On Monday 09 January 2006 22:20, Uttam Pawar wrote: > Hi, > > I'm new to the valgrind community. I recently did a > complete build of valgrind-3.1.0 release on a Power5 machine. After doing > make regtest I found total of 21 tests failure. These may be known or not, > but I just wanted to report them to the mailing list anyway. > > 1) Results on power5 platform, > == 174 tests, 18 stderr failures, 3 stdout failures > ================= > memcheck/tests/badjump (stderr) > memcheck/tests/badjump2 (stderr) > memcheck/tests/leak-cycle (stderr) > memcheck/tests/leak-tree (stderr) > memcheck/tests/mempool (stderr) > memcheck/tests/partiallydefinedeq (stderr) > memcheck/tests/pointer-trace (stderr) > memcheck/tests/supp1 (stderr) > memcheck/tests/supp_unknown (stderr) > memcheck/tests/toobig-allocs (stderr) > memcheck/tests/xml1 (stderr) > massif/tests/toobig-allocs (stderr) > none/tests/faultstatus (stderr) > none/tests/fdleak_cmsg (stderr) > none/tests/mremap (stderr) > none/tests/ppc32/jm-insns (stdout) > none/tests/ppc32/jm-insns (stderr) > none/tests/ppc32/jm-vmx (stdout) > none/tests/ppc32/jm-vmx (stderr) > none/tests/ppc32/testVMX (stdout) > none/tests/ppc32/testVMX (stderr) > > make: *** [regtest] Error 1 > > Enviornment: > Hardware: Power5 (with 8 8 processors) > OS: Linux elm3b149 2.6.5-7.97-pseries64.nm #1 SMP Thu Mar > 31 10:55:11 PST 2005 ppc64 ppc64 ppc64 GNU/Linux (SLES9) GCC: gcc -v > Reading specs > from /usr/lib/gcc-lib/powerpc-suse-linux/3.3.3/specs > Configured with: ../configure --enable-threads=posix > --prefix=/usr > --with-local-prefix=/usr/local --infodir=/usr/share/info > --mandir=/usr/share/man --enable-languages=c,c > ++,f77,objc,java,ada > --disable-checking --libdir=/usr/lib --enable-libgcj > --with-gxx-include-dir=/usr/include/g++ --with-slibdir=/lib > --with-system-zlib --enable-shared --enable-__cxa_atexit > --host=powerpc-suse-linux --build=powerpc-suse-linux > --target=powerpc-suse-linux > --enable-targets=powerpc64-suse-linux > --enable-biarch > Thread model: posix > gcc version 3.3.3 (SuSE Linux) > > > > 2) Results on power4 platform, > > == 174 tests, 23 stderr failures, 4 stdout failures > ================= > memcheck/tests/badjump (stderr) > memcheck/tests/badjump2 (stderr) > memcheck/tests/leak-cycle (stderr) > memcheck/tests/leak-tree (stderr) > memcheck/tests/mempool (stderr) > memcheck/tests/partiallydefinedeq (stderr) > memcheck/tests/pointer-trace (stderr) > memcheck/tests/stack_switch (stderr) > memcheck/tests/supp1 (stderr) > memcheck/tests/supp_unknown (stderr) > memcheck/tests/toobig-allocs (stderr) > memcheck/tests/xml1 (stderr) > massif/tests/toobig-allocs (stderr) > none/tests/faultstatus (stderr) > none/tests/fdleak_cmsg (stderr) > none/tests/mremap (stderr) > none/tests/ppc32/jm-insns (stdout) > none/tests/ppc32/jm-insns (stderr) > none/tests/ppc32/jm-vmx (stdout) > none/tests/ppc32/jm-vmx (stderr) > none/tests/ppc32/testVMX (stdout) > none/tests/ppc32/testVMX (stderr) > none/tests/shell (stdout) > none/tests/shell (stderr) > none/tests/shell_valid1 (stderr) > none/tests/shell_valid2 (stderr) > none/tests/shell_valid3 (stderr) > > make: *** [regtest] Error 1 > > Enviornment: > Hardware: Power4+ (with 4 processors) > OS: Linux elm3b11 2.4.21-17.EL #1 SMP Thu Jul 8 19:31:00 > EDT 2004 ppc64 ppc64 ppc64 GNU/Linux (RHEL3) > GCC: gcc -v > Reading specs > from /usr/lib/gcc-lib/ppc64-redhat-linux/3.2.3/specs > Configured with: ../configure --prefix=/usr > --mandir=/usr/share/man --infodir=/usr/share/info > --enable-shared --enable-threads=posix --disable-checking > --with-system-zlib --enable-__cxa_atexit > --host=ppc64-redhat-linux --build=ppc64-redhat-linux > --target=ppc64-redhat-linux --with-cpu=default32 > Thread model: posix > gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-52) > > > Please let me know if I'm missing some piece of information > to mention in this email. > > Also, let me know (which somebody will) if this is not the > right forum for this kind of information/questions. You've got the right place, and it's great you're testing, but as J asked in reply to yr last post (i guess yr not subscribed): On Friday 06 January 2006 22:42, Julian Seward wrote: > Thanks. Most of these are harmless - they happen on a PPC970 box > too. We should improve our regression test mechanism so it only > reports a failure when there really is one, but that's not as simple > as it sounds. > > > none/tests/ppc32/jm-vmx (stdout) > > none/tests/ppc32/jm-vmx (stderr) > > none/tests/ppc32/testVMX (stdout) > > none/tests/ppc32/testVMX (stderr) > > These are VMX (Altivec) tests. I presume they failed because POWER5 > doesn't support Altivec (right?) > > > none/tests/ppc32/jm-insns (stdout) > > none/tests/ppc32/jm-insns (stderr) > > These should not fail -- tests of the basic integer instruction set. > Can you send > > none/tests/ppc32/jm-insns.stdout.diff and > none/tests/ppc32/jm-insns.stderr.diff > > so we can see why they failed. > > J |