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