From: Dave Love <fx@gnu.org>
To: "Ludovic Courtès" <ludovic.courtes@inria.fr>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Packaging BLIS
Date: Fri, 08 Sep 2017 23:36:10 +0100 [thread overview]
Message-ID: <87tw0com1x.fsf@albion.it.manchester.ac.uk> (raw)
In-Reply-To: <87a826tslo.fsf_-_@inria.fr> ("Ludovic \=\?iso-8859-1\?Q\?Court\?\= \=\?iso-8859-1\?Q\?\=E8s\=22's\?\= message of "Thu, 07 Sep 2017 17:51:15 +0200")
ludovic.courtes@inria.fr (Ludovic Courtès) writes:
> That caught my attention so I packaged BLIS:
>
> https://git.savannah.gnu.org/cgit/guix.git/commit/?id=5a7deb117424ff4d430b771b50e534cf065c0ba1
>
> There are several “flavors” of BLIS, so you can always rebuild your
> favorite program with:
>
> --with-input=openblas=blis-haswell
>
> and similar (or even ‘--with-graft=blis=blis-haswell’ where applicable).
I'm not aware of an advantage of BLIS over OpenBLAS except for KNL (and
maybe Skylake Xeon, if that's covered). My interest was specifically
for avx512. (BLIS is documented as basically a research effort, which I
think explains the way it's built.)
> Hopefully the issue you linked to above will be fixed in future versions
> of BLIS, at which point we can probably provide a single “blis” package.
>
> Ludo’.
I still think it's important to be able to select the BLAS at run time
with dynamic linking. I suppose the trick I used for rpm will work
similarly, though I'm not sure how ld.so behaves in Guix.
next prev parent reply other threads:[~2017-09-08 22:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-21 12:23 Optionally using more advanced CPU features Ricardo Wurmus
2017-08-22 9:21 ` Ludovic Courtès
2017-08-23 13:59 ` Dave Love
2017-08-28 13:48 ` Ludovic Courtès
2017-09-01 10:46 ` Dave Love
2017-09-04 12:38 ` Ludovic Courtès
2017-09-07 15:51 ` Packaging BLIS Ludovic Courtès
2017-09-08 22:36 ` Dave Love [this message]
2017-09-11 7:12 ` Ludovic Courtès
2017-08-26 3:39 ` Optionally using more advanced CPU features Ben Woodcroft
2017-08-26 5:14 ` Pjotr Prins
2017-09-04 14:50 ` Ludovic Courtès
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tw0com1x.fsf@albion.it.manchester.ac.uk \
--to=fx@gnu.org \
--cc=guix-devel@gnu.org \
--cc=ludovic.courtes@inria.fr \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.