From: Ralf Baechle <ralf@linux-mips.org>
To: linux-mips@linux-mips.org
Subject: gcc 3.2.0 bug causes kernel failure
Date: Fri, 5 Mar 2004 16:22:07 +0100 [thread overview]
Message-ID: <20040305152206.GA21264@linux-mips.org> (raw)
Me and Steven have tracked down a LTP failure in the capget tests to a
bug in gcc 3.2.0. Reducing optimization to just -O seems to solve the
problem. To this point we've found the capget LTP problem with 2.4
kernel built with 3.2.0; 2.6.3 built with 2.95.4 seems to be ok. We've
also only tested 32-bit kernels. We'de be interested in test results
from other configurations, in particular 2.4 kernels built by later 3.2.x
compiler revisions would be of interest.
Ralf
next reply other threads:[~2004-03-05 15:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-05 15:22 Ralf Baechle [this message]
2004-03-05 16:49 ` gcc 3.2.0 bug causes kernel failure Steven J. Hill
2004-03-05 20:10 ` Steven J. Hill
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=20040305152206.GA21264@linux-mips.org \
--to=ralf@linux-mips.org \
--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