From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: python3: enable optimizations.
Date: Thu, 11 May 2023 16:25:52 +0200 [thread overview]
Message-ID: <20230511142552.BimDra3umVzqnR3Bucg3t4hVNRdzRGE-UhHIiVnjXJg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43791@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 535 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/pull/43791#issuecomment-1544084463
Comment:
Sorry for the delay. I don't really have a problem with enabling optimizations; if they improve runtime performance, we can pay the price in compile time. The question is how much PGO makes improves things for the average user if the optimization is tailored to the build system. I'd like to test a few things, including building on different CPUs to see how well the optimizations translate.
next prev parent reply other threads:[~2023-05-11 14:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-07 16:51 [PR PATCH] " mhmdanas
2023-05-11 14:25 ` ahesford [this message]
2023-05-12 12:10 ` tornaria
2023-08-08 18:40 ` [PR PATCH] [Updated] " mhmdanas
2023-08-13 13:10 ` ahesford
2023-08-13 13:11 ` [PR PATCH] [Closed]: " ahesford
2023-08-14 12:55 ` tornaria
2023-08-14 12:56 ` tornaria
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=20230511142552.BimDra3umVzqnR3Bucg3t4hVNRdzRGE-UhHIiVnjXJg@z \
--to=ahesford@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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.
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 NNTP newsgroup(s).