public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Faissal Bensefia <faissaloo@me.com>, libc-alpha@sourceware.org
Subject: Re: Faster string to integer conversion
Date: Sun, 10 Apr 2016 19:54:00 -0000	[thread overview]
Message-ID: <570AAF76.6090007@cs.ucla.edu> (raw)
In-Reply-To: <570A225E.20409@me.com>

Thanks for thinking about this. Certainly strtol etc. could be sped up and the 
approach you mention might be a win; it's hard to say, given its setup overhead. 
In practice most integers are small, and you'd need to benchmark the approach on 
a set of integers that are of "typical" size. It may well be more work to come 
up with a convincing benchmark than to come up with the actual code.

If you're interested in strtol speedup ideas, how about this one? Jettison 
tables like __strtol_ul_max_tab and replace their uses with invocations of the 
INT_ADD_WRAPV macro defined by the following recently-proposed patch:

https://sourceware.org/ml/libc-alpha/2016-04/msg00174.html

      reply	other threads:[~2016-04-10 19:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-10  9:52 Faissal Bensefia
2016-04-10 19:54 ` Paul Eggert [this message]

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=570AAF76.6090007@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=faissaloo@me.com \
    --cc=libc-alpha@sourceware.org \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).