From: Pavel Machek <pavel@suse.cz>
To: Dave Jones <davej@suse.de>,
Ruth Ivimey-Cook <Ruth.Ivimey-Cook@ivimey.org>,
Luigi Genoni <kernel@Expansa.sns.it>,
"J.A. Magallon" <jamagallon@able.es>,
Luca Barbieri <ldb@ldb.ods.org>,
Marcelo Tosatti <marcelo@conectiva.com.br>,
Linux-Kernel ML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] [2.4] [2.5] [i386] Add support for GCC 3.1 -march=pentium{-mmx,3,4}
Date: Mon, 27 May 2002 08:53:02 +0000 [thread overview]
Message-ID: <20020527085301.A38@toy.ucw.cz> (raw)
In-Reply-To: <Pine.LNX.4.44.0205260128110.2047-100000@Expansa.sns.it> <Pine.LNX.4.44.0205260044270.10923-100000@sharra.ivimey.org> <20020526023009.G16102@suse.de>
Hi!
> I would be (pleasantly) surprised to see gcc turn a C memcpy into faster
> assembly than our current implementation. And I'll bet
gcc has hand-coded assembly inside itself, if gcc compiled memcpy is slower
than hand-optimized one, you found a compiler bug.
> it'll stay that way for some time.
> gcc has come on in leaps and bounds, but for something as performance
> critical as memory copying/clearing, hand tuned assembly wins hands down.
> Even AMD's/Intel's performance guides suggest doing this. It's the only
> way to fly.
--
Philips Velo 1: 1"x4"x8", 300gram, 60, 12MB, 40bogomips, linux, mutt,
details at http://atrey.karlin.mff.cuni.cz/~pavel/velo/index.html.
next prev parent reply other threads:[~2002-05-28 20:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-25 21:01 Luca Barbieri
2002-05-25 23:37 ` J.A. Magallon
2002-05-25 22:53 ` Dave Jones
2002-05-25 23:29 ` Luigi Genoni
2002-05-25 23:49 ` Ruth Ivimey-Cook
2002-05-26 0:30 ` Dave Jones
2002-05-27 8:53 ` Pavel Machek [this message]
2002-05-29 11:42 ` Dave Jones
2002-05-29 19:57 ` Pavel Machek
2002-05-30 6:40 ` Jan Hubicka
2002-05-30 10:25 ` David Woodhouse
2002-05-30 10:45 ` Jan Hubicka
2002-05-26 1:08 ` J.A. Magallon
2002-05-26 0:21 ` Dave Jones
[not found] ` <1022380785.11859.59.camel@irongate.swansea.linux.org.uk>
2002-05-26 9:11 ` J.A. Magallon
2002-05-26 19:14 ` Alan Cox
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=20020527085301.A38@toy.ucw.cz \
--to=pavel@suse.cz \
--cc=Ruth.Ivimey-Cook@ivimey.org \
--cc=davej@suse.de \
--cc=jamagallon@able.es \
--cc=kernel@Expansa.sns.it \
--cc=ldb@ldb.ods.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@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
all inboxes | Powered by JetHome®