public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Samuelson <peter@cadcamlab.org>
To: "Mike A. Harris" <mharris@opensourceadvocate.org>
Cc: Lukasz Trabinski <lukasz@lt.wsisiz.edu.pl>,
	Linux Kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: Problems with Athlon CPU [long]
Date: Tue, 5 Dec 2000 14:55:41 -0600	[thread overview]
Message-ID: <20001205145541.E6567@cadcamlab.org> (raw)
In-Reply-To: <Pine.LNX.4.30.0012051135361.1881-200000@lt.wsisiz.edu.pl> <Pine.LNX.4.30.0012050613240.620-100000@asdf.capslock.lan>
In-Reply-To: <Pine.LNX.4.30.0012050613240.620-100000@asdf.capslock.lan>; from mharris@opensourceadvocate.org on Tue, Dec 05, 2000 at 06:17:39AM -0500


  [Lukasz Trabinski]
> > I know about it, but the compiler does.

[Mike A. Harris]
> Not sure what you mean however no part of the linux kernel ever uses
> glibc at all. It is not possible to do so in fact.

He means that gcc is linked to libc, so a libc bug could possibly
affect gcc.  I have not, however, ever heard of that happening.

> Your hardware is likely faulty, especially if it conks out in a
> different spot each time.

Yes.

Peter
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-12-05 21:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.30.0012051135361.1881-200000@lt.wsisiz.edu.pl>
2000-12-05 10:58 ` Problems with Athlon CPU [long] Lukasz Trabinski
2000-12-05 11:17 ` Mike A. Harris
2000-12-05 20:55   ` Peter Samuelson [this message]
2000-12-26 16:11   ` Arnaud S . Launay

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=20001205145541.E6567@cadcamlab.org \
    --to=peter@cadcamlab.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukasz@lt.wsisiz.edu.pl \
    --cc=mharris@opensourceadvocate.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