From: Ralf Baechle <ralf@oss.sgi.com>
To: Pete Popov <ppopov@pacbell.net>
Cc: Keith Owens <kaos@melbourne.sgi.com>,
linux-mips@oss.sgi.com, linux-mips@fnet.fr
Subject: Re: Kernel compiler
Date: Sat, 4 Nov 2000 04:20:02 +0100 [thread overview]
Message-ID: <20001104042002.A29373@bacchus.dhis.org> (raw)
In-Reply-To: <20001104.3105000@zeus.mvista.com>; from ppopov@pacbell.net on Sat, Nov 04, 2000 at 03:10:50AM +0000
On Sat, Nov 04, 2000 at 03:10:50AM +0000, Pete Popov wrote:
> > Sigh, yes you're right as other have already pointed out on IRC ...
>
> > Gcc 2.7 is no longer being used for Linux/MIPS since a long time and I'd
> > simply bitbucket any bugreport related to it. Most people are using egcs
> > 1.0.3a for everything which is older than the required minimum version
> 1.1.2,
> > so we're in some trouble.
>
> > I've got reports regarding the 1.1.2 crosscompiler which say that it
> > misscompiles MIPS kernels, sigh ...
>
> What are the symptoms of a "miscompiled" kernel and how does one detect
> that (assuming that the kernel actually compiles successfully, but has
> problems running).
When trying to work on a serial terminal hooked up to an Indy it'll oops.
Question is if the compiler is buggy or if it's particular code generation
is just triggering a bug in the kernel code.
Ralf
next prev parent reply other threads:[~2000-11-04 3:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-03 21:19 Kernel compiler Ralf Baechle
2000-11-04 2:44 ` Keith Owens
2000-11-04 2:53 ` Ralf Baechle
2000-11-04 3:03 ` Keith M Wesolowski
2000-11-04 3:10 ` Pete Popov
2000-11-04 3:20 ` Ralf Baechle [this message]
2000-11-04 3:13 ` Keith Owens
2000-11-04 10:40 ` Alan Cox
2000-11-04 10:40 ` Alan Cox
2000-11-07 3:39 ` Ralf Baechle
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=20001104042002.A29373@bacchus.dhis.org \
--to=ralf@oss.sgi.com \
--cc=kaos@melbourne.sgi.com \
--cc=linux-mips@fnet.fr \
--cc=linux-mips@oss.sgi.com \
--cc=ppopov@pacbell.net \
/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