From: Janus Weil <janus@gcc.gnu.org>
To: "Eric S. Raymond" <esr@thyrsus.com>
Cc: Mailing List <gcc@gcc.gnu.org>, Mark Atwood <fallenpegasus@gmail.com>
Subject: Re: Good news, bad news on the repository conversion
Date: Mon, 09 Jul 2018 07:18:00 -0000 [thread overview]
Message-ID: <CAKwh3qgKjXYfp8RWLYOOR8h6zbbtw-F+gya1KuDnmLf=54j5eA@mail.gmail.com> (raw)
In-Reply-To: <20180709002754.962F43A4AA7@snark.thyrsus.com>
2018-07-09 2:27 GMT+02:00 Eric S. Raymond <esr@thyrsus.com>:
> There is good news bad news on the GCC repository conversion.
>
> The good news is that I have solved the only known remaining technical
> problem in reposurgeon blocking the conversion. I've fixed the bug
> that prevented execute permissions from being carried by branch
> copies.
Great to hear that there is progress on that front!
> The bad news is that my last test run overran the memnory capacity of
> the 64GB Great Beast. I shall have to find some way of reducing the
> working set, as 128GB DD4 memory is hideously expensive.
Or maybe you could use a machine from the GCC compile farm?
According to https://gcc.gnu.org/wiki/CompileFarm, there are three
machines with at least 128GB available (gcc111, gcc112, gcc119).
Cheers,
Janus
next prev parent reply other threads:[~2018-07-09 7:18 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-09 0:28 Eric S. Raymond
2018-07-09 2:09 ` Jason Merrill
2018-07-09 7:18 ` Janus Weil [this message]
2018-07-09 10:16 ` Eric S. Raymond
2018-07-09 13:59 ` David Edelsohn
2018-07-09 16:35 ` Eric S. Raymond
2018-07-09 16:53 ` Janus Weil
2018-07-09 16:57 ` Jeff Law
2018-07-09 18:05 ` Paul Smith
2018-07-10 8:10 ` Jonathan Wakely
2018-07-10 9:14 ` Aldy Hernandez
2018-07-11 3:31 ` Mark Atwood
2018-07-11 4:29 ` Eric S. Raymond
2018-07-11 8:27 ` Alec Teal
2018-07-09 17:18 ` David Edelsohn
2018-07-09 18:16 ` David Malcolm
2018-07-09 8:40 ` Martin Liška
2018-07-09 19:51 ` Florian Weimer
2018-07-09 20:04 ` Eric S. Raymond
2018-07-10 8:10 ` Alec Teal
2018-07-10 8:11 ` Jonathan Wakely
2018-07-20 21:36 ` Joseph Myers
2018-07-20 23:47 ` Eric S. Raymond
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='CAKwh3qgKjXYfp8RWLYOOR8h6zbbtw-F+gya1KuDnmLf=54j5eA@mail.gmail.com' \
--to=janus@gcc.gnu.org \
--cc=esr@thyrsus.com \
--cc=fallenpegasus@gmail.com \
--cc=gcc@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).