On Friday 17 April 2009 08:18:43 Bill Hart wrote:
> We should figure out:
>
> 1) Does GMP default to Core2 if it can't identify the CPU (as MPIR
> 1.0.0 does) - I don't think so. I'm pretty sure it defaults to atom.

I havent tested , but looking at the code it defaults to x86_64 , which for 
gmp-4.3.0 is basically k8 code

> 2) Does it detect the CPU correctly - I think so, in this case at
> least, though clearly not in other cases
> 3) Does it just refuse to use pathcc and insist on gcc

maybe , 
our config.guess uses cc which is before configure even gets to the compiler 
tests , same for gmp-4.3.0


>
> There has to be some simple reason why we have this problem and they don't.
>
> Bill.
>
> 2009/4/17 Jason Moxham <ja...@njkfrudils.plus.com>:
> > On Thursday 16 April 2009 15:09:23 Jeff Gilchrist wrote:
> >> On Thu, Apr 16, 2009 at 9:57 AM, Jason Moxham
> >> <ja...@njkfrudils.plus.com>
> >
> > wrote:
> >> > and
> >> > cc -v
> >> > on both systems is ?
> >>
> >> Non-working system:
> >>
> >> 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>
> >
> > Thats the problem , the compiler is not defaulting to 64 bit , why ?
> > Doesn't the pathcc compiler have a default config file , how does it
> > compare between these two machines?
> >
> >> Working system:
> >>
> >> pathcc -Wall -m64 -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>
> >>
> >>
> >> Note the -m64 missing from the non-working system.
> >>
> >> 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