Different ATLAS versions have different routines so the architectural defaults for one version don't necessarily match another version.
If you don't want top performance then you can always set SAGE_ATLAS_ARCH=fast or SAGE_ATLAS_ARCH=base when compiling Sage, this will use some generic settings but will build much faster. On Monday, August 19, 2013 2:18:49 PM UTC+1, jason wrote: > > On 8/19/13 7:18 AM, Jeroen Demeyer wrote: > > I believe (but I welcome other opinions) that, if this new ATLAS is > > better in other respects, the ATLAS build time doesn't really matter. > > > But auto-tuning surely doesn't need to be done every time on every > machine. I thought there was an easy way to save the architecture > definitions. > > Is the situation such that before ATLAS was using architecture defaults, > but for some reason now it isn't? If that's the case, is it because > there aren't architecture defaults in the new ATLAS for these > architectures? If there are architecture defaults for machines like > John's, and we aren't using them (two big questions to answer, of > course), then surely that is a regression. The ATLAS FAQ indicates that > auto-tuning is usually worse than using architecture defaults: > http://math-atlas.sourceforge.net/faq.html#ArchDef > > Thanks, > > Jason > > > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
