Hi,

I just created a gmp-mpir-svn1523.spkg and build Sage 3.2.3.final
against it. The good new is that the segfaults I reported for svn-14XX
are gone and that we are seeing 11 doctest failures:

        sage -t  devel/sage/sage/modular/cusps.py # 1 doctests failed
        sage -t  devel/sage/sage/modular/congroup.py # 14 doctests failed
        sage -t  devel/sage/sage/modular/modsym/boundary.py # 2 doctests
failed
        sage -t  devel/sage/sage/modular/modsym/ambient.py # 4 doctests
failed
        sage -t  devel/doc/tut/tut.tex # 1 doctests failed
        sage -t  devel/doc/const/const.tex # 1 doctests failed
        sage -t  devel/sage/sage/rings/integer.pyx # 4 doctests failed
        sage -t  devel/sage/sage/rings/polynomial/toy_d_basis.py # 2 doctests
failed
        sage -t  devel/sage/sage/rings/arith.py # 3 doctests failed
        sage -t  devel/sage/sage/tests/book_stein_modform.py # 4 doctests
failed
        sage -t  devel/sage/sage/tests/book_stein_ent.py # 2 doctests failed

It seems that all those failures are due to different, but
mathematically identical output, so fixing them will be little work.
It seems most of those issues can be traced to the following two
changes:

Used to be, i.e. the Nils Moeller patches:
sage: xgcd(3,24)
(3, -15, 2)

eMPIRe-svn1523:

sage: xgcd(3,24)
(3, 1, 0)

----

Definition:     CRT(a, b, m, n)
Docstring:

        Use the Chinese Remainder Theorem to find some integer x such
        that x=a (mod m) and x=b (mod n).   Note that x is only well-
defined
        modulo m*n.


CRT(2,3, 3, 5)
Expected: (Nils Moeller patches)
    -7
Got: (eMPIRe)
    8

The spkg will need some testing, i.e. I need to fix it so that the
right assembly files for OSX 32 bit are deleted and so on, but overall
I call this progress :)

And this is also nice:

sage: len([a for a in srange(10**6) if not (-a^3).is_perfect_power()])
0

I am now running some larger examples to see if anything pops up.

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