[sage-devel] Re: Sage 3.0.6.alpha0 released

2008-07-21 Thread mabshoff
On Jul 21, 1:35 pm, "Andrzej Giniewicz" <[EMAIL PROTECTED]> wrote: > Hi, Hi Andrzej, > some new informations, gcc 4.2.4 is also affected by this, but all gcc > <= 4.2.3 are for sure working right, for 4.2.4 and 4.3.1 tachyon > segfaults, I'm looking for some live cd with gcc 4.3 to see if prob

[sage-devel] Re: Sage 3.0.6.alpha0 released

2008-07-21 Thread Andrzej Giniewicz
Hi, some new informations, gcc 4.2.4 is also affected by this, but all gcc <= 4.2.3 are for sure working right, for 4.2.4 and 4.3.1 tachyon segfaults, I'm looking for some live cd with gcc 4.3 to see if problem is also visible in it or not, it seems to appear in gcc trunk somewhere between 2008-0

[sage-devel] Re: Sage 3.0.6.alpha0 released

2008-07-21 Thread Andrzej Giniewicz
Hi, after some sniffing around, I noticed that for me (see bottom of mail for gcc version) techyon needs to be compiled with "make linux" (with disabled threads) or with "-fno-crossjumping -fno-reorder-blocks" added to "Make-arch" file at line 1134 (linux-thr target, after -O6) - second is better

[sage-devel] Re: Sage 3.0.6.alpha0 released

2008-07-21 Thread Andrzej Giniewicz
I was able to reproduce this on many different machines, all had only one common case - they had GCC 4.3.1 or later - additional to my system there is also friends Debian that is affected, as of arch a way to make it reproducible is to update to latest (pacman -Syu) still looking for someone with

[sage-devel] Re: Sage 3.0.6.alpha0 released

2008-07-20 Thread Andrzej Giniewicz
Hi, it still breaks on -O3 and -O2 iirc as when I tested... it should be lowered to -O1 to work always, anyway adding only those 2 mentioned earlier flags (-fno-crossjumping -fno-reorder-blocks) makes it work, I though rather about looking for what compiler versions it fails and patching it in th

[sage-devel] Re: Sage 3.0.6.alpha0 released

2008-07-20 Thread mabshoff
On Jul 19, 10:01 am, "Andrzej Giniewicz" <[EMAIL PROTECTED]> wrote: > Hi, > > after some sniffing around, I noticed that for me (see bottom of mail > for gcc version) techyon needs to be compiled with "make linux" (with > disabled threads) or with "-fno-crossjumping -fno-reorder-blocks" > added

[sage-devel] Re: Sage 3.0.6.alpha0 released

2008-07-20 Thread William Stein
On Sat, Jul 19, 2008 at 3:04 PM, Andrzej Giniewicz <[EMAIL PROTECTED]> wrote: > > Hi again, > > was trying to track that segfault in tachyon doctest, it happens > during show(t) in "texture" example, that's in: > > t = Tachyon(camera_center=(2,5,4), look_at=(2,0,0), raydepth=6) > t.light((10,3,4),

[sage-devel] Re: Sage 3.0.6.alpha0 released

2008-07-19 Thread Andrzej Giniewicz
Hi again, was trying to track that segfault in tachyon doctest, it happens during show(t) in "texture" example, that's in: t = Tachyon(camera_center=(2,5,4), look_at=(2,0,0), raydepth=6) t.light((10,3,4), 1, (1,1,1)) t.texture('mirror', ambient=0.05, diffuse=0.05, specular=.9, opacity=0.9, color

[sage-devel] Re: Sage 3.0.6.alpha0 released

2008-07-19 Thread mabshoff
On Jul 19, 6:17 am, "Andrzej Giniewicz" <[EMAIL PROTECTED]> wrote: > oh, and yes - I built it from source Hi Andrzej, any kind of seemingly Heisenbug that was hard/impossible to reproduce has bitten us in the ass down the road, so everybody please report any seemingly inconsequential or random

[sage-devel] Re: Sage 3.0.6.alpha0 released

2008-07-19 Thread Andrzej Giniewicz
oh, and yes - I built it from source --~--~-~--~~~---~--~~ 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.google.com/group/sage-dev

[sage-devel] Re: Sage 3.0.6.alpha0 released

2008-07-19 Thread William Stein
On Sat, Jul 19, 2008 at 3:13 PM, Andrzej Giniewicz <[EMAIL PROTECTED]> wrote: > > So... > >> I can't replicate this segfault on either OS X or Linux. Could you remind >> me of precisely what hardware/OS you're using and whether or not you >> built from source or used a pre-compiled binary. > > I

[sage-devel] Re: Sage 3.0.6.alpha0 released

2008-07-19 Thread Andrzej Giniewicz
So... > I can't replicate this segfault on either OS X or Linux. Could you remind > me of precisely what hardware/OS you're using and whether or not you > built from source or used a pre-compiled binary. It's 32 bit Arch Linux current, GCC 4.3.1 (patched to snapshot from 2008 06 26), GlibC 2.8

[sage-devel] Re: Sage 3.0.6.alpha0 released

2008-07-18 Thread John Cremona
Following Ansrzej's report I tried the same thing. For me the test always takes 2.0-2.1s but the 5th or 6th time I got the failure: sage -t devel/sage/sage/modular/ssmod/ssmod.py ** File "/home/jec/sage-3.0.6.alpha0/tmp/ssmod.py"

[sage-devel] Re: Sage 3.0.6.alpha0 released

2008-07-18 Thread mabshoff
On Jul 18, 1:01 am, "John Cremona" <[EMAIL PROTECTED]> wrote: Hi John, > Following Ansrzej's report I tried the same thing.  For me the test > always takes 2.0-2.1s but the 5th or 6th time I got the failure: > sage -t  devel/sage/sage/modular/ssmod/ssmod.py >

[sage-devel] Re: Sage 3.0.6.alpha0 released

2008-07-17 Thread Andrzej Giniewicz
Hi, small report - compiled fine, all tests passed (but that's what was reported by make test)... looking into test.log there's still segfault with tachyon test: sage -t devel/sage/sage/plot/tachyon.pysh: line 1: 2 Naruszenie ochrony pamięci tachyon /root/.sage//temp/gi

[sage-devel] Re: Sage 3.0.6.alpha0 released

2008-07-17 Thread John Cremona
Installed fine and all tests passed, with these flags set: SAGE_BUILD_THREADS=2 SAGE_PBUILD=yes on here: Linux version 2.6.18.8-0.3-default ([EMAIL PROTECTED]) (gcc version 4.1.2 20061115 (prerelease) (SUSE Linux)) #1 SMP Tue Apr 17 08:42:35 UTC 2007 John 2008/7/17 David Joyner <[EMAIL PROTECTED

[sage-devel] Re: Sage 3.0.6.alpha0 released

2008-07-17 Thread David Joyner
Installed fine and all tests passed on amd64 hardy heron. On Wed, Jul 16, 2008 at 11:48 PM, mabshoff <[EMAIL PROTECTED]> wrote: > > Hello folks, > > this is 3.0.6.alpha0. This release is a mix of bug fixes and new > features. Nothing crazy has been merged so far and it is unclear at > the moment