From: Ben Woodcroft <b.woodcroft@uq.edu.au>
To: Ricardo Wurmus <rekado@elephly.net>, guix-devel <guix-devel@gnu.org>
Subject: Re: Optionally using more advanced CPU features
Date: Sat, 26 Aug 2017 11:39:41 +0800 [thread overview]
Message-ID: <19eb4906-44d1-723b-94ba-9ab86dfbedf5@uq.edu.au> (raw)
In-Reply-To: <87inhhw1ms.fsf@elephly.net>
[-- Attachment #1: Type: text/plain, Size: 1292 bytes --]
Hi,
On 21/08/17 22:23, Ricardo Wurmus wrote:
> Hi Guix,
>
> I was wondering how we should go about optionally building software for
> more advanced CPU features. Currently, we build software for the lowest
> common feature set among x86_64 CPUs. That’s good for portability, but
> not so good for performance.
In many cases we can set the --with-arch flag when configuring GCC, so
that packages built with that GCC are optimised for that architecture by
default.
We have discussed this in the past,
(https://lists.gnu.org/archive/html/guix-devel/2016-10/msg00005.html)
but as you say individual packages sometimes need individual attention.
Anyway, to move forward I created a repo so that package recipes can be
modified to use a GCC that has been optimised for a particular
architecture. I put it out there so that it is more than just a patch on
this ML, but I'd be happy to incorporate it into Guix proper if that is
desired.
https://github.com/wwood/cpu-specific-guix
For instance, to build DIAMOND optimised for sandybridge:
GUILE_LOAD_PATH=/path/to/cpu-specific-guix:$GUILE_LOAD_PATH\ |guix build -e '(begin (use-modules (cpu-specific-guix) (gnu packages
bioinformatics))\ (cpu-specific-package diamond "sandybridge"))'|
HTH, ben
[-- Attachment #2: Type: text/html, Size: 2017 bytes --]
next prev parent reply other threads:[~2017-08-26 3:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-21 12:23 Optionally using more advanced CPU features Ricardo Wurmus
2017-08-22 9:21 ` Ludovic Courtès
2017-08-23 13:59 ` Dave Love
2017-08-28 13:48 ` Ludovic Courtès
2017-09-01 10:46 ` Dave Love
2017-09-04 12:38 ` Ludovic Courtès
2017-09-07 15:51 ` Packaging BLIS Ludovic Courtès
2017-09-08 22:36 ` Dave Love
2017-09-11 7:12 ` Ludovic Courtès
2017-08-26 3:39 ` Ben Woodcroft [this message]
2017-08-26 5:14 ` Optionally using more advanced CPU features Pjotr Prins
2017-09-04 14:50 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19eb4906-44d1-723b-94ba-9ab86dfbedf5@uq.edu.au \
--to=b.woodcroft@uq.edu.au \
--cc=guix-devel@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.