From: Josh McKinney <forming@home.com>
To: Nicholas Knight <tegeran@home.com>, linux-kernel@vger.kernel.org
Subject: Re: strange gcc crashes...
Date: Mon, 13 Aug 2001 14:26:09 -0500 [thread overview]
Message-ID: <20010813142609.A5700@home.com> (raw)
In-Reply-To: <E15WGJY-000Ecx-00@f12.port.ru> <01081305560700.00343@c779218-a>
In-Reply-To: <01081305560700.00343@c779218-a>
> > >> so it seems to me like kernel problem...
> > >
> > >why is that? I've never seen a sig11 from production >code
> > >that wasn't caused by flakey ram. in fact, your >descriptions
> > >are a perfect example of similar hardware problems.
> >
> Synthetic tests are never as good as a real good gcc run, I'd *never*
> trust them over the indications given by attempting to compile the kernel
> or something big like XFree86.
I agree. I had my computer mildy overclocked for a little while. Everything
ran just great, I could compile kernels, quake3 timedemo for two days, etc.
All was well until I tried to compile gcc itself and I kept getting random
errors. I finally opened up the case and bumped it back down, and like magic
it compiled just fine.
So my advice would be to don't overclock.
Josh
next prev parent reply other threads:[~2001-08-13 19:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-13 11:55 strange gcc crashes Samium Gromoff
2001-08-13 12:04 ` Rasmus Andersen
2001-08-13 12:56 ` Nicholas Knight
2001-08-13 19:26 ` Josh McKinney [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-08-11 14:58 Samium Gromoff
2001-08-11 15:16 ` Ignacio Vazquez-Abrams
2001-08-11 18:38 ` Horst von Brand
2001-08-11 16:42 ` J.H.M. Dassen (Ray)
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=20010813142609.A5700@home.com \
--to=forming@home.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tegeran@home.com \
/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.