Joseph Myers :
> I don't see any commits at
> git://thyrsus.com/repositories/gcc-conversion.git since January. Are
> there further changes that haven't been pushed there? (For example, I
> sent a few additions to the author map on 13 Feb.)
Yes, that copy is rather stale. I need toi do some an
I don't see any commits at
git://thyrsus.com/repositories/gcc-conversion.git since January. Are
there further changes that haven't been pushed there? (For example, I
sent a few additions to the author map on 13 Feb.)
--
Joseph S. Myers
jos...@codesourcery.com
I have no idea what order messages are in now because I wasn't CCed into
this (so was it before?) but it may not be much money. It depends how
long you need it for.
Presumably someone's mentioned swapspace too...
Anyway do let me know, I don't check the mailing lists as often as I'd
like and
Mark Atwood :
> ESR, how much for the memory expansion? It sounds like we have some
> volunteers to solve this problem with some money.
That's now rthe second problem out. There's a malformation that has
turned up in the repo that may sink the conversion entirely. I want to be
reasonably sure I
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 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 d
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 wrote:
>
> On 07/09/2018 10:53 AM, Janus Weil wrote:
> > 2018-07-09 18:35 GMT+02:00 Eric S. Raymond :
> >> David Edelsohn :
> The t
On Tue, 10 Jul 2018 at 09:10, Alec Teal wrote:
> PS: Migrating what to what?
Git.
> Wasn't the git migration done years ago?
No.
On Mon, 9 Jul 2018, 19:05 Paul Smith, wrote:
>
> On Mon, 2018-07-09 at 10:57 -0600, Jeff Law wrote:
> > On 07/09/2018 10:53 AM, Janus Weil wrote:
> > > 2018-07-09 18:35 GMT+02:00 Eric S. Raymond :
> > > > David Edelsohn :
> > > > > > The truth is we're near the bleeding edge of what conventional t
Is this still an issue? (I missed the convo due to an overzealous spam
filter; this is the only message I have)
I often use AWS Spot instances (bidding on instances other people
previsioned but put up for auction as it's not always needed) to get
results extremely quickly without hearing a fa
Florian Weimer :
> * Eric S. Raymond:
>
> > 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.
>
> Do you need interactive access to the machine
* Eric S. Raymond:
> 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.
Do you need interactive access to the machine, or can we run the job
for you
On Mon, 2018-07-09 at 06:16 -0400, Eric S. Raymond wrote:
> Janus Weil :
> > > 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.
On Mon, 2018-07-09 at 10:57 -0600, Jeff Law wrote:
> On 07/09/2018 10:53 AM, Janus Weil wrote:
> > 2018-07-09 18:35 GMT+02:00 Eric S. Raymond :
> > > David Edelsohn :
> > > > > The truth is we're near the bleeding edge of what conventional tools
> > > > > and hardware can handle gracefully. Most j
On Mon, Jul 9, 2018 at 12:35 PM Eric S. Raymond wrote:
>
> David Edelsohn :
> > > 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
On 07/09/2018 10:53 AM, Janus Weil wrote:
> 2018-07-09 18:35 GMT+02:00 Eric S. Raymond :
>> David Edelsohn :
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 comparativel
2018-07-09 18:35 GMT+02:00 Eric S. Raymond :
> David Edelsohn :
>> > 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
>> > parallelli
David Edelsohn :
> > 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 job
On Mon, Jul 9, 2018 at 6:16 AM Eric S. Raymond wrote:
>
> Janus Weil :
> > > 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 ma
Janus Weil :
> > 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?
>
> Accordin
On 07/09/2018 02:27 AM, Eric S. Raymond wrote:
> 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.
Hello.
I can help with by running a conversion o
2018-07-09 2:27 GMT+02:00 Eric S. Raymond :
> 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 bein
Thanks for the update.
On Mon, Jul 9, 2018, 10:28 AM Eric S. Raymond wrote:
> 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 prev
22 matches
Mail list logo
