going to run out of resources. But monitoring the
state of the machine (HP G9 with gobs of memory and 56 hyper-threads available)
suggests it is not breathing hard through most of the build.
-Original Message-
From: Paul Smith [mailto:psm...@gnu.org]
Sent: Sunday, July 17, 2016 11:33 AM
No I have not gotten to 4.2.1 yet.
I have experimented using j values ranging from 16 to 64. The majority of the
testing is with -Otarget. But I have tried all of them.
-Original Message-
From: Paul Smith [mailto:psm...@gnu.org]
Sent: Sunday, July 17, 2016 3:14 PM
To: Gardell, Steven
a smoking gun
here.
I have also run the “-Otrace” case at a few different job-levels:
j8 – 6:34
j32 – 6:00
j256 – 9:49
From: David Boyce [mailto:david.s.bo...@gmail.com]
Sent: Sunday, July 17, 2016 5:03 PM
To: Gardell, Steven
Cc: psm...@gnu.org; Bug-make@gnu.org
Subject: Re: Parallel builds a
any other settings that anyone might suggest since I
have the environment that is demonstrating the behavior.
From: David Boyce [mailto:david.s.bo...@gmail.com]
Sent: Monday, July 25, 2016 11:54 AM
To: Gardell, Steven
Cc: psm...@gnu.org; Bug-make@gnu.org
Subject: Re: Parallel builds across
]
Sent: Wednesday, July 27, 2016 4:59 PM
To: Gardell, Steven
Cc: Bug-make@gnu.org
Subject: Re: Parallel builds across makefiles
I haven't seen similar issues but I have a hypothesis: make is single-threaded
and therefore it consumes output from jobs in the same thread it uses to
reap/spawn new
Our experience is that it is really only sensible as a top-level control. That
said, it is convenient to have as an argument to make - which of course opens
one up to seeing it specified on explicit sub-make invocations. I would also
note that we have found that the performance behavior (this is
