I guess the idea of doing a 32 bit test if the 64 bit code fails is
probably a sensible one. The CPUID should still be returned correctly.

I too don't want to work around every broken system. However this is a
case that GMP gets right and we don't, so I would say we should fix
it.

Do you want to mimic what they do and we'll see if that works? If you
like we can do a 1.1.1, fix the Windows issues once Brian gets to that
and fix this issue and the test for stringinzing. Does configure set
the define for that before config.guess is run? It looks like it is
later in the configure run to me.

I'll check out this pentium-D failure and see what is going on. If
something needs fixing in 1.1.1 for that I'll commit that too.

We should have access to a new Sun server machine in the Sage lab here
and I am guessing we'll be able to test on it. Despite being a T2000
or something like that, it is not part of SkyNet.

Bill.

2009/4/17 Jason Moxham <ja...@njkfrudils.plus.com>:
>
>
> Thanks Jeff
>
> The problem is that pathcc has been set up to default to a 32bit compiler on
> the broken system. pathcc has a default config file which needs to be
> changed. GMP has a work around for this.
>
> Do we really want to workaround every broken configuration?
> We could provide a warning that  config.guess writes to config.log
>
> Jason
>
>
>
>
> On Friday 17 April 2009 19:06:02 Jason Moxham wrote:
>> that interesting , gmp fails as well , but
>> it look likes it tries a 32 bit version , and that passes
>>
>> I'll mimic it , and see what happens
>>
>> On Friday 17 April 2009 18:53:43 Jeff Gilchrist wrote:
>> > On Fri, Apr 17, 2009 at 8:14 AM, Jason Moxham <ja...@njkfrudils.plus.com>
>>
>> wrote:
>> > > can you put this in the gmp-4.3.0 directory and run config.guess
>> > > we will see what it thinks
>> >
>> > cc for build is
>> > host cc is
>> > cc is
>> > cc for build is cc
>> > host cc is
>> > cc is
>> > cc for build is cc
>> > host cc is
>> > cc is
>> > pathcc -Wall -TENV:simd_zmask=OFF -TENV:simd_imask=OFF
>> > -TENV:simd_omask=OFF -O3 -OPT:Ofast -fno-math-errno
>> > pathcc: no input files
>> > For general help: pathcc --help
>> > To search help: pathcc -help:<string>
>> > dummy-258421.s: Assembler messages:
>> > dummy-258421.s:5: Error: bad register name `%rbx'
>> > dummy-258421.s:9: Error: bad register name `%rdi)'
>> > dummy-258421.s:10: Error: bad register name `%rdi)'
>> > dummy-258421.s:11: Error: bad register name `%rdi)'
>> > dummy-258421.s:12: Error: bad register name `%rbx'
>> > dummy-258422.c:2: warning: return type defaults to ‘int’
>> > dummy-258422.c: In function ‘main’:
>> > dummy-258422.c:9: warning: implicit declaration of function ‘cpuid’
>> > dummy-258422.c:19: warning: implicit declaration of function ‘strcmp’
>> > dummy-258422.c:78: warning: implicit declaration of function ‘printf’
>> > dummy-258422.c:78: warning: incompatible implicit declaration of
>> > built-in function ‘printf’
>> > Please report this problem to <supp...@pathscale.com>.
>> > Problem report saved as /home/jeffg/.ekopath-bugs/pathcc_error_aJgBHv.i
>> > Please review the above file and, if possible, attach it to your problem
>> > report. Please review the above file and, if possible, attach it to your
>> > problem report. dummy-258422.c:2: warning: return type defaults to ‘int’
>> > dummy-258422.c: In function ‘main’:
>> > dummy-258422.c:9: warning: implicit declaration of function ‘cpuid’
>> > dummy-258422.c:19: warning: implicit declaration of function ‘strcmp’
>> > dummy-258422.c:78: warning: implicit declaration of function ‘printf’
>> > dummy-258422.c:78: warning: incompatible implicit declaration of
>> > built-in function ‘printf’
>> > core2-unknown-linux-gnu
>> >
>> > Jeff.
>>
>>
>
>
> >
>

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