public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: Adrian Bunk <bunk@stusta.de>, Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org
Subject: Re: 2.6.16-rc3-mm1: i386 compilation broken
Date: Wed, 15 Feb 2006 14:32:16 +0100	[thread overview]
Message-ID: <200602151432.16648.ak@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.61.0602151404141.9696@scrub.home>

On Wednesday 15 February 2006 14:19, Roman Zippel wrote:
> Hi,
> 
> On Tue, 14 Feb 2006, Andi Kleen wrote:
> 
> > Ok then the -ffreestanding was apparently still needed on other architectures too.
> > I guess that part of the patch can be just dropped.
> 
> The main problem is still the sprintf optimization, so 
> --fno-builtin-sprintf should fix it too.

Currently it will just use out of line strcpy etc. on x86-64.
Not quite optimal - probably need to go back to fix this


> That leaves only the single strchr, which is caused by an strpbrk 
> optimization in zoran_procfs.c, where we could use --fno-builtin-strpbrk 
> or simply directly replace that strpbrk with strchr.
> 
> If we really want to keep -ffreestanding, 

I think we should drop it, just i386 has to be fixed first.

> we have to rework how string.h  
> is organized to allow enabling builtin functions, but still provide fall 
> back functions. For example we had to add a lot of "#define foo 
> __builtin_foo" to linux/string.h and "#undef foo" to lib/string.c. 

Yes it would be ugly.


-Andi

  reply	other threads:[~2006-02-15 13:32 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-14  9:41 2.6.16-rc3-mm1 Andrew Morton
2006-02-14 11:07 ` 2.6.16-rc3-mm1 Marc Koschewski
2006-02-14 11:16 ` 2.6.16-rc3-mm1 Michal Piotrowski
2006-02-14 12:16   ` 2.6.16-rc3-mm1 Sander
2006-02-14 12:46     ` 2.6.16-rc3-mm1 Michal Piotrowski
2006-02-14 13:17 ` 2.6.16-rc3-mm1: i386 compilation broken Adrian Bunk
2006-02-14 13:27   ` Andi Kleen
2006-02-14 13:54     ` Michal Piotrowski
2006-02-14 20:23       ` Andrew Morton
2006-02-14 21:05         ` Andi Kleen
2006-02-14 21:08     ` Adrian Bunk
2006-02-15 13:19     ` Roman Zippel
2006-02-15 13:32       ` Andi Kleen [this message]
2006-02-14 14:00 ` 2.6.16-rc3-mm1: ISDN_DRV_GIGASET driver Adrian Bunk
2006-02-15  1:57   ` Tilman Schmidt
2006-02-15 22:10     ` Adrian Bunk
2006-02-14 14:33 ` 2.6.16-rc3-mm1 Brice Goglin
2006-02-14 20:28   ` 2.6.16-rc3-mm1 Andrew Morton
2006-02-14 23:26     ` 2.6.16-rc3-mm1 Con Kolivas
2006-02-14 23:38       ` 2.6.16-rc3-mm1 Brice Goglin
2006-02-15  2:58       ` 2.6.16-rc3-mm1 Andrew Morton
2006-02-14 15:22 ` [-mm patch] block/blktrace.c: make blk_trace_cleanup() static Adrian Bunk
2006-02-14 15:23   ` Jens Axboe
2006-02-16 23:28 ` 2.6.16-rc3-mm1 Pavel Machek

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=200602151432.16648.ak@suse.de \
    --to=ak@suse.de \
    --cc=akpm@osdl.org \
    --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