public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Sam James <sam@gentoo.org>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Xi Ruoyao <xry111@xry111.site>,
	gcc-patches@gcc.gnu.org, Gerald Pfeifer <gerald@pfeifer.com>,
	Jeff Law <jlaw@ventanamicro.com>
Subject: Re: [PATCH] maintainer-scripts/gcc_release: compress xz in parallel
Date: Tue, 8 Nov 2022 08:53:57 +0000	[thread overview]
Message-ID: <2DD8DF6B-0280-488E-9B02-E2CE815517CD@gentoo.org> (raw)
In-Reply-To: <Y2oYxo2OudVmMn1L@tucnak>

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



> On 8 Nov 2022, at 08:52, Jakub Jelinek <jakub@redhat.com> wrote:
> 
> On Tue, Nov 08, 2022 at 07:40:02AM +0000, Sam James wrote:
>>> On 8 Nov 2022, at 07:33, Xi Ruoyao <xry111@xry111.site> wrote:
>>> I'm wondering if running xz -T0 on different machines (with different
>>> core numbers) may produce different compressed data.  The difference can
>>> cause trouble distributing checksums.
>>> 
>> 
>> Your question is a good one - xz -T0 produces different results to xz -T1
>> but:
>> 1. The tarballs for GCC are only created on one machine and aren't
>> created repeatedly then compared with each other wrt mirroring;
> 
> No, that is not the case.
> While the snapshots are created on sourceware locally, GCC releases (and
> release candidates) are typically created on some RM's local machine.

We've misinterpreted each other. I mean the same tarball isn't then
recreated repeatedly and different copies uploaded to mirrors.

Obviously different machines may be used at different points.

[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 358 bytes --]

  reply	other threads:[~2022-11-08  8:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-08  7:14 Sam James
2022-11-08  7:33 ` Xi Ruoyao
2022-11-08  7:40   ` Sam James
2022-11-08  8:52     ` Jakub Jelinek
2022-11-08  8:53       ` Sam James [this message]
2022-11-09  1:52   ` Joseph Myers
2022-11-09  2:06     ` Xi Ruoyao
2022-11-10 14:16       ` Martin Liška
2022-11-08  7:34 ` Eric Botcazou
2022-11-08  7:36   ` Sam James
2022-11-08  7:45     ` Sam James
2022-11-11 21:48 ` Sam James
2022-11-22 11:54   ` Richard Sandiford
2022-11-17 17:42 ` Sam James

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=2DD8DF6B-0280-488E-9B02-E2CE815517CD@gentoo.org \
    --to=sam@gentoo.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gerald@pfeifer.com \
    --cc=jakub@redhat.com \
    --cc=jlaw@ventanamicro.com \
    --cc=xry111@xry111.site \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).