public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Szabolcs Nagy <szabolcs.nagy@arm.com>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH] elf: Remove allocate use on _dl_debug_printf
Date: Tue, 1 Nov 2022 15:06:58 +0000	[thread overview]
Message-ID: <Y2E2Eh1ms1cZfx15@arm.com> (raw)
In-Reply-To: <20221031190131.2183199-1-adhemerval.zanella@linaro.org>

The 10/31/2022 16:01, Adhemerval Zanella wrote:
> The maximum number of directives is already limited by the maximum
> value of iovec, and current padding usage on _dl_map_object_from_fd
> specifies a value of 16 (2 times sizeof (void *)) in hexa, which is
> lesser than the INT_STRLEN_BOUND(void *) (20 for LP64).

less than

> 
> This works if pointer are larger than 8 bytes, for instance 16.

pointers are

> In this case the maximum padding would be 32 and the IFMTSIZE would
> be 40.
> 
> The resulting code does use a slight larger static stack, below it

slightly
s/below it//

> the output of -fstack-usage (for x86_64):
> 
>  * master:
>    dl-printf.c:35:1:_dl_debug_vdprintf     1344    dynamic
> 
>  * patch:
>    dl-printf.c:36:1:_dl_debug_vdprintf     2416    static
> 
> However, there is an improvement in code generation:
> 
>  * master
>    text    data     bss     dec     hex filename
>    3309       0       0    3309     ced elf/dl-printf.os
> 
>  * patch
>    text    data     bss     dec     hex filename
>    3151       0       0    3151     c4f elf/dl-printf.os
> 
> Checked on x86_64-linux-gnu.

looks good with typos fixed in the commit message.

Reviewed-by: Szabolcs Nagy <szabolcs.nagy@arm.com>

> ---
>  elf/dl-printf.c | 15 +++++++--------
>  1 file changed, 7 insertions(+), 8 deletions(-)
> 
> diff --git a/elf/dl-printf.c b/elf/dl-printf.c
> index 00c114002c..1b55c87cfd 100644
> --- a/elf/dl-printf.c
> +++ b/elf/dl-printf.c
> @@ -27,6 +27,7 @@
>  #include <string.h>
>  #include <sys/uio.h>
>  #include <unistd.h>
> +#include <intprops.h>
>  
>  /* Bare-bones printf implementation.  This function only knows about
>     the formats and flags needed and can handle only up to 64 stripes in
> @@ -36,6 +37,9 @@ _dl_debug_vdprintf (int fd, int tag_p, const char *fmt, va_list arg)
>  {
>  # define NIOVMAX 64
>    struct iovec iov[NIOVMAX];
> +  /* Maximum size for 'd', 'u', and 'x' including padding.  */
> +  enum { IFMTSIZE = INT_STRLEN_BOUND(void *) };
> +  char ifmtbuf[NIOVMAX][IFMTSIZE];
>    int niov = 0;
>    pid_t pid = 0;
>    char pidbuf[12];
> @@ -100,6 +104,8 @@ _dl_debug_vdprintf (int fd, int tag_p, const char *fmt, va_list arg)
>  	  if (*fmt == '*')
>  	    {
>  	      width = va_arg (arg, int);
> +	      /* The maximum padding accepted is up to pointer size.  */
> +	      assert (width < IFMTSIZE);

OK

>  	      ++fmt;
>  	    }
>  
> @@ -160,14 +166,7 @@ _dl_debug_vdprintf (int fd, int tag_p, const char *fmt, va_list arg)
>  #endif
>  		  }
>  
> -		/* We use alloca() to allocate the buffer with the most
> -		   pessimistic guess for the size.  Using alloca() allows
> -		   having more than one integer formatting in a call.  */
> -		int size = 1 + 3 * sizeof (unsigned long int);
> -		if (width + 1 > size)
> -		  size = width + 1;
> -		char *buf = (char *) alloca (size);
> -		char *endp = &buf[size];
> +		char *endp = &ifmtbuf[niov][IFMTSIZE];
>  		char *cp = _itoa (num, endp, *fmt == 'x' ? 16 : 10, 0);

OK.

>  
>  		/* Pad to the width the user specified.  */
> -- 
> 2.34.1
> 

      reply	other threads:[~2022-11-01 15:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-31 19:01 Adhemerval Zanella
2022-11-01 15:06 ` Szabolcs Nagy [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=Y2E2Eh1ms1cZfx15@arm.com \
    --to=szabolcs.nagy@arm.com \
    --cc=adhemerval.zanella@linaro.org \
    --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).