public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Kim Phillips <kim.phillips@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC][PATCH] Update malloc to dlmalloc version 2.8.4
Date: Tue, 7 Jul 2009 15:47:59 -0500	[thread overview]
Message-ID: <20090707154759.2005cc75.kim.phillips@freescale.com> (raw)
In-Reply-To: <720F17F7-4145-49F8-9554-5A381319446F@kernel.crashing.org>

On Tue, 7 Jul 2009 14:50:31 -0500
Kumar Gala <galak@kernel.crashing.org> wrote:

> Those would help if the data structs had gotten bigger.  In this case  
> the code itself is just larger.

fyi, gcc4.4.0 apparently doesn't like to emit ld/st multiple insns as
much as prior versions did.

NAND bootstraps don't fit, e.g., because of the code density savings
ld/st multiples make:  e.g., mpc8313erdb.o is 322 bytes text with gcc
4.2.1 and is now 476 bytes text with gcc4.4...

btw, fixes for upstream gcc should be under way in the next couple of
days.

Kim

  parent reply	other threads:[~2009-07-07 20:47 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
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 [this message]
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=20090707154759.2005cc75.kim.phillips@freescale.com \
    --to=kim.phillips@freescale.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox