From: Jeff Law <law@redhat.com>
To: Janus Weil <janus@gcc.gnu.org>, "Eric S. Raymond" <esr@thyrsus.com>
Cc: David Edelsohn <dje.gcc@gmail.com>,
GCC Development <gcc@gcc.gnu.org>,
fallenpegasus@gmail.com
Subject: Re: Good news, bad news on the repository conversion
Date: Mon, 09 Jul 2018 16:57:00 -0000 [thread overview]
Message-ID: <aaba6c3d-d765-21cd-6561-1fad69077006@redhat.com> (raw)
In-Reply-To: <CAKwh3qjm47QYhXJLmDV4EJP0hvrb39gfNeaDSZhUhCDxD59-VQ@mail.gmail.com>
On 07/09/2018 10:53 AM, Janus Weil wrote:
> 2018-07-09 18:35 GMT+02:00 Eric S. Raymond <esr@thyrsus.com>:
>> David Edelsohn <dje.gcc@gmail.com>:
>>>> The truth is we're near the bleeding edge of what conventional tools
>>>> and hardware can handle gracefully. Most jobs with working sets as
>>>> big as this one's do only comparatively dumb operations that can be
>>>> parallellized and thrown on a GPU or supercomputer. Most jobs with
>>>> the algorithmic complexity of repository surgery have *much* smaller
>>>> working sets. The combination of both extrema is hard.
>>>
>>> If you come to the conclusion that the GCC Community could help with
>>> resources, such as the GNU Compile Farm or paying for more RAM, let us
>>> know.
>>
>> 128GB of DDR4 registered RAM would allow me to run conversions with my
>> browser up, but be eye-wateringly expensive. Thanks, but I'm not
>> going to yell for that help
>
> I for one would certainly be happy to donate some spare bucks towards
> beastie RAM if it helps to get the GCC repo converted to git in a
> timely manner, and I'm sure there are other GCC
> developers/users/sympathizers who'd be willing to join in. So, where
> do we throw those bucks?
I'd be willing to throw some $$$ at this as well.
Jeff
next prev parent reply other threads:[~2018-07-09 16:57 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
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 [this message]
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=aaba6c3d-d765-21cd-6561-1fad69077006@redhat.com \
--to=law@redhat.com \
--cc=dje.gcc@gmail.com \
--cc=esr@thyrsus.com \
--cc=fallenpegasus@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=janus@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).