From: Arjan van de Ven <arjan@infradead.org>
To: Bastian Blank <bastian@waldi.eu.org>
Cc: Linus Torvalds <torvalds@osdl.org>,
Christoph Hellwig <hch@infradead.org>,
Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>,
Richard Henderson <rth@twiddle.net>
Subject: Re: removing bcopy... because it's half broken
Date: Tue, 11 Jan 2005 11:32:12 +0100 [thread overview]
Message-ID: <1105439533.3917.22.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <20050111101010.GB27768@wavehammer.waldi.eu.org>
On Tue, 2005-01-11 at 11:10 +0100, Bastian Blank wrote:
> On Sun, Jan 09, 2005 at 12:42:42PM -0800, Linus Torvalds wrote:
> > On Sun, 9 Jan 2005, Christoph Hellwig wrote:
> > > We're building with -ffreestanding now, so gcc isn't allowed to emit
> > > any calls to standard library functions.
> > Bzzt. It still emits calls to libgcc.
>
> Yes. This means IMHO that the image and every module needs to link
> against libgcc to include the required symbols. It is rather annoying to
> see modules asking for libgcc symbols.
I disagree with your first sentence: The kernel provides the required
symbols (bcopy is special here, it no longer gets emitted by gcc since
like gcc version 2.6); the ones the kernel does NOT provide are
generally undesirable in kernel spec, eg floating point and 64 bit
divisions...
next prev parent reply other threads:[~2005-01-11 10:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-09 19:23 removing bcopy... because it's half broken Arjan van de Ven
2005-01-09 19:39 ` Ralf Baechle
2005-01-09 20:03 ` Russell King
2005-01-09 20:19 ` Linus Torvalds
2005-01-09 20:33 ` Arjan van de Ven
2005-01-09 20:34 ` Christoph Hellwig
2005-01-09 20:42 ` Linus Torvalds
2005-01-11 10:10 ` Bastian Blank
2005-01-11 10:32 ` Arjan van de Ven [this message]
2005-01-11 16:10 ` Linus Torvalds
2005-01-09 23:38 ` Richard Henderson
2005-01-10 0:43 ` Adrian Bunk
2005-01-10 16:55 ` Matthias-Christian Ott
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=1105439533.3917.22.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=akpm@osdl.org \
--cc=bastian@waldi.eu.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rth@twiddle.net \
--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;
as well as URLs for NNTP newsgroup(s).