I can confirm that t-get_ux passes on an Itanium with a working
compiler. So it is definitely not an MPIR bug, as Jason found.

We also had failures on a solaris machine and gcc70 for the same test.

Bill.

On 19 July 2012 20:27, Bill Hart <goodwillh...@googlemail.com> wrote:
> Hi all,
>
> we are currently working on the MPIR 2.6 release. The main new features are:
>
> * new Windows 64 functionality (due to Brian Gladman)
> * new FFT (due to William Hart)
>
> The code has been developed on a separate branch, mpir-exp
> (http://boxen.math.washington.edu/svn/mpir/mpir/branches/mpir-exp in
> svn repo).
>
> Here is the remaining list of things to do:
>
> * tuneup fails on mpir-exp branch
> * generic build option for sage
> * mpir build fails on MinGW due to mpn_addmul_2 symbol defined twice Pavel
> * Vlad report of MinGW sandybridge combination with FFT assert failure
> * Chris report of mpz_get_ux failure on Itanium
> * mpz_powm_ui doc says -ve exponent supported, which is rubbish
> * fix flint bugs in primality testing code
> * 32 and 64 bit tuning for fft
> * make sure the redc_2 include bug is fixed in trunk
> * set up autotools to recognize new mpn/generic/mulmod_bexpp1.c file
>
> Regarding the last item, Jason, would you be able to do the autoconf
> stuff for this. My autotools is out-of-date and our system won't allow
> us to install a more recent version (autotools fanboys observe --
> autotools sucks once again).
>
> Regarding the mpz_get_ux bug on Itanium, this fails on many
> architectures, due to a common gcc bug. Jason wanted to set up a test
> to reject all such broken compilers, but the test has to be run after
> the test for stdint.h which isn't possible. So it is not possible to
> reject such compilers. Which is probably just as well, as they are
> extremely common. So we will just have to stick with the failing test.
> Nothing we can do about it apparently. We'll add it to the long list
> of known issues about which we can do nothing.
>
> Bill.

-- 
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