From: "J . A . Magallon" <jamagallon@able.es>
To: Olaf Dietsche <olaf.dietsche@gmx.net>
Cc: Rik van Riel <riel@conectiva.com.br>, linux-kernel@vger.kernel.org
Subject: Re: gcc-2.95.2-51 is buggy
Date: Sun, 26 Nov 2000 20:55:40 +0100 [thread overview]
Message-ID: <20001126205540.A8066@werewolf.able.es> (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 16:33:25 +0100
On Sun, 26 Nov 2000 16:33:25 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.
>
That does not work for 2.2 kernels. Always compile for -m486. To use
the -march flag you need to modify arch/i386/kernel/Makefile. Patch
follows:
================= PATCH patch-gcc-arch:
--- linux-2.2.17/arch/i386/Makefile.orig Wed Nov 22 20:42:49 2000
+++ linux-2.2.17/arch/i386/Makefile Wed Nov 22 20:44:40 2000
@@ -24,23 +24,23 @@
CFLAGS := $(CFLAGS) $(CFLAGS_PIPE) $(CFLAGS_NSR)
ifdef CONFIG_M386
-CFLAGS := $(CFLAGS) -m386 -DCPU=386
+CFLAGS := $(CFLAGS) -march=i386 -DCPU=386
endif
ifdef CONFIG_M486
-CFLAGS := $(CFLAGS) -m486 -DCPU=486
+CFLAGS := $(CFLAGS) -march=i486 -DCPU=486
endif
ifdef CONFIG_M586
-CFLAGS := $(CFLAGS) -m486 -malign-loops=2 -malign-jumps=2 -malign-functions=2
-DCPU=586
+CFLAGS := $(CFLAGS) -march=i586 -malign-loops=2 -malign-jumps=2
-malign-functions=2 -DCPU=586
endif
ifdef CONFIG_M586TSC
-CFLAGS := $(CFLAGS) -m486 -malign-loops=2 -malign-jumps=2 -malign-functions=2
-DCPU=586
+CFLAGS := $(CFLAGS) -march=i586 -malign-loops=2 -malign-jumps=2
-malign-functions=2 -DCPU=586
endif
ifdef CONFIG_M686
-CFLAGS := $(CFLAGS) -m486 -malign-loops=2 -malign-jumps=2 -malign-functions=2
-DCPU=686
+CFLAGS := $(CFLAGS) -march=i686 -malign-loops=2 -malign-jumps=2
-malign-functions=2 -DCPU=686
endif
HEAD := arch/i386/kernel/head.o arch/i386/kernel/init_task.o
--
Juan Antonio Magallon Lacarta #> cd /pub
mailto:jamagallon@able.es #> more beer
Linux 2.2.18-pre23-vm #3 SMP Wed Nov 22 22:33:53 CET 2000 i686 unknown
-
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:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-24 5:20 gcc-2.95.2-51 is buggy 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
2000-11-26 19:41 ` Russell King
2000-11-26 19:55 ` J . A . Magallon [this message]
2000-11-24 9:37 ` Ion Badulescu
2000-11-24 10:18 ` Linux Kernel Developer
2000-11-24 9:57 ` Jakub Jelinek
-- strict thread matches above, loose matches on Subject: below --
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=20001126205540.A8066@werewolf.able.es \
--to=jamagallon@able.es \
--cc=linux-kernel@vger.kernel.org \
--cc=olaf.dietsche@gmx.net \
--cc=riel@conectiva.com.br \
/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