From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC][PATCH] Update malloc to dlmalloc version 2.8.4
Date: Tue, 7 Jul 2009 14:34:32 -0400 [thread overview]
Message-ID: <200907071434.33729.vapier@gentoo.org> (raw)
In-Reply-To: <BD5CF5B3-A666-49A1-9E32-7F88D8DB9057@kernel.crashing.org>
On Tuesday 07 July 2009 12:30:18 Kumar Gala wrote:
> On Jul 7, 2009, at 11:27 AM, Kumar Gala wrote:
> > Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
> > ---
> > This is an attempt at using dlmalloc v2.8.4. Its a work in
> > progress, but
> > wanted to post to see what peoples feelings are on updating. This
> > version
> > resolves all the various warnings we see w/gcc4.4 and the older
> > version of
> > dlmalloc however the trade of is the code size has increased.
> >
> > I still need to see if we need to hand relocate the global structs
> > or not.
> >
> > This diff is just of malloc.h to see how things are cfg, and of
> > dmalloc.src vs dmalloc.c to see the changes to it.
>
> Here are some size #'s
>
> [galak at blarg u-boot-85xx]$ size u-boot
> text data bss dec hex filename
> 392040 50536 41957 484533 764b5 u-boot
> 397660 49500 42397 489557 77855 u-boot (new dlmalloc)
>
> [galak at blarg u-boot-85xx]$ size common/dlmalloc.o
> text data bss dec hex filename
> 4768 1056 56 5880 16f8 common/dlmalloc.o
> 10390 16 492 10898 2a92 common/dlmalloc.o (new
> dlmalloc)
to say it has increased is an understatement. i cant imagine the upstream
code increasing that much. perhaps we had trimmed/customized the
implementation so as to shrink it ?
> old dlmalloc:
> [galak at blarg u-boot-85xx]$ nm --size-sort common/dlmalloc.o
use the bloatcheck script to do a human readable compare between the two
objects. you can find it in the linux kernel.
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
Url : http://lists.denx.de/pipermail/u-boot/attachments/20090707/87aa3b1e/attachment.pgp
next prev parent reply other threads:[~2009-07-07 18:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-07 16:27 [U-Boot] [RFC][PATCH] Update malloc to dlmalloc version 2.8.4 Kumar Gala
2009-07-07 16:30 ` Kumar Gala
2009-07-07 18:34 ` Mike Frysinger [this message]
2009-07-07 19:16 ` T Ziomek
2009-07-07 19:50 ` Kumar Gala
2009-07-07 20:02 ` Scott Wood
2009-07-07 20:22 ` Jean-Christophe PLAGNIOL-VILLARD
2009-07-07 20:25 ` Scott Wood
2009-07-07 22:24 ` Kumar Gala
2009-07-08 5:58 ` Mike Frysinger
2009-07-08 6:22 ` Robin Getz
2009-07-08 6:58 ` Peter Tyser
2009-07-08 18:57 ` Mike Frysinger
2009-07-07 20:39 ` T Ziomek
2009-07-07 20:47 ` Kim Phillips
2009-07-07 19:49 ` Kumar Gala
2009-07-08 4:37 ` Robin Getz
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=200907071434.33729.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.