unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: Florent Pruvost <florent.pruvost@inria.fr>,
	Emmanuel Agullo <emmanuel.agullo@inria.fr>,
	49096@debbugs.gnu.org
Subject: [bug#49096] [PATCH] gnu: petsc: Link against OpenBLAS rather than LAPACK.
Date: Tue, 22 Jun 2021 09:29:56 +0200	[thread overview]
Message-ID: <87sg1a4arv.fsf@gnu.org> (raw)
In-Reply-To: <YNCNe+4pBG+8vMbe@3900XT> (Efraim Flashner's message of "Mon, 21 Jun 2021 16:00:43 +0300")

Hi,

Efraim Flashner <efraim@flashner.co.il> skribis:

> On Fri, Jun 18, 2021 at 06:12:04PM +0200, Ludovic Courtès wrote:

[...]

>> Usually there’s no reason to depend on the reference (“Netlib”) BLAS/LAPACK
>> implementations because they perform poorly.  This change is one way to
>> bring consistency here.
>> 
>> Thoughts?
>> 
>> Ludo’.
>
> It sounds reasonable to me.

Cool, thanks for taking a look.

> As long as you're open to thoughts, perhaps we want to have a discussion
> (in a new thread) about renaming the input labels for lapack/openblas so
> it's easier to do 'guix build foo
> --with-inputs=blas=openblas-tuned-for-my-machine'

We’ve very much interested in that.  However, input labels don’t have a
role here since ‘--with-input’ matches packages by name.

So most likely, we’d (1) use OpenBLAS by default everywhere instead of
netlib blas/lapack, and (2) you’d use:

  --with-input=openblas=openblas-tuned

WDYT?

Ludo’.




  reply	other threads:[~2021-06-22  7:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-18 16:12 [bug#49096] [PATCH] gnu: petsc: Link against OpenBLAS rather than LAPACK Ludovic Courtès
2021-06-21 13:00 ` Efraim Flashner
2021-06-22  7:29   ` Ludovic Courtès [this message]
2021-06-23 12:34     ` zimoun
2021-06-22 15:57   ` bug#49096: " 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

  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=87sg1a4arv.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=49096@debbugs.gnu.org \
    --cc=efraim@flashner.co.il \
    --cc=emmanuel.agullo@inria.fr \
    --cc=florent.pruvost@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 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).