public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Harvey Harrison <harvey.harrison@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC-PATCH] x86: really use __builtin_memcmp on x86_32
Date: Mon, 10 Nov 2008 08:53:16 -0800	[thread overview]
Message-ID: <1226335996.5478.41.camel@brick> (raw)
In-Reply-To: <20081110080525.GA13452@elte.hu>

On Mon, 2008-11-10 at 09:05 +0100, Ingo Molnar wrote:
> * Ingo Molnar <mingo@elte.hu> wrote:
> 
> > * Harvey Harrison <harvey.harrison@gmail.com> wrote:
> > 
> > > Impact: prevent generic code from overriding __builtin_memcmp
> > > 
> > > lib/string.c was using a generic implementation of memcmp
> > > because __HAVE_ARCH_MEMCMP was not defined and it was then doing
> > > #undef memcmp and defining a generic version.
> > > 
> > > Signed-off-by: Harvey Harrison <harvey.harrison@gmail.com>
> > > ---
> > >  arch/x86/include/asm/string_32.h |    1 +
> > >  1 files changed, 1 insertions(+), 0 deletions(-)
> > 
> > > +#define __HAVE_ARCH_MEMCMP
> > >  #define memcmp __builtin_memcmp
> > >  
> > >  #define __HAVE_ARCH_MEMCHR
> 
> doesnt work that well:
> 
>  arch/x86/kernel/built-in.o: In function `efi_guidcmp':
>  efi.c:(.text+0x108b2): undefined reference to `memcmp'
>  arch/x86/kernel/built-in.o: In function `smp_check_mpc':
>  mpparse.c:(.init.text+0x4ec6): undefined reference to `memcmp'
>  arch/x86/kernel/built-in.o: In function `powernowk8_cpu_init':
> 
> with the attached config.
> 

Just let this one go to the bitbucket.

Harvey



  reply	other threads:[~2008-11-10 16:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-10  6:12 [RFC-PATCH] x86: really use __builtin_memcmp on x86_32 Harvey Harrison
2008-11-10  7:45 ` Ingo Molnar
2008-11-10  8:05   ` Ingo Molnar
2008-11-10 16:53     ` Harvey Harrison [this message]
2008-11-10  8:38 ` Andi Kleen

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=1226335996.5478.41.camel@brick \
    --to=harvey.harrison@gmail.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    /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