mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Weinehall <tao@acc.umu.se>
To: "Dr. Kelsey Hudson" <kernel@blackhole.compendium-tech.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: is this a bug?
Date: Wed, 8 Aug 2001 12:53:42 +0200	[thread overview]
Message-ID: <20010808125342.C17094@khan.acc.umu.se> (raw)
In-Reply-To: <3B70AEC5.5FE97ACC@pobox.com> <Pine.LNX.4.33.0108072041400.23797-100000@sol.compendium-tech.com>
In-Reply-To: <Pine.LNX.4.33.0108072041400.23797-100000@sol.compendium-tech.com>; from kernel@blackhole.compendium-tech.com on Tue, Aug 07, 2001 at 08:45:15PM -0700

On Tue, Aug 07, 2001 at 08:45:15PM -0700, Dr. Kelsey Hudson wrote:
> On Tue, 7 Aug 2001, J Sloan wrote:
> 
> > "Dr. Kelsey Hudson" wrote:
> 
> > > It's a bug in that screwed up compiler redhat shipped with 7.1.
> 
> > Oh please, not this FUD again.....
> 
> Call it what you wish -- But, if I see something break when using a
> certain compiler option versus another compiler option that does not
> cause a break, chances are it's a bug in the compiler. After all, the
> Athlon support *is* a new feature, is it not?
> 
> I don't even know why I bothered replying. Don't feed the trolls... Gotta
> watch for those signs....

Ah, but if you'd been observant you'd have noticed what kind of motherboard
he has (a VIA) and if you have been reading your kernel-list lately,
you'd have known that almost noone has been able to get a Athlon-optimized
kernel to work in a stable manner on those; probably because of the
Athlon-optimizations stressing the hardware too much.

I'd say flakey hardware is the problem here, not the compiler.


/David Weinehall
  _                                                                 _
 // David Weinehall <tao@acc.umu.se> /> Northern lights wander      \\
//  Project MCA Linux hacker        //  Dance across the winter sky //
\>  http://www.acc.umu.se/~tao/    </   Full colour fire           </

  reply	other threads:[~2001-08-08 10:54 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-07 11:51 Thodoris Pitikaris
2001-08-07 13:51 ` Andrzej Krzysztofowicz
2001-08-08  2:19 ` Dr. Kelsey Hudson
2001-08-08  3:15   ` J Sloan
2001-08-08  3:45     ` Dr. Kelsey Hudson
2001-08-08 10:53       ` David Weinehall [this message]
2001-08-08 11:05   ` Alan Cox
2001-08-08 12:59   ` Ron Flory
2001-08-08 16:51 ` jury gerold
2001-08-10  9:12   ` Eric W. Biederman
2001-08-10 12:22     ` jury gerold
2001-08-10 16:22       ` Eric W. Biederman
2011-03-24  0:46 Jay
2011-03-25 15:18 ` Steven Rostedt
2017-06-21  3:08 Is " Peter Teoh

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=20010808125342.C17094@khan.acc.umu.se \
    --to=tao@acc.umu.se \
    --cc=kernel@blackhole.compendium-tech.com \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®