public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Siddhesh Poyarekar <siddhesh@gotplt.org>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] gimple-ssa-sprintf: Fix typo in range check
Date: Fri, 26 Jul 2024 19:11:14 +0200	[thread overview]
Message-ID: <ZqPYsl7ZsVZhNl9Q@tucnak> (raw)
In-Reply-To: <20240725234838.3804003-1-siddhesh@gotplt.org>

On Thu, Jul 25, 2024 at 07:48:38PM -0400, Siddhesh Poyarekar wrote:
> The code to scale ranges for wide chars in format_string incorrectly
> checks range.likely to scale range.unlikely, which is a copy-paste typo
> from the immediate previous condition.
> 
> gcc/ChangeLog:
> 
> 	gimple-ssa-sprintf.cc (format_string): Fix type in range check
> 	for UNLIKELY for wide chars.
> 
> Signed-off-by: Siddhesh Poyarekar <siddhesh@gotplt.org>

LGTM.
What exactly the code really wants to do is unclear to me, what does
the INT_MAX on the target have to do with the minimum/maximum/expected
sizes of %S or %ls printed strings is unclear, target PTRDIFF_MAX
maybe.  And why it uses this
	  if (slen.range.something < target_int_max ())
	    slen.range.something *= something_else;
rather than say
	  slen.range.something
	    = MIN (slang.range.something * something_else, target_int_max ());
perhaps with some overflow checking is also something that is hard to guess.
In any case, I think your patch is a step in the right direction.

> --- a/gcc/gimple-ssa-sprintf.cc
> +++ b/gcc/gimple-ssa-sprintf.cc
> @@ -2623,7 +2623,7 @@ format_string (const directive &dir, tree arg, pointer_query &ptr_qry)
>  	  if (slen.range.likely < target_int_max ())
>  	    slen.range.likely *= 2;
>  
> -	  if (slen.range.likely < target_int_max ())
> +	  if (slen.range.unlikely < target_int_max ())
>  	    slen.range.unlikely *= target_mb_len_max ();
>  
>  	  /* A non-empty wide character conversion may fail.  */
> -- 
> 2.45.1

	Jakub


  reply	other threads:[~2024-07-26 17:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-25 23:48 Siddhesh Poyarekar
2024-07-26 17:11 ` Jakub Jelinek [this message]
2024-07-26 17:39   ` Siddhesh Poyarekar
2024-07-26 18:19     ` Jakub Jelinek

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=ZqPYsl7ZsVZhNl9Q@tucnak \
    --to=jakub@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=siddhesh@gotplt.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).