public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Martin Liška" <mliska@suse.cz>
To: Xi Ruoyao <xry111@xry111.site>, Joseph Myers <joseph@codesourcery.com>
Cc: Sam James <sam@gentoo.org>,
	gcc-patches@gcc.gnu.org, Gerald Pfeifer <gerald@pfeifer.com>,
	Jakub Jelinek <jakub@redhat.com>,
	Jeff Law <jlaw@ventanamicro.com>
Subject: Re: [PATCH] maintainer-scripts/gcc_release: compress xz in parallel
Date: Thu, 10 Nov 2022 15:16:05 +0100	[thread overview]
Message-ID: <ba2456ef-455c-1fda-79b7-3bdf0b17963c@suse.cz> (raw)
In-Reply-To: <6e2f0c0dd7cfe1b4abe5ddcc08e45e984ccbe61f.camel@xry111.site>

On 11/9/22 03:06, Xi Ruoyao via Gcc-patches wrote:
> On Wed, 2022-11-09 at 01:52 +0000, Joseph Myers wrote:
>> On Tue, 8 Nov 2022, Xi Ruoyao via Gcc-patches 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.
>>
>> gcc_release definitely doesn't use any options to make the tar file
>> reproducible (the timestamps, user and group names and ordering of the
>> files in the tarball, and quite likely permissions other than whether a
>> file has execute permission, may depend on when the script was run and on
>> what system as what user - not just on the commit from which the tar file
>> was built).  So I don't think possible variation of xz output matters here
>> at present.
> 
> OK then.  I'm already using commands like
> 
> git archive --format=tar --prefix=gcc-$(git gcc-descr HEAD)/ HEAD | xz -T0 > ../gcc-$(git gcc-descr HEAD).tar.xz
> 
> when I generate a GCC snapshot tarball for my own use.
> 
> 

Hi.

We may consider using zstd compression that also support a multi-threaded compression
(which is stable). Note the decompression of zstd is much faster than xz.

Martin

  reply	other threads:[~2022-11-10 14:16 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
2022-11-09  1:52   ` Joseph Myers
2022-11-09  2:06     ` Xi Ruoyao
2022-11-10 14:16       ` Martin Liška [this message]
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=ba2456ef-455c-1fda-79b7-3bdf0b17963c@suse.cz \
    --to=mliska@suse.cz \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gerald@pfeifer.com \
    --cc=jakub@redhat.com \
    --cc=jlaw@ventanamicro.com \
    --cc=joseph@codesourcery.com \
    --cc=sam@gentoo.org \
    --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).