mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Rodrigo Alencar <455.rodrigo.alencar@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Jonathan Cameron <jic23@kernel.org>,
	David Lechner <dlechner@baylibre.com>,
	Andy Shevchenko <andy@kernel.org>
Subject: Re: [PATCH v5 2/7] lib: kstrtox: round to nearest, ties to even in kstrto[u]dec64()
Date: Wed, 4 Nov 2026 12:56:47 +0200	[thread overview]
Message-ID: <ausPb3rf9X4FNHtI@ashevche-desk.local> (raw)
In-Reply-To: <7qc3geup2edufde3wbx5wsyhjz6tcnekoa4c4alxudqb7buvmf@lijbrfhachls>

On Wed, Nov 04, 2026 at 06:04:38AM -0300, Rodrigo Alencar wrote:
> On 03/11/26 19:55, Andy Shevchenko wrote:
> > On Mon, Nov 02, 2026 at 07:41:00AM -0300, Rodrigo Alencar via B4 Relay wrote:
> > 
> > > kstrtoudec64() and kstrtodec64() drop the digits beyond the requested
> > > scale, which truncates the result toward zero. The error is up to one
> > > unit in the last place and is always in the same direction.
> > > 
> > > This is easy to hit with values produced by userspace floating point
> > > formatting. Printing 0.3 with "%.17g" gives "0.29999999999999999",
> > > which is parsed as 299999 with a scale of 6 instead of 300000. With E
> > > notation a negative exponent can also drop integer digits, so "19e-1"
> > > with a scale of 0 gives 1 instead of 2.
> > 
> > To avoid unneeded brain work it would be nice to add an example for negative
> > input, like -19e-01. And I hope (and it seems the case) we have test cases
> > for that.
> 
> We do have the tests:
> 
> 	/* E notation: negative exponent rounds integer digits */
> 	{"-27e-4",		3,	-3LL},
> 	{"-125e-1",		0,	-12LL},
> 	{"-135e-1",		0,	-14LL},

Thanks! What I meant is to elaborate in the commit message, that the reader can
easily understand how it works for either of the sign of a value.

> > > Round the result to nearest instead, with ties to even. This is the
> > > IEEE 754 default rounding mode, as used by strtod() and printf(), and it
> > > does not bias results in either direction. The first discarded digit is
> > > known from where parsing stopped, so no extra pass over the string is
> > > needed: the remaining digits are only checked when the first discarded
> > > digit is a 5. Since round-half-even is symmetric, kstrtodec64() keeps
> > > rounding the magnitude and negates it.
> > > 
> > > Inputs that fit within the scale are parsed exactly as before. An input
> > > that rounds up past the type limit, such as "18446744073.7095516155"
> > > with a scale of 9, now returns -ERANGE.
> > > 
> > > Update the existing truncation test cases and add cases for ties and
> > > for rounding at the type limits.

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2026-11-04 10:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-02 10:40 [PATCH v5 0/7] Add E notation support to kstrtodec64() and IIO sysfs writes Rodrigo Alencar via B4 Relay
2026-11-02 10:40 ` [PATCH v5 1/7] lib: kstrtox: support E notation in kstrtoudec64() and kstrtodec64() Rodrigo Alencar via B4 Relay
2026-11-03 17:51   ` Andy Shevchenko
2026-11-02 10:41 ` [PATCH v5 2/7] lib: kstrtox: round to nearest, ties to even in kstrto[u]dec64() Rodrigo Alencar via B4 Relay
2026-11-03 17:55   ` Andy Shevchenko
2026-11-04  9:04     ` Rodrigo Alencar
2026-11-04 10:56       ` Andy Shevchenko [this message]
2026-11-02 10:41 ` [PATCH v5 3/7] lib: kstrtox: allow a negative scale " Rodrigo Alencar via B4 Relay
2026-11-02 10:41 ` [PATCH v5 4/7] lib: test-kstrtox: add E notation tests for kstrto[u]dec64() Rodrigo Alencar via B4 Relay
2026-11-02 10:41 ` [PATCH v5 5/7] iio: test: rescale: compare scales against the precision of the output Rodrigo Alencar via B4 Relay
2026-11-02 10:41 ` [PATCH v5 6/7] iio: core: use kstrtodec64() to parse fixed-point values Rodrigo Alencar via B4 Relay
2026-11-02 10:41 ` [PATCH v5 7/7] iio: test: add kunit tests for channel info writes Rodrigo Alencar via B4 Relay

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=ausPb3rf9X4FNHtI@ashevche-desk.local \
    --to=andriy.shevchenko@intel.com \
    --cc=455.rodrigo.alencar@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=andy@kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®