From: "Ludovic Courtès" <ludo@gnu.org>
To: Csepp <raingloom@riseup.net>
Cc: 65903@debbugs.gnu.org
Subject: [bug#65903] [PATCH v2] gnu: Make vice tunable.
Date: Tue, 19 Sep 2023 11:45:44 +0200 [thread overview]
Message-ID: <87il86ebsn.fsf@gnu.org> (raw)
In-Reply-To: <cuc5y47ptao.fsf@riseup.net> (Csepp's message of "Mon, 18 Sep 2023 14:17:25 +0200")
Hi,
Csepp <raingloom@riseup.net> skribis:
> Ludovic Courtès <ludo@gnu.org> writes:
[...]
>> 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’.
>
> Umm, it definitely solved it on my machine, which doesn't have AVX.
> If that's not a "proper" fix, then sure, I can try looking into it more.
> But it seems to me like `tunable?` is already working as intended.
What I meant is that someone installing ‘vice’ without ‘--tune’ will
still get a binary that assumes AVXsomething, which may or may not work
on their machine.
The default binary (without ‘--tune’) should target baseline x86_64.
That’s why we need both fixes I mentioned above.
HTH!
Ludo’.
prev parent reply other threads:[~2023-09-19 9:47 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
2023-09-18 12:17 ` Csepp
2023-09-19 9:45 ` Ludovic Courtès [this message]
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=87il86ebsn.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).