From: Adrian Bunk <bunk@stusta.de>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: Andi Kleen <ak@suse.de>, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] re-add -ffreestanding
Date: Thu, 7 Sep 2006 04:23:03 +0200 [thread overview]
Message-ID: <20060907022303.GG25473@stusta.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0609070313420.6761@scrub.home>
On Thu, Sep 07, 2006 at 03:23:31AM +0200, Roman Zippel wrote:
> Hi,
>
> On Thu, 7 Sep 2006, Adrian Bunk wrote:
>
> > > Define "full libc".
> >
> > Everything described in clause 7 of ISO/IEC 9899:1999.
>
> Its behaviour is also defined by the environment, so what gcc can assume
> is rather limited and you have not shown a single example, that any such
> assumption would be invalid for the kernel.
ISO/IEC 9899:1999 clause 7 defines the libc part of a hosted environment.
> > > Explain what exactly -ffreestanding fixes, which is not valid for the
> > > kernel.
> >
> > It's simply correct since the kernel doesn't provide everything
> > described in clause 7 of ISO/IEC 9899:1999.
> >
> > And it fixes compile errors caused by the fact that gcc is otherwise
> > allowed to replace calls to any standard C function with semantically
> > equivalent calls to other standard C functions - in a hosted environment
> > the latter are guaranteed to be present.
>
> The kernel uses standard C, so your point is?
A standard C freestanding environment or a standard C hosted environment?
> You already got two NACKs from arch maintainers, why the hell are you
> still pushing this patch? The builtin functions are useful and you want to
The same people who justified removing -ffreestanding with the "it was
only added for x86-64, so dropping it should be safe" that has proven
wrong now put their arch maintainers hats on for NACKing reverting this
patch...
> force arch maintainers to have to enable every single one manually and
> to maintain a list of these functions over multiple versions of gcc?
It could be done per architecture or globally for some functions.
And it doesn't sound like a bad idea to check the current code and think
of what it does and what it should do - many architecture specific
things (like much of include/asm-i386/string.h) seem to be more
historically than architecture specific.
> bye, Roman
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
next prev parent reply other threads:[~2006-09-07 2:25 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-30 17:57 [2.6 patch] re-add -ffreestanding Adrian Bunk
2006-08-30 18:13 ` Andi Kleen
2006-08-30 18:39 ` Russell King
2006-09-06 22:37 ` Adrian Bunk
2006-09-06 23:38 ` Roman Zippel
2006-09-06 23:50 ` Adrian Bunk
2006-09-07 0:05 ` Roman Zippel
2006-09-07 0:37 ` Adrian Bunk
2006-09-07 0:47 ` Roman Zippel
2006-09-07 1:02 ` Adrian Bunk
2006-09-07 1:23 ` Roman Zippel
2006-09-07 2:23 ` Adrian Bunk [this message]
2006-09-07 10:25 ` Roman Zippel
2006-09-07 6:30 ` Russell King
2006-09-07 10:27 ` Adrian Bunk
2006-09-07 11:40 ` Roman Zippel
2006-09-07 11:43 ` Russell King
2006-09-07 14:03 ` Kyle Moffett
2006-09-07 14:25 ` Russell King
2006-09-07 14:29 ` Roman Zippel
-- strict thread matches above, loose matches on Subject: below --
2006-08-21 21:21 Adrian Bunk
2006-08-21 21:24 ` Andi Kleen
2006-08-21 21:46 ` Adrian Bunk
2006-08-21 22:09 ` Andi Kleen
2006-08-21 22:24 ` Adrian Bunk
2006-08-21 22:27 ` Andi Kleen
2006-08-21 22:58 ` Adrian Bunk
2006-08-21 23:13 ` Andi Kleen
2006-08-22 3:37 ` Kyle Moffett
2006-08-22 10:37 ` Andi Kleen
2006-08-22 11:18 ` Adrian Bunk
2006-08-21 23:33 ` 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=20060907022303.GG25473@stusta.de \
--to=bunk@stusta.de \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--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 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.