Good point.

2009/2/23  <ja...@njkfrudils.plus.com>:
>
> On Monday 23 February 2009 12:06:28 Bill Hart wrote:
>> 2009/2/23 Cactus <rieman...@googlemail.com>:
>> > On Feb 23, 10:03 am, Bill Hart <goodwillh...@googlemail.com> wrote:
>> >> I've closed all the MPIR 0.9.0 trac tickets which were resolved.
>> >>
>> >> I opened a few new ones for MPIR 1.0.0 and made some blockers,
>> >> including the two serious issues Mariah reported.
>> >>
>> >> Can you guys scan down the list to see if any other tickets should be
>> >> made blockers for the 1.0.0 release.
>> >>
>> >> How do people feel about doing a relatively quick 1.0.0 release and
>> >> then concentrating on a major service release 1.1.0 to deal with a
>> >> whole pile of the more serious tickets that we have opened such as the
>> >> Windows 2000 and Apple x86 build issues, the OSX Core 2 make try
>> >> issue, the core dump on Sun for make tune, cleaning up the GCD code
>> >> and adding a fast xgcd function?
>> >>
>> >> Bill.
>> >
>> > I would like to complete the porting of JM's code to WIndows before
>> > 1.0.0 is released.
>> >
>> > This is very close to complete for the AMD64 stuff and it seems likely
>> > that the core2 stuff will not take long.
>>
>> I've certainly added tickets for this. I agree, we should have the
>> Windows code in parallel with the linux code.
>>
>> > I should mention that none of the K10 stuff has been done because I
>> > don't have any way of doing this on Windows.  So we will need a Visual
>> > Studio user with access to a K10 to do this.
>>
>> OK. We might release 1.0.0 without the K10 code for Windows. If we
>> can't test it then it isn't worth doing. I can live with that for now.
>>
>> I'll have a K10 soon, but not with Windows.
>>
>> Bill.
>>
>
> The K10 left and rshift is the same as the Core2 (mod inc/dec) and also it
> will run on a K8 , but not fast. So testing for correctness is not a
> problem , just speed
>
>
>>
>
>
> >
>

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