From: Adrian Bunk <bunk@stusta.de>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] Use -ffreestanding? (fwd)
Date: Mon, 22 Nov 2004 13:46:18 +0100 [thread overview]
Message-ID: <20041122124618.GJ3007@stusta.de> (raw)
In-Reply-To: <Pine.LNX.4.58.0411212208200.20993@ppc970.osdl.org>
On Sun, Nov 21, 2004 at 10:10:28PM -0800, Linus Torvalds wrote:
>
>
> On Mon, 22 Nov 2004, Adrian Bunk wrote:
> >
> > for the kernel, it would be logical to use -ffreestanding. The kernel is
> > not a hosted environment with a standard C library.
> >
> > Linus agreed that it would make sense.
>
> Note that while I agree that it sounds sensible, it would be good to have
> somebody specify exactly what changes from the use of "-ffreestanding".
>
> I _assume_ that all the things that gcc takes for granted are things that
> Linux already has its own definitions for, and that -ffreestanding doesn't
> actually change anything for at least the regular architectures. But if
> there is any object code changes, can you check those out and explain
> them?
Andi Kleen reported:
Newer gcc rewrites sprintf(buf,"%s",str) to strcpy(buf,str) transparently.
This is only true with unit-at-a-time (disabled on i386 but enabled
on x86_64). The Linux kernel doesn't offer a standard C library, and
such transparent replacements of kernel functions with builtins are
quite fragile.
Even with -ffreestanding, it's still possilble to explicitely use a gcc
builtin if desired.
> Linus
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:[~2004-11-22 12:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-22 5:49 Adrian Bunk
2004-11-22 6:10 ` Linus Torvalds
2004-11-22 12:46 ` Adrian Bunk [this message]
2004-11-22 8:36 ` Jan Engelhardt
2004-11-22 12:48 ` Adrian Bunk
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=20041122124618.GJ3007@stusta.de \
--to=bunk@stusta.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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
Powered by JetHome