public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Sam James <sam@gentoo.org>
To: Mark Wielaard <mark@klomp.org>
Cc: binutils@sourceware.org,  gdb-patches@sourceware.org
Subject: Re: [PATCH] src-release.sh: Use -T0 for xz compression
Date: Thu, 30 May 2024 22:56:50 +0100	[thread overview]
Message-ID: <87le3rdkv1.fsf@gentoo.org> (raw)
In-Reply-To: <20240530214331.1545787-1-mark@klomp.org> (Mark Wielaard's message of "Thu, 30 May 2024 23:43:31 +0200")

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

Mark Wielaard <mark@klomp.org> writes:

> Use parallel compression to create the xz archive.
>
> On my machine (using 4 cores) this reduces the time to create
> binutils-2.42.50.tar.xz from 1 minute 40 seconds to 56 seconds.
>
> xz has supported -T0 since version 5.2.0 (released 2014-12-21).

LGTM and it's the default from >=5.6.0 anyway. For >=5.4.0, you can use
it for parallel *de*compression too.

> ---
>  src-release.sh | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/src-release.sh b/src-release.sh
> index e454893298da..f29362aac207 100755
> --- a/src-release.sh
> +++ b/src-release.sh
> @@ -239,7 +239,7 @@ do_xz()
>      ver=$2
>      echo "==> Xzipping $package-$ver.tar.xz"
>      rm -f $package-$ver.tar.xz
> -    $XZPROG -k -v -9 $package-$ver.tar
> +    $XZPROG -k -v -9 -T0 $package-$ver.tar
>  }
>  
>  # Compress the output with zstd

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 377 bytes --]

  reply	other threads:[~2024-05-30 21:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-30 21:43 Mark Wielaard
2024-05-30 21:56 ` Sam James [this message]
2024-05-30 21:59   ` Sam James
2024-05-31  6:09   ` Eli Zaretskii
2024-05-31 12:54     ` Sam James
2024-06-03  9:36   ` Mark Wielaard

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=87le3rdkv1.fsf@gentoo.org \
    --to=sam@gentoo.org \
    --cc=binutils@sourceware.org \
    --cc=gdb-patches@sourceware.org \
    --cc=mark@klomp.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 read-only IMAP folder(s) and NNTP newsgroup(s).