Github messages for voidlinux
 help / color / mirror / Atom feed
From: sternenseemann <sternenseemann@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: foot: Add PGO build option
Date: Fri, 02 Jul 2021 10:05:31 +0200	[thread overview]
Message-ID: <20210702080531.Xv2w8WSmPFb98CKR5Hoz87hE2LksveUTjzvYqCZ3EiY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29526@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 840 bytes --]

New comment by sternenseemann on void-packages repository

https://github.com/void-linux/void-packages/issues/29526#issuecomment-872803985

Comment:
I can confirm that building foot with PGO can be reproducible, i. e. I can reproduce the exact hash of the binary package produced by our builders on two different local machines (at different times). This also leads me to [believe that a reproducible gcc with PGO is possible](https://github.com/NixOS/nixpkgs/pull/112928#issuecomment-809336063), but most likely very hard to get to work.

The only thing necessary to achieve a reproducible foot build is generating the random inputs which are used for profiling while building using a [fixed seed](https://github.com/NixOS/nixpkgs/blob/43b257365c2c73fc31421e9b28dde1166d75506a/pkgs/applications/terminal-emulators/foot/default.nix#L62).

  parent reply	other threads:[~2021-07-02  8:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-17  8:17 [ISSUE] " travankor
2021-04-27 23:49 ` ericonr
2021-07-02  6:02 ` dnkl
2021-07-02  8:05 ` sternenseemann
2021-07-02  8:05 ` sternenseemann [this message]
2022-05-09  2:13 ` github-actions
2022-05-10  2:44 ` ericonr
2022-05-10 11:10 ` ifreund
2022-08-09  2:13 ` github-actions
2022-08-24  2:14 ` [ISSUE] [CLOSED] " github-actions

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=20210702080531.Xv2w8WSmPFb98CKR5Hoz87hE2LksveUTjzvYqCZ3EiY@z \
    --to=sternenseemann@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).