Just as a note to humans, we are developing a fix for this as it is
becoming a bigger and bigger issue. Here is the ticket:
https://trac.sagemath.org/ticket/23272
-Aram
On Friday, July 21, 2017 at 6:20:44 PM UTC-4, Christopher Phoenix wrote:
>
> BTW, forgot to link this, but you can see the
BTW, forgot to link this, but you can see the full list of OpenBLAS targets
here: https://github.com/xianyi/OpenBLAS/blob/develop/TargetList.txt
This shows the reason why ATOM isn't the default choice. It would be bad if
OpenBLAS picked that and you were actually running an AMD cpu, or if you
I'm pretty sure that's an issue for upstream, not the Sage devs, maybe we
should ask the OpenBLAS devs? But I suspect that the problem here is that
there isn't a default choice that covers all CPU types. Atom is a catch-all
for many low-end X86_64 cpus (like my Celeron), but it's not the best
I just had the same problem with a new computer (Kaby Lake processor,
apparently). Can we patch OpenBLAS to fall back to ATOM if it's x86_64 but
can't detect the precise CPU? (I can't do this, but maybe someone else can.)
John
On Friday, July 14, 2017 at 12:25:57 AM UTC-7, Dima Pasechnik
Well, I have successfully built Sage on my 11e—over a period of several
hours! :-) Right now I'm running the tests with ./sage --testall to make
sure everything is a-ok, but cli Sage starts, as does the notebook, so it
looks good so far.
Maybe I'll try building the dev version of openblas on
Indeed, OPENBLAS_CONFIGURE="TARGET=ATOM" is a catch-all x86_64 processors
target.
Perhaps one can try the development version of openblas on these processors
(from https://github.com/xianyi/OpenBLAS)
On Friday, July 14, 2017 at 12:29:12 AM UTC+1, Christopher Phoenix wrote:
>
> I'm building Sage
