On Jan 3, 9:00 am, "Bill Hart" <goodwillh...@googlemail.com> wrote:
> The new intel machines. And I don't know if all Dunnington's use the
> same family/system CPUID etc. So there might be mutiple CPUID's we
> need to add to config.guess.
>
> Bill.

We should change the lowest common denominator on a x86_64 system to
something more useful than 486 , say P4 64bit without LAHF ? , then
people can at least get mpir working on new machines without mucking
about

For the K10 , we will need a separate directory for it , I have
mpn_popcount and mpn_hamdist which will not run on the K8  , requires
SSE4.1a or whatever it's called ...
before 7/7.75 c/l  now 1.5/1.75 c/l

>
> On 03/01/2009, mabshoff <michael.absh...@mathematik.uni-dortmund.de> wrote:
>
>
>
> > On Jan 3, 12:15 am, "Bill Hart" <goodwillh...@googlemail.com> wrote:
>
> > Hi Bill,
>
> >> I'll fix this.
>
> > Thanks.
>
> >> It's just a CPUID problem.
>
> > Yep, that is what I assumed.
>
> >> We actually already have a
> >> ticket for it. There are lots of new machines we should fix detection
> >> for.
>
> > Other than the new Dunnington core which machines are you referring
> > to?
>
> >> Bill.
>
> > Cheers,
>
> > Michael
--~--~---------~--~----~------------~-------~--~----~
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