On May 2, 7:56 pm, "William Stein" <[EMAIL PROTECTED]> wrote:
> Michael and Sage-devel,
No need to single me out - I read sage-devel ;)
> This is happening a lot (see below):
<SNIP>
> We really need to find a way to *immediately* report that
> "this Sage binary doesn't work on your processor" ASAP instead of after weeks
> and only when people push Sage to its limits.
>
> Or we need to build better binaries. Any ideas?
We can force ATLAS via magic arch switch to build binaries that do not
use SSE at all. But it would slow down some operations [obviously]. It
would only matter on 32 bit x86 - everywhere else this is a non-issue.
For starters I would stop calling the binaries i686 since they are
SSE2 binaries. Most people will probably not know what SSE2 is, so
that doesn't help. What we also could do is detect non-SSE2 capable
CPUs at startup on Linux x86 via the flags in /proc/cpuinfo and just
refuse to start in case the CPU's capabilities are insufficient. In
that case we should point people to the non-SSE binaries.
Cheers,
Michael
--~--~---------~--~----~------------~-------~--~----~
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-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
