public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Sam James <sam@gentoo.org>
To: gcc-patches@gcc.gnu.org
Cc: 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: Fri, 11 Nov 2022 21:48:19 +0000	[thread overview]
Message-ID: <E29B8510-6E5A-4E5E-8F8A-03809A3E97DC@gentoo.org> (raw)
In-Reply-To: <20221108071438.2523863-1-sam@gentoo.org>

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



> On 8 Nov 2022, at 07:14, Sam James <sam@gentoo.org> wrote:
> 
> 1. This should speed up decompression for folks, as parallel xz
>   creates a different archive which can be decompressed in parallel.
> 
>   Note that this different method is enabled by default in a new
>   xz release coming shortly anyway (>= 5.3.3_alpha1).
> 
>   I build GCC regularly from the weekly snapshots
>   and so the decompression time adds up.
> 
> 2. It should speed up compression on the webserver a bit.
> 
>   Note that -T0 won't be the default in the new xz release,
>   only the parallel compression mode (which enables parallel
>   decompression).
> 
>   -T0 detects the number of cores available.
> 
>   So, if a different number of threads is preferred, it's fine
>   to set e.g. -T2, etc.
> 
> Signed-off-by: Sam James <sam@gentoo.org>
> ---
> maintainer-scripts/gcc_release | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
> 
> 

Given no disagreements, anyone fancy pushing
this in time for Sunday evening for the next 13
snapshot? ;)


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

  parent reply	other threads:[~2022-11-11 21:48 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
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 [this message]
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=E29B8510-6E5A-4E5E-8F8A-03809A3E97DC@gentoo.org \
    --to=sam@gentoo.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gerald@pfeifer.com \
    --cc=jakub@redhat.com \
    --cc=jlaw@ventanamicro.com \
    /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).