ESR, how much for the memory expansion? It sounds like we have some volunteers to solve this problem with some money.
..m On Tue, Jul 10, 2018 at 2:14 AM Aldy Hernandez <al...@redhat.com> wrote: > Wait, there's a pot of money for making SVN go away? Sign me up! > While we're at it, let's start one for TCL and dejagnu! > On Mon, Jul 9, 2018 at 6:58 PM Jeff Law <l...@redhat.com> wrote: > > > > On 07/09/2018 10:53 AM, Janus Weil wrote: > > > 2018-07-09 18:35 GMT+02:00 Eric S. Raymond <e...@thyrsus.com>: > > >> David Edelsohn <dje....@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 > > > -- Mark Atwood http://about.me/markatwood +1-206-604-2198