On Mon, Apr 24, 2006 at 09:30:37PM -0500, erik quanstrom wrote: > On Mon Apr 24 21:16:57 CDT 2006, [EMAIL PROTECTED] wrote: > > On Mon, Apr 24, 2006 at 02:37:21PM -0600, Ronald G Minnich wrote: > > > This program: > > > > > > compiles to a 512KB binary on linux with -static > > > > glibc is bloated, printf and strtoul are also quite large. [..,] > > noooo.... you're kidding, right?
What I meant is that relative to some other (commonly used) routines within dietlibc, printf and stroul are large in object size terms. I should have written the above as two sentances. The biggest things seem to be printf support, perror support, and strtoul. __v_printf |080484b8| T | FUNC|00000773| |.text __dtostr |08048cc7| T | FUNC|000003ae| |.text sys_errlist |08049650| R | OBJECT|000001f8| |.rodata __umoddi3 |08049400| T | FUNC|000001e5| |.text __udivdi3 |080492c0| T | FUNC|0000013e| |.text strtoul |080482f0| T | FUNC|0000010e| |.text __lltostr |080490ec| T | FUNC|000000db| |.text __ltostr |080491c8| T | FUNC|00000099| |.text strtol |08048268| T | FUNC|00000086| |.text perror |080481ec| T | FUNC|0000007a| |.text compare to main: main |080480bc| T | FUNC|000000d6| |.text The dietlibc versions of the algorithms have generally been written to be small, rather than fast. DF
