9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] impressive
Date: Tue, 25 Apr 2006 05:20:19 -0500	[thread overview]
Message-ID: <5ff0a30a1e679e61ff04ca7a4cdcfa4c@quanstro.net> (raw)

i have not had a chance to look at dietlibc printf functions. the gnu
version is extra jumbo, and the code is very difficult to read.  but
printf is a pretty big set of functions, regardless.

it's curious that __lltostr is a different functino tha __ltostr.

as rob loves to point out, for small values of n, simple algorithms are
best.  n is usually small.  so i think it's generally a incorrect to
contrast small and fast.

- erik

On Mon Apr 24 21:50:10 CDT 2006, dfawcus@cisco.com wrote:
> On Mon, Apr 24, 2006 at 09:30:37PM -0500, erik quanstrom wrote:
> > On Mon Apr 24 21:16:57 CDT 2006, dfawcus@cisco.com wrote:
> > > 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


             reply	other threads:[~2006-04-25 10:20 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-25 10:20 erik quanstrom [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-05-10  0:45 erik quanstrom
2006-05-10  2:09 ` Lyndon Nerenberg
2006-05-10  3:35   ` David Arnold
2006-05-10  4:03     ` Lyndon Nerenberg
2006-05-08 22:02 erik quanstrom
2006-04-27  2:13 erik quanstrom
2006-04-27  1:35 erik quanstrom
2006-04-27  1:23 erik quanstrom
2006-04-27  5:08 ` Micah Stetson
2006-04-27  1:10 erik quanstrom
2006-04-27  2:06 ` Jack Johnson
2006-04-26  3:24 jmk
2006-04-26  2:38 erik quanstrom
2006-04-26  0:55 erik quanstrom
2006-04-26  1:07 ` Roman Shaposhnick
2006-04-26  0:26 erik quanstrom
2006-04-26  0:48 ` geoff
2006-04-26  0:54   ` Roman Shaposhnick
2006-04-26  0:53 ` Roman Shaposhnick
2006-04-26  2:15   ` Taj Khattra
2006-04-26  4:59     ` David Leimbach
2006-04-26 12:37       ` Anthony Sorace
2006-04-26 15:28     ` Rian Hunter
2006-04-26 16:39     ` Micah Stetson
2006-04-26 18:02       ` Bruce Ellis
2006-04-26 20:14         ` Micah Stetson
2006-05-08 14:50       ` Harri Haataja
2006-05-08 15:04         ` LiteStar numnums
2006-05-08 15:12           ` Charles Forsyth
2006-05-08 20:08             ` Micah Stetson
2006-05-08 20:52             ` LiteStar numnums
2006-05-08 21:10               ` Jack Johnson
2006-05-08 21:17                 ` andrey mirtchovski
2006-05-08 21:18                 ` Paul Lalonde
2006-05-08 22:25                 ` Francisco J Ballesteros
2006-05-09 21:56                   ` Dave Eckhardt
2006-05-10  0:13                     ` geoff
2006-05-10  8:39                       ` Lluís Batlle
2006-05-08 23:31                 ` geoff
2006-05-09  1:18                   ` Paul Lalonde
2006-05-09  1:39                     ` quanstro
2006-05-09  2:12                       ` Paul Lalonde
2006-05-09  2:20                         ` quanstro
2006-05-09  3:00                           ` Paul Lalonde
2006-05-09  9:32                             ` Bruce Ellis
2006-04-26 22:57     ` Roman Shaposhnick
2006-04-26  4:57 ` David Leimbach
2006-04-26  4:53   ` Ronald G Minnich
2006-04-26  5:11     ` Roman Shaposhnick
2006-04-25  2:30 erik quanstrom
2006-04-25  2:48 ` Derek Fawcus
2006-04-24 20:37 Ronald G Minnich
2006-04-24 20:51 ` Charles Forsyth
2006-04-24 21:32 ` Brantley Coile
2006-04-25 11:06   ` Anthony Sorace
2006-04-25 11:08     ` Anthony Sorace
2006-04-25  2:15 ` Derek Fawcus
2006-04-25  2:23   ` Roman Shaposhnick
2006-04-25  2:37     ` Derek Fawcus
2006-04-25  3:51       ` Roman Shaposhnick
2006-04-25  8:17         ` Derek Fawcus
2006-04-25 17:53           ` Roman Shaposhnick
2006-04-26  1:11             ` Derek Fawcus
2006-04-26  1:19               ` Roman Shaposhnick
2006-04-26  2:12                 ` Derek Fawcus
2006-04-25  3:02   ` Andy Newman
2006-04-25  3:13     ` Ronald G Minnich
2006-04-25 19:57     ` Dan Cross

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=5ff0a30a1e679e61ff04ca7a4cdcfa4c@quanstro.net \
    --to=quanstro@quanstro.net \
    --cc=9fans@cse.psu.edu \
    /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;
as well as URLs for NNTP newsgroup(s).