From: David Daney <ddaney@avtrex.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: linux-mips@linux-mips.org
Subject: Re: How reliable is GCC-3.3.1 wrt building mipsel-linux kernel?
Date: Wed, 19 Nov 2003 16:29:43 -0800 [thread overview]
Message-ID: <3FBC0AF7.90600@avtrex.com> (raw)
In-Reply-To: <20031119233023.GA30962@linux-mips.org>
Ralf Baechle wrote:
>On Tue, Nov 18, 2003 at 05:40:31PM -0800, David Daney wrote:
>
>
>><...>
>>But my main question is this: Have other people experienced
>>miscompilation (ie bad code generation) with gcc 3.3.1?
>>
>>
>
>Quite frequently using a new, possibly more agressive compiler triggers
>bugs in the kernel code ...
>
> Ralf
>
>
That's the whole point of my question.
Which options have other people used with gcc 3.3.1 with good results?
David Daney.
next prev parent reply other threads:[~2003-11-20 0:29 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 [this message]
2003-11-20 9:25 ` Jan-Benedict Glaw
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=3FBC0AF7.90600@avtrex.com \
--to=ddaney@avtrex.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@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