From: Adrian Bunk <bunk@fs.tum.de>
To: Robert Love <rml@tech9.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC][2.5 patch] K6-II/K6-II: enable X86_USE_3DNOW
Date: Tue, 15 Apr 2003 21:39:32 +0200 [thread overview]
Message-ID: <20030415193931.GS9640@fs.tum.de> (raw)
In-Reply-To: <1050359780.3664.114.camel@localhost>
On Mon, Apr 14, 2003 at 06:36:20PM -0400, Robert Love wrote:
> On Mon, 2003-04-14 at 18:21, Adrian Bunk wrote:
>
> > If my patch is wrong and this is a RTFM please give me a hint where to
> > find the "M".
>
> Patch looks right...
>
> > Questions:
> > Is it really correct to enable CONFIG_X86_USE_3DNOW?
>
> If you are right that the K6-2 and K6-3D support 3DNow!, then yes. At
> least its "correct" but it may not be optimal: I seem to recall 3DNow
> memory copies were not worthwhile on anything before an Athlon. Double
> check that, though.
It does, but Alan already explained why it doesn't make a difference.
> > Is the -march=k6-2 correct?
>
> Yes. Even if the above is true, splitting the K6 out like this is
> useful for the extra -march here. It certainly does not hurt (picking
> the original K6 will give proper support for the whole family, in
> needed).
>From a quick look of the gcc-3.2.2 sources it seems that except for the
3DNow! support gcc doesn't differenciate between K6 and K6-II, so this
change alone doesn't seem to make it worth adding a new processor type.
> Robert Love
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
prev parent reply other threads:[~2003-04-15 19:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-14 22:21 [RFC][2.5 patch] K6-II/K6-II: enable X86_USE_3DNOW Adrian Bunk
2003-04-14 22:27 ` Dave Jones
2003-04-14 22:06 ` Alan Cox
2003-04-15 19:37 ` Adrian Bunk
2003-04-14 22:36 ` Robert Love
2003-04-15 8:50 ` Paweł Gołaszewski
2003-04-15 19:39 ` Adrian Bunk [this message]
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=20030415193931.GS9640@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@tech9.net \
/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