From: Leo Prikler <leo.prikler@student.tugraz.at>
To: elaexuotee@wilsonb.com
Cc: guix-devel@gnu.org
Subject: Installing a wrapper guile script in <out>/bin
Date: Mon, 01 Feb 2021 13:16:10 +0100 [thread overview]
Message-ID: <c2356a81950053d3fc41342210c8ec06f1ac1b5b.camel@student.tugraz.at> (raw)
In-Reply-To: 3EA9135IVLYXR.223U6JDXT4SSS@wilsonb.com
Hi elaexuotee,
> More specifically, the package I have builds separate libraries for
> CPUs with
> AVX, AVX2, and no AVX support. Since build-type isn't sufficiently
> specific to
> distinguish such CPU features, I have, so far, opted to just build
> all three
> libs and stuff them under <out>/lib/<foo>.
That's certainly one approach to solving the issue of not knowing which
CPU your code runs on. Another approach is described in [1] under the
section "Dependency graph rewriting". TL;DR, just offer the base
package with no AVX features, an AVX package and an AVX2 package. Then
build any dependants against the base package. Users can afterwards
decide to build against optimized versions on their own.
Regards,
Leo
[1]
https://hpc.guix.info/blog/2018/01/pre-built-binaries-vs-performance/
next reply other threads:[~2021-02-01 12:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-01 12:16 Leo Prikler [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-02-01 11:28 Installing a wrapper guile script in <out>/bin elaexuotee
2021-02-01 16:04 ` Ludovic Courtès
2021-02-03 5:50 ` elaexuotee
2021-02-03 10:00 ` Maxime Devos
2021-02-03 11:04 ` elaexuotee--- via Development of GNU Guix and the GNU System distribution.
2021-02-03 12:12 ` Maxime Devos
2021-02-03 19:17 ` elaexuotee
2021-02-04 8:56 ` Maxime Devos
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=c2356a81950053d3fc41342210c8ec06f1ac1b5b.camel@student.tugraz.at \
--to=leo.prikler@student.tugraz.at \
--cc=elaexuotee@wilsonb.com \
--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).