From: Matthias Fuchs <matthias.fuchs@esd-electronics.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] CFG_64BIT_xxx and friends
Date: Mon, 8 Sep 2008 13:27:05 +0200 [thread overview]
Message-ID: <200809081327.06175.matthias.fuchs@esd-electronics.com> (raw)
In-Reply-To: <20080908130046.63a779ba@hskinnemo-gx745.norway.atmel.com>
Here is the U-Boot size for the PLU405 board (405EP-based) with
and without
#define CFG_64BIT_VSPRINTF
#define CFG_64BIT_STRTOUL
.
without:
# ppc_4xx-size u-boot
text data bss dec hex filename
289568 17532 301312 608412 9489c u-boot
with 64bit format handling:
# ppc_4xx-size u-boot
text data bss dec hex filename
291368 17532 301312 610212 94fa4 u-boot
So the difference is 1800 bytes on this architecture.
Matthias
On Monday 08 September 2008 13:00, Haavard Skinnemoen wrote:
> Stefan Roese <sr@denx.de> wrote:
> > > Seriously: How much of code size are we talking about? And activating
> > > / deactivation the feature is not so trivial as it affects the
> > > printf() format specifiers we have to use.
> >
> > I'm with Wolfgang here and think it would be best to unconditionally support
> > the 64bit printf format too.
>
> Would be nice to see some numbers first though. I suspect there won't
> be much difference, but it could be the printf() implementation does
> something stupid, and it's much easier to tell when the config symbol
> is still in place.
>
> Haavard
>
>
next prev parent reply other threads:[~2008-09-08 11:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-04 14:09 [U-Boot] CFG_64BIT_xxx and friends Matthias Fuchs
2008-09-06 23:12 ` Wolfgang Denk
2008-09-06 23:05 ` Jean-Christophe PLAGNIOL-VILLARD
2008-09-06 23:37 ` Wolfgang Denk
2008-09-08 7:43 ` Stefan Roese
2008-09-08 11:00 ` Haavard Skinnemoen
2008-09-08 11:27 ` Matthias Fuchs [this message]
2008-09-08 11:54 ` Haavard Skinnemoen
2008-09-08 12:23 ` Haavard Skinnemoen
2008-09-09 1:58 ` Jerry Van Baren
2008-09-09 7:11 ` Haavard Skinnemoen
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=200809081327.06175.matthias.fuchs@esd-electronics.com \
--to=matthias.fuchs@esd-electronics.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 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.