Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@oss.sgi.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Keith Owens <kaos@melbourne.sgi.com>,
	linux-mips@oss.sgi.com, linux-mips@fnet.fr
Subject: Re: Kernel compiler
Date: Tue, 7 Nov 2000 04:39:22 +0100	[thread overview]
Message-ID: <20001107043922.A31298@bacchus.dhis.org> (raw)
In-Reply-To: <E13s0ke-0004Sa-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Sat, Nov 04, 2000 at 10:40:42AM +0000

On Sat, Nov 04, 2000 at 10:40:42AM +0000, Alan Cox wrote:

> > The reports regarding egcs 2.96 and newer misscompiling the kernel only
> > affect x86 or are other architecture affected as well?  I don't have any
> > pending compiler >= 2.96 related bug reports.
> 
> The Red Hat 2.96 seems to compile 2.2 correctly when you fix the 2.2 bugs but
> does miscompile x86 fs/buffers.c on 2.4 according to reports. I think with mips
> you'd have to experiment. Also AFAIK that tree branch hasn't been tested on
> mips 

I asked Cort about their PPC experience and they also got trouble.  Reason
enough to ignore gcc-current for kernel use for now.  It's doing well
for userland however so we'll also have to use two compilers from now on,
one for kernel and one for userland.

Btw, I've now placed srpm and i386-linux rpms of a new release of the
egcs-1.1.2 Linux/MIPS crosscompiler on oss.sgi.com.  Users of the 64-bit
kernel, read Origin users should also update as this release has several
fixes.

  Ralf

      parent reply	other threads:[~2000-11-07  3:40 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
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 [this message]

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=20001107043922.A31298@bacchus.dhis.org \
    --to=ralf@oss.sgi.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=kaos@melbourne.sgi.com \
    --cc=linux-mips@fnet.fr \
    --cc=linux-mips@oss.sgi.com \
    /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