From: Eric Botcazou <botcazou@adacore.com>
To: gcc-patches@gcc.gnu.org, Sam James <sam@gentoo.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: Tue, 08 Nov 2022 08:34:09 +0100 [thread overview]
Message-ID: <2654849.mvXUDI8C0e@fomalhaut> (raw)
In-Reply-To: <20221108071438.2523863-1-sam@gentoo.org>
> I build GCC regularly from the weekly snapshots
> and so the decompression time adds up.
But is very largely dwarfed by the build time of the compiler, isn't it?
--
Eric Botcazou
next prev parent reply other threads:[~2022-11-08 7:34 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 [this message]
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=2654849.mvXUDI8C0e@fomalhaut \
--to=botcazou@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=jakub@redhat.com \
--cc=jlaw@ventanamicro.com \
--cc=sam@gentoo.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).