all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: 69581@debbugs.gnu.org
Subject: [bug#69581] [PATCH 07/11] gnu: rust: Add tuning information.
Date: Fri, 08 Mar 2024 22:57:03 +0100	[thread overview]
Message-ID: <87y1as2xqo.fsf@gnu.org> (raw)
In-Reply-To: <Zer_IsCoOrBYZMKO@3900XT> (Efraim Flashner's message of "Fri, 8 Mar 2024 14:05:54 +0200")

Hi,

Efraim Flashner <efraim@flashner.co.il> skribis:

> On Thu, Mar 07, 2024 at 10:38:06PM +0100, Ludovic Courtès wrote:

[...]

>> Then it should be declared in a module that’s not in a cycle with its
>> users (that’s annoying!).  Maybe a separate ‘llvm-meta.scm’?
>
> How about moving it into (guix cpu) together with the ones from gcc?
> There are apparently some CPUs that are identical but have different
> names that we could map together and would allow us to make any changes
> to them in one place.  We've already pretty much done that with the
> search paths.

To me, the whole point of the ‘compiler-cpu-architectures’ property is
that this info can be stored in the compiler package itself rather than
in some remote unrelated place (the same goes for search paths).  My
instinct would be to preserve that, hence the suggestion of a new (gnu
packages llvm-meta) or (… llvm-infra) module, something like that.

We should also keep in mind that those CPU names are those defined by
compilers themselves; they don’t have to match the vendor-chosen name or
the name chosen by some other compiler.

WDYT?  Does that make sense?

Ludo’.




  reply	other threads:[~2024-03-08 22:22 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-06 11:03 [bug#69581] [PATCH 00/11] CPU tuning patches Efraim Flashner
2024-03-06 11:06 ` [bug#69581] [PATCH 01/11] gnu: opus: Mark as tunable Efraim Flashner
2024-03-06 17:49   ` Ludovic Courtès
2024-03-06 11:06 ` [bug#69581] [PATCH 02/11] gnu: libvorbis: " Efraim Flashner
2024-03-06 11:06 ` [bug#69581] [PATCH 03/11] guix: cpu: Be consistent with x86_64 micro-architecture names Efraim Flashner
2024-03-06 17:53   ` Ludovic Courtès
2024-03-07  9:11     ` Efraim Flashner
2024-03-06 11:06 ` [bug#69581] [PATCH 04/11] guix: cpu: Rename x86-64-v1 to x86-64 Efraim Flashner
2024-03-06 17:59   ` Ludovic Courtès
2024-03-06 11:06 ` [bug#69581] [PATCH 05/11] guix: cpu: Enable tuning for i686-linux Efraim Flashner
2024-03-06 18:05   ` Ludovic Courtès
2024-03-07  9:09     ` Efraim Flashner
2024-03-06 11:06 ` [bug#69581] [PATCH 06/11] gnu: syncthing: Mark as tunable Efraim Flashner
2024-03-06 18:06   ` Ludovic Courtès
2024-03-07  9:09     ` Efraim Flashner
2024-03-06 11:06 ` [bug#69581] [PATCH 07/11] gnu: rust: Add tuning information Efraim Flashner
2024-03-06 18:09   ` Ludovic Courtès
2024-03-07  9:09     ` Efraim Flashner
2024-03-06 18:10   ` Ludovic Courtès
2024-03-07  9:10     ` Efraim Flashner
2024-03-07 21:38       ` Ludovic Courtès
2024-03-08 12:05         ` Efraim Flashner
2024-03-08 21:57           ` Ludovic Courtès [this message]
2024-03-10  8:26             ` Efraim Flashner
2024-03-06 11:06 ` [bug#69581] [PATCH 08/11] transformations: Add support for rust Efraim Flashner
2024-03-06 18:11   ` Ludovic Courtès
2024-03-06 11:06 ` [bug#69581] [PATCH 09/11] gnu: rav1e: Mark as tunable Efraim Flashner
2024-03-06 11:06 ` [bug#69581] [PATCH 10/11] gnu: clang-properties: Update x86_64 micro-architectures Efraim Flashner
2024-03-06 18:12   ` Ludovic Courtès
2024-03-07  9:10     ` Efraim Flashner
2024-03-07 21:42       ` Ludovic Courtès
2024-03-08 12:07         ` Efraim Flashner
2024-03-07  9:12     ` Efraim Flashner
2024-03-06 11:06 ` [bug#69581] [PATCH 11/11] gnu: clang-properties: Add micro-architecture support for powerpc64le Efraim Flashner
2024-03-06 18:12   ` Ludovic Courtès
     [not found] ` <handler.69581.B.170972307319660.ack@debbugs.gnu.org>
2024-03-10 10:51   ` bug#69581: Acknowledgement ([PATCH 00/11] CPU tuning patches) Efraim Flashner

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=87y1as2xqo.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=69581@debbugs.gnu.org \
    --cc=efraim@flashner.co.il \
    /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.