From: Konrad Hinsen <konrad.hinsen@fastmail.net>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: Guix Devel <guix-devel@gnu.org>, zimoun <zimon.toutoune@gmail.com>
Subject: Re: Investigating a reproducibility failure
Date: Thu, 03 Feb 2022 18:05:43 +0100 [thread overview]
Message-ID: <m1o83n6ftk.fsf@fastmail.net> (raw)
In-Reply-To: <87a6f8415g.fsf@elephly.net>
Hi Ricardo and Simon,
Ricardo Wurmus <rekado@elephly.net> writes:
> The case of OpenBLAS is an anomaly in that this mechanism seems to
> produce different binaries dependent on where it is built. When I first
Thanks a lot for those explanations, I hadn't realized how peculiar
OpenBLAS is!
> Your problem is that the OpenBLAS build system doesn’t recognize your
> modern CPU. Ideally, it wouldn’t need to know anything about the
> build-time CPU to build all the different code paths for different CPU
> features. The only way around this — retroactively — is to pretend to
> have an older CPU, e.g. by using qemu.
So all we need is a "QEMU build system" in Guix, just for OpenBLAS ;-)
> The new “--tune” feature is supposed to take care of cases like this.
Right, I remember Ludo's blog post about this.
zimoun <zimon.toutoune@gmail.com> writes:
> Somehow, “recent” processors cannot build old versions.
That's a whole new level of planned obsolescence!
Cheers,
Konrad.
next prev parent reply other threads:[~2022-02-03 17:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-02 20:35 Investigating a reproducibility failure zimoun
2022-02-02 23:43 ` zimoun
2022-02-03 9:16 ` Konrad Hinsen
2022-02-03 11:41 ` Ricardo Wurmus
2022-02-03 17:05 ` Konrad Hinsen [this message]
2022-02-03 12:07 ` zimoun
2022-02-05 14:12 ` Ludovic Courtès
2022-02-15 14:10 ` Bengt Richter
2022-02-16 12:03 ` zimoun
2022-02-16 13:04 ` Konrad Hinsen
2022-02-17 11:21 ` zimoun
2022-02-17 16:55 ` Konrad Hinsen
-- strict thread matches above, loose matches on Subject: below --
2022-02-01 14:05 Konrad Hinsen
2022-02-01 14:30 ` Konrad Hinsen
2022-02-02 23:19 ` Ricardo Wurmus
2022-02-02 23:36 ` Ricardo Wurmus
2022-02-05 14:05 ` Ludovic Courtès
2022-02-08 5:57 ` Konrad Hinsen
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=m1o83n6ftk.fsf@fastmail.net \
--to=konrad.hinsen@fastmail.net \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
--cc=zimon.toutoune@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).