From: Daniel Robbins <drobbins@gentoo.org>
To: gentoo-dev@cvs.gentoo.org
Subject: Re: [gentoo-dev] make.conf optimization flags for k6, athlon
Date: Sat Jul 14 02:12:02 2001 [thread overview]
Message-ID: <20010714021107.R22931@cvs.gentoo.org> (raw)
In-Reply-To: <01071410100900.00576@localhost>; from ermak@netvision.net.il on Sat, Jul 14, 2001 at 10:10:09AM +0300
On Sat, Jul 14, 2001 at 10:10:09AM +0300, Dan Armak wrote:
> I added it. I also added an i386 option. Does anyone know why the options
> started from 486 initially? Is there a problem in using 386 (with a math
> coprocessor)?
Nope, a 386 should work. However, bzip2 on a 386 is, um, super-slow?
It's horribly slow on a 486; imagine a 386.
--
Daniel Robbins <drobbins@gentoo.org>
President/CEO http://www.gentoo.org
Gentoo Technologies, Inc.
next prev parent reply other threads:[~2001-07-14 8:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-13 14:36 [gentoo-dev] make.conf optimization flags for k6, athlon Dan Armak
2001-07-13 14:55 ` Daniel Robbins
2001-07-13 15:00 ` Dan Armak
2001-07-13 15:38 ` Daniel Robbins
2001-07-14 1:11 ` Dan Armak
2001-07-14 2:12 ` Daniel Robbins [this message]
2001-07-14 3:28 ` Hendrik Visage
2001-07-14 4:04 ` Dan Armak
2001-07-14 18:56 ` Thomas Beaudry
2001-07-15 0:15 ` Dan Armak
2001-07-15 0:45 ` Thomas Beaudry
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=20010714021107.R22931@cvs.gentoo.org \
--to=drobbins@gentoo.org \
--cc=gentoo-dev@cvs.gentoo.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