From: Heinz Diehl <hd@cavy.de>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4.15 and GNU 3.0.2
Date: Sat, 8 Dec 2001 18:38:32 +0100 [thread overview]
Message-ID: <20011208173832.GA745@elfie.cavy.de> (raw)
In-Reply-To: <15362.34918.524256.760222@sinisa.nasamreza.org> <3C029E59.4040106@blue-labs.org> <15363.32056.147142.173419@sinisa.nasamreza.org>
In-Reply-To: <15363.32056.147142.173419@sinisa.nasamreza.org>
On Tue Nov 27 2001, Sinisa Milivojevic wrote:
> > Out of five computers I build kernels for at home here, one of them has
> > an AMD K6II processor in it and that is the only one that I need to use
> > gcc 2.95.3 with. The rest I use 3.0.x and they are quite stable.
I have also two machines using AMD's K6
elfie:~ # cat /proc/cpuinfo
processor : 0
vendor_id : AuthenticAMD
cpu family : 5
model : 9
model name : AMD-K6(tm) 3D+ Processor
stepping : 1
cpu MHz : 400.914
cache size : 256 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr mce cx8 pge mmx syscall 3dnow k6_mtrr
bogomips : 799.53
On one of them I compiled the kernel with
elfie:~ # gcc -v
Reading specs from /usr/local/gcc3/lib/gcc-lib/i586-pc-linux-gnu/3.1/specs
Configured with: /Src/gcc-20011203/configure --prefix=/usr/local/gcc3
Thread model: single
gcc version 3.1 20011203 (experimental)
and there were no problems yet (5 days up).
--
# Heinz Diehl, 68259 Mannheim, Germany
next prev parent reply other threads:[~2001-12-08 18:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-26 18:22 2.4.15 and GNU 3.0.2 Sinisa Milivojevic
2001-11-26 18:36 ` Mr. Shannon Aldinger
2001-11-26 19:56 ` David Ford
2001-11-27 11:47 ` Sinisa Milivojevic
2001-12-08 17:38 ` Heinz Diehl [this message]
[not found] <20011126193256.U5129@suse.de>
2001-11-26 19:18 ` Sinisa Milivojevic
2001-11-26 19:43 ` Ken Witherow
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=20011208173832.GA745@elfie.cavy.de \
--to=hd@cavy.de \
--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 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.