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:)
Date: Thu, 22 May 2003 12:24:42 -0700 [thread overview]
Message-ID: <20030522122442.651ae8f0.akpm@digeo.com> (raw)
In-Reply-To: <3ECCCF76.3020800@gmx.net>
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.
next prev parent reply other threads:[~2003-05-22 19:08 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-15 2:03 2.5.69-mm5: pccard oops while booting: resolved Felipe Alfaro Solana
2003-05-15 2:17 ` Andrew Morton
2003-05-15 11:36 ` Felipe Alfaro Solana
2003-05-15 12:00 ` Russell King
2003-05-15 13:16 ` Felipe Alfaro Solana
2003-05-15 13:44 ` Russell King
2003-05-15 13:47 ` Dave Jones
2003-05-15 22:31 ` Felipe Alfaro Solana
2003-05-15 23:00 ` Andrew Morton
2003-05-16 13:03 ` Felipe Alfaro Solana
2003-05-16 18:13 ` Ben Collins
2003-05-16 19:03 ` Felipe Alfaro Solana
2003-05-16 18:34 ` 2.5.69-mm6: pccard oops while booting Felipe Alfaro Solana
2003-05-16 20:29 ` Andrew Morton
2003-05-16 21:42 ` Felipe Alfaro Solana
2003-05-16 22:08 ` Carl-Daniel Hailfinger
2003-05-16 23:40 ` Felipe Alfaro Solana
2003-05-16 23:55 ` Russell King
2003-05-17 0:03 ` Felipe Alfaro Solana
2003-05-17 0:27 ` Carl-Daniel Hailfinger
2003-05-17 10:11 ` 2.5.69-mm6: pccard oops while booting: round 2 Felipe Alfaro Solana
2003-05-17 10:18 ` Andrew Morton
2003-05-17 11:05 ` Felipe Alfaro Solana
2003-05-17 11:22 ` Carl-Daniel Hailfinger
2003-05-17 12:51 ` 2.5.69-mm6: pccard oops while booting: round 3 Felipe Alfaro Solana
2003-05-18 19:38 ` 2.5.69-mm6: pccard oops while booting: gcc bug? Felipe Alfaro Solana
2003-05-22 13:24 ` [RFC] Disallow compilation with gcc 3.2.3 (was: Re: 2.5.69-mm6: pccard oops while booting:) Carl-Daniel Hailfinger
2003-05-22 14:05 ` Valdis.Kletnieks
2003-05-22 18:34 ` Felipe Alfaro Solana
2003-05-22 19:24 ` Andrew Morton [this message]
2003-05-22 14:26 ` 2.5.69-mm6: pccard oops while booting: gcc bug? Russell King
2003-05-17 11:39 ` 2.5.69-mm6: pccard oops while booting: round 2 Andrew Morton
2003-05-17 12:36 ` Felipe Alfaro Solana
2003-05-15 12:13 ` 2.5.69-mm5: pccard oops while booting: resolved Russell King
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030522122442.651ae8f0.akpm@digeo.com \
--to=akpm@digeo.com \
--cc=c-d.hailfinger.kernel.2003@gmx.net \
--cc=davej@suse.de \
--cc=felipe_alfaro@linuxmail.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®