all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludovic.courtes@inria.fr>
To: "Léo Le Bouter" <lle-bout@zaclys.net>
Cc: 47218@debbugs.gnu.org
Subject: bug#47218: glibc 2.33's HWCAPS and GCC Function Multiversioning for performance
Date: Thu, 18 Mar 2021 14:17:42 +0100	[thread overview]
Message-ID: <87lfakr47d.fsf@gnu.org> (raw)
In-Reply-To: <f63bb1764b53c6b5c7e959281d522cd0c24bd8f3.camel@zaclys.net> ("Léo Le Bouter"'s message of "Wed, 17 Mar 2021 19:59:51 +0100")

Hi Léo,

Léo Le Bouter <lle-bout@zaclys.net> skribis:

> Please see:
> - 
> https://www.gnu.org/software/libc/manual/html_mono/libc.html#Hardware-Capability-Tunables
> - https://www.phoronix.com/scan.php?page=news_item&px=glibc-hwcaps-RFC
> - https://gcc.gnu.org/onlinedocs/gcc/Function-Multiversioning.html
>
> This could help GNU Guix create binaries that include multiple code
> paths for several CPU features in the same binary and selecting the
> best at runtime when the binary is run.
>
> It is the best fit for GNU Guix because it means we can still use
> substitutes and profit from specialized optimizations without
> parameterized packages or each user adding "-march=native" to CFLAGS
> (breaking reproducibility).

For the record, we are well aware of these features and follow this very
closely in particular in the context of Guix-HPC:

  https://hpc.guix.info/blog/2018/01/pre-built-binaries-vs-performance/

It seems to me that this bug report is not actionable though.  Unless
there are concrete steps you’d like to suggest, I propose to close this
issue.

Thanks,
Ludo’.




      reply	other threads:[~2021-03-18 13:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-17 18:59 bug#47218: glibc 2.33's HWCAPS and GCC Function Multiversioning for performance Léo Le Bouter via Bug reports for GNU Guix
2021-03-18 13:17 ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87lfakr47d.fsf@gnu.org \
    --to=ludovic.courtes@inria.fr \
    --cc=47218@debbugs.gnu.org \
    --cc=lle-bout@zaclys.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 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.