public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Laight <david.laight.linux@gmail.com>
To: "licheng.li" <im.lechain@gmail.com>
Cc: "Willy Tarreau" <w@1wt.eu>,
	"Thomas Weißschuh" <linux@weissschuh.net>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/2] tools/nolibc: support left alignment (-) in printf
Date: Fri, 30 Jan 2026 15:00:39 +0000	[thread overview]
Message-ID: <20260130150039.33fb29ba@pumpkin> (raw)
In-Reply-To: <20260130102218.1324-2-im.lechain@gmail.com>

On Fri, 30 Jan 2026 18:22:17 +0800
"licheng.li" <im.lechain@gmail.com> wrote:

> From: Cheng Li <im.lechain@gmail.com>
> 
> Currently, __nolibc_printf() in nolibc parses the width field but always
> pads with spaces on the left. It ignores the '-' flag (left alignment).
> 
> This patch implements support for the '-' flag
> to forces left alignment by padding spaces on the right.
> 
> Logic behavior:
>  - "%5d"  -> "   -5" (unchanged, right align)
>  - "%-5d" -> "-5   " (new, left align)
> 
> Suggested-by: David Laight <david.laight.linux@gmail.com>
> Suggested-by: Willy Tarreau <w@1wt.eu>
> Signed-off-by: Cheng Li <im.lechain@gmail.com>

Looks reasonable.

Reviewed-by: David Laight <david.laight.linux@gmail.com>

	David

> ---
> v4 changes:
>  - Adopted optimization suggestions from David Laight
> v3 changes:
>  - Removed pad zeros support because of bug for signed number and pointer
> v2 changes:
>  - Adopted optimization suggestions from Willy Tarreau:
>    - Incremented 'written' counter at the start of loops.
>    - Reordered loop checks to optimize compiler register usage.
>  - Updated commit message to explicitly mention zero-padding ('0') support.
> ---
>  tools/include/nolibc/stdio.h | 17 +++++++++++++----
>  1 file changed, 13 insertions(+), 4 deletions(-)
> 
> diff --git a/tools/include/nolibc/stdio.h b/tools/include/nolibc/stdio.h
> index 1f16dab2ac88..1197928a1364 100644
> --- a/tools/include/nolibc/stdio.h
> +++ b/tools/include/nolibc/stdio.h
> @@ -250,7 +250,7 @@ typedef int (*__nolibc_printf_cb)(intptr_t state, const char *buf, size_t size);
>  static __attribute__((unused, format(printf, 4, 0)))
>  int __nolibc_printf(__nolibc_printf_cb cb, intptr_t state, size_t n, const char *fmt, va_list args)
>  {
> -	char escape, lpref, c;
> +	char escape, lpref, padc, c;
>  	unsigned long long v;
>  	unsigned int written, width;
>  	size_t len, ofs, w;
> @@ -261,11 +261,17 @@ int __nolibc_printf(__nolibc_printf_cb cb, intptr_t state, size_t n, const char
>  	while (1) {
>  		c = fmt[ofs++];
>  		width = 0;
> +		padc = ' ';
>  
>  		if (escape) {
>  			/* we're in an escape sequence, ofs == 1 */
>  			escape = 0;
>  
> +			if (c == '-') {
> +				padc = c;
> +				c = fmt[ofs++];
> +			}
> +
>  			/* width */
>  			while (c >= '0' && c <= '9') {
>  				width *= 10;
> @@ -358,12 +364,15 @@ int __nolibc_printf(__nolibc_printf_cb cb, intptr_t state, size_t n, const char
>  			if (n) {
>  				w = len < n ? len : n;
>  				n -= w;
> -				while (width-- > w) {
> +				if (padc == '-' && cb(state, outstr, w) != 0)
> +					return -1;
> +				while (width > w) {
> +					written++;
>  					if (cb(state, " ", 1) != 0)
>  						return -1;
> -					written += 1;
> +					width--;
>  				}
> -				if (cb(state, outstr, w) != 0)
> +				if (padc != '-' && cb(state, outstr, w) != 0)
>  					return -1;
>  			}
>  


  reply	other threads:[~2026-01-30 15:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-30 10:22 [PATCH v4 0/2] tools/nolibc: support left-aligned printing in printf licheng.li
2026-01-30 10:22 ` [PATCH v4 1/2] tools/nolibc: support left alignment (-) " licheng.li
2026-01-30 15:00   ` David Laight [this message]
2026-01-30 10:22 ` [PATCH v4 2/2] selftests/nolibc: add tests for printf left alignment and zero padding licheng.li

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=20260130150039.33fb29ba@pumpkin \
    --to=david.laight.linux@gmail.com \
    --cc=im.lechain@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@weissschuh.net \
    --cc=w@1wt.eu \
    /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