Re: [sage-devel] ATLAS - proposal to allow a threaded build.

2010-07-20 Thread Dr. David Kirkby
On 07/20/10 07:42 PM, Peter Jeremy wrote: On 2010-Jul-19 23:20:40 +0100, "Dr. David Kirkby" wrote: So if I understand you correctly, SAGE_NUM_THREADS=10 would set 10 threads globally in Sage, but SAGE_NUM_THREADS_ATLAS=1 would override the 10 to 1 (single threaded) for just ATLAS. Have I

Re: [sage-devel] ATLAS - proposal to allow a threaded build.

2010-07-20 Thread Peter Jeremy
On 2010-Jul-19 23:20:40 +0100, "Dr. David Kirkby" wrote: >> How about an extension to the standard environment variable parsing >> so that SAGE_FOO_bar is equivalent to (and overrides) SAGE_FOO in >> package 'bar' only? This allows variables to be overridden for >> specific packages without havi

Re: [sage-devel] ATLAS - proposal to allow a threaded build.

2010-07-19 Thread Dr. David Kirkby
On 07/19/10 10:37 PM, Peter Jeremy wrote: On 2010-Jul-17 08:52:49 +0100, "Dr. David Kirkby" wrote: I don't know if you have every written multi-threaded code, but it is non-trivial and very easy to make a mistake. Experience shows me that those mistakes show up on on one platform only. It's ha

Re: [sage-devel] ATLAS - proposal to allow a threaded build.

2010-07-19 Thread Peter Jeremy
On 2010-Jul-17 08:52:49 +0100, "Dr. David Kirkby" wrote: >I don't know if you have every written multi-threaded code, but it is >non-trivial and very easy to make a mistake. Experience shows me that those >mistakes show up on on one platform only. It's hard enough to track the bug if >you wrot

Re: [sage-devel] ATLAS - proposal to allow a threaded build.

2010-07-17 Thread Dr. David Kirkby
On 07/17/10 07:20 AM, Martin Albrecht wrote: How does this sound. 1) We add an environment variable SAGE_ATLAS_THREADS 2) If unset, then the behavior is unchanged, so we build an unthreaded ATLAS. 3) If set to "auto": $ export SAGE_ATLAS_THREADS=auto then we let ATLAS automatically determine t

Re: [sage-devel] ATLAS - proposal to allow a threaded build.

2010-07-16 Thread Martin Albrecht
> How does this sound. > > 1) We add an environment variable SAGE_ATLAS_THREADS > 2) If unset, then the behavior is unchanged, so we build an unthreaded > ATLAS. 3) If set to "auto": > > $ export SAGE_ATLAS_THREADS=auto > > then we let ATLAS automatically determine the number of threads. (I thin

Re: [sage-devel] ATLAS - proposal to allow a threaded build.

2010-07-16 Thread Carl Witty
On Fri, Jul 16, 2010 at 4:34 PM, Dr. David Kirkby wrote: > How does this sound. > > 1) We add an environment variable SAGE_ATLAS_THREADS > 2) If unset, then the behavior is unchanged, so we build an unthreaded > ATLAS. > 3) If set to "auto": > > $ export SAGE_ATLAS_THREADS=auto > > then we let ATL

[sage-devel] ATLAS - proposal to allow a threaded build.

2010-07-16 Thread Dr. David Kirkby
Currently, when ATLAS builds in Sage, it uses this option to the configure scrip, it used the option -t 0, which disables threading. The comment in spkg-install-script says: # -t 0: disable threading for now. and we can see that actually happens. ../src/configure --prefix="$SAGE_LOCAL