From: "Ludovic Courtès" <ludo@gnu.org>
To: raingloom <raingloom@riseup.net>
Cc: 65903@debbugs.gnu.org
Subject: [bug#65903] [PATCH v2] gnu: Make vice tunable.
Date: Sun, 17 Sep 2023 12:05:10 +0200 [thread overview]
Message-ID: <871qex15ex.fsf@gnu.org> (raw)
In-Reply-To: <6fc797b4ee3c49cb7fb730b4ba1664a733ebf0df.1694720820.git.raingloom@riseup.net> (raingloom@riseup.net's message of "Thu, 14 Sep 2023 21:47:00 +0200")
Hi,
raingloom <raingloom@riseup.net> skribis:
> From: Csepp <raingloom@riseup.net>
>
> * gnu/packages/emulators.scm (vice)[properties]: Set tunable? to #t.
> ---
> gnu/packages/emulators.scm | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/gnu/packages/emulators.scm b/gnu/packages/emulators.scm
> index 1d50c9ef01..0fb4a5853b 100644
> --- a/gnu/packages/emulators.scm
> +++ b/gnu/packages/emulators.scm
> @@ -118,6 +118,8 @@ (define-public vice
> (package
> (name "vice")
> (version "3.7.1")
> + ;; without this it would use AVX even when it's not suported:
Oh I see. It’s a problem that ‘tunable?’ in itself doesn’t solve.
The fix would be twofold: (1) remove ‘-march’ and similar compiler
arguments that cause it to generate code that assumes AVX availability,
and (2) add the ‘tune?’ property for those who want a fine-tuned binary.
Could you look into it?
Thanks,
Ludo’.
next prev parent reply other threads:[~2023-09-17 10:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-13 3:48 [bug#65903] [PATCH] gnu: Make vice tunable raingloom
2023-09-14 19:47 ` [bug#65903] [PATCH v2] " raingloom
2023-09-17 10:05 ` Ludovic Courtès [this message]
2023-09-18 12:17 ` Csepp
2023-09-19 9:45 ` 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
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=871qex15ex.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=65903@debbugs.gnu.org \
--cc=raingloom@riseup.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 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).