From: Daniel Jacobowitz <dan@debian.org>
To: David Daney <ddaney@avtrex.com>
Cc: linux-mips@linux-mips.org
Subject: Re: How reliable is GCC-3.3.1 wrt building mipsel-linux kernel?
Date: Tue, 18 Nov 2003 20:49:29 -0500 [thread overview]
Message-ID: <20031119014929.GA4811@nevyn.them.org> (raw)
In-Reply-To: <3FBACA0F.7070207@avtrex.com>
On Tue, Nov 18, 2003 at 05:40:31PM -0800, David Daney wrote:
> The subject line kind of says it all.
>
> We are running linux 2.4.18 on a mips4Kc core (ATI Xilleon 225) and find
> it to be quite stable when compiled with gcc 2.96/binutils 2.11.92.0.10
>
> When the kernel is compiled with gcc 3.3.1/binutils 2.14.90.0.5 it also
> seems to be quite stable, except for when one certian driver is used
> (basically an mpeg decoder driver). Under certian conditions the system
> seems to "freeze" (no messages printed anywhere and only a hard reset
> will recover).
>
> Yeah that is a good bug report...
>
> But my main question is this: Have other people experienced
> miscompilation (ie bad code generation) with gcc 3.3.1?
>
> One thing I am aware of is that if -fno-common is not used, bad code is
> generated for accessing some large structures. But I we use -fno-common
> for all compilation.
>
> I am trying to figrue out if I should be looking more at bugs in the
> driver, or if I should give up on gcc 3.3.1 and be done with it.
>
> Thanks in advance for any insight.
We haven't had problems here.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-11-19 1:49 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 [this message]
2003-11-19 23:30 ` Ralf Baechle
2003-11-20 0:29 ` David Daney
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=20031119014929.GA4811@nevyn.them.org \
--to=dan@debian.org \
--cc=ddaney@avtrex.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.