From: "Michał Nazarewicz" <m.nazarewicz@samsung.com>
To: Michal Nazarewicz <mina86@mina86.com>,
Denys Vlasenko <vda.linux@googlemail.com>
Cc: linux-kernel@vger.kernel.org,
"Douglas W. Jones" <jones@cs.uiowa.edu>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCHv2 1/3] lib: vsprintf: optimised put_dec_trunc() and put_dec_full()
Date: Tue, 10 Aug 2010 09:39:46 +0200 [thread overview]
Message-ID: <op.vg7owkd67p4s8u@pikus> (raw)
In-Reply-To: <201008100517.48231.vda.linux@googlemail.com>
> On Sunday 08 August 2010 21:29, Michal Nazarewicz wrote:
>> + /*
>> + * '(x * 0xcccd) >> 19' is an approximation of 'x / 10' that
>> + * gives correct results for all x < 81920. However, because
>> + * intermediate result can be at most 32-bit we limit x to be
>> + * 16-bit.
>> + *
>> + * Because of those, we check if we are dealing with a "big"
>> + * number and if so, we make it smaller remembering to add to
>> + * the most significant digit.
>> + */
>> + if (q >= 50000) {
>> + a = '5';
>> + q -= 50000;
> ...
>> + /*
>> + * We need to check if q is < 65536 so we might as well check
On Tue, 10 Aug 2010 05:17:48 +0200, Denys Vlasenko <vda.linux@googlemail.com> wrote:
> You meant "need to check if q is < 81920"?
No. 81920 is a 17 bit number and when we multiply it by 0xcccd we lose
the most significant bit. Therefore we cannot use the '(x * 0xcccd) >>
19' approximation for numbers which are higher then 65535.
>> + * if we can just call the _full version of this function.
>> + */
>> + if (q > 9999)
>> + return put_dec_full(buf, q);
--
Best regards, _ _
| Humble Liege of Serenely Enlightened Majesty of o' \,=./ `o
| Computer Science, Michał "mina86" Nazarewicz (o o)
+----[mina86*mina86.com]---[mina86*jabber.org]----ooO--(_)--Ooo--
next prev parent reply other threads:[~2010-08-10 7:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-08 19:29 [PATCHv2 1/3] lib: vsprintf: optimised put_dec_trunc() and put_dec_full() Michal Nazarewicz
2010-08-08 19:29 ` [PATCHv2 2/3] lib: vsprintf: optimised put_dec() for 32-bit machines Michal Nazarewicz
2010-08-08 19:29 ` [PATCHv2 3/3] lib: vsprintf: added a put_dec() test and benchmark tool Michal Nazarewicz
2010-08-10 4:15 ` [PATCHv2 2/3] lib: vsprintf: optimised put_dec() for 32-bit machines Denys Vlasenko
2010-08-10 7:42 ` Michał Nazarewicz
2010-08-10 16:10 ` Denys Vlasenko
2010-08-10 3:17 ` [PATCHv2 1/3] lib: vsprintf: optimised put_dec_trunc() and put_dec_full() Denys Vlasenko
2010-08-10 7:39 ` Michał Nazarewicz [this message]
2010-08-10 16:08 ` Denys Vlasenko
2010-08-10 22:42 ` Michal Nazarewicz
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=op.vg7owkd67p4s8u@pikus \
--to=m.nazarewicz@samsung.com \
--cc=akpm@linux-foundation.org \
--cc=jones@cs.uiowa.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=mina86@mina86.com \
--cc=vda.linux@googlemail.com \
/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.