From: Mark H Weaver <mhw@netris.org>
To: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Cc: guix <guix-devel@gnu.org>
Subject: Re: RFC: building numpy against OpenBLAS.
Date: Fri, 05 Jun 2015 09:54:24 -0400 [thread overview]
Message-ID: <87r3pqgt0v.fsf@netris.org> (raw)
In-Reply-To: <idjmw0jfu8w.fsf@bimsb-sys02.mdc-berlin.net> (Ricardo Wurmus's message of "Mon, 1 Jun 2015 15:11:59 +0200")
Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de> writes:
> Ricardo Wurmus writes:
>
>> python-numpy currently depends on Atlas, which means that it cannot be
>> substituted with a binary built elsewhere. OpenBLAS is an alternative
>> to Atlas and the binary can be used on all supported CPUs at runtime.
>> This makes it possible for us to make numpy substitutable.
>>
>> We currently do not have a working OpenBLAS on MIPS, so the attached
>> patch selects OpenBLAS as an input only when not on MIPS. Some
>> additional configuration happens only unless "atlas" is among the
>> inputs.
>
> If there are no objections I'd like to go ahead and push this patch to
> build numpy with OpenBLAS. From the comments I gather that it's not as
> controversial a change as I suspected.
I think we should go ahead and switch to OpenBLAS on _all_ platforms,
not just on MIPS. Were there any objections to that? If not, I'd
advocate just doing it.
Thanks!
Mark
next prev parent reply other threads:[~2015-06-05 13:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-22 15:00 RFC: building numpy against OpenBLAS Ricardo Wurmus
2015-05-22 15:16 ` Eric Bavier
2015-06-01 13:11 ` Ricardo Wurmus
2015-06-05 13:52 ` Mark H Weaver
2015-06-05 13:54 ` Mark H Weaver [this message]
2015-06-05 15:36 ` Mark H Weaver
2015-06-05 16:01 ` Ricardo Wurmus
2015-06-05 17:33 ` Mark H Weaver
2015-06-07 19:46 ` Ludovic Courtès
2015-06-07 21:32 ` Mark H Weaver
-- strict thread matches above, loose matches on Subject: below --
2015-05-23 7:20 Federico Beffa
2015-05-27 15:50 ` Ricardo Wurmus
2015-05-28 6:38 ` Federico Beffa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r3pqgt0v.fsf@netris.org \
--to=mhw@netris.org \
--cc=guix-devel@gnu.org \
--cc=ricardo.wurmus@mdc-berlin.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).