From: "Ludovic Courtès" <ludovic.courtes@inria.fr>
To: guix-devel <guix-devel@gnu.org>
Subject: LAPACK vs. OpenBLAS
Date: Thu, 24 Jun 2021 14:55:04 +0200 [thread overview]
Message-ID: <87wnqjs9qv.fsf@inria.fr> (raw)
Hello!
A surprisingly large number of packages depend on ‘lapack’:
--8<---------------cut here---------------start------------->8---
$ guix refresh -l lapack
Building the following 261 packages would ensure 614 dependent packages are rebuilt: […]
--8<---------------cut here---------------end--------------->8---
Among them are Julia and Octave. You can see the reverse dependency
graph with:
guix graph -t reverse-bag lapack | xdot -
There are two cases:
1. Packages that depend on both ‘lapack’ and ‘openblas’. This is
almost always a mistake because ‘openblas’ provides the same
interfaces as ‘lapack’, only with a more efficient implementation.
2. Packages that depend on ‘lapack’ only: for the same reason, they
should depend on ‘openblas’ instead.
I’ve addressed a case like #1 for numpy/scipy in
6623d1cd7f3298f2e5c224299d11a77f7ae18bf5, and #2 with commit
c7a5c3e0bba2ac3d197b219d21527863308b75dd (petsc).
Julia references both lapack and openblas:
--8<---------------cut here---------------start------------->8---
$ guix graph --path -t references julia lapack
/gnu/store/d077a9ggqlcyhnhcg4ng2ibnlarxq8zf-julia-1.5.3
/gnu/store/41rw9w35by4j8lbl85gi3xfiaf7zqykh-lapack-3.9.0
$ guix graph --path -t references julia openblas
/gnu/store/d077a9ggqlcyhnhcg4ng2ibnlarxq8zf-julia-1.5.3
/gnu/store/bs9pl1f805ins80xaf4s3n35a0x2lyq3-openblas-0.3.9
--8<---------------cut here---------------end--------------->8---
Can a Julia-savvy person check whether this is justified?
I’ll look at some of the other cases. Perhaps we could have a lint
checker warning against the use of lapack.
Thoughts?
Thanks,
Ludo’.
next reply other threads:[~2021-06-24 12:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-24 12:55 Ludovic Courtès [this message]
2021-06-24 13:58 ` LAPACK vs. OpenBLAS zimoun
2021-06-24 15:00 ` Eric Brown
2021-06-29 14:38 ` Ludovic Courtès
2021-06-29 16:00 ` Eric Brown
2021-06-29 16:13 ` Eric Brown
-- strict thread matches above, loose matches on Subject: below --
2021-08-06 12:32 Paul Garlick
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=87wnqjs9qv.fsf@inria.fr \
--to=ludovic.courtes@inria.fr \
--cc=guix-devel@gnu.org \
/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).