unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: 51536@debbugs.gnu.org
Subject: bug#51536: openblas builds not reproducible on different x86_64 machines
Date: Wed, 3 Nov 2021 16:03:04 +0100	[thread overview]
Message-ID: <CAJ3okZ2H=_MuXqU4_NjqC0LSZqi9pLJBDr+xN6pZ25zWnpzvFQ@mail.gmail.com> (raw)
In-Reply-To: <87h7cw7ewb.fsf@gmail.com>

 Hi Maxim,

On Mon, 1 Nov 2021 at 04:08, Maxim Cournoyer <maxim.cournoyer@gmail.com> wrote:

> Our OpenBLAS package uses DYNAMIC_ARCH=1 to provide optimizations for
> all supported targets, at least of x86 and x86_64.  In theory that seems
> OK, but in practice the builds differ depending on the host CPU.
>
> I've made a build on an old Core2 CPU (Q6700), and another one on
> Berlin.  I've run diffoscope on the result, and got tons of differences;
> here's the tail of the diffoscope output:

Well, it rings this bell [1] and this one [2] too. ;-)

Maybe I am wrong, but speaking about HPC, it seems expected that the
builds differ depending on the host CPU and I am not convinced we can
do better than DYNAMIC_ARCH=1 for performances which somehow sacrifice
reproducibility, IIUC.

1: <https://hpc.guix.info/blog/2018/01/pre-built-binaries-vs-performance/>
2: <https://hpc.guix.info/blog/2019/12/optimized-and-portable-open-mpi-packaging/>


Cheers,
simon




  parent reply	other threads:[~2021-11-03 15:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-01  3:07 bug#51536: openblas builds not reproducible on different x86_64 machines Maxim Cournoyer
2021-11-01  8:54 ` Efraim Flashner
2021-11-05 16:38   ` Maxim Cournoyer
2021-11-07  2:33   ` Maxim Cournoyer
2021-11-03 15:03 ` zimoun [this message]
2022-02-02 23:13 ` 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='CAJ3okZ2H=_MuXqU4_NjqC0LSZqi9pLJBDr+xN6pZ25zWnpzvFQ@mail.gmail.com' \
    --to=zimon.toutoune@gmail.com \
    --cc=51536@debbugs.gnu.org \
    --cc=maxim.cournoyer@gmail.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).