All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Ungerer <gerg@snapgear.com>
To: linux-m68k@vger.kernel.org
Cc: Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: [PATCH] m68k: remove arch specific non-optimized memcmp()
Date: Mon, 14 Feb 2011 17:39:53 +1000	[thread overview]
Message-ID: <4D58DC49.5060800@snapgear.com> (raw)
In-Reply-To: <4D548FBC.2050902@snapgear.com>

Hi Geert,

> On Fri, Feb 11, 2011 at 02:24, Greg Ungerer <gerg@snapgear.com> wrote:
>> On 07/02/11 10:57, Greg Ungerer wrote:
>>>
>>> m68k: remove arch specific non-optimized memcmp()
>>>
>>> The m68k arch implements its own memcmp() function. It is not optimized
>>> in any way (it is the most strait forward coding of memcmp you can get).
>>> Remove it and use the kernels standard memcmp() implementation.
>>>
>>> This also goes part of the way to fixing a regression caused by commit
>>> ea61bc461d09e8d331a307916530aaae808c72a2 ("m68k/m68knommu: merge MMU and
>>> non-MMU string.h"), which breaks non-coldfire non-mmu builds (which is
>>> the 68x328 and 68360 families). They currently have no memcmp() function
>>> defined, since there is none in the m68knommu/lib functions.
>>>
>>> Signed-off-by: Greg Ungerer<gerg@uclinux.org>
>>
>> Does anyone have any comments on this?
>
> Sorry, haven't tried it yet.
>
> Shouldn't you also remove the "#define memcmp(d, s, n)"?

I considered doing that. But leaving that in and going through
__builtin_memcmp() gives the compiler a chance to optimize
some simple calls to memcmp to inline instructions. In practice
it might not matter much, and I don't mind at all leaving it out
if you prefer.


>> I would like to push to Linus very soon now (so in the current
>> 2.6.38-rc). It seems like a clean fix on its own, but in particular
>> it helps me fix the problems caused by commit
>> ea61bc461d09e8d331a307916530aaae808c72a2
>> ("m68k/m68knommu: merge MMU and non-MMU string.h"
>>
>> I have compile and run tested on m68knommu targets, and compile
>> tested on m68k targets.
>
> If it compiles, it's good; if it boots, it's perfect ;-)

Unfortunately I don't have any true 68k machines to run
this on. I do have a lot of ColdFire boards though :-)

Regards
Greg



>>> ---
>>> Â arch/m68k/include/asm/string.h | Â  Â 4 +---
>>>  arch/m68k/lib/string.c         |   11 -----------
>>> Â 2 files changed, 1 insertions(+), 14 deletions(-)
>>>
>>> diff --git a/arch/m68k/include/asm/string.h
>>> b/arch/m68k/include/asm/string.h
>>> index 65b1312..ffc3c3f 100644
>>> --- a/arch/m68k/include/asm/string.h
>>> +++ b/arch/m68k/include/asm/string.h
>>> @@ -102,11 +102,9 @@ static inline int strcmp(const char *cs, const char
>>> *ct)
>>>
>>> Â #define __HAVE_ARCH_MEMMOVE
>>> Â extern void *memmove(void *, const void *, __kernel_size_t);
>>> +#endif /* CONFIG_COLDFIRE */
>>>
>>> -#define __HAVE_ARCH_MEMCMP
>>> -extern int memcmp(const void *, const void *, __kernel_size_t);
>>> Â #define memcmp(d, s, n) __builtin_memcmp(d, s, n)
>>> -#endif /* CONFIG_COLDFIRE */
>>>
>>> Â #define __HAVE_ARCH_MEMSET
>>> Â extern void *memset(void *, int, __kernel_size_t);
>>> diff --git a/arch/m68k/lib/string.c b/arch/m68k/lib/string.c
>>> index 4253f87..d399c5f 100644
>>> --- a/arch/m68k/lib/string.c
>>> +++ b/arch/m68k/lib/string.c
>>> @@ -243,14 +243,3 @@ void *memmove(void *dest, const void *src, size_t n)
>>> Â  Â  Â  Â return xdest;
>>> Â }
>>> Â EXPORT_SYMBOL(memmove);
>>> -
>>> -int memcmp(const void *cs, const void *ct, size_t count)
>>> -{
>>> - Â  Â  Â  const unsigned char *su1, *su2;
>>> -
>>> - Â  Â  Â  for (su1 = cs, su2 = ct; count> Â 0; ++su1, ++su2, count--)
>>> - Â  Â  Â  Â  Â  Â  Â  if (*su1 != *su2)
>>> - Â  Â  Â  Â  Â  Â  Â  Â  Â  Â  Â  return *su1< Â *su2 ? -1 : +1;
>>> - Â  Â  Â  return 0;
>>> -}
>>> -EXPORT_SYMBOL(memcmp);
>
> Gr{oetje,eeting}s,
>
> Â  Â  Â  Â  Â  Â  Â  Â  Â  Â  Â  Â  Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
> Â  Â  Â  Â  Â  Â  Â  Â  Â  Â  Â  Â  Â  Â Â  Â Â  -- Linus Torvalds

------------------------------------------------------------------------
Greg Ungerer  --  Principal Engineer        EMAIL:     gerg@snapgear.com
SnapGear Group, McAfee                      PHONE:       +61 7 3435 2888
8 Gardner Close                             FAX:         +61 7 3217 5323
Milton, QLD, 4064, Australia                WEB: http://www.SnapGear.com

  parent reply	other threads:[~2011-02-14  7:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-07  0:57 [PATCH] m68k: remove arch specific non-optimized memcmp() Greg Ungerer
2011-02-11  1:24 ` Greg Ungerer
2011-02-11  6:46   ` Geert Uytterhoeven
2011-02-14  7:39   ` Greg Ungerer [this message]
2011-02-15 19:50 ` Geert Uytterhoeven
2011-02-15 23:41   ` Greg Ungerer

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=4D58DC49.5060800@snapgear.com \
    --to=gerg@snapgear.com \
    --cc=geert@linux-m68k.org \
    --cc=linux-m68k@vger.kernel.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 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.