From: Linus Torvalds <torvalds@osdl.org>
To: Adrian Bunk <bunk@stusta.de>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] Use -ffreestanding? (fwd)
Date: Sun, 21 Nov 2004 22:10:28 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.58.0411212208200.20993@ppc970.osdl.org> (raw)
In-Reply-To: <20041122054959.GI3007@stusta.de>
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?
Linus
next prev parent reply other threads:[~2004-11-22 6:10 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 [this message]
2004-11-22 12:46 ` Adrian Bunk
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=Pine.LNX.4.58.0411212208200.20993@ppc970.osdl.org \
--to=torvalds@osdl.org \
--cc=akpm@osdl.org \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®