Date: Sun, 22 Jun 2003 12:13:23 -0700
From: Andrew Morton <akpm@digeo.com>
To: hps@intermeta.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: GCC speed (was [PATCH] Isapnp warning)
Message-Id: <20030622121323.1abdd079.akpm@digeo.com>
In-Reply-To: <bd4u7s$jkp$1@tangens.hometree.net>
References: <20030621125111.0bb3dc1c.akpm@digeo.com>
	<20030622103251.158691c3.akpm@digeo.com>
	<bd4u7s$jkp$1@tangens.hometree.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 867
Lines: 20

"Henning P. Schmiedehausen" <hps@intermeta.de> wrote:
>
>  Your problem is not the compiler but the build tool / system which
>  forces you to recompile all of your kernel if you change only small
>  parts.

No, the build system is OK.  And ccache nicely fixes up any mistakes which
the build system makes, and distcc speeds things up by 2x to 3x.

None of that gets around the fact that code needs to be tested with various
combinations of CONFIG_SMP, CONFIG_PREEMPT, different subarchitectures,
spinlock debugging, etc, etc.  If the compiler is slow people don't bother
doing this and the code breaks.

Cause and effect.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/