William Stein wrote:
> I agree -- making another patch now is a bad idea. I'll release sage-2.8.3 in
> a few minutes,
The version I downloaded this morning builds and all test passed.
> real84m42.810s
> user72m10.968s
> sys 8m39.530s
> To install gap, gp, singular, etc., scripts
>
On 8/31/07, Joel B. Mohler <[EMAIL PROTECTED]> wrote:
>
> On Thu, Aug 30, 2007 at 09:23:26PM -0400, David Harvey wrote:
> > On Aug 30, 2007, at 8:57 PM, William Stein wrote:
> > > David - please make a new ticket for 2.9 that addresses all the issues
> > > you mention below.
> >
> > done.
>
> I di
On Thu, Aug 30, 2007 at 09:23:26PM -0400, David Harvey wrote:
> On Aug 30, 2007, at 8:57 PM, William Stein wrote:
> > David - please make a new ticket for 2.9 that addresses all the issues
> > you mention below.
>
> done.
I didn't look at this ticket but I am aware of the code duplication in ext
On Aug 30, 2007, at 8:57 PM, William Stein wrote:
> David - please make a new ticket for 2.9 that addresses all the issues
> you mention below.
done.
david
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe fr
David - please make a new ticket for 2.9 that addresses all the issues
you mention below.
- William
(Sent from my iPhone.)
On Aug 30, 2007, at 5:32 PM, David Harvey <[EMAIL PROTECTED]>
wrote:
>
>
> On Aug 30, 2007, at 8:19 PM, William Stein wrote:
>
>> I commented out your version of __int
On Aug 30, 2007, at 8:19 PM, William Stein wrote:
> I commented out your version of __int__ and all the problems
> vaunsbed. I have posted an rc4.
okay,
but I don't think that ticket #411 should be fully closed until we
have removed the code duplication between ext and c_lib. Or at least
I commented out your version of __int__ and all the problems
vaunsbed. I have posted an rc4.
- William
(Sent from my iPhone.)
On Aug 30, 2007, at 4:57 PM, David Harvey <[EMAIL PROTECTED]>
wrote:
>
>
> On Aug 30, 2007, at 7:53 PM, mabshoff wrote:
>
>> There is hope: A potential source of t
On Aug 30, 2007, at 7:53 PM, mabshoff wrote:
> There is hope: A potential source of the problem has been indentified.
> To quote #sage-devel:
>
> 16:20 < was_> OK.
> 16:20 < was_> There are two versions of mpz_pylong in the SAGE source
> code.
> 16:20 < was_> that's what is causing the trouble.
On Aug 31, 12:47 am, "William Stein" <[EMAIL PROTECTED]> wrote:
> On 8/30/07, Martin Albrecht <[EMAIL PROTECTED]> wrote:
>
> > On Thursday 30 August 2007 19:11, mabshoff wrote:
> > > > On a suse 101. amd64: SAGE compiled file. The sage -testall
> > > > The above crash looks pretty serious -- it'
On 8/30/07, Martin Albrecht <[EMAIL PROTECTED]> wrote:
> On Thursday 30 August 2007 19:11, mabshoff wrote:
> > > On a suse 101. amd64: SAGE compiled file. The sage -testall
> > > The above crash looks pretty serious -- it's evidently a 64-bit only
> > > issue, which was probably introduced by our
Same result on my g4 laptop (though slower ... thank god William
compiles binaries for my machine).
-cc
On Aug 30, 2007, at 2:29 PM, David Harvey wrote:
>
> rc3 builds and -testall passes on ppc G5, OS 10.4.10,
>
> EXCEPT a trivial one:
>
> sage -t tut.tex
> *
rc3 builds and -testall passes on ppc G5, OS 10.4.10,
EXCEPT a trivial one:
sage -t tut.tex
**
File "tut.py", line 1894:
: f.partial_fraction(x)
Expected:
1/(2*(x - 1)) - (
Some good news: I just close #501 after re-valgrinding 2.8.3rc3. The
loss for both code snippets is only 3.5 kb lost + 320kb indirectly
lost regardless of the number of rounds done. Those are also fixable,
but I will open new tickets for those issues once I revisit that area
of the code. But I alr
On Aug 30, 8:13 pm, Martin Albrecht <[EMAIL PROTECTED]>
wrote:
> > Now where I see the problem: On a box with more than 2GB of RAM calloc
> > might return a pointer that lies above the range of signed int. Then
> > the cast to (int*) returns a pointer to the allocated memory module
> > 2^31.
>
>
> Now where I see the problem: On a box with more than 2GB of RAM calloc
> might return a pointer that lies above the range of signed int. Then
> the cast to (int*) returns a pointer to the allocated memory module
> 2^31.
The size of an "int" (mod 2^31) is not relevant for an "int *" which is of
On Aug 30, 7:28 pm, Martin Albrecht <[EMAIL PROTECTED]>
wrote:
> On Thursday 30 August 2007 19:11, mabshoff wrote:
>
> > > On a suse 101. amd64: SAGE compiled file. The sage -testall
> > > The above crash looks pretty serious -- it's evidently a 64-bit only
> > > issue, which was probably introd
On Aug 30, 6:57 pm, "William Stein" <[EMAIL PROTECTED]> wrote:
> On 8/30/07, David Joyner <[EMAIL PROTECTED]> wrote:
>
>
>
> > > On a suse 101. amd64: SAGE compiled file. The sage -testall
> > revealed several seg faults, such as:
>
> > sage -t matrix/strassen.pyx
>
> >
On Thursday 30 August 2007 19:11, mabshoff wrote:
> > On a suse 101. amd64: SAGE compiled file. The sage -testall
> > The above crash looks pretty serious -- it's evidently a 64-bit only
> > issue, which was probably introduced by our work to fix other bugs (??)
> > and/or memory leaks. This will
On 8/30/07, David Joyner <[EMAIL PROTECTED]> wrote:
> > On a suse 101. amd64: SAGE compiled file. The sage -testall
> revealed several seg faults, such as:
>
> sage -t matrix/strassen.pyx
>
>
> Unhandled SIGSEGV: A segmentation fault oc
On 8/30/07, Robert Bradshaw <[EMAIL PROTECTED]> wrote:
>
> Builds fine on my OS X PPC G5 (took almost two and a half hours
> though). gcc 4.0.1. Still running doctests, but it had some major
> errors in the sage/coding modules ("gap produced error output).
> Everything else is looking good, I'll
On Aug 30, 6:20 pm, "David Joyner" <[EMAIL PROTECTED]> wrote:
Hello David,
> On a suse 101. amd64: SAGE compiled file. The sage -testall
> revealed several seg faults, such as:
>
> sage -t matrix/strassen.pyx
I did valgrind that one on a 64 bit box, but didn't see anything
obvious.
>
>
On Aug 30, 2007, at 12:20 PM, David Joyner wrote:
>
> On a suse 101. amd64: SAGE compiled file. The sage -testall
> revealed several seg faults, such as:
Oh... I didn't know about sage -testall. I usually just report the
results of sage -t devel/sage/sage. Am I supposed to do testall when
r
On a suse 101. amd64: SAGE compiled file. The sage -testall
revealed several seg faults, such as:
sage -t matrix/strassen.pyx
Unhandled SIGSEGV: A segmentation fault occured in SAGE.
This probably occured because a *compiled* componen
rc3 builds and all tests pass on core duo, OS 10.4.10.
david
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sure enough, rc3 builds and all tests pass.
Alex
Alex Ghitza wrote:
> Hi,
>
> rc2 builds on
>
> Machine: Linux sillyname 2.6.22-gentoo-r5 #2 SMP Tue Aug 28 23:46:12 UTC
> 2007 i686 Intel(R) Core(TM)2 CPU 6400 @ 2.13GHz GenuineIntel GNU/Linux
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
rc2 builds on
Machine: Linux sillyname 2.6.22-gentoo-r5 #2 SMP Tue Aug 28 23:46:12 UTC
2007 i686 Intel(R) Core(TM)2 CPU 6400 @ 2.13GHz GenuineIntel GNU/Linux
real53m35.322s
user48m47.946s
sys 4m20.216s
There are some issues in ma
William Stein wrote:
> Hi,
>
> I was able to create a SAGE release candidate that builds and runs:
>
>http://sage.math.washington.edu/home/was/dist/s/dist/sage-2.8.3.rc2.tar
>
> As always, feedback on this would be greatly appreciated. There is
> really so much that is new or changed in th
Builds fine on my OS X PPC G5 (took almost two and a half hours
though). gcc 4.0.1. Still running doctests, but it had some major
errors in the sage/coding modules ("gap produced error output).
Everything else is looking good, I'll let you know if there are other
problems.
- Robert
On
28 matches
Mail list logo
