Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-mips@linux-mips.org
Subject: Re: How reliable is GCC-3.3.1 wrt building mipsel-linux kernel?
Date: Thu, 20 Nov 2003 10:25:43 +0100	[thread overview]
Message-ID: <20031120092543.GH1037@lug-owl.de> (raw)
In-Reply-To: <3FBC0AF7.90600@avtrex.com>

[-- Attachment #1: Type: text/plain, Size: 1052 bytes --]

On Wed, 2003-11-19 16:29:43 -0800, David Daney <ddaney@avtrex.com>
wrote in message <3FBC0AF7.90600@avtrex.com>:
> Ralf Baechle wrote:
> >On Tue, Nov 18, 2003 at 05:40:31PM -0800, David Daney wrote:

> Which options have other people used with gcc 3.3.1 with good results?

It's a question of what you call "good results". If there are bugs in
the kernel sources which only show up with a really aggressive HEAD
compiler, then IMHO it's a good result to see the compiled kernel crash,
just because there actually *is* a bug.

Companies however tend to accept a slower/more bloated/whatever software
(produced by an older compiler) in order not to start hunting down the
remaining (and possibly hard to find) bugs...

MfG, JBG

-- 
   Jan-Benedict Glaw       jbglaw@lug-owl.de    . +49-172-7608481
   "Eine Freie Meinung in  einem Freien Kopf    | Gegen Zensur | Gegen Krieg
    fuer einen Freien Staat voll Freier Bürger" | im Internet! |   im Irak!
   ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2003-11-20  9:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-19  1:40 How reliable is GCC-3.3.1 wrt building mipsel-linux kernel? David Daney
2003-11-19  1:49 ` Daniel Jacobowitz
2003-11-19 23:30 ` Ralf Baechle
2003-11-20  0:29   ` David Daney
2003-11-20  9:25     ` Jan-Benedict Glaw [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=20031120092543.GH1037@lug-owl.de \
    --to=jbglaw@lug-owl.de \
    --cc=linux-mips@linux-mips.org \
    /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