This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: if-conversion a performance bottleneck
- To: gcc at gcc dot gnu dot org
- Subject: Re: if-conversion a performance bottleneck
- From: Mathias Froehlich <frohlich at na dot uni-tuebingen dot de>
- Date: Fri, 5 May 2000 08:27:55 +0200 (MET DST)
> On Thu, May 04, 2000 at 10:31:59PM -0700, Mike Stump wrote:
> > Unfortunately -j3 gives you not three jobs, but an exponential cascade
> > of 3 jobs per recursive make level.
> I know. But 3 or 15 is still a lot better than 1000, which might
> be what you get with just -j.
> > I found that -j3 -l10 will at least try and limit them from expanding
> > too much, which is useful if your swap limited (just how did those 2
> > emacen grow to be 60M each, and netscape inflate to 90M? :-().
> That's what gigabytes of RAM are for. ;-)
Or use a recent version of gmake (>=3.78.1), which implements a so
called "jobserver mode". This limits ther _overall_ number of working
make jobs to the number given by -j. This does also work for recursive
makes.
Try it out it works great ...
Regards,
Mathias Froehlich
--
Mathias Fr"ohlich e-mail: frohlich@na.uni-tuebingen.de
Institut f"ur Mathematik, Universit"at T"ubingen, D-72076 T"ubingen