public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Richard Sandiford <rsandifo@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r13-4261] maintainer-scripts/gcc_release: compress xz in parallel
Date: Wed, 23 Nov 2022 09:53:59 +0000 (GMT) [thread overview]
Message-ID: <20221123095359.65500385456D@sourceware.org> (raw)
https://gcc.gnu.org/g:2650b6f9147c0d855c2763610b8a4bff18f5b5e0
commit r13-4261-g2650b6f9147c0d855c2763610b8a4bff18f5b5e0
Author: Sam James <sam@gentoo.org>
Date: Tue Nov 8 07:14:38 2022 +0000
maintainer-scripts/gcc_release: compress xz in parallel
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>
* gcc_release (XZ): Add -T0.
Diff:
---
maintainer-scripts/gcc_release | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/maintainer-scripts/gcc_release b/maintainer-scripts/gcc_release
index 2456908d716..962b8efe99a 100755
--- a/maintainer-scripts/gcc_release
+++ b/maintainer-scripts/gcc_release
@@ -609,7 +609,7 @@ FILE_LIST=""
# Programs we use.
BZIP2="${BZIP2:-bzip2}"
-XZ="${XZ:-xz --best}"
+XZ="${XZ:-xz -T0 --best}"
CVS="${CVS:-cvs -f -Q -z9}"
DIFF="${DIFF:-diff -Nrcpad}"
ENV="${ENV:-env}"
reply other threads:[~2022-11-23 9:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20221123095359.65500385456D@sourceware.org \
--to=rsandifo@gcc.gnu.org \
--cc=gcc-cvs@gcc.gnu.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).