From: ludo@gnu.org (Ludovic Courtès)
To: Dave Love <fx@gnu.org>
Cc: 29810@debbugs.gnu.org
Subject: [bug#29810] gnu: maths: Fix cache size detected by openblas on some
Date: Mon, 08 Jan 2018 10:43:45 +0100 [thread overview]
Message-ID: <87zi5oit2m.fsf@gnu.org> (raw)
In-Reply-To: <87r2rm29dy.fsf@albion.it.manchester.ac.uk> (Dave Love's message of "Fri, 22 Dec 2017 13:13:29 +0000")
Hi Dave,
Dave Love <fx@gnu.org> skribis:
> This addresses a potential performance problem, fixed in the post-0.2.20
> source. It's intended for application to a package definition updated
> to 0.2.20, which Ludo said is in the pipeline. Apologies that I don't
> seem to have converged on an acceptable style for changes.
>
>>From 23ad3a438ef7bcd34e2354f6cbdede634f0188d4 Mon Sep 17 00:00:00 2001
> From: Dave Love <fx@gnu.org>
> Date: Fri, 22 Dec 2017 12:48:29 +0000
> Subject: [PATCH 1/2] gnu: maths: Fix cache size detected by openblas on some
> x86_64.
>
> * gnu/packages/patches/openblas-Add-dummy-implementation-of-cpuid_count-for-the-CPUI.patch,
> gnu/packages/patches/openblas-Use-cpuid-4-with-subleafs-to-query-L1-cache-size-on-.patch:
> New files.
> * gnu/packages/maths.scm (openblas)[source]: Use them.
> * gnu/local.mk: Register them.
Thanks for the patch. Given the number of dependents, we would not push
it in master (info "(guix) Submitting Patches"). At the same time,
since 0.2.20 is in core-updates and well on its way, do you think we
should keep those patches?
Perhaps in core-updates we could keep both 0.2.19 with these patches and
0.2.20 (ISTR you said there were incompatibilities between these two
versions)? Would it make sense?
Thanks,
Ludo’.
next prev parent reply other threads:[~2018-01-08 9:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-22 13:13 [bug#29810] gnu: maths: Fix cache size detected by openblas on some Dave Love
2018-01-08 9:43 ` Ludovic Courtès [this message]
2019-02-12 23:21 ` bug#29810: " Leo Famulari
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=87zi5oit2m.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=29810@debbugs.gnu.org \
--cc=fx@gnu.org \
/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.