On Friday 30 January 2009 04:11:04 Bill Hart wrote:
> For this one I'm going to take a wild stab and guess that the clztab
> is wrong when you specify --host=586 on an Athlon, or there's some
> issue with arithmetic shifts.
>

host=pentiummmx passes 
Do we still test on a real plain pentium? , if we dont then perhaps its really 
broken
Also tried i486 i686 pentium2 pentium3 k6 k62 pentium4 , just to see what 
happend

> It's not clear to me that this is a meaningful failure.
>
> If any of these machines fail without specifying a host different to
> the one you are running the tests on, then we should track the bugs
> down. Otherwise it is not clear to me that the tests aren't supposed
> to fail.
>

I agree , I was just trying to break things 


> Bill.
>
> 2009/1/30  <ja...@njkfrudils.plus.com>:
> > On Friday 30 January 2009 03:22:28 ja...@njkfrudils.plus.com wrote:
> >> On Friday 30 January 2009 03:13:25 ja...@njkfrudils.plus.com wrote:
> >> > On Thursday 29 January 2009 17:56:47 Bill Hart wrote:
> >> > > The fat binary support on x86_64 is now fixed.
> >> >
> >> > Nice one
> >> >
> >> > > I fixed the issue with fat binaries on x86_64 machines with ABI =
> >> > > 32. Hopefully this also fixes it for cygwin and mingw. But it takes
> >> > > over 1.5 hours to build under cygwin (make completes successfully),
> >> > > however I didn't get through make check because I forgot to build in
> >> > > a directory without spaces in the name (a known cygwin bug), so it
> >> > > crapped out.
> >> > >
> >> > > Thus, I want to delay dealing with any further issues for fat
> >> > > binaries on mingw32 or cygwin until a service release, MPIR 0.9.1.
> >> > >
> >> > > So can we try again for release? Anything broken for anyone?
> >> >
> >> > make distclean is still broken for --enable-fat  on x86_64
> >> > and --host=none on x86_64
> >> >
> >> > only really a problem when your testing for lots of different options
> >> >
> >> > just trying the same sort of thing on plain x86
> >> >
> >> > are we ment to use --host=chip-os-something  or --build=chip-something
> >> > ?
> >> >
> >> > Jason
> >> >
> >> > > Bill.
> >>
> >> on a athlon linux box
> >>
> >> ./configure --enable-cxx --enable-alloca=debug --enable-assert
> >> --host=i386 && make && make check
> >>
> >> fails with
> >>
> >> ake[4]: Entering directory `/root/mpir/mpir/trunk/tests/misc'
> >> PASS: t-printf
> >> PASS: t-scanf
> >> PASS: t-locale
> >> ==================
> >> All 3 tests passed
> >> ==================
> >> make[4]: Leaving directory `/root/mpir/mpir/trunk/tests/misc'
> >> make[3]: Leaving directory `/root/mpir/mpir/trunk/tests/misc'
> >> Making check in cxx
> >> make[3]: Entering directory `/root/mpir/mpir/trunk/tests/cxx'
> >> make  t-assign t-binary t-cast t-constr t-headers t-istream t-locale
> >> t-misc t-ops t-ostream t-prec t-rand t-ternary t-unary
> >> make[4]: Entering directory `/root/mpir/mpir/trunk/tests/cxx'
> >> /bin/sh ../../libtool --tag=CXX --mode=link
> >> g++  -m32 -O2 -fomit-frame-pointer -mtune=i386 -march=i386   -o t-assign
> >> t-assign.o -L../../.libs ../../tests/libtests.la ../../libgmpxx.la
> >> ../../libgmp.la g++ -m32 -O2 -fomit-frame-pointer -mtune=i386
> >> -march=i386 -o t-assign t-assign.o  -L/root/mpir/mpir/trunk/.libs
> >> ../../tests/.libs/libtests.a ../../.libs/libgmpxx.a
> >> /root/mpir/mpir/trunk/.libs/libgmp.a /usr/lib/libstdc++.so
> >> -L/usr/i486-slackware-linux/bin -L/usr/i486-slackware-linux/lib
> >> ../../.libs/libgmp.a t-assign.o: In function `check_mpq()':
> >> t-assign.cc:(.text+0xb69): undefined reference to
> >> `__sync_fetch_and_add_4' t-assign.cc:(.text+0xb80): undefined reference
> >> to `__sync_fetch_and_add_4' t-assign.cc:(.text+0xb97): undefined
> >> reference to `__sync_fetch_and_add_4' t-assign.cc:(.text+0xbae):
> >> undefined reference to `__sync_fetch_and_add_4'
> >> t-assign.cc:(.text+0xe18): undefined reference to
> >> `__sync_fetch_and_add_4' t-assign.o:t-assign.cc:(.text+0xec0): more
> >> undefined references to `__sync_fetch_and_add_4' follow
> >> collect2: ld returned 1 exit status
> >> make[4]: *** [t-assign] Error 1
> >> make[4]: Leaving directory `/root/mpir/mpir/trunk/tests/cxx'
> >> make[3]: *** [check-am] Error 2
> >> make[3]: Leaving directory `/root/mpir/mpir/trunk/tests/cxx'
> >> make[2]: *** [check-recursive] Error 1
> >> make[2]: Leaving directory `/root/mpir/mpir/trunk/tests'
> >> make[1]: *** [check-recursive] Error 1
> >> make[1]: Leaving directory `/root/mpir/mpir/trunk'
> >> make: *** [check] Error 2
> >>
> >> I suppose this is real failure , and not just me picking awkward
> >> configure options which no one in their right mind would use
> >>
> >>
> >> Jason
> >
> > Some more
> >
> > on a athlon linux box
> >
> > ./configure --enable-cxx --enable-alloca=debug --enable-assert
> > --host=i486 && make && make check
> > PASSES
> >
> > on a athlon linux box
> >
> > ./configure --enable-cxx --enable-alloca=debug --enable-assert
> > --host=i586 && make && make check
> > FAILS
> >
> > make[4]: Leaving directory `/root/mpir/mpir/trunk/tests'
> > make  check-TESTS
> > make[4]: Entering directory `/root/mpir/mpir/trunk/tests'
> > PASS: t-bswap
> > PASS: t-constants
> > t-count_zeros.c:33: GNU MP assertion failed: (n) != 0
> > /bin/sh: line 4: 15019 Aborted                 ${dir}$tst
> > FAIL: t-count_zeros
> > PASS: t-gmpmax
> > PASS: t-hightomask
> > PASS: t-modlinv
> > PASS: t-popc
> > PASS: t-parity
> > PASS: t-sub
> > =============================================================
> > 1 of 9 tests failed
> > Please report to http://groups.google.co.uk/group/mpir-devel/
> > =============================================================
> > make[4]: *** [check-TESTS] Error 1
> > make[4]: Leaving directory `/root/mpir/mpir/trunk/tests'
> > make[3]: *** [check-am] Error 2
> > make[3]: Leaving directory `/root/mpir/mpir/trunk/tests'
> > make[2]: *** [check-recursive] Error 1
> > make[2]: Leaving directory `/root/mpir/mpir/trunk/tests'
> > make[1]: *** [check-recursive] Error 1
> > make[1]: Leaving directory `/root/mpir/mpir/trunk'
> > make: *** [check] Error 2
>
> 


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"mpir-devel" group.
To post to this group, send email to mpir-devel@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
-~----------~----~----~----~------~----~------~--~---

Reply via email to