From: Andreas Schwab <schwab@suse.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Pawe?? Sikora <pluto@pld-linux.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: unresolved symbol __udivsi3_i4
Date: Fri, 24 Sep 2004 14:49:08 +0200 [thread overview]
Message-ID: <je4qlnltmj.fsf@sykes.suse.de> (raw)
In-Reply-To: <20040924112954.GI22710@lug-owl.de> (Jan-Benedict Glaw's message of "Fri, 24 Sep 2004 13:29:54 +0200")
Jan-Benedict Glaw <jbglaw@lug-owl.de> writes:
> Well, the kernel is (or should be) a freestanding program, so it
> shouldn't use *any* external code (and it doesn't, intentionally).
> We're working hard not linking in libgcc.a
libgcc is an intrinsic part of the freestanding implementation provided by
the compiler, just like <stdarg.h>.
> So people started doing freestanding implementations of eg. __udivsi3 in
> their kernel files. But why should they? GCC also could have emitted
> inlined code to do that task, without ever calling an external function
> for that.
Inlining can be less efficient due to icache issues.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
prev parent reply other threads:[~2004-09-24 12:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-24 2:10 unresolved symbol __udivsi3_i4 Donald Duckie
2004-09-24 2:59 ` Randy.Dunlap
2004-09-24 3:23 ` Randy.Dunlap
2004-09-24 4:49 ` Donald Duckie
2004-09-24 23:14 ` Randy.Dunlap
2004-09-24 6:01 ` Paweł Sikora
2004-09-24 8:33 ` Geert Uytterhoeven
2004-09-24 10:52 ` Jan-Benedict Glaw
2004-09-24 11:15 ` Geert Uytterhoeven
2004-09-24 11:29 ` Jan-Benedict Glaw
2004-09-24 12:49 ` Andreas Schwab [this message]
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=je4qlnltmj.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pluto@pld-linux.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