[sage-devel] Re: quaddouble in sage, and other floating point issues

2007-08-23 Thread Jonathan Bober
See ticket number 468. http://trac.sagemath.org/sage_trac/ticket/468 I believe that this is fixed - at least the short easy part. I'm running ./sage -t right now to make sure that no new problems have been introduced. Someone should probably spend a few minutes looking at the patch to make sure

[sage-devel] Re: quaddouble in sage, and other floating point issues

2007-08-15 Thread William Stein
On 8/15/07, Jonathan Bober <[EMAIL PROTECTED]> wrote: > > I am willing to rewrite the quad double wrapper for part (2), but it's > possible that it will be at least a little while before it happens. It > shouldn't be too difficult, though, so it might happen soon. > > Part (1) probably requires de

[sage-devel] Re: quaddouble in sage, and other floating point issues

2007-08-15 Thread Jonathan Bober
On Wed, 2007-08-15 at 09:13 -0700, William Stein wrote: > On 8/14/07, William Stein <[EMAIL PROTECTED]> wrote: > > On 8/14/07, cwitty <[EMAIL PROTECTED]> wrote: > > > On Aug 14, 12:59 am, Jonathan Bober <[EMAIL PROTECTED]> wrote: > > > > This is exactly what NTL does in its quad float class. Just

[sage-devel] Re: quaddouble in sage, and other floating point issues

2007-08-15 Thread William Stein
On 8/14/07, William Stein <[EMAIL PROTECTED]> wrote: > On 8/14/07, cwitty <[EMAIL PROTECTED]> wrote: > > On Aug 14, 12:59 am, Jonathan Bober <[EMAIL PROTECTED]> wrote: > > > This is exactly what NTL does in its quad float class. Just about every > > > function starts and ends with a macro to adjus

[sage-devel] Re: quaddouble in sage, and other floating point issues

2007-08-14 Thread William Stein
On 8/14/07, cwitty <[EMAIL PROTECTED]> wrote: > On Aug 14, 12:59 am, Jonathan Bober <[EMAIL PROTECTED]> wrote: > > This is exactly what NTL does in its quad float class. Just about every > > function starts and ends with a macro to adjust the fpu, resulting in > > around 7 extra assembly instructi

[sage-devel] Re: quaddouble in sage, and other floating point issues

2007-08-14 Thread cwitty
On Aug 14, 12:59 am, Jonathan Bober <[EMAIL PROTECTED]> wrote: > This is exactly what NTL does in its quad float class. Just about every > function starts and ends with a macro to adjust the fpu, resulting in > around 7 extra assembly instructions. In the following code, the > overhead is quite si

[sage-devel] Re: quaddouble in sage, and other floating point issues

2007-08-14 Thread Jonathan Bober
On Tue, 2007-08-14 at 01:07 -0400, didier deshommes wrote: > 2007/8/14, William Stein <[EMAIL PROTECTED]>: > > Correct me if I'm wrong, but I don't think that makes sense. > > If I do this: > > > > sage: a = RQDF(5) > > sage: number_of_partitions(1000) > > 24061467864032622473692149727991 > > sage

[sage-devel] Re: quaddouble in sage, and other floating point issues

2007-08-13 Thread didier deshommes
2007/8/14, William Stein <[EMAIL PROTECTED]>: > Correct me if I'm wrong, but I don't think that makes sense. > If I do this: > > sage: a = RQDF(5) > sage: number_of_partitions(1000) > 24061467864032622473692149727991 > sage: del a > > then during the number_of_partitions call the CPU is set to > t

[sage-devel] Re: quaddouble in sage, and other floating point issues

2007-08-13 Thread William Stein
On 8/13/07, didier deshommes <[EMAIL PROTECTED]> wrote: > > cdef class RealQuadDoubleField_class(Field): > > """ > > Real Quad Double Field > > """ > > > > def __init__(self): > > fpu_fix_start(self.cwf) > > > > def __dealloc__(self): > > fpu_fix_end(self.cwf) >

[sage-devel] Re: quaddouble in sage, and other floating point issues

2007-08-13 Thread didier deshommes
2007/8/11, Jonathan Bober <[EMAIL PROTECTED]>: > cdef class RealQuadDoubleField_class(Field): > """ > Real Quad Double Field > """ > > def __init__(self): > fpu_fix_start(self.cwf) > > def __dealloc__(self): > fpu_fix_end(self.cwf) > > [etc] > > __dealloc__() i

[sage-devel] Re: quaddouble in sage, and other floating point issues

2007-08-13 Thread Jonathan Bober
> I just tried compiling quad double with the -ffloat-store and with the > fpu fix turned off, and it seems to be working. (The tests are still > running, but a bunch have passed already.) What I didn't realize when I wrote this email is that the tests should only take a few seconds to run. Turn

[sage-devel] Re: quaddouble in sage, and other floating point issues

2007-08-13 Thread Jonathan Bober
On Mon, 2007-08-13 at 10:25 -0700, cwitty wrote: > On Aug 11, 6:03 pm, Jonathan Bober <[EMAIL PROTECTED]> wrote: > > I have just noticed that using the C type long double from within sage > > doesn't work the way that I've expected it to. > > > > The issue is a little complicated, and other people

[sage-devel] Re: quaddouble in sage, and other floating point issues

2007-08-13 Thread William Stein
On 8/13/07, cwitty <[EMAIL PROTECTED]> wrote: > > (3a)What I think might be the best idea, at least on Linux, is to change > > the compilation settings for quad double so that the fpu fix is not > > needed. There are two ways to do this: If a processor supports sse2, > > then passing gcc -march=wh

[sage-devel] Re: quaddouble in sage, and other floating point issues

2007-08-13 Thread cwitty
On Aug 11, 6:03 pm, Jonathan Bober <[EMAIL PROTECTED]> wrote: > I have just noticed that using the C type long double from within sage > doesn't work the way that I've expected it to. > > The issue is a little complicated, and other people on this list > probably know more about it than I do, but,

[sage-devel] Re: quaddouble in sage, and other floating point issues

2007-08-12 Thread William Stein
On 8/11/07, Jonathan Bober <[EMAIL PROTECTED]> wrote: > (3a)What I think might be the best idea, at least on Linux, is to change > the compilation settings for quad double so that the fpu fix is not > needed. There are two ways to do this: If a processor supports sse2, > then passing gcc -march=wh