From: "Ludovic Courtès" <ludo@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 52001@debbugs.gnu.org
Subject: bug#52001: numpy CPU dispatch probably prevents builds of python-numpy from being reproducible
Date: Fri, 10 Dec 2021 23:42:41 +0100 [thread overview]
Message-ID: <87y24s5bfi.fsf@gnu.org> (raw)
In-Reply-To: <87y25ihm3e.fsf@elephly.net> (Ricardo Wurmus's message of "Sat, 20 Nov 2021 15:36:57 +0000")
Hi,
Ricardo Wurmus <rekado@elephly.net> skribis:
> Numpy accelerates operations with native code. Early in the build it
> probes the CPU / compiler for supported instruction extensions and
> then proceeds to build extensions for different features. I’m
> guessing that this won’t work when building on older CPUs, so the
> results of two builds on different CPUs may differ.
I don’t see anything in the build log that suggests it might be building
for a specific ISA extension (on x86_64).
On the contrary, it seems to do the right thing by dispatching to the
right optimized implementation at run time, in numpy/core/src/umath.
Apparently this directory contains templates for home-made function
multi-versioning, with variants and dispatch code generated by
numpy/core/code_generators/generate_umath.py.
Besides, I see the same .pyc difference as Maxime, but I don’t think it
relates to ISA extensions.
Ludo’.
prev parent reply other threads:[~2021-12-10 22:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-20 15:36 bug#52001: numpy CPU dispatch probably prevents builds of python-numpy from being reproducible Ricardo Wurmus
2021-11-20 16:26 ` Maxime Devos
2021-12-10 22:42 ` Ludovic Courtès [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y24s5bfi.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=52001@debbugs.gnu.org \
--cc=rekado@elephly.net \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.