On Thursday 27 May 2010 21:17:07 Bill Hart wrote:
> The gcc 4.3.2 test failures are all expected. Nothing we can do about
> that. That's a compiler bug. GMP and MPIR both simply won't build
> correctly with that version of gcc.
>
> Bill.
yes , but that has nothing to do with these failures?
[jasonmox...@cicero ~]$ gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/local/gcc-4.5.0/x86-Linux-pentium4-
fc/libexec/gcc/i686-pc-linux-gnu/4.5.0/lto-wrapper
Target: i686-pc-linux-gnu
Configured with: /usr/local/gcc-4.5.0/src/gcc-4.5.0/configure --enable-
languages=c,c++,fortran --with-gnu-as --with-
as=/usr/local/binutils-2.20.1/x86-Linux-pentium4-fc-gcc-4.4.3-rh/bin/as --
with-gnu-ld --with-ld=/usr/local/binutils-2.20.1/x86-Linux-pentium4-fc-
gcc-4.4.3-rh/bin/ld --with-gmp=/usr/local/mpir-1.2.2/x86-Linux-pentium4-
gcc-4.4.2 --with-mpfr=/usr/local/mpfr-2.4.2/x86-Linux-pentium4-fc-mpir-1.2.2-
gcc-4.4.2 --with-mpc=/usr/local/mpc-0.8.1/x86-Linux-pentium4-fc-mpfr-2.4.2-
mpir-1.2.2-gcc-4.4.3-rh --prefix=/usr/local/gcc-4.5.0/x86-Linux-pentium4-fc
Thread model: posix
gcc version 4.5.0 (GCC)
[jasonmox...@cicero ~]$
[jasonmox...@sextus ~]$ gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/local/gcc-4.5.0/x86_64-Linux-netburst-
fc/libexec/gcc/x86_64-unknown-linux-gnu/4.5.0/lto-wrapper
Target: x86_64-unknown-linux-gnu
Configured with: /usr/local/gcc-4.5.0/src/gcc-4.5.0/configure --enable-
languages=c,c++,fortran --with-gnu-as --with-gnu-
as=/usr/local/binutils-2.20.1/x86_64-Linux-netburst-gcc-4.4.3-rh/bin/as --
with-gnu-ld --with-ld=/usr/local/binutils-2.20.1/x86_64-Linux-netburst-
gcc-4.4.3-rh/bin/ld --with-gmp=/usr/local/mpir-1.2.2/x86_64-Linux-netburst-
gcc-4.4.3-rh --with-mpfr=/usr/local/mpfr-2.4.2/x86_64-Linux-netburst-
gcc-4.4.3-rh --with-mpc=/usr/local/mpc-0.8.1/x86_64-Linux-netburst-mpfr-2.4.2-
mpir-1.2.2-gcc-4.4.3-rh --prefix=/usr/local/gcc-4.5.0/x86_64-Linux-netburst-fc
Thread model: posix
gcc version 4.5.0 (GCC)
[jasonmox...@sextus ~]$
>
> On 27 May 2010 20:56, Jason Moxham <ja...@njkfrudils.plus.com> wrote:
> > This maybe related or not
> >
> > PASS: t-dc_bdiv_qr_n
> > PASS: t-dc_bdiv_qr
> > PASS: t-dc_bdiv_q
> > inv_divappr_q.c:45: GNU MP assertion failed: dn >= 6
> > /bin/sh: line 4: 24955 Aborted (core dumped) ${dir}$tst
> > FAIL: t-gcdext
> > PASS: st_fat
> > PASS: st_instrument
> > =============================================================
> > 1 of 48 tests failed
> > Please report to http://groups.google.co.uk/group/mpir-devel/
> > =============================================================
> > make[4]: *** [check-TESTS] Error 1
> > make[4]: Leaving directory `/tmp/mvngu/mpir-sandbox/test_stuff-
> > r2978/cicero/tests/mpn'
> > make[3]: *** [check-am] Error 2
> > make[3]: Leaving directory `/tmp/mvngu/mpir-sandbox/test_stuff-
> > r2978/cicero/tests/mpn'
> > make[2]: *** [check-recursive] Error 1
> > make[2]: Leaving directory `/tmp/mvngu/mpir-sandbox/test_stuff-
> > r2978/cicero/tests'
> > make[1]: *** [check-recursive] Error 1
> > make[1]: Leaving directory
> > `/tmp/mvngu/mpir-sandbox/test_stuff-r2978/cicero' make: *** [check] Error
> > 2
> > cicero
> >
> > PASSED CC=gcc CXX=g++ configure=
> > PASSED CC=gcc CXX=g++ configure= --enable-cxx --enable-gmpcompat
> > PASSED CC=gcc CXX=g++ configure= --enable-cxx --enable-gmpcompat
> > --enable- assert --enable-alloca=debug
> > PASSED CC=gcc CXX=g++ configure= --enable-cxx --enable-gmpcompat
> > --enable- assert --enable-alloca=debug --build=longlong-pc-linux-gnu
> > PASSED CC=gcc CXX=g++ configure= --enable-fat
> > PASSED CC=gcc CXX=g++ configure= --enable-fat --enable-cxx
> > --enable-gmpcompat FAILED CC=gcc CXX=g++ configure= --enable-fat
> > --enable-cxx --enable-gmpcompat --enable-assert --enable-alloca=debug
> >
> > At least it proves that try all possible combinations is worth something
> >
> > On Thursday 27 May 2010 20:16:26 Bill Hart wrote:
> >> I'll have to take a look. It is surely a bug in the test code. Though,
> >> given the absolutely enormous amount of testing I did with gcdext, I
> >> am finding it hard to believe that a segfault can still be in there.
> >> It must somehow have to do with the change we made the other day.
> >>
> >> Bill.
> >>
> >> On 27 May 2010 20:01, Jason Moxham <ja...@njkfrudils.plus.com> wrote:
> >> > our svn with the gcdext test changes still fail on sextus.skynet
> >> >
> >> > PASS: t-sb_bdiv_qr
> >> > PASS: t-dc_bdiv_q_n
> >> > PASS: t-dc_bdiv_qr_n
> >> > PASS: t-dc_bdiv_qr
> >> > PASS: t-dc_bdiv_q
> >> > /bin/sh: line 4: 18644 Segmentation fault ${dir}$tst
> >> > FAIL: t-gcdext
> >> > PASS: st_fat
> >> > PASS: st_instrument
> >> > =============================================================
> >> > 1 of 48 tests failed
> >> > Please report to http://groups.google.co.uk/group/mpir-devel/
> >> > =============================================================
> >> > make[4]: *** [check-TESTS] Error 1
> >> > make[4]: Leaving directory
> >> > `/home/jasonmoxham/mpir/trunk/sextus/tests/mpn' make[3]: ***
> >> > [check-am] Error 2
> >> > make[3]: Leaving directory
> >> > `/home/jasonmoxham/mpir/trunk/sextus/tests/mpn' make[2]: ***
> >> > [check-recursive] Error 1
> >> > make[2]: Leaving directory `/home/jasonmoxham/mpir/trunk/sextus/tests'
> >> > make[1]: *** [check-recursive] Error 1
> >> > make[1]: Leaving directory `/home/jasonmoxham/mpir/trunk/sextus'
> >> > make: *** [check] Error 2
> >> > [jasonmox...@sextus sextus]$ pwd
> >> > /home/jasonmoxham/mpir/trunk/sextus
> >> >
> >> > On Thursday 27 May 2010 19:58:36 Jason Moxham wrote:
> >> >> On Thursday 27 May 2010 16:04:38 Minh Nguyen wrote:
> >> >> > Hi folks,
> >> >> >
> >> >> > At this wiki page [1] is the build and test results on over 24
> >> >> > machines of various hardware/platform combinations. Unfortunately,
> >> >> > on about 8 of these machines, you find that MPIR r2978 builds fine,
> >> >> > make check passes, make tune completes successfully, and the test
> >> >> > suite pass. The other machines have some form of failure when
> >> >> > running make check, make tune, or the test suite. But overall, MPIR
> >> >> > r2978 builds OK on all the said machines so far with the usual
> >> >> > mantra:
> >> >> >
> >> >> > $ ./configure && make
> >> >> >
> >> >> > On FreeBSD 8.0, running the test suite mpirtest resulted in
> >> >> >
> >> >> > [mv...@gcc101 test_stuff]$ ./mpirtest ../mpir-r2978
> >> >> > bash: ./mpirtest: /bin/bash: bad interpreter: No such file or
> >> >> > directory
> >> >> >
> >> >> > This is because the header of mpirtest is
> >> >> >
> >> >> > #!/bin/bash
> >> >> >
> >> >> > This is unportable and can break on systems such FreeBSD. A more
> >> >> > portable header is to use the line
> >> >> >
> >> >> > #!/usr/bin/env bash
> >> >> >
> >> >> > And also to change the line
> >> >> >
> >> >> > SHE=/bin/bash
> >> >> >
> >> >> > to
> >> >> >
> >> >> > SHE=`which bash`
> >> >> >
> >> >> > If you agree, then I could make the change and commit it to the
> >> >> > test_stuff branch of SVN.
> >> >>
> >> >> Thanks , go ahead
> >> >>
> >> >> > [1] http://wiki.sagemath.org/mpir/BuildFarm/mpir-2.1.0
> >> >> >
> >> >> > --
> >> >> > Regards
> >> >> > Minh Van Nguyen
> >> >
> >> > --
> >> > You received this message because you are subscribed to the Google
> >> > Groups "mpir-devel" group. To post to this group, send email to
> >> > mpir-de...@googlegroups.com. To unsubscribe from this group, send
> >> > email to mpir-devel+unsubscr...@googlegroups.com. For more options,
> >> > visit this group at http://groups.google.com/group/mpir-devel?hl=en.
> >
> > --
> > You received this message because you are subscribed to the Google Groups
> > "mpir-devel" group. To post to this group, send email to
> > mpir-de...@googlegroups.com. To unsubscribe from this group, send email
> > to mpir-devel+unsubscr...@googlegroups.com. For more options, visit this
> > group at http://groups.google.com/group/mpir-devel?hl=en.
--
You received this message because you are subscribed to the Google Groups
"mpir-devel" group.
To post to this group, send email to mpir-de...@googlegroups.com.
To unsubscribe from this group, send email to
mpir-devel+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/mpir-devel?hl=en.
