porting uClibc to a new arch
Ricard Wanderlof
ricard.wanderlof at axis.com
Wed Jun 3 08:02:47 UTC 2009
On Wed, 3 Jun 2009, Florent DEFAY wrote:
> I am working on a toolchain for a new arch.
> We already ported binutils, GCC and Newlib.
>
> This is an embedded micro-controller. There is no OS because we don't need one.
> We are interested particularly in printf and scanf, which Newlib can do.
>
> The problem is that program linked with Newlib calling printf are too
> large. The target is 16 bit and RAM is addressed on 16 bit. We thought
> that replacing Newlib by uClibc could solve the problem.
Without any research into the matter, I would think that uClibc would be
larger than Newlib. To my mind, uClibc is geared towards the larger end of
the embedded market, i.e. 32-bit processors with MMU's (even if there are
exceptions), megabytes of memory etc, whereas Newlib is intended to be
small. Also uClibc is really designed as a small-scale replacement to
glibc which in turn is geared towards Linux. There are exceptions, but
that's the general direction.
You seem to have a "small" system with about 64Kbytes of memory at the
most. So uClibc wouldn't be my first choice.
/Ricard
--
Ricard Wolf Wanderlöf ricardw(at)axis.com
Axis Communications AB, Lund, Sweden www.axis.com
Phone +46 46 272 2016 Fax +46 46 13 61 30
More information about the uClibc
mailing list