From: Efraim Flashner <efraim@flashner.co.il>
To: Julien Lepiller <julien@lepiller.eu>
Cc: 55431-done@debbugs.gnu.org
Subject: [bug#55431] [PATCH] guix: cpu: recognize other architectures.
Date: Wed, 18 May 2022 15:05:38 +0300 [thread overview]
Message-ID: <YoThEsqvlKoj5T5o@3900XT> (raw)
In-Reply-To: <005DC196-6142-48CF-A82E-D532D6500597@lepiller.eu>
[-- Attachment #1: Type: text/plain, Size: 982 bytes --]
On Tue, May 17, 2022 at 05:55:38PM +0200, Julien Lepiller wrote:
> Thanks for fixing that anyway :)
>
> I was only interested in it because it made me unable to reconfigure my systems. I don't care too much about the --tune code, and I don't understand what you suggest. Do you mean to create "x86 on x86_64" as a separate architecture? Or as a --tune target?
>
As part of the autotuning process. GCC internally groups i686 and x86_64
together when determining how to tune for --march=native, and I'm pretty
sure I've added some i686 hardware for AMD when I was adding autotuning
support for AMD CPUs. Its similar for aarch64 and armhf, there are armhf
targets internally that accept armv8.X-a targets, so there's no need to
limit armhf tuning to armv7.
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2022-05-18 12:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-15 17:11 [bug#55431] [PATCH] guix: cpu: recognize other architectures Julien Lepiller
2022-05-17 12:59 ` bug#55431: " Efraim Flashner
2022-05-17 15:55 ` [bug#55431] " Julien Lepiller
2022-05-18 12:05 ` Efraim Flashner [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YoThEsqvlKoj5T5o@3900XT \
--to=efraim@flashner.co.il \
--cc=55431-done@debbugs.gnu.org \
--cc=julien@lepiller.eu \
/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.