From: Federico Beffa <beffa@ieee.org>
To: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: RFC: building numpy against OpenBLAS.
Date: Thu, 28 May 2015 08:38:34 +0200 [thread overview]
Message-ID: <CAKrPhPOj6K1JxEx=LX-6fZr2TT4npwbEzPgQtuK=XS=vbWmynA@mail.gmail.com> (raw)
In-Reply-To: <idj8ucaggtl.fsf@bimsb-sys02.mdc-berlin.net>
On Wed, May 27, 2015 at 5:50 PM, Ricardo Wurmus
<ricardo.wurmus@mdc-berlin.de> wrote:
>
> Federico Beffa writes:
>
>> Out of curiosity, could you outline how OpenBLAS is optimized for a
>> specific CPU architecture while being compiled on a different CPU (and
>> hence allowing to be substituted)?
>
> The Quick Install instructions[1] say that when OpenBLAS is compiled
> with DYNAMIC_ARCH=1
>
> "All kernel will be included in the library and dynamically switched
> the best architecutre at run time."
>
> It seems that unlike ATLAS, OpenBLAS does not perform any self-tuning
> but relies on hand-optimised code (e.g. by using CPU-specific
> instructions).
Sounds good. Thanks!
Fede
next prev parent reply other threads:[~2015-05-28 6:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-23 7:20 RFC: building numpy against OpenBLAS Federico Beffa
2015-05-27 15:50 ` Ricardo Wurmus
2015-05-28 6:38 ` Federico Beffa [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-05-22 15:00 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
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
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='CAKrPhPOj6K1JxEx=LX-6fZr2TT4npwbEzPgQtuK=XS=vbWmynA@mail.gmail.com' \
--to=beffa@ieee.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).