unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Paul Garlick <pgarlick@tourbillion-technology.com>
Cc: emmanuel.agullo@inria.fr, bavier@member.fsf.org, 47237@debbugs.gnu.org
Subject: [bug#47237] [PATCH] gnu: metis: Use 64-bit floating pointer numbers on 64-bit architectures.
Date: Fri, 19 Mar 2021 10:37:31 +0100	[thread overview]
Message-ID: <87k0q3iiw4.fsf@gnu.org> (raw)
In-Reply-To: <48a8a7c4dbe90415468d8db64cdfd82be52aeb4e.camel@tourbillion-technology.com> (Paul Garlick's message of "Thu, 18 Mar 2021 18:41:53 +0000")

Hi Paul and all,

Paul Garlick <pgarlick@tourbillion-technology.com> skribis:

> I think it is a good idea to allow for different variants, even on 64-
> bit architectures.
>
> In one direction there is a performance advantage using 32-bit floats. 
> In the other direction accuracy improves using the 64-bit data type.

True.  That concurs with what Emmanuel explains.

> There is a similar situation with the scotch library.  The scotch32
> package variant is preferable, even on 64-bit systems, except for the
> case of very large models.

Though ‘scotch32’ is about 32-bit integers, not floating point numbers.
So I guess it’s not the same kind of tradeoff?

Anyway, it sounds like the best course of action is to withdraw this
patch and instead come up with multiple variants or package parameters.

Thanks for your feedback!

Ludo’.




  reply	other threads:[~2021-03-19  9:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-18 15:02 [bug#47237] [PATCH] gnu: metis: Use 64-bit floating pointer numbers on 64-bit architectures Ludovic Courtès
2021-03-18 15:27 ` Emmanuel Agullo
2021-03-18 21:48   ` zimoun
2021-03-19 11:07     ` Emmanuel Agullo
2021-03-18 18:41 ` Paul Garlick
2021-03-19  9:37   ` Ludovic Courtès [this message]
2021-03-25 17:42     ` bug#47237: " 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=87k0q3iiw4.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=47237@debbugs.gnu.org \
    --cc=bavier@member.fsf.org \
    --cc=emmanuel.agullo@inria.fr \
    --cc=pgarlick@tourbillion-technology.com \
    /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).