From: Mike Castle <dalgoda@ix.netcom.com>
To: linux-kernel@vger.kernel.org
Subject: Re: gcc-2.95.2-51 is buggy
Date: Sun, 26 Nov 2000 13:36:13 -0600 [thread overview]
Message-ID: <20001126133612.B7698@thune.mrc-home.org> (raw)
In-Reply-To: <Pine.LNX.4.21.0011251805340.8818-100000@duckman.distro.conectiva> <87ofz2lpdm.fsf@tigram.bogus.local>
In-Reply-To: <87ofz2lpdm.fsf@tigram.bogus.local>; from olaf.dietsche@gmx.net on Sun, Nov 26, 2000 at 04:33:25PM +0100
On Sun, Nov 26, 2000 at 04:33:25PM +0100, Olaf Dietsche wrote:
> A simple `gcc -march=i686' or `gcc -mpentiumpro' does fix it as
> well. So, if you configure your kernel with `CONFIG_M686=y' the problem
> should be gone.
Btw, was this ever tested on other arch's? I don't remember seeing
anything come across this list.
mrc
--
Mike Castle Life is like a clock: You can work constantly
dalgoda@ix.netcom.com and be right all the time, or not work at all
www.netcom.com/~dalgoda/ and be right at least twice a day. -- mrc
We are all of us living in the shadow of Manhattan. -- Watchmen
-
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/
next prev parent reply other threads:[~2000-11-26 20:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-24 5:20 Andries.Brouwer
2000-11-24 5:44 ` Neil Brown
2000-11-24 6:47 ` Alexander Viro
2000-11-25 17:26 ` Rik van Riel
2000-11-25 19:16 ` Jeff V. Merkey
2000-11-25 20:01 ` Andries Brouwer
2000-11-25 20:06 ` Rik van Riel
2000-11-26 15:33 ` Olaf Dietsche
2000-11-26 16:58 ` Rik van Riel
2000-11-26 19:36 ` Mike Castle [this message]
2000-11-26 19:41 ` Russell King
2000-11-26 19:55 ` J . A . Magallon
2000-11-24 9:37 ` Ion Badulescu
2000-11-24 10:18 ` Linux Kernel Developer
2000-11-24 9:57 ` Jakub Jelinek
2000-11-24 8:09 Frédéric L . W . Meunier
2000-11-24 12:48 Andries.Brouwer
2000-11-24 16:46 ` Matthew Vanecek
2000-11-24 13:04 Mikael Pettersson
2000-11-27 14:28 Pavel Pisa;research student
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=20001126133612.B7698@thune.mrc-home.org \
--to=dalgoda@ix.netcom.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®