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 02:37:58 +0200 [thread overview]
Message-ID: <20060907003758.GD25473@stusta.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0609070202040.6761@scrub.home>
On Thu, Sep 07, 2006 at 02:05:59AM +0200, Roman Zippel wrote:
> Hi,
>
> On Thu, 7 Sep 2006, Adrian Bunk wrote:
>
> > it's correct, since with -ffreestanding gcc no longer has the right to
> > assume it had a full libc available.
>
> BS, even without it gcc can't make such assumption.
> There is not a single optimization, which would be invalid in a kernel
> environment and would be "fixed" by this option, so please stop this
> nonsense.
You are wrong.
Section 5.1.2.2.2 of ISO/IEC 9899:1999 says:
In a hosted environment, a program may use all functions, macros, type
definitions, and objects described in the library clause (clause 7).
Since a hosted environment means gcc+libc, it's therefore clear that gcc
can assume the presence of a full libc if gcc isn't told that it's used
as a freestanding environment.
> 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 0:38 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 [this message]
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
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=20060907003758.GD25473@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox