From: "Steven J. Hill" <sjhill@realitydiluted.com>
To: "Steven J. Hill" <sjhill@realitydiluted.com>
Cc: Ralf Baechle <ralf@linux-mips.org>, linux-mips@linux-mips.org
Subject: Re: gcc 3.2.0 bug causes kernel failure
Date: Fri, 05 Mar 2004 15:10:05 -0500 [thread overview]
Message-ID: <4048DE9D.6050002@realitydiluted.com> (raw)
In-Reply-To: <4048AF9E.2060401@realitydiluted.com>
Steven J. Hill wrote:
>
> All of these exhibit the same failure. They also exhibit the same success
> when the above compiler option is used. Thanks again to Ralf for giving
> me more ideas to try and verify this. I have not verified that newer
> gcc-3.2.x or gcc-3.3 versions fix this problem. Comments and more testing
> are welcome. Thanks.
>
I have confirmed that the bug for this issue was fixed in GCC 3.2.3. If you
need to use the GCC 3.2.x series, please use the 3.2.3 version. Thanks.
-Steve
prev parent reply other threads:[~2004-03-05 20:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-05 15:22 gcc 3.2.0 bug causes kernel failure Ralf Baechle
2004-03-05 16:49 ` Steven J. Hill
2004-03-05 20:10 ` Steven J. Hill [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=4048DE9D.6050002@realitydiluted.com \
--to=sjhill@realitydiluted.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