Date: Thu, 22 May 2003 12:24:42 -0700
From: Andrew Morton <akpm@digeo.com>
To: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2003@gmx.net>
Cc: felipe_alfaro@linuxmail.org, rmk@arm.linux.org.uk,
       linux-kernel@vger.kernel.org, davej@suse.de
Subject: Re: [RFC] Disallow compilation with gcc 3.2.3 (was: Re: 2.5.69-mm6:
 pccard oops while booting:)
Message-Id: <20030522122442.651ae8f0.akpm@digeo.com>
In-Reply-To: <3ECCCF76.3020800@gmx.net>
References: <1052964213.586.3.camel@teapot.felipe-alfaro.com>
	<20030514191735.6fe0998c.akpm@digeo.com>
	<1052998601.726.1.camel@teapot.felipe-alfaro.com>
	<20030515130019.B30619@flint.arm.linux.org.uk>
	<1053004615.586.2.camel@teapot.felipe-alfaro.com>
	<20030515144439.A31491@flint.arm.linux.org.uk>
	<1053037915.569.2.camel@teapot.felipe-alfaro.com>
	<20030515160015.5dfea63f.akpm@digeo.com>
	<1053090184.653.0.camel@teapot.felipe-alfaro.com>
	<1053110098.648.1.camel@teapot.felipe-alfaro.com>
	<20030516132908.62e54266.akpm@digeo.com>
	<1053121346.569.1.camel@teapot.felipe-alfaro.com>
	<3EC56173.1000306@gmx.net>
	<1053166275.586.9.camel@teapot.felipe-alfaro.com>
	<20030517031840.486683fc.akpm@digeo.com>
	<1053169552.613.1.camel@teapot.felipe-alfaro.com>
	<3EC61B63.9020906@gmx.net>
	<1053175886.660.4.camel@teapot.felipe-alfaro.com>
	<1053286732.812.5.camel@teapot.felipe-alfaro.com>
	<3ECCCF76.3020800@gmx.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8BIT
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1136
Lines: 25

Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2003@gmx.net> wrote:
>
> Felipe Alfaro Solana wrote:
> > I've read the announcement of gcc 3.3 and saw that gcc 3.2 is not yet
> > supported for linux kernel compilations (I've been using Red Hat's
> > gcc-3.2.3-4 to compile 2.5.69-mm6). So I thought, what would happen if I
> > use gcc 2.96 to compile the kernel instead?
> > 
> > And voil?... I've compiled 2.5.69-mm6 with Red Hat's 2.96.118 and now,
> > I'm unable to reproduce the pccard oops you've been trying to chase
> > down. Does this mean the pccard oops was caused by a compiler bug?
> 
> Nobody has found an error in the code we talked about, so a compiler bug
> in gcc 3.2.3 seems to be the only explanation.
> 

It could be due to some incorrect code in the kernel, but we got away with
it when using earlier compilers.  We need to work out precisely where and
why it went wrong.

-
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/