From: Ricardo Wurmus <rekado@elephly.net>
To: guix-devel@gnu.org
Subject: build system option to allow CPU optimizations?
Date: Wed, 24 Nov 2021 13:10:03 +0100 [thread overview]
Message-ID: <87ilwhu4zi.fsf@elephly.net> (raw)
Hi Guix,
currently we patch source code and build systems to ensure that no
special instructions are used that would not be portable,
e.g. AVX2, SSE4.1 etc. What do you think of adding a build system
option that would allow users to restore these optimizations?
The build phases that patch out these features would have to check
for that build system option, much like they check the TESTS?
option before attempting to run tests.
What do you think?
--
Ricardo
next reply other threads:[~2021-11-24 12:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-24 12:10 Ricardo Wurmus [this message]
2021-11-26 0:07 ` build system option to allow CPU optimizations? zimoun
2021-11-28 17:36 ` Ludovic Courtès
2021-11-28 18:20 ` Ricardo Wurmus
2021-12-20 17:40 ` Ludovic Courtès
2021-12-14 3:36 ` Maxim Cournoyer
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=87ilwhu4zi.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guix-devel@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 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).