public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Sam James <sam@gentoo.org>
To: Eric Botcazou <botcazou@adacore.com>
Cc: 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: Tue, 8 Nov 2022 07:45:15 +0000	[thread overview]
Message-ID: <950030A7-A084-4D24-AB1F-4ACF9423C873@gentoo.org> (raw)
In-Reply-To: <F0B9D80B-EDCA-4C1B-8667-5FE116CAF828@gentoo.org>

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



> On 8 Nov 2022, at 07:36, Sam James <sam@gentoo.org> wrote:
> 
> 
> 
>> On 8 Nov 2022, at 07:34, Eric Botcazou <botcazou@adacore.com> wrote:
>> 
>>>  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?
>> 
> 
> It is. It's no big deal if the patch isn't accepted, it's just very cheap to do
> for a decent benefit.
> 
> In particular, there's a lot of cases where I need to go through a cycle
> of checking various patches still apply and rebasing.
> 
> I won't be offended if the view is to not bother though. :)

Also: sometimes as a distribution we want to make some changes
to our build scripts and do a --disable-bootstrap and otherwise minimal
build repeatedly. It's useful there as well.

(A recent example was when playing with doing a separate JIT build,
as the docs recommend.)

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

  reply	other threads:[~2022-11-08  7:45 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 [this message]
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=950030A7-A084-4D24-AB1F-4ACF9423C873@gentoo.org \
    --to=sam@gentoo.org \
    --cc=botcazou@adacore.com \
    --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).