From: "M. R. Brown" <mrbrown@0xd6.org>
To: Benoit Poulot-Cazajous <poulot@ifrance.com>
Cc: nbecker@fred.net, linux-kernel@vger.kernel.org
Subject: Re: On K7, -march=k6 is good (Was Re: Why no -march=athlon?)
Date: Wed, 19 Dec 2001 11:56:16 -0600 [thread overview]
Message-ID: <20011219175616.GD19236@0xd6.org> (raw)
In-Reply-To: <x88r8ptki37.fsf@rpppc1.hns.com> <20011217174020.GA24772@0xd6.org> <lnitb3drx6.fsf_-_@walhalla.agaha>
In-Reply-To: <lnitb3drx6.fsf_-_@walhalla.agaha>
[-- Attachment #1: Type: text/plain, Size: 802 bytes --]
* Benoit Poulot-Cazajous <poulot@ifrance.com> on Wed, Dec 19, 2001:
>
> But gcc-2.95,x _supports_ "-march=k6", and we should use that instead of
> "-march-i686".
>
No, k6 != athlon. IIRC, the i686 optimization is closer to the Athlon than
the k6 opt.
>
> before the patch :
> 1017.92user 261.80system 24:39.89elapsed 86%CPU
> 706.33user 160.79system 16:23.61elapsed 88%CPU
> 1787.38user 418.76system 43:35.97elapsed 84%CPU
>
> after the patch :
> 1018.42user 253.85system 24:44.68elapsed 85%CPU
> 704.89user 151.76system 16:16.14elapsed 87%CPU
> 1786.96user 410.76system 43:05.32elapsed 85%CPU
>
> The improvement in system time is nice.
>
Er, there's not much difference...
Curious, what happens when you compile using gcc 3.0.1 against
-march=athlon?
M. R.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2001-12-19 17:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-17 14:59 Why no -march=athlon? nbecker
2001-12-17 15:54 ` Dominik Mierzejewski
2001-12-17 17:40 ` M. R. Brown
2001-12-19 17:46 ` On K7, -march=k6 is good (Was Re: Why no -march=athlon?) Benoit Poulot-Cazajous
2001-12-19 17:56 ` M. R. Brown [this message]
2001-12-19 18:39 ` nbecker
2001-12-19 18:47 ` M. R. Brown
2001-12-19 18:52 ` J Sloan
2001-12-19 19:01 ` Josh McKinney
2001-12-19 19:21 ` M. R. Brown
2001-12-19 19:28 ` J Sloan
2001-12-19 19:38 ` Allan Sandfeld
2001-12-19 21:40 ` Benoit Poulot-Cazajous
-- strict thread matches above, loose matches on Subject: below --
2001-12-19 20:33 RaúlNúñez de Arenas Coronado
2001-12-20 0:06 ` Alessandro Suardi
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=20011219175616.GD19236@0xd6.org \
--to=mrbrown@0xd6.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nbecker@fred.net \
--cc=poulot@ifrance.com \
/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.