All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Matt Mackall <mpm@selenic.com>,
	vital@ilport.com.ua
Subject: Re: [PATCH] reduce inlined x86 memcpy by 2 bytes
Date: Sun, 20 Mar 2005 14:17:37 +0100	[thread overview]
Message-ID: <20050320131737.GD4449@stusta.de> (raw)
In-Reply-To: <200503181121.42809.vda@port.imtp.ilyichevsk.odessa.ua>

Hi Denis,

what do your benchmarks say about replacing the whole assembler code 
with a

  #define __memcpy __builtin_memcpy

?

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


  parent reply	other threads:[~2005-03-20 13:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-18  9:21 [PATCH] reduce inlined x86 memcpy by 2 bytes Denis Vlasenko
2005-03-18 10:07 ` Denis Vlasenko
2005-03-20 13:17 ` Adrian Bunk [this message]
2005-03-22  6:40   ` Denis Vlasenko

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=20050320131737.GD4449@stusta.de \
    --to=bunk@stusta.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpm@selenic.com \
    --cc=vda@port.imtp.ilyichevsk.odessa.ua \
    --cc=vital@ilport.com.ua \
    /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.