public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Adrian Bunk <bunk@stusta.de>
Cc: Roman Zippel <zippel@linux-m68k.org>, linux-kernel@vger.kernel.org
Subject: Re: Cleanup possibility in asm-i386/string.h
Date: Fri, 10 Feb 2006 01:23:35 +0100	[thread overview]
Message-ID: <200602100123.36077.ak@suse.de> (raw)
In-Reply-To: <20060210000523.GE3524@stusta.de>

On Friday 10 February 2006 01:05, Adrian Bunk wrote:
> On Tue, Feb 07, 2006 at 01:39:50PM +0100, Roman Zippel wrote:
> > Hi,
> > 
> > On Tue, 7 Feb 2006, Andi Kleen wrote:
> > 
> > > > This means you define a prototype for the builtin function and not for the 
> > > > normal function. I'm not sure this is really intended.
> > > 
> > > What good would be a prototype for a symbol that is defined to a different symbol?
> > 
> > The point is you define a prototype for a builtin function, I'm not sure 
> > that's a good thing to do.
> > Actually I'd prefer to remove -ffreestanding again, especially because it
> > disables builtin functions, which we have to painfully enable all again 
> > one by one, instead of leaving it just to gcc.
> 
> I remember playing with using more gcc builtins in the kernel some time 
> ago, and some gcc builtin used a different library function, which was a 
> function the kernel did not supply.

It works fine on x86-64. If something is missing it can be also supplied.

-Andi


  reply	other threads:[~2006-02-10  0:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-07 11:15 Cleanup possibility in asm-i386/string.h Andi Kleen
2006-02-07 12:00 ` Roman Zippel
2006-02-07 12:08   ` Andi Kleen
2006-02-07 12:39     ` Roman Zippel
2006-02-10  0:05       ` Adrian Bunk
2006-02-10  0:23         ` Andi Kleen [this message]
2006-02-10  1:00           ` Kyle Moffett
2006-02-10 13:02           ` Roman Zippel
2006-02-10 13:49             ` Andi Kleen
2006-02-10 14:46               ` Roman Zippel
2006-02-10 15:02                 ` Andi Kleen
2006-02-10  0:53         ` Roman Zippel

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=200602100123.36077.ak@suse.de \
    --to=ak@suse.de \
    --cc=bunk@stusta.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zippel@linux-m68k.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox