The rosemary tune failure is at line 2 of inv_div_qr.c, which is
inside a comment! #&%$&~£ Suspect a broken compiler or file
corruption.

The fulvia build failure again looks like config.h is corrupted, which
suggests the build wasn't clean.

>From memory the issue can also be triggered by an incorrect value in
gmp-mparam.h for

#define USE_PREINV_DIVREM_1               1  /* native */

However, this is core2, and so should already have the right value.
I've probably done something wrong somewhere....

Bill.

On 12 May 2010 23:24, Jason Moxham <[email protected]> wrote:
> On Wednesday 12 May 2010 23:11:39 Minh Nguyen wrote:
>> Hi folks,
>>
>> I have tuned revision 2927 of MPIR on the Sage and Skynet machines.
>> Results --- including build failures, issues with make tune, and tune
>> logs --- are up on this wiki page [1]. I have *not* yet committed any
>> of the new tuning parameters as I do not have the necessary
>> privileges. The build failures with the two IA-64 Linux machines
>> resulted from using GCC 4.5.0. The other failure occurs on x86_64
>> Solaris 10.
>>
>> [1] http://wiki.sagemath.org/mpir/BuildFarm/mpir-2.0.1#MPIR2.0.1-r2927
>>
>> --
>> Regards
>> Minh Van Nguyen
>
> On cleo the IA64 machine we do get these passes
>
> configure: error: C++ compiler not available, see config.log for details
> cleo
>
> PASSED CC=cc CXX=c++ configure=
> PASSED CC=cc CXX=c++ configure=--enable-cxx --enable-gmpcompat
> PASSED CC=cc CXX=c++ configure=--enable-cxx --enable-gmpcompat --enable-assert
> --enable-alloca=debug
> PASSED CC=cc CXX=c++ configure=--enable-cxx --enable-gmpcompat --enable-assert
> --enable-alloca=debug --build=none-unknown-linux-gnu
> PASSED CC=icc CXX=icpc configure=
> FAILED CC=icc CXX=icpc configure=--enable-cxx --enable-gmpcompat
>
> cc which is gcc-4.1.1 passes all tests
> icc passes but the c++ compiler part of it "icpc" fails
>
>
> I will look at the Solaris Core2 failure  , and the rosemary tune failure
>
> Jason
>
>
>
> --
> You received this message because you are subscribed to the Google Groups 
> "mpir-devel" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to 
> [email protected].
> 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 [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/mpir-devel?hl=en.

Reply via email to