There are some problems with this. Compiling MPIR using generic C code, for example, will yield a *massive* slowdown of *everything*.
Linbox and ATLAS are also somewhat problematic in this regard. The solution is to use fat binaries for MPIR on x86 and x86_64 and a minimum architecture for each other supported architecture. You can force MPIR to build using whatever architecture you like. However this should only be done for binaries, not when building from source, where MPIR will in general be able to do much better. I'll let the Linbox and ATLAS people comment on their packages. However, I know that ATLAS, when it builds, tries multiple different assembly strategies until it finds an optimal one. It is possible to get within 30% of the assembly speed using generic C on some architectures, but I'm unsure if that can be done with ATLAS itself or not. The ratio might be somewhat greater, if it even provides a generic C implementation. Bill. On 18 Feb, 10:26, Volker Braun <[email protected]> wrote: > Instead of trying to detect the CPU and then possibly displaying an > error message, the binary packages should be built with the same > compiler flags as the binary distribution. This will ensure that every > computer that runs a target linux distribution will also be able to > run the sage binary distribution. > > For example, on Fedora 12 the page > athttp://fedoraproject.org/wiki/PackagingDrafts/RPMMacros_sharedstatedi... > lists: > > 64 bit: -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions - > fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic > 32 bit: -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions - > fstack-protector --param=ssp-buffer-size=4 -m32 -march=i686 - > mtune=atom -fasynchronous-unwind-tables > > Volker > > On Feb 17, 11:51 pm, "Dr. David Kirkby" <[email protected]> > wrote: > > > > > There seems to be a lot of problems that either are, or might be associated > > with > > people using binaries on older CPUs than what they are made on. (e.g see the > > thread "A command which causes Sage to crash" on sage-support). -- To post to this group, send an email to [email protected] To unsubscribe from this group, send an email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
