On Mar 12, 2:27 pm, Cactus <rieman...@googlemail.com> wrote:
> On Mar 12, 2:23 pm, Jeff Gilchrist <jeff.gilchr...@gmail.com> wrote:
>
> > On Thu, Mar 12, 2009 at 10:20 AM, Cactus <rieman...@googlemail.com> wrote:
> > > This can happen when tune cannot get a stable result.
> > > Does it fail consistently at the same point?
>
> > Yes, I just ran it about 6 times and it always fails after it displays
> > the #define GCDEXT_THRESHOLD line. There system is not loaded either
> > so I'm not sure what is going on.
>
> > Also some strange results with this 32bit window binary with
> > run-speed.py. I noticed you had x64\ directory hard-coded into the
> > script, is it only intended for 64bit code?
>
> > Jeff.
>
> I developed it for the 64-bit code but it should work where an
> equivalent function exists in the 32-bit code. As you can see from the
> results, some of the functions don't exist.
I found out how to get platform details in Python but I couldn't find
a way of obtaining machine speed. Does anyone know how to do this in
Python?
Brian
>
> Brian
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
